SJ-20101208143956-008-ZXWN MSCS (V4.10.13) MSC Server Data Configuration Guide (MSCS II) PDF

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

Contents
About This Manual ......................................................................................... I
Declaration of RoHS Compliance ................................................................. I
Chapter 1 Basic Service Configuraiton and Debugging......................... 1-1
1.1 Location Update Configuration and Debugging..................................................... 1-1
1.1.1 SCCP Data Configuration ......................................................................... 1-1
1.1.2 Security Variable Configuration ............................................................... 1-13
1.1.3 Roaming Data Configuration ................................................................... 1-16
1.1.4 Security Management Parameters Configuration...................................... 1-21
1.1.5 Debugging Location Update.................................................................... 1-42
1.2 Interior Calls Data Configuration and Debugging ................................................ 1-43
1.2.1 Number Analysis Configuration ............................................................... 1-43
1.2.2 Creating Mobile Number Prefix................................................................ 1-74
1.2.3 Creating Number Transform for CLIP (optional)........................................ 1-76
1.2.4 Variables Configuration........................................................................... 1-79
1.2.5 Debugging Interior Calls ......................................................................... 1-81
1.3 Inter-office Calls Data Configuration and Debugging ........................................... 1-82
1.3.1 Trunk Data Configuration ........................................................................ 1-82
1.3.2 Routing Data Configuration ....................................................................1-106
1.3.3 Modifying Pre-defined Timer .................................................................. 1-112
1.3.4 Debugging Inter-office Calls ................................................................... 1-113
Chapter 2 Billing Configuration and Debugging ..................................... 2-1

2.1 Overview ........................................................................................................... 2-1
2.2 CU Office Configuration ...................................................................................... 2-1
2.2.1 Creating a CU NE .................................................................................... 2-2
2.2.2 Creating Bill Server Module....................................................................... 2-3
2.3 MSCS Billing Parameters Configuration............................................................... 2-4
2.3.1 Setting Charge Parameter ........................................................................ 2-5
2.3.2 Configuring CS Network Entity Config Parameters ..................................... 2-8
2.3.3 Configuring an IP Address for Communication Between Foreground and
Background Subsystems ....................................................................... 2-10
Figures............................................................................................................. I
Tables ............................................................................................................ III
Index ...............................................................................................................V
I
Glossary .......................................................................................................VII
II
About This Manual
Purpose
ZXWN MSCS MSC Server Configuration Guide (MSCS I) describes MSCS data
configuration principle, basic office data configuration, version loading, resource
configuration, Mc interface interconnection data configuration, office direction signaling
interconnection data configuration, and radio office interconnection data configuration.
ZXWN MSCS MSC Server Data Configuration Guide (MSCS II) describes basic service
debugging related to call service, general service debugging related to billing.
Intended Audience
This manual is intended for engineers and technicians who have mastered the
communication principle of the mobile network.
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:
l MSCS system and its various components
What Is in This Manual

This manual contains the following chapters:
Chapter Summary
Chapter 1, Basic Service Configuration and Describes the basic service debugging related with
Debugging call service
Chapter 2, Billing Data Configuration Describes the data configuration of billing on CU

and MSCS
FCC Compliance Statement

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.
I
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.
II
Declaration of RoHS
Compliance
To minimize environmental impacts and take more responsibilities to the earth we live
on, this document shall serve as a formal declaration that MSCS manufactured by
ZTE CORPORATION is in compliance with the Directive 2002/95/EC of the European
Parliament - RoHS (Restriction of Hazardous Substances) with respect to the following
substances:
l Lead (Pb)
l Mercury (Hg)
l Cadmium (Cd)
l Hexavalent Chromium (Cr (VI))
l PolyBrominated Biphenyls (PBBs)
l PolyBrominated Diphenyl Ethers (PBDEs)
MSCS manufactured by ZTE CORPORATION meets 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.
I
II
Chapter 1
Basic Service Configuraiton
and Debugging
Table of Contents
Location Update Configuration and Debugging...........................................................1-1
Interior Calls Data Configuration and Debugging ......................................................1-43
Inter-office Calls Data Configuration and Debugging ................................................1-82
1.1 Location Update Configuration and Debugging

During commissioning, you need to realize location update for local subscribers first and
then go on with LU debugging for roaming subscribers. It is required that subscribers in
HLRs of various vendors in the province/state should all be tested before go on to test LU
of roaming subscribers out of the province/state.
l The main job of LU commissioning for local subscribers is to interconnect with the
local HLR that local subscribers are registered in.
l You need to cooperate with STP during debugging of LU for out-of-province
subscribers.
The location update configuration and debugging flow is as follows:
1. SCCP configurations and MAP related security variable configuration, refer to 1.1.1
SCCP Data Configuration and 1.1.2 Security Variable Configuration.
2. Roaming data and security management parameters configuration, refer to
1.1.3 Roaming Data Configuration and 1.1.4 Security Management Parameters
Configuration.
3. Location update debugging, refer to 1.1.5 Debugging Location Update.
1.1.1 SCCP Data Configuration

Description
The SCCP data configuration is used to provide the routing service for the SCCP. In the
R4 system, the MAP signaling between the MSCS/VLR and entities (such as HLR) in
the network is transferred through the SCCP. Each entity can be directly connected with
each other, and also can be connected with each other through STPs. When receiving
messages from the MAP application layer, the SCCP will send, receive and forward these
messages according to the route labels carried in the messages. The SCCP has two
routing modes: GT and DPC +SSN.
1-1
SJ-20101208143956-008|2011-02-28(R1.0) ZTE Proprietary and Confidential

ZXWN MSCS Data Configuration Guide (MSCS II)
The difference between the GT and the DPC+SSN routing modes is manifested in the case
where there are STPs in the source signaling point and the destination signaling point.
In the DPC+SSN routing mode, it is required that all the signaling points (including the
source signaling point, destination signaling point, and STP) in the network can identify
the Destination signaling Point Code (DPC). The signaling is directly sent from the MTP
layer after reaching the intermediate point instead of passing the SCCP layer. In this case,
more DPC data need to be configured for the source signaling point and the STP.
The GT routing mode can be used when the final DPC of the signaling is unknown to
the source signaling point and part of STPs. When this addressing mode is adopted, and
when the signaling is transferred to the STP, the SCCP translates the GT to the destination
signaling point or the DPC of the next-hop STP, and then sends the message to the MTP
for transfer. When the GT routing mode is adopted, the source signaling point only needs
to send the signaling to the STP of the next-hop GT translation according to the GT number
prefix, and then the STP determines whether to send the signaling to the next STP or the
destination signaling point . In this case, less DPC data need to be configured for the
source signaling point and the STP.
Configuration Rules
Tip:
Comply with operator’s specification for data compiling.
General rules are as follows:

l National and international SCCP addressing uses GT addressing mode and load is
shared by two STPs.
l Intra-province SCCP address uses DPC+SSN addressing with associated HLR and
use STP as the alternate route and uses GT addressing with non-associated HLR.
Before configuring GT translation, you should first configure GT translation selectors
to determine basic attribute of GT translation and then configure GT translation.
l GT translation selector
Usually you only need to configure two GT translation selectors, selector 1 for E.164
and selector 2 for E.214.
Data Configuration
The related operations of the SCCP data configuration are as follows.
1-2

Chapter 1 Basic Service Configuraiton and Debugging
No. Operations Instructions Commands
1 Createing a GT translation In general, one or two GT ADD GTT

selector translation selectors are
configured, corresponding to
E164 and E214 numbering
plans respectively.
2 Creating GT translation Create the GT translation ADD GT

data data for the source address
and the destination address
of the signaling on each end
point or transfer point.
1.1.1.1 Creating a GT Translation Selector
Abstract
In general, two GT translation selectors are configured, corresponding to E164 and E214
numbering plans respectively.
Prerequisites
Before the operation, it is required to confirm:
l The office ID to be configured is given.
l Interconnection with the adjacent HLR office is completed, and the signaling office
direction is successfully debugged.
l The MML Terminal window is opened.
Context
The numbers to be configured are described as follows:
1. E214 number
The format of the E.212 number is “MCC+MNC+MSIN”, while that of the E.214 number
is “CC+NDC+MSIN”, which are used for location registration of mobile subscribers.
It is usually required to convert the “MCC+MNC” part to “CC+NDC” according to mobile
number analysis, to construct the format of the E214 number.
2. E164 number
The format of the E.164 number is “MSISDN”, which is used for communication when
the mobile subscriber acts as the called party, and the communication between mobile
NEs.
During the location update debugging procedure, it is only required to configure the
MSC/VLR GT and HLR GT of the local office.
1-3

Steps
1. If no office is specified, execute command SET on the MML Terminal window or select
a NE from the system tree to specify the office to be configured.
Example: Select the MSCS office with ID as 11 from the system tree.
SET: NEID= 11;
2. Create a GT translation selector by executing command ADD GTT.
The explanation of the main parameters in command ADD GTT is shown in Table 1-1.
Table 1-1 Parameters in the ADD GTT Command
Parameter Parameter Description Instruction

Name
GTT GT type It is a mandatory parameter, 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.
TT Translation type It is a mandatory parameter, ranging from 0

to 255. It is the translation type of the GT
number, with the default value as 0.
PLAN Numbering plan, including It is a mandatory parameter. Select E.164

l NULL (idle) for the E164 format, and select E.214 for
l E.164 (ISDN/phone the E214 format. For example, if the mobile
numbering plan) number is analyzed as HLR, select E.164
l E.214 (ISDN/mobile for GT analysis of this number. If the mobile
numbering plan) number is analyzed as ISDN, select E.214 for
l X.121 (Data numbering GT analysis of this number.
plan)
l F.69 (Telex numbering
plan)
l E.210(Maritime mobile
numbering plan)
l E.212 (Land mobile
numbering plan)
l Reserved(2),
Reserved(8)~Reserved
(15): Reserved
1-4


Name
NATURE Address attribute, including It is a mandatory parameter. Select INT.

l SUB (address attributes
is subscriber number)
l INT (address attributes
is international number)
l NATRSV (address
attributes is national
reserved number)
l NATSIGN (address
attributes is national
valid number)
l INAPSCP (SCP
standby)
l CAMEL (address
attributes is intelligent
network service number)
l VACANT0, VA-
CANT7~VACANT255:
vacancy
GTTOPT SCCP Route Index It is an optional parameter, with a default of 0.
ID GT translation selector It is an optional parameter, ranging from 0

to 1023. It is the global number of the GT
translation selector.
CC Country code It is an optional parameter, consisting of 0~4

digits.
NMIN National minimum digit length They are optional parameters, which are
integers, ranging from 1 to 20. They
NMAX National maximum bit length
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.
1-5


Name
IMIN International minimum digit They are optional parameters, which are
length integers, ranging from 1 to 20. They
respectively correspond to the international
IMAX International maximum digit
minimum GT number length, and international
length
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.
CTRL GT translation attributes, It is an optional parameter, with the default

including: choice as R_L. Maximum Matching means
l R_L (intercepting digits match the number from right to left. When
from the number to analyzing a GT number, search the matched
be analyzed from right options with the maximum length. GT
to left for alignment, numbers are analyzed in the descending
corresponding to the order of their lengths, facilitating reducing the
maximum matching workload of GT data configuration.
policy)
l L_R (intercepting digits
from the number to
be analyzed from left
to right for alignment,
corresponding to the
minimum matching
policy)
NAME User alias It is a mandatory parameter, consisting of

1~50 characters.
It is used to identify a GT translation selector
to make it easily recognized.
Example: Create a GT translation selector with the following requirements:
l GT type: 4
l Translation type: 0
l Numbering plan: E.164
l Address attribute: international number
l GT translation selector: 1
l National minimum digit length: 5
l National maximum digit length: 15
l International minimum digit length: 1
l International maximum digit length: 5
l User alias: E.164.
1-6

The command is:

ADD GTT: GTT= 4, TT= 0, PLAN= E.164, NATURE= INT, GTTOPT= 0, ID= 1, CC=
"86", NMIN= 5, NMAX= 15, IMIN= 1, IMAX= 5, CTRL= R_L, OPPFX= NO, NAME=
"E164";
Example: Create a GT translation selector with the following requirements:
l GT type: 4
l Translation type: 0
l Numbering plan: E.214
l Address attribute: international number
l GT translation selector: 2
l National minimum digit length: 5
l National maximum digit length: 15
l International minimum digit length: 1
l International maximum digit length: 5
l User alias: E.214.
The command is:
ADD GTT: GTT= 4, TT= 0, PLAN= E.214, NATURE= INT, GTTOPT= 0, ID= 2, CC=
"86", NMIN= 5, NMAX= 15, IMIN= 1, IMAX= 5, CTRL= R_L, OPPFX= NO, NAME=
"E214";
– End of Steps –
1.1.1.2 Creating GT Translation Data
Prerequisites
l GT translation selectors are configured.
Context
The GT translation data are used for location update, calls and inter-office handover. When
configuring GT translation data, it is required to add the GT translation data for the source
address and the destination address of the signaling on each end point or transfer point.
When configuring location update data, it is required to translate the local GT number to
the office ID 0, that is, local office, and translate the GT number of the HLR to the HLR or
STP. Therefore, it is required to configure at lease two sets of GT translation data on the
MSCS.
E164 number: It is required to configure the local MSC/VLR GT, MSISDN number, and the
MSC/VLR GT having the LAI adjacency relationship.
1-7

E214 number: It is required to configure the corresponding number in E214 format

(CC+NDC+MSISDN) of the IMSI number (E212 format: MCC+NDC+MSISDN).
Steps
an NE from the system tree to specify the office to be configured.
SET: NEID= 11;
2. Create GT translation data by executing command ADD GT.
The explanation of the main parameters in command ADD GT is shown in Table 1-2.
Table 1-2 Parameters in the ADD GT Command
Parameter Name Parameter Description Instruction
GT Called GT It is a mandatory parameter, consisting

of 1~20 digits. It is used to query the
destination GT number of message
routing.
GTSL GT TransSelector ID It is a mandatory parameter, ranging from

0 to 1,023. Select the GT translation
selector respectively according to
configured E164 and E214 numbers.
GTDI GTDI 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 1st OFC-Turn Times List It is a mandatory parameter. 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 Office Group Support It is an optional parameter, with a default

of NO.
1-8

OFCGRP2 2nd OFC-Turn Times List It is an optional parameter. The number

grouping is supported. The user does
not need to type when the office ID
grouping is supported. The format is
poll respectively.
OFCGRP3 3rd OFC-Turn Times List It is an optional parameter. The number

poll respectively.
OFCGRP4 4th OFC-Turn Times List It is an optional parameter. The number

poll respectively.
SSN Subsystem No. Refer to Table It is an optional parameter. In the GT

1-3 for the options involved routing mode, select the default value
for SSN. In the DPC+SSN routing mode,
select the corresponding SSN.
NGT New GT It is an optional parameter, ranging from

0 to 20 of characters. It represents the
new GT translation type.
NTRNTYPE New GT Translator Type It is an optional parameter, ranging from

0 to 255. It represents the new GT
translation type.
1-9

TRNRLT Whether the translation result It is an optional parameter. In the GT

contains DPC and SSN. The routing mode, select the default value for
options includes TRNRLT. In the DPC+SSN routing mode,
l NULL (neither DPC nor select the DPC and SSN for TRNRLT.
SSN is in the result)
l DPC (containing DPC in
the result)
l SSN (containing SSN in the
result)
RTTYPE Routing mode, including It is an optional parameter. In general,

l GT (routing based on GT) select GT for direct connection, and DPC
l DPC (routing based on for non-direct connection.
DPC+SSN)
NGTTAG New GT Attribute, including the It is an optional parameter. It is the

following options: attribute of the new GT contained in the
l NGT (No new GT in the GT translation result. NGT(No new GT
GT translation result): The in the GT translation result) is selected
GT number in the GT by default.
translation result is still the
called GT number.
l 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).
l NTT: The GT number in the
GT translation result is the
new GT number in the NGT
parameter, only containing
translation type.
l 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.
l NTTNAI: The GT number in
the GT translation result is
the new GT number in the
NGT parameter, containing
translation type, numbering
1-10

plan, coding design, and

NAI
SCCP SCCP Encode Type, including: It is an optional parameter. It indicates the

l INT (international coding) standard type referred to by the SCCP
l USA(USA coding) coding in the GT translation result. The
default value is INT.
MAP MAP Stage It is an optional parameter, with a default

of R4.
VGT Virtual GT Support, including It is an optional parameter, with NO as

l NO (not supported) the default value.
l YES (supported)
TT TT conversion, including It is an optional parameter, with NO as

l NO (not supported) the default value.
l YES (supported)
NPFLAG Number plan flag, including: It is an optional parameter, with NO as

l NO: Not start using the default value.
l YES: Start using
NPLAN New called number plan, It is an optional parameter, with NULL as

including: the default value.
l NULL (idle)
l E.164 (ISDN/phone
numbering plan)
l X.121 (Data numbering
plan)
l F.69 (Telex numbering plan)
l E.210(Maritime mobile
numbering plan)
l E.212 (Land mobile
numbering plan)
l E.214 (ISDN/mobile
numbering plan)
SRVTYPE Service type, including: It is an optional parameter, with NULL as

l NULL: invalid the default value.
l GSM: GSM service
l CDMA: CDMA service
NAME Alias The alias of the GT translation data for

easy memory.
1-11

