SJ-20100211152857-010-ZXWN MSCS (V3.09.21) MSC Server Common Configuration Operation Guide

ZXWN MSCS
MSC Server
Common Configuration Operation Guide

Version 3.09.21
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: (86) 755 26771900
Fax: (86) 755 26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2010 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution of
this document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATION
or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on the
information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subject
matter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee,
the user of this document shall not acquire any license to the subject matter herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No.
Revision Date
Revision Reason
R1.0
Feb. 28, 2010
First edition
Serial Number: SJ-20100211152857-010
Contents
About This Manual............................................. I

Declaration of RoHS Compliance ....................... I
Data Making for New Commissioning ................1
Overview....................................................................... 1
MGW Data Configuration ................................................. 1
Overview................................................................... 1
Interface Address Configuration.................................... 3
Overview .......................................................... 3
Creating a Loopback Interface ............................. 4
Creating an SIPI Interface Address ....................... 5
Creating a Static Route ............................................... 7
Adjacent Office and Topology Configuration .................... 8
Overview .......................................................... 8
Creating an MGW Adjacent Office ......................... 9
Creating an MGW Voice CODEC Template .............14
Creating a Topology Node...................................15
Creating an Inter-MGW Bearer Mode ...................19
SIGTRAN Configuration ..............................................22
Overview .........................................................22
Creating an SCTP ..............................................24
Creating an ASP................................................27
Creating an AS .................................................28
Creating an M3UA Static Route ...........................32
Creating the SIO-Locating-AS .............................33
H.248 Configuration...................................................35
Overview .........................................................35
Creating MGC Static Data...................................37
Creating an MGW Static Data Template ................38
Creating MGW Static Data ..................................40
Creating a TID Analyzer .....................................41
Creating a TID Analyzer Entry.............................43
Confidential and Proprietary Information of ZTE CORPORATION
ZXWN MSCS Common Configuration Operation Guide
HLR Data Configuration ..................................................44

Overview..................................................................44
Creating a HLR Adjacent Office ....................................47
Signaling Data Configuration .......................................48
Creating a Signaling Link Set ..............................48
Creating an SPB-Accessed Signaling Link .............50
Creating a Signaling Route .................................53
Creating a Signaling Office .................................55
Creating IMSI Analysis ...............................................57
SCCP Data Configuration ............................................59
Creating GT Translation Selector .........................59
Creating GT Translation Data ..............................63
STP Data Configuration ..................................................69
Overview..................................................................69
Creating an STP Adjacent Office ..................................71
Signaling Data Configuration .......................................73
Creating a Signaling Link Set to the STP...............73
Creating a Signaling Link to the STP ....................75
Creating a Signaling Route to the STP ..................78
Creating a Signaling Office to the STP ..................79
Creating a GT Translation Data ....................................81
SCP Data Configuration (Destination Network)...................85
Overview..................................................................85
Creating a Signaling Subsystem ..................................87
Creating GT Translation Data.......................................89
Creating the CAMEL Configuration................................93
Recharge and Query Configuration ...............................94
Creating CAMEL Access Subscription
Information...........................................94
Creating Called Number Analysis.........................97
Configuration Related to Intelligent Tone Play ................99
Creating Interconnection Conversion for Service
Keys................................................... 100
Creating Tone Keys on the MGW Tone Board ......... 102
SMC Data Configuration ............................................... 104
Overview................................................................ 104
Creating GT Translation Data..................................... 106
Modifying VLR-Supported Services ............................. 110
Modifying Mobile Data of Local Office.......................... 111
PSTN/2G MSC (M3UA) Data Configuration....................... 111
II
Overview................................................................ 111
Creating 2G MSC/PSTN Adjacent Office....................... 113
Configuration Related to Trunk and Route ................... 115
Creating a DT Trunk Group ............................... 115
Creating a PCM System.................................... 119
Creating an Outgoing Route.............................. 121
Creating an Outgoing Route Set ........................ 122
Creating an Outgoing Route Link ....................... 123
SIGTRAN Configuration ............................................ 126
Creating an SCTP ............................................ 126
Creating an ASP.............................................. 129
Creating an AS ............................................... 130
Creating an M3UA Static Route ......................... 133
Creating the SIO-Locating-AS ........................... 134
BSC Data Configuration ................................................ 137
Overview................................................................ 137
Office Direction and Topology Configuration................. 139
Creating a BSC Adjacent Office ......................... 139
Creating BSC Office Direction............................ 143
Creating a BSC Topology Node .......................... 145
Creating the Topology Relationship between BSC
and MGW ............................................ 148
Trunk and PCM Configuration .................................... 150
Creating a DT Trunk Group ............................... 150
SIGTRAN Configuration ............................................ 159
Creating an SCTP ............................................ 159
Creating an ASP.............................................. 161
Creating an AS ............................................... 163
Creating an M3UA Static Route ......................... 165
Creating the SIO-Locating-AS ........................... 166
RNC Data Configuration................................................ 168
Overview................................................................ 168
Creating an RNC Adjacent Office................................ 170
Office Direction and Topology Configuration................. 174
Creating RNC Office Direction ........................... 174
Creating an RNC Topology Node ........................ 178
Creating the Topology Relationship between RNC
and MGW ............................................ 181
Trunk and PCM Configuration .................................... 183
III
Creating an ATM Trunk Group ........................... 183

Access Data Configuration............................. 193

Overview.................................................................... 193
Creating Emergency Call Center .................................... 194
Special Serivce Configuration ........................................ 196
Creating a Special Service Phone Group...................... 196
Creating the Special Service Phone Called Number
Analysis ......................................................... 199
LAI and GCI/Service Area Configuration.......................... 201
Creating a LAI Controlled by the Local Office ............... 201
Creating an Adjacent LAI .......................................... 205
Creating a Global Cell............................................... 209
Creating a Service Area ............................................ 211
Number Analysis Data Making ....................... 213

Number Analysis ......................................................... 213
Number Analysis Configuration ...................................... 218
Overview................................................................ 218
Creating a Number Analyzer Entry ............................. 218
Creating a DAS ....................................................... 221
Setting the Default DAS Template of the Local
Office............................................................. 223
Creating a DAS Template .......................................... 226
Creating the Called Number Analysis .......................... 230
Tone Configuration ........................................ 257

Creating MSCS Tones in Batches .................................... 257
Creating the Fixed Tone Play Data.................................. 258
Creating the Basic Service Tone Play Data....................... 265
Creating the Intelligent Service Tone Play Data ................ 274
Figure............................................................ 283
Table ............................................................. 285
Index ............................................................ 289
IV
About This Manual

Purpose
At first, thank you for choosing ZXWN wireless core network system of ZTE Corporation!
ZXWN system is the 3G mobile communication system developed
based on the UMTS technology. ZXWN system boasts powerful
service processing capability in both CS domain and PS domain,
providing more abundant service contents. Comparing with the
GSM, ZXWN provides telecommunication services in wider range,
capable of transmitting sound, data, graphics and other multi-media services. In addition, ZXWN has higher speed and resource utilization rate. ZXWN wireless core network system supports both
2G and 3G subscriber access, and provides various services related with the 3G core network.
The ZXWN MSCS system is designed for the UMTS system at the
core network control level. It supports the GSM core network,
UMTS protocols in the R99/R4/R5 stage and relevant functions at
the same time, and provides the carriers with an overall solution
to the evolution from the GSM core network to the 3GPP R99 and
then to the 3GPP R5.
The ZXWN MSCS system completes the functions of the Mobile
Switching Center Server and the Visitor Location Register (VLR)
together, and provides the Service Switching Point (SSP) functions
of intelligent calls. The ZXWN MSCS system supports the MGCF
function, and the coexistence of the MGCF and GMSCS. It also can
smoothly upgrade to the MGCF.
This manual aims to help operators master the methods of common data configuration of ZXWN MSCS.
Intended
Audience
This document is intended for engineers, technical and maintenance personnel who have mastered the principles of mobile network communications.
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:
What Is in This
Manual
CS network and its network elements
The basic knowledge, interfaces and protocols, and service

functions of ZXWN MSCS
This manual contains the following chapters:

Chapter
Summary
Chapter 1, Data Making

for New Commissioning
Introduces the procedure and method for

collecting and configuring interconnection
data so as to add various offices on the
soft-switch equipment that is normally
running in the current network
Chapter 2, Access Data

Configuration

configuring the location area and the cell
data on the MSCS
FCC Compliance
Statement
Chapter
Summary
Chapter 3, Number
Analysis Data Making
Introduces the procedure and method

for configuring the number analysis data
when the soft-switch equipment runs in
the current network normally
Chapter 4, Tone
Configuration

configuring the tone resources and tone
play data
This device complies with part 15 of the FCC Rules. Operation is

subject to the following two conditions.
1. This device may not cause harmful interference.
2. This device must accept any interference received, including
interference that may cause undesired operation.
Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate
the equipment.
Conventions
ZTE documents employ the following typographical conventions.

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.
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.
Mouse operation conventions are listed as follows:
II
Typeface
Meaning
Click
Refers to clicking the primary mouse button (usually the

left mouse button) once.
Doubleclick
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.
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 ZXWN MSCS 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 ZXWN MSCS 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.
This page is intentionally blank.
II
Chapter
Data Making for New

Commissioning
Table of Contents
Overview........................................................................... 1
MGW Data Configuration ..................................................... 1
HLR Data Configuration ......................................................44
STP Data Configuration ......................................................69
SCP Data Configuration (Destination Network).......................85
SMC Data Configuration ................................................... 104
PSTN/2G MSC (M3UA) Data Configuration........................... 111
BSC Data Configuration .................................................... 137
RNC Data Configuration.................................................... 168
Overview
Description
This chapter introduces the procedure and method of collecting

and making interconnection data so as to add various office directions on the ZXWN MSCS equipment.
MGW Data Configuration

Overview
Typical
Networking
Mc interface is the interface between MSCS and MGW. The networking structure is shown in Figure 1.
FIGURE 1 NETWORKING BETWEEN MSCS
AND
MGW
The Mc interface usually uses the IP bearer. Its protocol stack uses
the H.248/M3UA/SCTP/IP mode.
Data Collection
Collect the data related to the Mc interface before data configuration, as described in Table 1.
TABLE 1 DATA COLLECTION TABLE
Configuration
Flow
Parameter Items
Parameter Values
Real address of the MSCS
192.168.1.11
Loopback address of the MSCS
192.168.11.11
Port number of the MSCS
2001
Real address of the MGW
192.168.1.31
Loopback address of the MGW
192.168.31.31
Port number of the MGW
2001
Coding scheme of H.248 protocol
TEXT
MSCS signaling point code
1.11.2
MGW signaling point code
1.31.2
This configuration aims to complete the interconnection between

the MSCS and the MGW over the Mc interface so as to achieve the
management and control over the media resources of the MGW.
Table 2 describes the configuration flow.
Chapter 1 Data Making for New Commissioning
TABLE 2 CONFIGURATION FLOW

Steps
Operations
Related Command
Creating a loop-back interface
INTERFACE
LOOPBACK
ADD IP ADDRESS
Creating an SIPI interface

address
INTERFACE
Creating a static route
ADD IP ROUTE
Creating an MGW adjacent

office
ADD ADJOFC
Creating an MGW voice

CODEC template
ADD CODECTPL
Creating a topology node
ADD TOPO
Creating an inter-MGW bearer

mode
ADD MGWBEARMOD
Creating an SCTP
ADD SCTPCONN
Creating an ASP
ADD ASP
10
Creating an AS
ADD AS
11
Creating an M3UA static route
ADD M3UART
12
Creating the SIO-locating-AS
ADD SIOLOCAS
13
Creating MGC static data
ADD MGCSCFG
14
Creating an MGW static data

template
ADD MGSTPL
15
Creating MGW static data
ADD MGSCFG
16
Creating a TID analyzer
ADD TIDANL
17
Creating a TID analyzer entry
ADD TIDENTR
ADD IP ADDRESS
Interface Address Configuration

Overview
Introduction
Interface IP addresses are planned according to the actual networking applications. The IP address of Nc, Iu-CS and other interfaces can be configuration independently, or share with the Mc
interface address.
Creating a Loopback Interface

Prerequisites
Before the operation, it is required to confirm:
The RPU module configuration is completed, and the RPU works

normally.
The MML Terminal window is opened.
Context
Creating the loopback interface means creating the service address on the RPU loopback port. Since the service address of Mc
interface can use ports 1 and 2, it is recommended that each port
is configured with one IP address.
Steps
1. If no exchange is specified, execute command SET on the MML

Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create the RPU loop back interface. The command is INTERF
ACE LOOPBACK.
Port represents the port number, ranging from 1 to 128.
Example: Create the loop-back interface whose port number
is 1.
The command is as follows.
INTERFACE LOOPBACK:PORT=1;
3. Create the interface address. The command is ADD IP ADDR
ESS.
Table 3 describes the main parameters in the ADD IP ADDRESS command.
TABLE 3 PARAMETERS IN THE ADD IP ADDRESS COMMAND
Parameter
Name
Parameter
Description
Instruction
ADDRESS
IP address
It is a mandatory parameter.
The IP address of the
loop-back address.
MASK
Mask
It is a mandatory parameter
of 32-bit. In general, it is
255.255.255.255.
BROADCASTIP
Broadcast IP
address
It is an optional parameter. In
general, it is 255.255.255.255.
Example: Create a loop back address with the following requirements.
IP address: 192.168.11.11
Subnet mask: 255.255.255.255.
ADD IP ADDRESS:ADDRESS="192.168.11.11",MASK="255
.255.255.255",BROADCASTIP="255.255.255.255";
4. Save the online configured data. Otherwise, these will loss
when the RPU is restarted.The command is SAVE ONLINEDA
TA;.
5. Exit the interface configuration mode. The command is EXIT;
END OF STEPS
Creating an SIPI Interface Address

Prerequisites
The SIPI unit is created.
Context
MSCS is interconnected to MGW on the CE through its SIPI board.

The online configuration of SIPI board interface is to assign an IP
address to some physical port of this SIPI board.
Steps

system tree.
SET:NEID=11;
2. Enter the SIPI board interface configuration mode. The command is INTERFACE.
Table 4 describes the main parameters in the INTERFACE
command.
TABLE 4 INTERFACE REAL INTERFACE
Parameter
Name
Parameter
Description
Instruction
SUBSYSTEM
Subsystem ID
Select the default value 0.
MODULE
Module No.
Select the default value 1.
UNIT
Unit No.
It is a mandatory parameter. It
is the unit number of the real
interface. Select the unit number
of the board corresponded by the
interface.
SUNIT
Subunit No
It is a mandatory parameter. Real

interfaces sub-unit number fixedly
adopts 1.
Port number
It is a mandatory parameter. The

port number refers to the network
interface serial number of the
SIPI rear board for connecting to
the external. The four network
PORT
Parameter
Name
Parameter
Description
Instruction
interfaces are numbered 1 to 4
from top to bottom. Only the first
port is used.
Example: Create the interface address of SIPI board. The configuration requirements are as follows.
Unit number: 321
Sub-unit number: 1
Port number: 1
Home module number: No.1 OMP module.

INTERFACE:SUBSYSTEM=0,MODULE=1,UNIT=321,SUNI
T=1,PORT=1;
3. Create the interface address of the SIPI. The command is ADD
IP ADDRESS.
Table 5 describes the main parameters in the ADD IP ADDR
ESS command.
TABLE 5 ADD IP ADDRESS REAL INTERFACE
Parameter
Name
Parameter
Description
Instruction
ADDRESS
IP address
The Mc interface address of SIPI
board
MASK
Subnet mask
It is a mandatory parameter. The

real interface subnet address of
corresponding interface board
BROADCASTIP
Broadcast IP
address
It is an optional parameter,
corresponding to the broadcast
address of the real address of the
corresponding interface board.
Example: The configured parameters are as follows.
IP address: 192.168.1.11
Subnet mask: 255.255.255.248
Broadcast address: 255.255.255.255.

ADD IP ADDRESS:ADDRESS="192.168.1.11",MASK="255.
255.255.248",BROADCASTIP="255.255.255.255";
4. Save the online configured data. Otherwise, these will loss
when the RPU is restarted.The command is SAVE ONLINEDA
TA;.
5. Exit the interface configuration mode. The command is EXIT;

END OF STEPS
Creating a Static Route

Prerequisites
The interface address is created.
The BFD parameters are created when load-sharing networking

mode is adopted.
Context
Static route is created when the service IP address of local signaling plane and PE interface address are not in the same network section. Under the active/standby working mode, a destination address needs to be configured with a route only. Under the
load-sharing working mode, a destination address usually needs
to be configured with two routes.
Steps

system tree.
SET:NEID=11;
2. Create the static route. The command is ADD IP ROUTE.
Table 6 describes the parameters in the ADD IP ROUTE command.
TABLE 6 PARAMETERS IN THE ADD IP ROUTE COMMAND
Parameter
Name
Parameter
Description
NETPRE
Net prefix
MASK
Mask
Instruction
Type the network section of the
opposite-end equipment service
address according to the network
planning. Its prefix should match
its mask
NEXTHOP
Next hop IP
indicating the router interface
address (VRRP address). Type the
gateway address to the opposite
end office
DISTANCE
Distance
It is an optional parameter with a

default of 1, ranging from 1 to 254
BFDDETECT
Enable BFD
Detect
general, select NO. The setting
Enable BFD Detect is effective
only when IP address acts as the
next hop.
Example: Create the static route to the opposite end with the
following requirements.
Working mode: active/standby mode
Service address of the opposite equipment: 11.11.11.11
Mask: 255.255.255.0
Next hop IP: 10.0.74.1.
The command is as follows:

ADD IP ROUTE:NETPRE="11.11.11.11",MASK="255.255.
255.0",NEXTHOP="10.0.74.1",DISTANCE=1,BFDDETECT
=NO;
Example: Create two static routes to the opposite end with the
Working mode: load-sharing mode
Service address of the opposite equipment: 11.11.11.11
Mask: 255.255.255.0
Next hop IP: 10.0.74.1 and 10.0.74.2.

=NO;
=NO;
END OF STEPS
Adjacent Office and Topology

Configuration
Overview
Introduction
Adjacent office configuration means configuring the neighboring

office of the local office. There are two association modes, direct
association and quasi-association.
If the adjacent office is regarded as a node in the whole network
topology when the local office is in the center, topological node
configuration means adding the topological node of its adjacent
office in the local office. The topological nodes configured on MSCS
include MGW, RNC/BSC, and MSCS (Nc).
Configuration
Flow
Steps
Operations
Instructions
Command
Creating an MGW
adjacent office
Create the basic information of

MGW adjacent office.
ADD ADJOFC
Creating an MGW
voice CODEC template
Create the encoding and decoding

speech type modules supported by
IM-MGW.
ADD CODECTPL
Creating a topology node
Create the topology

relationship
between
MGCF
node and IM-MGW
node.
ADD TOPO
Creating
interMGW bear mode
(optional)
The
inter-MGW
bearer mode is
configured when
the Nb interfaces
between several
IM-MGWs
under
the same MGCF
are connected.
ADD MGWBEAR
MOD
Creating an MGW Adjacent Office

Prerequisites
The physical IP connection between the MSCS and the MGW

is clear, which is implemented by the connection between the
FE1 interfaces on the rear board of the SIPI boards of these
two NEs.
The signaling interworking data is planned and negotiated.
The basic configuration of the local office is completed.
The range of adjacent office number is configured in the resource management.
Context
Perform this procedure to configure the basic information of MGW

adjacent office. On the MSCS, each MGW is configured with three
adjacent offices according to the SCTP Planning.
Steps

system tree.
SET:NEID=11;
2. Create the MGW adjacent office. The command is ADD ADJO
FC.
Table 7 describes the main parameters in the ADD ADJOFC
command.
TABLE 7 PARAMETERS IN THE ADD ADJOFC COMMAND

Parameter
Name
Parameter
Description
Instruction
ID
Office ID
A mandatory parameter,
indicating the identification
number of the adjacent
office, and ranging from
1 to 3000. In general,
it is configured as the
exchange ID of the
adjacent office during the
all-network planning
NAME
User-defined alias
It is a mandatory
parameter. Type a
customized name.
Network type
A mandatory parameter,
indicating the network
type of the SPC used for
connecting the local office
to the adjacent office
when the local office is
configured with several
SPs. The default is the
network type of this SP
when there is only one SP
in the local office
OFCTYPE
The type of adjacent

office
It is a mandatory
parameter. Select MGW
for the MGW bearing H248
signaling. Select SGW for
another two MGW offices.
SPCFMT
SPC format
Select TRIPLE_DEC.
NET
SPCTYPE
SPC type
DPC
Destination SPC
RC
10
Area code
It is a mandatory
parameter. Select it
based on the SPC type
of the adjacent office
according to the signaling
point planning. In China,
all the NEs adopt the 24-bit
SPC except the BSC that
adopts the 14-bit SPC.
indicating the local toll
zone code of the adjacent
office. This parameter
has impact on the area
code added by the calling
number
Parameter
Name
Parameter
Description
Instruction
Association type,
including:
ASSOTYPE
SPTYPE
AM_SURE (direct
connection mode)
AM_QUASI (half
direct connection
mode)
AM_NONE (none
connection mode).
Signaling point type,

including SEP, STP,
and STEP
It is an optional parameter.
Select AM_SURE
Select SEP (signaling
end point) for the MGW
bearing H248 signaling.
Select STEP (signaling
transition / end point) for
another two MGW offices
Subservice function,
including
INTERNATIONAL
(International
signaling point
code)
INTERNATIONAL
STANDBY
(International
standby signaling
point code)
SSF
NATIONAL
(National signaling
point code)
NATIONAL
STANDBY
(National standby
signaling point
code).
In general, NATIONAL
is selected at home. For
the BSC adjacent office,
NATIONAL STANDBY is
selected.
Office Attribute,
including:
TAG
ISNI (Has ISNI

Function)
TRANS (Translate
Node)
It is an optional parameter
TEST (Need Test

Info:0X02/0X01)
TEST
Test flag
It is used to set whether
the MTP3 link actively
initiates the link test
after entering the service
status. In most cases, this
parameter is selected.
11
Parameter
Name
Parameter
Description
Instruction
with a default of NO. It
is used for SCCP to judge
whether to use the LUDT
message.
BANDFLAG
Broadband attribute
The maximum length of a

broadband link message
is 4,000, and that of a
narrowband link message
is 255. Because the MTP
layer does not have the
segmentation function, the
incorrect configuration of
this parameter probably
causes the long packet to
be discarded.
Select this parameter
when all the links between
two SPs are SIGTRAN or
ATM signaling links.
Protocol Type,
including:
PRTCTYPE
CLST
CHINA (China)
ITU (International
Telecommunications Union)
ANSI (American
National Standards
Institute)
Cluster ID
The CHINA and the ITU
are used for the NO.7
signaling networking of
the ITU standard and the
ANSI is used for the NO.7
signaling networking of
the American standard.
In general, select CHINA
for the domestic office
and select ITU for the
international office
within 0~65535. In
general, select the default
value 65535. It is valid
when the protocol type
of the adjacent office is
ANSI. The signaling point
connected to the signaling
transfer point belongs to
the corresponding cluster
Office Info, including:
INFO
12
CIC_PCM (CIC
starts the load
sharing according
to the PCM code
mode)
BLOCK (Manual
block status)
EVEN_CIC (The
office controls
the even CIC
when CIC resource
contention occurs)
and the default value is
CIC_PCM
Parameter
Name
RELATEDOFC1
Parameter
Description
CALLING(Calling
transform is
allowed)
CALLED (Called
transform is
allowed)
MOD24_CIC (CIC
mode with 24
mode)
TEST (Dynamic
test)
Related Office ID
Instruction
ranging from 0 to 3000
Office Extend Info,

including:
SIGBRDCST
(Support Signaling
Broadcast
Message)
MTP (Hongkong
MTP Standard)
DUPU ( Screen
DUPU message)
SUA_REC_DT1
(Receive SUA
message and
handle it as DT1
message)
INFOEX
SUA_SND_DT1
(Send SUA
message and
handle it as DT1
message without
SN.)
OPEN_TG_RES
(Open outter trunk
group resource)
For example, create MGW adjacent office. The office ID is 101,

the alias is MGW1, and the destination SPC is 1.31.2. For other
parameters, adopt the default value. The command is as follows:
ADD
ADJOFC:ID=101,NAME="MGW1",NET=3,OFCTYPE
=MGW,SPCFMT=TRIPLE_DEC,SPCTYPE=14,DPC="1.31.2
",RC="25",ASSOTYPE=AM_SURE,SPTYPE=SEP,SSF=NATIO
NAL STANDBY,SUBPROTTYPE=DEFAULT,TEST=YES,BAND
FLAG=YES,PRTCTYPE=CHINA,CLST=65535,INFO="CIC_P
CM",RELATEDOFC1=0;
END OF STEPS
13
Creating an MGW Voice CODEC Template

Prerequisites
The basic configuration of the local office is completed.
The range of the MGW voice CODEC template numbers is configured in the resource management configuration.
Context
Perform this procedure to create the encoding and decoding

speech type modules supported by MGW. In general, MSCS is
configured with a default common voice CODEC template.
Steps

system tree.
SET:NEID=11;
2. Create the MGW voice CODEC template. The command is ADD
CODECTPL.
Table 8 describes the main parameters in the ADD CODECTPL
command.
TABLE 8 PARAMETERS IN THE ADD CODECTPL COMMAND
Parameter
Name
Parameter
Description
Instruction
ID
Template
number
for defining an encoding and
decoding speech template,
ranging from 1 to 255.
GRPID
The group
number of the
speech coding.
It is a mandatory parameter for

specifying the OID format and
encoding and decoding type list.
Up to eight types can be defined
in an encoding and decoding
template.
VALFG
Valid option,
including YES
(valid) and NO
(invalid)

setting whether this encoding
and decoding speech template is
valid. Select YES
specify an Organization Identifier
(OID).
It has the following parameters.
OID
14
OID
OID_NONE: No OID
OID_ITU_T: ITU_T
OID_ETSI: ETSI
OID_IETF: IETF
Parameter
Name
Parameter
Description
Instruction
ITYPE
ITU_T CODEC
type.
general, ITUT_G711A_64 is
selected.
ETYPE
ETSI CODEC
type
general, ETSI_UMTS_AMR
and ETSI_UMTS_AMR_2 are
selected.
ACTRATE
Activated
CODEC rate
general, the default value is
selected
SUPRATE
Supported
CODEC rate
selected
OM
ACS optimized
mode
selected
Example: Configure an MGW encoding and decoding speech

template with the following requirements.
Template ID: 1
CODEC group number: 1
Valid option: YES
OID: ETSI
ETSI CODEC type: ETSI_UMTS_AMR2
Activated CODEC rate: 5.90 K and 6.70 K
Supported CODEC rate: 5.90 K and 6.70 K
ACS optimize mode: Yes.
ADD
CODECTPL:ID=1,GRPID=GRPID1,VALFG=YES,OID
=OID_ETSI,ETYPE=ETSI_UMTS_AMR_2,ACTRATE="Rate59
0"&"Rate670",SUPRATE="Rate590"&"Rate670",OM=YES;
END OF STEPS
Creating a Topology Node

Prerequisites
Context
The encoding and decoding speech template is configured.
The range of the topological node number is configured in the

resource management.
Perform this procedure to configure the topology relationship

between MSCS node and MGW node. This command is used to
configure the adjacent NE information, including equipment type,
15
bearer type and attributes, user plane version, encoding and

decoding template, and other information.
For Mc interface, only the adjacent office bearing H.248 protocol
is configured as a topological node.
Steps

system tree.
SET:NEID=11;
2. Create an MGW topology node. The command is ADD TOPO.
Table 9 describes the main parameters in the ADD TOPO command.
TABLE 9 PARAMETERS IN THE ADD TOPO COMMAND
Parameter
Name
ID
OFCID
Parameter
Description
Topological node
ID
Office ID
Instruction
It is a mandatory parameter to
define ID of this node, ranging
from 1 to 2,048.
It is recommended that the ID
and office No. of a topological
node are consistent
for specifying the office ID of
this topological node. This
parameter must be defined by
the ADD ADJOFC command
first.
In this case, type the actual
MGW office number
NAME
CODECID
ETYPE
Alias
for naming this topological
node, with a length ranging
from 1 to 50 characters.
CODEC identity
for specify the CODEC
template used by this
topological node. This
parameter must be defined
by the ADD CODECTPL
command first.
Equipment type
This parameter is used to

specify the NE type of this
topological node.
Select R4GW for an MGW
node
PROTTYPE
16
Protocol type
Select H.248 for Mc interface.
Parameter
Name
IPVER
ATTR
Parameter
Description
Instruction
IP version of the
node
It is the IP protocol version

supported between nodes.
Select IPV4 or IPV6
according to the actual
conditions. Currently, IPV4 is
supported.
Bearer attributes
This parameter is only valid

for the node with the type
of R4GW (MGW). The bearer
types supported by MGW
are BNCAAL1, BNCAAL2,
BNCAAL1S, BNCIPRTP, and
BNCTDM. MGW can support
one or more of these types of
bearers.
In general, select BNCAAL2,
BNCIPRTP, and BNCTDM
UPVER
User plane
protocol version
of RNC or MGW
Extended
attributes (tunnel
mode), including:
NOTUNL
(None tunnel
mode)
RTUNL
(Rapid tunnel
mode)
ATTR2
DTUNL
(Delay tunnel
mode)
Signaling transfer
mode, including:
TRFMOD
MCINTF (Mc
interface signal
transfer mode)
This parameter is used to set

the user plane version of this
node.
In general, select V2

which tunnel mode is adopted
for bearer establishment when
this node supports the IP/RTP
bearer. The default value is
NOTUNL (None tunnel mode).
In general, select DTUNL
(Delay tunnel mode) for an
MGW topological node.

which mode is used by the
topology for reporting when
it detects CNG or CED fax
signals.
The default value is MCINTF
Error SDU
control, including
options:
UPERRCTRL
YES: The user

plane entity implements error
inspection, and
sets the FQC bit
position according to the result.
It will transmit
all frames includes the error
frames to the
user plane layer.
This parameter regulates the

handling method of the user
plane for error frames. It is
only valid for MGW-type and
RNC-type topological node.
The default value is YES
17
Parameter
Name
Parameter
Description
During a call, the
error packet control parameter
delerrsdu=Yes,
which is delivered
by the terminal
established by
MGW on the Mc
interface. The
deliveryOfErroneousSDU is YES,
NA, NA during
RAB assignment.
NO: The user
plane entity implements the
error inspection.
It will directly
discard the error
frame. During
a call, the error packet control parameter
delerrsdu=No,
which is delivered
by the terminal
established by
MGW on the Mc
interface. The
deliveryOfErroneousSDU is NO,
NA, NA during
RAB assignment.
INVALIDTION:
The user plane
entity does not
implement the
error inspection.
During a call, the
delerrsdu=NA,
which is delivered
by the terminal
established by
MGW on the Mc
interface. The
deliveryOfErroneousSDU is NA,
NA, NA during
RAB assignment.
18
Instruction
Parameter
Name
Parameter
Description
DTMFTC
Tandem office
send DTMF
use TC mode,
including two
options:
NO
YES
Instruction

whether the tandem office
uses the TC resources during
DTMF number delivery.
The default value is NO
It contains the following

options.
MGWCON
MGW congestion
reporting
capability
SMGWCON (Standard
MGW congestion event)
CMGWCON (Custom MGW

congestion event).
The default value is

SMGWCON.
Example: Create a topology node with the following requirements.
MGW office ID: 101
Equipment type: R4 gateway
Protocol type: H248
Supported user plane protocol version: V2
CODEC ID: 1.
The specific command is as follows.

ADD TOPO:ID=101,OFCID=101,NAME="MGW101",CODE
CID=1,ETYPE=R4GW,PROTTYPE=H248,IPVER=IPV4,ATT
R="BNCAAL2"&"BNCIPRTP"&"BNCTDM",UPVER="V2",ATTR
2=DTUNL,TRFMOD=MCINTF,UPERRCTRL=YES,DTMFTC=N
O,MGWCON=SMGWCON,AUTOFAX=YES,OOBTC=NO,BCUI
D=0,SENDCAP=NO,G711TRAN=NO,BICCDTMF=TRANSPA
RENT,IPBCP2833=BYMGW,BICCDTMPPER=0,AOIPPRO=P
RIVATE;
END OF STEPS
Creating an Inter-MGW Bearer Mode

Prerequisites
The MGW topological node is created.
Context
The inter-MGW bearer mode is configured when the Nb interfaces

between several MGWs under the same MSCS are connected.
Steps

19

system tree.
SET:NEID=11;
2. Create the inter-MGW bearer mode. The command is ADD
MGWBEARMOD.
Table 10 describes the main parameters in the ADD MGWBE
ARMOD command.
TABLE 10 PARAMETERS IN THE ADD MGWBEARMOD COMMAND
Parameter
Name
Parameter
Description
Instruction
MGWPAIR
MGW node pair
Type the gateway node ID

configured in the topological
node configuration.
Bearer attribute
between MGWs,
the options
include:
AAL1(support
bncAAL1)
ATTR
AAL2(support
bncAAL2)
AAL1S (support
nbcAAL1Struct)
The parameter specifies the

bearer attribute between
MGWs. Select RTP or TDM
according to the type of Nb
interface bearer.
RTP (support
bncIPRTP)
TDM(support
bncTDM)
CTYPE
Type of tone code

between MGWs,
the options
including:
GENERAL
AMRONLY
20
AMRONLY represents the AMR

encoding and decoding mode
is used only. When G.711 and
other encoding and decoding
modes are allowed, select
GENERAL
NAME
Alias
Adjacent office alias of

gateway 1-Adjacent office alias
of gateway 21
AAL1
AAL1 bearer type

rate(%)

rate (%) of the AAL1 bearer
between two gateways
AAL2
AAL2 bearer type

rate(%)

rate (%) of the AAL2 bearer
AAL1S
AAL1STRUCT
bearer type
rate(%)

rate (%) of the AAL1 STRUCT
bearer between two gateways
RTP
IPRTP bearer type

rate(%)

rate (%) of the IPRTP bearer
Parameter
Name
Parameter
Description
Instruction
TDM
TDM bearer type

rate(%)

rate (%) of the TDM bearer
DIRECT
Top-priority direct
link topology, the
options include:
The default is NO
NO
YES
User plane mode
for multi-gateway
IP bearer, the
options include:
UPMODE
TRANSPARENT(transparent
mode)
The default is TRANSPARENT
SUPPORT(support
mode)
Public IP network
domain index
IPNET
G711TRAN
G711 that is
forced to use
the transparent
mode. Options
include:
The parameter is used to set

the public IP network domain
index (ADD IPDOMAIN)
The default is NO
NO
YES
Example: Configure the bearer mode between two MGWs with

the following requirements.
MGW 1 node ID: 101
MGW 2 node ID: 201
Bearer mode: RTP
Type of tone code between MGWS: AMRONLY
Supported version: V2
Alias: MGW101-MGW201
Other parameters: default value.

ADD MGWBEARMOD:MGWPAIR="101"-"201",ATTR="RTP
",NAME="MGW101-MGW201",CTYPE=AMRONLY,AAL1=0,A
AL2=0,AAL1S=0,RTP=100,TDM=0,DIRECT=NO,UPMODE
=TRANSPARENT,G711TRAN=NO;
END OF STEPS
21
SIGTRAN Configuration
Overview
Description
SINGTRAN-related configuration is required not only by the Mc

interface between MSCS and MGW, but also by the Nc interface
between MSCS and other direct-associated office over IP.
When the SCTP bears the M3UA protocol, configuring SCTP, ASP,
AS, M3UA static route and SIO-locating-AS is required.
When the SCTP bears H248 protocol, configuring SCTP is required
only. In general, this mode is not used.
Compared with the MTP data configuration of the traditional No.7
signaling, the SCTP association configuration and the ASP configuration of the M3UA are similar to the link logic and bearer information configurations in the MTP configuration, and the AS configuration of the M3UA is similar to the link set configuration in the
MTP configuration. The configuration of SIO location AS is similar
to the signaling office direction and route configuration in the MTP
configuration. The only difference between them is that one piece
of SIO location AS configuration record is configured the IP route
to a subscriber of an office.
22
Configuration
Flow
Figure 2 shows the flow of SIGTRAN configuration.

FIGURE 2 SIGTRAN CONFIGURATION FLOW
According to the rules regulated in SCTP Planning, perform the

configuration by following the procedure specified below.
Steps
Operations
Instructions
Command
Creating SCTP
Create an association
between two offices
ADD SCTPCONN
Creating ASP
Create the oneto-one relationship

between the ASP and
the association. ASP
is one of instances of
AS.
ADD ASP
Creating AS
Create the tag, user

type, subsystem type
of AS
ADD AS
23
Steps
Operations
Instructions
Command
Creating M3UA
static route
Create the mapping

relationship between
the M3UA static route
and the AS.
ADD M3UART
Creating
the SIOLocating-AS
Locate one service to

a routing table that
is maintained by the
ASP under the AS.
ADD SIOLOCAS
Creating an SCTP
Prerequisites
The physical configuration of the SMP module is completed.
The SCTP flag is configured in the resource management.
Context
The SCTP connection is called as association, which is of one-toone correspondence with ASP. It can be equivalent to the communication link used by the AS. An SMP can support up to 128
associations. When multiple BCTC shelves are configured, associations must share the load in each shelf.
Steps

system tree.
SET:NEID=11;
2. Create the SCTP connection. The command is ADD SCTPCO
NN.
Table 11 describes the chief parameters of the ADD SCTPC
ONN command.
TABLE 11 PARAMETERS IN THE ADD SCTPCONN COMMAND
Parameter
Name
MODULE
24
Parameter
Description
Instruction
Module No.
It is a mandatory
parameter, indicating
the number of the
signaling module
homed by this SCTP
association. Select the
SMP module number.
Each SMP can support
up to 128 associations.
The associations under
the same AS are
required sharing load
on SMP modules as
more as possible.
Parameter
Name
OFCID
Parameter
Description
Instruction
SCTP opposite office

ID
It is a mandatory
parameter, designating
the office No. of
the direct-associated
association. Type
the MGW adjacent
office No. specified
in the adjacent office
configuration.
Bearer protocol
types, including
PROT
M2UA
M2PA
M3UA
SUA
H248
BICC
IUA
DHCTRL
SIP
DIM
V5UA
H245
SCTP application
attributes. Options
include:
ROLE
SVR: SCTP is used

as server
CLT: SCTP is used as
client
LOCADDR
Local IP address
It is a mandatory
parameter. It is used to
identify the upper-layer
protocol type borne by
the SCTP association.
In general, M3UA is
selected. M2UA is
selected when MGW
transfers the signaling
with the M2UA mode.
It is a mandatory
parameter. For Mc
interface, MSCS is
configured as CLT, and
MGW is configured
as SVR. For Nc
interface, this should
be negotiated by both
sides. For example, the
small signaling point
serves as CLT, and
the big signaling point
serves as SVR
It is a mandatory
parameter. It
designates the service
address of local end
of this association,
with a format of
Local IP address
type-VPN of local
IP address-Local IP
address
Local IP address type:
IPv4 and IPv6
VPN of local IP address:
Rang from 0 to 65535
25
Parameter
Name
Parameter
Description
Instruction
Local IP address:
the format is
xxx.yyy.zzz.mmm
LOCPORT
REMADDR
Local port number
Opposite IP address
It is a mandatory
parameter. It is the
local SCTP port number
of the association,
ranging from 1 to
65535.
It is a mandatory
parameter. It
designates the service
address of remote end
of this association,
with a format of
Remote IP address
type-VPN of remote
IP address-Remote
IP address
Remote IP address
type: IPv4 and IPv6;
VPN of remote IP
address: Rang from 0
to 65535
Remote IP address:
the format is
xxx.yyy.zzz.mmm
REMPORT
NAME
ID
Opposite port
number
It is a mandatory
parameter. It is
the opposite SCTP
port number of the
association, ranging
from 1 to 65535.
Alias
It is a mandatory
parameter with a
length ranging from 1
to 50 characters.
SCTP ID
It is an optional
global serial number of
the SCTP association,
Configure it according
to the association
planning.
Example: Create the SCTP connection for the Mc interface with

26
MGW office ID: 101
Bearer protocol: M3UA
Application attribute: CLT
SCTP signaling processing module number: 3
Local port number: 2001
Opposite port number: 2001
Local IP address: 192.168.1.11
Opposite IP address: 192.168.1.31
SCTP association ID: 1

ADD SCTPCONN:MODULE=3,OFCID=101,PROT=M3UA,R
OLE=CLT,LOCADDR="IPv4"-"0"-"192.168.1.11",LOCPORT
=2001,REMADDR="IPv4"-"0"-"192.168.1.31",REMPORT=2
001,NAME="MGW101-1",ID=1,INSTRM=16,OUTSTRM=1
6,MAXRTRY=5,MAXRTO=500,MINRTO=50,INITRTO=10
0,HB=500,FIXNH=NO,SCTPMAXRTRYNUM=10,DELAYAC
K=20,MAXBURST=4,PRIMARYPATH=REMIP1,PMTU=0,BR
EAKTIME=0,PDTHRESH=0,MINCWND=0,PLTIMER=10,M
PPLTHRD=2,DPLEN=MTU,CB=200;
END OF STEPS
Creating an ASP
Prerequisites
The SCTP association information configuration is completed.
The range of the ASP configuration identification is created in

the resource management configuration.
Context
Perform this procedure to define the one-to-one relationship between the ASP and the association. ASP is one of instances of AS.
Steps

system tree.
SET:NEID=11;
2. Create the ASP. The command is ADD ASP.
Table 12 describes the main parameters in the ADD ASP command.
27
TABLE 12 PARAMETERS IN THE ADD ASP COMMAND

Parameter
Name
Parameter
Description
Instruction
It is a mandatory parameter,
ASSOCID
NAME
ID
SCTP ID
Alias
ASP ID
ISLOOP
ASP self-loop ID
Type the association ID

configured in the SCTP
connection configuration.
with a lengthen ranging from
1 to 50 characters. It may
be named with a format of
Adjacent office alias-SCTP
number.
It is recommended to be
consistent with ASSOCID.
It is an optional parameter. It is
used to set whether the ASP is
self-looped.
Select the default value NO
ISLOCK
ASP blocking flag
used set whether the ASP is in
blocking state.
Blocking is used for
management. Select the
default value NO
Example: Create the ASP between MSCS and MGW for Mc interface with the following requirements.
MGW office ID: 101
ASP configuration ID: 1
User alias: MGW101-1.

ADD ASP:ASSOCID=1,NAME="MGW101-1",ID=1,ISLOOP
=NO,ISLOCK=NO;
END OF STEPS
Creating an AS
Prerequisites
28
The ASP configuration is finished.
Context
The AS provides the transmission channels for upper-layer services. For example, H248 and TUP/UP are different services. They
use different AS for transmission. The AS can use one or more
associations for communication.
Steps

system tree.
SET:NEID=11;
2. Create the AS. The command is ADD AS.
Table 13 describes the main parameters in the ADD AS command.
TABLE 13 PARAMETERS IN THE ADD AS COMMAND
Parameter
Name
Parameter
Description
Instruction
PROT
Supported
adaptation layer
protocols
It indicates the protocol

type of a bearer. In general,
M3UA is selected according
to the networking planning.
It is configured as M2UA
when MGW transfers the
signaling with M2UA mode.
ASP
ASP ID
It is associated with the

ASP ID configured in the
ASP configuration.
NAME
Alias
It is a mandatory
parameter. The alias
customized by the user.
AS ID
It is an optional
parameter. It is the unique
identification of the AS. In
general, it is the same as
that of the ASP for easy
memory. The parameter
ranges from 1 to 640
ID
EXISTCTX
Whether the routing

context ID exists
CTXID
Routing context ID
The routing context is
unique in the network.
This parameter must
be consistent with the
AS configuration of the
opposite-end. Its default
value is NO
29
Parameter
Name
Parameter
Description
Instruction
Usage tag. Options

include:
SGP
ASTAG
ASP
SRV (IPSP server)
CLT (IPSP client)
ASUP
User types
supported by AS.
Options include TUP,
ISUP, BICC, H.248,
ALCAP SCCP, PCA,
NNSF and ALL
For Mc interface, MSCS

generally serves as
IPSP_Client, and MGW
serves as IPSP_Server.
When MGW acts as a SGW,
the AS at the MSCS side
serves as ASP, and the AS
at the SGW side serves as
SGP.
For Nc interface, this should
small signaling point serves
as IPSP_Client, and the big
signaling point serves as
IPSP_Server.
It defines the upper-layer
user types supported by
the AS. Currently, there are
eight types of users.
User type is not configured
signaling with the M2UA
mode
The supported service
modes include:
ASMD
Service modes
supported
OVERRIDE(Over-ride
mode)
LOAD (Load share

mode).
In the over-ride mode,

only one ASP is in the
activated statue. In this
case, only one ASP needs
be configured. In the
load sharing mode, N
ASPs should be configured
in the activated working
statue, and K ASPs should
be configured in the
deactivated standby statue.
The value of N+K is not
more than the number of
ASPs actually configured
30
Parameter
Name
Parameter
Description
Instruction
SSN
Types of subsystem.
Options include
NO_SSN (subsystem
SSN excluded
(null)), SCCP, REV2
(standby), ISUP,
OMAP, MAP, HLR,
VLR, MSC, EIR, AUC,
REV11(standby),
INAP, USSD, VLRA,
SGSN_BSCAP,
RANAP, RNSAP,
GMLC_MAP, CAP,
GSMSCF_MAP,
SIWF_MAP, SGSN_
MAP, GGSN_MAP,
IP (intelligent
peripherals),
SMC, SSP_SCP,
BSC_BSSAP_LE,
MSC_BSSAP_LE,
SMLC_BSSAP_LE,
BSS_O_M_A ,
BSSAP_A and
RVE255.
Types of subsystem
supported by application
server (AS).
The parameter ranges from

0 to 16.
The N value in load
sharing mode
NVAL
The N+K should be equal to

the number of ASP under
AS.
The N value indicates that
AS puts into use if N ASPs
put into use.
Example: Configure the AS between MSCS and MGW for Mc

interface with the following requirements.
MGW office ID: 101
Supported adaptation layer protocol: M3UA
AS configuration ID: 1
Supported user type: H248
ASP ID: 1
Client: MSCS
Alias: H248

ADD AS:PROT=M3UA,ASPID="1",NAME="H248",ID=1,EX
ISTCTX=NO,ASTAG=SGP,ASUP="H248",ASMD=LOAD,NV
AL=1,KVAL=0;
END OF STEPS
31
Creating an M3UA Static Route

Prerequisites
The AS configuration is finished.
The range of the M3UA static route identification is configured

in the resource management configuration.
Context
Perform this procedure to configure the mapping relationship between the M3UA static route and the AS. An M3UA static route
can be used by up to 64 SIO-locating-ASs. Otherwise, configuring
more M3UA static routes is required.
Steps

system tree.
SET:NEID=11;
2. Create the M3UA static route. The command is ADD M3UART.
Table 14 describes the main parameters in the ADD M3UART
command.
TABLE 14 PARAMETERS IN THE ADD M3UART COMMAND
Parameter
Name
Parameter
Description
Instruction
ID
ID of M3UA
static route
indicating the serial number of the
M3UA static route ID, ranging from
1 to 640. In general, it is the same
as the AS ID.
ASID
AS ID
corresponding to the AS ID
specified in the ADD AS command.
Nature: routes are directly sorted
according by the ASP marshalling
sequence in the routing table.
MODE
Alignment
mode of
routes.
Options
include
BYTURNS
LOCAL
NATURE
Local: It is unnecessary to realize

the algorithm in the background.
The background just needs to make
the alignment according to the
Nature option.
BYTURNS: in the routing table,
the routes at the odd-bit position
are sorted by the serial number of
the activated ASP, and the routes
at the even-bit position are sorted
inversely by the serial number of
the activated ASP
The default is BYTURNS.
NAME
32
Alias
It is a mandatory parameter defined

by a user, with a length ranging
Example: Create an M3UA static route for Mc interface with

MGW office ID: 101
M3UA static route ID: 1
AS ID: 1
User alias: MGW101.

ADD M3UART:ID=1,ASID=1,MODE=BYTURNS,NAME="MG
W101";
END OF STEPS
Creating the SIO-Locating-AS

Prerequisites
Context
The M3UA static route configuration is completed.
The range of the SIO-locating-AS configuration ID is configured

in the resource management configuration.
The configuration of SIO-locating-AS is used to locate one service

to a routing table that is maintained by the ASP under the AS. On
MSCS, H248 protocol is generally configured between MSCS and
MGW, and ISUP, TUP, and SCCP protocols are configured between
MSCS and other adjacent offices that are switched by MGW.
A routing key describes a set of No.7 signaling parameters and
parameter values. The corresponded AS is selected according to
the message attributes, thus to select a route for the message.
The message attributes include DPC+NET+OPC+SIO. The DPC
represents the destination SPC, the NET represents the network
type, OPC represents the original SPC, and the SIO represents
the service information octet.
Steps

system tree.
SET:NEID=11;
2. Create the SIO-locating-AS. The command is ADD SIOLOCAS.
Table 15 describes the main parameters in the ADD SIOLO
CAS command.
33
TABLE 15 PARAMETERS IN THE ADD SIOLOCAS COMMAND

Parameter
Name
Parameter
Description
Instruction
ID
SIOlocation-AS ID
indicating the serial number of
SIO-locating-AS, ranging from 1 to
4096. In general, it is the same as
the AS ID.
NAME
Alias
It is a mandatory parameter, which

is the alias customized by the user.
Service
indication.
Options include
SIO
NULL
TUP
ISUP
BICC
H.248
ALCAP
SCCP
PCA
NNSF
Select H.248 for Mc interface,

BICC for Nc interface, SCCP for
the RNC or BSC office transferred
through MGW, and TUP or ISUP
for the 2G MSC/PSTN office
transferred through MGW.
Destination
adjacent office
ID
indicating the adjacent office ID
corresponded by the destination
signaling point of the M3UA.
It needs to associate with the
adjacent office ID in the adjacent
office configuration.
OPOFCID
Original
adjacent office
ID
It is the adjacent office ID

corresponding to the M3UA
originating signaling point. If
0 (indicating the local office)
is selected, it indicates that
the message is sent from the
local office, and the routing
context is routed according to
DPC+NET+OPC+SIO. If 65535
(invalid) is selected, it indicates
that the OPC field is invalid, and
the routing context is routed
according to DPC+NET+SIO
PCM
PCM system
number
It is an optional parameter. It
ranges from 0 to 65535, with a
default of 65535 (invalid).
OFCID
34
indicating the subscriber type
belonged by the transmitted
message. Different user types can
be located to the same AS under
the precondition that the MS must
support these user types
Parameter
Name
Parameter
Description
RT1
ID 1 of M3UA
static route
RT2
ID 2 of M3UA
static route
Instruction
It corresponds to the ID
specified in the M3UA static
route configuration. RT1 is a
mandatory parameter. In general,
RT1 is required. When the
optimum route mode is adopted,
RT1 is set as an active route, and
RT2 is set as a standby route.
Example: Create SIO-locating-AS between MSCS and MGW

with the following requirements.
MGW office ID: 101
Destination adjacent office ID: 101
Service indication: H.248
M3UA static route ID: 1.

ADD SIOLOCAS:ID=1,NAME="MGW-H248",SIO=H248,OF
CID=101,OPOFCID=65535,PCM=65535,RT1=1,RT2=0;
END OF STEPS
H.248 Configuration
Overview
Description
H.248 protocol is only used on Mc interface. It provides the following functions.
Under the control of MGC, it can establish, modify and release

the media channel in the MG, and can control the attributes of
bearer and user plane.
It reports the events in the MG to the MGC.
It maintains the office and terminal status between MGC and

MG.
35
Configuration
Flow
Figure 3 shows the configuration flow of H.248 protocol.

FIGURE 3 CONFIGURATION FLOW
Flow Description
36
The H.248 configuration procedures are as follows:

Steps
Operations
Instructions
Command
Creating MGC
static data
Cofigure the data

related to the
MGCF and H.248.
ADD MGCSCFG
Creating an
MGW static data
template
Create the
template used
by the MGW
static data
configuration.
ADD MGSTPL
Creating MGW
static data
Create the static

data for each
IM-MGW under
the MGCF.
ADD MGSCFG
Steps
Operations
Instructions
Command
Creating a TID
analyzer
The TID analysis

configuration is
necessary for
the H.248 server
to perform the
character string
conversion of
the CIC. Nomally
adopt the default
configuration.
ADD TIDANL
Creating a TID
analysis entry
Create a
TID analyzer
entrance.
Nomally adopt
the default
configuration.
ADD TIDENTR
Creating MGC Static Data

Prerequisites
The data configuration of the local office is completed.
Context
Perform this procedure to set the data related to the MSCS and
H.248.
Steps

system tree.
SET:NEID=11;
2. Create the MGC static data. The command is ADD MGCSCFG.
Table 16 describes the main parameters in the ADD MGCSCFG
command.
TABLE 16 PARAMETERS IN THE ADD MGCSCFG COMMAND
Parameter
Name
Parameter
Description
Instruction
MEGACO
MEGACO version
number
Select the supported MEGACO
version number, which must be
consistent with that negotiated
with the MGW. The default value
is 1
ACTTM
Service activation
detection
timer(s)
ranging from 0 to 3600, with a
default of 600
ACTCHK
Service activation
detection switch
being activated by default.
37
Parameter
Name
Parameter
Description
Instruction
WAITTM
MGW answer
waiting timer
(ms)
default of 7800
PTRYNUM
PEND retry
times(t)
default of 5
PTRYTM
PEND retry time

(ms)
default of 4000
CTXLIVETM
Context live
time(s)
default of 1200
Alias
ranging from 0 to 50 characters.
It may be the same as the office
name
NAME
Example: To create the MGC static data of an MSCS office with

all the parameters adopting default value, the specific command is as follows.
ADD MGCSCFG:MEGACO=1,ACTTM=600,ACTCHK=ON,W
AITTM=7800,PTRYNUM=5,PTRYTM=4000,CTXLIVETM=1
200,MGACTTM=600;
END OF STEPS
Creating an MGW Static Data Template

Prerequisites
Context
Perform this procedure to set the template used by the MGW static
data configuration.
Steps

system tree.
SET:NEID=11;
2. Create an MGW static data template. The command is ADD
MGSTPL.
Table 17 describes the main parameters in the ADD MGSTPL
command.
38
TABLE 17 PARAMETERS IN THE ADD MGSTPL COMMAND

Parameter Name
Parameter
Description
Instruction
NAME
Alias
This is a mandatory parameter

with a length ranging from
1 to 50 characters. It can
be consistent with the office
name.
ID
Static data template

number
The number of a template,

MEGACO
MEGACO version
number
This parameter must be

consistent with that negotiated
with the MGW.
ACTCHK
Gateway activation
detection switch
It is configured as ON by
default
PRTTM
Transient protection
timer (s)
It ranges from 1 to 180. Type

the default value 10
PRT
Transient protection
switch
It is configured as ON by
default.
PENDTM
Interval of PEND
messages (ms)
It ranges from 0 to 3600, with

a default of 200
LNGTM
Maximum existence
time (ms)
It ranges from 0 to 65535,

with a default of 15000
RTRNTM
Retransmission
timer (ms)

with a default of 3800
MTRNNUM
Maximum
transmission times
It ranges from 0 to 15, with a

default of 1
TRNMD
Retransmission
mode
CTYPE
H.248 protocol
coding mode
FIXED:
Duration
changeable
UNFIXED:
changeable
un-
Duration
It must be consistent with that

negotiated with the MGW data
configuration
Example: Create an MGW static data template with the following requirements.
Template ID: 1
User name: MGW101

ADD MGSTPL:NAME="MGW101",ID=1,MEGACO=1,ACTC
HK=ON,PRTTM=10,PRT=ON,PENDTM=200,LNGTM=1500
39
0,RTRNTM=3800,MTRNNUM=1,TRNMD=UNFIXED,CTYPE
=TEXT;
END OF STEPS
Creating MGW Static Data

Prerequisites
The MGW topological node is configured.
The MGW static data template is configured.
The MSCS voice batch processing is finished.
Context
Perform this procedure to configure the static data for each MGW
under the MSCS.
Steps

system tree.
SET:NEID=11;
2. Create MGW static data. The command is ADD MGSCFG.
Table 18 describes the main parameters in the ADD MGSCFG
command.
TABLE 18 PARAMETERS IN THE ADD MGSCFG COMMAND
Parameter Name
40
Parameter
Description
Instruction
ID
Gateway
number

configuring the node number of
this gateway, ranging from 1 to
2048. It is associated with the node
ID specified by the ADD TOPO
command.
TPLID
Static data
template
number
associated with the template
number configured on the MGW
static data template configuration.
TONEID
Service tone
template ID
It is an optional parameter ranging

from 0 to 65535. It uses the
template ID specified in the BADD
STONE command.
LANGID
Language
description
template ID
It is an optional parameter, ranging

from 0 to 65535. It uses the
template ID specified in the BADD
STONE command.
Parameter Name
Parameter
Description
Instruction
NAME
Alias
ranging from 0 to 50 characters. It
may be the same as the office name
BKMGC
Backup MGC
information
It is an optional parameter, with a

default of NULL
PKGLOST
Threshold of
package loss
rate (0.01%)

from 0 to 10000, with a default of
10
JIT
Threshold
of network
jittering (ms)

50
DELAY
Threshold of
network delay
(ms)

200
MGW tandem
It is an optional parameter for

setting whether this MGW is used
for the tandem function. Type the
default value NO
MGW
Example: Create static data for an MGW with the following

requirements.
MGW office ID: 101
Static configuration template ID: 1
Alias: MGW101.

ADD MGSCFG:ID=101,NAME="MGW101",TPLID=1,TONE
ID=1,LANGID=1,PKGLOST=10,JIT=50,DELAY=200,MGW
=NO;
END OF STEPS
Creating a TID Analyzer

Prerequisites
Context
The TID analysis configuration is necessary for the H.248 server

to perform the character string conversion of the CIC. The H.248
server converts the CIC on the server to the corresponding character string according to the mode configured by the TID analysis.
Then it sends this character string to the gateway's H.248 for analyzing and operating the corresponded CIC. Since the form of the
terminals used by the Mc interface is relatively fixed currently, you
may adopt the default configuration.
41
Steps

system tree.
SET:NEID=11;
2. Create the TID analyzer. The command is ADD TIDANL.
Table 19 describes the main parameters in the ADD TIDANL
command.
TABLE 19 PARAMETERS IN THE ADD TIDANL COMMAND
Parameter Name
Parameter
Description
Instruction
NAME
User alias
characters. It may be the
same as the office name.
PREV
TID analyzer index
It is the global number of
the current analyzer for TID
analyzer entry to use, ranging
from 1 to 255.
TIDPFX
TID prefix
It is an optional parameter with

a default of TDM
with a default of TRUNK (trunk
type).
TAG
Analysis result flag.

Options include
USER, TRUNK, RTP,
ATM, ROOT and
PCM+IDX.
PCMSPR
PCM flag
with a default of .
IDXSPR
IDX flag
with a default of /.
PCM start location
default of 1, indicating that the
PCM number starts from the
first digit of the PCM flag.
PCMPOS2
PCM end location
default of 0. Since there is a
PCM flag, the End Location is
meaningless.
IDXPOS1
IDX start location
PCMPOS1
42
Example: TDM_5/1 is a
trunk terminal form. TDM is
the TID prefix, _ is the PCM
separation mark, 5 is the PCM
number, "/ is the IDX (time
slot index) is the separation
mark, and 1 is the time slot
number
Parameter Name
Parameter
Description
Instruction
default of 1, indicating that the
time slot number starts from
the first digit of the IDX flag.
IDXPOS2
IDX end location
default of 0. Since there is an
IDX flag, the End Location is
meaningless.
Example: Create a TID analyzer with the following requirements.
MGW office ID: 101
TID index: 1
Alias: MGW101
The command is:

ADD
TIDANL:NAME="MGW101",PREV=1,TIDPFX="TDM
",TAG=TRUNK,PCMSPR="_",IDXSPR="/",PCMPOS1=1,PC
MPOS2=0,IDXPOS1=1,IDXPOS2=0;
END OF STEPS
Creating a TID Analyzer Entry

Prerequisites
Context
Steps
The MGW topological node is configured.
The TID analyzer configuration is completed.
Perform this procedure to configure a TID analyzer entry.

system tree.
SET:NEID=11;
2. Create a TID analyzer entry. The command is ADD TIDENTR.
Table 20 describes the main parameters in the ADD TIDENTR
command.
43
TABLE 20 PARAMETERS IN THE ADD TIDENTR COMMAND

Parameter
Name
Parameter
Description
Instruction
ND
Gateway
It is a mandatory parameter. It is the

node ID allocated by the topological
node configuration.
TIDENTID
TID analyzer
index
associating the TID analyzer ID
specified in the TID analyzer
configuration.
TIDTPLID
TID template
number
By default, the system already

creates a TID template whose ID is
1. You may query it with the SHOW
TIDTPL command.
User Alias
It is a mandatory parameter with

a length ranging from 0 to 50
characters. It may be the same as
the office name.
NAME
Example: Create a TID analyzer entry with the following requirements.
MGW office ID: 101
TID analyzer index: 1
TID template ID: 1
Alias: MGW101.

ADD TIDENTR:ND=101,TIDENTID=1,TIDTPLID=1,NAME
="MGW101";
END OF STEPS
HLR Data Configuration

Overview
Typical
Networking
44
When ZXWN CS is interconnected with the HLR, the HLR is usually

connected to the MSCS in the TDM mode in the existing network.
Figure 4 shows the typical networking between ZXWN CS and the
HLR.
FIGURE 4 TYPICAL NETWORKING BETWEEN
Data Collection
THE
ZXWN CS
AND THE
HLR
Before data configuration, it is supposed to complete collecting

and negotiating the related data from the MSCS to the HLR office.
Table 21 lists the data to be collected. The parameter values are
just examples. Input these parameters according to the actual
condition during the practical data construction procedure.
TABLE 21 MSCS-HLR INTERCONNECTION DATA COLLECTION
Data Configuration Flow
Parameter Items
Parameter Values
ZXWN MSCS signaling point code (24-bit)
3.11.1
HLR signaling point code (24-bit)
3.1.1
HLR number
8613907551
Signaling point code type
24-bit signaling point code
SP type
SEP
Association type
Direct connect
Signaling link code
Signaling E1 number
E1 9
Start timeslot number of E1
16TS
Quantity of timeslots
Table 22 describes the data configuration flow of the HLR adjacent

office.
45
TABLE 22 DATA
FOR
INTERCONNECTION
WITH THE
HLR
Steps
Operations
Related Command
Creating a HLR Adjacent

Office
ADD ADJOFC
Creating a Signaling Link Set
ADD N7LKS
Creating an SPB-accessed
Signaling Link
ADD N7LNKE1
Creating a Signaling Route
ADD N7ROUTE
Creating a Signaling Office
ADD N7OFC
Creating IMSI Analysis
ADD IMSIANA
Creating GT Translation
Selector
ADD GTT
Creating GT Translator Data
ADD GT
Generally, the following five types of GT numbers are configured

in ZXWN.
Local offices MSC/VLR number GT
HLR number GT
Mobile subscriber number (MSISDN) GT
MSC/VLR number GT with interoffice handover
IMSI-constructed GT
Here, whether to configure the last number in the E214 format

depends on the specific result of "IMSI Number Analysis". For
example, if MCC+MNC (such as 46000) in "IMSI Number Analysis"
is configured as CC+NDC (such as 86139) in E214 format, the GT
number in this E214 format should be configured here. If the IMSI
number analysis is configured as the E164 number in the HLT GT
form in "IMSI Number Analysis", the corresponding GT number in
the E164 format should be configured here.
For the above four number forms, the rule to select GT is to start
from the beginning so as to select this number's minimum prefix
that can identify different office directions for analysis, and to select as few identifiable prefixes as possible so as to simplify the GT
configuration.
Different carriers have different requirements on whether the GT
or the DPC addressing mode is used for transferring the MAP and
CAP messages between two signaling points. Some carriers require transferring the MAP and CAP messages between the intra-province signaling points in the DPC addressing mode, and
the MAP and CAP messages between the extra-province signaling points in the GT addressing mode, and some carriers require
transfer all the MAP and CAP messages in the GT addressing mode.
In case of the DPC addressing mode, the STP has light load, but
is configured with more data. In case of the GT addressing mode,
the STP has heavy load, but are configure with less data.
46
Creating a HLR Adjacent Office

Prerequisites
The E1 line between the MSCS and HLR is well corrected.

Meanwhile, the signaling interworking data is planned and
negotiated.
The configuration of local office data is complete.
Context
Creating the HLR adjacent office means configuring the basic information for the HLR adjacent office.
Steps

system tree.
SET:NEID=11;
2. Create a HLR adjacent office. The command is ADD ADJOFC.
Table 23 describes the parameters in the ADD ADJOFC command.
Parameter
Name
Parameter
Description
Instructions
SPCFMT
Signaling point code

format
Select TRIPLE_DEC
(888/333 format
Dec Numeric
Characters).
Signaling point code

type
Specify it according to
the SPC type of the
adjacent office. In this
case, select 24 (24
bit signaling point
code).
DPC
Destination signaling
point code
It is a mandatory
parameter. Set
the 24-bit signaling
point code to this
HLR adjacent office
according to its
signaling point code
type.
OFCTYPE
Adjacent Office Types
Select
HLR/HLRe&AUC.
SPCTYPE
47
Parameter
Name
Parameter
Description
Instructions
Broadband attribute,
including:
BANDFLAG
YES (Support
broadband
attribute)
Select No (Not support

broadband attribute).
No (Not support
broadband
attribute)
For example, create a HLR adjacent office with the following

requirements.
Office ID: 1
Signaling point code: 3.1.1
Signaling point code type: 24bit
Adjacent office type: HLR/HLRe and AUC
Association type: Direct connection mode

ADD ADJOFC:ID=1,NAME="HLR",NET=1,OFCTYPE="HLR/
HLRe"&"AUC",SPCFMT=TRIPLE_DEC,SPCTYPE=24,DPC="3
.1.1",RC="25",ASSOTYPE=AM_SURE,SPTYPE=SEP,SSF=N
ATIONAL,SUBPROTTYPE=DEFAULT,TEST=YES,BANDFLAG
=NO,PRTCTYPE=CHINA,CLST=65535,INFO="CIC_PCM",RE
LATEDOFC1=0;
END OF STEPS
Signaling Data Configuration

Creating a Signaling Link Set
Prerequisites
Context
The adjacent office configuration is completed.
The data configuration of local office is completed.
The range of signaling link set is configured in the resource

management.
Perform this procedure to configure a narrowband signaling link set

to the adjacent office, including 64k signaling link set, 2M signaling
link set, N64k signaling link set.
When configuring the signaling link set connected by TDM, you
may select N64, NN64, and N2M.
48
Steps
64k indicates that the narrow-band signaling link in this signaling link set only seizures one time slot on one E1 line, with
64 Kbps bandwidth.
N64K indicates that the narrow-band signaling link in this

signaling link set seizures N consecutive time slots on one E1
line (8n25).
2M indicates that the narrow-band signaling link in this signaling link set seizures all 31 time slots on one E1 line (time slot
0 is unavailable), with 1.984Mbps bandwidth.

system tree.
SET:NEID=11;
2. Create a signaling link set. The command is ADD N7LKS.
Table 24 describes the main parameters in the ADD N7LKS
command.
TABLE 24 PARAMETERS IN THE ADD N7LKS COMMAND
Parameter
Name
Parameter Description
Instruction
Direct-associated office
of the signaling link set
It is a mandatory
parameter. Type the
adjacent office ID of
this signaling link set,
which is specified in
the adjacent office
configuration.
Signaling link set ID
It is a mandatory
parameter. It
designates the signaling
link set No. for
distinguishing signaling
link sets, ranging from
1 to 1024.
Alias
It is a mandatory
parameter describing
the name of this
signaling link set for
easy identification.
TYPE
Signaling link set type
This parameter indicates

the types of the
signaling links in this
signaling link set. Select
N64 for a 64K signaling
link, NN64 for an
n64K signaling link,
and N2M for a 2M
signaling link.
LECM
Link error revision,
This parameter
OFCID
ID
NAME
49
Parameter
Name
including:
BASIC (basic error
revision, transit delay
15 ms): all the signaling
links use this method
for relatively short
transit delay, except for
satellite links.
PCR (Preventive Cyclic
Retransmission: transit
delay15 ms): Satellite
links use this method
for it has a relatively
long transit delay.
Instruction
designates the error
correction method of
the signaling links in
this set. In general,
select BASIC. In
general,BASICis
selected when the
line transit delay is less
than 15ms, and PCR is
selected when the line
transit delay is greater
than 15ms.For a 2M
signaling link, BASIC
must be selected. This
parameter shall be
consistent with that
of the opposite end
through negotiation.
Example: Create a signaling link set connected by HLR office

104 with the following requirements.
HLR office ID: 1
Signaling link set No.: 1
Group type: 64K narrowband link set
Link error revision: Basic error revision
Alias: HLR-1.

ADD N7LKS:OFCID=1,TYPE=N64,ID=1,LECM=BASIC,NA
ME="HLR-1";
END OF STEPS
Creating an SPB-Accessed Signaling Link

Prerequisites
Context
50
The signaling link group configuration is completed.
Signaling link is the physical channel carrying signaling messages.

The narrow-band signaling link used on the MSCS is an SPB-accessed signaling link.
Note:
In order to evenly distribute the traffic load to an office on each
link that is selected in the dynamic routing table corresponded
by the SLC, usually the number of links in a link set to a directassociated office is configured as 2n, namely, 2, 4, 8, or 16 links
are configured. Make sure that load onto each link is not too heavy
to cause it breakdown.
Steps

system tree.
SET:NEID=11;
2. Create an SPB-accessed signaling link. The command is ADD
N7LNKE1
Table 25 describes the main parameters in the ADD N7LNKE1
command.
TABLE 25 PARAMETERS IN THE ADD N7LNKE1 COMMAND
Parameter
Name
LKSID
SLC
MODULE
NAME
Parameter
Description
Instruction
Signaling link
set ID
designating the signaling link
set No. of this signaling link.
It is associated with the ID of
the signaling link set that is
configured.
Signaling Link
Code (SLC)
This parameter designates the

SLC of this signaling link, ranging
from 0 to 15. It needs to
be consistent with the SLC of
the same signaling link of the
opposite-end office.
Signaling
management
module No.
Select a signaling module.
Several signaling links of the
same office should be configured
to different physical boards.
In addition, the signaling links
managed by each SMP module
should share load.
Alias
designating the name of
the signaling link for easy
identification, with a length
ranging from 1 to 50 characters.
51
Parameter
Name
Parameter
Description
SPBUNT
SPB unit
number
CPU
CPU ID of SPB
E1
E1 number of
the SPB board
Instruction
The CPU ID ranges from 1 to 4.
Several signaling links of the same
office should be configured to
different SPB boards. In addition,
the signaling links processed by
the CPUs on SPB board should
share load.
This parameter designates the

number of the E1 where the
signaling link is located, ranging
from 9 to 25. By default, it is
numbered from 9
64k signaling link: the time slot
number of the signaling link is 16
TS
Start timeslot
number of E1
N64k signaling link: its start

time slot ranges from 1 to 31
2M signaling link: Its start time
slot is 1
Configure the number of the time
slots occupied by the signaling
link.
TSNUM
Quantity of
timeslots
64K signaling link: Its time slot

amount is 1.
N64K signaling link: Its time
slot amount is N.
2M signaling link: Its time slot
amount is 31.
Miscellaneous
information,
including:
E1: This
link uses
the E1-type
interface.
INFO
N64KT1:
This link uses
the T1-type
interface, with
64K normal
coding mode.
I64KT1: This
link uses
the T1-type
interface, with
64K reversal
phase coding
mode.
56KT1: This
link uses
the T1-type
interface, with
54K coding
mode.
52
Configure the interface type and

coding mode of this link. In
general, it is an E1 link.
Example: Create an SPB-accessed signaling link with the following requirements.
Signaling link No.: 0
SMP module No.: 3
Signaling link alias: HLR-1-1
SPB board unit No.: 721
Start time slot number of E1: 9
Time slot amount: 1
Other parameters: default.

ADD N7LNKE1:LKSID=1,SLC=0,MODULE=3,NAME="HLR1-1",ID=1,SPBUNT=721,CPU=1,E1=9,TS=16,TSNUM=1,L
OOP=NO,INFO=E1,FCPLTHR=255;
END OF STEPS
Creating a Signaling Route

Prerequisites
The signaling link group configuration is completed.
The range of signaling route ID is configured in the resource

management.
Context
The signaling routing configuration is used for specifying the signaling link set to be selected and the method when the signaling
selects a route. The signaling route to a direct-associated office
only contains the signaling link sets to this office. The signaling
route to a quasi-associated office contains one or two signaling
link sets to the intermediate office.
Steps

system tree.
SET:NEID=11;
2. Create a signaling route. The command is ADD N7ROUTE.
Table 26 describes the main parameters in the ADD N7ROUTE
command.
53
TABLE 26 PARAMETERS IN THE ADD N7ROUTE COMMAND

Parameter
Name
Parameter
Description
Instruction
NAME
Alias
designating a signaling route
for easy identification.
Signaling link set 1
The signaling route contains

the first signaling link set.
Type the serial number of the
signaling link set 1.
Signaling link set 2
It is the second signaling

link set contained by the
signaling route. At least
either LKSID1 or LKSID2
is not equal to zero and
contains signaling links. If
only one signaling link set
exists, type 0
Signaling route
number
This parameter designates

the serial number of the
signaling route, ranging from
1 to 2000. When there
is only one signaling link
set, this parameter may be
configured to be consistent
with the signaling link set
number.
LPM
Arrangement mode
of signaling link
sets. Refer to Table
27 for its options.

the rules that should be
obeyed when the signaling
links of two signaling link
sets are sorted. When two
link sets have the same
signaling links, and the total
number is not more than
16, RAND (random order) is
recommended
LPMIN
Arrangement mode
in a signaling link
set. Refer to Table
27 for its options.

the rules that should be
obeyed when the signaling
links in a signaling link set
are sorted. RAND (random
order) is recommended
MANUAL
Sort manually,
including NO(Need
Not Manual)
and YES(Need
Manual)
The parameter indicates

whether to manually sort the
signaling routes of the two
link groups
Link list
The maximum number

of instance is 16. The
format is <INDEX>-<LINK>,
representing the alignment
order and link number
respectively.
LKSID1
LKSID2
ID
LINKS
54
TABLE 27 ARRANGEMENT MODE OF SIGNALING SETS

Mode
Meanings
Instruction
RAND
Random
arrangement
mode
Random arrangement mode
SLS0
Select On
SLS_BIT0
Selecting links between two

link sets according to Bit 0 of
SLS
SLS1
Select On
SLS_BIT1

SLS
SLS2
Select On
SLS_BIT2

SLS
SLS3
Select On
SLS_BIT3

SLS
SLS01
Select On
SLS_BIT0-1

link sets according to Bits 0
and 1 of SLS
SLS12
Select On
SLS_BIT1-2

and 2 of SLS
SLS23
Select On
SLS_BIT2-3

and 3 of SLS
Example: Create a signaling route with the following requirements.
Alias: HLR
Signaling route No.: 1
Other parameters: default.

ADD
N7ROUTE:NAME="HLR",LKSID1=1,LKSID2=0,ID
=1,LPM=RAND,LPMIN=RAND,MANUAL=NO;
END OF STEPS
Creating a Signaling Office

Prerequisites
The signaling route configuration is completed.
55
Context
Perform this procedure for configuring the correspondence between the destination signaling office and the signaling route.
Steps

system tree.
SET:NEID=11;
2. Create a signaling office. The command is ADD N7OFC.
Table 28 describes the main parameters in the ADD N7OFC
command.
TABLE 28 PARAMETERS IN THE ADD N7OFC COMMAND
Parameter
Name
Instruction
ID
Signaling route office
It is a mandatory
parameter. Type the
adjacent office No. of
the destination office
RT1
This parameter
designates the serial
number of the direct
route to the destination
adjacent office.
It is a mandatory
parameter. Configure
the serial number of the
direct route to this office,
RT2
Alternate route 1,
indicating the serial
number of the first
alternate route to the
destination adjacent
office.
RT3
Alternate route 2,
number of the second
office. This parameter
is configured when only
the first alternate route
is already configured.
RT4
Alternate route 3,
number of the third
office. This parameter is
configured when only the
second alternate route is
already configured.
NAME
56
Alias
This parameter ranges

from 0 to 2000.
Select up to three
available alternate
routes according to the
actual conditions. When
there is no alternate
route, configure it as 0.
It is a mandatory
parameter. This
parameter designates
the name of the
signaling office for
easy identification
Example: Create a signaling office to a HLR adjacent office

whose office ID is 1 and the direct-associated route number is
1. The specific command is as follows.
ADD
N7OFC:ID=1,RT1=1,RT2=0,RT3=0,RT4=0,NAME
="HLR";
END OF STEPS
Creating IMSI Analysis

Prerequisites
Context
The No. of the exchange to be configured is given.
The UE brings with an IMSI number in the E212 format when originating a location update request. The MSC/VLR builds the GT
according to this IMSI for addressing the HLR. The IMSI number
analysis is used to convert the IMSI number to a number that can
address to the HLR.
There are two types of analysis result indications: ISDN format
and HLR format.
1. ISDN
The corresponding number prefix in the IMSI is converted
into specified analysis result, and the rest digits are added
behind the analysis result. For example, if the analyzed
number is 46000, the network-accepted IMSI number is
460001234567890, the corresponding Country Code (CC) is
86 and the Network Destination Code (NDC) is 139. In the
analysis of ISDN mode, 46000 can be analyzed into 86139.
This number is analyzed into 861391234567890. Based on
this, the typical application of this mode is to convert the
MCC+MNC in the IMSI into the CC+NDC, and keep the rest
part, thus forming the E214 number format.
2. HLR
The corresponding number prefix in the IMSI is converted into
specified analysis result, and the rest digits are deleted. For
example, if the analyzed number is 46000, the conversion result is HLRs GT number 8613907551, and the network-accepted IMSI number is 460001234567890. In the HLR mode,
this IMSI number is analyzed into 8613907551234, namely the
HLRs GT number. Based on this, the typical application of this
mode is to convert the IMSI headed by specific MCC+MNC into
the GT number of a HLR.
Steps

system tree.
SET:NEID=11;
2. Create an IMSI analysis. The command is ADD IMSIANA.
57
Table 29 describes the parameters in the ADD IMSIANA command.

TABLE 29 PARAMETERS IN THE ADD IMSIANA COMMAND
Parameters
Explanation
Instruction
IMSI prefix
specifying the IMSI prefix to
be analyzed. It is an integer,
consisting of 1~20 digits.
HDSTCODE
Home destination
code
which is an integer consisting
of 1~16 digits. It is the
number converted from an
IMSI number. It may be
CC+NDC or HLRs GT
number. In this case, enter
the GT number of the HLR.
HDSTCODET
Destination code
type, including
HLR and ISDN.
In this case, enter HLR.
NAME
Alias
consisting of 1~50 characters.
It is used to specifically
describe an IMSI analysis
record to make it easily
recognized.
SM
Short message ID
Enter the default 0.
OPID
Operator ID
INDADC
Independent ADC
IMSI
For example, create the IMSI number analysis with the following requirements.
Analyzed number: 460001234
Home destination code: 8613907551
Analysis result: HLR
Alias: HLR

ADD IMSIANA:IMSI="460001234",HDSTCODE="8613907
551",HDSTCODET=HLR,NAME="HLR",SM=0,OPID=0,IND
ADC=NO;
END OF STEPS
58
SCCP Data Configuration

Creating GT Translation Selector
Prerequisites
Context
The GT translation selector and the GT translation data configuration both belong to the SCCP data configuration. The SCCP
data configuration serves the SCCP routing. In the R4 system,
the MAP signaling between such entities as MSCS/VLR and HLR in
the network is transferred through the SCCP. All the entities may
be directly connected, or forwarded by a signaling transfer point.
When the SCCP receives messages from the MAP application layer,
it will send, receive and forward these messages according to the
route labels in the messages. The SCCP is of two message routing
modes, GT routing and DPC+SSN routing.
These two routing modes are different when the STP exists between the originating signaling point and the destination signaling
point. The DPC+SSN routing mode requires that all the signaling points in the network (including originating signaling points,
destination signaling points, and STP) can identify this destination
signaling point code (DPC). The signaling is directly transferred
through the MTP layer after reaching the intermediate node, without passing the SCCP layer. In this case, more DPC data are configured for the originating signaling point and STPs. The GT routing method may be used in case that the originating SP and some
STPs do not know the final DPC of this signaling. In this addressing method, when the signaling reaches the STP, the GT should
be translated into the destination signaling point, or the DPC of
STP of the next hop GT translation at first through the SCCP, and
then messages are transferred to the MTP for transmission. In the
GT routing mode, the originating signaling point only sends the
signaling to the STP of the next hop GT translation according to
the GT number prefix. The STP translates it and decides whether
to send it the next STP or the destination signaling point. In this
case, less DPC data are configured for the originating signaling
point and STPs.
Before configuring the GT translation data, configure the GT translation selector to determine the basic attribute of the GT translation. In general, two GT translation selectors are required, respectively corresponding to E164 and E214 coding plans. Pay attention
to the configurations of numbering plan, address attributes, country code and bit length during configuration.
Steps

system tree.
SET:NEID=11;
2. Create a GT translation selector. The command is ADD GTT.
59
Table 30 describes the parameters in the ADD GTT command.

TABLE 30 PARAMETERS IN THE ADD GTT COMMAND
Parameter
Name
GTT
TT
Parameter
Description
Instruction
GT type
raging from 1 to 4. When it
is 1, the GT contains address
attributes. When it is 2, the
GT contains translation type.
When it is 3, the GT contains
translation type, numbering
plan, and coding design.
When it is 4, the GT contains
translation type, numbering
plan, coding design, and
address attributes. GT4 is
selected by default
Translation type
ranging from 0 to 255. It is
the translation type of the
GT number, with the default
value as 0
Numbering plan,
including
NULL (idle)
E.164
(ISDN/phone
numbering
plan)
E.214
(ISDN/mobile
numbering
plan)
RES
(reserved)
X.121 (Data
numbering
plan)
F.69 (Telex
numbering
plan)
E.210(Maritime mobile
numbering
plan)
E.212 (Land
mobile
numbering
plan)
Reserved(2),
Reserved(8) Reserved (255):
Reserved
PLAN
60
Select E.164 for the E164
format, and select E.214
for the E214 format. For
example, if the mobile
number is analyzed as HLR,
select E.164 for GT analysis
of this number. If the mobile
number is analyzed as ISDN,
select E.214 for GT analysis
of this number
Parameter
Name
Parameter
Description
Instruction
Address attribute,
including
NULL(idle)
SUB (address
attributes is
subscriber
number)
INT (address
attributes is
international
number)
NATRSV
(address
attributes
is national
reserved
number)
NATURE
NATSIGN
(address
attributes is
national valid
number)
CAMEL
(address
attributes is
intelligent
network
service
number)
VACANT0,VACANT7 VACANT255: vacancy
Select INT
ID
GT translation
selector
the global number of the GT
translation selector
CC
Country code
consisting of 0~4 digits. It is
86 in China
National minimum
digit length
They are optional parameters,

which are integers, ranging
from 1 to 20. They
respectively correspond to the
national minimum GT number
length, and national maximum
GT number length configured
in the GT translation data
configuration. In general, the
national minimum digit length
is set to 5, while the national
maximum digit length is set
to 15
NMIN
61
Parameter
Name
Parameter
Description
NMAX
National maximum
bit length
IMIN
International
minimum digit
length
IMAX
International
maximum digit
length
CTRL
GT translation
attributes,
including R_L
(intercepting digits
from the number
to be analyzed
from right to left
for alignment,
corresponding
to the maximum
matching policy),
and L_R
((intercepting
digits from the
number to be
analyzed from
left to right
for alignment,
corresponding
to the minimum
matching policy)
Instruction
They are optional parameters,

which are integers, ranging
from 1 to 20. They
respectively correspond
to the international minimum
GT number length, and
international maximum GT
number length configured
in the GT translation data
configuration. In general, the
international minimum digit
length is set to 1, while the
international maximum digit
length is set to 5
with the default choice as
R_L. Maximum Matching
means match the number
from right to left. When
analyzing a GT number,
search the matched options
with the maximum length.
GT numbers are analyzed in
the descending order of their
lengths, facilitating reducing
the workload of GT data
configuration
NAME
User alias
It is used to identify a GT
translation selector to make it
easily recognized
For example, create a GT translation selector with the following

requirements.
62
GT type: 4
Translation type: 0
Numbering plan: ISDN/phone numbering plan
Address attribute: international number
GT translation selector ID: 1
Alias: E164

ADD GTT:GTT=4,TT=0,PLAN=E.164,NATURE=INT,GTTOP
T=0,ID=1,CC="86",NMIN=5,NMAX=9,IMIN=2,IMAX=5,C
TRL=R_L,NAME="E164";
For example, create a GT translation selector with the following
requirements.
GT type: 4
Translation type: 0
Numbering plan: ISDN/mobile numbering plan
Address attribute: international number
Alias: E214

ADD GTT:GTT=4,TT=0,PLAN=E.214,NATURE=INT,GTTOP
T=0,ID=2,CC="86",NMIN=5,NMAX=9,IMIN=2,IMAX=5,C
TRL=R_L,NAME="E214";
END OF STEPS
Creating GT Translation Data

Prerequisites
Context
The GT translation selector is configured.
The GT data are used for location update, call, and inter-office
handover. Configuring GT translation data should follow this principle: Understanding the service signaling flow and making clear
the signaling route. To response every message sent to the opposite end, the GT translation data both of the source address and
destination address of signaling must be configured at every end
point or transfer point.
When configuring the location update data, the local offices GT
number is translated to office 0, namely, the local office, and the
HLRs GT number is translated to the HLR or the STP. Therefore,
at least two types of the GT translation data are configured on the
MSCS. In general, the following two kinds of GT translation data
are required.
E164 number: it requires configuring the local offices MSC/VLR
GT, MSISDN number, and MSC/VLR GT with location-area adjacent
relation.
E214 number: it requires configuring E214 format number corresponded by IMSI number (E212 format).
Steps

63

system tree.
SET:NEID=11;
2. Create the GT translation data. The command is ADD GT.
Table 31 describes the parameters in the ADD GT command.
TABLE 31 PARAMETERS IN THE ADD GT COMMAND
Parameter
Name
GT
OPGT
GTSL
GTDI
64
Parameter
Description
Instruction
Called GT number
used to query the destination
GT number of message
routing
Calling GT number
consisting of 0~20 digits. It
is the number of the virtual
MSC where the subscriber is
located during GT translation.
During GT routing, query
where there are matched data
according to the VMSC where
the subscriber is located and
the target GT number. If there
are matched data, perform
GT translation based on the
matched data. If there is
no matched data, perform
translation again based on
that the calling GT number is
0
GT translation
selector
ranging from 0 to 1023. Select
the GT translation selector
respectively according to
configured E164 and E214
numbers
Number change
ID

with the default value as
0. It is the ID of flexible
policy template change. The
target GT number can be
flexibly changed based on
it. When the GT translation
result contains a new GT,
this parameter does not take
effect
Parameter
Name
Parameter
Description
Instruction
OFCIDS
Office ID and poll

list
The number of instance is
1~4 when office ID grouping
is supported. The number
of instance is 1~16 when
office ID grouping is not
supported. The format
is <OFCID>-<SELNUM>,
representing the office ID to
be polled and the number of
poll respectively.
GRP
Whether to
support grouping
of office ID
with a default of NO
The office ID and

poll number of the
multiple signaling
points for the
second group
is supported. The user
does not need to type when
the office ID grouping is
poll respectively.
The office ID and

poll number of the
multiple signaling
points for the third
group
poll respectively.
OFCGRP34
The office ID and

poll number of the
multiple signaling
points for the
fourth group
poll respectively.
SSN
Subsystem No.
Refer to Table 32
for the options
involved
the GT routing mode, select
the default value for SSN. In
the DPC+SSN routing mode,
select the corresponding SSN
New GT number
ranging from 0 to 20 of
characters. It represents the
new GT translation type.
OFCGRP2
OFCGRP3
NGT
65
Parameter
Name
Parameter
Description
NTRNTYPE
New GT
translation type
It represents the new GT
translation type.
TRNRLT
Whether the
translation result
contains DPC
and SSN. The
options includes
NULL (neither
DPC nor SSN is in
the result), DPC
(containing DPC
in the result), and
SSN (containing
SSN in the result)
the GT routing mode, select
the default value for TRNRLT.
In the DPC+SSN routing
mode, select the DPC and
SSN for TRNRLT
RTTYPE
Routing mode,
including GT
(routing based
on GT) and DPC
(routing based on
DPC+SSN)
general, select GT for direct
connection, and DPC+SSN
for non-direct connection
Instruction
Attribute of the
new GT , including
the following
options:
NGT (No new
GT in the GT
translation
result): The GT
number in the GT
translation result
is still the called
GT number.
NGTTAG
NAI: The GT
number in the
GT translation
result is the new
GT number in the
NGT parameter,
only containing
Nature Of Address
Indicator (NAI).
NTT: The GT
number in the
GT translation
result is the new
GT number in the
NGT parameter,
only containing
translation type.
NTTES: The GT
number in the GT
translation result
is the new GT
number in the
NGT parameter,
only containing
66
It is the attribute of the
new GT contained in the GT
translation result. NGT(No
new GT in the GT translation
result) is selected by default
Parameter
Name
Parameter
Description
translation type,
numbering plan,
and coding design.
Instruction
NTTNAI: The GT
number in the GT
translation result
is the new GT
number in the
NGT parameter,
containing
translation type,
numbering plan,
coding design,
and NAI
SCCP coding type,
including:
SCCP
INT (international
coding) and
USA(USA coding)
It indicates the standard type
referred to by the SCCP coding
in the GT translation result.
The default value is INT
VGT
GT varying
with different
office IDs,
including NO (not
supported), and
YES (supported)
with NO as the default value
TT
TT conversion,
including NO (not
supported), and
YES (supported)
with NO as the default value
NAME
Alias
The alias of the GT translation

data for easy memory.
TABLE 32 SSN
SSN
Meaning
NO_SSN
Not containing SSN
SCCP
SCCP
ISUP
ISDN user part
OMAP
Operation and maintenance application part
MAP
Mobile user part
HLR
Home location register
VLR
Visitor location register
MSC
Mobile switching center
EIR
Equipment identity register
67
SSN
Meaning
AUC
Authentication center
ISDN/ASE
ISDN_ASE(11)
INAP/OTA
INAP/OTA subsystem
USSD
USSD
VLRA
VLRA
SGSN_BSCAP
SGSN BSCAP
RANAP
RANAP
RNSAP
RNSAP
GMLC_MAP
GMLC MAP
CAP
CAP
GSMSCF_MAP
GSMSCF MAP
SIWF_MAP
SIWF MAP
SGSN_MAP
SGSN MAP
GGSN_MAP
GGSN MAP
IP
IP
SMC
SMC subsystem
SSP_SCP
SSPSCP subsystem
BSC_BSSAP_LE/MPC
BSC_BSSAP_LE/MPC
MSC_BSSAP_LE
MSC_BSSAP_LE
SMLC_BSSAP_LE
SMLC_BSSAP_LE
BSS_O_M_A
BSS_O_M_A
BSSAP_A
BSSAP_A
NPDB
NPDB
ATER
ATER
UDS_DMCC
UDS_DMCC
Other Reserved
Reserved
For example, create the GT translation data with the following

requirements.
68
GT number: 8613907551
Office poll: 1-1
Subsystems SSN number: SCCP

ADD GT:GT="8613907551",GTSL=1,GTDI=0,OFCIDS="1""1",GRP=NO,SSN=NO_SSN,NTRNTYPE=0,TRNRLT="DPC
"&"SSN",RTTYPE=GT,NGTTAG=NGT,SCCP=INT,VGT=NO,T
T=NO,NPFLAG=NO,NPLAN=NULL,SRVTYPE=NULL;
END OF STEPS
STP Data Configuration

Overview
Typical
Networking
ZXWN CS may interconnect with the STP in one of the following

two ways.
ZXWM MSCS is directly connected to the STP.
The built-in SG of ZXWN MGW forwards the signaling.
In the current networking environment, the STP is usually directly

connected to the ZXWN MSCS in the TDM mode. This section introduces this configuration method.
Networking
Diagram
Figure 5 shows the typical networking between ZXWN CS and the

STP.
FIGURE 5 TYPICAL NETWORKING BETWEEN
Data Collection
THE
ZXWN CS
AND THE
STP
Before data configuration, it is supposed to complete collecting and

negotiating the related data from the MSCS to the STP adjacent
office. Table 33 lists the data to be collected. Where, the parameter values are just examples. Enter these parameters according
69
to the actual condition during the practical data construction procedure.

TABLE 33 MSCS-STP DATA COLLECTION
Parameter Items
Parameter Values
ZXWN MSCS signaling point code

(24-bit)
3.11.1
STP signaling point code (24-bit)
3.2.1
Signaling point code type
SP type
STP
Association type
Direct connect
Signaling link code
Signaling E1 number
E1 10
16TS
Table 34 describes the configuration flow.

TABLE 34 MSCS-STP DATA CONFIGURATION FLOW
70
Steps
Operations
Related Command
Creating an STP adjacent

office
ADD ADJOFC
Creating a signaling link set

to the STP
ADD N7LKS
Creating a signaling link to

the STP
ADD N7LNKE1
Creating a signaling route to

the STP
ADD N7ROUTE
Creating a signaling office to

the STP
ADD N7OFC
Creating a GT translation
data
ADD GT
In the above configuration flow table, the SSN subsystem of

the SCCP is generated automatically according to the adjacent
office type specified in the adjacent office configuration. You
may query the generated subsystem with the SHOW N7SSN
command.
In general, all the GT numbers except the local office are transmitted to the corresponding STP for forwarding, when the GT
number is configured in the current network. In operation
method, analyze the subdivided GT number in the local office
to the local office direction, and then analyze the smallest GT
prefix (such as 86139) in the network to the STP, thus greatly

simplify the working load of data configuration.
Creating an STP Adjacent Office

Prerequisites
The E1 line between the MSCS and the STP is well connected.
Meanwhile, the signaling interworking data is planned and negotiated.
Context
Creating an STP adjacent office means configuring the basic information for the opposite STP office.
Steps

system tree.
SET:NEID=11;
2. Create an STP adjacent office. The command is ADD ADJOFC.
Parameter Name
Parameter
Description
Instruction
ID
Office ID
indicating the ID of the adjacent
office, and ranging from 1 to
3000. It is usually configured
as the exchange ID of the
adjacent office during the
all-network planning.
NAME
Alias
Enter a character string to
describe an STP adjacent office.
Network type
indicating the network type of
the SPC used for connecting
the local office to the adjacent
office when the local office
is configured with several
Signaling Points (SP). The
default is the network type of
this SP when there is only one
SP in the local office.
NET
71
Parameter Name
Parameter
Description
Instruction
OFCTYPE
Adjacent Office
Types
Configure the adjacent office

type. Select MSCSERVER for
the STP adjacent office.
SPCFMT
Signaling point
code format
Select TRIPLE_DEC
(888/333 format Dec Numeric
Characters).
SPCTYPE
Signaling point
code type
Specify it according to the SPC

type of the adjacent office. In
this case, select 24 (24 bit
signaling point code).
DPC
Destination
signaling point
code
Set the 24-bit signaling point
code to this STP adjacent office
according to its signaling point
code type.
RC
Area code
Indicates the local toll zone

code of the adjacent office
ASSOTYPE
Association type
Select AM_SURE (direct

connection mode) in this case.
SPTYPE
Signaling point
type
If this signaling point forwards

messages through this adjacent
office, it is configured as STP
or STEP. Otherwise, it is
configured as SEP. In this case,
select STP.
SSF
Subservice type
In this case, select National

(National signaling point code).
Broadband
attribute,
including:
YES (Support
broadband
attribute)
No (Not
support
broadband
attribute)
BANDFLAG
PRTCTYPE
Protocol type
Since the MSCS is connected

to the STP through the TDM,
select NO (Not support
broadband attribute).
Select CHINA.
For example, create an STP adjacent office with the following

requirements.
72
Office ID: 2
Signaling point code: 3.2.1
Signaling point code type: 24-bit
Adjacent office type: MSCSERVER
Association type: Direct connection mode

ADD ADJOFC:ID=2,NAME="STP",NET=1,OFCTYPE="MSC
SERVER",SPCFMT=TRIPLE_DEC,SPCTYPE=24,DPC="3.2.1
",RC="25",ASSOTYPE=AM_SURE,SPTYPE=STP,SSF=NATI
ONAL,SUBPROTTYPE=DEFAULT,TEST=YES,BANDFLAG=N
O,PRTCTYPE=CHINA,CLST=65535,INFO="CIC_PCM",RELA
TEDOFC1=0;
END OF STEPS
Signaling Data Configuration

Creating a Signaling Link Set to the STP
Prerequisites
The adjacent office is configured.
The range of signaling link set is configured in the resource

management.
Context
Perform this procedure to add an MTP link set to the STP adjacent
office.
Steps

system tree.
SET:NEID=11;
2. Create a signaling link set to the STP adjacent office. The command is ADD N7LKS.
Table 36 describes the parameters in the ADD N7LKS command.
TABLE 36 PARAMETERS IN THE ADD N7LKS COMMAND
Parameter
Name
Parameter
Description
Instruction
OFCID
Office ID
designating the adjacent office
directly connected to this signaling
link set. It is the STP adjacent
office ID specified in the ADD
ADJOFC command. Note that
every adjacent office can only has
one link set.
TYPE
Linkset type,
including:
Select N64, NN64, or N2M for
73
Parameter
Name
Parameter
Description
Instruction
the signaling link set connected
through the TDM.
N64K (64K
narrowband
signaling
link set)
64k indicates that the

narrow-band signaling link
in this signaling link set only
seizures one time slot on one E1
line, with 64 Kbps bandwidth.
NN64K
(n64K
narrowband
signaling
link set)
N64K indicates that the

narrow-band signaling link in
this signaling link set seizures N
consecutive time slots on one E1
line (8n25).
N2M (2M
narrowband
signaling
link set)
2M indicates that the narrowband

signaling links in this link set
seizures all 31 time slots of one
E1 line, with the bandwidth as
1.984Mbps.
ATM
(Broadband
signaling
link set)
M2PA (M2PA
signaling
link set)
Select ATM for the signaling link

set connected through ATM.
Select M2PA for the signaling link
set connected through IP.
Generally, select N64 for the
signaling link set to the STP.
This parameter should be
negotiated by the two ends of the
connection for consistency.
ID
Linkset ID
designating the unique No. of this
signaling link set. It is numbered
from 1. It is suggested to be the
same as the adjacent office ID.
Link error
revision,
including:
BASIC (basic error revision,

transit delay 15 ms): all the
signaling links except satellite
links uses this method.
BASIC
(basic error
revision)
PCR (preventive cyclic retransmission)
LECM
NAME
Alias
PCR (Preventive Cyclic

Retransmission: transit delay15
ms): Satellite links use this
method for it has a relatively long
transit delay.
In this case, select BASIC (basic
error revision).
naming this signaling link set for
easy identification.
For example, create a signaling link set to the STP office with
74
STP office ID: 2
Signaling link set number: 2
Signaling link set type: 64K narrowband link set
Link error revision: Basic error revision
Alias: TOSTP

ADD N7LKS:OFCID=2,TYPE=N64,ID=2,LECM=BASIC,NA
ME="TOSTP";
END OF STEPS
Creating a Signaling Link to the STP

Prerequisites
The signaling link set configuration is complete.
The SPB board configuration is complete.
Context
Signaling links are the physical channels bearing signaling messages. Configuring an MTP link to the STP means creating an signaling link borne on the E1.
Steps

system tree.
SET:NEID=11;
2. Create an E1 signaling link. The command is ADD N7LNKE1.
Table 37 describes the parameters in the ADD N7LNKE1 command.
TABLE 37 PARAMETERS IN THE ADD N7LNKE1 COMMAND
Parameter
Name
LKSID
SLC
MODULE
Parameter
Description
Instruction
Linkset ID
indicating the signaling link
set belonged by this signaling
link, and using the signaling
link set ID configured in the
ADD N7LKS command.
Signaling link
code
It is the link selecting code,

ranging from 0 to 15. One
signaling link set has up to
16 narrowband signaling
links. This parameter must
be consistent with that of
the opposite end office. The
signaling link codes in the
same signaling link set cannot
be repeated.
SMP module No.
designating the module
number of the SMP managing
this signaling link.
75
Parameter
Name
Parameter
Description
Instruction
NAME
Alias
which is the alias customized
by the user.
ID
Signaling Link
It is the global number of a

signaling link. In general, it
ranges from 1 to 1000 for
a narrowband signaling link,
and from 1001 to 1920 for a
broadband signaling link. It
is suggested that this number
should be consistent with the
adjacent office ID.
SPBUNT
SPB unit No.
designating the unit number
of the SPB board specified in
the physical configuration.
SPB CPU
It is the CPU number of the

SPB board that has four
CPUs. There is no fixed
correspondence between the
E1 No. of this signaling link
and the SPB subunit No..
Since an SPB board provides
16 E1 lines, and supports up
to 64 64Kbps narrowband
links, the narrowband links
should be distributed evenly
in the subunit.
SPB E1
An SPB board has 16 E1 lines

numbered from 9 to 24. E1
numbers are corresponded to
the E1 lines on the rear board
of the SPB board. Select the
E1 number corresponding
to the E1 line actually
connected.
SPB E1 time slot

start number
It is the start time slot

number of the SPB E1 subunit
used by this E1 signaling
link for outgoing the office.
consistent with the opposite
end through negotiation.
It ranges from 1 to 31 for
64Kbps signaling links.
SPB E1 timeslot
amount
It is the quantity of
consecutive timeslots on
the E1 subunit of the SPB
board. These timeslots are
used by this E1 signaling
link for outgoing the office.
consistent with that of
the opposite end through
negotiation. It is fixed as 1
for 64Kpbs signaling link
CPU
E1
TS
TSNUM
76
Parameter
Name
Parameter
Description
Instruction
LOOP
Self loop
In general, select NO.
Link info,
including:
INFO
E1: This
link uses
the E1-type
interface.
N64KT1
(support
T1-64 normal
code): This
link uses
the T1-type
interface, with
64K normal
coding mode.
I64KT1
(support
T1-64
inverted
code): This
link uses
the T1-type
interface, with
64K inverse
coding mode.
56KT1
(support
T1-64K): This
link uses
the T1-type
interface, with
56K coding
mode.
Select E1.
For example, create a signaling link with the following requirements.
Signaling link set: 2
Signaling link code: 0
SMP module manages this signaling link: 3
Unit No. of the SPB board: 721
SPB E1: 10
Initial time slot of E1: 16
Number of time slot: 1

ADD N7LNKE1:LKSID=2,SLC=0,MODULE=3,NAME="TOS
TP",ID=2,SPBUNT=721,CPU=1,E1=10,TS=16,TSNUM=1,L
OOP=NO,INFO=E1,FCPLTHR=255;
END OF STEPS
77
Creating a Signaling Route to the STP

Prerequisites
The signaling link set configuration is complete.
The range of signaling route ID is configured in the resource

management.
Context
The signaling routing configuration is used for specifying the signaling link set to be selected and the method when the signaling
selects a route.
Steps

system tree.
SET:NEID=11;
2. Create the signaling route to the STP. The command is ADD
N7ROUTE.
Table 38 describes the parameters in the ADD N7ROUTE command.
TABLE 38 PARAMETERS IN THE ADD N7ROUTE COMMAND
Parameter
Name
Parameter
Description
Instruction
Alias
for naming a signaling office
for easy recognition, consisting
of 1~50 characters.
Linkset 1 ID
designating the first signaling
link set used by this route. It
uses the signaling link set ID
specified in the ADD N7LKS
command, ranging from 0 to
1024.
LKSID2
Linkset 2 ID
designating the second
signaling link set used by this
route. In general, a route
to a directly connected office
only has one signaling link
set. Then, enter 0 for this
parameter. If there are two
STPs between the local office
and a quasi-associated office,
respectively select the ID of the
signaling link sets to these two
STPs, ranging from 0 to 1024.
ID
Signaling route
ID
designating the global number
of the signaling route, ranging
from 1 to 2000. This parameter
NAME
LKSID1
78
Parameter
Name
Parameter
Description
Instruction
is used for selecting a signaling
route in the signaling office
configuration.
LPM
Line mode
among linkset
In general, select RAND, which

means that link sets are sorted
at random. The links in the
static route table are sorted by
turns. For example, there are
two signaling links, link a and
link b. The sorting method is:
a, b, b, a, a, b, b, a, a, b, b, a,
a, b, b, a.
LPMIN
Line mode in a
link set
In general, the RAND option is

selected, namely being sorted
at random.
MANUAL
Sort manually
Select NO (Need not manual).
For example, create a signaling route with the following requirements.
STP office ID: 2
Alias: TOSTP
Signaling route No.: 2

ADD N7ROUTE:NAME="TOSTP",LKSID1=2,LKSID2=0,ID
=2,LPM=RAND,LPMIN=RAND,MANUAL=NO;
END OF STEPS
Creating a Signaling Office to the STP

Prerequisites
The signaling route is configured.
Context
Creating a signaling office to the STP means configuring the mapping relationship between the destination signaling office and the
signaling route.
Steps

system tree.
SET:NEID=11;
2. Create the signaling office to the STP. The command is ADD
N7OFC.
79
Table 39 describes the parameters in the ADD N7OFC command.

TABLE 39 PARAMETERS IN THE ADD N7OFC COMMAND
Parameter
Name
Parameter
Description
Instruction
Signaling office ID
It is a mandatory
the destination office
where the signaling arrives
finally. It is the HLR
adjacent office ID specified
in the ADD ADJOFC
command, ranging from 1
to 3000.
This parameter
designates the
serial number of
the direct route
to the destination
adjacent office.
It is a mandatory
the route preferentially
selected for sending the
signaling message to
the destination office.
It is the signaling route
ID specified in the ADD
N7ROUTE command,
RT2
Alternate route
1, indicating the
serial number of the
first alternate route
to the destination
adjacent office.
The first alternative route
is selected when the
signaling message fails to
reach the destination office
through the direct route.
It is the signaling route
N7ROUTE command,
RT3
Alternate route
2, indicating the
serial number
of the second
alternate route
to the destination
adjacent office.
corresponding to the link
route already configured.
It is configured only when
the first alternative route
is configured, ranging from
0 to 2000.
RT4
Alternate route 3,
number of the third
alternate route
to the destination
adjacent office.
corresponding to the link
route already configured.
It is configured only when
the second alternative
route is configured,
NAME
Alias
It is a mandatory
parameter for naming
a signaling office.
ID
RT1
For example, create a signaling office with the following requirements.
80
STP office ID: 2
Direct-connected route number: 2
Alias: TOSTP

ADD N7OFC:ID=2,RT1=2,RT2=0,RT3=0,RT4=0,NAME="T
OSTP";
END OF STEPS
Creating a GT Translation Data

Prerequisites
Context
The GT data are used for location update, call, and inter-office
handover. Configuring GT translation data should follow this principle: Understanding the service signaling flow and making clear
the signaling route. To response every message sent to the opposite end, the GT translation data both of the source address and
destination address of signaling must be configured at every end
point or transfer point.
When configuring the location update data, the local offices GT
number is translated to office 0, namely, the local office, and the
HLRs GT number is translated to the HLR or the STP. Therefore,
at least two types of the GT translation data are configured on the
MSCS. In general, the following two kinds of GT translation data
are required.
E164 number: it requires configuring the local offices MSC/VLR
GT, MSISDN number, and MSC/VLR GT with location-area adjacent
relation.
E214 number: it requires configuring E214 format number corresponded by IMSI number (E212 format).
Steps

system tree.
SET:NEID=11;
81

Parameter Name
Instruction
Called GT number
used to query the destination
GT number of message routing
Calling GT number
the number of the virtual MSC
where the subscriber is located
during GT translation. During
GT routing, query where there
are matched data according to
the VMSC where the subscriber
is located and the target GT
number. If there are matched
data, perform GT translation
based on the matched data.
If there is no matched data,
perform translation again based
on that the calling GT number
is 0
GT translation
selector
ranging from 0 to 1023. Select
the GT translation selector
respectively according to
configured E164 and E214
numbers
Number change ID
It ranges from 0 to 256, with

the default value as 0. It is the
ID of flexible policy template
change. The target GT number
can be flexibly changed based
on it. When the GT translation
result contains a new GT, this
parameter does not take effect
OFCIDS
Office ID and poll

list
is supported. The number
representing the office ID to be
polled and the number of poll
respectively.
GRP
Whether to support
grouping of office
ID
It is an optional parameter, with

a default of NO
GT
OPGT
GTSL
GTDI
82
Parameter
Description
Parameter Name
Parameter
Description
Instruction
The office ID and

poll number of the
multiple signaling
points for the
second group
It is an optional parameter. The

number of instance is 1~4 when
office ID grouping is supported.
The user does not need to type
when the office ID grouping
is supported. The format
respectively.
The office ID and

poll number of the
multiple signaling
group

respectively.
The office ID and

poll number of the
multiple signaling
points for the fourth
group

respectively.
Subsystem No.
the GT routing mode, select the
default value for SSN. In the
DPC+SSN routing mode, select
the corresponding SSN
NGT
New GT number
ranging from 0 to 20 of
characters. It represents the
new GT translation type.
NTRNTYPE
New GT translation
type
It represents the new GT
translation type.
TRNRLT
Whether the
translation result
contains DPC
and SSN. The
options includes
NULL (neither
DPC nor SSN is in
the result), DPC
(containing DPC
in the result), and
SSN (containing
SSN in the result)
the GT routing mode, select the
default value for TRNRLT. In the
DPC+SSN routing mode, select
the DPC and SSN for TRNRLT
OFCGRP2
OFCGRP3
OFCGRP34
SSN
83
Parameter Name
Parameter
Description
RTTYPE
Routing mode,
including GT
(routing based
on GT) and DPC
(routing based on
DPC+SSN)
Instruction
general, select GT for direct
connection, and DPC+SSN for
non-direct connection
Attribute of the new

GT , including the
following options:
NGT (No new GT in
the GT translation
result): The GT
number in the GT
translation result is
still the called GT
number.
NAI: The GT
number in the GT
translation result
is the new GT
number in the
NGT parameter,
only containing
Nature Of Address
Indicator (NAI).
NGTTAG
NTT: The GT
number in the GT
translation result
is the new GT
number in the
NGT parameter,
only containing
translation type.
NTTES: The GT
number in the GT
translation result
is the new GT
number in the
NGT parameter,
only containing
translation type,
numbering plan,
and coding design.
NTTNAI: The GT
number in the GT
translation result
is the new GT
number in the
NGT parameter,
containing
translation type,
numbering plan,
coding design, and
NAI
84
is the attribute of the new GT
contained in the GT translation
result. NGT(No new GT in
the GT translation result) is
selected by default
Parameter Name
SCCP
Parameter
Description
Instruction
SCCP coding type,

including:
It indicates the standard type
referred to by the SCCP coding
in the GT translation result. The
default value is INT
INT (international
coding) and
USA(USA coding)
VGT
GT varying with
different office IDs,
including NO (not
supported), and
YES (supported)

NO as the default value
TT
TT conversion,
including NO (not
supported), and
YES (supported)

NO as the default value
NAME
Alias
The alias of the GT translation

data for easy memory.

requirements.
GT number: 861390010
Office poll: 2-1

ADD GT:GT="861390010",GTSL=1,GTDI=0,OFCIDS="2""1",GRP=NO,SSN=SCCP,NTRNTYPE=0,TRNRLT="DPC"&"S
SN",RTTYPE=GT,NGTTAG=NGT,SCCP=INT,VGT=NO,TT=N
O,NPFLAG=NO,NPLAN=NULL,SRVTYPE=NULL;
END OF STEPS
SCP Data Configuration

(Destination Network)
Overview
Typical
Networking
In the existing networks, the SCP is usually connected with the

MSCS (SSP) through the STP in the signaling network. The protocol stack structure at both the MSCS side and the SCP side are
CAP/TCAP/SCCP/MTP. Figure 6 shows the networking diagram.
85
FIGURE 6 NETWORKING BETWEEN
Data Collection
THE
ZXWN CS
AND THE
SCP

and negotiating the related data from the MSCS to the SCP office.
Parameter Items
Parameter Values

(24-bit)
3.11.1
3.2.1
STP Signaling point code type
SP type
STP
Association type
Direct connect
Signaling link code
Signaling E1 number
E1 10
16TS
SCP GT
8613907552
CAMEL version
CAMEL3
Definition of SCP service key
Service key values of various

subscribers
The SCP adjacent office data configuration contains the following

three parts.
1. Creating a direct-connected link to the STP.
86
2. Creating the GT translation data to the SCP.

3. Creating intelligent service data.
Table 42 describes the SCP adjacent office data configuration flow.
TABLE 42 MSCS-SCP DATA CONFIGURATION FLOW
Steps
Operations
Related Command

office
ADD ADJOFC

to STP
ADD N7LKS
Creating an MTP Link to the

STP
ADD N7LNKE1

the STP
ADD N7ROUTE

the STP
ADD N7OFC
Creating a signaling
subsystem
ADD N7SSN
Creating GT translation
selector
ADD GTT
Creating GT translation data

to the SCP
ADD GT
Creating the CAMEL

configuration
ADD CAMEL
10
Creating CAMEL access

subscription information
ADD CAINFO
11
Creating called number

analysis
ADD TPDNAL
12
Creating interconnection
conversion for service keys
ADD SVRTRANSKEY
13
Creating tone keys on the

MGW tone board
ADD TONESVC
Creating a Signaling Subsystem

Prerequisites
Context
Perform this procedure for configuring a No.7 signaling subsystem. According to the subsystem, the lower-layer signaling is distributed to the upper-layer service module for processing.
87
In general, a subsystem is automatically generated during the adjacent office configuration. In this networking system, since SCP
is forwarded through STP, configuring SCP adjacent office data is
not required. Therefore, it is required to create the subsystem
manually on the MML Terminal of NMS system.
Steps

system tree.
SET:NEID=11;
2. Create a signaling subsystem. The command is ADD N7SSN.
Table 43 describes the parameters in the ADD N7SSN command.
TABLE 43 PARAMETERS IN THE ADD N7SSN COMMAND
Parameter
Name
Parameter
Description
Instruction
OFCID
Office ID
Enter the office ID

corresponded by the
signaling point. 0
represents the local
office ID.
SSN
Signaling point
subsystem.
In this case, select

SSP_SCP.
ID
N7SSN ID
This parameter identifies

the serial number of this
subsystem, ranging from
0 to 32784.
TAG
With backup SSN
Select No (Without
backup SSN) by default.
NAME
Alias
The name of this signaling

subsystem to make it
easily recognized.
For example, create a subsystem with the following requirements.
Office ID: 0
Signaling point subsystem: SSP_SCP
Subsystem ID: 1
Alias: SCPSSN

ADD N7SSN:OFCID=0,SSN=SSP_SCP,ID=1,TAG=NO,NAM
E="SCPSSN";
END OF STEPS
88

Prerequisites
Context
Create the SCP GT data. The GT of the SCP is sent to the SCCP
layer of the STP office for it to convert the GT into the DPC + SSN
of the SCP for addressing.
Steps

system tree.
SET:NEID=11;
Parameter
Name
GT
GTSL
GTDI
Parameter
Description
Instructions
Called GT number
It is a mandatory
parameter, consisting
of 1~20 digits. It is used
to query the destination
GT number of message
routing
GT translation
selector
It is a mandatory
parameter, ranging from
0 to 1023. Select the
GT translation selector
respectively according
to configured E164 and
E214 numbers
Number change ID

with the default value as
0. It is the ID of flexible
policy template change.
The target GT number
can be flexibly changed
based on it. When the
GT translation result
contains a new GT, this
parameter does not take
effect
89
Parameter
Name
Parameter
Description
Instructions
OFCIDS
Office ID and poll list
It is a mandatory
parameter. The number
of instance is 0~3000
when office ID grouping is
supported. The number
representing the office
ID to be polled and
the number of poll
respectively.
GRP
Whether to support
grouping of office ID
It is an optional
parameter, with a default
of NO
The office ID and

poll number of the
multiple signaling
points for the second
group
It is an optional
office ID grouping is
supported. The user does
not need to type when
ID to be polled and
the number of poll
respectively.
The office ID and

poll number of the
multiple signaling
group
It is an optional
ID to be polled and
the number of poll
respectively.
The office ID and

poll number of the
multiple signaling
points for the fourth
group
It is an optional
ID to be polled and
the number of poll
respectively.
OFCGRP2
OFCGRP3
OFCGRP34
90
Parameter
Name
Parameter
Description
Instructions
Subsystem No.
It is an optional
parameter. In the GT
routing mode, select
the default value for
SSN. In the DPC+SSN
routing mode, select the
corresponding SSN
NGT
New GT number
It is an optional
0 to 20 of characters. It
represents the new GT
translation type.
NTRNTYPE
New GT translation
type
It is an optional
0 to 255. It represents
the new GT translation
type.
TRNRLT
Whether the
translation result
contains DPC and
SSN. The options
includes NULL
(neither DPC nor
SSN is in the result),
DPC (containing DPC
in the result), and
SSN (containing SSN
in the result)
It is an optional
parameter. In the GT
routing mode, select the
default value for TRNRLT.
In the DPC+SSN routing
mode, select the DPC
and SSN for TRNRLT
RTTYPE
Routing mode,
including GT (routing
based on GT) and
DPC (routing based
on DPC+SSN)
It is an optional
parameter. In general,
select GT for direct
connection, and
DPC+SSN for non-direct
connection
SSN
Attribute of the new

GT , including the
following options:
NGT (No new GT in
the GT translation
result): The GT
number in the GT
still the called GT
number.
NGTTAG
NAI: The GT number

in the GT translation
result is the new
GT number in the
NGT parameter, only
containing Nature
Of Address Indicator
(NAI).
It is an optional
attribute of the new
GT contained in the
GT translation result.
NGT(No new GT in the
GT translation result) is
selected by default
NTT: The GT number

result is the new
GT number in the
91
Parameter
Name
Parameter
Description
Instructions
NGT parameter,
only containing
translation type.
NTTES: The GT
number in the GT
translation result
is the new GT
number in the
NGT parameter,
only containing
translation type,
numbering plan, and
coding design.
NTTNAI: The GT
number in the GT
translation result
is the new GT
number in the
NGT parameter,
containing
translation type,
numbering plan,
coding design, and
NAI
SCCP coding type,
including:
SCCP
INT (international
coding) and
USA(USA coding)
It is an optional
parameter. It indicates
the standard type
referred to by the
SCCP coding in the
GT translation result. The
VGT
GT varying with
including NO (not
supported), and YES
(supported)
It is an optional
parameter, with NO
as the default value
TT
TT conversion,
including NO (not
supported), and YES
(supported)
It is an optional
parameter, with NO
NAME
Alias
The alias of the GT

translation data for easy
memory.

requirements.
GT number: 8613907552
Office poll: 2-1 (here, the office is STP)

92
END OF STEPS
Creating the CAMEL Configuration

Prerequisites
The support capability of local office is configured as "NULL" in

the local office mobile data configuration.
The No.7 signaling subsystem of the local office is generated

properly. (Query it with the SHOW N7SSN command.)
Context
Creating the CAMEL configuration is to make the intelligent subscriber subscribed OCSI in the HLR properly trigger the IN service,
and make and receive a call.
Steps

system tree.
SET:NEID=11;
2. Create the CAMEL configuration.
CAMEL.
The command is ADD
Table 45 describes the parameters in the ADD CAMEL command.

TABLE 45 PARAMETERS IN THE ADD CAMEL COMMAND
Parameter
Name
Parameter
Description
Instruction
CAMEL phase,
including:
None: Not
supported
CAMEL1: Support
CAMEL1
CAMEL2: Support
CAMEL2
CAMEL3: Support
CAMEL3
CAMEL4: Support
CAMEL4
VER
It is an optional
parameter. The CAMEL
version supported by
the local office must
be consistent with that
supported by the SCP.
93
Parameter
Name
Parameter
Description
CNMACT
Approach of high
version CAMEL
subscription info,
including:
REJ (Reject)
Ignore (Ignore)
Instruction
Type the default value

REJ (REJ).
Approach of CAMEL1
subscription info,
including:
C1ACT
INAPTYPE
REJ (Reject)
Ignore (Ignore)
ACPT (Accept)
INAP protocol type
Select ACPT, by default.
Select CHINA, by
default.
For example, create the CAMEL configuration with the following

requirements.
CAMEL phase: CAMEL3

Approach of high version CAMEL subscription information:
REJ (reject)
Approach of CAMEL1 subscription information: ACPT (accept)

ADD CAMEL:VER=CAMEL3,CNMACT=REJ,C1ACT=ACPT,IN
APTYPE=CHINA;
END OF STEPS
Recharge and Query Configuration

Creating CAMEL Access Subscription Information
Prerequisites
Context
94
The No. of the exchange to be configured is known.
The support capability of local office is configured as "NULL" in

the local office mobile data configuration.
The No.7 signaling subsystem of the local office is generated

properly. (Query it with the SHOW N7SSN command.)
The access code of the call service can trigger the intelligent network service.
Steps

system tree.
SET:NEID=11;
2. Create the CAMEL subscription information. The command is
ADD CAINFO.
Table 46 describes the main parameters in the command.
TABLE 46 PARAMETERS IN THE ADD CAINFO COMMAND
Parameter
Name
Parameter
Description
Instruction
CAMELIDX
CAMEL information
index
which is an integer,
It is used to set the
intra-system number of
this configuration for using
in the configuration of the
number analysis result. It
is not to be repeated with
any other.
CIC
Carrier identity
code
consisting of 1~6 numeric
characters.
SCP address
(Country code +
National Number)
It is a mandatory string
parameter with a length
ranging from 1 to 16 digits.
It is the GT number of
the SCP. It must be in the
international format.
External service
key
which is an integer, ranging
from 1 to 4294967295. It is
uniquely identify the service
after the negotiation with
the SCP.
NAME
Alias
consisting of 1~50
characters. It is used
to describe the CAMEL
access subscription type to
make it easily recognized.
ID
CAMEL
configuration ID
from 1 to 65535.
SCP
SKEY
95
Parameter
Name
Parameter
Description
Instruction
Numbering plan,
including:
E164
(ISDN/phone
numbering
plan E164)
X121 (Data
numbering
plan X121)
F69 (Telegraph
numbering
plan F69)
NUMPLAN
Select E164.
CAMEL phase,
including:
VER
None: Not
supported
CAMEL1:
Support
CAMEL1
CAMEL2:
Support
CAMEL2
CAMEL3:
Support
CAMEL3
CAMEL4:
Support
CAMEL4
Default call
handling,
including:
DCH
HOLD (Hold
call)
RELEASE
(Release call)
This parameter is set after
the negotiation with the
SCP. Currently, the version
CAMEL3 is frequently used.
Configure it according to the
actual service requirements.
Select HOLD by default.
For example, create the CAMEL access subscription information

CAMEL index: 1
SCP address: 8613907552
External service key: 1
Alias: PPS
Number plan: ISDN/phone numbering plan E164
96
ADD CAINFO:CAMELIDX=1,CIC="111",SCP="8613907552
",SKEY=1,NAME="PPS",NUMPLAN=E164,VER=CAMEL3,DC
H=HOLD;
END OF STEPS
Creating Called Number Analysis

Prerequisites
The CAMEL access subscription information is configured.
The number analyzer entry is configured.
Context
The subscriber must dial special service access number to trigger

the IN services, and then the system performs the number analysis. If the number analysis result is the IN service, the IN service
flow is triggered. Therefore, in the ZXWN MSCS system, the number analysis result corresponded by the called number must be
configured as the IN service type. In this way, the IN service can
be triggered.
Steps

system tree.
SET:NEID=11;
2. Create the called number analysis.
TPDNAL.
The command is ADD
Table 47 describes the parameters in the ADD TPDNAL command.

TABLE 47 PARAMETERS IN THE ADD TPDNAL COMMAND
Parameter
Name
Parameter
Description
Instruction
ENTR
Analyzer entry
from 1 to 1000. Select the
corresponding analyzer entry
of the analyzed number
prefix. This analyzer entry is
configured by the ADD ENTR
command.
DIGIT
Analyzed
Number
It is a character string,
consisting of 0~9, *, #, D, or
E.
97
Parameter
Name
Parameter
Description
Instruction
Alias
describe the called number
analysis to make it easily
recognized.
Call service types
with a default of NULL. It is
used to specify the service type
triggered by this number, and
determine the direction of this
call. Select an IN service type.
Select SSP in this case.
Number analysis
result 1
It is an optional integer-type
parameter, ranging from 0 to
2147483647. Keep the default,
because this configuration does
not take effect here.
Number analysis
result 2
255. Select the CANELIDX
(CAMEL information index)
already configured in the
CAMEL access subscription
information.
Number analysis
result 3
parameter, ranging from 0
to 2147483647. Select the
CANELIDX (CAMEL information
index) already configured in
the CAMEL access subscription
information.
CHAINAL
Chain analysis
index
It is used to specify the

analysis index number of the
routing chain. This parameter
must be defined by the ADD
CHAINAL command at first.
Then it can be indexed here.
This parameter takes effect
only when the call service type
is outgoing service (including
various outgoing services).
RNLEN
MNP routing
number length
Enter an integer ranging from
0 to 40.
NAME
CAT
RST1
RST2
RST3
98
Parameter
Name
MINLEN
MAXLEN
Parameter
Description
Instruction
Minimum
number length
which is an integer ranging
from 0 to 255, with a default
of 3. It is used to specify the
minimum digit length of the
called number. If the called
number is shorter than this
length, the call failure occurs.
In general, it is configured as
6.
Maximum
number length
which is an integer ranging
from 0 to 255, with a default
of 20. It is used to specify the
maximum digit length of the
dialed number. If the called
number exceeds this length,
the call failure occurs. In
general, it is configured as 11.
For example, create the called number analysis for the SSP
recharge query service with the following requirements.
SN of number analyzer entry: 1
Service type: SSP
Number analysis result 1: 1

ADD TPDNAL:ENTR=1,DIGIT="13800138000",NAME="R
echarge Service",SPECRST=0,SPECIDX=0,CAT=SSP,RST1
=1,RST2=0,RST3=0,CHAINAL=0,RNLEN=0,MINLEN=3,M
AXLEN=20,OVLYPRI=NO,REL=NO,NET=1,NAT=DEF,OPD
DICONT=NO,TPDDICONT=NO,OPDDI=0,TPDDI=0,OPDL
YDDI=0,TPDLYDDI=0,DDIOVERB=0,IWVIDEO=LSUP,TI
MELMT=0,AUXDAS=0,A6=0,PFXLEN=0,INSRV=INM,FAXI
DX=0,AVIDX=0,DVIDX=0,ADATAIDX=0,DDATAIDX=0,D
DCPLAY=NONE,VAD=INVALID,CALLSERVPRILVL=INVALI
D,RERTS=0,INCHAIN=NO,BICT=NO,ICT=0,ICTT=10,GN
M=NORMAL,STBILL=INVALID,HOPDAS=0,MCA=NO,IVVR
=NO,WANTL=0,IMSCENTR=NO;
END OF STEPS
Configuration Related to Intelligent

Tone Play
The data related to the basic tone and the intelligent tone are created during the tone-related configuration is created in batches.
99
The intelligent tone play requires attention to the configuration of

service keys. Service key divides into the internal service keys and
the external service keys. External key code is delivered by the
SCP, while internal service key code is the corresponded internal
service code.
Therefore, the intelligent tone play configuration includes the interconnection conversion configuration of external service keys
and the service key configuration of the MGW tone board.
The internal service keys of the ZXWN MSCS are described in Table
48.
TABLE 48 INTERNAL SERVICE KEYS
Service
Service Key Value
Basic services
PPS services
VPMN services
17951 IP services
Mobile phone rechargeable card services
Calling/called party paid services
Mobile Eight Hundred services
Zone and time-dependent services
41
Creating Interconnection Conversion for Service

Keys
Prerequisites
The conversion of service key to service tone ID is created in

batches on the MSCS.
Context
Creating the CAMEL tone play data is to configure the mapping

relationship between the internal and external service keys, thus
to convert the external service key into the internal one. After the
intelligent service is triggered, the MSCS can implement the service processing flow properly, and the MGW can play the intelligent
service tone correctly.
Steps

system tree.
SET:NEID=11;
2. Create the interconnection conversion for service keys. The
command is ADD SVRTRANSKEY.
100
Table 49 describes the parameters in the ADD SVRTRANSKEY

command.
TABLE 49 PARAMETERS IN THE ADD SVRTRANSKEY COMMAND
Parameter
Name
Parameter
Description
Instruction
ID
Configuration ID
It is an optional
integer-type parameter,
ranging from 0 to
4294967295. This ID
is used inside the system.
It is not to be repeated with
any other.
SVCKEY
Service key coding.

Refer to Table 50 for
the options involved.
It is a mandatory
parameter. Select it
according to the actually
configured service type.
Alias
It is a mandatory
of 1~50 characters. It
is used to describe an
service-key interconnection
conversion to make it easily
recognized.
SCP type
It is an optional
integer-type parameter,
ranging from 0 to 255. It
identifies the SCP type.
Currently, it is configured
as 0.
NAME
SCPTYPE
TABLE 50 SERVICE KEY CODES

Options
Meanings
TRDT
Traditional services
PPS
PPS services
VPMN
VPMN services
17951IP
17951IP services
MBCARD
Handset voucher card services
PAY
Calling/called payment services
MB800
Mobile 800 services
SMSPPS
SMSPPS
IVC
New voucher service tone
IGWVPMN
IGWVPMN services
IGWPPS
IGWPPS services
101
Options
Meanings
UPTANN1.2
Universal one number
ONS
One Number
ES
Universal in students service
IPVN2
IPVN2
CLTM
Cell and time division service
IPZHTC
IP direct-bus service
LTIC
All-purpose IC service
MS
Universal in multi-cities
121V1
Uniform showing incoming call
ACC_200
ACC_200
200V1
Changing number acknowledgment service
RC
Different phone handling tone
ACC_300
ACC_300
VOT
VOT
VPN
VPN
UPT
UPT
FPH
FPH
For example, create a service-key interconnection conversion

External service key code: 11
Service key code: PPS service
Alias: PPS service
ID: 1
SCP type: 0

ADD SVRTRANSKEY:EXSVCKEY=11,SVCKEY=PPS,NAME
="PPS Service",ID=1,SCPTYPE=0;
END OF STEPS
Creating Tone Keys on the MGW Tone Board

Prerequisites
102
The corresponded MRB unit is created on the MGW.
Context
Perform this procedure for configuring the service keys on the

MGW tone board.
Steps

system tree.
SET:NEID=11;
2. Create a service key on the tone board. The command is ADD
TONESVC.
Table 51 describes the parameters in the ADD TONESVC command.
TABLE 51 PARAMETERS IN THE ADD TONESVC COMMAND
Parameter Name
Parameter
Description
Instruction
UNIT
Tone unit number
It is a mandatory integer-type
2000. Select the MRB unit
number of the intelligent tone.
SUNIT
Tone subunit
number
It is a mandatory integer-type
255. Enter the TONE subunit
No. of the MRB.
SKEY1
Service key 1
SKEY2
Service key 2
SKEY3
Service key 3
SKEY4
Service key 4
SKEY5
Service key 5
SKEY6
Service key 6
NAME
Alias
65535. Configure the internal
service key delivered by the
SCP corresponded by this tone
resource.
It is used to describe a
tone unit to make it easily
recognized.
For example, create the service key on the tone board with the
Tone unit number: 1209
Subunit number: 9
103
ADD
TONESVC:UNIT=1209,SUNIT=9,SKEY1=1,SKEY2
=1,SKEY3=1,SKEY4=1,SKEY5=1,SKEY6=1,NAME="SVC
1";
END OF STEPS
SMC Data Configuration

Overview
Typical
Networking
In the existing networks, the SMC is usually connected to the MSCS

through the STP in the signaling network. The protocol stacks at
the MSCS and the SMC sides both use the MAP/TCAP/SCCP/MTP
method. The MAP protocol is employed between the MSCS and
the SMC. This protocol may be borne either on the TDM or the
IP. In general, the current networking mode uses the TDM bearer.
Figure 7 shows the networking diagram.
FIGURE 7 NETWORKING BETWEEN ZXWN CS
Data Collection
104
AND
SMC

and negotiating the related data from the MSCS to the SMC office.
Parameter Items
Parameter Values
ZXWN MSCS signaling point code (24-bit)
3.11.1
3.2.1
STP Signaling point code type
24-bit signaling point

code
SP type
STP
Association type
Direct connect
Signaling link code
Signaling E1 number
E1 10
16 TS
SMC GT
8613907553
Table 53 describes the data configuration flow of the SMC adjacent

office.
TABLE 53 DATA CONFIGURATION FLOW
OF
SMC ADJACENT OFFICE
Steps
Operations
Related Command

office
ADD ADJOFC

to the STP
ADD N7LKS
Creating a signaling link to

the STP
ADD N7LNKE1

the STP
ADD N7ROUTE

the STP
ADD N7OFC
Creating GT translation data

to the SMC
ADD GT
Modifying VLR-supported
Sservices
SET VLRSRVEN
Modifying mobile data of

local office
SET MSCCFG
105

Prerequisites
Context
Perform this procedure to configure the SMC GT data. The GT of

the SMC is sent to the SCCP layer of the STP office, and the SCCP
layer of the STP office converts the GT into the DPC + SSN, and
then deliver it to the MTP layer for addressing.
Steps

system tree.
SET:NEID=11;
Table 54 describes the parameters in the ADD GTT command.
Parameter
Name
GT
GTSL
GTDI
106
Parameter
Description
Instruction
Called GT number
It is a mandatory
of 1~20 digits. It
is used to query the
destination GT number
of message routing
GT translation selector
It is a mandatory
parameter, ranging
from 0 to 1023. Select
the GT translation
selector respectively
according to configured
E164 and E214
numbers
Number change ID
It ranges from 0 to
256, with the default
value as 0. It is the
ID of flexible policy
template change. The
target GT number can
be flexibly changed
based on it. When the
contains a new GT, this
parameter does not
take effect
Parameter
Name
Parameter
Description
Instruction
OFCIDS
Office ID and poll list
It is a mandatory
parameter. The
number of instance
is 0~3000 when
supported. The number
of instance is 1~64
when office ID grouping
is not supported.
The format is
<OFCID>-<SELNUM>,
ID to be polled and
the number of poll
respectively.
GRP
Whether to support
grouping of office ID
It is an optional
parameter, with a
default of NO
The office ID and poll

number of the multiple
signaling points for the
second group
It is an optional
supported. The user
does not need to type
when the office ID
grouping is supported.
The format is
<OFCID>-<SELNUM>,
ID to be polled and
the number of poll
respectively.

third group
It is an optional
supported. The user
when the office ID
The format is
<OFCID>-<SELNUM>,
ID to be polled and
the number of poll
respectively.
OFCGRP2
OFCGRP3
107
Parameter
Name
Parameter
Description
Instruction

fourth group
It is an optional
supported. The user
when the office ID
The format is
<OFCID>-<SELNUM>,
ID to be polled and
the number of poll
respectively.
Subsystem No.
It is an optional
parameter. In the
GT routing mode, select
the default value for
SSN. In the DPC+SSN
routing mode, select
the corresponding SSN
New GT number
It is an optional
parameter, ranging
from 0 to 20 of
characters. It
represents the new
GT translation type.
NTRNTYPE
New GT translation type
It is an optional
parameter, ranging
from 0 to 255. It
represents the new GT
translation type.
TRNRLT
Whether the translation

result contains DPC
and SSN. The options
includes NULL (neither
DPC nor SSN is in
the result), DPC
(containing DPC in
the result), and SSN
(containing SSN in the
result)
It is an optional
parameter. In the
GT routing mode,
select the default
value for TRNRLT. In
the DPC+SSN routing
mode, select the DPC
and SSN for TRNRLT
RTTYPE
Routing mode,
including GT (routing
based on GT) and
DPC (routing based on
DPC+SSN)
It is an optional
parameter. In
general, select GT
for direct connection,
and DPC+SSN for
non-direct connection
OFCGRP34
SSN
NGT
108
Parameter
Name
Parameter
Description
Instruction
Attribute of the new GT

, including the following
options:
NGT (No new GT in the
GT translation result):
The GT number in the
is still the called GT
number.
NAI: The GT number in
the GT translation
result is the new
GT number in the
NGT parameter, only
containing Nature
Of Address Indicator
(NAI).
NGTTAG
NTT: The GT number in

the GT translation
result is the new
GT number in the
NGT parameter, only
containing translation
type.
It is an optional
attribute of the new
GT contained in the
GT translation result.
NGT(No new GT in the
GT translation result) is
selected by default
NTTES: The GT number

result is the new
GT number in the
NGT parameter, only
type, numbering plan,
and coding design.
NTTNAI: The GT
number in the GT
the new GT number
in the NGT parameter,
type, numbering plan,
coding design, and NAI
SCCP coding type,
including:
SCCP
VGT
INT (international
coding) and USA(USA
coding)
GT varying with
including NO (not
supported), and YES
(supported)
It is an optional
the standard type
referred to by the
SCCP coding in the GT
translation result. The
It is an optional
parameter, with NO
109
Parameter
Name
Parameter
Description
Instruction
TT
TT conversion,
including NO (not
supported), and YES
(supported)
It is an optional
parameter, with NO
NAME
Alias
The alias of the GT

translation data for
easy memory.

requirements.
GT number: 8613907553
Office poll: 2-1 (here, the office is STP)

END OF STEPS
Modifying VLR-Supported Services

Prerequisites
Context
For details about VLR-supported services, refer to ZXWN MSCS

MSC Server Data Configuration Guide. Here we only modify the
related parameters for the VLR to support the MO/MT SMS services.
Steps

system tree.
SET:NEID=11;
2. Modify the VLR-supported services to make the VLR supporting
the MO/MT SMS.
SET VLRSRVEN:TELESRV="TSMS_MTPP"&"OSMS_MOPP";
110
Where, TSMS_MTPP means MT SMS, while OSMS_MOPP

means MO SMS.
END OF STEPS
Modifying Mobile Data of Local Office

Prerequisites
Context
For details, refer to Local Office Data Configuration in ZXWN

MSCS MSC Server Data Configuration Guide. Here, we only modify
the related parameters to make the local office support the SMS
service.
Steps

system tree.
SET:NEID=11;
2. Perform this procedure for modify the mobile data of the local
office to make it support the SMS service. The command is as
follows.
SET MSCCFG:ENTAG="SMS";
Where, The parameter SMS means that the local office supports the SMS service.
END OF STEPS
PSTN/2G MSC (M3UA)

Data Configuration
Overview
Typical
Networking
TUP/ISUP signaling is used between ZXWN MSCS and PSTN/MSC.

The signaling from MSCS to MGW uses the IP bearer, and MGW
implements the signaling transfer between the IP bearer and the
TMD bearer. In the existing network, ZXWN MSCS is usually interconnected with the opposite switch in the M3UA mode. Figure
8 shows the networking structure and interface protocols.
111
FIGURE 8 INTERCONNECTION
Data Collection
AND
PSTN/MSC
FOR
INTERCONNECTION
WITH THE
MGW
Parameter Items
Parameter Values
Real interface address of ZXWN MSCS
192.168.1.11
Real interface address of ZXWN MGW
192.168.1.31

(24-bit)
3.11.1
Signaling point code (24-bit) of ZXWN

MGW (SG)
3.31.1
SCTP port No. of ZXWN MSCS (client)
3001
SCTP port No. of ZXWN MGW (server)
3001
TABLE 56 DATA
112
ZXWN MSCS
Before data configuration, it is supposed to complete collecting the

related data of MSCS-to-MGW, and MGW-to-PSTN/MSC. Table 55
and Table 56 list the data to be collected. The parameter values
are just examples. Input these parameters according to the actual
TABLE 55 DATA
BETWEEN
FOR
INTERCONNECTION
WITH THE
PSTN/MSC OFFICE
Parameter Items
Parameter Values
Signaling point code of the PSTN/MSC

switch
3.28.1
Inter-office signaling type
ISUP
CIC code of the junction circuit
0~31
This section introduces the data configuration on the MSCS for

adding a PSTN/2G MSC adjacent office under the precondition that
the H248 data between the MGW and the MSCS are configured,
and that the MGW is successfully registered to the MSCS. Table
57 describes the configuration flow of the PSTN/2G MSC adjacent

office data.
TABLE 57 CONFIGURATION FLOW
DATA
OF
PSTN/2G MSC ADJACENT OFFICE
Steps
Operations
Related Command
Creating 2G MSC/PSTN
adjacent office
ADD ADJOFC
Creating a DT trunk group
ADD TG DT
Creating a PCM system
ADD SPCM
Creating an outgoing route
ADD RT
Creating an outgoing route set
ADD RTS
Creating an outgoing route link
ADD CHAIN
ADD SCTPCONN
Creating the associations and

the M3UA data switched by the
signaling
ADD ASP
ADD AS
ADD M3UART
Creating the SIO-locating-AS
ADD SIOLOCAS
Creating 2G MSC/PSTN Adjacent

Office
Prerequisites
The E1 line between the MGW and the 2G MSC/PSTN is well

connected. Meanwhile, the signaling interworking data is
planned and negotiated.
Context
Perform this procedure to configure the basic information of the

2G MSC/PSTN adjacent office.
Steps

system tree.
SET:NEID=11;
2. Create a 2G MSC/PSTN adjacent office. The command is ADD
ADJOFC.
113

Parameter
Name
Parameter
Description
Instruction
Association type,
including:
ASSOTYPE
AM_SURE
(direct
connection
mode)
AM_QUASI
(half direct
connection
mode)
AM_NONE
(none
connection
mode).
Select AM_QUASI.
Broadband
attribute,
including:
BANDFLAG
OFCTYPE
YES (Support
broadband
attribute)
Select NO.
No (Not
support
broadband
attribute)
Adjacent Office
Types
If the adjacent office is 2G

MSC, select MSCSERVER
or GMSCSERVER
according to its functions.
If the adjacent office is
PSTN, select PSTN.
For example, create a 2G MSC adjacent office with the following

requirements., with the , , , and the . The 24-bit signaling point
coding mode and the quasi-associated mode are adopted.
Office ID: 28
Network type: 1
User alias: TO2GMSC
Destination SPC: 3.28.1
Adjacent office type: GMSCSERVER
Association type: half direct connection mode

ADD ADJOFC:ID=28,NAME="2G MSC",NET=1,OFCTYPE
="GMSCSERVER",SPCFMT=TRIPLE_DEC,SPCTYPE=24,DPC
="3.28.1",RC="25",ASSOTYPE=AM_SURE,SPTYPE=STEP,S
SF=NATIONAL,SUBPROTTYPE=DEFAULT,TEST=YES,BAND
114
FLAG=NO,PRTCTYPE=CHINA,CLST=65535,INFO="CIC_PC
M",RELATEDOFC1=0;
END OF STEPS
Configuration Related to Trunk and

Route
Creating a DT Trunk Group
Prerequisites
Context
Steps
The adjacent office pointed by the trunk group is created.
The range of the trunk group number is configured in the resource management configuration.
Perform this procedure to create a DT trunk group.

system tree.
SET:NEID=11;
2. Create a DT trunk group by executing command ADD TG DT.
Table 59 describes the parameters in the ADD TG DT command.
TABLE 59 PARAMETERS IN THE ADD TG DT COMMAND
Parameter
Name
TG
OFC
Parameter
Description
Instruction
Trunk group ID
It is a mandatory
parameter. It is used
to define a trunk group,
and needs to be planned in
the resource management
system in advance
ID of the office where

the trunk group
belongs
It is a mandatory
specify the corresponding
office of the trunk group.
This parameter must be
defined by command ADD
ADJOFC at first. Then it
can be indexed here
115
Parameter
Name
Parameter
Description
Instruction
MODULE
Module where the

trunk group belongs
It is a mandatory
a service module. Different
trunk groups to the same
office need to be allocated
to different CMP modules
ND
Node No. of the MGW

where the trunk group
belongs
It is a mandatory
parameter. Select the MGW
topology node connected
with the 2G MSC/PSTN
node
User alias
consisting of 0~50
to specifically describe a
trunk group to make it
easily recognized
NAME
Inter-office line signal

identification. Options
include:
SIGLINE
BSC: BSC Ground

Circuit
TUP: Interoffice
Common Channel
Signaling TUP
ISUP: Interoffice
Common Channel
Signaling ISUP
DLC1: Interoffice
Channel
Associated
Signaling
DL/DC(1)
R2: R2 Signaling
BICC: BICC Type
ANU: ANU
Signaling
SORMUP: SORMUP
Signaling
It is used to identify the line
type of this trunk. Select
it according to inter-office
signaling. For the Ai
interface, select ISUP] or
TUP
Trunk group types,

including the following
three types:
KIND
IN (incoming trunk
group): Indicates
that the local office
processes the
incoming calls from
the peer-end office.
OUT (outgoing trunk
group): Indicates that
the local office only
processes the outgoing
116
If BSC is selected for the
inter-office line signal
identification, it must be
configured to BIDIR
Parameter
Name
Parameter
Description
calls to the peer-end
office.
Instruction
BIDIR (Two-way
trunk group):
Indicates that the local
office processes both
the incoming calls
from the peer-end
office and the outgoing
office
Bearer establishment
direction, including the
following three types:
NODIR: The
inter-office bearer
is established without
direction.
BWAY
BACK: The inter-office

bearer is established
based on the backward
mode.
Select NODIR for DT trunk
groups
FORWD: The
inter-office bearer
is established based
on the forward mode
Overload control
threshold
THD
ranging from 0 to 100,
with a default of 100. This
parameter takes effect
when levels of congestion
occur and load control is
required
Circuit selecting
modes, including:
MIN: Every time when
the system selects a
trunk circuit, it always
begins with the circuit
with the minimum
number. This mode
can implement the
preferred plan of trunk
circuits.
CICSEL
MAX: Every time when

with the maximum
number. This mode
can implement the
preferred plan of trunk
circuits.
trunk circuit selecting policy
of the system within this
trunk group, with a default
of CYC. If this No.7 trunk
group is a two-way trunk
group, it is recommended
to set the circuit selecting
mode to ODD/EVEN mode
to prevent contention
when two exchanges select
circuits
CYC: Every time when

the system selects
a trunk circuit, it
always begins with the
circuit next to the one
117
Parameter
Name
Parameter
Description
Instruction
previously selected.
Suppose the numbers
of the trunk circuits
in a trunk group in
ascending order are
TKC0, TKC1, . ,
TKCn. If TKC0 is
selected at the first
time, the system will
select the trunk circuit
in the order of TKC0
TKC1TKCnTK
C0TKC1TKCn.
ODD: Every time when
selects the circuit with
an odd number.
EVEN: Every time
when the system
selects a trunk circuit,
it always selects the
circuit with an even
number.
IDLE: Every time
when the system
idlest circuit.
BUSY: Every time
when the system
busiest circuit
DAS
DAS for the called

number
It is used to analyze
the called number in
an incoming call. This
by command ADD DAS
at first. Then it can be
indexed here
Example: Create a DT trunk group to the 2G MSC office with

the following requirements:
Trunk group ID: 28
ID of the office where the trunk group belongs: 28
User alias: DT28
No. of the CMP module where the trunk group belongs: 4
MGW topology node No.: 101
Other parameters: Adopt the default values.

ADD TG DT:TG=28,OFC=28,MODULE=4,ND=101,NAME
="DT28",SIGLINE=ISUP,KIND=BIDIR,BWAY=NODIR,THD
118
=100,CICSEL=ODD,DAS=0,SIPDAS=0,OPDAS=1,PREDA
S=0,DDI=0,OPDDI=0,MINNAT=0,MAXNAT=26,MININT
=0,MAXINT=26,INREG=INVALID,OUTREG=INVALID,COLE
N=10,BUSYRATE=100,ROAMDAS=0,Q850CCIDX=0,SME
NTERID=0,MLPPDM=4294967295,DISINDEX=0;
END OF STEPS
Creating a PCM System

Prerequisites
The DT trunk group is configured.
Context
The PCM system management data associate the resources on the

gateway with the signaling on the MSCS.
Steps

system tree.
SET:NEID=11;
2. Create a PCM system by executing command ADD SPCM.
Table 60 describes the parameters in the ADD SPCM command.
TABLE 60 PARAMETERS IN THE ADD SPCM COMMAND
Parameter
Name
TG
PCM
Parameter
Description
Instruction
No. of the trunk

group where
the PCM system
belongs
from 1~1000. Select the
trunk group where this PCM
system belongs from the list
of configured trunk groups. It
is used to specify the trunk
group invoking this PCM
system. This parameter is
associated with the trunk
group No. in command ADD
TG ATM, ADD TG DT, ADD
TG PRA, and ADD TG RTP
PCM system No.
It is a parameter for
interconnection with the
peer-end office. If the
configured PCM system
belongs to the inter-office
trunk, the PCM system No. of
the same circuit between two
offices must be the same.
119
Parameter
Name
Parameter
Description
Instruction
When the inter-office line
identification of a trunk group
is TUP or ISUP, the PCM
system No. ranges from 0 to
127.
is BICC, the PCM system No.
ranges from 0 to 5999.
is BSC or ANU, the PCM
system No. ranges from 0 to
2047
NUM
Number of created
PCM systems
PCM No. in the

MGW
MGWPCM
NAME
E1
DDF
The corresponding
trunk group can
invoke the PCM
resources between
the start PCM No.
in the MGW and the
end PCM No.
It is an optional parameter. If
PCM systems belong to a DT
trunk group, this parameter
needs not be configured. If
PCM systems belong to a RTP
or ATM trunk group, select
the number the created PCM
systems
If the PCM system belongs
to a RTP or ATM trunk group,
this parameter needs not be
configured. If the PCM system
belongs to a DT trunk group,
select the corresponding PCM
No. in the MGW
User alias
describe the PCM system
configuration to make it
easily recognized
E1 identification
For DT trunk groups,
describes the E1 with any
characters, which can be set
to DTB/SDTB unit No.-E1
No.
Digital Distribution
Frame (DDF)
location description
For DT trunk groups, the DDF
location description can be set
to Frame No.-Row No.-Port
No.
Example: Create a PCM system to the BSC office with the following requirements:
120
No. of the trunk group where the PCM system belongs: 28
PCM system No.: 1
PCM No. in the MGW: 13

ADD SPCM:TG=28,PCM=1,NUM=3,MGWPCM="1"-"3",INF
O=65535;
END OF STEPS
Creating an Outgoing Route

Prerequisites
The range of outgoing route ID is configured in the resource

management.
Context
Configuring outgoing routes make every trunk group correspond

to an outgoing route.
Steps

system tree.
SET:NEID=11;
2. Create an outgoing route by executing command ADD RT.
Table 61 describes the parameters in the ADD RT command.
TABLE 61 PARAMETERS IN THE ADD RT COMMAND
Parameter Name
Parameter
Description
Instruction
RT
Route No.
from 1~2000. It exclusively
identifies a route. To facilitate
management, the route No. is
configured to be consistent with
the trunk group No.
TG
Trunk group No.
corresponding to the trunk
group No. in the trunk group
configuration
Called number
transform index
during outgoing
calls
It is an optional parameter, which

is an integer ranging from 0 to
2048, with a default of 0. The
called number is transformed
according to this index during
outgoing calls. This index has no
influence on the incoming calls
through this trunk
DDI
121
Parameter Name
Parameter
Description
Instruction
OPDDI
Calling number
transform index
during outgoing
calls

2048, with a default of 0. The
calling number is transformed
according to this index during
outgoing calls. This index has no
influence on the incoming calls
through this trunk
DLPFX
Whether to delete
the prefix of the
calling number
during outgoing
calls, including
NO and YES
with a default of NO. If YES is
selected, the prefix of the calling
number (such as 0/00) will be
deleted during outgoing calls
NAME
User alias
Example: Create an outgoing route with the following requirements.
Route No.: 28
Trunk group No.: 28
User alias: Rout28

ADD RT:RT=28,TG=28,DDI=0,OPDDI=0,DLPFX=NO,NAM
E="ROUT28",HOPCNT=0,RERTS=0,CLISETIDX=65535;
END OF STEPS
Creating an Outgoing Route Set

Prerequisites
The outgoing route set number is created.
Context
Perform this procedure to create an outgoing route set. Every

route belongs to a route set, which contains up to 12 routes.
Steps

system tree.
SET:NEID=11;
2. Creat an outgoing route group by executing command ADD
RTS.
Table 62 describes the parameters in the ADD RTS command.
122
TABLE 62 PARAMETERS IN THE ADD RTS COMMAND

Parameter
Name
RTS
NAME
Parameter
Description
Instruction
Route group No.
from 1~3000. It is used to
identify a route group
User alias
describe a route group to make
it easily recognized
is in the format of No.-Route
No.-Load sharing proportion.
When the percentage is set to
0, the poll mode is adopted.
SEQ: No., which is the location
of the route in the route group.
RTPER
Route No. and

load sharing
proportion list
RTVAL: Route No., associated

with the route group. This
by command ADD RT at first.
PERVAL: Load sharing
proportion of each route in the
route group. If it is set to 0
for all routes by default, the
load is evenly allocated to each
route
Example: Create an outgoing route group with the following

requirements.
Route group No.: 28
User alias: Rout28
Locaiton: 1
Route No.: 28
Percentage: 0

ADD RTS:RTS=28,NAME="ROUT28",RTPER="1"-"28"-"0";
END OF STEPS
Creating an Outgoing Route Link

Prerequisites
The range of outgoing route link ID is configured in the resource

management.
123
Context
Perform this procedure to configure an outgoing route link. Every

outgoing route set belongs to an outgoing route link, which contains up to four route sets.
Steps

system tree.
SET:NEID=11;
2. Creat an outgoing route chain by executing command ADD
CHAIN.
Table 63 describes the parameters in the ADD CHAIN command.
TABLE 63 PARAMETERS IN THE ADD CHAIN COMMAND
Parameter
Name
CHAIN
NAME
Parameter
Description
Instruction
Route chain No.
from 1 to 3000. It is
used to define an outgoing
route chain. When it is
configured in the number
analysis configuration, it
is associated to the route
chain configured here
User alias
consisting of 0~50
to specifically describe a
route chain to make it easily
recognized
Whether the
preference policy
is supported in the
MGW, including:
PRND
NO: When 2B occurs,

the calls in the
same MGW are
not preferred, and
routing is performed
according to other
routing policies of the
system instead.
YES: When 2B
occurs, the calls in
the same MGW are
preferred
124
with a default of YES. It is
a policy for selecting the
rouging route
Parameter
Name
Parameter
Description
RTS1
No. of route group

1, used to set the
route group with
the highest priority
in a route chain
during routing. One
route chain can be
configured with at
most 4 route groups
RTS2
No. of route group 2,

used to set the route
group with the level-2
priority in a route
chain during routing.
One route chain can
be configured with at
most 4 route groups
RTS3

priority in a route
One route chain can
most 4 route groups
RTS4

priority in a route
One route chain can
most 4 route groups
RTPLC
Route Selection Policy

Number
Select the route selection
policy number configured in
ADD RTPLC command
DAS for the called

number
by command ADD DAS
at first. Then it can be
indexed here. It needs to be
set only when Inter-MGW
route chain is set in the
called number analysis. The
default value is 0
TPDAS
Instruction
Select route groups
according to the priority
order. Select route group 1
fist. Only when the circuits
in route group 1 are used
up or all the circuits are
unavailable, the circuits
in route group 2 can be
selected. Only when the
circuits in route group 2 are
used up or all the circuits
are unavailable, the circuits
in route group 3 can be
selected
Example: Create an outgoing route chain with the following

requirements.
Route chain No.: 28
User alias: RLink28
125
No. of Route group 1: 28

ADD
CHAIN:CHAIN=28,NAME="RLink28",PRINODE=YE
S,RTS1=28,RTS2=0,RTS3=0,RTS4=0,RTPLC=0,TPDAS
=0;
END OF STEPS
Creating an SCTP
Prerequisites
Context
The physical configuration of the SMP module is complete.
The range of the SCTP ID is configured in the resource management configuration.
The configuration of SCTP basic connection is used to configure

the basic information of the SCTP association.
Tip:
SCTP basic connection configuration requires using the real interface address or the loop-back IP address. If the IP protocol stack
is configured before the configuration of the interconnection data
with MGW, configuring IP protocol stack again is not required. The
IP address of this real interface can be used directly when a new
association is created. Different associations are distinguished by
different SCTP port numbers.
Steps

system tree.
SET:NEID=11;
2. Create an SCTP. The command is ADD SCTPCONN.
Table 64 describes the parameters in the ADD SCTPCONN
command.
126

Parameter Name
MODULE
OFCID
Parameter
Description
Instruction
Module No.
indicating the number of the
signaling module homed by this
SCTP association. Select the SMP
module number. Each SMP can
support up to 128 associations.
The associations under the same
AS are required sharing load
on SMP modules as more as
possible.
SCTP opposite
office ID
designating the office No. of the
direct-associated association.
Type the MGW adjacent office No.
specified in the adjacent office
configuration.
Bearer protocol
types, including
PROT
M2UA
M2PA
M3UA
SUA
H248
BICC
IUA
DHCTRL
SIP
DIM
V5UA
H245
SCTP application
attributes.
Options include:
ROLE
SVR: SCTP is
used as server
CLT: SCTP is used
as client
It is a mandatory parameter. It is
used to identify the upper-layer
protocol type borne by the SCTP
association. In general, M3UA is
selected.M2UA is selected when
MGW transfers the signaling with
the M2UA mode.
It is a mandatory parameter. For

Mc interface, MSCS is configured
as CLT, and MGW is configured
as SVR. For Nc interface, this
should be negotiated by both
sides. For example, the small
signaling point serves as CLT,
and the big signaling point serves
as SVR
127
Parameter Name
Parameter
Description
Instruction
designates the service address
of local end of this association,
with a format of Local IP
address type-VPN of local IP
address-Local IP address
LOCADDR
Local IP address
Local IP address type: IPv4 and

IPv6;
VPN of local IP address: Rang
from 0 to 65535;
Local IP address: the format is
xxx.yyy.zzz.mmm
LOCPORT
Local port
number
is the local SCTP port number of
the association, ranging from 1
to 65535.
REMADDR
Opposite IP
address
designates the service address of
opposite end of this association,
REMPORT
Opposite port
number
the opposite SCTP port number
of the association, ranging from
1 to 65535.
NAME
Alias

characters.
SCTP ID
the global serial number of the
SCTP association, ranging from 1
to 2048. Configure it according
to the association planning.
ID
For example, configure the SCTP connection between MSCS 30

and MGW 31. Bearer protocol is M3UA, SCTP signaling processing module number is 3, local port number is 3001, opposite
port number is 3001, local IP address is 192.168.1.30, opposite IP address is 192.168.1.31, and SCTP association ID is 2.
128
MGW office ID: 101

001,NAME="PSTN",ID=2,INSTRM=16,OUTSTRM=16,MAX
RTRY=5,MAXRTO=500,MINRTO=50,INITRTO=100,HB=5
00,FIXNH=NO,SCTPMAXRTRYNUM=10,DELAYACK=20,M
AXBURST=4,PRIMARYPATH=REMIP1,PMTU=0,BREAKTI
ME=0,PDTHRESH=0,MINCWND=0,PLTIMER=10,MPPLTH
RD=2,DPLEN=MTU,CB=200;
END OF STEPS
Creating an ASP
Prerequisites
The SCTP association information is configured.
The range of the ASP ID is configured in the resource management configuration.
Context
ASP configuration defines the one-to-one relationship between the

ASP and the association.
Steps

system tree.
SET:NEID=11;
Table 65 describes the parameters in the ADD ASP command.
Parameter Name
ASSOCID
Parameter
Description
SCTP ID
Instruction
It is a mandatory parameter, ranging
from 1 to 2048
Type the association ID configured in
the SCTP connection configuration.
NAME
Alias
It is a mandatory parameter, with

a lengthen ranging from 1 to 50
characters. It may be named with a
format of Adjacent office alias-SCTP
number.
ID
ASP ID

from 1 to 2048.
129
Parameter Name
Parameter
Description
Instruction
It is recommended to be consistent
with ASSOCID.
ISLOOP
ISLOCK
ASP self-loop
ID
ASP blocking
flag
It is an optional parameter. It is used

to set whether the ASP is self-looped.
It is an optional parameter. It is used
set whether the ASP is in blocking
state.
Blocking is used for management.
Example: Create the ASP between MSCS and MGW with the
MGW office ID: 101
User alias: ISUP.
ADD ASP:ASSOCID=2,NAME="ISUP",ID=2,ISLOOP=NO,I
SLOCK=NO;
END OF STEPS
Creating an AS
Prerequisites
The ASP configuration is complete.
The range of the AS ID is configured in the resource management configuration.
Context
AS configuration is used to configure the basic information for the

application server.
Steps

system tree.
SET:NEID=11;
2. Create the AS. The command is ADD AS.
Table 66 describes the parameters in the ADD AS command.
130
TABLE 66 PARAMETERS IN THE ADD AS COMMAND

Parameter
Name
Parameter
Description
Instruction
PROT
Supported
adaptation layer
protocols
It indicates the protocol

type of a bearer. In general,
M3UA is selected according
to the networking planning.
It is configured as M2UA
signaling with M2UA mode.
ASPID
ASP ID

ASP configuration.
NAME
Alias
It is a mandatory
parameter. The alias
customized by the user.
AS ID
It is an optional
parameter. It is the unique
identification of the AS. In
memory. The parameter
ranges from 1 to 640
ID
EXISTCTX
Whether the routing

context ID exists
CTXID
Routing context ID
The routing context is
unique in the network.
This parameter must
opposite-end. Its default
value is NO
Usage tag. Options

include:
SGP
ASTAG
ASP
SRV (IPSP server)
CLT (IPSP client)
For Mc interface, MSCS

generally serves as
IPSP_Client, and MGW
serves as IPSP_Server.
When MGW acts as a SGW,
the AS at the MSCS side
serves as ASP, and the AS
at the SGW side serves as
SGP.
For Nc interface, this should
small signaling point serves
as IPSP_Client, and the big
signaling point serves as
IPSP_Server.
131
Parameter
Name
ASUP
Parameter
Description
User types
supported by AS.
Options include TUP,
ISUP, BICC, H.248,
ALCAP SCCP, PCA,
NNSF and ALL
Instruction
It defines the upper-layer
user types supported by
the AS. Currently, there are
eight types of users.
User type is not configured
signaling with the M2UA
mode
The supported service
modes include:
ASMD
Service modes
supported
OVERRIDE(Over-ride
mode)
LOAD (Load share

mode).

only one ASP is in the
activated statue. In this
case, only one ASP needs
be configured. In the
load sharing mode, N
in the activated working
statue, and K ASPs should
be configured in the
deactivated standby statue.
The value of N+K is not
ASPs actually configured
SSN
132
Types of subsystem.
Options include
NO_SSN (subsystem
SSN excluded
(null)), SCCP, REV2
(standby), ISUP,
OMAP, MAP, HLR,
VLR, MSC, EIR, AUC,
REV11(standby),
INAP, USSD, VLRA,
SGSN_BSCAP,
RANAP, RNSAP,
GMLC_MAP, CAP,
GSMSCF_MAP,
SIWF_MAP, SGSN_
MAP, GGSN_MAP,
IP (intelligent
peripherals),
SMC, SSP_SCP,
BSC_BSSAP_LE,
MSC_BSSAP_LE,
SMLC_BSSAP_LE,
BSS_O_M_A ,
BSSAP_A and
RVE255.
Types of subsystem
supported by application
server (AS).
Parameter
Name
Parameter
Description
Instruction
0 to 16.
NVAL
The N value in load

sharing mode
The N+K should be equal to

the number of ASP under
AS.
The N value indicates that
AS puts into use if N ASPs
put into use.
Example: Create the AS between MSCS and MGW with the

MGW office ID: 101
AS configuration ID: 2
Supported user type: ISUP
ASP ID: 2
Client: MSCS
Alias: ISUP

ADD AS:PROT=M3UA,ASPID="2",NAME="ISUP",ID=2,EXI
STCTX=NO,ASTAG=CLT,ASUP="ISUP",ASMD=LOAD,NVAL
=1,KVAL=0;
END OF STEPS

Prerequisites
The AS configuration is complete.
The range of M3UA static route ID is configured in the resource

management.
Context
Creating an M3UA static route means configuring the mapping relationship between an M3UA static route and an AS.
Steps

system tree.
SET:NEID=11;
command.
133

Parameter
Name
Parameter
Description
Instruction
ID
ID of M3UA
static route
as the AS ID.
ASID
AS ID
MODE
Alignment
mode of
routes.
Options
include
BYTURNS
LOCAL
NATURE

Nature option.
the activated ASP
NAME
Alias


MGW office ID: 101
AS ID: 2
User alias: ISUP.

ADD M3UART:ID=2,ASID=2,MODE=BYTURNS,NAME="IS
UP";
END OF STEPS

Prerequisites
134
The M3UA static route configuration is complete.
Context
Where, a routing keyword describes the parameters and their values of a group of No.7 signaling messages. The corresponding AS
is selected according to the message attributes, serving the purpose of selecting route for messages.
The attribute of the message includes DPC+NET+OPC+SIO,
where, DPC is the destination signaling point code, NET is the
network type, OPC is the originating signaling point code, and
SIO is the service indicator octet.
to a routing table that is maintained by the ASPs under the AS.
signaling, the ASP configuration of the SCTP connection and M3UA
is similar to the link logic and bearer information configuration in
the MTP configuration, the AS configuration of the M3UA is similar
to the link set configuration in the MTP configuration, and the SIOlocating-AS configuration is similar to the signaling office ID and
route configuration in the MTP configuration. The difference is that
the IP route to one subscriber of one office is configured in one
SIO-locating-AS configuration record.
Steps

system tree.
SET:NEID=11;
Table 68 describes the parameters in the ADD SIOLOCAS
command.
Parameter
Name
Parameter
Description
Instruction
ID
SIOlocation-AS ID
indicating the serial number of
SIO-locating-AS, ranging from 1 to
4096. In general, it is the same as
the AS ID.
NAME
Alias

is the alias customized by the user.
135
Parameter
Name
Parameter
Description
Service
indication.
Options include
SIO
TUP
ISUP
BICC
H.248
ALCAP
SCCP
PCA
NNSF
Instruction
indicating the subscriber type
belonged by the transmitted
message. Different user types can
be located to the same AS under
the precondition that the MS must
support these user types
Select H.248 for Mc interface,
BICC for Nc interface, SCCP for
the RNC or BSC office transferred
through MGW, and TUP or ISUP
for the 2G MSC/PSTN office
transferred through MGW.
Destination
adjacent office
ID
indicating the adjacent office ID
corresponded by the destination
signaling point of the M3UA.
It needs to associate with the
adjacent office ID in the adjacent
office configuration.
OPOFCID
Original
adjacent office
ID
It is the adjacent office ID

corresponding to the M3UA
originating signaling point. If
0 (indicating the local office)
is selected, it indicates that
the message is sent from the
local office, and the routing
context is routed according to
DPC+NET+OPC+SIO. If 65535
(invalid) is selected, it indicates
that the OPC field is invalid, and
the routing context is routed
according to DPC+NET+SIO
PCM
PCM system
number
ranges from 0 to 65535, with a
default of 65535 (invalid).
RT1
ID 1 of M3UA
static route
RT2
ID 2 of M3UA
static route
OFCID
It corresponds to the ID
specified in the M3UA static
route configuration. RT1 is a
mandatory parameter. In general,
RT1 is required. When the
optimum route mode is adopted,
RT1 is set as an active route, and
RT2 is set as a standby route.
Example: Create SIO-locating-AS between MSCS and 2G MSC

136
2G MSC office ID: 28
Service indication: ISUP

ADD SIOLOCAS:ID=2,NAME="ISUP",SIO=ISUP,OFCID=2
8,OPOFCID=65535,PCM=65535,RT1=2,RT2=0;
END OF STEPS
BSC Data Configuration

Overview
Typical
Networking
BSSAP signaling is used between the ZXWN MSCS and BSC. The
signaling from the ZXWN MSCS to the MGW uses the IP bearer, and
the MGW completes the signaling switching from the IP bearer to
the TMD bearer. The MGW provides the TDM bearer of the user
plane, and the user data are transferred through PCM codes. In
the existing networks, both the MSCS and the MGW usually use
the same 14-bit SPC for interworking with the BSC. The networking
diagram is shown in Figure 9.
FIGURE 9 NETWORKING
Data Collection
WITH
BSC

the related data of MSCS-to-MGW, and MGW-to-BSC. Table 69 and
Table 70 list the data to be collected. The parameter values are
137
TABLE 69 DATA
INTERCONNECTION
WITH THE
MGW
Parameter Items
Parameter Values
192.168.1.11
192.168.1.31

MSCS
1.11.1

MGW (SG)
1.31.1
4001
4001
TABLE 70 DATA
FOR
FOR
INTERCONNECTION
WITH THE
BSC
Parameter Items
Parameter Values
BSC signaling point code
1.99.1
Inter-office signaling type
BSSAP
CIC code of the junction circuit
0~31

adding a BSC adjacent office under the precondition that the H248
data between the MGW and the MSCS are configured, and that the
MGW is successfully registered to the MSCS. Table 71 describes the
BSC adjacent office data configuration flow.
TABLE 71 BSC ADJACENT OFFICE DATA CONFIGURATION FLOW
138
Steps
Operations
Related Command
Creating a BSC
adjacent office
ADD ADJOFC
Creating BSC office

direction
ADD BSCOFC
Creating a BSC
topology node
ADD TOPO
Creating the topology

relationship between
BSC and MGW
ADD RNCMGWTOPO
Creating a DT trunk
group to the BSC
ADD TG DT
Creating a PCM
system
ADD SPCM
Creating the
associations and the
Steps
Operations
Related Command
ADD SCTPCONN
ADD ASP
M3UA data switched

by the signaling
ADD AS
ADD M3UART
8
Creating the
SIO-locating-AS
ADD SIOLOCAS
Office Direction and Topology

Configuration
Creating a BSC Adjacent Office
Prerequisites
Context
Perform this procedure for configuring the basic information of the

BSC adjacent office.
Steps

system tree.
SET:NEID=11;
2. Create the BSC adjacent office. The command is ADD ADJO
FC.
command.
139

Parameter
Name
Parameter
Description
Instruction
ID
Office ID
number of the adjacent office,
and ranging from 1 to 2048.
It is usually configured as the
exchange ID of the adjacent
office during the all-network
planning.
NAME
Alias
by the user.
NET
Network type
office when the local office is
configured with several SPs.
The default is the network type
of this SP when there is only
one SP in the local office.
OFCTYPE
Adjacent office
type
SPCFMT
SPC format
Select TRIPLE_DEC
SPCTYPE
SPC type
DPC
SPC
RC
Area code
Type BSC in this case
Specify it based on the SPC
type of the adjacent office. In
China, BSC adopts the 14-bit
SPC.
When the adjacent office type
is BSC, RC must be empty.
Association type,
including
ASSOTYPE
140
AM_SURE
(direct
connection
mode)
AM_QUASI
(half direct
connection
mode)
AM_NONE(none connection
mode)
Select AM_QUASI
Parameter
Name
Parameter
Description
Instruction
Signaling point
type, including
SPTYPE
SEP
STP
STEP
Select SEP
Subservice
function, including
INTERNATIONAL (International signaling point

code)
INTERNATIONAL
STANDBY
(International
standby signaling point
code)
SSF
TEST
NATIONAL
(National
signaling point
code)
NATIONAL
STANDBY
(National
standby
signaling point
code).
Test flag
In general, select NATIONAL
STANDBY for BSC adjacent
office.
It is an optional parameter, for

setting whether the MTP3 link
actively initiates the link test
after entering in the service
status.
It is selected by default.
BANDFLAG
Broadband
attribute
Select NO
Protocol types,
including:
CHINA (China)
ITU (International Telecommunications

Union)
ANSI
(American
National
Standards
Institute).
PRTCTYPE
CHINA and ITU are used for
the NO.7 signaling networking
of the ITU standards. ANSI
is used for the No.7 signaling
networking of the American
standards.
141
Parameter
Name
CLST
Parameter
Description
Instruction
Cluster ID
The cluster number should
be configured in ADD CLST.
0 to 65535, with a default of
65535.
Office Info,
including:
CIC_PCM (CIC
using PCM
Code Mode
Starts Load
Control)
BLOCK
(Manual Block
State)
EVEN_CIC
(Office
Controls Even
CIC if CIC
Resource
Collision)
INFO
RELATEDOFC1
CALLING
(Allow Calling
Transform)
CALLED
(Allow Called
Transform)
MOD24_CIC
(Mod 24 CIC
Mode)
TEST
(Dynamic Test)
Related office ID
with a default of CIC_PCM
ranging from 0 from 3000
Office extend info,

including
SIGBRDCST
(Support
Signaling
Broadcast
Message)
MTP
(Hongkong
MTP Standard)
INFOEX
142
DUPU (
Screen DUPU
message)
SUA_REC_
DT1 (Receive
SUA message
and handle
Parameter
Name
Parameter
Description
Instruction
it as DT1
message)
SUA_SND_DT1 (Send
SUA message
and handle
it as DT1
message
without SN.)
OPEN_TG_RES (Open
outter trunk
group resource)
Example: Create a BSC adjacent office with the following requirements.
BSC office ID: 99
Network type: 2
User alias: BSC99
SPC type: 14-bit
Sub-service function: National standby SPC
Adjacent office type: BSC
Association type: Quasi-associated mode.

ADD
ADJOFC:ID=99,NAME="BSC99",NET=2,OFCTYPE
="BSC",SPCFMT=TRIPLE_DEC,SPCTYPE=14,DPC="1.99.
1",ASSOTYPE=AM_QUASI,SPTYPE=SEP,SSF=NATIONAL
STANDBY,SUBPROTTYPE=DEFAULT,TEST=YES,BANDFLAG
LATEDOFC1=0;
END OF STEPS
Creating BSC Office Direction

Prerequisites
You know the ID of the exchange to be configured.
The BSC adjacent office is created.
Context
Perform this procedure to configure some additive attributes of the

BSC adjacent office.
Steps

143

system tree.
SET:NEID=11;
2. Create the BSC office direction. The command is ADD BSCO
FC.
Table 73 describes the main parameters in the ADD BSCOFC
command.
TABLE 73 PARAMETERS IN THE ADD BSCOFC COMMAND
Parameter
Name
Parameter
Description
Instruction
BSCOFCID
BSC office ID
MCC
Mobile country
code
with the length ranging from 1
to 3 characters.
MNC
Mobile network
code
with a length ranging from 1
to 3 characters.
Service identifier
Type it according to the actual
conditions. In general, all
the options can be selected,
except SUPCELLLOAD
(Support load-based switch)
and ALL (Support all).
INFO
A interface load
share mode,
including
SELTYPE
144
EXCELLENT
(excellent
choice priority)
LOAD (load
share priority)
Select EXCELLENT in this
case.
NAME
Alias
to 50 characters.
RAS
BSC office
re-assignment
Select YES or NO according to
the actual conditions
CICINMGW
MGW manage BSC

CIC, including
options: NO(NO)
and YES(YES)
The default is NO(NO)
BEARTYPE
BSC bearer type,

including options:
TDM(TDM),
IPV4(IPV4) and
IPV6(IPV6)
with a default of TDM(TDM)
Example: Create the BSC office direction with the following

requirements.
BSC office ID: 99
Mobile country code: 460
Mobile network code: 00
Service identifier: "BSCRST"&"MSCRST"&"BSCRCIC"&"MSCRCIC"&"BLOCKCIC"&"BLOCKCICG"&"UNBLOCKCIC"&"

UNBLOCKCICG"&"RESINDN"&"CHARGEINDN"&"FLUXCONTROL"&"BSCTRACK"&"MSCTRACK"&"QUEUEINDN"&"CALLREBUILD"&"SUPCELLLOAD"&"UNBLOCKCICINS"&"SupComID"&"SupEmlpp"&"SupChnNed"&"SupCIResMode"&"SupLCS"
Alias: BSC99.

ADD BSCOFC:BSCOFCID=99,MCC="460",MNC="00",INFO
="BSCRST"&"MSCRST"&"BSCRCIC"&"MSCRCIC"&"BLOCKCIC
"&"BLOCKCICG"&"UNBLOCKCIC"&"UNBLOCKCICG"&"RESIND
N"&"CHARGEINDN"&"FLUXCONTROL"&"BSCTRACK"&"MSCTR
ACK"&"QUEUEINDN"&"CALLREBUILD"&"SUPCELLLOAD"&"UN
BLOCKCICINS"&"SupComID"&"SupEmlpp"&"SupChnNed"&"S
upCIResMode"&"SupLCS",SELTYPE=EXCELLENT,NAME="BS
C99",RAS=NO,CICINMGW=NO,CICATTR="TFRV1"&"THRV
1"&"TFRV2"&"THRV2"&"TFRV3"&"THRV3"&"DFR14"&"DFR12
"&"DFR6"&"DFR3"&"DHR6"&"DHR3"&"HSCSD14x2"&"HSCSD1
2x2"&"HSCSD6x2"&"HSCSD14x4"&"HSCSD12x4"&"HSCSD6x
4"&"HSCSD12x6"&"HSCSD6x6",BEARTYPE=TDM,PROTYPE
=PRIVATE,IPCODECMODE=CC,SETPRE=SET1;
END OF STEPS
Creating a BSC Topology Node

Prerequisites
You know the number of the exchange to be configured.
The encoding and decoding speech template is added.
Context
Perform this procedure to configure the adjacent NE information,

including equipment type, bearer type and attributes, user plane
version, encoding and decoding template, and other information.
Steps

system tree.
SET:NEID=11;
2. Create a BSC topological node. The command is ADD TOPO.
Table 74 describes the main parameters in the ADD TOPO
command.
145

Parameter
Name
ID
OFCID
NAME
CODECID
Parameter
Description
Instruction
Topology node
ID
used for defining a topological
node. It is recommended that
this ID is consistent with the
office ID of this node.
Office ID
for specify the office ID of this
topological node, ranging from 1
to 2048. This parameter must
be defined by the ADD ADJOFC
command first. Type the BSC
office ID according to actual
conditions.
Alias

naming this topological node,
with a length ranging from 1 to
50 characters.
CODEC identity
for specifying the Encoding and
decoding speech Template used
by this topological node. This
the ADD CODECTPL command
first.
conditions.
ETYPE
Equipment type

specifying the NE type of this
topological node.
Select BSC for an BSC node.
146
IPVER
IP version of
the node
indicating the IP protocol version
supported between nodes.
Select IPV4 or IPV6 according
to the actual conditions. In
general, it is set as IPV4
ATTR
Bearer
attributes
This parameter is only valid

for the node with the type
of R4GW (MGW). You need
not to configure it for an BSC
topological node.
UPVER
User plane
protocol version
It is an optional parameter. This

parameter is not configured for
a BSC node
Parameter
Name
Parameter
Description
Instruction
Extended
attributes
(tunnel mode),
including
ATTR2
TRFMOD
NOTUNL
(None
tunnel
mode)
RTUNL
(Rapid
tunnel
mode)
DTUNL
(Delay
tunnel
mode)
Transmission
mode, including
MCINTF (Mc
interface signal
transfer mode)
This parameter sets which

tunnel mode is used for setting
up a bearer when this node
supports the IP/RTP bearer, with
a default of NOTUNL (None
tunnel mode).

that mode used by the topology
for reporting the detected CNG
or CED fax signals, with a default
of MCINTF (Mc interface signal
transfer mode).
YES: The user plane entity
implements error inspection,
and sets the FQC bit position
according to the result. It will
transmit all frames includes
the error frames to the user
plane layer. During a call,
the error packet control
parameter delerrsdu=Yes,
which is delivered by the
terminal established by MGW
on the Mc interface. The
NA, NA during RAB assignment.
UPERRCTRL
Error SDU
control
NO: The user plane entity

implements the error inspection.
It will directly discard the
error frame. During a call, the
delerrsdu=No, which is delivered
by the terminal established by
MGW on the Mc interface. The
INVALIDTION: The user plane
entity does not implement the
error inspection. During a
call, the error packet control
parameter delerrsdu=NA,
which is delivered by the
terminal established by MGW
on the Mc interface. The
147
Parameter
Name
Parameter
Description
Instruction
deliveryOfErroneousSDU is NA,
plane for error frames. It is
only valid for MGW-type and
RNC-type topological node. The
default value is YES
DTMFTC
Tandem office
send DTMF
use TC mode,
containing two
options:
NO
YES

whether the tandem office uses
the TC resources during DTMF
number delivery.
It contains the following options.
MGWCON
MGW
congestion
reporting
capability
SMGWCON (Standard MGW

congestion event)
CMGWCON (Custom MGW

congestion event).
The default value is SMGWCON.
Example: Create a BSC topological node with the following

requirements.
BSC office ID: 99
Topological node ID: 99
Alias: BSC99
CODEC ID: 1

ADD TOPO:ID=99,OFCID=99,NAME="BSC99",CODECID
=1,ETYPE=BSC,PROTTYPE=H248,DMNAME="RNC",IPVER
=IPV4,UPVER="V2",ATTR2=NOTUNL,TRFMOD=MCINTF,UP
ERRCTRL=YES,DTMFTC=NO,MGWCON=SMGWCON,AUTOF
AX=YES,OOBTC=NO,BCUID=0,SENDCAP=NO,G711TRAN
=NO,BICCDTMF=TRANSPARENT,IPBCP2833=BYMGW,BIC
CDTMPPER=0,AOIPPRO=PRIVATE;
END OF STEPS
Creating the Topology Relationship between BSC

and MGW
Prerequisites
148
The BSC topological node is configured.
Context
Perform this procedure to configure the topological relationship

between BSC and MGW, thus to associate the MGW node with the
BSC node.
Steps

system tree.
SET:NEID=11;
2. Create the topological relationship between BSC and MGW. The
command is ADD RNCMGWTOPO.
Table 75 describes the main parameters in the ADD RNCMG
WTOPO command.
TABLE 75 MAIN PARAMETERS IN THE ADD RNCMGWTOPO
COMMAND
Parameter
Name
Parameter
Description
Instruction
MGWID
MGW node ID
RANTYPE
Office type
RANID
RNC/BSC node
number
It is the node ID specified

during the MGW topological
node configuration
Select BSC for BSC access.
during the BSC topological
node configuration.
Load Sharing
Mode, including:
SHMODE
NONE (NOT
Load Sharing)
BEARLOAD
(Bear Load
Sharing)
MBLOAD
(MasterBackup Load
Sharing)
Bearer Type 1,
including:
BTYPE1
BRATIO1
ATM (ATM)
IP (IP)
Bearer Type 1
Ratio
The parameter is used to

set the multiple load sharing
modes, with a default of NONE
The parameter indicates the

first bearer type, with a default
of ATM
The parameter is used to the
set the proportion of the first
bearer type, with a default of 1
149
Parameter
Name
Parameter
Description
Bearer Type 2,
including:
BTYPE2
BRATIO2
NONE (NONE)
ATM (ATM)
IP (IP)
Bearer Type 2
Ratio
Instruction

second bearer type, with a
default of NONE

the set the proportion of the
default of 1
BPER
Ratio of bearer
from MGW to BSC
NAME
Alias
It is used for setting the traffic

load-sharing ratio when the
BSC accesses several MGWs.
If the BSC only connects to
one MGW, this parameter is set
as 1 by default
to 50 characters.
Example: Create the topology relationship between BSC and

MGW with the following requirements.
MGW node ID: 101
Office type: BSC
BSC node ID: 99.

ADD RNCMGWTOPO:MGWID=101,RANTYPE=BSC,RANI
D=99,SHMODE=NONE,BTYPE1=ATM,BRATIO1=1,BTYPE2
=NONE,BRATIO2=1,BPER=1;
END OF STEPS
Trunk and PCM Configuration

Creating a DT Trunk Group
Prerequisites
150
The exchange ID to be configured is given.
The adjacent office to which the trunk group points is created.
The trunk group No. range is set in the resource management

system.
Context
When the A interface or Ai interface adopts the TDM bearer, or

when MGWs are interconnected through the TDM bearer, DT trunk
groups need to be configured. The circuit status in each trunk
group is managed by the corresponding trunk management module, so it is required to configure multiple trunk groups to each
BSC office (4~8 trunk groups are recommended). To implement
load sharing, it is required to allocate roughly the same number of
BSC circuits to each CMP module.
Steps

system tree.
SET:NEID=11;
2. Create a DT trunk group by executing command ADD TG DT.
The explanation of the main parameters in command ADD TG
DT is shown in Table 76.
TABLE 76 PARAMETERS IN THE ADD TG DT COMMAND
Parameter
Name
Instruction
Trunk group ID
It is a mandatory
to define a trunk
group, and needs to be
planned in the resource
management system in
advance

the trunk group belongs
It is a mandatory
parameter. It is
used to specify the
corresponding office of
the trunk group. This
parameter must be
defined by command
ADD ADJOFC at first.
Then it can be indexed
here
MODULE
Module where the trunk

group belongs
It is a mandatory
a service module.
Different trunk groups
to the same office
need to be allocated to
different CMP modules
ND
Node No. of the MGW

belongs
It is a mandatory
parameter. Select the
MGW topology node
connected with the 2G
MSC/PSTN node
TG
OFC
151
Parameter
Name
NAME
Instruction
User alias
It is an optional
of 0~50 characters. It
is used to specifically
describe a trunk group
to make it easily
recognized

identification. Options
include:
BSC: BSC Ground

Circuit
TUP: Interoffice
Common Channel
Signaling TUP
ISUP: Interoffice
Common Channel
Signaling ISUP
DLC1: Interoffice
Channel Associated
Signaling DL/DC(1)
R2: R2 Signaling
BICC: BICC Type
ANU: ANU Signaling
SORMUP: SORMUP
Signaling
SIGLINE
It is an optional
to identify the line type
of this trunk. Select it
according to inter-office
signaling. For the Ai
interface, select ISUP]
or TUP
Trunk group types,

three types:
IN (incoming trunk
group): Indicates
processes the incoming
calls from the peer-end
office.
KIND
OUT (outgoing trunk

office.
BIDIR (Two-way trunk
group): Indicates
processes both the
incoming calls from the
peer-end office and the
outgoing calls to the
peer-end office
152
It is an optional
parameter. If BSC
is selected for the
inter-office line signal
identification, it must be
configured to BIDIR
Parameter
Name
Instruction
NODIR: The inter-office
without direction.
BWAY

mode.
It is an optional
parameter. Select
NODIR for DT trunk
groups
FORWD: The
inter-office bearer is
established based on
the forward mode
Overload control
threshold
THD
It is an optional
0 to 100, with a default
of 100. This parameter
takes effect when levels
of congestion occur and
load control is required
Circuit selecting modes,

including:
with the minimum
number. This mode can
implement the preferred
plan of trunk circuits.
CICSEL

with the maximum
the system selects
a trunk circuit, it
always begins with
the circuit next to the
one previously selected.
Suppose the numbers
of the trunk circuits in a
trunk group in ascending
order are TKC0, TKC1,
. , TKCn. If TKC0
is selected at the first
select the trunk circuit
in the order of TKC0T
KC1TKCnTKC0
TKC1TKCn.
It is an optional
specify the trunk circuit
selecting policy of the
system within this trunk
group, with a default of
CYC. If this No.7 trunk
group is a two-way
trunk group, it is
recommended to set the
circuit selecting mode
to ODD/EVEN mode
to prevent contention
when two exchanges
select circuits

153
Parameter
Name
an odd number.
Instruction
EVEN: Every time when

an even number.
IDLE: Every time when
selects the idlest circuit.
BUSY: Every time when
selects the busiest
circuit
DAS
SIPDAS
OPDAS
PREDAS
154
DAS for the called

number
It is an optional
to analyze the called
number in an incoming
call. This parameter
must be defined by
command ADD DAS at
first. Then it can be
indexed here
DAS for the domain

name of the called
number during a SIP
outgoing call
It is used get the name

of the IMS domain
where the called party
is located through
analyzing the called
number during a SIP
outgoing call. It is
only used for RTP trunk
groups
DAS for the calling

number
the calling number in
parameter must be
defined by command
ADD DAS at first. Then
it can be indexed here
DAS for pre-analyzing

the called number
It is used to pre-analyze
parameter must be
defined by command
ADD PREDAS at first.
here
Parameter
Name
DDI
OPDDI
MINNAT
MAXNAT
MININT
MAXINT
Instruction
Incoming called number

transform ID
It is the index of
the incoming called
number transform. This
parameter must be
defined by command
ADD DDI at first. Then
Incoming calling
number transform ID
It is the index of
the incoming calling
parameter must be
defined by command
Minimum national
number length
It is an optional
parameter, which is
an integer ranging from
of 0. It is used to
specify the minimum
digit length of the
called number during a
national incoming call
Maximum national
number length
It is an optional
parameter, which is
of 26. It is used to
specify the maximum
digit length of the
called number during a
national incoming call
Minimum international
number length
It is an optional
parameter, which is
of 0. It is used to
specify the minimum
digit length of the
called number during an
international incoming
call
Maximum international
number length
It is an optional
parameter, which is
of 26. It is used to
specify the maximum
digit length of the
called number during an
international incoming
call
155
Parameter
Name
Instruction
INREG
Incoming register
signaling flag, including
options: INVALID,
MFC, MFP, DTMF, DP
and MF
It is an optional
parameter, with a
default of INVALID
OUTREG
Outgoing register
signaling flag, including
options: INVALID,
MFC, MFP, DTMF, DP
and MF
It is an optional
parameter, with a
default of INVALID
COLEN
The maximum length of

CAS calling number end
It is an optional
parameter. It ranges
from 1 to 32, with a
default of 10.
Trunk circuit usage
It is an optional
parameter, which is
an integer ranging
default of 100. After
the trunk circuit usage
is configured, when the
ratio of busy circuits to
all circuits in this trunk
group exceeds this
value, congestion occurs
in this trunk group.
After the congestion
is relieved, report the
trunk congestion times
and congestion duration
in the performance
statistics. This
parameter does not
take effect when it is
configured to 100
DAS for roaming

numbers
It is an optional
parameter. After this
DAS is configured, if
the local office serves
as a GMSC, this DAS
is preferred for the
returned roaming
numbers. Otherwise,
the roaming number
DAS configured in
the number analysis
template is used
BUSYRATE
ROAMDAS
156
Parameter
Name
Instruction
Q850CCIDX
Q850 customization
index
It is an optional
default of 0.
ID of signaling
modification entrance
It is an optional
parameter, associated
with the inter-office
signaling modification
entrance. It ranges
default of 0
SMENTERID
Example: Create a DT trunk group to the BSC office with the

following requirements:
Trunk group ID: 99
User alias: BSC99
No. of the CMP module where the trunk group belongs: 3
The command is:

ADD TG DT:TG=99,OFC=99,MODULE=4,ND=101,NAME
="BSC99",SIGLINE=BSC,KIND=BIDIR,BWAY=NODIR,THD
=100,CICSEL=ODD,DAS=0,SIPDAS=0,OPDAS=0,PREDA
S=0,DDI=0,OPDDI=0,MINNAT=0,MAXNAT=26,MININT
END OF STEPS

Prerequisites
The DT trunk group is configured.
Context

Steps

system tree.
SET:NEID=11;
157

Parameter
Name
Parameter
Description
Instruction
PCM
TG
PCM-belonged trunk group ID
NUM
Number
100. In general, select the
default value.
MGW PCM
number
consisting of MGWPCM_S and
MGWPCM_F. The start and
end numbers of the MGW
PCM mean that the trunks
corresponded by PCM resources
of this number section can be
invoked. This parameter is left
blank when the PCM-belonged
trunk number is an interoffice
BICC.
INFO
Self-loop PCM
number
with a default of 65535.
Enter an integer ranging
from 0 to 65535. In general,
select the default value. The
corresponding self-loop PCM
number is required in case of
configuring a self-loop office.
NAME
Alias
MGWPCM
Example: Create a PCM system to the BSC office with the following requirements:
No. of the trunk group where the PCM system belongs: 99
PCM system No.: 1
User alias: BSC1-1.

ADD SPCM:TG=99,PCM=1,NUM=3,MGWPCM="4"-"6",INF
O=65535,NAME="BSC1-1";
END OF STEPS
158
Creating an SCTP
Prerequisites
The physical configuration of the SMP module is complete.
The range of the SCTP ID is configured in the resource management configuration.
Context
The configuration of SCTP basic connection is used to configure

the basic information of the SCTP association.
Steps

system tree.
SET:NEID=11;
2. Create the SCTP connection. The command is ADD SCTPCO
NN.
Table 78 describes the parameters in the ADD SCTPCONN
command.
Parameter Name
MODULE
OFCID
Parameter
Description
Instruction
Module No.
indicating the number of the
signaling module homed by this
SCTP association. Select the SMP
module number. Each SMP can
support up to 128 associations.
The associations under the same
AS are required sharing load
on SMP modules as more as
possible.
SCTP opposite
office ID
designating the office No. of the
direct-associated association.
Type the MGW adjacent office No.
specified in the adjacent office
configuration.
159
Parameter Name
Parameter
Description
Instruction
Bearer protocol
types, including
PROT
M2UA
M2PA
M3UA
SUA
H248
BICC
IUA
DHCTRL
SIP
DIM
V5UA
H245
SCTP application
attributes.
Options include:
ROLE
SVR: SCTP is
used as server
CLT: SCTP is used
as client
used to identify the upper-layer
protocol type borne by the SCTP
association. In general, M3UA is
selected.M2UA is selected when
MGW transfers the signaling with
the M2UA mode.
It is a mandatory parameter. For

Mc interface, MSCS is configured
as CLT, and MGW is configured
as SVR. For Nc interface, this
should be negotiated by both
sides. For example, the small
signaling point serves as CLT,
and the big signaling point serves
as SVR
designates the service address
of local end of this association,
with a format of Local IP
address type-VPN of local IP
address-Local IP address
LOCADDR
Local IP address
Local IP address type: IPv4 and

IPv6;
VPN of local IP address: Rang
from 0 to 65535;
Local IP address: the format is
xxx.yyy.zzz.mmm
160
LOCPORT
Local port
number
is the local SCTP port number of
the association, ranging from 1
to 65535.
REMADDR
Opposite IP
address
designates the service address of
opposite end of this association,
REMPORT
Opposite port
number
the opposite SCTP port number
of the association, ranging from
1 to 65535.
Parameter Name
Parameter
Description
Instruction
NAME
Alias

characters.
SCTP ID
the global serial number of the
SCTP association, ranging from 1
to 2048. Configure it according
to the association planning.
ID

MGW office ID: 101

001,NAME="BSC",ID=3,INSTRM=16,OUTSTRM=16,MAXR
TRY=5,MAXRTO=500,MINRTO=50,INITRTO=100,HB=50
0,FIXNH=NO,SCTPMAXRTRYNUM=10,DELAYACK=20,MA
XBURST=4,PRIMARYPATH=REMIP1,PMTU=0,BREAKTIM
E=0,PDTHRESH=0,MINCWND=0,PLTIMER=10,MPPLTHR
D=2,DPLEN=MTU,CB=200;
END OF STEPS
Creating an ASP
Prerequisites
Context
The SCTP association information is configured.
The range of the ASP ID is configured in the resource management configuration.
ASP configuration defines the one-to-one relationship between the

ASP and the association.
161
Steps

system tree.
SET:NEID=11;
Table 79 describes the parameters in the ADD ASP command.
Parameter
Name
Parameter
Description
Instruction
ASSOCID
NAME
ID
SCTP ID
Alias
ASP ID
ISLOOP
ASP self-loop ID
Type the association ID

configured in the SCTP
connection configuration.
with a lengthen ranging from
1 to 50 characters. It may
be named with a format of
Adjacent office alias-SCTP
number.
It is recommended to be
consistent with ASSOCID.
used to set whether the ASP is
self-looped.
ISLOCK
ASP blocking flag
used set whether the ASP is in
blocking state.
Blocking is used for
management. Select the
default value NO
Example: Create the ASP between MSCS and MGW with the
MGW office ID: 101
User alias: SCCP.
162
ADD ASP:ASSOCID=3,NAME="SCCP",ID=3,ISLOOP=NO,I
SLOCK=NO;
END OF STEPS
Creating an AS
Prerequisites
The ASP configuration is complete.
Context
AS configuration is used to configure the basic information for the

application server.
Steps

system tree.
SET:NEID=11;
2. Create an AS. The command is ADD AS.
Table 80 describes the parameters in the ADD AS command.
TABLE 80 AS PARAMETERS
Parameter
Name
Parameter
Description
Instruction
PROT
Adaptation layer
protocol
It is a mandatory
parameter. It is required
to be consistent with that
at the adjacent office side.
Configure it according to
the actual conditions. In
general, select M3UA.
ASPID
ASP ID

ASP configuration.
Alias
It is a mandatory
parameter, which is
customized by the user
for easy recognition.
AS ID
It is an optional
unique ID of the AS. In
memory.
NAME
ID
163
Parameter
Name
Parameter
Description
Instruction
If routing context
exists, including:
NO: Routing
context does not
exist
YES: Routing
context exists
EXISTCTX
This parameter must

opposite-end.
CTXID
Routing context ID
It is an integer parameter.
If the YES (Routing
context exists) option
is selected for the
EXISTCTX parameter,
this parameter must
opposite-end.
ASTAG
Usage tag
In this case, select CLT

(IPSP Client).
ASUP
User types
It is an optional
parameter. In this case,
select SCCP.
Service mode,
including:
ASMD
OVERRIDE
(Over-ride mode)
LOAD (Load share

mode)

only one ASP is activated.
In this case, only one ASP
needs to be configured. In
the load sharing mode, N
to be in activated working
status, and K ASPs should
be configured to be in
deactivated standby
status. Make sure that
the value of N+K is not
ASPs actually configured.
negotiated between both
ends for consistency.
It is an integer parameter,
NVAL
N value of load share

mode
N+K should be equal

to the number of ASPs
configured under this AS.
N indicates that this AS
is in service as soon as N
ASPs are in service.
It is an integer parameter,
KVAL
K value of load share

mode
N+K should be equal

to the number of ASPs
configured under this AS.
K indicates that this AS is
out of service as soon as
K ASPs are out of service.
164
Example: Create the AS between MSCS and MGW with the

AS ID: 3
Supported user type: SCCP
ASP ID: 3
Client: MSCS
Alias: BSSAP

ADD AS:PROT=M3UA,ASPID="3",NAME="BSSAP",ID=3,E
XISTCTX=NO,ASTAG=CLT,ASUP="SCCP",ASMD=LOAD,NV
AL=1,KVAL=0;
END OF STEPS

Prerequisites
The AS configuration is complete.
The range of M3UA static route ID is configured in the resource

management.
Context
Configuring an M3UA static route means configuring the mapping

relationship between an M3UA static route and an AS.
Steps

system tree.
SET:NEID=11;
command.
Parameter
Name
Parameter
Description
Instruction
ID
ID of M3UA
static route
as the AS ID.
ASID
AS ID
165
Parameter
Name
Parameter
Description
Instruction
MODE
Alignment
mode of
routes.
Options
include
BYTURNS
LOCAL
NATURE

Nature option.
the activated ASP
NAME
Alias


AS ID: 3
User alias: SCCP.

ADD M3UART:ID=3,ASID=3,MODE=BYTURNS,NAME="SC
CP";
END OF STEPS

Prerequisites
Context
The M3UA static route configuration is complete.
Where, a routing keyword describes the parameters and their values of a group of No.7 signaling messages. The corresponding AS
is selected according to the message attributes, serving the purpose of selecting route for messages. The attribute of the message
includes DPC+NET+OPC+SIO, where, DPC is the destination signaling point code, NET is the network type, OPC is the originating
signaling point code, and SIO is the service indicator octet.
to a routing table that is maintained by the ASPs under the AS.
166
signaling, the ASP configuration of the SCTP connection and M3UA

is similar to the link logic and bearer information configuration in
the MTP configuration, the AS configuration of the M3UA is similar
to the link set configuration in the MTP configuration, and the SIOlocating-AS configuration is similar to the signaling office ID and
route configuration in the MTP configuration. The difference is that
the IP route to one subscriber of one office is configured in one
SIO-locating-AS configuration record.
Steps

system tree.
SET:NEID=11;
Table 82 describes the parameters in the ADD SIOLOCAS
command.
Parameter Name
Parameter
Description
Instruction
ID
SIO-locating-AS ID
indicating the serial number
of SIO-locating-AS, ranging
from 1 to 4096. In general,
it is the same as the AS ID.
NAME
The name of the

SIO-locating-AS
It is customized by users for

identification.
OFCID
Destination office ID
The ID of the adjacent

office corresponded by the
destination signaling point
of M3UA. It corresponds
to the adjacent office
ADJOFC command.
SIO
Service indication
Select SCCP.
RT1
M3UA static route ID 1
It is the static route ID

configured by the ADD
M3UART command.
Example: Create SIO-locating-AS between MSCS and BSC with

BSC office ID: 99
Destination adjacent office ID: 99
Service indication: SCCP
167
ADD SIOLOCAS:ID=3,NAME="SCCP",SIO=SCCP,OFCID=9
9,OPOFCID=65535,PCM=65535,RT1=3,RT2=0;
END OF STEPS
RNC Data Configuration

Overview
Typical
Networking
In the R4 phase, the interface between the RNC and the CS domain
uses the ATM bearer, and the MSCS processes the control plane
of the Iu_CS interface. The signaling is based on the AAL5 and
is transmitted by the SCCP. MGW processes the user plane and
the bearer control plane of the Iu-CS interface. The user data
are based on the AAL2, and transferred on the AAL2 connection.
The ALCAP controls the establishment and release of user plane
connections. In the existing networks, the signaling interworking
between the MSCS and the RNC is implemented by the built-in SG
(SG) in the MGW. Figure 10 shows the networking mode and the
interface protocol stack.
FIGURE 10 NETWORKING BETWEEN MGW
AND
RNC
The ATM bearer is used between the MGW and the RNC, and the
IP bearer is used between the MGW and MSCS. Working in the
switching mode, the built-in SG in the MGW performs the signaling
switching between the MSCS and the RNC.
Data Collection
168

the related data of MSCS-to-MGW, and MGW-to-RNC. Table 83 and
Table 84 list the data to be collected. The parameter values are
TABLE 83 DATA
INTERCONNECTION
WITH THE
MGW
Parameter Items
Parameter Values
192.168.1.11
192.168.1.31

MSCS
1.11.1

MGW (SG)
1.31.1
4001
4001
TABLE 84 DATA
FOR
FOR
INTERCONNECTION
WITH THE
RNC
Parameter Items
Parameter Values
The type of the local signaling point
14-bit
SPC of the local office
1.100.1
RNCID
Location area code
12FB
Service area code
AMR codec rate (newly added)
122
ATM address/coding type (the coding

type is NSAP)
00.00.00.00.00.00.00.00.0
0.00.00.00.00.00.00.00.00
.00.00.06
MCC+MNC
46007
Path ID
Signaling link code (SLC) in a signaling

link set

adding a RNC adjacent office under the precondition that the MGW
is successfully registered to the MSCS, including the configurations
of signaling-forwarded data to and through the RNC. Table 85 describes the configuration flow.
169
TABLE 85 RNC ADJACENT OFFICE DATA CONFIGURATION FLOW

Steps
Operations
Related Command
Creating a RNC adjacent

office
ADD ADJOFC
Creating RNC office

direction
ADD RNCOFC
Creating a RNC topology

node
ADD TOPO
Creating the topology

relationship between RNC
and MGW
ADD RNCMGWTOPO
Creating an ATM trunk

group
ADD TG ATM
Creating a PCM system
ADD SPCM
ADD SCTPCONN
Creating the associations

and the M3UA data switched
by the signaling
ADD ASP
ADD AS
ADD M3UART
Creating the SIOLocating-AS
ADD SIOLOCAS
Creating an RNC Adjacent Office

Prerequisites
Context
Perform this procedure for configuring the basic information of the

RNC adjacent office.
Steps

system tree.
SET:NEID=11;
2. Create the RNC adjacent office. The command is ADD ADJO
FC.
command.
170

Parameter
Name
Parameter
Description
Instruction
ID
Office ID
number of the adjacent office,
and ranging from 1 to 2048.
It is usually configured as the
exchange ID of the adjacent
office during the all-network
planning.
NAME
Alias
by the user.
NET
Network type
office when the local office is
configured with several SPs.
The default is the network type
of this SP when there is only
one SP in the local office.
OFCTYPE
Adjacent office type
SPCFMT
SPC format
Select TRIPLE_DEC
SPCTYPE
SPC type
Specify it based on the SPC
type of the adjacent office
DPC
SPC
RC
Area code
Type RNC in this case
When the adjacent office type

is RNC, RC must be empty.
Association type,
including
ASSOTYPE
AM_SURE
(direct
connection
mode)
AM_QUASI
(half direct
connection
mode)
Select AM_QUASI
AM_NONE
(none
connection
mode)
171
Parameter
Name
Parameter
Description
Instruction
Signaling point
type, including
SPTYPE
SEP
STP
STEP
Select SEP
Subservice
function, including
INTERNATIONAL (International signaling point

code)
INTERNATIONAL
STANDBY
(International
standby signaling point code)
SSF
TEST
NATIONAL
(National
signaling point
code)
NATIONAL
STANDBY
(National
standby
signaling point
code)
Test flag
general, select NATIONAL for
domestic use.
It is an optional parameter, for

setting whether the MTP3 link
actively initiates the link test
after entering in the service
status.
It is selected by default.
BANDFLAG
Broadband
attribute
Select YES when all the links
between two SPs are SIGTRAN
or ATM signaling links.
Protocol types,
including:
CHINA (China)
ITU (International Telecommunications

Union)
ANSI
(American
National
Standards
Institute).
PRTCTYPE
172
CHINA and ITU are used for
the NO.7 signaling networking
of the ITU standards. ANSI
is used for the No.7 signaling
networking of the American
standards.
Parameter
Name
CLST
Parameter
Description
Instruction
Cluster ID
The cluster number should
be configured in ADD CLST.
65535.
Office Info,
including:
CIC_PCM (CIC
starts the
load sharing
according to
the PCM code
mode)
BLOCK
(Manual block
status)
EVEN_CIC
(The office
controls the
even CIC when
CIC resource
contention
occurs)
INFO
RELATEDOFC1
CALLING(Calling
transform is allowed)
CALLED
(Called
transform is
allowed)
MOD24_CIC
(CIC mode with
24 mode)
TEST
(Dynamic test)
Related office ID
with a default of CIC_PCM
(CIC using PCM Code Mode
Starts Load Control)
ranging from 0 from 3000
Office extend info,

including
INFOEX
SIGBRDCST
(Support
Signaling
Broadcast
Message)
MTP
(Hongkong
MTP Standard)
DUPU (
Screen DUPU
message)
173
Parameter
Name
Parameter
Description
SUA_REC_
DT1 (Receive
SUA message
and handle it as
DT1 message)
SUA_SND_DT1 (Send
SUA message
and handle it as
DT1 message
without SN.)
OPEN_TG_RES (Open
outter trunk
group resource)
Instruction
Example: Create an RNC adjacent office with the following requirements.
RNC office ID: 100
Network type: 2
User alias: RNC100
SPC type: 14-bit
Adjacent office type: RNC
Association type: Quasi-associated mode.

ADD
ADJOFC:ID=100,NAME="RNC100",NET=2,OFCTYP
E="RNC",SPCFMT=TRIPLE_DEC,SPCTYPE=14,DPC="1.10
0.1",ASSOTYPE=AM_QUASI,SPTYPE=SEP,SSF=NATIONAL
STANDBY,SUBPROTTYPE=DEFAULT,TEST=YES,BANDFLAG
LATEDOFC1=0;
END OF STEPS
Office Direction and Topology

Configuration
Creating RNC Office Direction
Prerequisites
174
The RNC adjacent office is created.
Context
Perform this procedure to configure some additive attributes of the

RNC adjacent office, thus to associate the RNCID with the RNC
office.
Steps

system tree.
SET:NEID=11;
2. Create the RNC office direction. The command is ADD RNCO
FC.
Table 87 describes the main parameters in the ADD RNCOFC
command.
TABLE 87 PARAMETERS IN THE ADD RNCOFC COMMAND
Parameter
Name
Parameter
Description
Instruction
OFCID
RNC office ID
It is the RNC office ID

specified in the RNC office
configuration.
MCC
Mobile country code
ranging from 1 to 4
characters. For China,
it is 460.
MNC
Mobile network code
to 3 characters.
RNCID
RNC ID
provided by the RNC side.
RABDLY
RAB Delay(ms)

100
Class A SDU Error

Ratio. The options
include:
ERRRATIO1
(1*10^(-2)
ERRRATIO2
(7*10^(-3)
SDUERA
ERRRATIO3
(1*10^(-3)
ERRRATIO4
(1*10^(-4)
ERRRATIO5
(1*10^(-5)

ERRRATIO2 (7*10^(-3)
175
Parameter
Name
Parameter
Description
Instruction
Class A Residual BER.

The options include:
ERRRATIO1
(5*10^(-2))
ERRRATIO2
(1*10^(-2))
ERRRATIO3
(5*10^(-3))
ERRRATIO4
(1*10^(-3))
ERRRATIO5
(1*10^(-4))
ERRRATIO6
(1*10^(-5))
ERRRATIO7
(1*10^(-6))
RBERA

ERRRATIO7 (1*10^(-6))
Class B Residual BER.

ERRRATIO1
(5*10^(-2))
ERRRATIO2
(1*10^(-2))
ERRRATIO3
(5*10^(-3))
ERRRATIO4
(1*10^(-3))
ERRRATIO5
(1*10^(-4))
ERRRATIO6
(1*10^(-5))
ERRRATIO7
(1*10^(-6))
RBERB

ERRRATIO4 (1*10^(-3))
Class C Residual BER.

ERRRATIO1
(5*10^(-2))
ERRRATIO2
(1*10^(-2))
ERRRATIO3
(5*10^(-3))
ERRRATIO4
(1*10^(-3))
ERRRATIO5
(1*10^(-4))
ERRRATIO6
(1*10^(-5))
ERRRATIO7
(1*10^(-6))
RBERC
176

ERRRATIO3 (5*10^(-3))
Parameter
Name
Parameter
Description
Instruction
Iu Interface Load
Share Mode. The
options include:
SELMGTYPE
ATMADDR
ADDRPLAN
EXCELLENT(Excellent choice
priority)
LOAD(Load share
priority)
RNC ATM Address
ATM Address
Plan, including
E.164(E.164) and
NSAP(NSAP)

EXCELLENT (Excellent
choice priority)
Configure the ATM address
and coding plan of the
corresponding RNC.
ATM address code can adopt
the NSAP that has a fixed
length of 20 bytes) or E.164
(that is an extendable BCD
code).
The configuration here
should be consistent with
the RNC office ID parameters
at the MGW side.
First Rebear Mode.

BTRY1
NO(NO RETRY);
BEARER(TRY
OTHER REBEAR
MODES;
MGW(TRY OTHER
MGW)
The default is NO(NO

RETRY)
Second Rebear Mode.

BTRY2
RAS
NO(NO RETRY);
BEARER(TRY
OTHER REBEAR
MODES;
MGW(TRY OTHER
MGW)
RNC Office
ReAssignment.
Options include:
NO(NO);
YES(YES)
The default is NO(NO

RETRY)
The default value is NO(NO)
Example: Create the RNC office direction with the following

requirements.
RNC office ID: 100
177
RNC ID: 1
ATM address of RNC: 12.3456.7890.abcd.efff.ffff.ffff.ffff.ffff.ffff.ff

ATM address plan: E164.

ADD RNCOFC:OFCID=100,MCC="460",MNC="00",RNCID
=1,RABDLY=100,SDUERA=ERRRATIO2,RBERA=ERRRATI
O7,RBERB=ERRRATIO4,RBERC=ERRRATIO3,SELMGTYPE
=EXCELLENT,ATMADDR="12.3456.7890.abcd.efff.ffff.ffff.fff
f.ffff.ffff.ff",ADDRPLAN=E164,BTRY1=NO,BTRY2=NO,RAS
=NO;
END OF STEPS
Creating an RNC Topology Node

Prerequisites
The voice CODEC template is created.
Context
Perform this procedure to create the adjacent NE information, including equipment type, bearer type and attributes, user plane
version, encoding and decoding template, and other information.
Steps

system tree.
SET:NEID=11;
2. Create an RNC topology node. The command is ADD TOPO.
Table 88 describes the main parameters in the ADD TOPO
command.
Parameter
Name
178
Parameter
Description
Instruction
ID
Topological
node ID
ranging from 1 to 2,048. It is used
for defining a topological node. It
is recommended that this ID is
consistent with the office ID of this
node.
OFCID
Office ID
for specify the office ID of this
topological node, ranging from 1
Parameter
Name
Parameter
Description
Instruction
to 3,000. This parameter must
be defined by the ADD ADJOFC
command first. Type the RNC office
ID according to actual conditions.
NAME
CODECID
Alias
CODEC
identity

naming this topological node, with
characters.
for specifying the Encoding and
decoding speech Template used
by this topological node. This
parameter must be defined by the
ADD CODECTPL command first.
conditions.
ETYPE
Equipment
type

specifying the NE type of this
topological node.
Select RNC for an RNC node.
IPVER
IP version of
the node
indicating the IP protocol version
supported between nodes. Select
IPV4 or IPV6 according to the
actual conditions. In general, it is
set as IPV4
ATTR
Bearer
attributes
This parameter is only valid for

the node with the type of R4GW
(MGW). You need not to configure
it for an RNC topology node.
UPVER
User plane
protocol
version
It is an optional parameter to
regulate the user plane version
of this node, ranging from V1
to V16. It can support one or
more of these user plane versions.
This parameter is only valid for
RNC-type or MGW-type NE.
In general, V2 is selected (meaning
supporting Version 2) according to
the user-plane version supported
by RNC.
Extended
attributes
(tunnel
mode),
including
NOTUNL
(None
tunnel
mode)
RTUNL
(Rapid
tunnel
mode)
ATTR2
This parameter sets which tunnel

mode is used for setting up a
bearer when this node supports
the IP/RTP bearer, with a default of
NOTUNL (None tunnel mode).
179
Parameter
Name
Parameter
Description
TRFMOD
Instruction
DTUNL
(Delay
tunnel
mode)
Transmission
mode,
including
MCINTF (Mc
interface
signal transfer
mode)
This parameter is used to set that

mode used by the topology for
reporting the detected CNG or
CED fax signals, with a default
of MCINTF (Mc interface signal
transfer mode).
YES: The user plane entity
implements error inspection, and
sets the FQC bit position according
to the result. It will transmit all
frames includes the error frames to
the user plane layer. During a call,
the error packet control parameter
delerrsdu=Yes, which is delivered
UPERRCTRL
Error SDU
control
NO: The user plane entity

implements the error inspection.
It will directly discard the error
frame. During a call, the
delerrsdu=No, which is delivered
INVALIDTION: The user plane
entity does not implement the
error inspection. During a call,
the error packet control parameter
delerrsdu=NA, which is delivered
deliveryOfErroneousSDU is NA, NA,
NA during RAB assignment.
plane for error frames. It is only
valid for MGW-type and RNC-type
topological node. The default value
is YES
180
Parameter
Name
Parameter
Description
DTMFTC
Tandem office
send DTMF
use TC mode,
containing two
options: No
and YES
Instruction
whether the tandem office uses the
TC resources during DTMF number
delivery.
It contains the following options.
MGWCON
MGW
congestion
reporting
capability
SMGWCON (Standard MGW

congestion event)
CMGWCON (Custom MGW

congestion event).
The default value is SMGWCON.
Example: Create a topology node with the following requirements.
RNC office ID: 100
Topology node ID: 100
Alias: RNC100
CODEC ID: 1
RNC-supported user-plane version: V2.

ADD TOPO:ID=100,OFCID=100,NAME="RNC100",CODEC
ID=1,ETYPE=RNC,PROTTYPE=H248,DMNAME="RNC",IP
VER=IPV4,UPVER="V2",ATTR2=NOTUNL,TRFMOD=MCINT
F,UPERRCTRL=YES,DTMFTC=NO,MGWCON=SMGWCON,A
UTOFAX=YES,OOBTC=NO,BCUID=0,SENDCAP=NO,G711
TRAN=NO,BICCDTMF=TRANSPARENT,IPBCP2833=BYMG
W,BICCDTMPPER=0,AOIPPRO=PRIVATE;
END OF STEPS
Creating the Topology Relationship between RNC

and MGW
Prerequisites
The RNC topology node is created.
Context
Perform this procedure to configure the topological relationship

between RNC and MGW, thus to associate the MGW node with the
RNC node.
Steps

181

system tree.
SET:NEID=11;
2. Create the topology relationship between RNC and MGW. The
command is ADD RNCMGWTOPO.
Table 89 describes the main parameters in the ADD RNCMG
WTOPO command.
TABLE 89 PARAMETERS IN THE ADD RNCMGWTOPO COMMAND
Parameter
Name
Parameter
Description
Instruction
MGWID
MGW node ID
RANTYPE
Office type
RANID
RNC/BSC node
number

during the MGW topological
node configuration
Select RNC for RNC access.
during the RNC topological
node configuration.
Load Sharing
Mode, including:
SHMODE
NONE (NOT
Load Sharing)
BEARLOAD
(Bear Load
Sharing)
MBLOAD
(MasterBackup Load
Sharing)
Bearer Type 1,
including:
BTYPE1
BRATIO1
ATM (ATM)
IP (IP)
Bearer Type 1
Ratio
Bearer Type 2,
including:
BTYPE2
182
NONE (NONE)
ATM (ATM)
IP (IP)

set the multiple load sharing
modes, with a default of
NONE
The parameter indicates

the first bearer type, with a
default of ATM
The parameter is used to the
set the proportion of the first
bearer type, with a default of
1

default of NONE
Parameter
Name
Parameter
Description
Instruction
BRATIO2
Bearer Type 2
Ratio

the set the proportion of the
default of 1
BPER
Ratio of bearer
from MGW to RNC
NAME
Alias
It is used for setting the

traffic load-sharing ratio
when the RNC accesses
several MGWs. If the RNC
only connects to one MGW,
this parameter is set as 1 by
default
to 50 characters.
Example: Create the topology relationship between RNC and

MGW with the following requirements.
MGW node ID: 101
RNC node ID: 100.

ADD RNCMGWTOPO:MGWID=101,RANTYPE=RNC,RANI
D=100,SHMODE=NONE,BTYPE1=ATM,BRATIO1=1,BTYPE
2=NONE,BRATIO2=1,BPER=1;
END OF STEPS
Trunk and PCM Configuration

Creating an ATM Trunk Group
Prerequisites
The trunk group No. range is set in the resource management

system.
The adjacent MGW office to which the trunk group points is

created.
Context
When the ATM bearer is adopted between MGWs, configure ATM

trunk groups.
Steps

183

system tree.
SET:NEID=11;
2. Create an ATM trunk group by executing command ADD TG
ATM.
The explanation of the main parameters in command ADD TG
ATM is shown in Table 90.
TABLE 90 PARAMETERS IN THE ADD TG ATM COMMAND
Parameter
Name
TG
OFC
NAME
MODULE
ND
184
Instruction
Trunk group ID
It is a mandatory
to define an ATM trunk
group, and needs to be
planned in the resource
management system in
advance. It is a global
unified number

the trunk group belongs
It is a mandatory
parameter, ranging
from 1 to 256. It is
used to specify the
corresponding office of
the trunk group. This
parameter must be
defined by command
ADD ADJOFC at first.
here
User alias
It is an optional
of 0~50 characters.
describe a trunk group to
make it easily recognized
Module where the trunk

group belongs
It is a mandatory
parameter, which is
an integer, ranging from
1 to 127. It is used to
specify the SMP module
of processing traffic on
this trunk group
Node No. of the MGW

belongs
It is a mandatory
parameter, which is
1~2048. It is used to
specify the topology
node No. of the MGW
providing bearer, which
is controlled by the local
MGCF
Parameter
Name
Instruction
SIGLINE

identification, including
BICC (BICC signaling)
It is an optional
identify the line type of
this trunk, with a default
of BICC
Trunk group types,

three types:
IN (incoming trunk
the local office processes
the incoming calls from
the peer-end office.
KIND
OUT (outgoing trunk

office.
BIDIR (Two-way trunk
the local office processes
both the incoming calls
from the peer-end office
and the outgoing calls to
the peer-end office
It is an optional
to specify the call
connection direction
in this trunk group in
the local office, with
a default of BIDIR. It
should be negotiated
with the peer-end office
NODIR (No direction):
The inter-office bearer
is established without
direction.
BWAY

mode.
It is an optional
specify the inter-office
bearer establishment
direction, with a default
of NODIR
FORWD: The
inter-office bearer is
established based on the
forward mode
THD
Overload control
threshold
It is an optional
of 100. This parameter
takes effect when levels
of congestion occur and
load control is required
185
Parameter
Name
Instruction
Circuit selecting modes,

including:
with the minimum
with the maximum
CICSLTP

the system selects
a trunk circuit, it
always begins with
the circuit next to the
one previously selected.
Suppose the numbers
of the trunk circuits in a
trunk group in ascending
order are TKC0, TKC1,
. , TKCn. If TKC0
is selected at the first
select the trunk circuit in
the order of TKC0TKC
1TKCnTKC0TK
C1TKCn.
an odd number.
EVEN: Every time when
an even number.
IDLE: Every time when
selects the idlest circuit.
BUSY: Every time when
selects the busiest circuit
186
It is an optional
specify the trunk circuit
selecting policy of the
system within this trunk
group, with a default
of CYC. If this trunk
group is a two-way
trunk group, it is
recommended to set the
circuit selecting mode
to ODD/EVEN mode to
prevent contention when
two exchanges select
circuits
Parameter
Name
DAS
SIPDAS
OPDAS
PREDAS
DDI
OPDDI
MINNAT
Instruction
DAS for the called

number
It is an optional
to analyze the called
number in an incoming
call. This parameter
must be defined by
command ADD DAS at
first. Then it can be
indexed here
DAS for the domain

name of the called
number during SIP
outgoing calls
It is used get the name

of the IMS domain
where the called party
is located through
analyzing the called
number during a SIP
outgoing call. It is
only used for RTP trunk
groups
DAS for the calling

number
the calling number in
parameter must be
defined by command
ADD DAS at first. Then
DAS for pre-analyzing

the called number
It is used to pre-analyze
parameter must be
defined by command
ADD PREDAS at first.
here
Incoming called number

transform ID
It is the index of
the incoming called
parameter must be
defined by command
Incoming calling number

transform ID
It is the index of
the incoming calling
parameter must be
defined by command
Minimum national
number length
It is an optional
parameter, which is an
integer ranging from 0 to
26, with a default of 0.
minimum digit length of
the called number during
a national incoming call
187
Parameter
Name
MAXNAT
MININT
MAXINT
INREG
Instruction
Maximum national
number length
It is an optional
maximum digit length of
the called number during
a national incoming call
Minimum international
number length
It is an optional
minimum digit length
of the called number
during an international
incoming call
Maximum international
number length
It is an optional
maximum digit length
of the called number
during an international
incoming call
Incoming register
signaling flag. Options
include:
INVALID
OUTREG
Outgoing register
signaling flag. Options
include:
INVALID
COLEN
BUSYRATE
188
It is an optional
value of INVALID
It is an optional
value of INVALID
The maximum length of

CAS calling number end
It is an optional
default of 10.
Trunk circuit usage
It is an optional
parameter, which is
an integer ranging
default of 100. After
the trunk circuit usage
is configured, when the
ratio of busy circuits
to all circuits in this
trunk group exceeds this
value, congestion occurs
in this trunk group.
After the congestion
is relieved, report the
trunk congestion times
and congestion duration
in the performance
statistics. This
Parameter
Name
Instruction
parameter does not
take effect when it is
configured to 100
ROAMDAS
DAS for roaming

numbers
It is an optional
parameter. After this
DAS is configured, if
the local office serves
as a GMSC, this DAS
is preferred for the
returned roaming
numbers. Otherwise,
the roaming number
DAS configured in
the number analysis
template is used
Q850CCIDX
Q850 customization
index
It is an optional
default of 0.
ID of signaling
modification entrance
IIt is an optional
parameter, associated
with the inter-office
signaling modification
entrance. It ranges
default of 0
SMENTERID
Example: Create an ATM trunk group with the following requirements.
Trunk group ID: 100
User alias: RNC
No. of the module processing the trunk group: 3
Inter-office line signal identification: BICC
The command is:

ADD TG ATM:TG=100,OFC=100,MODULE=4,ND=101,NA
ME="RNC",SIGLINE=BICC,KIND=BIDIR,BWAY=NODIR,TH
D=100,CICSEL=ODD,DAS=0,SIPDAS=0,OPDAS=0,PRED
AS=0,DDI=0,OPDDI=0,MINNAT=0,MAXNAT=26,MININT
END OF STEPS
189

Prerequisites
The ATM trunk group is configured.
Context

Steps

system tree.
SET:NEID=11;
Parameter
Name
Parameter
Description
Instruction
PCM
TG
PCM-belonged trunk group ID
Number
100. In general, select the default
value.
MGW PCM
number
consisting of MGWPCM_S and
MGWPCM_F. The start and end
numbers of the MGW PCM mean
that the trunks corresponded by
PCM resources of this number
section can be invoked. This
parameter is left blank when the
PCM-belonged trunk number is an
interoffice BICC.
INFO
Self-loop PCM
number
It is an optional parameter, with a

default of 65535. Enter an integer
ranging from 0 to 65535. In
general, select the default value.
The corresponding self-loop PCM
number is required in case of
configuring a self-loop office.
NAME
Alias
NUM
MGWPCM
Example: Create a PCM system to the RNC office with the following requirements:
190
No. of the trunk group where the PCM system belongs:

100
PCM system No.: 1
User alias: RNC.

ADD SPCM:TG=100,PCM=1,NUM=3,MGWPCM="7"-"9",IN
FO=65535,NAME="RNC";
END OF STEPS
191
192
Chapter
Access Data
Configuration
Table of Contents
Overview........................................................................ 193
Creating Emergency Call Center ........................................ 194
Special Serivce Configuration ............................................ 196
LAI and GCI/Service Area Configuration.............................. 201
Overview
Description
This chapter describes how to configure the location area and the
cell data on the MSCS. When a base station is added on the radio
side, the corresponding cell data need to be configured on the
MSCS. When the adjacent MSC is added on the network side, the
adjacent location area data need to be configured on MSCS for the
proper handover between the offices.
When the MSCS is interconnected with the BSC, the special service number dialed in different cells requires to converting to different numbers for connection. When the MSCS is interconnected
with the RNC, the special service number dialed in different cells
possibly also requires conversion. Therefore, configuring different
special service attendant consoles and special service group data
is required.
Configuration
Flow
Table 92 describes the access configuration flow.

TABLE 92 ACCESS CONFIGURATION FLOW
Steps
Operations
Related Command
Creating emergency call center
ADD ECC
Creating a special-service
phone group
ADD SSPN
Creating the special service

phone called number analysis
ADD TPDNAL
Creating a LAI controlled by

the local office
ADD LAI
Creating an adjacenet LAI
ADD LAI
193
Steps
Operations
Related Command
Creating a global cell
ADD GCI
Creating a service area
ADD SAI
Creating Emergency Call

Center
Prerequisites
Context
The emergency call function does not analyze the emergency call
number. After the subscriber dials a specified emergency call number in one location area, the core network will obtain the emergency call center index according to the location area where the
emergency call is received. After that, it will find the corresponding number of the emergency call center number according to the
the emergency call center index, and then analyze this number.
This topic describes how to create emergency call center.
Steps

system tree.
SET:NEID=11;
2. Create emergency call center with the command ADD ECC.
The explanation of the main parameters in command ADD ECC
is shown in Table 93.
TABLE 93 PARAMETERS IN THE ADD ECC COMMAND
Parameter
Name
Instruction
ECC
Emergency Call Center

Number
It is a mandatory
of 1~32 digits
ECCIDX
Emergency Call Center

Index
It is an optional
parameter, which is
0 to 255
Emergency Call Service

Type, including
SERVTYPE
194
DFT: Default
Emergency Call
Center Number
It is an optional
parameter with the
default value DFT
Chapter 2 Access Data Configuration
Parameter
Name
POLICE: Police
Emergency Call
Center Number
AMBULANCE:
Ambulance
Emergency Call
Center Number
FIRE: Fire-fighting
Emergency Call
Center Number
MARINE: Marine
Emergency Call
Center Number
MOUTAIN: Mountain
Area Emergency Call
Center Number
Instruction
Configuration Number
Type, including
UNKNOWN:
Unknown
INTERNATIONAL:
International
NATIONAL: National
SPECIAL: Special
Number Of The
Network
SHORT: Abbreviated
Number
NAT
NAME
Alias
It is an optional
parameter withe
the default value
UNKNOWN
It is an optional
of 0~50 characters
For example, create the emergency call center. The emergency

call number is 112, the emergency call center index is 1, the
emergency call service type is DFT, the configuration number
type is international, and the alias is Emergency1. The command is as follows:
ADD ECC:ECC="112",ECCIDX=1,SERVTYPE="DFT",NAT=I
NTERNATIONAL,NAME="Emgergency1";
END OF STEPS
195
Special Serivce
Configuration
Creating a Special Service Phone
Group
Prerequisites
Context
In the case of the MSCS being connected with the BSC, when you
dial a special-service number in different cells, it is required to
convert this number to different numbers for connection.
In the case of the MSCS being connected with the RNC, when you
dial a special-service number in different service areas, it is also
required to convert this number to different numbers for connection.
Therefore, different special-service attendant consoles need to be
configured.
Steps

system tree.
SET:NEID=11;
2. Create a special service phone group with the command ADD
SSPN.
The explanation of the main parameters in command ADD
SSPN is shown in Table 94.
TABLE 94 PARAMETERS IN THE ADD SSPN COMMAND
Parameter
Name
196
Parameter
Description
Instruction
SSPGID
Special
Service
Phone Group
ID
which is an integer, ranging form
1 to 65535. It is associated with
the special-service phone group
ID in the special-service group
configuration, exclusively defines an
attendant console together with the
special-service number
SSPGNAME
Special
Service
Phone Group
Name
It is an optional parameter, consisting

of 0~50 characters. It is used to
identify a special-service group
Parameter
Name
SSNUM 1
PNUM1
SSNUM 2
PNUM2
SSNUM 3
PNUM3
SSNUM 4
PNUM4
Parameter
Description
Instruction
Special
Service
Number 1

is an integer, ranging form 1 to
2147483647. It is the special-service
number, such as 114. It exclusively
defines an attendant console together
with the special-service traffic group
ID
Phone
Number 1
indicating the phone console number
corresponding to the special service
phone group ID and the special
service number. It ranges from 0 to
40
Special
Service
Number 2

ID
Phone
Number 2
40
Special
Service
Number 3

ID
Phone
Number 3
40
Special
Service
Number 4

ID
Phone
Number 4
40
197
Parameter
Name
SSNUM 5
PNUM5
SSNUM 6
PNUM6
SSNUM 7
PNUM7
SSNUM 8
PNUM8
198
Parameter
Description
Instruction
Special
Service
Number 5

ID
Phone
Number 5
40
Special
Service
Number 6

ID
Phone
Number 6
40
Special
Service
Number 7

ID
Phone
Number 7
40
Special
Service
Number 8

ID
Phone
Number 8
40
Parameter
Name
SSNUM 9
PNUM9
SSNUM 10
PNUM10
Parameter
Description
Instruction
Special
Service
Number 9

ID
Phone
Number 9
40
Special
Service
Number 10

ID
Phone
Number 10
40
For example, create the special service phone group. The Special service phone group ID is 1, the special service number is
110, the phone number is 0086251100 and the special service
phone group name is SSPN1. The command is as follows:
ADD SSPN:SSPGID=1,SSPGNAME="SSPN1",SSNUM1=11
0,PNUM1="0086251100";
END OF STEPS
Creating the Special Service Phone

Called Number Analysis
Prerequisites
Context
The number analyzer entry is created.
The special service phone group is created.
This topic details how to create the special service called number
analysis.
199
Steps

system tree.
SET:NEID=11;
2. Analyze the prefix of a called number by executing command
ADD TPDNAL.
TPDNAL is shown inTable 95
Parameter Name
ENTR
DIGIT
Parameter
Description
Instructions
Number analyzer entry
from 1 to 1000. Select the
corresponding analyzer entry
of the analyzed number prefix.
For local calls, select the corresponding analyzer entry of the
local number analyzer
Analyzed number
consisting of 0~20 digits. Input
the prefix of the called number, whose length must make it
be distinguished in the local office. For intra-office calls, it is
required to configure both the
prefix of the called number and
that of the local-office roaming
number
describe the called number
analysis to make it easily
recognized
NAME
User alias
CAT
Call service types
It is an optional parameter, select LSFR (Free Special Service

Of The Current Office)
RST1
Number analysis
result 1
Type the special service

number configured in ADD
SSPN
For example, create the special service called number analysis

with the following requirements:
200
Number analyzer entry: 1
User alias: SS1
Call service types: LSFR
Number analysis result 1 :110
Other parameters: Use default

ADD TPDNAL:ENTR=1,DIGIT="110",NAME="SS1",SPEC
RST=0,SPECIDX=0,CAT=LSFR,RST1=110,RST2=0,RST3
=0,CHAINAL=0,RNLEN=0,MINLEN=3,MAXLEN=20,OVLY
PRI=NO,REL=NO,NET=1,NAT=DEF,OPDDICONT=NO,TP
DDICONT=NO,OPDDI=0,TPDDI=0,OPDLYDDI=0,TPDLY
DDI=0,DDIOVERB=0,IWVIDEO=LSUP,TIMELMT=0,AUX
DAS=0,A6=0,PFXLEN=0,INSRV=INM,FAXIDX=0,AVIDX
=0,DVIDX=0,ADATAIDX=0,DDATAIDX=0,DDCPLAY=NO
NE,VAD=INVALID,CALLSERVPRILVL=INVALID,RERTS=0,I
NCHAIN=NO,BICT=NO,ICT=0,ICTT=10,GNM=NORMAL,S
TBILL=INVALID,HOPDAS=0,MCA=NO,IVVR=NO,WANTL
=0,IMSCENTR=NO;
END OF STEPS
LAI and GCI/Service Area

Configuration
Creating a LAI Controlled by the
Local Office
Prerequisites
The RNC/BSC office direction attributes are configured.
The LAI range is set in the Resource Management system.
Context
This section introduces how to configure the basic information for

a Location Area ID (LAI) controlled by the BSC/RNC.
Steps
1. If no exchange is specified, execute the command SET on the

MML Terminal window or select a NE from the system tree to
specify the exchange to be configured.
Example: Select the MSCS 11 from the system tree.
SET:NEID=11;
2. Create a LAI controlled by the local office by executing command ADD LAI.
The explanation of the main parameters in command ADD LAI
is shown inTable 96.
201
TABLE 96 PARAMETERS IN THE ADD LAI COMMAND

Parameter
Name
Parameter
Description
Instruction
LAC
Location area
code (HEX)
consisting of 4 HEX digits. It
should be consistent with that
of the RNC/BSC side
Alias
It is used to describe the LAI,
such as Adjacent BSC/RNC
office name-LAI
Location area ID
It is used to define a LAI in
the system, ranging from
1~65534. If there is no special
requirements, enter the LAI
in the cell of the BSC/RNC
connected with the MSCS
Virtual MSC index
It indicates whether the
BSC/RNC connected with
the MSCS accesses the
MSCS through the public
domain. If the BSC/RNC
accesses the MSCS through
the public domain, enter 0.
Otherwise, enter the index of
the connected virtual MSC
MCC
Mobile Country
Code
consisting of 0~3 digits. Enter
it according to the actual
condition, such as 460 for
China
MNC
Mobile Network
Code
Enter the corresponding MNC
of this LAI
MSC number.
It indicates which MSC the

accessed RNC/BSC belongs to.
At present, in the network
management system in the
default case, if the accessed
RNC/BSC is controlled by the
local office (i.e., the BELONG
field is MSC), no MSC number
needs to be entered. If
VMSCIDX is 0, the system
directly adopts the MSC
number from the local-office
mobile data. If VMSCIDX is not
0, the system directly adopts
the corresponding virtual MSC
number from the virtual MSC
configuration. If the accessed
RNC/BSC is not controlled by
NAME
ID
VMSCIDX
MSC
202
Parameter
Name
Parameter
Description
Instruction
the local office, this parameter
needs to be entered
VLR number
It indicates which VLR the

RNC/BSC is controlled by
the local office (i.e., the
BELONG field is MSC), no
VLR number needs to be
entered. If VMSCIDX is 0, the
system directly adopts the VLR
mobile data. If VMSCIDX is not
0, the system directly adopts
the corresponding virtual VLR
number from the virtual MSC
configuration. If the accessed
RNC/BSC is not controlled by
the local office, this parameter
needs to be entered
LOCNUM
Location number
The VLR brings the location
number to the HLR during
PROVIDE-SUBSCRIBERLOCATION procedures. Enter
country code + area code,
such as 8625 for Nanjing in
China
ECCIDX
Emergency call
index
Select a configured emergency
call index. If no emergency
call index is configured, select
0
BSC ID in the LAI
Enter one or more adjacent
BSC office IDs managing
this LAI. In case of the RAN
accessing the MSCS, there
is no need to configure this
parameter
RNC ID in the LAI
Enter one or more adjacent
RNC office IDs managing
this LAI. In case of the BSC
accessing the MSCS, there
is no need to configure this
parameter
DAS for the called

number
Enter the originating DAS 101
from the number analysis
configuration. If no DAS is
configured, enter 0 at first and
then modify it
VLR
BSC
RNC
TPDAS
203
Parameter
Name
Parameter
Description
Instruction
Belonging to,
including
BELONG
NO_MSC(not
belong to
local MSC
Server
domain)
MSC (belong
to local
MSC Server
domain)
DATTR
(belong to
double home
domain)
with MSC as the default value.
If this LAI is managed by
the local office, select MSC.
Otherwise, select NO_MSC. In
this case, it is required to enter
the MSC number and VLR
number where this LAI belongs
to. IF this LAI is managed by
a dual-homing domain, select
DATTR
Location area
attribute,
including:
LAIATTR
ATTBILL
(Produce
attempt call
bill)
NONE (none)
WDMID
Work domain
index
with 0 as the default value.
In case of dual-homing
networking, enter the
dual-homing work domain
index ranging from 0 to 255
UPVER
UP mode version
of MSC-B
indicating the version No. of
the MSC user plane where the
location area exists
R5HOCASE
GSMSSPGID
204
Support HO Case
of Version R5,
including:
NO
YES
GSM Special
Service Phone
Group ID
and the default value is NO. It
configures whether the local
LAI supports the R5 handover.
During 3G-to-2G handover,
determine the transform
mode for the handover and
ensure the compatibility of
the version according to the
configuration. That is to say,
when the option is YES, the
handover is done according to
the handover reason defined
in R5 version. If the option
is NO, the handover is done
according to the handover
reason defined in R4 version
ranging from 0 to 65535 and
it is defined by the command
ADD SSPN
Parameter
Name
Parameter
Description
Instruction
UMTSSSPGID
UMTS Special
Service Phone
Group ID
defined by the command ADD
SSPN
Extend Info,
including:
EXTINFO
NONBCLAI
(Non-Broadcast
LAI in POOL)
For the non-broadcast LAI in
POOL, the value is Null
For example, create BSC location area with the following requirements.
Location area code: 12FB
Location area identity: 201
User alias: BSC-12FB
Location number: 8625
BSC ID in LAI: 99
DAS for the called number: 1
Other parameters: use default

ADD LAI:LAC="12FB",NAME="BSC-12FB",ID=201,MCC="4
60",MNC="00",LOCNUM="8625",ECCIDX=1,BSC="99",R
NC="0",TPDAS=1,BELONG=NO_MSC,WDMID=0,UPVER
=1,R5HOCASE=NO,GSMSSPGID=1,UMTSSSPGID=0,PAG
EIDX=0,ASSTIMER=0;
END OF STEPS
Creating an Adjacent LAI

Prerequisites
Context
The LAI range is set in the Resource Management system.
This section introduces how to create an adjacent LAI where handover services may occur.
When a handover occurs, the handover request message carries
the target cell. The MSCSERVER needs to get the MSCNUM according to the LAI in the message, and judge whether the handover
occurs within the local office. When the corresponding MSC number of the LAI is different with the local MSC number, it is required
205
to initiates an inter-office handover to other MSC. Therefore, it is

required to configure the number of the home MSC/VLR of the adjacent LAI belongs.
Steps

SET:NEID=11;
2. Create an adjacent LAI by executing command ADD LAI.
The explanation of the main parameters in command ADD LAI
TABLE 97 PARAMETERS IN THE ADD LAI COMMAND
Parameter
Name
Parameter
Description
Instructions
LAC
Location area code

(HEX)
It consists of 4 HEX digits. It
should be consistent with that
of the RNC/BSC side
Alias
It is used to describe the LAI,
such as Adjacent BSC/RNC
office name-LAI
Location area ID
It is used to define a LAI in
the system, ranging from
1~65534. If there is no
special requirements, enter
the LAI in the cell of the
BSC/RNC connected with the
MSCS
Virtual MSC Index
BSC/RNC connected with
the MSCS accesses the
MSCS through the public
domain. If the BSC/RNC
accesses the MSCS through
the public domain, enter 0.
Otherwise, enter the index of
the connected virtual MSC
Mobile Country
Code
consisting of 0~3 digits. Enter
it according to the actual
condition, such as 460 for
China
Mobile Network
Code
Enter the corresponding MNC
of this LAI, such as 00 for
China Mobile, and 01 for
China Unicom
NAME
ID
VMSCIDX
MCC
MNC
206
Parameter
Name
MSC
VLR
LOCNUM
Parameter
Description
Instructions
MSC number
It indicates which MSC the

default case, if the connected
field is MSC), no MSC number
directly adopts the MSC
mobile data. If VMSCIDX is
not 0, the system directly
adopts the corresponding
virtual MSC number from the
virtual MSC configuration. If
the accessed RNC/BSC is not
controlled by the local office,
this parameter needs to be
entered. When configuring
the adjacent LAI, enter the
corresponding MSC GT of the
adjacent LAI
VLR number
It indicates which VLR the

field is MSC), no VLR number
directly adopts the VLR
mobile data. If VMSCIDX is
not 0, the system directly
adopts the corresponding
virtual VLR number from the
virtual MSC configuration. If
the accessed RNC/BSC is not
controlled by the local office,
this parameter needs to be
entered. When configuring
the adjacent LAI, enter the
corresponding VLR GT of the
adjacent LAI
Location number
The VLR brings the location
number to the HLR during
PROVIDE-SUBSCRIBERLOCATION procedures. Enter
country code + area code,
such as 8625 for Nanjing in
China
207
Parameter
Name
Parameter
Description
Instructions
Belonging,
including
BELONG
NO_MSC(not
belong to local
MSC Server
domain)
MSC (belong
to local
MSC Server
domain)
DATTR
(belong to
double home
domain)
with MSC as the default value.
If this LAI is managed by
the local office, select MSC.
Otherwise, select NO_MSC.
In this case, it is required to
enter the MSC number and
VLR number where this LAI
belongs to. IF this LAI is
managed by a dual-homing
domain, select DATTR
Location area
attribute,
including:
LAIATTR
ATTBILL
(Produce
attempt call
bill)
NONE (none)
WDMID
Work domain
index
with 0 as the default value.
In case of dual-homing
networking, enter the
dual-homing work domain
index ranging from 0 to 255
UPVER
UP mode version
of MSC-B
indicating the version No. of
the MSC user plane where the
location area exists
R5HOCASE
GSMSSPGID
208
Support HO Case
of Version R5,
including:
NO
YES
GSM Special
Service Phone
Group ID
and the default value is NO. It
configures whether the local
LAI supports the R5 handover.
During 3G-to-2G handover,
determine the transform
mode for the handover and
ensure the compatibility of
the version according to the
configuration. That is to say,
when the option is YES, the
handover is done according to
the handover reason defined
in R5 version. If the option
is NO, the handover is done
according to the handover
reason defined in R4 version
ranging from 0 to 65535 and
it is defined by the command
ADD SSPN
Parameter
Name
Parameter
Description
Instructions
UMTSSSPGID
UMTS Special
Service Phone
Group ID
defined by the command ADD
SSPN
Extend Info,
including:
EXTINFO
NONBCLAI
(Non-Broadcast
LAI in POOL)
For the non-broadcast LAI in
POOL, the value is Null
For example, create the BSC location area with the following
requirements.
Location area code: 1111
Location area identity: 301
User alias: BSC-1111
Location number: 8625
VLR number: 8613954353
Belong type: NO_MSC

ADD LAI:LAC="1111",NAME="BSC-1111",ID=301,MCC="4
60",MNC="01",MSC="8613954353",VLR="8613954353",LO
CNUM="8625",ECCIDX=0,BSC="0",RNC="0",TPDAS=0,BE
LONG=NO_MSC,WDMID=0,UPVER=1,R5HOCASE=NO,GS
MSSPGID=0,UMTSSSPGID=0,PAGEIDX=0,ASSTIMER=0;
END OF STEPS
Creating a Global Cell

Prerequisites
Context
The DAS for the called number is configured.
The BSC LAI is configured.
When the BSC accesses the MSCS, it is required to configure the

global cell data. When a GSM handover occurs, the handoveroriginated office (intra/inter-office handover) needs to know the
home BSC of the handover-terminated cell, so that it can initiates
a handover request to the BSC.
209
Steps

SET:NEID=11;
2. Create a global cell by executing command ADD GCI.
The explanation of the main parameters in command ADD GCI
TABLE 98 PARAMETERS IN THE ADD GCI COMMAND
Parameter Name
Parameter
Description
Instructions
Location area ID
ranging 1 to 65534. Select the
home LAI of the cell from the list
of configured LAIs
Cell Identity
(hex)
composed of GCIBEGIN (Cell
Identity Begin) and GCIEND (Cell
Identity End). The format of it is
CIB-CIE. Configure it according to
the real conditions. It should be
consistent with that of the BSC
side
TPDAS
Called Number
Selector
ranges from 0 to 4096, with
a default of 0. It may not be
configured here. During the call
data configuration, it could be
modified and the referred value
is the number analysis selector in
the number analysis configuration
BSC
BSC Office

from 0 to 3000. Select the BSC
office that manages this cell
LAIID
GCI
Cell Attribute,
including
GCIATTR
NONE (none)
ATTBILL
(produce
attempt call bill)
210
NAME
Alias
consisting of 0~50 characters
SSPGID
Special service
phone group ID

from 0 to 65535. It is defined by
the command ADD SSPN
VMSCIDX
Virtual MSC
Index
ranges from 0 to 65535. If 0
is selected, it represents public
domain, if 0 is not selected,
Parameter Name
Parameter
Description
Instructions
the virtual MSC index should be
entered.
ECCIDX
Emergency
index
call

from 0 to 65535.
For example, create the global cell with the following requirements.
Location area ID: 201
Called number selector: 101
Cell identity (Hex): 1111-1111
BSC office ID: 99
Alias: GCI1
Special service phone group ID: 1
Emergency call index: 1
Other parameters: adopt the default value.

ADD GCI:LAIID=201,GCI="1111"-"1111",TPDAS=1,BSC
=99,NAME="GCI1",SSPGID=1,ECCIDX=1;
END OF STEPS
Creating a Service Area

Prerequisites
The RNC LAI is created.
Context
During the RNC access, it is required to configure the data for the
service area.
Steps
1. If the exchange is not specified, execute the command SET

on the MML Terminal window or select a NE from the system
tree to specify the exchange to be configured.
SET:NEID=11;
2. Create a service area with the command ADD SAI.
The parameter description of the command ADD SAI is shown
in Table 99.
211
TABLE 99 PARAMETERS IN THE ADD SAI COMMAND

Parameter
Name
Parameter
Description
LAIID
Location
Area ID
It is a mandatory parameter ranging

from 1 to 65534. Select the home LAI
of the cell from the list of the configured LAIs
SAC
Service Area
Code (hex)
It is a mandatory parameter composed of SACB (Service Area Code

Begin) and SACE (Service Area Code
End).
The format is SACB-SACE.
Configure it according to the real conditions. It should be consistent with
that of the RNC side
RNC
RNC Office

from 0 to 2048. Select the RNC office
that manages this service area
NAME
Alias

from 0 to 50 characters
SSPGID
Special Service
Phone
Group

from 0 to 65535 and it is defined by
the command ADD SSPN
VMSCIDX
Virtual
Index

from 0 to 65535. If 0 is selected, it
means the common domain. If it is
not 0, enter the accessed virtual MSC
index No.
ECCIDX
Emergency
call index
MSC
Instructions

from 0 to 65535.
For example, create a service area identity with the following

requirements. The is 201, the , and the is 100. For the other
parameters, select the default value. The command is as follows:
Location area ID: 201
Service area code: 0000
RNC office ID: 100
Alias: SAI1
Special service phone group: 1
Emergency call index: 1

ADD SAI:LAIID=201,SAC="0000"-"0000",RNC=100,NAME
="SAI1",SSPGID=1,ECCIDX=1;
END OF STEPS
212
Chapter
Number Analysis Data

Making
Table of Contents
Number Analysis ............................................................. 213
Number Analysis Configuration .......................................... 218
Number Analysis
The switch performs network addressing based on each type of
numbers. In the mobile switch, there are two types of numbers.
One type is subscriber number, including fixed subscriber number
and mobile subscriber number. The other type is network number, including Mobile Station Roaming Number (MSRN), MSC/VLR
number, HLR number, and handover number. ZXWN MSCS number analysis configuration is used to determine the corresponding
network addressing and service processing methods of each type
of number to ensure that the switch can correctly perform signaling interaction and voice channel connection.
ZXWN MSCS system provides seven number analyzers: new service number analyzer, CENTREX number analyzer, private-network
number analyzer, special-service number analyzer, local-network
number analyzer, national toll-service number analyzer, and international toll-service number analyzer. For a specified DAS, numbers pass each type of analyzers specified by this DAS in a fixed
order. The analyzers strictly follow the following order to perform
number analysis, as shown in Figure 11.
213
FIGURE 11 ANALYSIS ORDER OF NUMBER ANALYZERS
Configuration instances of common DASs and the number analysis

results are as follows:
1. DAS for pre-analyzing the called number
It is used to process special dial prefixes, including performing
call restriction, format conversion of the called number.
After an exchange receives 10193+called number dialed by
a subscriber, 10193 is deleted in this exchange, and the subsequent routing is based on the existing traffic routing, as shown
in Table 100.
TABLE 100 DAS FOR PRE-ANALYZING THE CALLED NUMBER
Analyzer
Entry
Analyzed Number
Analysis Result
If call restriction is
required, analyze it to
pre-analysis ending, and
call rejected
10193 + 0 + local area

code
New
service
number
analyzer
10193 + 0 + non-local
area code
10193 + G network
number section
10193 + C network
number section
214
If no call restriction is
required, analyze it to
pre-analysis normally
ending, and delete
10193 + 0 + local area
code from the change
index of the called
number
Analyze it to
pre-analysis normally
ending, and delete
10193 from the change
index of the called
number.
Whether to add 10193 to
the called-number index
in the CDR depends
on the CDR filling
requirements on the
billing center
Chapter 3 Number Analysis Data Making
2. Originating DAS: used to analyze the called number in the local-office-originated call, as shown in Table 101.
TABLE 101 ORIGINATING DAS
Analyzer
Entry
Analyzed Number
Analysis Result
New
service
number
analyzer
Charging query number
Analyze it to the SSP

charging query service
Free special-service
number
Analyze it to the
local-office free special
service, pointing to
the special-service
number configured on
the attendant console
Corresponding attendant
console number of the
special-service number
Analyze it to the
outgoing free special
service, pointing to the
special-service circuit
group
Short number
Special-service number
of the operator
Analyze it to the
outgoing free special
service, pointing to the
special-service circuit
group
Specialservice
number
analyzer
Vacant number
0
Localnetwork
number
analyzer
All numbers are analyzed

by the subsequent
analyzers
Local PSTN number
Analyze it to
the local-network
outgoing/local-call
the gateway office
Local number section of

other mobile network
Analyze it to
the local-network
outgoing/local-call
the gateway office
Non-local number section

of other mobile network
Analyze it to the
automatic service in
the national toll region,
pointing to the tandem
office of the local province
Number section of the

local mobile network
Analyze it to the MSC

common service
215
Analyzer
Entry
Analyzed Number
Analysis Result
Vacant number
National
toll-service
number
analyzer
International
toll-service number
analyzer
All numbers are analyzed

by the subsequent
analyzers
0 + Local area code +

Local PSTN number
Analyze it to
the local-network
outgoing/local-call
the gateway office
0 + Non-local area code
Analyze it to the
automatic service in
the national toll region,
pointing to the tandem
office of the local province
00 + International
number
Analyze it to the
international toll
automatic service
3. Forwarding DAS: used to analyze the number to which the call

is forwarded, as shown in Table 102.
TABLE 102 FORWARDING DAS
Analyzer Entry
Analyzed Number
Analysis Result
Vacant number
Local PSTN number
Analyze it to the
local-network
outgoing/local-call
the gateway office
Local number
section of other
mobile network
Analyze it to the
local-network
outgoing/local-call
the gateway office
Non-local number
section of other
mobile network
Analyze it to the
automatic service
in the national toll
region, pointing to
the tandem office of
the local province
Local-network
number analyzer
216
All numbers are

analyzed by
the subsequent
analyzers
Analyzer Entry
Analyzed Number
Analysis Result
Number section of
the local mobile
network
Analyze it to the MSC

common service
Vacant number
National toll-service
number analyzer
All numbers are

analyzed by
the subsequent
analyzers
0 + Local area
code + Local PSTN
number
Analyze it to the
local-network
outgoing/local-call
the gateway office
0 + Non-local area
code
Analyze it to the
automatic service
in the national toll
region, pointing to
the tandem office of
the local province
4. Roaming DAS: used to analyze the roaming number in the response message to the routing information query message, as
shown in Table 103. It is unnecessary to analysis the CC in
national roaming numbers.
TABLE 103 ROAMING DAS
Analyzer Entry
Analyzed Number
Analysis Result
Roaming number
section of the local
service area in the
local office
Analyze it to the
local MSC service
Analyze it to the
outgoing service of
the local MSC.
Local-network
number analyzer
Roaming number
section of non-local
service area in the
local office
Note: The roaming

DAS is used when
there is no direct
voice channel
between MGWs
(switched through
the T office) in the
region networking
National other
roaming sections
Analyze it to the
national toll call
00 + International
number
Analyze it to the
international toll
automatic service
217
Number Analysis
Configuration
Overview
Description
This section only introduces the basic steps of number analysis.

For detailed configuration related with number analysis (including number pre-analysis, calling number analysis, and number
change), refer to ZXWN MSCS MSC Server Number Analysis.
Data Configuration
The related operations of the number analysis configuration are as

follows.
Steps
Operations
Instructions
Commands
Creating a number
analyzer entry
Specify an ID
for each type of
number analyzers
ADD ENTR
Creating a DAS
The DAS is the

collection of
various number
analyzer entries,
specifying the
order and rule
of performing
number analysis.
ADD DAS
Setting the default

DAS template of
the local office
Set the default

DAS template
of the local
office means
creating the DAS
used for localoffice service
processing.
SET LDASTM
PLT
Creating a
DAS template
(optional)
Create multiple
DAS templates in
the dual-homing
or regional
networking.
ADD ACRTMPLT
Creating the called

numbers analysis
Create number
analysis for
prefixes of called
numbers and
roaming numbers
ADD TPDNAL
Creating a Number Analyzer Entry

Prerequisites
218
The number analyzer entry range is set in the resource management system.
Context
Creating number analyzer entries means specifying an ID for each

type of number analyzers.
Steps

system tree.
SET:NEID=11;
2. Create a number analyzer entry by executing command ADD
ENTR.
ENTR is shown in Table 104.
TABLE 104 PARAMETERS IN THE ADD ENTR COMMAND
Parameter
Name
Instruction
ID
Analyzer entry
It is an optional
parameter, which is
1 to 1000
NAME
User alias
It is a mandatory
parameter, consisting of
0~50 characters
TYPE
Analyzer entry type
It is an optional
parameter. Refer
to Table 105 for the
configuration description
NTYPE
Number analysis result

under this analyzer,
including CALLED
(analysis on called
numbers), CALLING
(analysis on calling
numbers), FORWARD
(analysis on calling
numbers during call
forwarding), OPIMSI
(analysis on calling IMSI
numbers), TPIMSI
(analysis on called
IMSI numbers), and
FWDIMSI (analysis on
IMSI numbers during
call forwarding)
It is an optional
parameter, with CALLED
as the default value. In
general, select CALLED
Virtual MSC index
It is an optional
parameter, which is
an integer, ranging
from 0 to 65535. Enter
it according to the
actual condition. The
default value is 0 (public
domain)
VMSCIDX
219
TABLE 105 ANALYZER ENTRY TYPES

Parameter
Name
Configuration
Description
NEWSRV
New service number

analyzer
After this analyzer

is configured, if the
number is not matched
in this analyzer, it is sent
to the next entry for
analysis
CENTREX
CENTREX number
analyzer
This analyzer is not

configured
PRINET
Private-network number
analyzer
This analyzer is not

configured
SPECSRV
analyzer
After this analyzer

in this analyzer, it is is
sent to the next entry
for analysis
LOCAL
Local-network number
analyzer
After this analyzer

in this analyzer, the
analysis ends
NATIONAL
number analyzer
After this analyzer

in this analyzer, the
analysis ends
INTER
International toll-service
number analyzer
After the number is

analyzed in this analyzer,
the analysis ends
Example: Create a number analyzer entry with the following

requirements.
Number analyzer entry ID: 1
User alias: Entr1
Number analyzer entry type: Local number analyzer
Analyzed number type: Called number.
The command is:

ADD ENTR:ID=1,NAME="Entr1",TYPE=LOCAL,NTYPE=CAL
LED;
END OF STEPS
220
Creating a DAS
Prerequisites
Context
The DAS range is set in the resource management system.
The DAS is the collection of various number analyzer entries, specifying the order and rule of performing number analysis.
Table 106 lists common DASs.
TABLE 106 COMMON DASS
Parameter
Name
Configuration
Description
MS
MS originating
Used to analyze the called

number when an MS
originates a call
MSRN
Mobile station roaming

number
Used to analyze roaming

numbers or handover
numbers
CNG
Calling number analysis
Used for traffic division of

calling numbers
LI
Intercepted number
Used for the interception

function
PBRT
Personal Back Ring Tone
Used for the PBRT function
FWD
Forwarding number
analysis
Used to analyze the

third-party number to
which the call is forwarded
Number pre-analysis
Used for the number

pre-analysis function,
standardizing called
numbers, and performing
call restriction based on
numbers
PREDAS
Steps

system tree.
SET:NEID=11;
2. Create a DAS by executing command ADD DAS.
The explanation of the main parameters in command ADD DAS
221
TABLE 107 PARAMETERS IN THE ADD DAS COMMAND

Parameter
Name
Instruction
ID
DAS
It is a mandatory
integer, ranging from
1 to 4096. It is the
index number of the
newly-added DAS
NAME
User alias
It is an optional
parameter, consisting of
0~50 characters.
NEWSRV
New service number

analyzer entry
CENTR
CENTREX number
analyzer entry
PRINET
Private-network number
analyzer entry
SPECSRV
analyzer entry
LOCAL
Local-network number
analyzer entry
NATIONAL
number analyzer entry
INTER
International
toll-service number
analyzer entry
VMSCIDX
Virtual MSC index
Enter the umber

analyzer entry IDs
contained by a DAS
Example: Create a MS originating DAS with the following requirements.
DAS ID: 101
User alias: MSQH
Local number analyzer entry: 1
The command is:

ADD
DAS:ID=101,NAME="MSQH",NEWSRV=0,CENTR
=0,PRINET=0,SPECSRV=0,LOCAL=1,NATIONAL=0,INTE
R=0;
END OF STEPS
222
Setting the Default DAS Template of

the Local Office
Prerequisites
The DAS is configured.
Context
Creating the default DAS template of the local office means creating the DAS used for local-office service processing.
Steps

system tree.
SET:NEID=11;
2. Set the default DAS template of the local office by executing
command SET LDASTMPLT.
The explanation of the main parameters in command SET
LDASTMPLT is shown in Table 108.
TABLE 108 PARAMETERS IN THE SET LDASTMPLT COMMAND
Parameter Name
MS
MSRN
Parameter
Description
Instruction
MS originating
DAS

is an integer, ranging from 0
to 4096. It is used to analyze
the called number when an MS
originates a call. If the called
party is a mobile subscriber,
the MSC needs to query the
routing information from the
corresponding HLR. If the called
party is a fixed subscriber, the
MSC connect the call to the
corresponding local exchange or
toll exchange according to location
of the called party
MSRN DAS

to 4096. It is used to analyze
the MSRN returned from the
HLR, and judge whether the call
belongs to the local-office mobile
service or outgoing mobile service
based on this number. If the call
belongs to the local-office mobile
service, this number is sent to
the corresponding module for
processing. If the call belongs to
the outgoing mobile service, select
the corresponding route chain
for call connection. In addition,
223
Parameter Name
Parameter
Description
Instruction
this DAS also analyzes forwarding
numbers returned from the HLR,
and subscriber numbers from
other mobile office or fixed office
is an integer, ranging from 0 to
4096.
OR
Preferred
routing DAS
When it is set that the local office

supports preferred routing in the
global variable control system,
configure this DAS for international
roaming call and the forwarding
service
4096.
CNG
LI
IP
Calling number
DAS
Interception
DAS
IP DAS
It is used to analyze the calling

number in outgoing calls to
implement traffic division of the
calling number and calling number
change function
4096.
It is used for the interception
service
4096.
It is used for the IP telephone
service
ICBCNG
PBRT
Incoming call
restriction DAS
for calling
numbers
PBRT DAS

4096.
It is used for the incoming call
restriction service
4096.
It is used for the PBRT service
224
FWD
Forwarding DAS

4096
FWDCNG
Forwarding
DAS for calling
numbers

4096
CNGVIGW
Calling number
DAS of virtual
IGW

4096
Parameter Name
Parameter
Description
Instruction
FWDVIGW
Forwarding DAS
of virtual IGW

4096
INTRA
Wire and
wireless
integrated DAS

4096. It is used for the function
of one number for two MSs and
mixed group
ROUTCAT1
MS originating
DAS for
category-1
subscribers

4096
ROUTCAT2
MS originating
DAS for
category-2
subscribers

4096
ROUTCAT3
MS originating
DAS for
category-3
subscribers

4096
ROUTCAT4
MS originating
DAS for
category-4
subscribers

4096
ROUTCAT5
MS originating
DAS for
category-5
subscribers

4096
IMSIOPDAS
Outgoing IMSI
traffic division
DAS

4096
OVERLAY
Calling
OVERLAY DAS

4096
IGWMONITOR
IGW
interception
DAS

4096
SHLRSKEY
SHLR service
key conversion
DAS

4096
IMSITPDAS
DAS for called

IMSI

4096
IMSIFWDAS
DAS for the

IMSI of the
subscriber to
whom the call is
forwarded

4096
225
Parameter Name
Parameter
Description
Instruction
TESTCALLDAS
Test call DAS

4096
MRBT
Multi-media
ring back tone
DAS

4096
INTPREDAS
International
number
pre-analysis
DAS

4096
PREDAS
Number
pre-analysis
DAS

1000
RECNCTDAS
Reconnection
DAS

4096
Example: Configure the default DAS template of the local office

MS originating DAS: 101
MSRN DAS: 201
Forwarding DAS: 301.
The command is:

SET LDASTMPLT:MS=101,MSRN=201,FWD=301;
END OF STEPS
Creating a DAS Template

Prerequisites
Context
It is required to create multiple DAS templates in the dual-homing

or regional networking.
Steps

system tree.
SET:NEID=11;
2. Create a DAS template by executing command ADD ACRTMP
LT.
226

ACRTMPLT is shown in Table 109.
TABLE 109 PARAMETERS IN THE ADD ACRTMPLT COMMAND
Parameter
Name
Instruction
TMPLIDX
Routing template ID
It is a mandatory
parameter, ranging
from 1~65535
NAME
User alias
It is a mandatory
of 1~50 characters
MS
MS originating DAS
It is an optional
parameter, which is
0 to 4096
MSRN
MSRN DAS
It is an optional
parameter, which is
0 to 4096
OR
Preferred routing DAS
It is an optional
parameter, which is
0 to 4096
Calling number DAS
It is an optional
parameter, which is
0 to 4096
LI
Interception DAS
It is an optional
parameter, which is
0 to 4096
IP
IP DAS
It is an optional
parameter, which is
0 to 4096
CBCNG
Incoming call restriction

DAS for calling numbers
It is an optional
parameter, which is
0 to 4096
PBRT
PRBT DAS
It is an optional
parameter, which is
0 to 4096
Forwarding DAS
It is an optional
parameter, which is
0 to 4096
CNG
FWD
227
Parameter
Name
Instruction
FWDCNG
Forwarding DAS for

calling numbers
It is an optional
parameter, which is
0 to 4096
CNGVIGW
Calling number DAS of

virtual IGW
It is an optional
parameter, which is
0 to 4096
FWDVIGW
Forwarding DAS of
virtual IGW
It is an optional
parameter, which is
0 to 4096
INTRA
Wire and wireless

integrated DAS
It is an optional
parameter, which is
0 to 4096. It is used
for the function of one
number for two MSs and
mixed group
ROUTCAT1
MS originating DAS for

category-1 subscribers
It is an optional
parameter, which is
0 to 4096
ROUTCAT2

It is an optional
parameter, which is
0 to 4096
ROUTCAT3

It is an optional
parameter, which is
0 to 4096
ROUTCAT4

It is an optional
parameter, which is
0 to 4096
ROUTCAT5

It is an optional
parameter, which is
0 to 4096
IMSIOPDAS
Calling IMSI number

selector
It is an optional
parameter, which is
0 to 4096
Calling OVERLAY DAS
It is an optional
parameter, which is
0 to 4096
OVERLAY
228
Parameter
Name
Instruction
LIIGW
IGW interception DAS
It is an optional
parameter, which is
0 to 4096
SHLR service key DAS
It is an optional
parameter, which is
0 to 4096
IMSITPDAS
DAS for called IMSI
It is an optional
parameter, which is
0 to 4096
IMSIFWDAS
DAS for the IMSI of the

subscriber to whom the
call is forwarded
It is an optional
parameter, which is
0 to 4096
MBRT
Multi-media ring back

tone DAS
It is an optional
parameter, which is
0 to 4096
INTPREDAS
International number
pre-analysis DAS
It is an optional
parameter, which is
0 to 4096
PREDAS
Number pre-analysis
DAS
It is an optional
parameter, which is
0 to 1000
RECNCTDAS
Reconnection DAS
It is an optional
parameter, which is
0 to 4096
SHLRSKEY
Example: Add a DAS template with the following requirements.
DAS template ID: 1
User alias: VMSC1
MS originating DAS: 101
MSRN DAS: 201
Preferred routing DAS: 301
Calling number DAS: 401
The command is:

ADD
ACRTMPLT:TPLIDX=1,NAME="VMSC1",MS=101,M
SRN=201,OR=301,CNG=401,LI=0,IP=0,CBCNG=0,PBRT
=0,CFU=0,CFUCNG=0,CFNDUB=0,CFNDUBCNG=0,CFUD
UB=0,CFUDUBCNG=0,CFNRC_E=0,CFNRCCNG_E=0,CF
NRC_L=0,CFNRCCNG_L=0,CFNRY=0,CFNRYCNG=0,CD
229
=0,CDCNG=0,FWD=0,FWDCNG=0,CNGVIGW=0,FWDVI
GW=0,INTRA=0,ROUTCAT1=0,ROUTCAT2=0,ROUTCAT3
=0,ROUTCAT4=0,ROUTCAT5=0,IMSIOPDAS=0,OVERLA
Y=0,LIIGW=0,SHLRSKEY=0,IMSITPDAS=0,IMSIFWDAS
=0,MBRT=0,INTPREDAS=0,PREDAS=0,CFPRE=0,CFUPR
E=0,NDUBPRE=0,UDUBPRE=0,CFNRCE_PRE=0,CFNRCL_
PRE=0,CFNRYPRE=0,CDPRE=0,MORCPRE=0,GMSCRCPR
E=0,CFRCPRE=0,MTRCPRE=0,RECNCTDAS=0,CAMELDN
ALIDX=0,SSDAS=0,ASCODEDAS=0;
END OF STEPS
Creating the Called Number Analysis

Prerequisites
Context
This section introduces how to configure number analysis for prefixes of called numbers and roaming numbers. The called number
analysis determines the subsequent service procedures of the call.
Steps

system tree.
SET:NEID=11;
2. Analyze the prefix of a called number or roaming number by
executing command ADD TPDNAL.
TPDNAL is shown in Table 110.
Parameter
Name
ENTR
DIGIT
230
Parameter
Description
Instruction
Number
analyzer entry

1000. Select the corresponding
analyzer entry of the analyzed
number prefix. For local calls,
select the corresponding analyzer
entry of the local number analyzer
Analyzer
number
consisting of 1~20 digits. Input
the prefix of the called number,
whose length must make it be
distinguished in the local office.
For intra-office calls, it is required
to configure both the prefix of
Parameter
Name
Parameter
Description
Instruction
the called number and that of the
local-office roaming number
NAME
SPECRST
SPECIDX
User alias
It is used to specifically describe

the called number analysis to
make it easily recognized
Special analysis
result rule
It is used to specify the index

number of the special analysis
result rule for the associated called
number. This parameter must
be defined by command ADD
CEDSPECRL at first. Then it can
be indexed here. This parameter
is configured to implement the
routing service based on number
length. When the system performs
analysis on the called number,
it automatically matches the
actual length of the called number
to see whether the length is
within the range of Special
analysis result rule for called
numbers. If the length is within
the range, the system adopts the
routing information in Special
analysis result of called numbers.
Otherwise, the system adopts the
routing information in the called
number analysis
Special analysis
result index

number of the special analysis
result of the associated called
number. This parameter must
SPECRST at first. Then it can
be indexed here. This parameter
routing service based on number
length. When the system performs
analysis on the called number,
it automatically matches the
actual length of the called number
to see whether the length is
within the range of Special
analysis result rule for called
numbers. If the length is within
the range, the system adopts the
routing information in Special
analysis result of called numbers.
Otherwise, the system adopts the
routing information in the called
number analysis
231
Parameter
Name
CAT
Parameter
Description
Call service
types, including
the options in
Table 111
Instruction
used to specify the service type
triggered by this number, and
determine the direction of this
call. The system adopts vacant
number by default.
The called number of the local
office is analyzed to MSCO (MSC
common service). The roaming
number of the local office is
analyzed to MSLL (MSC local
service). The roaming number of
other office is analyzed to MSLO
(MSC local outgoing service)
When the call service type is
vacant number, local-network
local-office/common service, MSC
local-network local-office service,
Mobile Number Portability (MNP),
or H323 call, number analysis
result 1 must be fixed to 0. When
the call service type is outgoing
call or toll call, number analysis
result 1 is used to specify the
index number of the outgoing
route chain.
equal access: CIC of the
operator where the subscriber
is located or equal access:
non-local-network CIC, number
analysis result 1 is used to specify
the index number of the outgoing
route chain.
RST1
Number
analysis result
1

OVERLAY prefix incoming
service, number analysis result
1 is used to specify the index
number of the outgoing route
chain. When the call service type
is OVERLAY: CAMEL service
triggered by MO, or OVERLAY:
CAMEL service triggered by MT,
number analysis result 1 is used
to specify the index number of the
outgoing route chain.
When the call service type is IP
service, IP mobile service, or
independent IP service number
route chain.
MNP outgoing routing number
route chain.
Outgoing paid special service
232
Parameter
Name
Parameter
Description
Instruction
or Outgoing free special
service, number analysis result
1 is used to specify the index
number of the outgoing route
chain.
The above-specified index number
of the outgoing route chain must
CHAIN at first. Then it can be
indexed here.
Mobile emergency special
service, Local-office paid
special service or Local-office
free special service, number
the special-service number. This
command ADD SSPN at first.
When the call service type is Tone
play service, CAT_SEND_TONE,
number analysis result 1 is used
to specify the ID of the tone to be
played
RST2
Number
analysis result
2

number of CAMEL access
subscription information of the
calling subscriber. This parameter
must be defined by command
ADD CAINFO at first. Then it
can be indexed here. When the
call service type is equal access:
CIC of the operator where the
subscriber is located or equal
access: non-local-network CIC,
this parameter must be configured.
OVERLAY: CAMEL service
CAMEL service triggered by
MT, this parameter must be
configured. When the call service
type is other types except the
above-listed, number analysis
result 2 must be fixed to 0
RST3
Number
analysis result
3

number of CAMEL access
subscription information of the
called subscriber. This parameter
must be defined by command ADD
CAINFO at first. Then it can be
indexed here.
OVERLAY: CAMEL service
CAMEL service triggered by
MT, this parameter must be
configured. When the call service
233
Parameter
Name
Parameter
Description
Instruction
above-listed, number analysis
result 3 must be fixed to 0
CHAINAL
Route chanin
analysis index
It is used to specify the analysis

index number of the route chain.
This parameter must be defined
by command ADD CHAINAL at
first. Then it can be indexed. This
parameter takes effect only when
the call service type is outgoing
service (including various outgoing
services). It priority is higher than
that of the outgoing route chain
referred to in number analysis
result 1. Route chain analysis is
an intelligent routing policy better
than the policy of specifying a
single route chain
RNLEN
Length of the
carried routing
number
When the call service type is MNP

outgoing routing, it is configured
to the length of the carried routing
number. When the call service
above-listed, it must be fixed to 0
255, with a default of 3. It is
used to specify the minimum digit
length of the analyzed number
required for call connection.
MINLEN
Minimum digit
length of
numbers
During an incoming call, if the

received digits are shorter than
this length, the system waits
for the subsequent digits. If the
system judges that there is no
subsequent digit, and the received
digits are shorter than this length,
the system considers that the
number format is wrong, and
releases the call.
During a local-office-originated
call, if the received digits are
shorter than this length, the
system considers that the number
format is wrong, and releases the
call.
For the OVERLAY prefix incoming
service, the system gets the length
of the OVERLAY prefix according
to the minimum digit length of
numbers. Therefore, it is required
to configure the minimum digit
length of numbers to the length of
the OVERLAY prefix. Otherwise,
procedures cannot be correctly
processed
234
Parameter
Name
Parameter
Description
Instruction
255, with a default of 20. It is
used to specify the maximum digit
length of the analyzed number
required for call connection.
MAXLEN
Maximum
digit length of
numbers
During an incoming call, it is

the basis of whether to wait
for subsequent digits. If the
received digits reach this length,
the system does not wait for
subsequent digits.
During a local-office-originated
call, if the received digits are
longer than this length, the system
determines whether to continue or
release the call according to flag
No call when the called number
exceeds the length in the option
enabling configuration. If the
system determines to continue the
call, it cuts the exceeding digits
OVERLAY
priority,
including:
OVLYPRI
NO (No
priority):
Trigger the
intelligent
service based
on CSI at
first, and
then trigger
the intelligent
service again
based on
OVERLAY
HCSI (Higher
than the CSI
in priority):
Trigger the
intelligent
service based
on OVERLAY
at first, and
then trigger
the intelligent
service again
based on CSI
It is used to the priority relationship

between triggering the intelligent
service based on CSI and triggering
the intelligent service based on
OVERLAY. The system adopts No
Priority by default. When the call
service type is OVERLAY(CAMEL
service triggered by MO), this
parameter is effective. Otherwise,
this parameter is ineffective
235
Parameter
Name
Parameter
Description
Instruction
Voice channel
release mode,
including:
CING (calling
control
release):
The calling
party controls
whether to
release the
call. In this
mode, when
only the called
party hooks on,
the call still can
continue.
REL
CED(called
control
release):
The called
party controls
whether to
release the call.
In this mode,
when only the
calling party
hooks on, the
call still can
continue.
indicates a resource release mode
when subscribers hook on. In
general, select NO. Select CED for
such special numbers as 110 and
119
NO (noncontrol
release): Both
the calling
party and the
called party
can control
whether to
release the call.
In this mode,
no matter
whether the
calling party or
the called party
hooks on, the
call is released
NET
236
Type of the
destination
network

a default of 1. For calls to other
office in the local network, select
the signaling network where the
destination office is located. For
intra-office calls, this option is
meaningless.
Parameter
Name
Parameter
Description
Instruction
Number
address
attribute,
including:
DEF (default
attribute): Do
not replace
the address
attribute of
the analyzed
number.
INT
(international
number):
Replace the
address
attribute of
the analyzed
number with
international
number.
NAT (national
number):
Replace the
address
attribute of
the analyzed
number with
national (valid)
number.
NAT
is used to replace the address
attribute of the analyzed number.
In general, it is set to DEF, or is
set according to the requirements
of the peer end
LOC(local
number):
Replace the
address
attribute of
the analyzed
number with
local number.
UNK (attribute
unknown):
Replace the
address
attribute of
the analyzed
number with
unknown
Transforming
the calling
number again,
including:
OPDDICONT
NO (Not
allowed): It is
not allowed to
transform the
calling number
again in the
subsequent call
procedures.
is used to specify whether it is
allowed to transform the calling
number again in the subsequent
call procedures when the calling
number was already transformed
once. The system adopts NO by
default
237
Parameter
Name
Parameter
Description
Instruction
YES (allowed):
It is allowed to
transform the
calling number
again in the
subsequent call
procedures.
Transforming
the called
number again,
including:
TPDDICONT
NO (Not
allowed): It is
not allowed to
transform the
called number
again in the
subsequent call
procedures.
YES (allowed):
It is allowed to
transform the
called number
again in the
subsequent call
procedures
OPDDI
TPDDI
OPDLYDDI
is used to specify whether it is
allowed to transform the called
number again in the subsequent
call procedures when the called
number was already transformed
once. The system adopts NO by
default
Calling-number
immediate
transform
index
is the number stream transform
index of the calling-number
immediate transform. Immediate
transform immediately makes the
calling number transformed. This
command ADD DDI at first. Then
Called-number
immediate
transform
index
index of the called-number
called number transformed. This
Calling-number
delay transform
index
index of the calling-number delay
transform. Delay transform takes
effects in the IAM message at the
outgoing side instead of making
the calling number transformed
immediately. This parameter must
be defined by command ADD DDI
at first. Then it can be indexed
here.
According to the IAM message at
the outgoing side, perform the
calling-number delay transform
238
Parameter
Name
Parameter
Description
Instruction
here, and then perform the
calling-number delay transform in
the number pre-analysis
TPDLYDDI
DDIOVERB
Called-number
delay transform
index
index of the called-number
called number transformed. This
B-interface
number
transform
index
It is the number stream transform

index of the called number in the
outgoing call request message
between the MSC and the VLR. The
transform purpose is to facilitate
the VLR judging the toll call
authority. This parameter must be
defined by command ADD DDI at
first. Then it can be indexed here
Whether to
support the
interworking
between video
calls, including:
IWVEDIO
LSUP:
Local-network
subscribers
support the
interworking
between
video calls by
default). The
call continues.
OSUP:
Subscribers in
other networks
support the
interworking
between video
calls). The call
continues.
used to specify whether to support
the interworking between video
calls. The default value is LSUP
ONSUP:
Subscribers
in other
networks do
not support the
interworking
TIMELMT
Maximum
call duration
(minute)
It is used to specify the maximum

call duration allowed for a call.
When the duration of a call reaches
the maximum call duration, the
system automatically release the
call. If it is unnecessary to restrict
the maximum call duration, adopt
the default value of 0
239
Parameter
Name
Parameter
Description
Instruction
AUXDAS
Assistant DAS
is used to specify the DAS for
analyzing the called number again
when the call service type is
outgoing service, and when the
connection between the local office
and the mutually-backed-up office
is broken in the mutual backup
dual-homing networking. This
command ADD DAS at first. Then
A6
Sending A6
signal after
receiving
how many
digits during
incoming calls
It is used to specify the number

of digits that the system receives
enough to send A6 signal to the
front office. This parameter only
takes effect during incoming
calls using Channel Associated
Signaling (CAS)
Toll prefix +
Area code
length

to 15. When the call service
type is national/international toll
service, this parameter needs to
be configured
Enabled
options Refer
to Table 112 for
details
In general, select CCS7
(Automatically sending the
calling number when using CCS7
for outgoing services) and (No call
when the called number exceeds
the maximum digit length)
Fax analysis
resutl index
It is used to specify the bearer

analysis result index number of
the called number associated with
the fax service. This parameter
must be defined by command ADD
BEARRST at first. Then it can be
indexed here. This parameter
routing service based on the bearer
capability. For the fax service,
if the associated bearer analysis
result index of the called number
is configured, the call adopts the
associated bearer analysis result
of the called number, thus flexible
routing is implemented
PFXLEN
ENOPT
FAXIDX
240
Parameter
Name
AVIDX
DVIDX
ADATAIDX
Parameter
Description
Instruction
Analog video
analysis result
index

the called number associated
with the analog video service.
by command ADD BEARRST at
first. Then it can be indexed here.
This parameter is configured to
implement the routing service
based on the bearer capability.
For the analog video service, if
the associated bearer analysis
Digital video
analysis result
index

with the digital video service.
by command ADD BEARRST at
first. Then it can be indexed here.
For the digital video service, if
Analog data
analysis result
index

the called number associated with
the analog data service. This
command ADD BEARRST at first.
For the analog data service, if
241
Parameter
Name
DDATAIDX
Parameter
Description
Instruction
Digital data
analysis result
index

with the digital data service. This
command ADD BEARRST at first.
For the digital data service, if the
index of the called number is
configured, the call adopts the
Whether to play
the DDC tone,
including:
DDCPLAY
NONE (Not
playing the
DDC tone): It
is not required
to play the DDC
tone in the local
office.
PLAY (Playing
the DDC tone):
It is required
to play the DDC
tone in the local
office.
It is used to specify whether

to play the DDC tone in the
local office. The system adopts
NONE by default. The purpose
of configuring whether to play
the DDC tone in the number
analysis configuration is to avoid
no tone play or repeated tone play
caused by inconsistent tone play
configuration during inter-office
DDC calls
Voice Activity
Detection
(VAD) flag,
including:
VAD
OPPMGWID
242
CLOSE: Not
starting the
VAD function.
OPEN: Starting
the VAD
function.
INVALID: The
VAD function is
invalid
Opposite-end
MGW ID
It is used to specify whether to

start the VAD function. The system
adopts INVALID by default
It is used to specify between which

opposite-end MGW and the local
MGW the TDM backup route is
adopted. The QOSs between the
local MGW and all opposite-end
MGWs can be found through
automatic test calls. When the
QOS difference between the
opposite-end MGW and the local
MGW is specified, the call adopts
the TDM backup route
Parameter
Name
Parameter
Description
Instruction
Call type
priority,
including:
INVALID: The
call priority is
invalid.
HIGHEST: The
call has the
highest priority.
CALLSERVPRILVL
HIGHER: The
call has a
priority one
level lower than
the highest
priority.
NORMAL:
The call has
a priority one
level lower
than the higher
priority.
It is used to specify the call

priority. The system adopts
INVALID by default. The call
priority has two functions. In
one case, in the softswitch office
in the toll softswitch network,
the voice coding format can be
dynamically selected according to
the call priority and the load on
the IP bearer network. In another
case, based on the combined
information of office ID and
priority configured in the number
analysis configuration, the final
priority of a call is got to perform
load control
LOW: The call

has the lowest
priority
RERTS
Re-routing
route chain
It is used to specify the re-routing

route chain ID. This parameter
must be defined by command
ADD RERTS at first. Then it
can be indexed here. When flag
RRTO in enabled options takes
effect, the re-routing route chain
takes effect too. For an outgoing
call procedure, if the call fails,
and the corresponding failure
cause is configured with Enabling
rerouting for failure in the R_ICP
configuration, re-select the route
from this route chain according
to the re-routing route chain.
For an incoming call using ISUP,
TUP, or BICC signaling, when
the call procedure is an outgoing
procedure, and the call fails before
the IAM message is sent, the
re-routing route chain serves as
the standby route, and is not
controlled by RRTO.
If route chain analysis is
configured, the re-routing
route chain here is invalid. In this
case, use the re-routing route
chain configured in the route chain
analysis
243
Parameter
Name
Parameter
Description
Inter-MGW
route chain or
not, including:
INCHAIN
NO: The
outgoing route
chain got
from number
analysis is not
an inter-MGW
route chain.
YES: The
outgoing route
chain got
from number
analysis is
an inter-MGW
route chain
Instruction
It is used to specify whether the
outgoing route chain got from
number analysis is an inter-MGW
route chain. The system select
NO by default. If YES is selected,
the routes in the outgoing route
chains will not be selected for
the outgoing route. The outgoing
route will be got after perform
number analysis again according
to the associated called number
DAS configured in the outgoing
route chain.
This parameter is used in the
following cases:
One virtual outgoing route chain
is got based on number analysis
at first, and then the real outgoing
route is got based on the called
number DAS associated with the
virtual outgoing route chain.
When one MSCS controls multiple
areas, the outgoing route chain
facilitates subscriber management
RECMDMGWNODEID
Recommended
MGW nodes
It is used to specify the set of

recommended MGWs for outgoing
service. In the case of multiple IP
domains, if one MSCS manages
multiple MGWs, and these MGWs
belong to different IP domains,
the set of recommended MGWs
for outgoing service needs to be
configured. The MGW set here
should be a sub-set of the MGW
set supported by outgoing service.
by command ADD TOPO at first.
Then it can be indexed here
TABLE 111 CALL SERVICE TYPES

Call
Service
Types
244
Meanings
Description
NONE
Vacant number
Indicates that the subsequent call

procedures are processed based
on the procedure of processing
vacant numbers
LLC
Localnetwork localoffice/common
service

on the local service procedure
Call
Service
Types
Meanings
Description
LOL
Local-network
outgoing/localcall service
Indicates that the subsequent

call procedures are processed
based on the local-call service
procedure. The mobile-to-fixed
local outgoing call service is
usually analyzed to this type
LORU
Local-network
outgoing/rural
(network) call
service

based on the local rural (network)
outgoing call service procedure.
The mobile-to-fixed rural outgoing
call service is usually analyzed to
this type
DWTM
Domestic toll
(intra-region)
manual service

on the domestic toll (intra-region)
manual service procedure. In
general, it is not recommended to
configure this service type
DWTA
Domestic toll
(intra-region)
automatic
service

on the domestic toll (intra-region)
automatic service procedure. In
DBTM
Domestic toll
(inter-region)
manual service

on the domestic toll (inter-region)
manual service procedure. In
DBTA
Domestic toll
(inter-region)
automatic
service

on the domestic toll (inter-region)
automatic service procedure. The
domestic toll call service is usually
analyzed to this type
INTM
International
toll manual
service

on the international toll manual
service procedure. In general, it
is not recommended to configure
this service type
International
toll automatic
service

based on the international toll
automatic service procedure. The
international toll call service is
INTA
245
Call
Service
Types
Meanings
Description
Local-office paid
special service

based on the local-office paid
special service procedure. The
local-office paid special service is
Local-office free
special service

based on the local-office free
special service procedure. The
local-office free special service is
Outgoing paid
special service

on the outgoing paid special
service procedure. The outgoing
paid special service is usually
Outgoing free
special service

based on the outgoing free special
service procedure. The outgoing
free special service is usually
DEPS
Additional
service

based on the additional service
procedure. In general, it is not
recommended to configure this
service type
CENTL
Intra-office
call within
the CENTREX
business group

on the intra-office call procedure
within the CENTREX business
group.
CENTO
Outgoing call
within the
CENTREX
business group

on the outgoing call procedure
within the CENTREX business
group
TELCA
Intelligent
Ntwork service
call

on the intelligent network service
call procedure
EQACL
Equal access:
CIC of the
operator where
the subscriber is
located

based on the procedure of Equal
access: CIC of the operator where
the subscriber is located
LSPA
LSFR
OUPA
OUFR
246
Call
Service
Types
Meanings
Description
EQACO
Equal access:
non-localnetwork CIC

based on the procedure of Equal
access: non-local-network CIC
Tone play service, CAT_SEND_TONE

based on the tone play service
procedure. After calling the
number that is analyzed to this
type, the system will directly play
the tone according to the tone
ID configured in number analysis
result 1
Toll DDC
incoming call

based on the toll DDC incoming
call service procedure. The toll
incoming DDC call that needs to
be routed in the local office is
Local DDC call

on the local DDC call service
procedure. The local DDC call
(dialing the MSISDN number) that
needs to be routed in the local
office is analyzed to this type
Toll DDC
outgoing call

based on the toll DDC outgoing
outgoing DDC call is analyzed to
this type
Local DDC
outgoing call

based on the local DDC outgoing
call service procedure. The local
outgoing DDC call is analyzed to
this type
MSCO
MSC common
service

on the MSC common service
procedure. The call (dialing the
MSISDN number) that needs to
be routed in the local office is
MSLL
MSC localnetwork
local-office
service (only
for roaming
numbers)

based on the MSC local-network
local-office service procedure. It
is used to analyze the roaming
numbers and handover numbers
of the local office
STONE
DDCI
DDCC
DDCO
DDCCO
247
Call
Service
Types
Meanings
Description
MSLO
MSC local
outgoing
service (only
for roaming
numbers)

on the local outgoing service
procedure. The local outgoing call
of roaming numbers is analyzed
to this type
CINRE
Calling-number
incoming call
restriction

on the calling-number incoming
call restriction procedure
MSLTE
MSC national
toll call (only
for roaming
numbers)

based on the MSC national toll
outgoing call of roaming numbers
is analyzed to this type
AAC
Automatic
response
number

based on the automatic response
number service procedure
OVERLAY
prefix incoming
service

on the OVERLAY prefix incoming
service procedure. The OVERLAY
prefix incoming call is analyzed to
this type
OVCS
OVERLAY call
service

on the OVERLAY call service
procedure. It is used for the IGW
system
MSITE
MSC
international
toll call (only
for roaming
numbers)

based on the MSC international
toll call service procedure. The
international toll outgoing call is
IP
IP fixed service

on the IP fixed service procedure.
It is used for the IGW system
SSP
SSP charging
and querying
service

on the SSP charging and querying
service procedure.
NSSP
Non-SSP
charging and
querying service
Reserved
OVPRE
248
Call
Service
Types
Meanings
Description
IPMO
IP mobile
service

based on the IP mobile service
procedure. The IP service in the
mobile system is analyzed to this
type
INSIP
IP service dialed
by intelligentnetwork
subscribers
Reserved
ALIP
Independent IP
service

on the independent IP service
procedure. The independent IP
incoming call is analyzed to this
type
OVMO
OVERLAY:
MO-triggered
CAMEL service

on the OVERLAY: MO-triggered
CAMEL service procedure
OVMT
OVERLAY:
MT-triggered
CAMEL service

on the OVERLAY: MT-triggered
CAMEL service procedure
MNP
Mobile number
portability

on the MNP service procedure
MNPR
MNP MNP
outgoing routing

on the MNP outgoing routing
service procedure
SIPO
SIP outgoing
call

on the SIP outgoing call service
procedure
H323
H323 call

based on the H323 call service
procedure.
MOIMC
Mobile
emergency
special service

on the mobile emergency special
service procedure
249
Call
Service
Types
250
Meanings
Description
SSSP
Independent
SSP outgoing
service

based on the independent SSP
outgoing service procedure. The
SSSP (Independent SSP outgoing
service) in the analysis result of
the called number is used for the
IGW system
IGWA
IGW
supplementary
service (only for
IGW)

based on the IGW supplementary
service procedure
DASA
DAS service
(virtual IGW)
(only for IGW)
A new DAS is got through number

analysis, which is used for the
subsequent analysis of the called
number
OCIC
Local valid CIC

service

on the local valid CIC service
procedure. This parameter is
reserved
OUPAOD
Outgoing
paid special
service (can
be dialed by
the defaulting
subscribers)

on the outgoing paid special
service (can be dialed by the
defaulting subscribers) procedure
LINTS
Local-office
intelligent
service

on the local-office intelligent
service procedure. It is used for
the IGW system
SHLRQ
SHLR querying
service (only for
IGW)

on the SHLR querying service
procedure
IGWC
IGW common
service (only for
IGW)

based on the IGW common
service procedure. The call to
PHS subscribers, which needs to
be routed in the local office, is
ISSPQ
IGWSSP
charging and
querying service
(only for IGW)

on the IGW SSP charging and
querying service procedure
IGWLF
IGW local-office
free special
service

based on the IGW local-office free
special service procedure
Call
Service
Types
Meanings
Description
IGWLP
IGW local-office
paid special
service

based on the IGW local-office paid
special service procedure
IGWOV
IGWOVERLAY
prefix incoming
service

based on the IGWOVERLAY prefix
incoming service procedure
IGWDDCIN
IGW toll DDC

incoming call

on the IGW toll DDC incoming call
service procedure
IGWDDCLOCAL
IGW local DDC

call

on the IGW local DDC call service
procedure
Test call

on the test call service procedure.
It is used to analyze test calls
TEST
TABLE 112 ENABLED OPTIONS

Enabled
Options
CCS7
CHGK
Meanings
Description
Automatically sending
the calling number when
using CCS7 for outgoing
services

outgoing TUP signaling
carries the calling
number. When the local
office actively sends the
calling number, it sends
an IAI message of TUP
signaling to the peer-end
office, carrying the calling
number. Otherwise, the
local office sends an
IAM message of TUP
signaling to the peer-end
office, not carrying
the calling number.
For ISUP signaling, it
indicates whether the
local MSC number is filled
in the location number
information
Changing the type of

calling subscribers
Indicates whether to
set the type of the
calling subscriber in the
outgoing IAM message of
ISUP or BICC signaling
to the calling subscriber
types flexibly configured
in security variables
251
Enabled
Options
Meanings
Description
CHGN
Changing the number
Indicates that the

analyzed number is
changed, and the system
notifies the calling
subscriber by playing
the tone
DELA
Delayed dialing of the

special service
Reserved
MAIL
166-voice-mailbox
service
Indicates that the call

is a 166-voice-mailbox
service
NSCP
Not waiting for SCP

responses
Reserved
RRTO
Rerouting after outgoing

failure
For incoming calls

using ISUP, TUP, or
BICC signaling, the
call procedure is an
outgoing call procedure.
When the local office
does not receives a REL
message after sending an
outgoing IAM message to
the peer-end office, this
option control whether
rerouting is allowed
NETF
IN forward message
Reserved
VNUM
Virtual number
Reserved
HRA
High rate
Reserved
NUMLEN
Estimate Number Length
Estimate Number Length
CEC
Charge as emergency
call
Charge as emergency
call
NOLMTLEN
No Limited Time Length

For Tone
No Limited Time Length

For Tone
IGFWD
Ignore Redirection Info

In Outgoing Call
Ignore Redirection Info

In Outgoing Call
ECL
Use Emergency Call Level
Use Emergency Call Level
Not triggering IN service

of the calling number
Indicates whether the

call triggers the IN
service of the calling
number. This option is
used for the case where
the IN service of the
calling number cannot
be triggered when the
call to the IN subscriber
is forwarded or when
some special numbers
are dialed
NTC
252
Enabled
Options
Meanings
Description
NCEL
No call when the called

number exceeds the
length

system releases the call
if the analyzed number
exceeds the configured
maximum digit length
Interception number
incoming

call is an incoming
call returned from the
interception center. This
option is only used in the
IGW system
Sending the connect

message in advance
(only for IGW)

local office sends a
ringing message of the
called subscriber and a
connect message to
the calling subscriber
at the same time (that
is, sends a connect
message to the calling
subscriber before the
called subscriber answers
the call). This option is
only used in the IGW
system
Not triggering SHLR

query

number section needs
to be transformed in
the SHLR during call
origination. In the
SHLR mixed networking,
common call origination
procedures need to
interact with the SHLR
to get the calling
logic number, and the
called physical number.
However, in the specific
calls, the called number
needs no transform. In
this case, select this
option in the number
analysis result. This
IGW system
Over net number in SHLR

incoming call restrain
the SHLR from returning
the IN access code. This
option is used to prevent
repeatedly triggering IN
services. This option is
only used in the IGW
system
LSIN
CON
SHLRF
SHLRG
253
Enabled
Options
JUDG
REBO
Meanings
Description
Needing to judge the IP

resource

routing query in the SHLR
is forcibly performed
during IP calls. This
IGW system
Restraining HOMEBOX
service
Indicates whether
incoming calls trigger
the HOMEBOX service
in the local office. This
IGW system
Example: Configure the called number analysis with the following requirements.
Analyzer entry: 1
User alias: TPDNAL1
Call service type: MSC common service
The command is:

ADD TPDNAL:ENTR=1,DIGIT="13902099",NAME="TPDN
AL1",SPECRST=0,SPECIDX=0,CAT=MSCO,RST1=0,RST2
=0,RST3=0,CHAINAL=0,RNLEN=0,MINLEN=3,MAXLEN
=20,OVLYPRI=HCSI,REL=NO,NET=1,NAT=DEF,OPDDIC
ONT=NO,TPDDICONT=NO,OPDDI=0,TPDDI=0,OPDLYD
DI=0,TPDLYDDI=0,DDIOVERB=0,IWVIDEO=LSUP,TIME
LMT=0,AUXDAS=0,A6=0,PFXLEN=0,INSRV=INM,FAXID
X=0,AVIDX=0,DVIDX=0,ADATAIDX=0,DDATAIDX=0,D
Example: Configure the roaming number analysis of the local
office with the following requirements.
Analyzer entry: 1
User alias: TPDNAL1
Call service type: MSC local service
The command is:

ADD TPDNAL:ENTR=1,DIGIT="15902099",NAME="TPDN
AL2",SPECRST=0,SPECIDX=0,CAT=MSLL,RST1=0,RST2
=0,RST3=0,CHAINAL=0,RNLEN=0,MINLEN=3,MAXLEN
=20,OVLYPRI=HCSI,REL=NO,NET=1,NAT=DEF,OPDDIC
ONT=NO,TPDDICONT=NO,OPDDI=0,TPDDI=0,OPDLYD
DI=0,TPDLYDDI=0,DDIOVERB=0,IWVIDEO=LSUP,TIME
LMT=0,AUXDAS=0,A6=0,PFXLEN=0,INSRV=INM,FAXID
254
X=0,AVIDX=0,DVIDX=0,ADATAIDX=0,DDATAIDX=0,D
END OF STEPS
255
256
Chapter
Tone Configuration
Table of Contents
Creating MSCS Tones in Batches........................................ 257
Creating the Fixed Tone Play Data...................................... 258
Creating the Basic Service Tone Play Data........................... 265
Creating the Intelligent Service Tone Play Data .................... 274
Creating MSCS Tones in

Batches
Prerequisites

Context
The NetNumen M30 network management system provides the

function of quickly creating tone play data in batches, avoiding
low efficiency, and the error-prone problem of the manual setting.
Since most of the tones in the system have been clearly defined in
the related protocols and national standard, it is suggested to configure tone play data through this function in practical use. In case
of special requirements, adjust different system tones according
to different services.
Note:
During batch deletion, delete the MGW static data first; otherwise,
the system will prompt that The tone play template No. is being
used by the MGW static data, so it cannot be deleted.
Steps

system tree.
SET:NEID=11;
2. Create MSCS tones in batches.
STONE.
The command is BADD
Table 113 describes the main parameters in the BADD STONE

command.
257
TABLE 113 PARAMETERS IN THE BADD STONE COMMAND

Parameter
Name
Instruction
Voice type, includes
TYPE
ALL: all configuration of

tone
ICP: tone service
KD: the relationship

between the call type
and the KD
LANGDES: language
description string
MSGID: external MSGID,

relation to inter service
key
TONEID: the service

tone ID to the protocol
package
TONEIN: service key and

its relation to tone ID
TONEPLAYMT: the
method of playing tones
Select it
according to the
actual condition.
Example: Create the batch processing of all the MSCS tones.

BADD STONE:TYPE=ALL;
3. After completing the tone play data configuration on both the
MSCS and the MGW, perform the dial test to check whether the
system can correctly play tones.
END OF STEPS
Creating the Fixed Tone

Play Data
Prerequisites
Context
The NMS system works properly, and the client logs in to the
server.
The physical data configuration is complete, and the TONE-type

MRB board is created on the MGW.
1. Description of the tone play data of fixed tones on the MSCS
258
ToneID: ID of a service tone in the MSCS system. The

ToneID of fixed tones ranges from 1 to 99.
Tone package type (TonePro): a parameter defined in the
H.248 protocol. It is specified in the Q.1950 protocol that
the tone packages of fixed tones are divided into two types,
Chapter 4 Tone Configuration
BCG (Basic Call Progress Tones Generator with Directionality) and XCG (Expanded Call Progress tones Generator
Package). Each fixed tone must belong to one of them.
Service tone No. in the tone package (PKGID): a parameter

defined in the H.248 protocol, used to distinguish different
service tones in the same type of tone packages.
In the actual configuration, perform the configuration according to the tones supported by the system.
2. Description of the tone play data of fixed tones on the MGW
ToneID: same with that of the MSCS.
Tone package type (TonePro): same with that of the MSCS.
Service tone No. in the tone package (PKGID): same with

that of the MSCS.
Frequency point: an internal ID in the MGW, associated
with the frequency point No. in the code dot information
configuration. Through it, the play frequency, volume, and
the circuit type of the fixed tone can be indexed.
Play duration: the duration of playing a part of tone at a
frequency of a fixed tone. A fixed tone is played in series
based on the duration of each frequency. The play period
of a fixed tone equals to the sum of durations of all frequencies.
Frequency: tone frequency of a fixed tone.
Volume: volume
Circuit type: PCM compression mode of a fixed tone, including A law and u law
The MRB board circularly plays tones according to the configured duty ratio. If there is phase and amplitude saltus
between the first dot and the last one of the code dots of the
tone generated according to a special frequency f, noise will
occur when the MRB board circularly plays the tone. The
background generates single-frequency tones according to
COS (fL)/4000, where is the constant of circumference ratio, f is the frequency for generating fixed tones,
and L is the code dot length. fL/4000 must be an integer,
so that the generated fixed tone can be circularly played
without interruption. Therefore, during the configuration,
it is required to confirm whether to select 640 bytes or 800
bytes for the fixed code dot length according to the frequency.
3. Brief introduction to data association

The MSCS translates the ToneID generated by the service into
the exclusive combination of TonPro and PKGID, and transfers
it the MGW.
The MGW translates the exclusive combination of TonePro and
PKGID into the ToneID. It gets the frequency point and play
duration according to the ToneID, and then gets the actual frequency, volume, circuit type of the tone play according to the
frequency point.
This topic introduces how to create tone play data for a fixed tone,
taking the ring back tone as an example. The fixed tone play data
259
configuration is used to implement the function of playing fixed

tones.In normal cases, the fixed tone configuration data can be
created in batches. In case of special requirements, it is required
to separately configure the fixed tone play data.
Steps

system tree.
SET:NEID=11;
2. Create a tone ID. The command is ADD TONEID.
Table 114 describes the main parameters in the ADD TONEID
command.
TABLE 114 PARAMETERS IN THE ADD TONEID COMMAND FOR
FIXED TONES
Parameter
Name
TPLID
TONE
Parameter
Descriptions
Instruction
Playback template
index number
Numbered from 1,
used in MGW static
data configuration
(ADD MGSCFG), and
determining the played
tones supported by the
MGW
Tone ID
Tone ID self-defined in
ZXWN, for internal use.
It is usually consistent
with the internal Tone ID
of the MGW. Refer to the
corresponding tone list of
the Tone ID to configure
it. The TONEID of the ring
back tone is 2.
Tone package type,

including:
CG (CG package)
CT (CT package)
AU (AU package)
AN (AN package)
BCG (BCG
package)
XCG (XCG
package)
THREEGXCG
(THREEGXCG
package)
AASB (AASB
package)
AASDC (AASDC
package)
PKG
260
A parameter defined
in the H.248 protocol,
for classifying tones in
the H.248 protocol. For
details, see the contents
in the H.248 protocol.
The tone package type
of the ring back tone is
BCG (Basic Call Progress
Tones Generator with
Directionality)
Parameter
Name
Parameter
Descriptions
Instruction
132 (132 package)
INPKGID
Tone ID in the tone

package
A parameter defined in the

H.248 protocol, specifying
the number of a tone in
the specific type of tone
package. For details, see
the contents in the H.248
protocol. The number of
the ring back tone in the
BCG package is 65.
ID
ID
Used to specify the ID of

this service tone
URL
URL address/character
string code
corresponded by the
service tone
Used to specify the

corresponding URL
address of this service
tone. In general, only AN
and AASB packages need
to be configured.
For example, create a service tone ID with the following requirements.
Tone play template index: 1
Service tone ID: 2
Tone package type: BCG
Service tone No. in this tone package: 65
ID: 2

ADD TONEID:TPLID=1,TONE=2,ANARSLT=EOTA,PKG=B
CG,INPKGID=65,ID=2;
Example: Select the MGW exchange with ID as 31 from the
system tree.
SET:NEID=31;
4. Create a service-tone-to-protocol-tone-package configuration.
The command is ADD TONEPRO.
Table 115 describes the parameters in the ADD TONEPRO
command.
261
TABLE 115 PARAMETERS IN THE ADD TONEPRO COMMAND

Parameter
Name
Parameter
Description
Instruction
SN
Used to define a service-toneID-to-protocol-tone-package

configuration in the system. It
is of a unified number globally,
PKGTP
Package type
A parameter defined in the H.248

protocol, for classifying tones in
the H.248 protocol. For details,
see the contents in the H.248
protocol. The tone package
type of the ring back tone is
BCG (Basic Call Progress Tones
Generator with Directionality)
TPRO
Service
tone type,
corresponding
to the INPKGID
parameter
in the ADD
TONEID
command on
the MSCS
A parameter defined in the H.248

protocol, specifying the number
of a tone in the specific type of
tone package. For details, see the
contents in the H.248 protocol.
The number of the ring back tone
in the BCG package is 65.
Tone ID
Tone ID self-defined in ZXWN,

for internal use. It is usually
consistent with the internal Tone
ID of the MSCS. Refer to the
corresponding tone list of the
Tone ID to configure it. The
TONEID of the ring back tone is 2.
ANSPEC
Service key
code

H.248 protocol, corresponding to
the URL parameter in the ADD
TONEID command on the MSCS,
which does not take effect during
configuring fixed tones. Configure
it to 1.
SKEY
Service key
The internal service key in ZXWN.

The fixed tones belong to basic
service tones, and the service key
is 1.
NAME
Alias
Used to specifically describe the

configuration of a service tone ID
to make it easily recognized.
TPROID
TONE
For example, create ring-back-tone-to-protocol-tone-package

configuration with the following requirements.
262
ID: 1
Package type: BCG
Service tone ID: 2
Service key: 1
Alias: RingbackTone

ADD TONEPRO:TPROID=1,PKGTP=BCG,TPRO=65,TONE
=2,ANSPEC="1",SKEY=1,NAME="RingbackTone";
5. Create a tone frequency. The command is ADD CODEDOTS.
Table 116 describes the parameters in the ADD CODEDOTS
command. The ring back tone includes mute and 450 Hz tone.
First set the frequency and volume for the mute, and then set
the frequency point information for the 450 Hz tone.
TABLE 116 PARAMETERS IN THE ADD CODEDOTS COMMAND
Parameter
Name
Parameter
Description
Instruction
FREQ
Frequency point No..

Specify the frequency
of tone play and
number it globally
Set it according to the

plan.
CDFREQ
Code point frequency

(Hz)
Select it according to the

actual conditions.
DECIBEL
Code point volume

(Db)

actual conditions.
Circuit type, including

A law and u law
The circuit type of

all records must be
configured to be the
same, being A law or u
law instead of both
CDLEN
Code point byte

stream length, which
can be 640 bytes or
800 bytes
When no code point

byte stream length is
entered, the system
will set a default value
according to the circuit
type, 640 for A law, and
800 for u law. A/u law
and code point length
can be specified at the
same time.
NAME
Alias
Specifically describes
the language description
string to make it easily
recognized
CTYPE
Note:
The MRB board circularly plays tones according to the configured duty ratio. If there is phase and amplitude saltus between
the first dot and the last one of the code dots of the tone generated according to a special frequency f, noise will occur when
the MRB board circularly plays the tone.
The background generates single-frequency tones according to
COS (fL)/4000, where is the constant of circumference
ratio, f is the frequency for generating fixed tones, and L is the
263
code dot length. fL/4000 must be an integer, so that the generated fixed tone can be circularly played without interruption.
For
double-frequency
or
multiple-frequency
tones,
they are generated according to COS(f1L)/4000+
COS(f2L)/4000++ COS(fnL)/4000. In this case, all
fL/4000s must be integers.
For example, create a frequency for the ring back tone with
Frequency No.: 9
Code point frequency: 440 Hz and 480 Hz
Code point volume: 16Db
Circuit type: A law
Code point byte stream length: 800 bytes
Alias: RingbackTone

ADD CODEDOTS:FREQ=9,CDFREQ="440"&"480",DECIBEL
=-16,CTYPE=A,CDLEN=800,NAME="RingbackTone";
6. Create a fixed tone. The command is ADD FIXTONE.
The ADD FIXTONE command is used to set the frequency
point information included by the fixed tone, and the play duration of each frequency point. The explanation of the main
parameters is described in Table 117.
TABLE 117 PARAMETERS IN THE ADD FIXTONE COMMAND
Parameter
Name
TONE
FRDU
NAME
Parameter
Description
Instruction
Service Tone ID
Used to define a service

tone ID configuration
in the system. This
parameter ranges from 1
to 50. and is of a unified
number in the entire
office.
Frequency point and

duration (in 10 ms)
Frequency point uses

the frequency point No.
defined in the ADD
CODEDOTS command.
Configure the duration
according to the actual
conditions.
Alias
recognized
For example, create a ring back tone with the following requirements.
264
Service tone ID: 2
Frequency point: 9-40
Duration: 0-20
Alias: RingbackTone.

ADD
FIXTONE:TONE=2,FRDU="9"-"40"&"0"-"20",NAME
="RingbackTone";
7. Transfer data to the foregrounds of the MSCS and the MGW.
Dial a local mobile phone to test whether the ring back tone is
properly played.
END OF STEPS
Creating the Basic Service

Tone Play Data
Prerequisites
Context
server.

Each kind of tone play requirement and the corresponding relationship between basic tones in the version are planned well
in the local office.
1. Description of the tone-play data of basic service tones on the

MSCS
ErrCode: When a service fails, the system will exclusively

identify the service failure according to the ErrCode, which
is the initial condition of the basic service tone play. The
MSCS confirm the ToneID based on the above information.
ToneID: ID of a service tone in the MSCS system. The
Tone package type (TonePro): a parameter defined in the
H.248 protocol. It is specified in the H.248.7 protocol that
the tone package type of basic service is an.
Service tone No. in the tone package (PKGID): a parameter
defined in the H.248 protocol, used to distinguish different
service tones in the same type of tone packages. For the
allocation of PKGID, refer to the H.248 protocol.
Language type: language type of service tones, such as
English, Chinese, first Chinese and then English.
Play duration: tone play period.
Play times: times of playing tones.
Play interval: interval between two times of playing tones.
Notify that the tone play is complete: Whether to notify the

MSCS after tone play.
265

MGW
ToneID: ID of a service tone in the MGW system.

Tone package type (TonePro): same with that of the MSCS.

Service tone No. in the tone package (PKGID): same with
that of the MSCS.
Language type: same with that of the MSCS.
Play duration: same with that of the MSCS.
Play times: same with that of the MSCS.
Play interval: same with that of the MSCS.
The
Notify that the play is complete: same with that of the

MSCS.
Service key: The ZXWN system defines an ID for each service. The tone play types for different services are different. The service key of the basic services is fixed as 1. The
service key of each tone subunit is configured in the network management system, determining the service tone
type of the tone subunit.
Fixed tone elements and variable tone elements: In the
same service, tone elements are used to distinguish different tones. After finding the subunit of the tone resource,
the system can play the tone on the subunit according to
fixed tone elements and variable tone elements.
Unit No.: associated with the unit No. of the MRB board in
the physical configuration in the ZXWN network management system, and used to address the MRB board playing
the tone during the tone play.
Subunit No.: associated with the subunit No. of the MRB
board in the physical configuration in the ZXWN network
management system. The subunits of the MRB board can
be configured to TONE, DTMF, and MFC. Only the subunit
of TONE type can be used to play tones. The service key
of each subunit of TONE type should be configured on the
network management system.

The MSCS translates the ErrCode generated by the service processing module into the ToneID. Then it translates the ToneID
into the exclusive combination of TonePro and URL, and translates the language type, play method, and other parameters
of the basic services at the same time. It transfers TonePro,
URL, language type, and the play method to the MGW.
URL into the ToneID and the service key, translates the language type to that on the MGW, and saves the play method.
It gets the tone element component (fixed tone elements and
variable tone elements) according to the ToneID and the language type, and gets the tone unit No. and the subunit No.
according to service key 1 of the basic services.
The basic service tone play data configuration is used to implement
the function that the system automatically plays the related tone
266
when a basic call service fails. For example, the system plays the
invalid number tone when a subscriber dials an incorrect number,
and ringing-time-out tone when the called subscriber makes no
reply for a long time. In normal cases, the basic service tone
play data can be created in batches. This topic introduces how to
configure the tone play data for a basic tone, taking the vacant
number tone as an example.
Steps

system tree.
SET:NEID=11;
2. Create a voice service. The command is ADD TONESRV.
Table 118 describes the parameters in the ADD TONESRV
command.
TABLE 118 PARAMETERS IN THE ADD TONESRV COMMAND
Parameter
Name
FAILCODE
Parameter
Description
Instruction
Tone play cause
Enter it according to the

error code returned by
the service processing
module.
Analysis result,
including:
EOTA: End
analysis
CONT: Number
analyzed
subsequently
ANARSLT
TONE
Tone ID

actual conditions.
of the MGW.
Service tag provided

in the call failure
code, including:
SRVTAG
TONESIG
(Sending tone
signal between
offices): Sending
tone signal to the
calling side.
ACKSIG
(Sending the
called-partyanswering signal
to the calling
side): Sending
false answering
It is an optional
parameter, which is of
enumeration type, with a
default of TONESIG.
267
Parameter
Name
Parameter
Description
signal to the
calling side.
Instruction
PLAYFLG:
Meaning whether
to set the tone
play duration and
times according
to the service
tones.
Alias
Specifically describes the

voice service to make it
easily recognized
ITERR
Iteration times

times of this failure tone
to be played repeatedly,
with a default of 0. It is
invalid to the fixed failure
tone.
DURATION
Playback duration (s)
It is used to specify
the play duration of
this failure tone, with a
default of 0.
NAME
For example, create a vacant-number-tone service with the

Call failure code: 4005
Analysis result: end of tone analysis
Service tone ID: 101
Service tag provided to subscribers in the call failure code:

TONESIG
Alias: "Invalid Number Tone"
Play times of failure tones: 5
Play duration of failure tones: 10 seconds

ADD TONESRV:FAILCODE=4005,ANARSLT=EOTA,TONE
=101,SRVTAG="TONESIG",ITERR=5,DURATION=10;
3. Create a tone ID. The command is ADD TONEID.
Table 119 describes the parameters in the ADD TONEID command.
268
TABLE 119 PARAMETERS IN THE ADD TONEID COMMAND

Parameter
Name
TPLID
Parameter
Description
Instruction
Playback template
index number
Numbered from 1, used

in MGW static data
configuration (ADD
MGSCFG), and determining
the played tones supported
by the MGW
Analysis result,
including:
EOTA: End
analysis
CONT: Number
analyzed
subsequently
ANARSLT
TONE
Tone ID

actual conditions.
ZXWN, for internal use. It is
usually consistent with the
internal Tone ID of the MGW.
Refer to the corresponding
tone list of the Tone ID to
configure it.
Tone package type,

including:
PKG
INPKGID
CG (CG package)
CT (CT package)
AU (AU package)
AN (AN package)
BCG (BCG
package)
XCG (XCG
package)
THREEGXCG
(THREEGXCG
package)
AASB (AASB
package)
AASDC (AASDC
package)
132 (132
package)
Tone ID in the tone

package
A parameter defined in
the H.248 protocol, for
classifying tones in the
H.248 protocol. For details,
see the contents in the
H.248 protocol.
This parameter is invalid for

basic service tones.
269
Parameter
Name
Parameter
Description
Instruction
ID
ID
Used to specify the ID of this

service tone
URL
URL address/character string code

corresponded by the
service tone
Used to specify the

corresponding URL address
of this service tone. In
general, only AN and
AASB packages need to be
configured.
For example, create an ID for the vacant number with the following requirements.
ToneID: 101
Tone package type: AN
Corresponding URL: cmcc_bs_101

ADD
TONEID:TPLID=1,TONE=101,ANARSLT=EOTA,PK
G=AN,INPKGID=101,ID=101,URL="cmcc_bs_101",NAME
="Invalid Number Tone";
4. Create the play method for service tones. The command is
ADD TONEPLAYMT.
Table 120 describes the parameters in the ADD TONEPLAYMT
command.
TABLE 120 PARAMETERS IN THE ADD TONEPLAYMT COMMAND
FOR BASIC SERVICE TONES
270
Parameter
Name
Parameter
Description
Instruction
SRVKEY
Service key
The basic service key is TRDT.
LANG
Language type
Selected according to the

actual requirements. For
example 4097 (First Chinese
and then English)
ITERR
Iteration times

actual requirement, such as 5
times.
DURATION
Playback
duration(s)

actual requirement, such as
15 seconds.
CMP
Notify that the tone

play is complete,
indicating whether
to notify the MSCS
after tone play

actual requirements. For the
vacant number tone, it is
required to set notifying the
MSCS after tone play.
For example, create a tone play method for the vacant number
tone with the following requirements.
Service key: traditional service TDRT
Language type: 4097 (First Chinese then English)
Tone play times: 5
Tone play duration: 15 seconds.

ADD
TONEPLAYMT:SRVKEY=TRDT,LANG=4097,ITERR
=5,DURATION=15,INTERVAL=1,CMP=YES;
system tree.
SET:NEID=31;
6. Create a service-tone-to-protocol-tone-package configuration.
The command is ADD TONEPRO.
Table 121 describes the parameters in the ADD TONEPRO
command.
TABLE 121 PARAMETERS IN THE ADD TONEPRO COMMAND
Parameter
Name
Instruction
PKGTP
Service tone type,

corresponding to the
PKG parameter in
the ADD TONEID
command on the MSCS
A parameter defined
TPRO
Service tone type in the

protocol
This parameter is invalid

for basic service tones.
Configure it to 1.
Tone ID
with the internal Tone
ID of the MSCS. Refer to
the corresponding tone
list of the Tone ID to
configure it.
ANSPEC
Service tone number in

the protocol
A parameter defined
corresponding to the
URL parameter in the
ADD TONEID command
on the MSCS.
SKEY
Service key
An internal service key.

The service key of the
basic service tones is 1.
TONE
271
For example, create the vacant-number-ToneID-to-protocol

tone package configuration.
ToneID: 101
Tone packet type: AN
Corresponding URL: cmcc_bs_101.

ADD
TONEPRO:TPROID=24,PKGTP=AN,TPRO=1,TON
E=101,ANSPEC="cmcc_bs_101",SKEY=1,NAME="Invalid
Number Tone";
7. Create the tone-language comparison configuration. The command is ADD LANGSTR.
Table 122 describes the parameters in the ADD LANGSTR
command.
TABLE 122 PARAMETERS IN THE ADD LANGSTR COMMAND
Parameter Name
Parameter
Description
Instruction
Language Descriptor
Kept to be consistent with the

LANG parameter in the ADD
TONEPLAYMT command,
and analyzing the language
character string.
LG1
Language 1
Configured according to the

actual situation, such as Eng,
where language 1 is ENG
(English)
LG2
Language 2

actual situation
LG3
Language 3

actual situation
LG4
Language 4

actual situation
LG5
Language 5

actual situation
LGSTR
For example, create the vacant-number-tone-language comparison configuration with the following requirements.
Language descriptor: Eng
Language 1: English

ADD
LANGSTR:LGSTR="EN",LG1=Eng,LG2=INVALID,LG
3=INVALID,LG4=INVALID,LG5=INVALID,NAME="Invalid
Number Tone";
8. Create a tone ID and tone element composition configuration.
The command is ADD TONELIST.
Table 123 describes the parameters in the ADD TONELIST
command.
272
TABLE 123 PARAMETERS IN THE ADD TONELIST COMMAND

Parameter Name
Parameter
Description
Instruction
TONE
Tone ID
Enter the ToneID, which is 101 for

the vacant number tone.
LANG
Language type
Enter the language type of the

service tone (EN)
KIND
Tone type
Select Exclu for the vacant number

tone
For example, create composition of the vacant number toneID

and tone element, and add the English tone element components of the vacant number tone. The specific command is as
follows.
ADD TONELIST:TONE=101,LANG=Eng,KIND=Exclu,ST1
=0,ST2=0,ST3=0,ST4=0,ST5=0,VTP1=Invalid,VTP2=Inval
id,VTP3=Invalid,VTP4=Invalid,VTP5=Invalid,CD1=65535,C
D2=65535,CD3=65535,CD4=65535,CD5=65535,CD6=655
35,NAME="Invalid Number Tone";
9. Create a service key configuration on the tone board. The command is ADD TONESVC.
Table 124 describes the parameters in the ADD TONESVC
command.
TABLE 124 PARAMETERS IN THE ADD TONESVC COMMAND
Parameter
Name
Parameter
Description
Instruction
UNIT
MRB unit No.
Enter the MRB unit No.
SUNIT
Tone subunit No. in

the MRB
Enter the tone subunit

No.
SKEY1
Service key
Enter basic service key 1
SKEY2
Service key
SKEY3
Service key
SKEY4
Service key
SKEY5
Service key
SKEY6
Service key
For example, create the service key configuration on the tone

board in the MGW office with the following requirements. Configure service key 1 of the basic services on the TONE subunit
of the MRB board. The specific command is as follows.
ADD
TONESVC:UNIT=221,SUNIT=9,SKEY1=1,SKEY2
=0,SKEY3=0,SKEY4=0,SKEY5=0,SKEY6=0;
273
10. Transfer data to the foregrounds of the MSCS and the MGW.
Dial a local mobile phone to test whether the ring back tone is
properly played.
END OF STEPS
Creating the Intelligent

Service Tone Play Data
Prerequisites
Context
server.

The MTP interconnection data configuration and the SCCP data

configuration with the SCP are complete.
The service keys and EMIDs are planned together with the SCP.

MSCS
External EMID: A tone parameter in PA operations, which

can exclusively identify the contents and the language type
of the tone to be played between the SCP and the MSCS.
This parameter is determined by the SCP, and sent to the
SSP.
Internal EMID: the EMID defined by ZTE. Its coding standard is shown in Figure 12.
FIGURE 12 CODING STANDARD
OF THE
INTERNAL EMID
External service key: The service key delivered by the

SCP. It is contained in the EMID, which consists of the 8
most significant bits in the internal EMID.
Internal service key: IDs of different intelligent service
in ZTE, which is the highest in the internal EMID code.
Other parameters are the same with those of the basic service tone play.
2. The intelligent service tone play data on the MGW are the same
with the basic service tone play data on the MGW.
274
The MSCS translates the external EMID sent from the SCP into
the internal EMID, and finds the external service key, language
type, and the record notification No. according to the EMID.
Then it translates the external service key into the internal
service key, and gets the play method of the corresponding intelligent service tone. It gets ToneID according to the service
tone notification No. and the service key, translates the ToneID
into the exclusive combination of TonePro and URL, and translates the language type, play method, and other parameters
of the intelligent services at the same time. Then it transfers
the TonePro, URL, language type, and the play method to the
MGW.
The intelligent service tone play procedure of the MGW is the
same with the basic service tone play procedure of the MGW.
URL into the ToneID and the service key, translates the language type to that on the MGW, and saves the play method.
It gets the tone element components (fixed tone elements and
variable tone elements) according to the ToneID and the language type, and gets the tone unit No. and the subunit No.
according to service key of the intelligent services.
The intelligent service tone play data configuration is used to enable the ZXWN CS equipment to play intelligent service tones,
complete the SRF function, and implement the function that the
system can play the related intelligent service tone based on the
EMID sent from the SCP. This topic introduces how to configure
the tone play data for the intelligent service.
Steps

system tree.
SET:NEID=11;
2. Create MSGID conversion. The command is ADD EMIDTRF.
Table 125 explains the parameters in the ADD EMIDTRF command.
275
TABLE 125 PARAMETERS IN THE ADD EMIDTRIF COMMAND

Parameter
Name
Parameter
Description
Instruction
EMID
ID of external message
Used to specify the

EMID to be converted
SRVKEY
Service key
Used to specify the

external service key to
which the EMID is to be
converted
Code in the service key
Used to specify the

radio access mode
applied to the handover
policy
MID
Language type,
including:
MIXED: indicates
that the language
type is mixed tone.
MANDARIN:
indicates the
language type is
mandarin.
LANG
EN: indicates the

language type is
English.
LOCAL: indicates
the language type
is local language
Select it according to
the actual condition.
Tip:
MSGID (MSGID conversion) can be added in batches through
Dev Configuration > Tone Configuration > Tone Batch
Operation > Batch Create MSCS Tone (BADD STONE) on
the MML Terminal window.
For example, create MSGID conversion with the following requirements.
External message ID: 201
Service key: 1
Code in the service key: 1
Language type: English.

ADD EMIDTRF:EMID=201,SRVKEY=1,MID=1,LANG=EN;
3. Create the interconnection conversion for service keys. The
command is ADD SVRTRANSKEY.
Table 126 describes the parameters in the ADD SVRTRANS
KEY command.
276
TABLE 126 PARAMETERS IN THE ADD SVRTRANSKEY

COMMAND
Parameter
Name
Parameter
Description
Instruction
EXSVCKEY
External service key

coding
Specifies the code of an

external service key
SVCKEY
Service Key Codes
Specifies a service key

code in the system
NAME
Alias
the service key
interconnection
conversion to make
it easily recognized
ID
ID
Defines the service

key interconnection
conversion in the system
SCPTYPE
SCP type
Used to specify the SCP

type
Service key
description
Used to specifically
describe the
corresponding service
key to make it easily
recognized
SVCKEYDES
For example, create the service key interconnection conversion

External service key No.: 11
Service key No.: PPS service
Alias: "PPS service"
Configuration ID: 1
SCP type: 0

ADD SVRTRANSKEY:EXSVCKEY=10,SVCKEY=PPS,NAME
="PPS Service",ID=1,SCPTYPE=0;
4. Create service-key-to-service-tone-ID configuration.
command is ADD TONEIN.
The
Table 127 describes the parameters in the ADD TONEIN command.
277
TABLE 127 PARAMETERS IN THE ADD TONEIN COMMAND

Parameter
Name
Instruction
SVCKEY
Service Key Codes
Specifies a service key

code in the system
MID
The code in the service

key
Specifies the code of

the service tone in the
corresponding service
key
Analysis result,
including:
ANARSLT
TONEID
ID
NAME
EOTA: End analysis
CONT: Number
analyzed
subsequently
Select it according to
the actual conditions.
Tone ID
Used to specify the ID

of the service tone
ID
Used to define
the service key
interconnection
conversion in the
system
Alias
Used to specifically
describe the service
key interconnection
conversion to make it
easily recognized
For example, create service-key-to-service-tone-ID conversion

configuration with the following requirements.
Service key codes: PPS service
Code in the service key: 1
Service tone ID: 201
The No. is tone 20001.

ADD TONEIN:SRVKEY=PPS,ANARSLT=EOTA,MID=1,TON
EID=201,ID=20001;
5. Create a tone ID. The command is ADD TONEID. Configure
the ToneID, the corresponding protocol tone package type, and
the corresponding URL of the service tone.
Table 128 describes the parameters in the ADD TONEID command. This step of configuration mainly aims to configure the
tone play method for the intelligent service on the MSCS.
278
TABLE 128 PARAMETERS IN THE ADD TONEID COMMAND

Parameter
Name
TPLID
TONE
Parameter
Description
Instruction
Playback template
index number
Numbered from 1,
used in MGW static
data configuration
(ADD MGSCFG), and
determining the played
tones supported by the
MGW
Tone ID
of the MGW. Refer to the
corresponding tone list of
the Tone ID to configure it.
Tone package type,

including:
PKG
CG (CG package)
CT (CT package)
AU (AU package)
AN (AN package)
BCG (BCG
package)
XCG (XCG
package)
THREEGXCG
(THREEGXCG
package)
AASB (AASB
package)
AASDC (AASDC
package)
132 (132
package)
A parameter defined
INPKGID
Tone ID in the tone

package

H.248 protocol, specifying
the number of a tone in
the specific type of tone
package. For details, see
the contents in the H.248
protocol.
URL
URL address/character string code

corresponded by the
service tone
Used to indicate the

corresponding URL
address of the service
tone. In general, only AN
and AASB packages need
to be configured.
6. Create the play method for service tones. The command is

ADD TONEPLAYMT.
279
Table 129 describes the parameters in the ADD TONEPLAYMT

command. This step of configuration mainly aims to configure
the tone play method for the intelligent service on the MSCS.
TABLE 129 PARAMETERS IN THE ADD TONEPLAYMT COMMAND
Parameter
Name
Parameter
Description
Instruction
SRVKEY
Service key

actual requirement.
LANG
Language type

actual requirements. For
example 4097 (First
Chinese and then English)
ITERR
Iteration times

5 times.
DURATION
Playback duration

15 seconds.
CMP
Notify that the tone

play is complete,
indicating whether
to notify the MSCS
after tone play

actual requirement.
7. Create the language description string. The command is ADD

LANGDES.
Table 130 explains the parameters in the ADD LANGDES command. This step of configuration mainly aims to configure the
language translation data on the MSCS.
TABLE 130 PARAMETERS IN THE ADD LANGDES COMMAND
Parameter
Name
Parameter
Description
Instruction
TPLID
Language template
No.
Used to specify the template

No. of the language
description string
LANG
Language type
Used to specify the language

type
LANGDES
Language
description string
Used to specify the

corresponding description
string of the language type
NAME
Alias
Used to specifically describe

recognized
For example, create a language description string with the following requirements.
280
Language template No.: 1
Language type: 2
Language description string: en

ADD LANGDES:TPLID=1,LANG=2,LANGDES="en";
system tree.
SET:NEID=31;
9. The data configuration procedure of the MGW is the same with
that of the basic service tone on the MGW.
END OF STEPS
281
282
Figure
Figure 1 Networking Between MSCS and MGW........................ 2

Figure 2 SIGTRAN CONFIGURATION FLOW ............................23
Figure 3 CONFIGURATION FLOW..........................................36
Figure 4 Typical Networking Between the ZXWN CS and the
HLR .................................................................45
Figure 5 Typical Networking Between the ZXWN CS and the
STP .................................................................69
Figure 6 Networking Between the ZXWN CS and the SCP ........86
Figure 7 Networking Between ZXWN CS and SMC ................ 104
Figure 8 Interconnection between ZXWN MSCS and
PSTN/MSC ...................................................... 112
Figure 9 Networking with BSC ........................................... 137
Figure 10 Networking Between MGW and RNC ..................... 168
Figure 11 ANALYSIS ORDER OF NUMBER ANALYZERS ........... 214
Figure 12 Coding Standard of the Internal EMID .................. 274
283
284
Table
Table 1 Data Collection Table................................................ 2

Table 2 Configuration Flow ................................................... 3
Table 3 PARAMETERS IN THE ADD IP ADDRESS COMMAND .... 4
Table 4 INTERFACE REAL INTERFACE................................... 5
Table 5 ADD IP ADDRESS REAL INTERFACE ......................... 6
Table 6 PARAMETERS IN THE ADD IP ROUTE COMMAND ........ 7
Table 7 PARAMETERS IN THE ADD ADJOFC COMMAND ..........10
Table 8 PARAMETERS IN THE ADD CODECTPL COMMAND ......14
Table 9 PARAMETERS IN THE ADD TOPO COMMAND..............16
Table 10 PARAMETERS IN THE ADD MGWBEARMOD
COMMAND ........................................................20
Table 11 PARAMETERS IN THE ADD SCTPCONN COMMAND....24
Table 12 PARAMETERS IN THE ADD ASP COMMAND ..............28
Table 13 PARAMETERS IN THE ADD AS COMMAND ................29
Table 14 PARAMETERS IN THE ADD M3UART COMMAND........32
Table 15 PARAMETERS IN THE ADD SIOLOCAS COMMAND.....34
Table 16 PARAMETERS IN THE ADD MGCSCFG COMMAND......37
Table 17 PARAMETERS IN THE ADD MGSTPL COMMAND ........39
Table 18 PARAMETERS IN THE ADD MGSCFG COMMAND........40
Table 19 PARAMETERS IN THE ADD TIDANL COMMAND.........42
Table 20 PARAMETERS IN THE ADD TIDENTR COMMAND.......44
Table 21 MSCS-HLR Interconnection Data Collection...............45
Table 22 Data for Interconnection with the HLR .....................46
Table 23 PARAMETERS IN THE ADD ADJOFC COMMAND ........47
Table 24 PARAMETERS IN THE ADD N7LKS COMMAND ..........49
Table 25 PARAMETERS IN THE ADD N7LNKE1 COMMAND ......51
Table 26 PARAMETERS IN THE ADD N7ROUTE COMMAND......54
Table 27 ARRANGEMENT MODE OF SIGNALING SETS..............55
Table 28 PARAMETERS IN THE ADD N7OFC COMMAND ..........56
Table 29 PARAMETERS IN THE ADD IMSIANA COMMAND ......58
Table 30 PARAMETERS IN THE ADD GTT COMMAND ..............60
Table 31 PARAMETERS IN THE ADD GT COMMAND ................64
Table 32 SSN ....................................................................67
Table 33 MSCS-STP Data Collection......................................70
285
Table 34 MSCS-STP Data Configuration Flow .........................70

Table 35 PARAMETERS IN THE ADD ADJOFC COMMAND ........71
Table 36 PARAMETERS IN THE ADD N7LKS COMMAND ..........73
Table 37 PARAMETERS IN THE ADD N7LNKE1 COMMAND ......75
Table 38 PARAMETERS IN THE ADD N7ROUTE COMMAND......78
Table 39 PARAMETERS IN THE ADD N7OFC COMMAND ..........80
Table 41 Data Collection Table .............................................86
Table 42 MSCS-SCP Data Configuration Flow .........................87
Table 43 PARAMETERS IN THE ADD N7SSN COMMAND ..........88
Table 45 PARAMETERS IN THE ADD CAMEL COMMAND ..........93
Table 46 PARAMETERS IN THE ADD CAINFO COMMAND ........95
Table 47 PARAMETERS IN THE ADD TPDNAL COMMAND ........97
Table 48 Internal Service Keys .......................................... 100
Table 49 PARAMETERS IN THE ADD SVRTRANSKEY
COMMAND ...................................................... 101
Table 50 Service Key Codes .............................................. 101
Table 51 PARAMETERS IN THE ADD TONESVC COMMAND .... 103
Table 52 Data Collection Table ........................................... 105
Table 53 Data Configuration Flow of SMC Adjacent Office ...... 105
Table 54 PARAMETERS IN THE ADD GT COMMAND .............. 106
Table 55 Data for Interconnection with the MGW.................. 112
Table 56 Data for Interconnection with the PSTN/MSC Office .. 112
Table 57 Configuration Flow of PSTN/2G MSC Adjacent Office
Data .............................................................. 113
Table 58 PARAMETERS IN THE ADD ADJOFC COMMAND ...... 114
Table 59 PARAMETERS IN THE ADD TG DT COMMAND ......... 115
Table 60 PARAMETERS IN THE ADD SPCM COMMAND .......... 119
Table 61 PARAMETERS IN THE ADD RT COMMAND .............. 121
Table 62 PARAMETERS IN THE ADD RTS COMMAND ............ 123
Table 63 PARAMETERS IN THE ADD CHAIN COMMAND ........ 124
Table 64 PARAMETERS IN THE ADD SCTPCONN COMMAND .. 127
Table 65 PARAMETERS IN THE ADD ASP COMMAND ............ 129
Table 66 PARAMETERS IN THE ADD AS COMMAND .............. 131
Table 67 PARAMETERS IN THE ADD M3UART COMMAND...... 134
Table 68 PARAMETERS IN THE ADD SIOLOCAS COMMAND... 135
Table 70 Data for Interconnection with the BSC ................... 138
Table 71 BSC Adjacent Office Data Configuration Flow .......... 138
286
Tables

Table 73 PARAMETERS IN THE ADD BSCOFC COMMAND ...... 144
Table 74 PARAMETERS IN THE ADD TOPO COMMAND .......... 146
Table 75 MAIN PARAMETERS IN THE ADD RNCMGWTOPO
COMMAND ...................................................... 149
Table 76 PARAMETERS IN THE ADD TG DT COMMAND ......... 151
Table 78 PARAMETERS IN THE ADD SCTPCONN COMMAND .. 159
Table 79 PARAMETERS IN THE ADD ASP COMMAND ............ 162
Table 80 AS Parameters.................................................... 163
Table 81 PARAMETERS IN THE ADD M3UART COMMAND...... 165
Table 82 PARAMETERS IN THE ADD SIOLOCAS COMMAND... 167
Table 84 Data for Interconnection with the RNC ................... 169
Table 85 RNC Adjacent Office Data Configuration Flow .......... 170
Table 87 PARAMETERS IN THE ADD RNCOFC COMMAND ...... 175
Table 88 PARAMETERS IN THE ADD TOPO COMMAND .......... 178
Table 89 PARAMETERS IN THE ADD RNCMGWTOPO
COMMAND ...................................................... 182
Table 90 PARAMETERS IN THE ADD TG ATM COMMAND ....... 184
Table 92 Access Configuration Flow .................................... 193
Table 93 PARAMETERS IN THE ADD ECC COMMAND............. 194
Table 94 PARAMETERS IN THE ADD SSPN COMMAND .......... 196
Table 95 PARAMETERS IN THE ADD TPDNAL COMMAND ...... 200
Table 96 PARAMETERS IN THE ADD LAI COMMAND ............. 202
Table 97 PARAMETERS IN THE ADD LAI COMMAND ............. 206
Table 98 PARAMETERS IN THE ADD GCI COMMAND............. 210
Table 99 PARAMETERS IN THE ADD SAI COMMAND ............. 212
Table 100 DAS FOR PRE-ANALYZING THE CALLED NUMBER ... 214
Table 101 ORIGINATING DAS ............................................ 215
Table 102 FORWARDING DAS ............................................ 216
Table 103 ROAMING DAS.................................................. 217
Table 104 PARAMETERS IN THE ADD ENTR COMMAND ........ 219
Table 105 ANALYZER ENTRY TYPES .................................... 220
Table 106 COMMON DASS................................................. 221
Table 107 PARAMETERS IN THE ADD DAS COMMAND .......... 222
Table 108 PARAMETERS IN THE SET LDASTMPLT
COMMAND ...................................................... 223
287
Table 109 PARAMETERS IN THE ADD ACRTMPLT

COMMAND ...................................................... 227
Table 110 PARAMETERS IN THE ADD TPDNAL COMMAND .... 230
Table 111 CALL SERVICE TYPES......................................... 244
Table 112 ENABLED OPTIONS............................................ 251
Table 113 PARAMETERS IN THE BADD STONE COMMAND .... 258
Table 114 PARAMETERS IN THE ADD TONEID COMMAND
FOR FIXED TONES ........................................... 260
Table 115 PARAMETERS IN THE ADD TONEPRO COMMAND .. 262
Table 116 PARAMETERS IN THE ADD CODEDOTS
COMMAND ...................................................... 263
Table 117 PARAMETERS IN THE ADD FIXTONE COMMAND ... 264
Table 118 PARAMETERS IN THE ADD TONESRV COMMAND .. 267
Table 119 PARAMETERS IN THE ADD TONEID COMMAND..... 269
Table 120 PARAMETERS IN THE ADD TONEPLAYMT
COMMAND FOR BASIC SERVICE TONES .............. 270
Table 121 PARAMETERS IN THE ADD TONEPRO COMMAND .. 271
Table 122 PARAMETERS IN THE ADD LANGSTR COMMAND .. 272
Table 123 PARAMETERS IN THE ADD TONELIST COMMAND .. 273
Table 124 PARAMETERS IN THE ADD TONESVC COMMAND .. 273
Table 125 PARAMETERS IN THE ADD EMIDTRIF COMMAND .. 276
Table 126 PARAMETERS IN THE ADD SVRTRANSKEY
COMMAND ...................................................... 277
Table 127 PARAMETERS IN THE ADD TONEIN COMMAND .... 278
Table 128 PARAMETERS IN THE ADD TONEID COMMAND..... 279
Table 129 PARAMETERS IN THE ADD TONEPLAYMT
COMMAND ...................................................... 280
Table 130 PARAMETERS IN THE ADD LANGDES COMMAND .. 280
288
Index
D
Data configuration ....... 2,
45, 59, 69, 71, 8687,
93, 104105, 112, 135,
137138, 168169, 258,
260, 265266, 269,
274275, 279, 281
G
GT translation
selector .................. 59,
6263, 68, 81, 85, 87,
89, 92, 106, 110
H
Handover ................. 46,
63, 81, 193, 276
N
Networking mode ..... 104, 168
Number section ........ 158, 190
O
Outgoing route.........113,
121124
P
Physical configuration .......... 76, 126, 159, 266
S
Signaling link ............ 70,
7379, 105, 169
Signaling point ............ 2,
4548, 59, 70, 72, 86,
88, 105, 112, 114, 138,
166167, 169
Signaling route.......... 70,
7880, 87, 105
289

SJ-20100211152857-010-ZXWN MSCS (V3.09.21) MSC Server Common Configuration Operation Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SJ-20100211152857-010-ZXWN MSCS (V3.09.21) MSC Server Common Configuration Operation Guide

Uploaded by

Copyright:

Available Formats

ZXWN MSCS

Common Configuration Operation Guide

Feb. 28, 2010

Serial Number: SJ-20100211152857-010

About This Manual............................................. I

Confidential and Proprietary Information of ZTE CORPORATION

ZXWN MSCS Common Configuration Operation Guide

HLR Data Configuration ..................................................44

Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION

ZXWN MSCS Common Configuration Operation Guide

Creating an ATM Trunk Group ........................... 183

Access Data Configuration............................. 193

Number Analysis Data Making ....................... 213

Tone Configuration ........................................ 257

Confidential and Proprietary Information of ZTE CORPORATION

About This Manual

CS network and its network elements

The basic knowledge, interfaces and protocols, and service

This manual contains the following chapters:

Chapter 1, Data Making

Introduces the procedure and method for

Chapter 2, Access Data

Introduces the procedure and method for

Confidential and Proprietary Information of ZTE CORPORATION

ZXWN MSCS Common Configuration Operation Guide

Introduces the procedure and method

Introduces the procedure and method for

This device complies with part 15 of the FCC Rules. Operation is

ZTE documents employ the following typographical conventions.

References to other Manuals and documents.

Menus, menu options, function names, input fields,

Keys on the keyboard and buttons on screens and

Mouse operation conventions are listed as follows:

Refers to clicking the primary mouse button (usually the

Refers to quickly clicking the primary mouse button

Refers to clicking the secondary mouse button (usually

Confidential and Proprietary Information of ZTE CORPORATION

Hexavalent Chromium (Cr (VI))

PolyBrominated Biphenyls (PBBs)

PolyBrominated Diphenyl Ethers (PBDEs)

The ZXWN MSCS manufactured by ZTE CORPORATION meet

Confidential and Proprietary Information of ZTE CORPORATION

ZXWN MSCS Common Configuration Operation Guide

This page is intentionally blank.

Confidential and Proprietary Information of ZTE CORPORATION

Data Making for New

This chapter introduces the procedure and method of collecting

MGW Data Configuration

Confidential and Proprietary Information of ZTE CORPORATION

ZXWN MSCS Common Configuration Operation Guide

FIGURE 1 NETWORKING BETWEEN MSCS

Real address of the MSCS

Loopback address of the MSCS

Port number of the MSCS

Real address of the MGW

Loopback address of the MGW

Port number of the MGW

Coding scheme of H.248 protocol

MSCS signaling point code

MGW signaling point code

This configuration aims to complete the interconnection between

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Data Making for New Commissioning