Table 1-3 SSN
SSN Meaning
NO_SSN Not contain 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
AUC Authentication center
ISDN/ASE ISDN_ASE(11)
INAP/OTA INAP/OTA subsystem
USSD USSD
VLRA VLRA
SGSN_BSSAP SGSN BSSAP
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
NPDB NPDB
ATER ATER
IP IP
SMC SMC subsystem
SSP_SCP SSPSCP subsystem
HLR_SSAP HLR_SSAP
UDS_DMCC UDS_DMCC
BSC_BSSAP_LE/MPC BSC_BSSAP_LE/MPC
MSC_BSSAP_LE MSC_BSSAP_LE
1-12

SSN Meaning
SMLC_BSSAP_LE SMLC_BSSAP_LE
BSS_O_M_A BSS_O_M_A
BSSAP_A BSSAP_A
Other Reserved Reserved
Example: Create the HLR GT translation data with the following requirements:
l GT number: 8613907551
l GT translation selector ID: 1
l Office ID poll: 1-1
l Routing mode: GT routing
l Other parameters: Adopt default values.
The command is:
ADD GT: GT= "8613907551", GTSL= 1, GTDI= 0, OFCIDS= "1"-"1", GRP= NO, SSN=
NO_SSN, NTRNTYPE= 0, TRNRLT= "SSN", RTTYPE= GT, NGTTAG= NGT, SCCP=
INT, MAP= R4, VGT= NO, TT= NO, NPFLAG= NO, NPLAN= NULL, SRVTYPE= NULL;
1.1.2 Security Variable Configuration

Security Variable configurations related to MAP is as shown in Table 1-4.
Table 1-4 Security Variable Configuration
No. Operations Instructions
1 Configuring System Control Parameters Introduces the System Control Parameters

related to MAP configuration related to MAP.
2 Configuring CS Network Entity Config Introduces the CS Network Entity Config

Parameter related to MAP Parameter configuration related to MAP.
1.1.2.1 Configuring System Control Parameters related to MAP
Abstract
This topic introduces the system control parameters configuration related to MAP.
Prerequisites
The GT data configuration is completed.
1-13

Steps
1. In the NetNumen M30 window, select Views > Professional Maintenance > MSCS
> Security Variable > WCN Security Variable > System Control. The System
Control tab pops up.
2. On the System Control tab, select the corresponding variables, and click on the
sub-toolbar to enter the editing status. Select the corresponding options, as shown in
Figure 1-1.
l Send MAP Phase Setting: Phase2+ for domestic 2G and R4 for 3G. The phase
number actually sent in MAP message should be the lower one of the MAP phase
configured here and the MAP phase configured in GT translation.
l Receive MAP Phase Setting: it is usually same as the MAP phase of the sending
end.
l TM Packet Size (Byte): it is related to capacity of interconnected devices. If they
support XUDT message, size of TM packet can be set as 2000 to reduce number
of message sending. It should be set as 150 if XUDT is not supported so that
over-long streams can be sent in packets.
Figure 1-1 Security Variable Configuration 1
3. Click the button on the sub-toolbar.
1-14

1.1.2.2 Configuring CS Network Entity Config Parameter related to MAP
Abstract
This topic introduces the CS network entity config parameters configuration related to MAP.
Prerequisites
Steps
1. On the NetNumen M30 window, select Views > Professional Maintenance > MSCS
> Security Variable > WCN Security Variable > CS Network Entity Config. The CS
Network Entity Config tab pops up.
2. On the CS Network Entity Config tab, select the corresponding variables, and click
on the sub-toolbar to enter the editing status. Select the corresponding options, as
shown in Figure 1-2.
l Filling Rule of MSC Number or VLR Number in MAP/CAP Dialog Message:
choose Fill MSCNum/VLRNum Corresponding to GCI/LAI.
l Filling Rule of GT in MAP/CAP Dialog Initial Message: same as above

1-15

1.1.3 Roaming Data Configuration

Description
The following conditions can judge whether a subscriber is roaming:
l Whether the subscriber roams from one country to another one: Based on the MCC,
compare the MCC configured in the local-office mobile data configuration.
l Whether the subscriber roams from one network to another one: Based on the MNC,
compare the MNC configured in the local-office mobile data configuration, and the
MNCs configured in the local-office other-MNC configuration.
l Whether the subscriber roams within a LAI: Based on the number in the IMSI excluding
the MCC and MNC, compare the location number configured in the LAI configuration,
and the area code configured in the mobile-network area-code configuration.
Data Configuration
The related operations of the roaming data configuration are as follows.
Steps Operations Instructions Commands
1 Creating IMSI number analysis IMSI number analysis ADD IMSIANA

is used to convert the
IMSI number to another
number or a number that
can address the HLR
2 Creating a mobile service access Configure the relationship ADD NDCMNC

number and MNC between a mobile service
access number and a
MNC for inter-network
roaming
3 Creating a mobile network ID and area Configure the relationship ADD NCCFG
code mapping between a mobile network
ID and a area code
to judge whether a
subscribers is roaming
1.1.3.1 Creating IMSI Number Analysis
Prerequisites

1-16

Context
IMSI number analysis is used to convert the IMSI number to a number that can address
the HLR. The VLRMAP performs GT translation through this number to address the HLR
where the IMSI is registered. Create IMSI number analysis according to the roaming data
provided by operators, usually configuring the local-network and international roaming
data.
Background
In IMSI number analysis, it is required to set the “home destination code type”, which can
be “ISDN” or “HLR”.
1. ISDN
The corresponding number prefix in the IMSI is converted into the specified analysis
result, and the rest digits are added behind the analysis result. For example, if the
analyzed number is 46000, it is converted to 86139, the network-admitted IMSI number
is 460001234567890, the corresponding Country Code (CC) is 86, and the Network
Destination Code (NDC) is 139. In this mode, this IMSI 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, forming the E214
number format.
2. HLR
The corresponding number prefix in the IMSI is converted into the specified analysis
result, and the rest digits are deleted. For example, if the analyzed number is 46000,
it is converted to the GT number 8613903066 of the HLR, and the network-admitted
IMSI number is 460001234567890. In this mode, this IMSI number is analyzed to
8613903066, that is the GT number of the HLR. 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
SET: NEID= 11;

2. Creating IMSI number analysis by executing command ADD IMSIANA.
The explanation of the main parameters in command ADD IMSIANA is shown in Table
1-5.
1-17

Table 1-5 Parameters in the ADD IMSIANA Command
IMSI IMSI prefix It is a mandatory parameter, consisting

of 20-digit integers at most. It is the
MCC+MNC in the IMSI.
HDSTCODE Home destination code It is a mandatory parameter, consisting of

16-digit integers at most. It is the number
that the IMSI number is converted to. It is
of the format of “CC+NDC” or the HLR GT
number in general.
HDSTCODET Destination code type, It is an optional parameter. HLR: When

including ISDN and HLR there is a specific HLR number, select HLR
ISDN: The MAP makes the analyzed home
destination code replace the CC in an
IMSI to form the corresponding destination
number of this IMSI. For example, if the
IMSI is 46000091212, and the home
destination code is 87, the translated result
is 8703091212. The ISDN mode is usually
used for international roaming subscribers.
NAME Alias It is used to describe a piece of IMSI

analysis record for easy memory. It
consists of 50-digit integers at most.
ENOTHOPT Whether to enable options, Whether to enable options related to HLR.

including:
l NULL: None
l CRTN: Criterion
l PRDG: Predigestion
and SMS Format
l CHKIMEI: CheckIMEI
ADD
INDADC Independent ADC GT It is an optional parameter, with a default

Number, inclduding of NO.
l NO
l YES
ADCGT Independent ADC GT It is an optional parameter, ranging from

Number 0~16.
SM Format code of short The parameter ranges from 0 to 255, with

message a default of 0.
OPID Operator ID The parameter ranges from 0 to 255, with

a default of 0.
1-18

Example: Create the IMSI number analysis with the following requirements:
l Prefix: 46000
l Home destination code: 86139
l Home destination code type: ISDN
l Other parameters: Adopt default values.
The command is:
ADD IMSIANA: IMSI= "46000", HDSTCODE= "86139", HDSTCODET= ISDN, INDAD
C= NO, SM= 0, OPID= 0;
1.1.3.2 Creating a Mobile Service Access Number and MNC
Abstract
This section introduces how to configure the relationship between a mobile service access
number and an MNC for inter-network roaming.
Prerequisites
Steps
SET: NEID= 11;
2. Create the relationship between a mobile service access number and an MNC by
executing command ADD NDCMNC.
The explanation of the main parameters in command ADD NDCMNC is shown in Table
1-6.
Table 1-6 Parameters in the ADD NDCMNC Command
ID Access number configuration It identifies the order of configuring access

ID numbers, ranging from 1 to 1,000.
CC Country code It indicates the CC of the mobile service

access code. Enter it according to the
actual condition.
1-19

NDC National destination code It indicates the mobile digital service access
number. Enter it according to the actual
condition
MCC Mobile country code Enter it according to the actual condition.
MNC Mobile network code Enter it according to the actual condition.
NAME User alias It is a mandatory parameter, consisting of

0~50 characters. It is used to describe
the relationship between a mobile service
access number and a MNC.
Example: Create the relationship between a mobile service access number and a
MNC with the following requirements.
l Access number configuration ID: 1
l CC: 86
l Mobile service access number: 139
l MCC: 460
l MNC: 00.
The command is:
ADD NDCMNC: ID= 1, CC= "86", NDC= "139", MCC= "460", MNC= "00";
1.1.3.3 Creating a Mobile Network ID and Area Code Mapping
Abstract
This section introduces how to configure the relationship between a mobile network ID and
a area code to judge whether a subscribers is roaming.
Prerequisites
l The exchange ID to be configured is given.

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;
1-20

2. Create the relationship between a mobile network ID and an area code by executing
command ADD NCCFG.
The explanation of the main parameters in command ADD NCCFG is shown in Table
1-7.
Table 1-7 Parameters in the ADD NCCFG Command
MSIN Mobile subscriber It is a mandatory parameter. Enter the No.

identification number 3-8 digits in the IMSI except “MCC+MNC”.
ACODE Area code It is a mandatory parameter. Enter the

area code of the area where the subscriber
belongs.
NAME Alias It consists of 0~50 characters. It is the

name defined by a user for easy memory.
Example: Create the relationship between a mobile network ID and an area code with
the following requirements.
l Mobile Subscriber Identification Number: 1234
l Area code: 755.
The command is:
ADD NCCFG: MSIN= "1234", ACODE= "755";
1.1.4 Security Management Parameters Configuration

Description
Security parameters in Security Management include encryption and integrity protection,
authentication parameters, TMSI re-allocation, CS-domain security parameters and
security variables in CS-domain NE configuration.
Note:
These parameters are closely related to safety policy of the customer so you need to set
them as required. The configurations below are for your reference. For 2G access, you
need to set authentication and encryption parameters in Access Configuration > Mobility
Management. For 3G access, you need to set authentication, encryption and integrity
protection parameters in Access Configuration > Mobility Management.
1-21

Configuration Flow
Steps Operations Instructions Command
1 Modifying security Set encryption algorithm for 2G SET SEC

policy and set encryption and integrity
protection algorithms for 3G.
2 Modifying Set authentication policy for SET AUTHP

Authentication Policy services
3 Modify TMSI Set TMSI reallocation policy for SET TMSI

reallocation policy services
4 Creating IMEI request Create IMEI request policy for ADD IMEIREQ
policy services
5 Modifying Page Policy Modify page policy related SET PAGE

parameters
6 Configuring CS Security Introduces the CS security -

Parameter parameters configuration
related to encryption and
authentication.
7 Configuring CS Network Introduces the CS Network -

Entity Config Parameter Entity Config parameter
configuration related to
encryption and authentication.
1.1.4.1 Modifying Security Policy
Abstract
Set encryption algorithm for 2G and set encryption and integrity protection algorithms for
3G.
Prerequisites

Steps
SET: NEID= 11;
1-22

2. Modify security policy, the command is SET SEC.

The explanation of the main parameters in command SET SEC is shown in Table 1-8.
Table 1-8 Parameters in the SET SEC Command

Name
OFC Office ID This parameter indicates

the ID of a BSC or an
RNC adjacent office. This
parameter is mandatory and
its value is an integer from
0 to 65,534. The value 0
indicates all BSC and RNC
offices.
NAME Alias This parameter describes

a security policy in
detail, which facilitates
identification. This
parameter is optional and its
value is a string.
AEA A Encryption Algorithm Enable, including: Choose all encryption

l NEAAI: A network allows the A interface algorithms of Interface A
to use no encryption algorithm. that BSC supports.
l A51EAE: A network allows the A interface
to use encryption algorithm 1.
AEADIS A Encryption Algorithm Disable Choose all encryption

algorithms of Interface A
that BSC does not support.
1-23


Name
UEA Lu Encryption Algorithm Enable, including: Choose all encryption

l NIUEA: A network allows the lu interface algorithms of Interface Iu
to use no encryption algorithm. that RNC supports.
l IU1EAE: A network allows the lu interface
l IU10EAE: A network allows the lu
interface to use encryption algorithm 10.
interface to use encryption algorithm 15
UEADIS Iu Encryption Algorithm Disable Choose all encryption

algorithms of Interface Iu
that RNC does not support.
1-24


Name
UIA Iu Integrity Protect Algorithm Enable, Choose all integrity protect

including: algorithm of interface Iu that
l BIPA1: A network allows the lu interface RNC supports.
to use integrity protection algorithm 1.
l BIPA2: A network allows the lu interface
UIADIS Iu Integrity Protection Algorithm Disable Choose all integrity protect

algorithm of interface Iu that
RNC does not support.
ENCRYP Encryption Enable, including: It is an optional parameter,

l NO with a default of NO.
l YES
Set encryption algorithm for 2G, the command is:
1-25

SET SEC: OFC= 0, AEA= "NEAAI";

Set encryption and integrity protection algorithms for 3G, the command is:
SET SEC: OFC= 0, UEA= "IU1EAE", UIA= "BIPA1", ENCRYP= YES;
1.1.4.2 Modifying Authentication Policy
Abstract
This topics describes how to modify authentication policy.
Prerequisites
Steps
SET: NEID= 11;
2. Modify authentication policy, the command is SET AUTHP.
The explanation of the main parameters in command SET AUTHP is shown in Table
1-9.
Table 1-9 Parameters in the SET AUTHP Command
VMSCIDX Virtual MSC Index This parameter indicates a

virtual MSC index for which
authentication configurations are
to be modified. This parameter
is mandatory and its value is
an integer from 0 to 65,535.
The value 0 indicates the public
domain.
1-26

ROAMTYPE Roam Type, including: This parameter indicates a user

l RNO: not roaming roaming type to be authenticated.
l RNINTRA: roaming in a local This parameter and a virtual
network and local area MSC index determine a unique
l RNINTER: roaming in a authentication policy. Normally
local network and between DEFAULT is selected.
different areas
l RNINTERNET: roaming in a
nation and between different
networks
l RINTER: roaming between
different countries
l DEFAULT: default roaming
type
IMSI IMSI This parameter is optional and

its value is a string of 0 to 16
characters.
NAME Alias This parameter describes an

authentication policy in detail,
which facilitates identification.
The value of this parameter is a
string.
MO Auth Ratio of MO Call This parameter indicates the

authentication ratio in an MO
call process. The value of this
parameter is an integer from 0 to
100.
SS Auth Ratio of Call Independent SS Independent SS This parameter

indicates the authentication ratio
a supplementary service that is
not related to calls. The value of
this parameter is an integer from
0 to 100.
EC Auth Ratio of Emergency Call This parameter indicates the

authentication ratio in an
emergency call process. The
value of this parameter is an
integer from 0 to 100.
1-27

REESTAB Auth Ratio of Call This parameter indicates the

Re-establishment authentication ratio in a call
reconnection process. The value
of this parameter is an integer
from 0 to 100.
SMSMO SMS MO Authentication Ratio This parameter is optional and its

value is an integer from 0 to 100.
SMSMT SMS MT Authentication Ratio This parameter is optional and its

LCS Auth Ratio of LCS This parameter indicates the

authentication ratio in a location
service process. The value of this
100.
MT Auth Ratio of MT Call This parameter indicates the

authentication ratio in an MT
call process. The value of this
100.
USSD USSD Authentication Ratio This parameter is optional and its

LUNORMAL Auth Ratio of Normal LU This parameter indicates the

authentication ratio in a normal
location update process. The
LUATTACH Auth Ratio of IMSI Attach This parameter indicates the

authentication ratio in an IMSI
attachment process. The value of
0 to 100.
LUPERIODIC Auth Ratio of Periodic LU This parameter indicates the

authentication ratio in a periodical
location update process. The
1-28

REUSE Reuse Number of Auth Vector This parameter indicates the

number of times that an
authentication parameter can
be used repeatedly. The value of
1 to 5. Note that this parameter
is valid only when the following
conditions are met:
l A user accesses a BSC.
l The VLR fails to obtain the
authentication parameter
group from the HLR.
AUTHPARA Auth Parameter, including: This parameter sets an

l ERAU: The CN supports authentication parameter. You
reauthentication. can set this parameter according
l MSRA: Authentication to the actual situation. In addition,
is required during first this parameter is optional and its
registration of a user. value is of enumeration type.
l CKSNA: Authentication is
required when the TMSI is
known and the CKSNs are
the same during an access.
l ECSC: Emergency call with
security context.
AUTHDISPARA Authentication Disable Parameter Set this parameter according to

the actual situation.
Example: Modify authentication policy with the following requirements.

l Virtual MSC Index: 0
l Roam Type: DEFAULT
l Auth Ratio of MO Call: 0
l Auth Ratio of Call Independent SS: 0
l Auth Ratio of Emergency Call: 0
l Auth Ratio of Call Re-establishment: 0
l SMS MO Authentication Ratio: 0
l SMS MT Authentication Ratio: 0
l Auth Ratio of LCS: 0
l Auth Ratio of MT Call: 0
l USSD Authentication Ratio: 0
l Auth Ratio of Normal LU: 100
l Auth Ratio of IMSI Attach: 100
l Auth Ratio of Periodic LU: 100
1-29

l Reuse Number of Auth Vector: A user accesses a BSC

l Auth Parameter: Authentication is required during first registration of a user.
The command is:
SET AUTHP: VMSCIDX= 0, ROAMTYPE= DEFAULT, MO= 0, SS= 0, EC= 0, REE
STAB= 0, SMSMO= 0, SMSMT= 0, LCS= 0, MT= 0, USSD= 0, LUNORMAL= 100,
LUATTACH= 100, LUPERIODIC= 100, REUSE= 1, AUTHPARA= "MSRA";
1.1.4.3 Modify TMSI Reallocation Policy
Abstract
When TMSI reallocation is enabled, the TMSI reallocation process includes encryption
process, and Kc(2G) or Ck(3G) is necessary for encryption process.
Prerequisites
Steps
SET: NEID= 11;
2. Modify TMSI reallocation policy, the command is SET TMSI.
The explanation of the main parameters in command SET TMSI is shown in Table
1-10.
Table 1-10 Parameters in the SET TMSI Command
VMSCIDX Virtual MSC Index This parameter indicates a virtual

MSC index for which a TMSI
reallocation policy is configured. This
parameter is mandatory and its value
is an integer from 0 to 65,535. The
value 0 indicates the public domain.
1-30

ROAMTYPE Roam Type, including: Normally DEFAULT is selected.

l RNO: not roaming
l RNINTRA: roaming in a local
network and local area
l RNINTER: roaming in a local
network and between different
areas
networks
different countries
l DEFAULT: default roaming type
IMSI IMSI Range This parameter is optional and its

value is a string of 0 to 15 characters.
NAME Alias This parameter describes a TMSI

reallocation policy in detail, which
facilitates identification. The value of
this parameter is a string.
MO TMSI Realloc For MO Call, including: NO is recommended.

l NO: TMSI reallocation is not
enabled in an MO call process.
l YES: TMSI reallocation is
enabled in an MO call process.
EC TMSI Realloc For Emergency Call, NO is recommended.

including:
enabled in an emergency call
process.
enabled in an emergency call
process.
SMSMO TMSI Realloc For SMSMO, including: NO is recommended.

enabled in an SMS MO service
process.
enabled in an SMS MO service
process.
1-31

SMSMT TMSI Realloc For SMSMT, including: NO is recommended.

enabled in an SMS MT service
process.
enabled in an SMS MT service
process.
LCS TMSI Realloc For LCS, including: NO is recommended.

enabled in an LCS service
process.
enabled in an LCS service
process.
SS TMSI Realloc For Call Independent NO is recommended.

SS, including:
enabled in a supplementary
service that is not related to
calls.
enabled in a supplementary
service that is not related to
calls.
USSD TMSI Realloc For USSD, including: NO is recommended.

enabled in a USSD service.
enabled in a USSD service.
REESTAB TMSI Realloc For Call NO is recommended.

Re-establishment, including:
enabled in a call reconnection
process.
enabled in a call reconnection
process.
1-32

MT TMSI Realloc For MT Call, including: NO is recommended.

enabled in an MT call process.
enabled in an MT call process.
LUNORMAL TMSI Realloc For Normal LU, YES is recommended.

including:
enabled in a normal location
update process.
enabled in a normal location
update process.
LUPERIODIC TMSI Realloc For Periodic LU, NO is recommended.

including:
enabled in a periodical location
update process.
enabled in a periodical location
update process.
LUATTACH TMSI Realloc For IMSI Attach, YES is recommended.

including:
enabled in an IMSI attachment
process.
enabled in an IMSI attachment
process.
LUFIRSTREG TMSI Realloc For First Register, YES is recommended.

including:
enabled during first registration
of a user.
enabled during first registration
of a user.
Example: Modify TMSI reallocation policy with the following requirements:

l Roam Type: default
l TMSI Realloc For MO Call: No
1-33

l TMSI Realloc For Emergency Call: No

l TMSI Realloc For SMSMO: No
l TMSI Realloc For SMSMT: No
l TMSI Realloc For LCS: No
l TMSI Realloc For Call Independent SS: No
l TMSI Realloc For USSD: No
l TMSI Realloc For Call Re-establishment: No
l TMSI Realloc For MT Call: No
l TMSI Realloc For Normal LU: Yes
l TMSI Realloc For Periodic LU: No
l TMSI Realloc For IMSI Attach: Yes
l TMSI Realloc For First Register: Yes
The command is:
SET TMSI: VMSCIDX= 0, ROAMTYPE= DEFAULT, MO= NO, EC= NO, SMSMO= NO,
SMSMT= NO, LCS= NO, SS= NO, USSD= NO, REESTAB= NO, MT= NO, LUNORM
AL= YES, LUPERIODIC= NO, LUATTACH= YES, LUFIRSTREG= YES;
1.1.4.4 Creating IMEI Request Policy
Abstract
This topic describes how to create IMEI request policy.
Normally, configure not to obtain IMEI in all conditions.
Prerequisites
Steps
SET: NEID= 11;

2. Create IMEI request policy, the command is ADD IMEIREQ.
Table 1-11 describes the main parameters in the ADD IMEIREQ command.
1-34

Table 1-11 Parameters in the ADD IMEIREQ Command
VMSCIDX Virtual MSC Index This parameter indicates a virtual

MSC index for which an IMEI
checking policy is configured.
The value of this parameter is
an integer from 0 to 65,535.
The value 0 indicates the public
domain.
ANATYPE Analysis Type, including: For the same VMSC, the matching
l ImsiPrefix: IMSI prefix of IMSI prefixes and roaming
l RoamType: roaming type types can be set at the same time.
The matching of IMSI prefixes has
a higher priority. The matching of
IMSI prefixes supports left match
and long match. For example,
when 420 and the 42003 prefix
are set at the same time, the
IMSI 4200388261624 matches
the record whose IMSI prefix is
42003.
IMSIPFX IMSI Range This parameter is optional and

its value is a string. The string
contains digits from 0 to 15 or is
DEFAULT. The string DEFAULT
indicates that all IMSIs are
matched.
ROAMTYPE Roam Type, including: Normally DEFAULT is selected.

l RNO: not roaming
l RNINTRA: roaming in a local
network and local area
l RNINTER: roaming in a
local network and between
different areas
networks
different countries
l DEFAULT: default roaming
type
1-35

MORF MO Ratio (1/n) This parameter is optional and its

The value 0 indicates that no IMEI
is requested for this access type.
ECRF EC Ratio (1/n) This parameter is optional and its

SMSMORF SMS MO Ratio (1/n) This parameter is optional and its

MTRF MT Ratio (1/n) This parameter is optional and its

SMSMTRF SMS MT Ratio (1/n) This parameter is optional and its

LCSRF LCS Ratio (1/n) This parameter is optional and its

SSRF Call Independent SS Ratio (1/n) This parameter is optional and its
USSDRF USSD-MT Ratio (1/n) This parameter is optional and its

REESTABRF Call Re-establishment Ratio (1/n) This parameter is optional and its
LUNORMALRF Normal LU Ratio (1/n) This parameter is optional and its

1-36

LUPERIODICRF Periodic LU Ratio (1/n), including: This parameter is optional and its
l NO: An IMEI is not obtained value is of enumeration type.
for a greylist.
l YES: An IMEI is obtained for
an unknown user.
LUATTACH Get IMEI at IMSI Attach, including: This parameter is optional and its
for a greylist.
an unknown user.
LUFIRSTREG Get IMEI At First Register, This parameter is optional and its
including: value is of enumeration type.
l NO: An IMEI is not forcibly
obtained when the IMEI is
invalid. IMEIs are obtained
by ratio according to service
types.
l YES: An IMEI is always
invalid.
INVADIMEI Get IMEI when IMEI invalid, This parameter is optional and its
l NO: An IMEI is not forcibly
invalid. IMEIs are obtained
by ratio according to service
types.
l YES: An IMEI is always
invalid.
IMEISV Using IMEISV, including: This parameter is optional and its

l NO: IMEISV is not used. value is of enumeration type.
l YES: IMEISV is used.
BLACKPLC Get IMEI for Black List, including: This parameter is optional and its
for a blacklist.
a blacklist.
1-37

GREYPLC Get IMEI For Grey List, including: This parameter is optional and its
for a greylist.
a greylist.
UNKPLC Get IMEI for Unknown User, This parameter is optional and its
l NO: An IMEI is not obtained
for an unknown user.
an unknown user.
IMEISVFLPLC Policy of Obtain IMEISV Fail, This parameter is optional and its
l REL: Release the process.
l IGN: Ignore it.
l RETRY: Continue to obtain
an IMEI only.
l CHKRETRY: Have a retry if
IMEI checking is required.
Otherwise, ignore it.
IMEIFLPLC Policy Of Obtain IMEI Fail, This parameter is optional and its
l REL: Release the process.
l IGN: Ignore it.
NAME Alias This value of this parameter is a

string of 0 to 50 characters.
Example, create IMEI request policy with the following requirements:

l Analysis Type: roaming type
l Roam Type: default
l Policy Of Obtain IMEI Fail: IGN
l Configure not to obtain IMEI.
The command is:

ADD IMEIREQ: VMSCIDX= 0, ANATYPE= RoamType, ROAMTYPE= DEFAULT, MO
RF= 0, ECRF= 0, SMSMORF= 0, MTRF= 0, SMSMTRF= 0, LCSRF= 0, SSRF= 0, US
SDRF= 0, REESTABRF= 0, LUNORMALRF= 5, LUPERIODICRF= 10, LUATTACH=
NO, LUFIRSTREG= NO, INVADIMEI= NO, IMEISV= NO, BLACKPLC= NO, GREYPL
C= NO, UNKPLC= NO, IMEISVFLPLC= IGN, IMEIFLPLC= IGN;
1-38

1.1.4.5 Modifying Page Policy
Abstract
For 2G and 3G access, set paging parameters in Access Configuration > Mobility
Management.
If second paging is enabled, set Whether to enable Retry Page with IMSI in place
of TMSI as YES in Security Variable > WCN Security Variable > CS Network Entity
Config, which means using TMSI for the first paging and IMSI for the second paging.
Prerequisites
Steps
SET: NEID= 11;
2. Modify page policy, the command is SET PAGE.
The explanation of the main parameters in command SET PAGE is shown in Table
1-12.
Table 1-12 Parameters in the SET PAGE Command

Name
PAGEIDX Page configure index This parameter indicates the index of a

paging policy. The value of this parameter
is an integer from 1 to 512. In addition, this
parameter is mandatory.
NAME Alias This parameter describes a paging policy in

detail. The value of this parameter is a string.
PAGECNT Resending times of paging This parameter indicates the number of times
message for resending a paging message. The value of
this parameter is an integer from 0 to 2. Set
it as 1 if you need to enable second paging.
Otherwise, set it as 0.
1-39


Name
PAGETIMER Page response timer (s) This parameter indicates the duration for
waiting for a paging response. The value of
this parameter is an integer from 0 to 255. If
a paging message (including Search) does
not need to be resent, the MSC sets the page
response timer to twice of this duration.
PAGETMSI Use TMSI on paging, This parameter indicates whether to use a

including: TMSI for paging. Normally select YES.
l NO: A TMSI is not used
for paging.
l YES: A TMSI is used
for paging.
PREPAGE Support prepaging, This parameter indicates whether to support

including: prepaging in the local office.
l NO: Prepaging is not
supported in the local
office.
l YES: Prepaging is
supported in the local
office.
Example: modify page policy with the following requirements:

l Page configure index: 1
l Resending times of paging message: 1
l Use TMSI on paging: yes
l Support pre-paging: no
l Other parameters: default.
The command is:
SET PAGE: PAGEIDX= 1, PAGECNT= 1, PAGETMSI= YES, PREPAGE= NO;
1.1.4.6 Configuring CS Security Parameter
Prerequisites
Context
This topic introduces the CS security parameters configuration related to encryption and
authentication.
1-40

Steps
> Security Variable > WCN Security Variable > CS Security Parameter. The CS
Security Parameter tab pops up.
2. On the CS Security Parameter tab, select the corresponding parameters, and click
on the sub-toolbar to enter the editing status, as shown in Figure 1-3.
l Whether to request IMSI when MS access with unknown TMSI: choose YES.
l Whether to get IMSI from MS when Authentication fails using TMSI: choose
YES.
l Num of Auth Vectors Kept: after the current authentication is completed, initiate
the flow to get authentication parameters from HLR if number of authentication
sets left is lower than the value. Recommended value is 1.

1.1.4.7 Configuring CS Network Entity Config Parameter
Abstract
This topic introduces the CS Network Entity Config parameter configuration related to
encryption and authentication.
1-41

Prerequisites
Steps
1. On the NetNumen M30 window, select Views > Professional Maintenance >
MSCS > Security Variable > WCN Security Variable > CS Network Entity Config
Parameter. The CS Network Entity Config Parameter tab pops up.
2. On the CS Network Entity Config tab, select Number of Authentication Vectors,
and click on the sub-toolbar to enter the editing status. Enter the value as 5, as
shown in Figure 1-4.

1.1.5 Debugging Location Update

Abstract
This topic takes LU debugging of local subscribers for example to describe the basic
procedure of LU debugging.
1-42

Prerequisites
l The interconnection configuration between MSCS and local HLR is completed.
l The interconnection configuration between MSCS and BSC/RNC is completed.
Steps
1. Prepare for the debugging.
l The HLR office direction is reachable and sub-system state is normal.
l The office direction between MSCS and BSC/RNC is reachable.
l The LA and cell configuration is completed.
2. Check state.
a. Check if office directions between MSCS and HLR and between MSCS and
BSC/RNC are reachable.
Check office direction state through signaling options of Dynamic Management.
b. Check sub-system status of HLR and BSC/RNC office directions is normal.
3. Open Signaling Trace and Failure Observer, switch on handset, choose network,
log in and perform LU debugging.
l Signaling Trace: Track with IMSI or MSISDN of subscriber , select BSSAP,
RANAP, and MAP, then start.
l Failure Observer: Trace failure observation of MSCS and SCCP.
1.2 Interior Calls Data Configuration and Debugging

When the location update of the mobile phone is successfully debugged, and the
subscriber information can be found in the VLR, perform the interior calls data configuration
and debugging.
The interior calls data configuration and debugging flow is as follows:
1. Number analysis configuration, refer to 1.2.1 Number Analysis Configuration.
2. Mobile number prefix configuration, refer to 1.2.2 Creating Mobile Number Prefix.
3. Number transform for CLIP configuration (optional), refer to 1.2.3 Creating Number
Transform for CLIP (optional).
4. Security variable configuration for adding international prefix to national calls and
MSISDN length, refer to 1.2.4.1 Configuring Security Variable for Adding International
Prefix to National Calls and 1.2.4.2 Setting MSISDN Length in Security Variable.
5. Perform interior calls debugging, refer to 1.2.5 Debugging Interior Calls.
1.2.1 Number Analysis Configuration

Description
This section only introduces the basic steps of number analysis.
1-43

Data Configuration
The related operations of the number analysis configuration are as follows.
1 Creating a number analyzer Specify an ID for each type ADD ENTR

entry of number analyzers
2 Creating a DAS The DAS is the collection ADD DAS

of various number analyzer
entries, specifying the order
and rule of performing
number analysis.
3 Setting the default DAS Set the default DAS SET LDASTMPLT
template of the local office template of the local office
means creating the DAS
used for local-office service
processing.
4 Creating a DAS template Create multiple DAS ADD ACRTMPLT

(optional) templates in the
dual-homing or regional
networking.
5 Creating the called numbers Create number analysis for ADD TPDNAL
analysis prefixes of called numbers
and roaming numbers
6 Creating number transform Configure the basic number ADD DDI

index change method for number
analysis.
1.2.1.1 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
1-44

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 1-5.
Figure 1-5 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 1-13.
Table 1-13 DAS for Pre-analyzing the Called Number
Analyzer Entry Analyzed Number Analysis Result
New service 10193 + 0 + local area code If call restriction is required, analyze
number analyzer it to “pre-analysis ending, and call
rejected”
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
10193 + 0 + non-local area code Analyze it to “pre-analysis normally

ending”, and delete 10193 from the
10193 + G network number section
change index of the called number.
10193 + C network number section
Whether to add 10193 to the
called-number index in the CDR
1-45

depends on the CDR filling

requirements on the billing center
2. Originating DAS: used to analyze the called number in the local-office-originated call,
as shown in Table 1-14.
Table 1-14 Originating DAS
New service Charging query number Analyze it to the SSP charging query
number analyzer service
Special-service Free special-service number Analyze it to the local-office free

number analyzer special service, pointing to the
special-service number configured
on the attendant console
Corresponding attendant console Analyze it to the outgoing free

number of the special-service number special service, pointing to the
special-service circuit group
Short number -
Special-service number of the Analyze it to the outgoing free

operator special service, pointing to the
special-service circuit group
Local-network 0 Vacant number

number analyzer
All numbers are analyzed by the
subsequent analyzers
Local PSTN number Analyze it to the local-network

outgoing/local-call service, pointing
to the gateway office
Local number section of other mobile Analyze it to the local-network

network outgoing/local-call service, pointing
Non-local number section of other Analyze it to the automatic service in

mobile network the national toll region, pointing to the
tandem office of the local province
Number section of the local mobile Analyze it to the MSC common

network service
1-46

National 0 Vacant number

toll-service
All numbers are analyzed by the
number analyzer
subsequent analyzers
0 + Local area code + Local PSTN Analyze it to the local-network

number outgoing/local-call service, pointing
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
International 00 + International number Analyze it to the international toll

toll-service automatic service
number analyzer
3. Forwarding DAS: used to analyze the number to which the call is forwarded, as shown
in Table 1-15.
Table 1-15 Forwarding DAS
Local-network number 0 Vacant number

analyzer
All numbers are analyzed by
the subsequent analyzers
Local PSTN number Analyze it to the local-network

outgoing/local-call service,
pointing to the gateway office
Local number section of other Analyze it to the local-network

mobile network outgoing/local-call service,
Non-local number section of Analyze it to the automatic

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

mobile network service
1-47

National toll-service number 0 Vacant number

analyzer
All numbers are analyzed by
the subsequent analyzers
0 + Local area code + Local Analyze it to the local-network

PSTN number outgoing/local-call service,
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 1-16. It is unnecessary
to analysis the CC in national roaming numbers.
Table 1-16 Roaming DAS
Local-network number Roaming number section of Analyze it to the local MSC

analyzer the local service area in the service
local office
Roaming number section of Analyze it to the outgoing

non-local service area in the service of the local MSC.
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 Analyze it to the national toll

sections call
00 + International number Analyze it to the international

toll automatic service
1.2.1.2 Creating a Number Analyzer Entry
Abstract
Creating number analyzer entries means specifying an ID for each type of number
analyzers.
1-48

Prerequisites
l The number analyzer entry range is set in resource configuration.
Steps
1. If no office is specified, execute command SET in the MML Terminal window or select
SET: NEID= 11;

2. Create a number analyzer entry by executing command ADD ENTR.
The explanation of the main parameters in command ADD ENTR is shown in Table
1-17.
Table 1-17 Parameters in the ADD ENTR Command
ID Analyzer entry It is an optional parameter, which is

an integer, ranging from 1 to 10,000.
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 1-18 for the configuration
description.
NTYPE Number analysis result under this It is an optional parameter, with

analyzer, including CALLED as the default value. In
l CALLED (analysis on called general, select CALLED.
numbers)
l CALLING (analysis on calling
numbers)
l FORWARD (analysis on calling
numbers during call forwarding)
l OPIMSI (analysis on calling
IMSI numbers)
l TPIMSI (analysis on called IMSI
numbers)
l FWDIMSI (analysis on IMSI
numbers during call forwarding)
1-49

VMSCIDX 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).
Table 1-18 Analyzer Entry Types
Parameter Name Parameter Description 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 Special-service number analyzer After this analyzer is configured, if

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

analyzer, the analysis ends.
NATIONAL National toll-service number After this analyzer is configured, if

analyzer the number is not matched in this
analyzer, the analysis ends.
INTER International toll-service number After the number is analyzed in this

analyzer analyzer, the analysis ends.
Example: Create a number analyzer entry with the following requirements.

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

ADD ENTR: ID= 1, NAME= "Entr1", TYPE= LOCAL, NTYPE= CALLED;
1-50

1.2.1.3 Creating a DAS
Abstract
The DAS is the collection of various number analyzer entries, specifying the order and rule
of performing number analysis.
Prerequisites
l The DAS range is set in resource configuration.
l The number analyzer entry is configured.
Context
Table 1-19 lists common DASs.
Table 1-19 Common DAS
Parameter Name Parameter Description 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.
PREDAS Number pre-analysis Used for the number pre-analysis

function, standardizing called
numbers, and performing call
restriction based on numbers.
Steps
SET: NEID= 11;
2. Create a DAS by executing command ADD DAS.
The explanation of the main parameters in command ADD DAS is shown in Table 1-20.
1-51

Table 1-20 Parameters in the ADD DAS Command
ID Number Analysis Selector It is a mandatory parameter, which

is an integer, ranging from 1 to
4,096. It is the index number of the
newly-added DAS.
NAME User alias It is an optional parameter,

NEWSRV New service number analyzer entry Enter the umber analyzer entry IDs
contained by a DAS.
CENTR CENTREX number analyzer entry
PRINET Private-network number analyzer

entry
SPECSRV Special-service number analyzer

entry
LOCAL Local-network number analyzer

entry
NATIONAL National toll-service number

analyzer entry
INTER International toll-service number

analyzer entry
Example: Create a MS originating DAS with the following requirements.

l DAS ID: 101
l User alias: MSQH
l Local number analyzer entry: 1
l Other parameters: Adopt the default values.
The command is:
ADD DAS: ID= 101, NAME= "MSQH", NEWSRV= 0, CENTR= 0, PRINET= 0, SPECS
RV= 0, LOCAL= 1, NATIONAL= 0, INTER= 0;
1.2.1.4 Setting the Default DAS Template of the Local Office
Abstract
Creating the default DAS template of the local office means creating the DAS used for
local-office service processing.
Prerequisites
1-52


l The DAS is configured.
Steps
SET: NEID= 11;
2. Set the default DAS template of the local office by executing command SET LDAST
MPLT.
The explanation of the main parameters in command SET LDASTMPLT is shown in
Table 1-21.
Table 1-21 Parameters in the SET LDASTMPLT Command

Name
MS MS- Originating Selector It is an optional parameter, which is an integer,

ranging from 0 to 4,096. 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 office or toll office according to
location of the called party.
MSRN Roaming Number Selector It is an optional parameter, which is an integer,

ranging from 0 to 4,096. 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, this DAS also
analyzes forwarding numbers returned from the
HLR, and subscriber numbers from other mobile
office or fixed office.
1-53


Name
OR Optimal Routing Number It is an optional parameter, which is an integer,

Selector ranging from 0 to 4,096.
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.
CNG Calling Number Analysis It is an optional parameter, which is an integer,

It is used to analyze the calling number in outgoing
calls to implement traffic division of the calling
number and calling number change function.
LI Lawful Interception Number It is an optional parameter, which is an integer,

It is used for the interception service.
IP IP Call Selector It is an optional parameter, which is an integer,

ranging from 0 to 4,096.
It is used for the IP telephone service.
CBCNG Incoming Call Limit Calling It is an optional parameter, which is an integer,

Number Selector ranging from 0 to 4,096.
It is used for the incoming call restriction service.
PBRT Personal Back Ring Tone It is an optional parameter, which is an integer,

It is used for the PBRT service.
FWD Forward Number Selector It is an optional parameter, which is an integer,

FWDCNG Forward Original Called It is an optional parameter, which is an integer,

CNGVIGW Calling Number It is an optional parameter, which is an integer,

Selector(IGW) ranging from 0 to 4,096.
FWDVIGW Forward Number It is an optional parameter, which is an integer,

INTRA Share Number It is an optional parameter, which is an integer,

Selector(IGW) ranging from 0 to 4,096. It is used for the function
of one number for two MSs and mixed group.
ROUTCAT1 MS Category 1 Originating It is an optional parameter, which is an integer,


1-54


Name



IMSIOPDAS Calling IMSI Number It is an optional parameter, which is an integer,

OVERLAY Overlay Number Selector It is an optional parameter, which is an integer,

LIIGW Lawful Interception Number It is an optional parameter, which is an integer,

SHLRSKEY SHLR Service Key Selector It is an optional parameter, which is an integer,

IMSITPDAS Called IMSI Number It is an optional parameter, which is an integer,

IMSIFW- Forward IMSI Number It is an optional parameter, which is an integer,

DAS Selector ranging from 0 to 4,096.
MRBT Multimedia Back Ring Tone It is an optional parameter, which is an integer,

PREDAS Originating Number It is an optional parameter, which is an integer,

Pre-analysis Selector ranging from 0 to 4,096.
RECNCT- Reconnection Number It is an optional parameter, which is an integer,

DAS Selector ranging from 0 to 4,096.
Example: Configure the default DAS template of the local office with the following
requirements.
l MS originating DAS: 101
l MSRN DAS: 201
l Forwarding DAS: 301.
The command is:
SET LDASTMPLT: MS= 101, MSRN= 201, FWD= 301;

1-55

1.2.1.5 Creating a DAS Template
Abstract
It is required to create multiple DAS templates in the dual-homing or regional networking.
Prerequisites
Steps
SET: NEID= 11;
2. Create a DAS template by executing command ADD ACRTMPLT.
The explanation of the main parameters in command ADD ACRTMPLT is shown in
Table 1-22.
Table 1-22 Parameters in the ADD ACRTMPLT Command
TMPLIDX Analysis Selector Template Index It is a mandatory parameter, ranging

from 1~65,535.
NAME User alias It is a mandatory parameter,

MS MS- Originating Selector It is an optional parameter, which is

MSRN Roaming Number Selector It is an optional parameter, which is

OR Optimal Routing Number Selector It is an optional parameter, which is

CNG Calling Number Analysis Selector It is an optional parameter, which is

LI Lawful Interception Number Selector It is an optional parameter, which is

IP IP Call Selector It is an optional parameter, which is

CBCNG Incoming Call Limit Calling Number It is an optional parameter, which is

Selector an integer, ranging from 0 to 4,096.
1-56

PBRT Personal Back Ring Tone Number It is an optional parameter, which is

FWD Forward Number Selector It is an optional parameter, which is

an integer, ranging from 0 to 4,096
FWDCNG Forward Original Called Number It is an optional parameter, which is

CNGVIGW Calling Number Selector(IGW) It is an optional parameter, which is

FWDVIGW Forward Number Selector(IGW) It is an optional parameter, which is

INTRA Share Number Selector(IGW) It is an optional parameter, which is

It is used for the function of one
number for two MSs and mixed
group.
ROUTCAT1 MS Category 1 Originating Selector It is an optional parameter, which is





IMSIOPDAS Calling IMSI Number Selector It is an optional parameter, which is

OVERLAY Overlay Number Selector It is an optional parameter, which is

an integer, ranging from 0 to 4,096
LIIGW Lawful Interception Number It is an optional parameter, which is

Selector(IGW) an integer, ranging from 0 to 4,096.
SHLRSKEY SHLR Service Key Selector It is an optional parameter, which is

IMSITPDAS Called IMSI Number Selector It is an optional parameter, which is

IMSIFWDAS Forward IMSI Number Selector It is an optional parameter, which is

1-57

MBRT Multimedia Back Ring Tone Number It is an optional parameter, which is

PREDAS Originating Number Pre-analysis It is an optional parameter, which is

RECNCTDAS Reconnection Number Selector It is an optional parameter, which is

Example: Add a DAS template with the following requirements.

l DAS template ID: 1
l MS originating DAS: 101
l MSRN DAS: 201
l Preferred routing DAS: 301
l Calling number DAS: 401
The command is:
ADD ACRTMPLT: TPLIDX= 1, MS= 101, MSRN= 201, OR= 301, CNG= 401, LI= 0,
IP= 0, CBCNG= 0, PBRT= 0, FWD= 0, FWDCNG= 0, CNGVIGW= 0, FWDVIGW= 0,
INTRA= 0, ROUTCAT1= 0, ROUTCAT2= 0, ROUTCAT3= 0, ROUTCAT4= 0, ROUT
CAT5= 0, IMSIOPDAS= 0, OVERLAY= 0, LIIGW= 0, SHLRSKEY= 0, IMSITPDAS=
0, IMSIFWDAS= 0, MBRT= 0, PREDAS= 0, RECNCTDAS= 0, NC= 0, TESTCALLD
AS= 0, CFPRE= 0, CFUPRE= 0, NDUBPRE= 0, UDUBPRE= 0, CFNRCE_PRE= 0,
CFNRCL_PRE= 0, CFNRYPRE= 0, CDPRE= 0, MORCPRE= 0, GMSCRCPRE= 0,
CFRCPRE= 0, MTRCPRE= 0, CAMELDNALIDX= 0, SSDAS= 0, CFU= 0, CFUCNG=
0, CFNDUB= 0, CFNDUBCNG= 0, CFUDUB= 0, CFUDUBCNG= 0, CFNRC_E= 0,
CFNRCCNG_E= 0, CFNRC_L= 0, CFNRCCNG_L= 0, CFNRY= 0, CFNRYCNG= 0,
CD= 0, CDCNG= 0;
1.2.1.6 Creating the Called Number Analysis
Abstract
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.
Prerequisites
l The number analyzer entry is configured.
1-58

Steps
SET: NEID= 11;
2. Create called number analysis, the command is ADD TPDNAL.
The explanation of the main parameters in command ADD TPDNAL is shown in Table
1-23.
Table 1-23 Parameters in the ADD TPDNAL Command
Parameter Name Parameter Instruction

Description
ENTR Analyzer Entry It is a mandatory parameter, which is an integer,

ranging from 1 to 10,000. Select the corresponding
analyzer entry of the analyzed number prefix. For
local calls, select the corresponding analyzer entry
of the local number analyzer.
NANNAT Number analysis It is a mandatory parameter with a default value

nature, including: of ALL.
l ALL: All
l INT: International
number
l NAT: Domestic
number
l LOC: Local
number
l NESL: Network
specific nature
l UNK: Attribute
unknown
l ISUP_BICC_0X08
: ISUP&BICC(0X-
08)
l ISUP_BICC_0X7
E: ISUP&BICC(0
X7E)
DIGIT Analyzer number It is a mandatory parameter, consisting of 1~40

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.
1-59


Description
NAME Alias It is an optional parameter, consisting of 0~50

characters.
It is used to specifically describe the called number
analysis to make it easily recognized.
SPECRST Special analysis result It is used to specify the index number of the
rule 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.
SPECIDX Special analysis result It is used to specify the index number of the special
index analysis result of the associated called number.
This parameter must be defined by command ADD
SPECRST 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.
1-60


Description
CAT Call service types, It is an optional parameter. It is used to specify

including the options in the service type triggered by this number, and
Table 1-24 determine the direction of this call. The system
adopts “vacant number” by default.
l The called number of the local office is
analyzed to MSCO (MSC common service).
l The roaming number of the local office is
analyzed to MSLL (MSC local service).
l The roaming number of other office is
analyzed to MSLO (MSC local outgoing
service).
RST1 Number analysis result l When the call service type is vacant number,
1 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.
l When the call service type is 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.
l When the call service type is 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.
l When the call service type is IP service, IP
mobile service, or independent IP service
number analysis result 1 is used to specify the
index number of the outgoing route chain.
l When the call service type is MNP outgoing
routing number analysis result 1 is used to
1-61


Description
specify the index number of the outgoing route

chain.
l When the call service type is Outgoing paid
special service 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 be defined by command ADD
CHAIN at first. Then it can be indexed here.
When the call service type is Mobile emergency
special service, Local-office paid special
service or Local-office free special service,
number analysis result 1 is used to specify the
special-service number. This parameter must be
defined by command ADD SSPN at first. Then it
can be indexed here.
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 l It is used to specify the index number of

2 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.
l 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.
l When the call service type is OVERLAY:
CAMEL service triggered by MO, or
OVERLAY: 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.
1-62


Description
RST3 Number analysis result l It is used to specify the index number of

3 CAMEL access subscription information of the
called subscriber. This parameter must be
defined by command ADD CAINFO at first.
l When the call service type is OVERLAY:
CAMEL service triggered by MO, or
OVERLAY: 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 3 must
be fixed to 0.
CHAINAL Route chanin analysis It is used to specify the analysis index number of
index 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.
BACKCHAINAL Backup chain set It is used to specify the analysis index number of
the route chain. This parameter must be defined
by command ADD CHAINAL at first.
RNLEN Length of the carried When the call service type is MNP outgoing
routing number routing, it is configured to the length of the carried
routing number. When the call service type is other
types except the above-listed, it must be fixed to 0.
MINLEN Minimum digit length It is an optional parameter, which is an integer

of numbers ranging from 0 to 255, with a default of 3. It is used
to specify the minimum digit length of the analyzed
number required for call connection.
l 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.
1-63


Description
l 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.
l 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.
MAXLEN Maximum digit length It is an optional parameter, which is an integer

of numbers ranging from 0 to 255, with a default of 20. It is
used to specify the maximum digit length of the
analyzed number required for call connection.
l 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.
l 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.
OVLYPRI OVERLAY priority, It is used to the priority relationship between

including: triggering the intelligent service based on CSI
l NO (No priority): and triggering the intelligent service based on
Trigger the OVERLAY. The system adopts No Priority
intelligent service by default. When the call service type is
based on CSI OVERLAY(CAMEL service triggered by MO), this
at first, and parameter is effective. Otherwise, this parameter
then trigger the is ineffective.
intelligent service
again based on
OVERLAY
l HCSI (Higher
than the CSI in
priority): Trigger
the intelligent
1-64


Description
service based on
OVERLAY at first,
and then trigger
the intelligent
service again
based on CSI
REL Voice channel release It is an optional parameter. It indicates a resource

mode, including: release mode when subscribers hook on. In
l CING (calling general, select NO. Select CED for special
control release): numbers.
The calling party
controls whether
to release the
call. In this mode,
when only the
called party hooks
on, the call still
can continue.
l 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.
l NO (non-control
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.
1-65


Description
NET Type of the destination It is an optional parameter, with a default of 1. For

network 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.
NAT Number address It is an optional parameter. It is used to replace

attribute, including: the address attribute of the analyzed number. In
l DEF(default general, it is set to DEF, or is set according to the
attribute): Do requirements of the peer end.
not replace the
address attribute
of the analyzed
number.
l INT (international
number): Replace
the address
attribute of the
analyzed number
with international
number.
l NAT (national
number): Replace
the address
attribute of the
analyzed number
with national
(valid) number.
l LOC(local
number): Replace
the address
attribute of the
analyzed number
with local number.
l NES: Network
specific nature
l UNK (attribute
unknown):
Replace the
address attribute
of the analyzed
number with
unknown
1-66


Description
l ISUP_BICC_0
X08 ISUP&BICC
0X08
l ISUP_BICC_0
X7E ISUP&BICC
0X7E
TIMELMT Maximum call duration It is used to specify the maximum call duration
(minute) 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.
PFXLEN Toll prefix + Area code It is an optional parameter, which is an integer,

length ranging from 0 to 15. When the call service type
is national/international toll service, this parameter
needs to be configured.
ENOPT Enabled options Refer It is an optional parameter. In general, select

to Table 1-25 for details CCS7 (Automatically sending the calling number
when using CCS7 for outgoing services) and
(No call when the called number exceeds the
maximum digit length).
DDCPLAY Whether to play the It is used to specify whether to play the DDC tone
DDC tone, including: in the local office. The system adopts NONE by
l NONE (Not default. The purpose of configuring whether to play
playing the DDC the DDC tone in the number analysis configuration
tone): It is not is to avoid no tone play or repeated tone play
required to play caused by inconsistent tone play configuration
the DDC tone in during inter-office DDC calls.
the local office.
l PLAY (Playing the
DDC tone): It is
required to play
the DDC tone in
the local office.
1-67


Description
VAD Voice Activity It is used to specify whether to start the VAD

Detection (VAD) flag, function. The system adopts INVALID by default.
including:
l INVALID: Invalid
l ALERTCALL:
VAD Closing
Control(alerting
status and calling
status)
l ALERT:
VAD Closing
Control(alerting
status)
CALLSERVPRIL- Call type priority, It is used to specify the call priority. The system
VL including: adopts INVALID by default. The call priority has
l INVALID: The call two functions. In one case, in the softswitch office
priority is invalid. in the toll softswitch network, the voice coding
l HIGHEST: The format can be dynamically selected according
call has the to the call priority and the load on the IP bearer
highest priority. network. In another case, based on the combined
l HIGHER: The information of office ID and priority configured in
call has a priority the number analysis configuration, the final priority
one level lower of a call is got to perform load control.
than the highest
priority.
l NORMAL: The
call has a priority
one level lower
than the higher
priority.
l LOW: The call has
the lowest priority
Table 1-24 Call Service Types
Call Service Types Meanings
NONE Null Number
MSLO Outgoing/Local Service Of The Local Network (msc)_G
LOL Outgoing/Local Service Of The Local Network
LORU Local Network Outgoing/Rural(Network) Call Service
1-68

DWTM Domestic Toll (Within Macro Cell) Manual Service
DWTA Domestic Toll (Within Macro Cell) Auto-Service
DBTM Domestic Toll(Between Macro Cell) Manual Service
DBTA Domestic Toll(Between Macro Cell) Auto-Service
INTM International Toll Manual Service
INTA International Toll Automatic Service
LSPA Paid Special Service Of The Current Office
LSFR Free Special Service Of The Current Office
OUPA Outgoing Paid Special Service
OUFR Outgoing Free Special Service
CENTL Local Call Within The CENTREX Business Group
CENTO Outgoing Call Within The CENTREX Business Group
EQACL Equal Access:CIC Of The Subscribed Operator_G
EQACO Equal Access:Non-Local-Network CIC_G
STONE Announcement Service,CAT_SEND_TONE
DDCI DDC Direct Collect Incoming_G
DDCC DDC Local Direct Collect Call_G
DDCO DDC Direct Collect Outgoing_G
DDCCO DDC Local Collect Outgoing_G
MSLTE MSC Domestic Toll(Roaming Number)
MSITE MSC International Toll(Roaming Number)
IP IP Fixed Service
SSP SSP Charging And Querying Service
IPMO IP Mobile Service
ALIP Independent IP Service
OVMO OVERLAY: MO-Triggered CAMEL Service
OVMT OVERLAY: MT-Triggered CAMEL Service
MNP Mobile Number Portability
MNPR Mobile Number Portability Routing
H323 H323 Call(G)
MOIMC Special Service Of Mobile Emergency_G
E911FREE E911 Free Special Service Of The Current Office
1-69

HONET HONET_G
SSSP Independent SSP Outgoing Service_G
IGWA IGW Supplement Service_G
DASA Selector Analysis Service(Virtual IGW)_G
OCIC Local Valid CIC Service_G
OUPAOD Outgoing Paid Special Service(Can Dial When Overdue)_G
LINTS Current Office Intelligent Service_G
SHLRQ SHLR Querying Service_G
IGWC IGW Common Service_G
ISSPQ IGW SSP Charging And Querying Service_G
LOCALLOST Local Outgoing Lost Hint
IGWOV IGW OVERLAY Prefix Service Of The Current Office_G
IGWDDCIN IGW DDC Direct Collect Incoming_G
IGWDDCLOCAL IGW DDC Local Direct Collect Call_G
OVPRE OVERLAY prefix incoming service_G
OVCS OVERLAY calling service_G
MSCO MSC common service_G
MSLL MSC local and current office service(Roaming number)_G
TEST Test call_G
LNP Local Number Portability_G
LNPR Local Number Portability Routing_G
MRBMON MRB Tone Monitor
MSCRELCALL MSCS Call Release Service
Table 1-25 Enabled Options
Enabled Options Meanings
CHGK Change Calling User Kind
CEC Charge as emergency call
CHGN Number Change By The Subscriber
MAIL 166 Voice Mailbox Service_G
RRTO Reroute After Outgoing Failure
NUMLEN Estimate Number Length_G
NOLMTLEN No Limited Time Length For Tone_G
1-70

Enabled Options Meanings
IGFWD Ignore Redirection Info In Outgoing Call_G
ECL Use Emergency Call Level_G
NTC Not Trigger Calling The Intelligent Service_G
NCEL Monitoring Number Incoming_G
LSIN Interception number incoming
CON Early Send Connect Message(IGW Only)_G
SHLRF Not Trigger SHLR Query_G
SHLRG Over Net Number In SHLR_G
JUDG Need Judge IP Resource_G
REBO Restrain HOMEBOX Operation_G
TCUG Indicates whether to trigger trunk CUG limit
LONGNUMCUT Cut Over length Number
ANSAN Answer The Call When Play Announcement_G
Example: Configure the called number analysis with the following requirements.
l Analyzer entry: 1
l Analyzed number: 13901234
l Call service type: MSC common service
The command is:
ADD TPDNAL: ENTR= 1, NANNAT= ALL, DIGIT= "13901234", SPECRST= 0, SPEC

IDX= 0, CAT= MSCO, RST1= 0, RST2= 0, RST3= 0, CHAINAL= 0, BACKCHAINAL=
0, RNLEN= 0, MINLEN= 3, MAXLEN= 20, OVLYPRI= NO, REL= NO, NET= 1, NAT
= DEF, TPDDI= 0, TPDLYDDI= 0, DDIOVERB= 0, IWVIDEO= LSUP, TIMELMT= 0,
AUXDAS= 0, A6= 0, PFXLEN= 0, FAXIDX= 0, AVIDX= 0, DVIDX= 0, ADATAIDX= 0,
DDATAIDX= 0, DDCPLAY= NONE, VAD= INVALID, CALLSERVPRILVL= INVALID,
RERTS= 0, INCHAIN= NO, RECMDMGWNODEID1= 0, RECMDMGWNODEID2= 0,
ICTT= 0, BICT= NO, TNID= 0, GNM= NORMAL, STBILL= INVALID, HOPDAS= 0, CA
LLRIGHT= 0, CALLINGTPTDAS= 0, CALLINGOPTDAS= 0, IVVR= NO, MCA= NO,
IMSCENTR= NO, WANTL= 0, TONETST= NO, OPID= 0, RERT= 0;
Example: Configure the roaming number analysis of the local office with the following
requirements.
l Analyzer entry: 1
l Analyzed number: 115901234
l Call service type: MSC local service
The command is:
1-71

ADD TPDNAL: ENTR= 1, NANNAT= ALL, DIGIT= "15901234", SPECRST= 0, SPEC

IDX= 0, CAT= MSLL, RST1= 0, RST2= 0, RST3= 0, CHAINAL= 0, BACKCHAINAL=
0, RNLEN= 0, MINLEN= 3, MAXLEN= 20, OVLYPRI= NO, REL= NO, NET= 1, NAT
= DEF, TPDDI= 0, TPDLYDDI= 0, DDIOVERB= 0, IWVIDEO= LSUP, TIMELMT= 0,
AUXDAS= 0, A6= 0, PFXLEN= 0, FAXIDX= 0, AVIDX= 0, DVIDX= 0, ADATAIDX= 0,
DDATAIDX= 0, DDCPLAY= NONE, VAD= INVALID, CALLSERVPRILVL= INVALID,
RERTS= 0, INCHAIN= NO, RECMDMGWNODEID1= 0, RECMDMGWNODEID2= 0,
ICTT= 0, BICT= NO, TNID= 0, GNM= NORMAL, STBILL= INVALID, HOPDAS= 0, CA
LLRIGHT= 0, CALLINGTPTDAS= 0, CALLINGOPTDAS= 0, IVVR= NO, MCA= NO,
IMSCENTR= NO, WANTL= 0, TONETST= NO, OPID= 0, RERT= 0;
1.2.1.7 Creating Number Transform Index
Abstract
Number change index configures the basic number change method for number analysis.
Prerequisites
l The number analysis selector and called number analysis configuration is completed.
Steps
SET: NEID= 11;
2. Create number transform index, the command is ADD DDI.
The explanation of the main parameters in command ADD DDI is shown in Table 1-26.
Table 1-26 Parameters in the ADD DDI Command
DDI Number Transform Index This parameter uniquely identifies

a number change. Its value is an
integer ranging from 1 to 4,096.
NAME Alias This parameter specifies a number

change. Its value is a string of up
to 50 bytes.
1-72

MTHD Number Transform Mode, including: This parameter is mandatory and its
l ADD: Add Number value is of enumeration type.
l DEL: Delete Number
l OVR: Modify Number
l REP: Replace
l ORG: No Transform_G
l HCODE: H Code Transform
l PRO: Only Transform Address
Nature
OFFSET Start Position Of The Number This parameter specifies the start
position of number change. Its value
is an integer ranging from 0 to 48.
LENGTH Deleted Or Modified Number Length This parameter specifies the length
of the number to be deleted or
modified. Its value is an integer
ranging from 0 to 48.
DN Added/Modified/Replaced Number This parameter specifies the number

to be added or replaced. Its value is
a string of 0 to 40 characters.
NEWNAT New Address Nature, including: This parameter is optional and its
l DEF: Default attribute value is of enumeration type.
l INT: International number
l NAT: Domestic number
l LOC: Local number
l UNK: Attribute unknown
PI Presentation indicator, including: This parameter is optional and its

l PA: Presentation Allowed value is of enumeration type.
l PR: Presentation Restricted
l NO: Address not Available
l REV_11: Reserve(03)
l PASS: Pass
IC Incomplete indicator, including: This parameter is optional and its

l COM: Complete value is of enumeration type.
l INC: Incomplete
l PASS: Pass
Example: create number transform index, add 0086 in front of the first digit of the
number. The command is:
ADD DDI: DDI= 1, MTHD= ADD, OFFSET= 1, LENGTH= 0, DN= "0086", NEWNAT=
DEF, PI= PASS, IC= PASS, NEWTYPE= 0;
1-73

Example: create number transform index, delete the two digits of number starting from
the first digit. The command is:
ADD DDI: DDI= 2, MTHD= DEL, OFFSET= 1, LENGTH= 2, NEWNAT= DEF, PI= PA
SS, IC= PASS, NEWTYPE= 0;
Example: create number transform index, change the three digits of number starting
from the first digit as 0086. The command is:
ADD DDI: DDI= 3, MTHD= MOD, OFFSET= 1, LENGTH= 3, DN= "0086", NEWNAT=
Example: create number transform index, replace the number with 0086. The
command is:
ADD DDI: DDI= 4, MTHD= REP, OFFSET= 1, LENGTH= 0, DN= "0086", NEWNAT=
Example: create number transform index, change to address nature to international

number. The command is:
ADD DDI: DDI= 5, MTHD= MOD, OFFSET= 1, LENGTH= 0, NEWNAT= INT, PI= PA
SS, IC= PASS, NEWTYPE= 0;
Tip:
Number attribute change can be used seperately or together with number adding,
deleting, modifying and substitution.
Example: create number transform index the number transorm mode is original
No-change works only in CDR number change. The command is:
ADD DDI: DDI= 6, MTHD= ORIGINAL, OFFSET= 1, LENGTH= 0, NEWNAT= DEF,
PI= PASS, IC= , NEWTYPE= 0PASS;
1.2.2 Creating Mobile Number Prefix

Prerequisites

1-74

Context
This function is used to configure a mobile number prefix. The system determines whether
a number is a mobile number or not based on the number prefix. When the system collates
number formats, organizes number address attributes or judges the validity of a dialing
method, the system may need to know whether a number is a mobile number or not. Then,
this function is helpful.
The international format of a fixed number is country code + area code + subscriber
number and the international format of a mobile number is country code + mobile
subscriber number. When the system collates numbers in international format, it needs
to analyze whether the number is a fixed number or a mobile number. Then, the system
can handle the area code correctly.
Steps
SET: NEID= 11;
2. Create mobile number prefix, the command is ADD MCODE.
The explanation of the main parameters in command ADD MCODE is shown in Table
1-27.
Table 1-27 Parameters in the ADD MCODE Command
Parameter Parameter Instruction

Name Description
CODE MSISDN Prefix Mobile number prefix. The value of this parameter is
a string consisting of 1 to 10, *, #, D and E.
NAME Alias The value of this parameter is a string describing

a mobile number prefix.
Example, create mobile number prefix with the following requirements.

l MSISDN Prefix: 18
l Alias: 18
The command is:

ADD MCODE: CODE= "18", NAME= "18";
1-75

1.2.3 Creating Number Transform for CLIP (optional)

Abstract
Some international offices require that calling line presentation should be of this format:
national prefix (usually 0)+NDC+SN.
Prerequisites

Steps
SET: NEID= 11;

2. Create number transform for CLIP, the command is ADD OPNUMTRFDSP.
The explanation of the main parameters in command ADD OPNUMTRFDSP is shown
in Table 1-28.
Table 1-28 Parameters in the ADD OPNUMTRFDSP Command
CLINGTYPE Calling User Type, including: This parameter is mandatory and

l LOCMB: LAN its value is of enumeration type.
l OTHMB: Other Mobile
l LOCFIX: Local Fixed
l OTHFIX: Other Fixed
l INTL: International
l UN: Unknown
l INVALID: Invalid
l INTROAM: International
Roam
1-76

CLEDTYPE Called User Type, including: This parameter is optional and its
l LOCMB: LAN value is of enumeration type.
l OTHMB: Other Mobile
l LOCFIX: Local Fixed
l OTHFIX: Other Fixed
l INTL: International
l UN: Unknown
l INTROAM: International
Roam
l ALL: All
NAME Alias This parameter is optional and

its value is a string of 0 to 50
characters.
NUMCHG Calling Number Format, This parameter is optional and its

l NOTRF: Not Transform
l INTL_INTL: International
Prefix,Number attribute is
international
l INTL_UNKN: International
unknown
l NO_INTL_INTL: No
International Prefix,Number
attribute is international
l NAT_NAT: National
Prefix,Number attribute
is national
l NAT_UNKN: National
unknown
l NO_NAT_NAT: No national
national
l NO_NDC_LOC: No
NDC,User number
format,Number attribute
is local
l NO_NDC_UNKN: No
NDC,User number
format,Number attribute
is unknown
1-77

l NO_NDC_NAT_NAT: No
NDC,national prefix,Number
attribute is national
l NO_NDC_NAT_UNKN: No
NDC,national prefix,Number
attribute is unknown
l DEFOPDN: Default calling
number
l DEFOPDN_INTL:
International format Default
calling number
l ONHC_No_INTPREFIX:
ONHC, INT Format Number
With Prefix
l ONHC_With_INTPREFIX:
ONHC, INT Format Number
With Prefix
SI Screening indicator, including: This parameter is optional and its

l REV_00: Reserve(00) value is of enumeration type.
l UP: User Provided
l NP: Network Provided
l PASS: Pass
PI Presentation indicator, including: This parameter is optional and its

l PA: Presentation Allowed value is of enumeration type.
l PR: Presentation Restricted
l NO: Address not Available
l PASS: Pass
IC Incomplete indicator, including: This parameter is optional and its

l COM: Complete value is of enumeration type.
l INC: Incomplete
l PASS: Pass
NPI Numbering Plan indicator, This parameter is optional and its

l E164: E.164
l X121: X121
l F69: F69
l PRIVATE: PRIVATE
l PASS: Pass
TRFAS Number Transform Selector The value is an integer ranging

from 0 to 2,048.
1-78

Example: create number transform for CLIP with the following requirements:
l Calling User Type: LAN
l Called User Type: All
l Alias: OPNUMTRFDSP_LOCMB
l Calling Number Format: national prefix, number attribute is unknown
l Other parameters: default.
The command is:
ADD OPNUMTRFDSP: CLINGTYPE= LOCMB, CLEDTYPE= ALL, NAME= "OPNUMT
RFDSP_LOCMB", NUMCHG= NAT_UNKN, SI= PASS, PI= PASS, IC= PASS, NPI= PASS,
TRFAS= 0;
1.2.4 Variables Configuration

1.2.4.1 Configuring Security Variable for Adding International Prefix to National Calls
Abstract
This topic introduces the security variable configuration for adding international prefix to
national calls.
Prerequisites
l The data configuration is completed.
Steps
> Security Variable > WCN Security Variable > CS Security Parameter. The CS
Security Parameter tab pops up.
2. On the CS Security Parameter tab, select Whether to delete home MCC where
analysis the MSISDN, and click on the sub-toolbar to enter the editing status, select
YES, as shown in Figure 1-6.
1-79

Figure 1-6 CS Security Parameter Configuration

1.2.4.2 Setting MSISDN Length in Security Variable
Abstract
This topic introduces the System Control configuration related to MSISDN length.
You must examine the Length of MSISDN before increasing in international offices and
make sure the value is correct. Otherwise, MT fails.
Prerequisites
l The data configuration is completed.
Steps
1. In the NetNumen M30 window, select Views > Professional Maintenance > MSCS
> Security Variable > WCN Security Variable > System Control. The System
Control tab pops up.
2. On the System Control tab, select the corresponding parameters, and click on the
sub-toolbar to enter the editing status, as shown in Figure 1-7.
l Phone number upgrading status setting: choose After upgrade.
l Length of MSISDN before increasing: enter 11.
1-80

l Position for insertion value: enter 3.

l Insertion value on increasing: enter 0.
Figure 1-7 Call Control Parameter Configuration

1.2.5 Debugging Interior Calls

Abstract
This topics describes the debugging procedure for interior calls.
Prerequisites
l Signaling interconnection debugging is completed.
l Location update debugging is completed.
l Call data configuration is completed.
Steps
1. Make preparations for debugging.
l MS LU succeeds.
LU debugging for MS succeeds and subscriber information can be queried in VLR.

l MGW registration succeeds.
1-81

Check MGW state with the command SHOW MGWSTAT.

The normal status is In Service.
l Physical resources of MGW are normal.
Check sub-unit status of resources borads in Dynamic Management.
2. Check bearer status at interface Iu and A.
l For Iu interface, check AAL2 status when adopting ATM bearer. Check IP
connection when adopting IP bearer.
l For A interface, check A interface circuits status when adopting TDM bearer.
Check IP connection when adopting IP bearer.
3. Open Signaling Trace and Failure Observer, make interior calls and debug
according to the signaling and call losses.
l Signaling Trace: Open user signal tracing, open SCCP signaling tracing in MTP3
signaling tracing to HLR and open SCCP signaling tracing in MTP3 signaling
tracing to BSC/RNC.
l Failure Observer: Track failure observation of MSCS and SCCP.
1.3 Inter-office Calls Data Configuration and Debugging

When the local-office call debugging is completed, and the local-office call is successfully
made, perform inter-office calls data configuration and debugging.
When interconnecting with end office, GMSC and TMSC, you need to configer resources
for inter-office calls beside signaling interconnection.
You need to configure PCM allocation and VTCD load-sharing for RTP/RTCP at MGW.
You need to configure trunk groups, trunk group tags, PCM system,inter-MGW PCMs,
outgoing routes, outgoing route groups and outgoing route links at MSCS.
Inter-office calls data configuration and debugging flow is as follows:
1. Trunk data configuration, refer to 1.3.1 Trunk Data Configuration.
2. Routing data configuration, refer to 1.3.2 Routing Data Configuration.
3. Timers configuration, refer to 1.3.3 Modifying Pre-defined Timer.
4. Inter-office calls debugging, refer to 1.3.4 Debugging Inter-office Calls.
1.3.1 Trunk Data Configuration

The related operations of the trunk data configuration are as follows.
1-82

1 Creating a DT trunk When the A interface and ADD TG DT

group Ai interface adopts the TDM
bearer, or when MGWs are
interconnected through the
TDM bearer, create DT trunk
groups
Creating a PRA trunk When the PRA is adopted, ADD TG DT

group create PRA trunk groups
Creating an ATM trunk When the ATM bearer is ADD TG ATM

group adopted between MGWs,
create ATM trunk groups
Creating a RTP trunk When the IP bearer is ADD TG RTP

group adopted between MGWs,
create BICC trunk groups
2 Creating a PCM system DT, ATM, RTP, and RTP ADD SPCM
trunk groups all need to be
created with PCM systems
Creating a PCM system When the MGWs managed ADD INPCM

between MGWs by one MSCS are
interconnected through
TDM circuits, no trunk group
or trunk route needs to be
created, and only PCM
systems between the MGWs
need to be created
1.3.1.1 Creating a DT Trunk Group
Abstract
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.
Prerequisites
1-83

l The adjacent office to which the trunk group points is created.

l The trunk group No. range is set in the resource management system.
Steps
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
1-29.
Table 1-29 Parameters in the ADD TG DT Command
TG 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.
OFC ID of the office where the trunk It is a mandatory parameter. It is

group belongs used to specify the corresponding
office of the trunk group. This
parameter must be defined by
command ADD ADJOFC at first.
NODE Node No. of the MGW where the It is a mandatory parameter. Select
trunk group belongs the MGW topology node connected
with the 2G MSC/PSTN node.
MODULE Module where the trunk group It is a mandatory parameter.

belongs It indicates a service module.
Different trunk groups to the same
office need to be allocated to
different CMP modules.
1-84

LINE Inter-office line signal identification. It is an optional parameter. It is

Options include: used to identify the line type of
l GBSC: G-BSC Ground this trunk. Select it according to
Circuit(0) inter-office signaling. For the Ai
l TUP: Interoffice Common interface, select ISUP or TUP.
Channel Signaling TUP
l ISUP: Interoffice Common
Channel Signaling ISUP
l CASDLDC: CAS-DL/DC(3)
l R2: R2 Signaling
l BICC: BICC Type
l ANU: ANU Signaling
l SORMUP: SORMUP Signaling
VDT Virtual circuit The default value is FALSE.

consisting of 0~64 characters. It is
used to specifically describe a trunk
group to make it easily recognized.
KIND Trunk group types, including the It is an optional parameter. If BSC

following three types: is selected for the inter-office line
l IN (incoming trunk group): signal identification, it must be
Indicates that the local office configured to BIDIR.
processes the incoming calls
from the peer-end office.
l OUT (outgoing trunk group):
Indicates that the local office
only processes the outgoing
calls to the peer-end office.
l BIDIR (Two-way trunk group):
processes both the incoming
calls from the peer-end office
and the outgoing calls to the
peer-end office
1-85

INREG Incoming register signaling flag, It is an optional parameter, with a

including options: default of INVALID.
l INVALID: Invalid Value
l MFC: Outgoing/Multi-
Frequency Control
l MFP: Outgoing/Multi-
Frequency Pulse
l DTMF: Outgoing/Double Tone
Multi-Frequency
l DP: Outgoing/Direct Current
Pulse
l MF: Outgoing/Multi-Frequency
OUTREG Outgoing register signaling flag, It is an optional parameter, with a

including options: default of INVALID.
l INVALID: Invalid Value
l MFC: Outgoing/Multi-
Frequency Control
l MFP: Outgoing/Multi-
Frequency Pulse
l DTMF: Outgoing/Double Tone
Multi-Frequency
l DP: Outgoing/Direct Current
Pulse
l MF: Outgoing/Multi-Frequency
TPDAS DAS for the called number It is an optional parameter. It is

used 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.
OPDAS DAS for the calling number It is used to analyze the calling
number in an incoming call. This
command ADD DAS at first. Then
it can be indexed here.
1-86

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.
PREDAS DAS for pre-analyzing the called It is used to pre-analyze the called
number number in an incoming call. This
command ADD PREDAS at first.
TPINDAS Incoming called number transform It is an optional parameter, ranging

selector from 0 to 2,048.
OPINDAS Incoming calling number transform It is an optional parameter, ranging

TPOUTDAS Outgoing called number transform It is an optional parameter, ranging

OPOUTDAS Outgoing calling number transform It is an optional parameter, ranging

PLSCLDDAS Pulse meter called number It is an optional parameter, ranging

transform selector from 0 to 2,048.
PLSCLRDAS Pulse meter calling number It is an optional parameter, ranging

BEARWAY Bearer establishment direction, It is an optional parameter. Select

including the following three types: NODIR for DT trunk groups.
l NODIR: The inter-office bearer
is established without direction.
l BACK: The inter-office bearer
is established based on the
backward mode.
l FORWD: The inter-office
bearer is established based on
the forward mode
1-87

CICSEL Circuit selecting modes, including: It is an optional parameter. It is used

l FIFO: Circular selecting to specify the trunk circuit selecting
l MIN: Minimum CIC Priority policy of the system within this trunk
l MAX: Maximum CIC Priority group, with a default of FIFO. If
l ODD: Odd Number CIC Priority this No.7 trunk group is a two-way
l EVEN: Even CIC Priority trunk group, it is recommended
l FREE: Free CIC Priority to set the circuit selecting mode
l BUSY: Busy CIC Priority to ODD/EVEN mode to prevent
l ODDASC: ODDASC contention when two exchanges
l EVENASC: EVENASC select circuits.
GATE Overload control threshold It is an optional parameter, ranging

from 0 to 100, with a default of 100.
This parameter takes effect when
levels of congestion occur and load
control is required.
SMENTERID ID of signaling modification It is an optional parameter,

entrance associated with the inter-office
signaling modification entrance. It
ranges from 0 to 65,535, with a
default of 0.
EQUC1 Cancel operation of congestion It is an optional parameter with the

level 1 default value of FALSE.
ACCL1 Call access rate 1 It is an optional parameter, ranging

from 0 to 100. The default value is
100.


100.
Example: Create a DT trunk group to the 2GMSC/PSTN office with the following
requirements:
l Trunk group ID: 28
l ID of the office where the trunk group belongs: 28
l MGW topology node No.: 101
l Line signaling flag: ISUP
l No. of the CMP module where the trunk group belongs: 7
l Method Of Circuit Selection: ODD
The command is:
1-88

ADD TG DT: TG= 28, OFC= 28, NODE= 101, MODULE= 7, LINE= ISUP, VDT= FALSE,
KIND= BIDIR, INREG= INVALID, OUTREG= INVALID, TPDAS= 0, OPDAS= 0, ROA
MDAS= 0, PREDAS= 0, TPINDAS= 0, OPINDAS= 0, TPOUTDAS= 0, OPOUTDAS=
0, PLSCLDDAS= 0, PLSCLRDAS= 0, BEARWAY= NODIR, CICSEL= ODD, GATE=
100, SMENTERID= 0, EQUC1= FALSE, ACCL1= 100, EQUC2= FALSE, ACCL2= 100,
HOPCUN= 20, CASOPLEN= 10, VMSCIDX= 0, BUSYRATE= 100, FAILCONVIDX=
0, DISINDEX= 0, MLPPDM= 4294967295, SUPERCLIINDEX= 0, AIFTCRES= "GSM-
FR"&"GSM HR"&"GSM-EFR"&"FR-AMR"&"HR AMR"&"OFR AMR-WB"&"OHR AMR-W
B"&"FR AMR-WB"&"OHR AMR"&"CSD", MNPDAS= 0;
1.3.1.2 Creating a PRA Trunk Group
Abstract
When the PRA is adopted, create PRA trunk groups.
Prerequisites
l The trunk group No. range is set in resource configuration.
Steps
SET: NEID= 11;
2. Create a PRA trunk group by executing command ADD TG PRA.
The explanation of the main parameters in command ADD TG PRA is shown in Table
1-30.
Table 1-30 Parameters in the ADD TG PRA Command

needs to be planned in resource
configuration in advance.
1-89



LINE Inter-office line signal identification It is an optional parameter. It is

used to identify the line type of this
trunk. It is used to identify the line
type of this trunk, with a default of
PRA.


peer-end office
INREG Incoming register signaling flag It is an optional parameter, with a

default of INVALID.
1-90

OUTREG Outgoing register signaling flag It is an optional parameter, with a

default of INVALID.

here.

used.






1-91


backward mode.
the forward mode



default of 0.


100.


100.
1-92

VMSCIDX Virtual MSC index It is an optional parameter, ranging

from 0 to 65,535.
BUSYRATE Usage ratio of trunk It is an optional parameter with the

default value of 100.
FAILCONVIDX Fail reason mapping index It is an optional parameter, ranging

from 0 to 65,535.
IOI Carrier ID It is an optional parameter, and max

length is 63 characters.
SUPERCLIINDEX Super cli index It is an optional parameter, ranging

from 0 to 2,048.
MNPDAS MNP number DAS It is an optional parameter, ranging

from 0 to 2,048.
Example: Create a PRA trunk group with the following requirements.

l No. of the module processing the trunk group: 7
l Inter-office line signal identification: PRA
The command is:
ADD TG PRA: TG= 102, OFC= 102, NODE= 101, MODULE= 7, LINE= PRA, KIND=
BIDIR, INREG= INVALID, OUTREG= INVALID, TPDAS= 0, OPDAS= 0, ROAMDAS=
0, PREDAS= 0, TPINDAS= 0, OPINDAS= 0, TPOUTDAS= 0, OPOUTDAS= 0, PL
SCLDDAS= 0, PLSCLRDAS= 0, BEARWAY= NODIR, CICSEL= ODD, GATE= 100,
SMENTERID= 0, EQUC1= FALSE, ACCL1= 100, EQUC2= FALSE, ACCL2= 100, HO
PCUN= 20, CASOPLEN= 10, VMSCIDX= 0, BUSYRATE= 100, FAILCONVIDX= 0,
DISINDEX= 0, SUPERCLIINDEX= 0, MNPDAS= 0;
1.3.1.3 Creating an ATM Trunk Group
Abstract
When the ATM bearer is adopted between MGWs, create ATM trunk groups.
Prerequisites
1-93

l The adjacent MGW office to which the trunk group points is created.
Steps
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
1-31.
Table 1-31 Parameters in the ADD TG ATM Command



LINE Inter-office line signal identification It is an optional parameter. It is

used to identify the line type of this
trunk. It is used to identify the line
type of this trunk, with a default of
BICC.

1-94


peer-end office

default of INVALID.

default of INVALID.

here.

used.
1-95








backward mode.
the forward mode

1-96



default of 0.


100.


100.

from 0 to 65,535.


from 0 to 65,535.
DISINDEX Incoming call number analysis It is an optional parameter, ranging

process index from 0 to 255.
MLPPDM MLPP domain It is an optional parameter.

REDIRCV Cause value for redirection It is an optional parameter, ranging

from 0 to 255.

from 0 to 2,048.

from 0 to 2,048.
Example: Create an ATM trunk group with the following requirements.
1-97


l User alias: RNC
l Inter-office line signal identification: BICC
The command is:
ADD TG ATM: TG= 100, OFC= 100, NODE= 101, MODULE= 7, LINE= BICC, KIND=
BIDIR, INREG= INVALID, OUTREG= INVALID, TPDAS= 0, OPDAS= 0, ROAMDAS=
0, PREDAS= 0, TPINDAS= 0, OPINDAS= 0, TPOUTDAS= 0, OPOUTDAS= 0, PL
SCLDDAS= 0, PLSCLRDAS= 0, BEARWAY= NODIR, CICSEL= ODD, GATE= 100,
SMENTERID= 0, EQUC1= FALSE, ACCL1= 100, EQUC2= FALSE, ACCL2= 100, HO
PCUN= 20, CASOPLEN= 10, VMSCIDX= 0, BUSYRATE= 100, FAILCONVIDX= 0,
DISINDEX= 0, MLPPDM= 4294967295, SUPERCLIINDEX= 0, MNPDAS= 0;
1.3.1.4 Configuring an RTP Trunk Group
Abstract
When the IP bearer is adopted between MGWs, configure RTP trunk groups, which are
BICC trunk groups.
Prerequisites
l The adjacent MGW office to which the trunk group points is created.
Steps
SET: NEID= 11;

2. Add a RTP trunk group by executing command ADD TG RTP.
The explanation of the main parameters in command ADD TG RTP is shown in Table
1-32.
1-98

Table 1-32 Parameters in the ADD TG RTP Command



LINE Inter-office line signal identification, It is an optional parameter. It is

including: used to identify the line type of this
l BICC trunk.
l SIP


peer-end office
1-99


default of INVALID.

default of INVALID.

here.

used.





1-100



backward mode.
the forward mode



default of 0.


100.

1-101


100.

from 0 to 65,535.

SIPROUTESET SIP route set It is an optional parameter, ranging

from 0 to 65,534.

from 0 to 65,535.
DISINDEX Incoming call number analysis It is an optional parameter, ranging

process index from 0 to 255.
MLPPDM MLPP domain It is an optional parameter.

REDIRCV Cause value for redirection It is an optional parameter, ranging

from 0 to 255.
MAXFWD Max-forwards value It is an optional parameter, ranging

from 1 to 255.

from 0 to 2,048.

from 0 to 2,048.
Example: Create a RTP trunk group with the following requirements.

l User alias: MGW102
l Inter-office line signal identification: BICC
The command is:
ADD TG RTP: TG= 102, OFC= 102, MODULE= 7, LINE= BICC, KIND= BIDIR, INREG=
INVALID, OUTREG= INVALID, TPDAS= 0, OPDAS= 0, ROAMDAS= 0, PREDAS=
0, TPINDAS= 0, OPINDAS= 0, TPOUTDAS= 0, OPOUTDAS= 0, PLSCLDDAS= 0,
PLSCLRDAS= 0, BEARWAY= NODIR, CICSEL= ODD, GATE= 100, SMENTERID=
0, EQUC1= FALSE, ACCL1= 100, EQUC2= FALSE, ACCL2= 100, HOPCUN= 20, CA
SOPLEN= 10, VMSCIDX= 0, BUSYRATE= 100, SIPROUTESET= 0, FAILCONVIDX=
1-102

0, DISINDEX= 0, MLPPDM= 4294967295, MAXFWD= 70, SUPERCLIINDEX= 0, MNP

DAS= 0;
1.3.1.5 Creating a PCM System
Abstract
The PCM system management data associate the resources on the MGW with the
signaling on the MSCS.
Prerequisites
l The DT, ATM, or RTP trunk group is configured.
Steps
SET: NEID= 11;
2. Create a PCM system by executing command ADD SPCM.
The explanation of the main parameters in command ADD SPCM is shown in Table
1-33.
Table 1-33 Parameters in the ADD SPCM Command
TG No. of the trunk group where It is a mandatory parameter, which is an

the PCM system belongs integer, ranging from 1~4,000. 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.
1-103

PCM PCM system No. It is a mandatory parameter. 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.
MGWPCM PCM No. in the MGW It is an optional parameter. If the PCM

The corresponding trunk system belongs to a RTP or ATM trunk
group can invoke the PCM group, this parameter needs not be
resources between the start configured. If the PCM system belongs to
PCM No. in the MGW and a DT trunk group, select the corresponding
the end PCM No. PCM No. in the MGW.
INFO Self-Loop PCM Number The default value is 65,535.
NAME User alias It is an optional parameter, consisting of

0~50 characters. It is used to specifically
describe the PCM system configuration to
make it easily recognized.
E1 E1 identification It is an optional parameter, consisting of

0~50 characters. For DT trunk groups,
describes the E1 with any characters, which
can be set to “DTB/SDTB unit No.-E1 No.”.
DDF Digital Distribution Frame It is an optional parameter, consisting of

(DDF) location description 0~50 characters. 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 2G MSC/PSTN office with the following
requirements:
l No. of the trunk group where the PCM system belongs: 28
l PCM system No.: 1
l PCM No. in the MGW: 7
The command is:
ADD SPCM: TG= 28, PCM= 1, MGWPCM= 7, INFO= 65535;
1.3.1.6 Creating a PCM System between MGWs
Abstract
When the MGWs managed by one MSCS are interconnected through TDM circuits, it
is required to configure the PCM systems between the MGWs. Since the MGWs are
1-104

interconnected within the MSCS, it is required to add the bearer mode between the MGWs
in the topology configuration, but no trunk group, trunk route or other parameters need to
be configured.
Prerequisites
l The bearer mode between the MGWs is configured in the topology configuration. .
Steps
SET: NEID= 11;
2. Create a PCM system between MGWs by executing command ADD INPCM.
The explanation of the main parameters in command ADD INPCM is shown in Table
1-34.
Table 1-34 Parameters in the ADD INPCM Command

Description
INTG Trunk Group of Inner It is an optional parameter, ranging from 1 to

MGW 4,000.
PCM PCM system No. It is a mandatory parameter. Enter the PCM

system No. in the MSCS.
LOCWPCM MGW Local PCM It is a mandatory parameter. Enter the PCM

Number system No. in MGW1.
REMWPCM MGW Remote PCM It is a mandatory parameter. Enter the PCM

Number system No. in MGW2.
MODULE Management module It is a mandatory parameter. Select the No. of the

No. CMP module of managing this PCM system.
NAME User alias It is an optional parameter, which is in the format

of “Adjacent office MGW1 user alias-Adjacent
office MGW2 user alias-PCM system No.”
LOCE1 MGW Local E1 ID It is an optional parameter, which can be set to

“DTB/SDTB unit No.-E1 No.”
REME1 MGW Remote E1 ID It is an optional parameter, which can be set to

“DTB/SDTB unit No.-E1 No.”
1-105


Description
LOCDDF Description Of MGW It is an optional parameter, which can be set to

Local DDF Location “Frame No.-Row No.-Port No.”
REMDDF Description Of MGW It is an optional parameter, which can be set to

Remote DDF Location “Frame No.-Row No.-Port No.”
Example: Add a PCM system between MGWs with the following requirements.
l Trunk group of inner MGW: 102
l Management module No.: 7
l PCM system No.: 1
l PCM No. in MGW1 and MGW2: 1
The command is:
ADD INPCM: INTG= 102, MODULE= 7, PCM= 1, LOCWPCM= 1, REMWPCM= 1;
1.3.2 Routing Data Configuration

Description
Outgoing route chains are directly referred to in number analysis results. Each outgoing
route chain contains at most 4 outgoing route groups (in active/standby relationship),
and each outgoing route group contains at most 12 outgoing routes (in load sharing
relationship). The outgoing route has a one-to-one correspondence with the trunk group.
Data Configuration
The related operations of the routing data configuration are as follows.
1 Creating an outgoing Each trunk group corresponds to ADD RT

route an outgoing route.
2 Creating an outgoing Each route belongs to a route ADD RTS

route group group, and each route group
contains at most 12 routes.
3 Creating an outgoing Each outgoing route group ADD CHAIN

route chain belongs to an outgoing route
chain, and each route chain
contains at most 4 route groups.
1-106

1.3.2.1 Creating an Outgoing Route
Abstract
Each trunk group corresponds to an outgoing route.
Prerequisites
l The outgoing route No. range is set in resource configuration.
Steps
SET: NEID= 11;
2. Create an outgoing route by executing command ADD RT.
The explanation of the main parameters in command ADD RT is shown in Table 1-35.
Table 1-35 Parameters in the ADD RT Command
RT Route No. It is a mandatory parameter, which is an

integer, ranging from 1~65,535. 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. It is a mandatory parameter, corresponding

to the trunk group No. in the trunk group
configuration

0~50 characters.
RTINFO Route Send Flag It is an optional parameter.
METHOD Route Method It is an optional parameter, with a default of

SeBySe.
DLPFX Whether to delete the It is an optional parameter, with a default

prefix of the calling number of NO. If YES is selected, the prefix of the
during outgoing calls, calling number (such as 0/00) will be deleted
including NO and YES during outgoing calls.
1-107

RERT Automatic Re-routing It is an optional parameter, with a default

Chain Set Group Number value of 0.
CLISETIDX CLI Set Index It is an optional parameter, with a default

value of 65535.
Example: Create an outgoing route with the following requirements.

l Route No.: 28
l Trunk group No.: 28
The command is:
ADD RT: RT= 28, TG= 28, METHOD= SeBySe, DLPFX= NO, RERT= 0, CLISETIDX=
65535, TPDASOUT= 0, OPDASOUT= 0;
1.3.2.2 Creating an Outgoing Route Group
Abstract
Each route belongs to a route group.
This topics introduces how to create an outgoing route group.
Prerequisites
l The outgoing route No. is added.
Steps
SET: NEID= 11;
2. Creat an outgoing route group by executing command ADD RTS.

The explanation of the main parameters in command ADD RTS is shown in Table 1-36.
1-108

Table 1-36 Parameters in the ADD RTS Command

Name
RTS Route group No. It is a mandatory parameter, which is an

integer, ranging from 1~65,535. It is used to
identify a route group.
CICTYPE Circuit type It is an optional parameter, with a default of

TRUNK.
NAME User alias It is an optional parameter, consisting of 0~50

characters. It is used to specifically describe
a route group to make it easily recognized.
RTINFO Route No. and load sharing It is an optional parameter. It is in the format
proportion list of “No.-Route No.-Load sharing proportion.
When the percentage is set to 0, the poll
mode is adopted.
l SEQ: No., which is the location of the
route in the route group.
l RTVAL: Route No., associated with the
route group. This parameter must be
defined by command ADD RT at first.
l 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
l CSTVAL: Route cost.
RTFLG Route policy, including: It is an optional parameter, with a default of

l TURN: in turn TURN.
l LOW: lowest cost route
l HIGH: highest access
route
l PEAR: route by pear
CTLFLG Route control, including: It is an optional parameter. Select according

l NONE: none to actual situation.
l DYCTL: dynamic control
l PRIO: priority MGW
Example: Create an outgoing route group with the following requirements.

l Route group No.: 28
l Locaiton:1
l Route No.: 28
l Percentage: 0
1-109

The command is:

ADD RTS: RTS= 28, CICTYPE= TRUNK, RTINFO= "1"-"28"-"0"-"0", RTFLG= TURN;
1.3.2.3 Creating an Outgoing Route Chain
Abstract
Each outgoing route group belongs to an outgoing route chain, and each route chain
contains at most 8 route groups.
Prerequisites
l The outgoing route chain No. range is set in resource configuration.
Steps
SET: NEID= 11;
2. Creat an outgoing route chain by executing command ADD CHAIN.

The explanation of the main parameters in command ADD CHAIN is shown in Table
1-37.
Table 1-37 Parameters in the ADD CHAIN Command
CHAIN Route chain No. It is a mandatory parameter, which is an

integer, ranging from 1 to 65,535. 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.
RTS1 Direct route set number, used It is an mandatory parameter. Type the
to set the route group with the direct route set number.
highest priority in a route chain
during routing
1-110


0~50 characters. It is used to specifically
describe a route chain to make it easily
recognized
RTS2 No. of route group 2, used to set It is an optional parameter. Select route
the route group with the level-2 groups according to the priority order.
priority in a route chain during
routing. One route chain can be
configured with at most 4 route
groups
RTS3 No. of route group 3, used to set

the route group with the level-3
groups

groups

groups

groups

groups
1-111


groups
TPDAS DAS for the called number It is an optional parameter. It is used 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. It needs to be set only
when “Inter-MGW route chain” is set in
the called number analysis. The default
value is 0.
RTPLC Route Selection Policy Number It is an optional parameter. Select the

route selection policy number configured
in ADD RTPLC command.
Example: Create an outgoing route chain with the following requirements.

l Route chain No.: 28
l No. of Route group 1: 28
The command is:
ADD CHAIN: CHAIN= 28, RTS1= 28, RTS2= 0, RTS3= 0, RTS4= 0, RTS5= 0, RTS6=
0, RTS7= 0, RTS8= 0, TPDAS= 0, RTPLC= 0;
1.3.3 Modifying Pre-defined Timer

Abstract
SS7_TIMER_ISUP_ITUT_T7: timer of waiting for ACM, 20s by default. You may need to
modify it as 30s because ACM wait time may be longer than 20s.
G_MCC WaitStopTone: timer of waiting for tone stop, 20s by default. You need to modify
it as 2s because CF can start only after tone stops.
How to modify: first query setting of the timer with command SHOW DEFPRETMR and
then modify the macro value of the timer.
Prerequisites
1-112


Steps
SET: NEID= 11;
2. Modify pre-defined timer, the command is SET DEFPRETMR.
The explanation of the main parameters in command SET DEFPRETMR is shown in
Table 1-38.
Table 1-38 Parameters in the SET DEFPRETMR Command
TIMER Timer ID Timer ID
NAME Alias It should be consisted of Arabic

numerals, English alphabets,
underlines and spaces.
CURINTERVAL Current Interval (ms) This parameter is used to identify

the current Timer’s value.
NEWNAME New Alias It consists of 0~50 characters. It

is the name defined by a user for
easy memory.
Exmaple: modify the timer SS7_TIMER_ISUP_ITUT_T7 as 30000ms, the command

is:
SET DEFPRETMR: TIMER= 208784, CURINTERVAL= 30000;
Example: modify the timer G_MCC WaitStopTone as 2000ms, the command is:
SET DEFPRETMR: TIMER= 201051, CURINTERVAL= 2000;
1.3.4 Debugging Inter-office Calls

Abstract
This topic introduces the inter-office call debugging procedure.
Prerequisites
l Signaling interconnection debugging is completed.
l Location update debugging is completed.
1-113

l Interior call debugging is completed.
Steps
1. Make preparations for debugging.
a. Finish debugging of intra-office call service.
Note:
Sometimes, you need to commissioning inter-office call first ahead of intra-office

call is OK. Anyway, you still need to check system status and set parameters as
per the requirements for intra-office call debugging.
b. Finish interconnection with neighbor offices.

Signaling is reachable to neighbor offices.
In case of TDM bearer, you need to interconnect inter-office circuits first.
In case of IP bearer, you need to get media-plane routes reachable between
MGWs and they can ping each other.
2. Check if status of inter-office trunks is OK.
You can check status of inter-office CIC (ISUP, TUP and BICC) in Dynamic
Management or use the probe to check STATUS in R_CIC.
3. Open signaling tracing and failure observation, make outgoing calls and debug
according to signaling and call losses.
l Signaling Trace: open subscriber signaling tracing and select BSSAP, MAP,
TUP/ISUP/BICC.
à For TDM office directions, you can open ISUP and TUP signaling tracing in
MTP3 signaling tracing to neighbor offices.
à For IP office directions, you can open SCTP signaling tracking to neighbor
offices or use the packet-capture tool to track code streams at interface C
and Nb.
l Failure Observer: trace failure observation of MSCS and SCCP.
1-114

Chapter 2
Billing Configuration and
Debugging
Table of Contents
Overview ....................................................................................................................2-1
CU Office Configuration..............................................................................................2-1
MSCS Billing Parameters Configuration .....................................................................2-4
2.1 Overview
Billing configuration includes:
l CU office configuration
l MSCS billing parameters configuration
l ZXWN CU billing server configuration
The billing configuration and debugging flow is as follows:
1. CU office and bill server module configuration, refer to 2.2 CU Office Configuration.
2. On MSCS, need to set billing configuration, then CDR can be generated normally.
MSCS billing parameters configuration is as follows:
a. Charge parameter configuration, refer to 2.3.1 Setting Charge Parameter.
b. CS Network Entity Config configuration, refer to 2.3.2 Configuring CS Network
Entity Config Parameters.
c. NE-back server communication IP address configuration, refer to 2.3.3
Configuring an IP Address for Communication Between Foreground and
Background Subsystems.
Tip:
Before billing configuration, need to finish CU billing server commissioning.
2.2 CU Office Configuration

The related operations of the CU office configuration are as follows.
2-1

Create the CU NE
corresponded by the
1 Creating a CU NE ADD NE
exchange on the
background OMM system.
Connect the changing

2 Creating bill server module server module with the ADD MODULEB
charging server IP address.
2.2.1 Creating a CU NE
Abstract
Perform this procedure to create the CU NE corresponded by the exchange on the
background OMM system.
Prerequisites
The MML Terminal window is opened.
Steps
1. Create a CU NE with the ADD NE command.
Table 2-1 describes the main parameters in the ADD NE command.
Table 2-1 Parameters in the ADD NE Command
ID Unique ID of an exchange It is a mandatory parameter. It

cannot be modified once it is
created.
TYPE Type of the exchange to be created, It is a mandatory parameter. Select

including: CG.
l MSCS
l CG
SUBTYPE Sub-type of the NE, including: It is an optional parameter. Select

l NONE NONE.
l GSM_LS
l GSM_GMSC
CAPTYPE NE capacity type It is an optional parameter.
VENDOR Equipment manufacturer It is an optional parameter, with a

default of ZTE.
2-2

Chapter 2 Billing Configuration and Debugging
STATE User-defined state It is an optional parameter, with a

default of 0.
NAME User-defined exchange name It is an optional parameter,

consisting of 0~50 characters .
LOC Location of the equipment It is an optional parameter. Type

the location information of the
equipment. It is recommended to
describe it with letters and digits.
Example: Create CU NE with the following requirements.

l Office ID: 71
l Type: CU
l Alias: CU71
l Other parameter: default.
The specific command is as follows.
ADD NE: ID= 71, TYPE= CG, SUBTYPE= NONE, VENDOR= "ZTE", STATE= 0, NAM
E= "CU71";
Result
After the command is executed successfully, the CU node is added under the root node in
the OMM client interface.
2.2.2 Creating Bill Server Module

Abstract
Perform this procedure to connect the changing server module with the charging server
IP address.
Prerequisites
l You know the ID of the CU to be configured.
Steps
1. If no offcie is specified, execute command SET on the MML Terminal window or select
a NE from the system tree to specify the offcie to be configured.
Example: Select the CU with ID as 71 from the system tree.
2-3

SET: NEID= 71;

2. Create bill server module, the command is ADD MODULEB.
Table 2-2 describes the main parameters in the ADD MODULEB command.
Table 2-2 Parameters in the ADD MODULEB Command
Parameter Name Parameter Description Instructions
MODULE Module No. of the charging server Indicates the module No. of the
charging server. The module No.
must be consistent with the module
No. that is set during the installation
of the charging server. It is a
mandatory parameter ranging from
130 to 135.
IP Charging server IP Indicates the IP address of the

charging server. It is a mandatory
parameter and it must be consistent
with the IP address that is set during
the installation of the charging
server.
NAME Alias It is an optional parameter indicating

the name of the user.
Example: create bill server module with the following requirements.

l Module No. of the charging server: 130
l Charging server IP: 192.168.11.130
The command is:
ADD MODULEB: MODULE= 130, IP= "192.168.11.130";
2.3 MSCS Billing Parameters Configuration

The related operations of the MSCS billing parameters configuration are as follows.
Set billing configuration,

1 Setting charge parameter then CDR can be SET CHARGE
generated normally.
Configure variables
Configuring CS network
2 control configurations -
entity config parameters
related to charging.
2-4

Configure the IP address

Setting NE-back server
to connect each CMP
3 communication IP SET BKIP
module and the billing
dddress
server.
2.3.1 Setting Charge Parameter

Abstract
On MSCS, it is necessary to set billing configuration, then CDR can be generated normally.
Prerequisites
l You know the ID of the MSCS to be configured.
Steps
Example: Select the MSCS with ID as 11 from the system tree.
SET: NEID= 11;
2. Set charge parameters, the command is SET CHARGE.

Table 2-3 describes the main parameters in the SET CHARGE command.
Table 2-3 Parameters in the SET CHARGE Command
TIMETHD Time threshold for call ticket (m) Partial CDR's time threshold (min).
It's value range is 5~60. Default
value is 30 min.
EVTTHD Supplementary service invoke times Partial CDR's supplement services

limit active times threshold. It's value
range is 0~10. Default value is 0. 0
means this parameter is not useful.
LONGTHD Time threshold for long call(m) long time supervise threshold(min).
It's value range is 0~2880. 0 means
this parameter is not useful.
2-5

ROAM Mode for GMSC produce roam It is an option parameter.

ticket, including:
l NOFORINTRA: Produce No
local network roaming call
Tickets
l YESFORINTRA: Produce local
network roaming call Tickets
IMEIMOE Whether to produce MOE ticket, It is an option parameter.

including:
l NO: Not providing IMEI based
emergency call CDR
l YES: Providing IMEI based
emergency call CDR
CW Call waiting accounting method, It is an option parameter.

including:
l NORMAL: Represent in call
ticket for previous stable calls
l WAITING: Represent in call
ticket for the waiting call
l BOTH: Represent in both of the
above call tickets
PACDRTYPE Account method for failure It is an option parameter.

announcement, including:
l NO: No call ticket
l YES: Produce the call ticket
PRDBILL Whether to produce the periodic It is an option parameter.

ticket, including:
l NO: NO
l YES: YES
FCDRTYPE Fill rule of called number in sps-free, It is an option parameter.

including:
l FADN: Filled as dialled number
l FACN: Filled as called number
MOSTBILL Account method for tone in the MO It is an optional parameter, with a

call default of NO.
NNICFSTBILL Account method for tone in the IN It is an optional parameter, with a

call default of NO.
SPSFREENOCH- No charge for SPS FREE in trunk It is an optional parameter, with a

ARGE out bill default of NO.
2-6

CSLCDRSTYLE Produce BILL according to CSL style It is an optional parameter, with a

default of NO.
IPNOANMBILL Produce BILL when IP do not send It is an optional parameter, with a

ANM default of NO.
FILTER- Whether to filter no charging BILL It is an optional parameter, with a

NOCHARGE default of NO.
ISDNPACDR- Account method for ISDN failure It is an optional parameter, with a

TYPE VOICE default of NO.
DSTNUMMOD Destination number mode for It is an optional parameter, with a

MCC/MCF produce CAMELLEG default FCN.
Tticket, including
l FCN: Final connection number
l SCP: SPC indicative connection
number
REESTAB Produce reestablishment bill after It is an optional parameter, with a

call reestablished default of YES.
REESTFAILM- Method of release time in CDR when It is an optional parameter, with a

THD call re-establish failed, including: default of REESTTIME.
l REESTTIME: Re-establish
invocation time
l RELTIME: Call release time
l REESTFORCC: Re-establish
invocation time for MCC, call
release time for others
ALMLTCALL Alarm time threshold for long call(m) It is an optional parameter, ranging
from 0 to 2,880.
SMSMOLINFO SMS-MO contain concatenated It is an optional parameter, with a

information default of NO.
SMSMTLINFO SMS-MT contain Concatenated It is an optional parameter, with a

Information default of NO.
DCH DCH function allowed It is an optional parameter, with a

default of NO.
DCHISC DCH in stable call It is an optional parameter, with a

default of YES.
MNP MNP CHARGEincluding: It is an optional parameter, with a

l NO: Not support default of NO.
l RN: RN only
l RNTP: RN with called number
l MSRN: MSRN (RN+MSISDN)
2-7

MSRN MSRN in ticket It is an optional parameter, with a

default of NO.
BINDING Binding of the validity of trunk group It is an optional parameter, with a

and CIC, including: default of YES.
l NO
l YES
IMMEDCHARG- Charging immediately when receive It is an optional parameter, with a

ERECVANM ANM in the MO call, including: default of NO.
l NO
l YES
EMCDRNLMT Whether emergency call controlled It is an optional parameter, with a

by configured call duration limit, default of YES.
including:
l NO
l YES
MO_CAMEL The method of filling CAMEL info in It is an optional parameter, with a

MOC/MOE, including: default of OCSI.
l OCSI: OCSI priority
l OVERLAY: OVERLAY priority
Example: set charge parameters with the following requirements.

l Partial CDR's time threshold (min): 30
l Long time supervise threshold (min): 1440
l Providing roaming CDR mode: Produce Local Network Roaming Call Tickets
l Providing IMEI based emergency call CDR mod: Not providing IMEI based
emergency call CDR
l Call waiting charging mode: Call waiting flag is provided in CW CDR
l Call failure announcement charging mode: No providing CDR.
The command is:

SET CHARGE: TIMETHD= 30, LONGTHD= 1440, ROAM= YESFORINTRA, IMEIMOE=
NO, CW= NORMAL, PACDRTYPE= NO, PRDBILL= NO, FCDRTYPE= FADN;
2.3.2 Configuring CS Network Entity Config Parameters

Abstract
This topics describes the security variable configurations related to charging.
2-8

Prerequisites
l The MSCS charge parameter configuration is completed.
Steps
> Security Variable > WCN Security Variable > CS Network Entity Config. The CS
Network Entity Config tab pops up.
2. On the CS Network Entity Config tab, select the corresponding parameters, and click
on the sub-toolbar to enter the editing status, as shown in Figure 2-1.
l Whether to support PPS flag in SMS-MO CDR: whether to add prepaid flag
(PPS-FLAG)in prepaid user SMS-MO CDR, it is easier for billing center charging,
normally set as NO.
l Whether report call duration for ANN: whether to report call duration when
CAMEL users dial free call, when it set as NO: call duration in ACR will be 0
for free call answer; when it set as YES: report actual call duration in ACR for free
call answer, suggest to set as YES.
Figure 2-1 CS Network Entity Config
2-9

2.3.3 Configuring an IP Address for Communication Between

Foreground and Background Subsystems
Abstract
The MSCS based on the ETCA platform uses two GPBX1 as the accounting
dual-computer, while the MP module uses the GPBB0. The foreground CDRs are
generated by the CMP module on the GPBB0 blade, and then delivered to the SWBB0
through the internal bus. Connected with the SWBB0 through an IP network, the GPBX1
blade receives the foreground CDRs generated by the CMP module through the SWBB0
network interface.
This procedure describes how to configure the IP address to connect each CMP module
and the billing server. If the GENBKIP (Generate IP for NE-Back Communication
) parameter is selected when configuring the CMP module with the ADD MODULE
command, you need not to configure the IP address in this case.
Prerequisites
Before you begin, make sure that:
l The ID of the office to be configured is known.
l The physical configuration is completed.
Steps
SET: NEID= 11;
2. To configure an IP address for communication between the foreground and the
background subsystems, use the SET BKIP command.
Table 2-4 gives description of the parameters in the SET BKIP command.
Table 2-4 Parameters in the SET BKIP Command
Parameter Name Parameter Instructions

Description
MODULE Module number Type the CMP module number on the MSCS,
ranging from 2 to 511.
MODULENAME Module name A character string consisting of up to 50

characters.
2-10

Parameter Name Parameter Instructions

Description
PORT Port, including: Specifies the mode of delivering the foreground

l OMC (OMC CDRs generated by the CMP module, select
port): The CTRL (CTRL Plane Port).
foreground CDRs
are delivered to
the billing server
through the OMP
network interface.
It is not applicable
for the moment.
l CTRL (CTRL
plane port): The
foreground CDRs
are delivered
to the billing
server through
the SWBB0. It is
used at present.
IP IP address Type an IP address according to the billing

IP address planning. The CMP address is
configured as: 172.Bno.32.Node (Bno is the
MSCS office ID configured with the ADD NE
command, and the Node is the CMP module
number).
NEWIP New IP address If the source IP needs to be modified, you need

to type the new IP address.
NEWMASK New IP mask If the source IP mask needs to be modified,

you need to type the new IP mask. 20–subnet
mask is used, such as 255.255.240.0, if there
is no special requirement.
For example, set the IP address for communication between CMP 7 and the IP address
is 172.11.32.7, the subnet mask is 255.255.240.0, and the port is the control plane port.
The command is:
SET BKIP: MODULE= 7, MODULENAME= "CMP7", PORT= CTRL, IP= "172.11.32.7";
2-11

This page intentionally left blank.
2-12

Figures
Figure 1-1 Security Variable Configuration 1 ........................................................... 1-14
Figure 1-5 Analysis Order of Number Analyzers ..................................................... 1-45
Figure 1-6 CS Security Parameter Configuration .................................................... 1-80
Figure 1-7 Call Control Parameter Configuration..................................................... 1-81
Figure 2-1 CS Network Entity Config......................................................................... 2-9
I
Figures

Tables
Table 1-1 Parameters in the ADD GTT Command .................................................... 1-4
Table 1-2 Parameters in the ADD GT Command ...................................................... 1-8
Table 1-3 SSN ........................................................................................................ 1-12
Table 1-4 Security Variable Configuration................................................................ 1-13
Table 1-5 Parameters in the ADD IMSIANA Command .......................................... 1-18
Table 1-6 Parameters in the ADD NDCMNC Command ......................................... 1-19
Table 1-7 Parameters in the ADD NCCFG Command ............................................. 1-21
Table 1-8 Parameters in the SET SEC Command.................................................... 1-23
Table 1-9 Parameters in the SET AUTHP Command .............................................. 1-26
Table 1-10 Parameters in the SET TMSI Command................................................ 1-30
Table 1-11 Parameters in the ADD IMEIREQ Command........................................ 1-35
Table 1-12 Parameters in the SET PAGE Command............................................... 1-39
Table 1-13 DAS for Pre-analyzing the Called Number ............................................. 1-45
Table 1-14 Originating DAS..................................................................................... 1-46
Table 1-15 Forwarding DAS .................................................................................... 1-47
Table 1-16 Roaming DAS ....................................................................................... 1-48
Table 1-17 Parameters in the ADD ENTR Command.............................................. 1-49
Table 1-18 Analyzer Entry Types............................................................................. 1-50
Table 1-19 Common DAS ....................................................................................... 1-51
Table 1-20 Parameters in the ADD DAS Command ................................................ 1-52
Table 1-21 Parameters in the SET LDASTMPLT Command................................... 1-53
Table 1-22 Parameters in the ADD ACRTMPLT Command ................................... 1-56
Table 1-23 Parameters in the ADD TPDNAL Command ......................................... 1-59
Table 1-24 Call Service Types................................................................................. 1-68
Table 1-25 Enabled Options.................................................................................... 1-70
Table 1-26 Parameters in the ADD DDI Command ................................................. 1-72
Table 1-27 Parameters in the ADD MCODE Command .......................................... 1-75
Table 1-28 Parameters in the ADD OPNUMTRFDSP Command............................. 1-76
Table 1-29 Parameters in the ADD TG DT Command............................................. 1-84
Table 1-30 Parameters in the ADD TG PRA Command .......................................... 1-89
Table 1-31 Parameters in the ADD TG ATM Command ......................................... 1-94
Table 1-32 Parameters in the ADD TG RTP Command........................................... 1-99
III
Table 1-33 Parameters in the ADD SPCM Command............................................ 1-103

Table 1-34 Parameters in the ADD INPCM Command.......................................... 1-105
Table 1-35 Parameters in the ADD RT Command................................................. 1-107
Table 1-36 Parameters in the ADD RTS Command............................................... 1-109
Table 1-37 Parameters in the ADD CHAIN Command.......................................... 1-110
Table 1-38 Parameters in the SET DEFPRETMR Command ................................ 1-113
Table 2-1 Parameters in the ADD NE Command....................................................... 2-2
Table 2-2 Parameters in the ADD MODULEB Command ......................................... 2-4
Table 2-3 Parameters in the SET CHARGE Command ............................................. 2-5
Table 2-4 Parameters in the SET BKIP Command.................................................. 2-10
IV
Index
D
Destination signaling point.................... 1-2
G
GT routing ............................................ 1-2
GT translation data............................... 1-3
GT translation selector ......................... 1-3
S
SCCP................................................... 1-1
Source signaling point .......................... 1-2
V
Index

Glossary
ATM
- Asynchronous Transfer Mode
BICC
- Bearer Independent Call Control protocol
DPC
- Destination Point Code
SCCP
- Signaling Connection Control Part
SSN
- Sub-System Number
VII

SJ-20101208143956-008-ZXWN MSCS (V4.10.13) MSC Server Data Configuration Guide (MSCS II) PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

SJ-20101208143956-008-ZXWN MSCS (V4.10.13) MSC Server Data Configuration Guide (MSCS II) PDF

Загружено:

Авторское право:

Доступные форматы

ZXWN MSCS

Revision No. Revision Date Revision Reason

R1.0 2011-02-28 First edition

Serial Number: SJ-20101208143956-008

Publishing Date: 2011-02-28(R1.0)

Chapter 2 Billing Configuration and Debugging ..................................... 2-1

Prerequisite Skill and Knowledge

What Is in This Manual

Chapter 2, Billing Data Configuration Describes the data configuration of billing on CU

FCC Compliance Statement

Italics References to other Manuals and documents.

“Quotes” Links on screens.

Note: Provides additional information about a certain topic.

Checkpoint: Indicates that a particular step needs to be checked before

Tip: Indicates a suggestion or hint to make things easier or more productive

MSCS manufactured by ZTE CORPORATION meets the requirements of EU 2002/95/EC; however,

1.1 Location Update Configuration and Debugging

1.1.1 SCCP Data Configuration

SJ-20101208143956-008|2011-02-28(R1.0) ZTE Proprietary and Confidential

General rules are as follows:

SJ-20101208143956-008|2011-02-28(R1.0) ZTE Proprietary and Confidential

No. Operations Instructions Commands

1 Createing a GT translation In general, one or two GT ADD GTT

2 Creating GT translation Create the GT translation ADD GT

1.1.1.1 Creating a GT Translation Selector

SJ-20101208143956-008|2011-02-28(R1.0) ZTE Proprietary and Confidential

Table 1-1 Parameters in the ADD GTT Command

Parameter Parameter Description Instruction

GTT GT type It is a mandatory parameter, raging from 1

TT Translation type It is a mandatory parameter, ranging from 0

PLAN Numbering plan, including It is a mandatory parameter. Select E.164

SJ-20101208143956-008|2011-02-28(R1.0) ZTE Proprietary and Confidential

Parameter Parameter Description Instruction

NATURE Address attribute, including It is a mandatory parameter. Select INT.

GTTOPT SCCP Route Index It is an optional parameter, with a default of 0.

ID GT translation selector It is an optional parameter, ranging from 0

CC Country code It is an optional parameter, consisting of 0~4

SJ-20101208143956-008|2011-02-28(R1.0) ZTE Proprietary and Confidential

Parameter Parameter Description Instruction

CTRL GT translation attributes, It is an optional parameter, with the default

NAME User alias It is a mandatory parameter, consisting of

Example: Create a GT translation selector with the following requirements:

SJ-20101208143956-008|2011-02-28(R1.0) ZTE Proprietary and Confidential

The command is:

1.1.1.2 Creating GT Translation Data

SJ-20101208143956-008|2011-02-28(R1.0) ZTE Proprietary and Confidential

E214 number: It is required to configure the corresponding number in E214 format

Table 1-2 Parameters in the ADD GT Command

Parameter Name Parameter Description Instruction

GT Called GT It is a mandatory parameter, consisting

GTSL GT TransSelector ID It is a mandatory parameter, ranging from

GTDI GTDI It ranges from 0 to 256, with the default

OFCIDS 1st OFC-Turn Times List It is a mandatory parameter. The

GRP Office Group Support It is an optional parameter, with a default

SJ-20101208143956-008|2011-02-28(R1.0) ZTE Proprietary and Confidential

Parameter Name Parameter Description Instruction

OFCGRP2 2nd OFC-Turn Times List It is an optional parameter. The number

OFCGRP3 3rd OFC-Turn Times List It is an optional parameter. The number

OFCGRP4 4th OFC-Turn Times List It is an optional parameter. The number

SSN Subsystem No. Refer to Table It is an optional parameter. In the GT

NGT New GT It is an optional parameter, ranging from

NTRNTYPE New GT Translator Type It is an optional parameter, ranging from

SJ-20101208143956-008|2011-02-28(R1.0) ZTE Proprietary and Confidential