PDF SJ 20100211152857 007 ZXWN Mscs v30921 MSC Server Data Configuration Guidemgcf

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

R1.0 Feb. 28, 2010 First edition
Serial Number: SJ-20100211152857-007

Contents
About This Manual............................................. I

Declaration of RoHS Compliance ....................... I
Data Configuration Overview............................. 1
MGCF Introduction.......................................................... 1
Overall Flow of MGCF Data Configuration ........................... 2
Basic Operations of the OMM System ................................ 4
Logging in the OMM Client ........................................... 4
Entering the MML Terminal........................................... 7
Operations on the MML Terminal ................................... 8
Synchronizing Data....................................................
10
Local Office Data Configuration ....................... 13
Overview...................................................................... 14
Local Exchange Configuration .......................................... 15
Overview.................................................................. 15
Creating an Exchange ................................................ 15
Setting Province and City Information of the
Bureau ............................................................. 17
Physical Configuration ....................................................
18
Overview.................................................................. 18
Creating a Rack......................................................... 19
Creating a Shelf ........................................................ 20
Creating the UIM Unit ................................................ 21
Creating a Module ..................................................... 23
Creating other Units................................................... 25
Creating a CHUB Unit ........................................ 26
Creating a CLKG Unit......................................... 27
Creating an SIPI Unit......................................... 29
Creating a USI Unit ........................................... 30
Creating an SPB Unit ......................................... 32
Creating Background Server Node ............................... 33
Capacity Configuration ................................................... 34
Confidential and Proprietary Information of ZTE CORPORATION I

ZXWN MSCS Data Configuration Guide(MGCF)
Overview.................................................................. 34
Configuring the MGCF Office Capacity........................... 34
Configuring Service Data Area..................................... 37
Version Loading............................................................. 39
Overview..................................................................
40
Creating Version File Directory ....................................
41
Creating OMP Boot Files .............................................
44
Configuring OMP Running Parameters via Serial
Port ................................................................. 47
Configuring OMP Global Data ...................................... 58
Synchronizing All
Tables ............................................. 59
Loading Version
Files.................................................. 62
Creating MGCF Tones in
Batches...................................... 65
Office Information Configuration ...................................... 67
Overview.................................................................. 67
Creating Local Office Signaling Point............................. 67
Creating Local Office Configuration............................... 70
Resource Configuration ................................... 73
Resource Planning ......................................................... 73
Configuring Resource Attributes....................................... 73
MGCF-IM-MGW Interconnection Data
Configuration .................................................. 79
Overview...................................................................... 79
Interface IP Address Configuration ................................... 81
Overview.................................................................. 81
Creating a Loopback Interface ..................................... 82
Creating an SIPI Interface Address .............................. 83
Creating a Virtual Interface Address ............................. 85
BFD Configuration (Optional) ..........................................
87 Overview..................................................................
87
Creating BFD Authentication ....................................... 87
Creating a BFD Session .............................................. 88
Creating a Static Route ..................................................
90
Adjacent Office and Topology Configuration ....................... 92
Overview.................................................................. 92
II
Creating an IM-MGW Adjacent Office ............................ 92
Confidential and Proprietary Information of ZTE CORPORATION
Creating an MGW Voice CODEC Template ...................... 97
Creating a Topology Node ........................................... 99
Creating Inter-MGW Bear Mode ................................. 103
Overview................................................................ 106
SCTP Planning......................................................... 108
Creating an SCTP .................................................... 108
Creating an ASP ...................................................... 111
Creating an AS........................................................ 113
Creating an M3UA Static Route..................................
116
Creating the SIO Locate AS....................................... 117
H.248 Configuration.....................................................
119
Overview................................................................ 119
Creating MGC Static Data ......................................... 121
Creating MGW Static Data Template ........................... 122
Creating MGW Static Data ........................................ 124
Creating a TID Analyzer ........................................... 126
Creating a TID Analysis Entrance ............................... 127
MGCF-SIP Office Interconnection Data
Configuration ................................................ 129
Overview.................................................................... 129
SIPCC Data Configuration ............................................. 130
Overview................................................................ 130
Creating a SIP Adjacent Office................................... 130
Creating SIP Office Direction ..................................... 135
Creating SIP Adjacent Office Topology Node ................ 136
SIP Protocol Stack Configuration.................................... 141
Overview................................................................ 141
Creating an IP Link .................................................. 142
Setting the Capacity for a SIP Module.........................
144 Creating a Domain where the MGCF
Belongs ............... 145 Creating a MGCF
Host .............................................. 146
Creating Route Selector............................................
147
Creating Service Group ............................................
148
Creating an Adjacent Host ........................................
149
Creating UDP Bear...................................................
151
Creating a SIP Signaling Link ....................................
153
Creating a SIP Signaling Route ..................................
154
Creating a SIP signaling Route Set .............................
Confidential and Proprietary Information of ZTE CORPORATION III
155
Creating IP Distribution Policy ...................................
156
Creating URI Analysis...............................................
MGCF-Other-Exchange Interconnection Data

Configuration ................................................ 165
Networking Mode......................................................... 165
Office Interconnection in IP Domain ............................... 166
Overview................................................................ 166
Direct-Associated Office Configuration in IP
Domain .......................................................... 167
Overview ....................................................... 167
Creating an Adjacent Office .............................. 168
Creating an MSCS Topological Node ................... 172
M3UA-Transferred Office Configuration ....................... 175
M2UA-Transferred Office Configuration ....................... 177
Overview ....................................................... 177
Creating an M2UA IP Link.................................
179
TDM Office Interconnection ........................................... 181
Overview................................................................ 181
Creating a Signaling Link Set .................................... 183
Creating an SPB-Accessed Signaling Link .................... 185
Creating a Signaling Route........................................ 188
Creating a Signaling Office........................................ 190
Basic Service Data Configuration................... 193
Overview.................................................................... 193
Number Analysis Configuration ...................................... 193
Overview................................................................ 198
Creating Number Analysis Entrance............................ 198
Creating Number Analysis Selector ............................ 201
Setting the Template of Number Analysis Selector of
the Current Office ............................................ 203
Creating Templet of Number Analysis Selector
(Optional)....................................................... 206
Creating Called Number Analysis ............................... 211
Trunk Data Configuration ..............................................
235
Overview................................................................
235 Creating a DT Trunk Group........................................
236
Creating an ATM Trunk Group ....................................
243
Creating RTP Trunk Group.........................................
250
Creating PCM ..........................................................
254
IV Confidential and Proprietary Information of ZTE CORPORATION
Configure a PCM System between MGWs .................... 256
Route Data Configuration.............................................. 258
Overview................................................................
Creating a Route ..................................................... 259
Creating a Route Set................................................ 260
Creating an Outgoing Route Chain ............................. 262
Configuration Instance.................................. 265
Overview.................................................................... 265
Local Office Data Configuration...................................... 266
Local Exchange Configuration ................................... 267
Physical Configuration .............................................. 267
Capacity Configuration ............................................. 268
Version Loading....................................................... 269
Office Data Configuration.......................................... 269
Resource Attribute Configuration ................................... 270
Adjacent IM-MGW Office Interconnection Data
Configuration ...................................................... 271
Adjacent SCSCF Office Interconnection Data
Configuration ...................................................... 274
Basic Service Data Configuration ................................... 276
Call Data Configuration............................................. 276
SIP Service Data Configuration .................................. 277
Data Synchronization ...................................................
277
MGCF-IM-MGW Interconnection Debugging
Procedure ........................................................... 277
Checking the IM-MGW Office Status ........................... 278
Checking the Physical Connection .............................. 279
Debugging the SCTP ................................................ 279
Debugging the M3UA ............................................... 279
Confirming the Working Status of the IM-MGW ............ 280
H.248/SCTP Problem Location Method ........................ 281
M3UA Problem Location Method................................. 281
Figure............................................................ 283
Table ............................................................. 285
Index ............................................................ 289
Confidential and Proprietary Information of ZTE CORPORATION V

This page is intentionally blank.
VI Confidential and Proprietary Information of ZTE CORPORATION

About This Manual
Purpose At first, thank you for choosing ZXWN wireless core network sys-
tem of ZTE Corporation!
ZXWN system is the 3G mobile communication system developed
based on the UMTS technology. ZXWN system boasts powerful
service processing capability in both CS domain and PS domain,
providing more abundant service contents. Comparing with the
GSM, ZXWN provides telecommunication services in wider range,
capable of transmitting sound, data, graphics and other multi-
media services. In addition, ZXWN has higher speed and
resource uti- lization rate. ZXWN wireless core network system
supports both 2G and 3G subscriber access, and provides various
services related with the 3G core network.
The ZXWN MSCS system is designed for the UMTS system at the
core network control level. It supports the GSM core network,
UMTS protocols in the R99/R4/R5 stage and relevant functions at
the same time, and provides the carriers with an overall solution
to the evolution from the GSM core network to the 3GPP R99 and
then to the 3GPP R5.
The ZXWN MSCS system completes the functions of the Mobile
Switching Center Server and the Visitor Location Register (VLR)
together, and provides the Service Switching Point (SSP)
functions of intelligent calls. The ZXWN MSCS system supports
the MGCF function, and the coexistence of the MGCF and
GMSCS. It also can smoothly upgrade to the MGCF.
This purpose of this manual is to let the carrier master the data
configuration method of MGCF.
Intended This manual is intended for engineers and technicians who have
mastered the communication principle of the mobile network.
Audience
To use this document effectively, users should have a general un-
Prerequisite Skill derstanding of wireless telecommunications technology. Familiar-
and ity with the following is helpful:
Knowledge
� MSCS system and its various components
What Is in This This manual contains the following chapters:
Manual
Chapter Summary
Describes the overall flow of the

Chapter 1, Data Configuration MGCF data configuration and basic
Overview operations of the background
network management (OMM)
system
Describes the physical

Chapter 2, Local Office Data configuration, capacity
Configuration configuration, version
configuration, and office
information configuration of MGCF

Chapter Summary
Chapter 3, Resource Describes MGCF resource planning

Configuration and attribute configuration
Chapter 4, MGCF-IM-MGW Describes the signaling

Interconnection Data interworking configuration between
Configuration MGCF and IM-MGW
Chapter 5, MGCF-SIP Office Describes the signaling

Interconnection Data interworking configuration between
Configuration MGCF and SIP office
Describes the signaling

Chapter 6, MGCF-Other-
interworking configuration between
Exchange Interconnection Data
MGCF and other exchanges at the
Configuration
network side
Describes the basic data

Chapter 7, Basic Service Data
configuration related with the
Configuration
call service
Chapter 8, Configuration Sets MGCF trial office as an

Instance example to describe the data
configuration of the local office and
the peer office
FCC Compliance This device complies with part 15 of the FCC Rules. Operation is
Statement 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 re-
sponsible for compliance could void the user's authority to
operate the equipment.
Conventions ZTE documents employ the following typographical conventions.
Typeface Meaning
Italics References to other Manuals and documents.
“Quotes” Links on screens.
Bold Menus, menu options, function names, input fields,

radio button names, check boxes, drop-down lists,
dialog box names, window names.
CAPS Keys on the keyboard and buttons on screens and

company name.
Note: Provides additional information about a certain

topic.
Checkpoint: Indicates that a particular step needs to

be checked before proceeding further.
Tip: Indicates a suggestion or hint to make things

easier or more productive for the reader.
II Confidential and Proprietary Information of ZTE CORPORATION

About This Manual
Mouse operation conventions are listed as follows:
Typeface Meaning
Click Refers to clicking the primary mouse button (usually the

left mouse button) once.
Double- Refers to quickly clicking the primary mouse button

click (usually the left mouse button) twice.
Right-click Refers to clicking the secondary mouse button (usually

the right mouse button) once.
Confidential and Proprietary Information of ZTE CORPORATION III

IV Confidential and Proprietary Information of ZTE CORPORATION

Declaration of RoHS
Compliance
To minimize the environmental impact and take more

responsibility to the earth we live, this document shall serve as
formal declaration that ZXWN MGCF manufactured by ZTE
CORPORATION are in compliance with the Directive 2002/95/EC
of the European Parlia- ment - RoHS (Restriction of Hazardous
Substances) with respect to the following substances:
� Lead (Pb)
� Mercury (Hg)
� Cadmium (Cd)
� Hexavalent Chromium (Cr (VI))
� PolyBrominated Biphenyls (PBB’s)
� PolyBrominated Diphenyl Ethers (PBDE’s)
…
The ZXWN MGCF manufactured by ZTE CORPORATION meet the

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

II Confidential and Proprietary Information of ZTE CORPORATION

Chapter
1
Data Configuration
Overview
Table of Contents
MGCF Introduction.............................................................. 1
Overall Flow of MGCF Data Configuration ............................... 2
Basic Operations of the OMM System .................................... 4
MGCF Introduction
Networking ZXWN MSCS can serve as a MGCF, composing an IMS system to-
gether with NEs of ZXUN. The MGCF can be combined with the
GMSCS, or separately set. The position of the MGCF in the IMS
network is shown in Figure 1.
FIGURE 1 IMS NETWORKING
Interface When the MSCS serves as a MGCF, the following interfaces are
involved:
� Mg interface: The MGCF is connected with the CSCF through
the Mg interface adopting the SIP protocol.
� Nc: The MGCF is connected with the R4 CS network through
the Nc interface adopting the BICC protocol.
� Ai interface: The MGCF is connected with the PSTN network
through the Ai interface adopting the ISUP protocol.
� Mn interface: The MGCF is connected with the IM-MGW
through the Mn interface adopting the H.248 protocol.

1
Overall Flow of MGCF Data

Configuration
Prerequisites Before the data configuration, it is required to confirm:
� The hardware installation is completed and the cable connec-
tions are normal.
The rack, shelves, and boards are all installed. Cables are all
connected well, and the equipment can be normally powered
on.
� The background network management system is installed.
The IP addresses of the background OMM server and client
are planned. The LAN is constructed, and the foreground OMP
is connected.
The OMM server software and client software are installed,
en- suring that the OMM client can normally log in to the
OMM server. For the installation of the OMM server software
and client software, refer to ZXWN MSCS MSC Server
Software In- stallation.
Configuration The overall flow of the MGCF data configuration is shown in
Flow Figure 2.
2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Data Configuration Overview
FIGURE 2 OVERALL FLOW OF THE MGCF DATA CONFIGURATION
Flow Description The flow description of MGCF data configuration is shown in .
Steps Operations Description
Perform local exchange configuration,

Local office data physical configuration, capacity
1 configuration, version loading, office
configuration
information configuration, and basic SIP
configuration for the local office
MGCF-IM-MGW
Configure the Mn-interface signaling
2 interconnection
interconnection data
data configuration
MGCF-SIP office Configure the SIP signaling

3 interconnection interconnection data with CSCF,
data configuration BGCF, and MGCF office

3
MGCF-other Configure the signaling interconnection

4 exchange data with other offices at the network
interconnection side except the MGW, such as MSCS,
data configuration PSTN, and 2G MSC
5 Basic service data Configure the data related to the SIP

configuration service and the basic call service
Basic Operations of the

OMM System
To perform data configuration, it is required to be familiar with
the basic operations of the OMM system, including the following
operations.
No. Operations
1 Logging in the OMM Client
2 Entering the MML Terminal
3 Operations on the MML Terminal
4 Synchronizing Data
Logging in the OMM Client

Prerequisites Before the operation, it is required to confirm:
� The server and the client of the network management are in-
stalled.
� The communication between the server and the client is nor-
mal.
Context The purpose of logging in to the OMM client is to perform data
configuration and daily maintenance by using the background
OMM software.
Steps 1. On the OMM server, select Start > Programs > ZXWN-CS
(OMM) > Start Server. the NetNumen (TM) Console win-
dow pops up, displaying the start process of the OMM server,
as shown in Figure 3.

FIGURE 3 START PROCESS OF THE OMM SERVER
2. After the OMM server starts successfully, the prompt messages

are displayed in the Detailed Specification area, as shown in
Figure 4.
FIGURE 4 START INFORMATION OF THE OMM SERVER
3. On the server, click Start > Programs > ZXWN-CS (OMM)

> Start Client , and then the Login dialog box appears, as
shown in Figure 5.

5
FIGURE 5 LOGIN WINDOW
4. After entering the login information, click OK. The

parameter description is described in Table 1.
TABLE 1 LOGIN PARAMETER DESCRIPTION
Name Meaning Default

Indicates the name of the
subscriber who logs in the
network server. The default
name is admin (system
administrator). If other
subscriber fails to log in the
network management server
for many times (exceeds the
maximum), the subscriber
will be locked automatically.
This subscriber only could be
unlocked by the administrator
User name admin
or when the locking duration
expires. The login operation
that exceeds the maximum
should be reported to the
network management, so that
the network management
could
know the maintenance status of
the equipment in order to
avoid the login of the
unauthorized subscriber and
other operation errors. The
maximum login limitation times
in this system is 3
It indicates the password that is
used to log in the OMM server.
Password The password of the new Null
installed network management
is null

Name Meaning Default
Indicates the IP address of the

network management server. If
the server and the client are not
Server installed in the same computer,
it is required to enter the real 127.0.0.1
address
IP address of the server. or
else, you can enter the actual
IP address or adopt the default
IP address
END OF STEPS
Result After the login is successful, the main window of the OMM system
pops up, as shown in Figure 6.
FIGURE 6 NETNUMEN M30 MSCS/MGW OMM SYSTEM WINDOW
Entering the MML Terminal

Prerequisites To enter the MML terminal, the following condition must be met:
The user has logged in the OMM Server successfully.
Context This topic describes how to enter the MML terminal.
1. On the OMM client, select Views > MML Terminal to enter
Steps
the MML Terminal window. The left shows the configuration
tree, and the right shows the attribute pane, as shown in
Figure 7.

7
FIGURE 7 MML TERMINAL WINDOW
END OF STEPS
Result Enters the MML Terminal successfully.
Operations on the MML Terminal

Command The main operation of the data configuration is to type the com-
Terminal mand in the MML Terminal window, as shown in Figure 8.
Window

FIGURE 8 MML TERMINAL WINDOW
On the left pane of the MML Terminal window, the root node
represents the OMM server node, which is the real root node. The
nodes under the root node represent the specific NEs to be con-
figured.
Command Typing The command is typed in the input box at the lower right corner
of the MML Terminal window. For example, type in command
SET:NEID=11;, as shown in Figure 8.
In general, a command is associated with a network element (ex-
cept the command used to configure an exchange). For example,
create a shelf for MGCF11(the ID can be queried with the com-
mand SHOW NE;). The following two methods can be used to
perform the conjunction:
� Type the command SET: NEID=11; and click F5 to execute
the command (the method is widely adopted in this
document).
� Select the network element of which the exchange ID is 11
from the left configuration system tree, such as MGCF11.
Command This part describes the procedure of command line operation.
Click
Execution F5 to execute the command after it is typed.
After the command is executed, the Command Execute Result
pane shows the result or the information read by this command,
as shown in Figure 9.

9
FIGURE 9 COMMAND EXECUTION OPERATIONS
Synchronizing Data
� The MML Terminal window is opened.
� Some data configurations or all data configuration are com-
pleted.
Context When configuring the data on the OMM, such as creating data,
modifying data or deleting data, the data will be saved to the
OMM Server in the form of data list after executing the F5
button. At this time, the foreground data are not modified.
The data synchronization is to synchronize the data on the OMM
Server to the foreground.
The data synchronization operation could be done after finishing
each step or after finishing configuring all the data.
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 MGCF exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Data transfer includes transferring data by using the “Admin”
user and transferring data by using the current login user.
� Synchronize Admin data. The command is SYNA.
Tip:
This command is used by Admin users to synchronize all
table data, no matter whether the tables are locked by
other users.
Table 2 describes the parameters in this command.

TABLE 2 PARAMETERS IN THE SYNA COMMAND
Name Meaning Instructions
USER- It consists of 0~50

User name characters and the default
NAME value is admin
It includes
– CHG (Single User
Changed Tables)
STYPE Sync type
– ALL (All Tables)
– ALLCHG (All Changed
Tables)
It indicates the module ID in

MODULES Module list decimal. If there are many
module IDs, use the symbol
& to connect them.
It is an optional parameter
Response timeout and the default value is
TIMEOUT 600. Adjust the response
(100ms)
timeout according to the
actual requirement.
SAVE Save when It is an optional parameter

completed and the default value is YES
TOSLAVE Sync to slave when It is an optional parameter

completed and the default value is YES
� Synchronize the data of currently login user. The

command is SYN.
Tip:
This command is used to synchronize the table data con-
figured by a login user. The table data not configured by
the login user can not be synchronized to the foreground.
Table 3 describes the parameters in this command.
TABLE 3 PARAMETERS IN THE SYN COMMAND
It indicates the module

ID in decimal. If there
MODULES Module list are many module IDs,
use the symbol & to
connect them.
It is an optional
Response timeout parameter and the
TIMEOUT
(100ms) default value is 600.
Adjust the response

11

timeout according to
the actual requirement.
It is an optional
SAVE Save when completed parameter and the
default value is YES
It is an optional
TOSLAVE Sync to slave when
parameter and the
completed
default value is YES
� Example: To synchronize all the tables with

admin user.
The command is as follows:
SYNA:STYPE=ALL,TIMEOUT=600,SAVE=YES,TOSLAV
E=YES;
� Example: To synchronize the data of the current user, the
command is as follows:
SYN:TIMEOUT=600,SAVE=YES,TOSLAVE=YES;
END OF STEPS
Result After the command is executed, the progress of table transferring

is shown on the Message Report pane.

Chapter
2
Local Office Data
Configuration
Table of Contents
Overview.......................................................................... 14
Local Exchange Configuration .............................................. 15
Physical Configuration ........................................................ 18
Capacity Configuration ....................................................... 34
Version Loading................................................................. 39
Creating MGCF Tones in Batches.......................................... 65
Office Information Configuration .......................................... 67

13
Overview
Configuration Figure 10 shows the flow of the local office data configuration.
Flow
FIGURE 10 LOCAL OFFICE DATA CONFIGURATION FLOW
Flow Description The local office data configuration contains the following steps.
Steps Operations Procedures
Local exchange Create MGCF exchange and set the

1 province and city information of the local
Configuration
office
Create foreground-corresponded racks,

Physical shelves, units, modules, and their
2
configuration attributes on the background OMM
system

Chapter 2 Local Office Data Configuration
3 Capacity Set the MP table capacity

configuration
Load the version files to the foreground,

4 Version loading which are required for normal running of
different foreground boards
5 Create MGCF
Create a batch MGCF tones
tones in batches
6 Office information Configure the local office signaling point,

configuration exchange type and country code
Local
Exchange
Configuration
Overview
Introduction Local exchange configuration is to define the information of the
local exchange on the OMM system such as its type. It is the first
data configuration in deployment.
Contents The exchange configuration contains the following steps.
Steps Operations Instructions Commands
Create the NE
Creating an corresponded by
1 the exchange on the ADD NE
exchange
background OMM
system
Configure the
provincial and
city codes of the
Setting province and exchange, thus
2 city information of to display the SET PCINFO
the bureau area information
in the Element
Management
System (EMS)
Creating an Exchange
Prerequisites The MML Terminal window is opened.
Context Perform this procedure to create the NE corresponded by the ex-
change on the background OMM system.
Steps 1. Create an MGCF exchange with the ADD NE command.

15
Table 4 describes the main parameters in the ADD NE com-

mand.
TABLE 4 PARAMETERS IN THE ADD NE COMMAND
Parameter
Parameter Description Instruction
Name
It is a mandatory
The unique ID of an parameter. It ranges
ID from 11 to 30. It cannot
exchange
be modified once it is
created.
It is a mandatory
TYPE Type of the exchange to
parameter. Select
be created
MSCS.
It is an optional
parameter. Select NONE
MESUBTYPE NE sub-type for an end office, and
TMSC1 or TMSC2 for a
tandem office.
It is an optional
Exchange name parameter. With a
NAME
customized by user length ranging from 0 to
50 characters.
It is an optional
VENDOR Equipment manufacturer parameter. Type ZTE, by
default.
It is an optional
STATE State defined by the user parameter. Select 0,
by default.
It is an optional
parameter. Type the
Location where the location information
LOC of the equipment. It
equipment is located
is recommended to
describe it with
letters or
digits.
Example: Create an MGCF office with the following require-

ments.
� Office ID: 11
� TYPE: MSCS
� Alias: MGCF11
� Other parameter: default.
The specific command is as follows.
ADD
NE:ID=11,TYPE=MSCS,MESUBTYPE=NONE,NAME
="MGCF11",VENDOR="ZTE",STATE=0;
END OF STEPS
Result After the command is executed successfully, the MGCF11 node is
created under the root node in the OMM client interface. Mean-

while, the rack is generated, with the rack No. as 1 and the alias
as rack1.
Setting Province and City Information

of the Bureau
� The MGCF exchange is added.
Context Perform this procedure to configure the provincial and city codes
of the exchange, thus to display the area information in the
Element Management System (EMS).
system tree.
SET:NEID=11;
2. Set the province and city codes of the exchange. The
command is SET PCINFO.
Table 5 describes the main parameters in the SET PCINFO
command.
TABLE 5 PARAMETERS IN THE SET PCINFO COMMAND
Parame- Parameter
Instruction
ter Name Description
It is a mandatory parameter. For

PROVINCE Provincial code displaying area information of the
exchange in the EMS.
CITY City code It is a mandatory parameter. For

setting the city code.
Example: Set the province and city codes of the exchange.

The exchange is located in Nanjing city of Jiangsu province.
SET PCINFO:PROVINCE="320000",CITY="320101";
END OF STEPS
Result After the command is executed, the SUCCESS result is shown in

the Execute Result column of the History Command pane.

17
Physical Configuration
Overview
Introduction This section describes the physical configuration .
Flow Figure 11 shows the physical configuration flow.
diagram
FIGURE 11 PHYSICAL CONFIGURATION FLOW
Flow description The physical configuration contains the following steps.

Steps Operations Instructions Command
Create a logic rack

1 Creating a Rack on the ADD RACK
background OMM
system
Create a logic shelf
2 Creating a Shelf on the background ADD SHELF
OMM system
3 Creating the UIM Create the UIM ADD UNIT

Unit board
When MSCS has

several modules,
4 Creating a Module it is required to ADD MODULE
create SMP board
for BCTC shelf
Create other logic

Creating Other boards in the BCTC
5 shelf of MSCS ADD UNIT
Units
exchange, except
for UIM unit
Creating Connect the SMP

6 Background Server with the billing ADD SVRINF
Node server
Creating a Rack
� The exchange has been created.
Context Perform this procedure to create a logic rack on the background
OMM system. It corresponds to the rack on the foreground. Since
the system automatically creates rack 1 during the exchange cre-
ation, you need not to create it again. But you need to create
other racks manually here.
system tree.
SET:NEID=11;
2. Create a rack. The command is ADD RACK.
Table 6 describes the parameters in the ADD RACK
command.

19
TABLE 6 PARAMETERS IN THE ADD RACK COMMAND
Parameter Parameter
Instructions
Name Description
It is a mandatory
parameter within 1~15.
Rack 1 is generated
RACK Rack No. during creating the
exchange.
Other racks need to be
created by manual. The
rack No. begins from 2
Rack type, includes
� 3G_STAND-
It is an optional
ARD_RACK: ZTE
RACK TYPE parameter. Select it
standard rack
according to the actual
� 3G_INTEGRA- rack type.
TION_RACK: ZTE
integration rack
It is an optional
NAME Alias parameter and consists
of 0~50 strings
Example: Create a ZTE standard rack whose rack No. is 2.

The command is as follows.
ADD RACK:RACK=2,RACKTYPE=3G_STANDARD_RACK,NA
ME="RACK2";
Example: Create a ZTE integration rack whose rack No. is 3.
ADD
RACK:RACK=3,RACKTYPE=3G_INTEGRATION_RAC
K,NAME="RACK2";
END OF STEPS
Result After the command is executed successfully, the rack is created
under MGCF11 exchange, and is shown on the Daily
Maintenance
> Rackchart Management tab.
Creating a Shelf
� You know the ID of the exchange to be configured.
� The rack is created under the corresponding exchange.
Context Perform this procedure to create a logic shelf on the background
OMM system. It corresponds to the shelf on the foreground.
MGCF only adopts BCTC shelf. One rack can be configured with
up to four BCTC shelves.

Note:
Shelf 2 of rack 1 must be created first, and then other shelves
are created.

system tree.
SET:NEID=11;
2. Create a shelf. The command is ADD SHELF.
Table 7 describes the parameters in the ADD SHELF
command.
TABLE 7 PARAMETERS IN THE ADD SHELF COMMAND

RACK Rack No. It is a mandatory parameter that is within

1~15.
SHELF Shelf No. It is a mandatory parameter, ranging

from 1 to 4. Shelf 2 must be configured
first.
It is a mandatory parameter. MGCF
TYPE Shelf type can only be configured with BCTC shelf
(control shelf).
NAME It is an optional parameter, with a length

Alias
ranging from 0 to 50 characters.
Example: Create a BCTC shelf in rack 1, with the shelf

number as 2 and the name as “BCTC”. The specific command
is as follows.
ADD SHELF:RACK=1,SHELF=2,TYPE=BCTC,NAME="BCT
C";
END OF STEPS
Result After BCTC shelf is created successfully, the OMP module and the
RPU module are created at the same time. The numbers of these
two modules are 1 and 2. Slots 11 and 12 of the rack display the
OMP board.
Creating the UIM Unit

� The BCTC shelf is created in the corresponding rack.

21
Context Creating the UIM unit is to create the UIM board. In general, UIM
board adopts 1+1 backup mode. It is fixedly inserted into slots 9
and 10 in the BCTC shelf.
system tree.
SET:NEID=11;
2. Create a UIM Unit. The command is ADD UNIT.
Note:
You must first create the UIMC unit in shelf 2 of rack 1, and
then create the UIMC units in other BCTC shelves.
Table 8 describes the parameters in the ADD UNIT

command.
TABLE 8 PARAMETERS IN THE ADD UNIT COMMAND

Parameter Parameter
Instruction
Name Description
It is a mandatory parameter and

the format is RACK-SHELF-
SLOT.
� The rack No. is within 1~15
and the default value is 1.
This parameter is defined by
LOC Unit location the ADD RACK command.
� The shelf No. is within 1~4.
the ADD SHELF command.
� The slot represents the slot
number. In BCTC shelf, the
UIM slot number must be 9
and 10.
MODULE Module No. It is a mandatory parameter.

Select 1.
UNIT Unit No. It is an optional parameter,

ranging from 1 to 2000.
It is a mandatory parameter.
Select it according to the
CPU type of the UIMC board,
TYPE Unit type including UIM2_GCS_755
and UIM2_GCS_8260.
UIM2_GCS_755 sub-card
is mostly used at present.
It is a mandatory parameter
BKMODE Backup mode and the backup mode is
ONEPLUSONE.
NAME Alias It is an optional parameter and

consists of 0~50 characters.

Example: Add the UIM units with the following requirements.

� Rack No.: 1
� Shelf No.: 2
� Slot No.: 9 and 10
� Unit type: UIM2_GCS_755
� Backup mode: 1+1 backup
ADD
UNIT:LOC="1"-"2"-"9",MODULE=1,UNIT=921,TYPE
=UIM2_GCS_755,BKMODE=ONEPLUSONE,CLK1=16383,CL
K2=16383;
Tip:
After the 1+1 backup mode is selected for the UIM board lo-
cated in slot 9, the system will automatically create the UIM
board located in slot 10. In addition, the unit numbers of left
and right slots are consistent.
END OF STEPS
Result After the UIM unit is created successfully, the active and standby
UIM boards are shown in the corresponding slots of the rack
chart.
Creating a Module
� The UIM unit is created under the exchange.
Context When MGCF has several modules, it is required to create SMP
board for BCTC shelf. When BCTC has more shelves, SMP and
CMP modules should be allocated to each BCTC shelf equally.
system tree.
SET:NEID=11;
2. Create a module. The command is ADD MODULE.
Table 9 describes the parameters in the ADD MODULE com-
mand.

23
TABLE 9 PARAMETERS IN THE ADD MODULE COMMAND
It is a mandatory parameter. Its

format is RACK-SHELF-SLOT. The
LOC Location range of RACK is within 1~15 and
the default value is 1. The shelf
No. is within 1~4 and the slot No.
is within 1~17.
It is a mandatory parameter,
MODULE Module No. ranging from 3 to 127. A new
module is numbered from 3.
� Select SMP for a signaling
module.
FUNC1 Module 1 type � Select MSCBASECMP for a
service module.
� When MSCS serves as MGCF,
select SIP type.
It is an optional parameter. If it is
FUNC2 Module 2 type left blank, its configuration is the
same as that of FUNC1.
It is an optional parameter. Two

CPUTYPE CPU type options available, X86 and
CENTRINO. Select according to
the actual board type.
It is an optional parameter. In
general, select ONEPLUSONE
(one plus one backup) for a service
BKMODE Backup mode module, and ONEPLUSONE (one
plus one backup) or No (Without
backup) for a signaling module,
which is determined by the actual
configuration.
NAME1 Module 1 user It is an optional parameter and

alias consists of 0~50 characters.
NAME2 Module 2 user It is an optional parameter and

alias consists of 0~50 characters.
Example: Create SMP modules with the following require-

ments.
� Location: Slots 5 and 6 in BCTC shelf 2 of rack 1
� Module number: 3 and 4
� Module type: SMP
� CPU type: CENTRINO
� Module 1 name: SMP3
� Module 2 name: SMP4.


ADD
MODULE:LOC="1"-"2"-"5",MODULE="3"&"4",FUNC1
="SMP",FUNC2="SMP",CPUTYPE=CENTRINO,BKMODE=ON
EPLUSONE,NAME="SMP3",NAME2="SMP4";
Example: Create CMP modules with the following require-
ments.
� Location: Slots 7 and 8 in BCTC shelf 2 of rack 1
� Module number: 5 and 6
� Module type: CMP
� CPU type: CENTRINO
� Module 1 name: CMP5
� Module 2 name: CMP6.
ADD MODULE:LOC="1"-"2"-"7",MODULE="5"&"6",FUNC1
="MSCBASECMP"&"SIP",FUNC2="MSCBASECMP"&"SIP",CP
UTYPE=CENTRINO,BKMODE=ONEPLUSONE,NAME="CMP5
",NAME2="CMP6";
END OF STEPS
Result After the SMP/CMP module is created successfully, its correspond-
ing slot in the rack chart displays the SMP board.
Creating other Units

� The UIM unit is created.
Context Perform this procedure to create other logic boards in the BCTC
shelf of MGCF exchange, except for UIM unit.
Table 10 lists the main boards in MGCF.
TABLE 10 MGCF BOARD TYPES
Board Board Type Backup Mode
SIPI2_IPSEC
No backup or 1+1
SIPI SIPI2_NC active/standby backup
SIPI_NC
SPB2_8260_8260C4
SPB No backup
SPB2_8250_85XXC2

25
Board Board Type Backup Mode
USI2_NC
USI 1+1 active/standby backup
USI_NC
CHUB CHUB 1+1 active/standby backup
CLKG CLKG 1+1 active/standby backup

system tree.
SET:NEID=11;
2. Create other units. The command is ADD UNIT.
No. Operations
1 Creating a CHUB unit
2 Creating a CLKG unit
3 Creating an SIPI unit
4 Creating a USI Unit
5 Creating an SPB unit
END OF STEPS
Creating a CHUB Unit

Context Perform this procedure to create the CHUB logic board
corresponding to that in the foreground BCTC shelf of MGCF
Steps
exchange.
1. If no exchange is specified, execute command SET on the
system tree.
SET:NEID=11;
2. Create a CHUB unit. The command is ADD UNIT.
Table 11 describes the main parameters in the command.

TABLE 11 PARAMETER IN THE ADD UNIT COMMAND
Parameter Parameter
Instruction
Name Description
It is a mandatory parameter, with

a format of RACK-SHELF-SLOT
� RACK represents the rack
number, ranging from 1 to 15.
In general, it is configured as
Location of 1.
LOC the unit in the
system � SHELF represents the shelf
� SLOT represents the slot
number. CHUB boards are
fixedly inserted into slots 15
and 16 in shelf 2 of rack 1.
Module It is a mandatory parameter.

MODULE number of the Select 1
unit
UNIT Unit number It is an optional parameter

of the ranging from 1 to 2000.
board
TYPE Logic unit type

Select CHUB
of the board
Backup mode Select ONEPLUSONE 1+1

BKMODE
of the unit active/standby backup
Example: Create CHUB boards with the following require-

ments.
Location: Slots 15 and 16 of shelf 2 in rack 1
Unit type: CHUB
Backup mode: 1+1 active/standby backup
Other parameters: default.
ADD
UNIT:LOC="1"-"2"-"15",MODULE=1,UNIT=1521,TY
PE=CHUB,BKMODE=ONEPLUSONE,CLK1=16383,CLK2=16
383;
END OF STEPS
Result After the unit is created successfully, corresponding slots of the

rack chart display these CHUB boards.
Creating a CLKG Unit


27
Context Perform this procedure to create the CLKG logic board

corresponding to that in the foreground BCTC shelf of MGCF
Steps
exchange.
system tree.
SET:NEID=11;
2. Create a CLKG unit. The command is ADD UNIT.
Table 12 describes the parameters in the command.
Parame- Parameter
Instruction
LOC Unit location It is a mandatory parameter and

the format is RACK-SHELF-SLOT.
and the default value is 1. This
parameter is defined by the
ADD RACK command.
� The slot No. is within 1~17.
MODULE Module No. It is a mandatory parameter.

Select the OMP module belonging
to CLKG.
UNIT Unit No. It is an optional parameter, ranging

from 1 to 2000.
TYPE Unit type It is a mandatory parameter. For

CLKG, select CLKG
BKMODE Backup mode It is a mandatory parameter

and the backup mode is
ONEPLUSONE.
NAME Alias It is an optional parameter and

consists of 0~50 characters.
Example: Create CLKG boards with the following require-

ments.
� Location: Slots 13 and 14 of shelf 2 in rack 1
� Unit type: CLKG
� Backup mode: 1+1 active/standby backup
� Other parameters: default.
ADD UNIT:LOC="1"-"2"-"13",MODULE=1,UNIT=1321,TY
PE=CLKG,BKMODE=ONEPLUSONE,CLK1=16383,CLK2=163
83;

3. After creating the CLKG unit, configure the CLKG board param-
eters with the SET CLKETHR command as required.
Configure its parameters based on the clock source actually
provided.
Example: Configure clockbase setting of the CLKG board to be
allowed, and the clock reference is 8KBase. The command is
as follows.
SET CLKETHR:CLKBASE=ALLOWED,BASETYPE=8KBase,B
ASEINFO="8KBase";
END OF STEPS

rack chart display these CLKG boards.
Creating an SIPI Unit

Context Perform this procedure to create the SIPI logic board correspond-
ing to that in the foreground BCTC shelf of MGCF exchange.
� SIPI boards work in load-sharing mode
In load-sharing mode, two SIG-IPI boards both serve as ac-
tive board, and maintain each own associations. The relation-
ship between associations is load-sharing, which means that
the service transmission is shared evenly by the associations
of these two SIG_IPI boards. When the association on one of
these two interface boards is interrupted, all the service data
will be moved to the association of another interface board
that works normally. In this way, the inter-office
communication will not be interrupted for this cause. This
project is recommended for office commissioning .
� SIPI boards work in active/standby mode .
Two SIG_IPI boards serve as mutual backup. In normal con-
ditions, associations are only processed on active board, and
backed up only on standby board. The associations on the ac-
tive board are disconnected when the active board is
abnormal or extracted. At this moment, the standby board
quickly re- places the active board to connect the
associations, thus to restore the normal communication
Steps
between offices.
system tree.
SET:NEID=11;
2. Create an SIPI unit. The command is ADD UNIT.
Table 13 describes the main parameters in the command.

29
Parame- Parameter
Instruction

Location of In general, it is configured as
LOC the unit in the 1
system
� SHELF represents the shelf
number, ranging from 1 to 4
number
MODULE Module number It is a mandatory parameter.

of the unit Select 1
UNIT Unit number of It is an optional parameter.

the board Ranging from 1 to 2000.

Select SIPI_NC
of the board
It supports the NO (Without

Backup mode of backup) and ONEPLUSONE (One
BKMODE plus one backup) modes. Select it
the unit
according to the actual networking
mode
Example: Add SIPI boards with the following requirements.

� Unit type: SIPI_NC
ADD
=SIPI_NC,BKMODE=ONEPLUSONE,CLK1=16383,CLK2=16
383;
END OF STEPS
rack chart display these SIPI boards.
Creating a USI Unit


Context Perform this procedure to create the USI logic board

corresponding to that in the foreground BCTC shelf of MGCF
Steps
exchange.
system tree.
SET:NEID=11;
2. Create a USI unit. The command is ADD UNIT.
Table 14 describes the main parameters in the ADD UNIT
command.
Parameter Parameter Instruction

Name Description

Location of In general, it is configured as
LOC the unit in the 1
system
� SHELF represents the shelf
number, ranging from 1 to 4
number


the board Ranging from 1 to 2000

Select USI_NC
of the board
BKMODE Backup mode Select ONEPLUSONE

of the unit
Example: Create SIPI boards with the following requirements.

� Unit type: USI_NC
ADD
=USI_NC,BKMODE=ONEPLUSONE,CLK1=16383,CLK2=163
83;
END OF STEPS

31

rack chart display these USI boards.
Creating an SPB Unit

Context Perform this procedure to create the SPB logic board correspond-
ing to that in the foreground BCTC shelf of MGCF exchange. SPB
board is created only when the narrowband No.7 signaling is used
between MGCF and other offices.
system tree.
SET:NEID=11;
2. Create an SPB unit. The command is ADD UNIT.
Table 15 describes the main parameters in the ADD UNIT
command.
Parameter Parameter
Instruction
Name Description
It is a mandatory parameter and

the format is RACK-SHELF-
SLOT.
and the default value is 1.
Location of This parameter is defined by
LOC the unit in the the ADD RACK command.
system
� The slot No. is within 1~17.


the boar Ranging from 1 to 2000.
Logic unit type Select it according to the CPU

TYPE type of this SPB board, for
of the board
example, SPB2_8260_8260C4
BKMODE Backup mode Select No backup

of the unit

Example: Create an SPB board with the following require-

ments.
� Location: Slot 7 of shelf 2 in rack 1
� Unit type: SPB_8260_8260C4
� Backup mode: No backup
� Other parameters:
default. The command is as
follows.
ADD
UNIT:LOC="1"-"2"-"7",MODU
LE=1,UNIT=721,TYPE
=SPB2_8260_8260C4,BKMODE=NO,CLK1=16383,CLK2=16
383;
Example: Create an SPB board with the following require-
ments.
� Location: Slot 8 of shelf 2 in rack 1
� Unit type: SPB_8260_8260C4
� Backup mode: No backup
default. The command is as
follows.
ADD
Result After the unit is created successfully, corresponding slot of the
UNIT:LOC="1"-"2"-"8",MODU
rackLE=1,UNIT=821,TYPE
chart display the SPB board.
383;
Creating Background Server Node
END OF STEPS

� The corresponding MP module is created.
Context Perform this procedure to connect the SMP with the billing server.
All SMP units should be mapped to the billing server.
system tree.
SET:NEID=11;
2. Create the background server node. The command is ADD
SVRINF.
Table 16 describes the main parameters in the ADD SVRINF
command.

33
TABLE 16 PARAMETER IN THE ADD SVRINF COMMAND
Parameter Parameter Descrip- Instruction

Name tion
It is a mandatory
Module number of parameter, ranging from
MODULE 1 to 127, including all
foreground MP
the modules except for
module 2
It is an optional
CGMODULE Module number of
parameter, ranging
billing server
from 130 to 135
Example: Create the billing server node 130 corresponding to

the foreground SMP module 3. The specific command is as
follows.
ADD SVRINF:MODULE=3,CGMODULE=130;
END OF STEPS

Capacity Configuration
Overview
Table 17 shows the capacity configuration flow.
TABLE 17 CAPACITY CONFIGURATION
Steps Operation Instruction Command
Configure the
Configuring the
capacity for each SET MSCSCAPAC
1 MGCF office
table in the MP ITY
capacity
module
Normally select the

Configuring service
2 default value for SET DATASIZE
data area
all parameters
Configuring the MGCF Office

Capacity
Prerequisites To perform this operation, the following conditions must be met:

� The ID of the exchange to be configured is known.

� The physical configuration is completed.
Context This topic describes how to configure the capacity for each table
in the MP module. MGCF capacity is configured according to the
actual capacity of the equipment. In general, these parameters
adopt their default value, except in special cases.
system tree.
SET:NEID=11;
2. Configure the MGCF office capacity with the command SET
MSCSCAPACITY.
The parameter description of the command SET MSCSCAPAC
ITY is shown in Table 18.
TABLE 18 OFFICE CAPACITY CONFIGURATION PARAMETERS
Name Meaning Range Default
GCI Capacity Of GCI Config 1~12000 1280

Table
LAI Capacity Of LAI Config 1~1000 64

Table
AOC- Capacity Of Tariff Config 1~1000 128

FEE Table
IROAM Capacity Of IMSI Analy- 1~3000 1000

sis Config Table
PCM Capacity Of PCM Table 2000~20000 2048
BSC Capacity Of 1~128 32

BSC/RNC Config Table
MASK Capacity Of Black/ White 1~80000 2048

List Number
NUM- Capacity Of Number Pre- 1~20000 1000

LEN analysis
CALL Capacity Of CFG Rela- 1~1024 512

- tionship Table
DATA
CTRL- Capacity Of Access Net- 1~128 64
UNT work Unit
SIPTRA Capacity Of SIP Process 2000~20000 6000

Data
SIPSTA Capacity Of SIP Function 1000~8000 3000

Adaptor Data

35
Name Meaning Range Default
SIPRES Capacity Of SIP Call Re- 1000~8000 2500

sources
HRBT- Capacity Of Home Ring 1~80000 1

MS Back Tone
SSP Capacity Of 1~60000 1024

Special Service Phone
Group
USER Capacity Of Users 1~80000 4000

Under- control
TID- Capacity Of TID And 1~1024 512

TRUNK Trunk Link
MDNAL Capacity Of Mobile Num- 1~65535 8192

Analysis Config
DNAL Capacity Of Num-Analy- 1~100000 8192

sis Config
MPDFT Capacity Of Default Per- 2000~10000 2000

Def Timer(MP)
MPDEF Capacity Of Defined Pre- 2000~15000 2000

Def Timer(MP)
PPDFT Capacity Of Default Pre- 2000~10000 2000

Def Timer(PP)
PPDEF Capacity Of Defined Pre- 2000~10000 2000

Def Timer(PP)
LIM- Capacity Of Limit Cheat- 0~60000 0

ITMS ing Subscriber
DNHO- Capacity Of 1~400000 150000

ME Number Home
LINK Capacity Of Link 1920~5000 1920
GT Capacity Of GT 20001~50000 20000
SPC Capacity Of SPC 1~2000 2000
VMSC Capacity Of VMSC Table 16~256 16
SAI Capacity Of SAI Config 1~12000 1280

Table
MGW Capacity Of MGW 1~128 32
ANA-
Capacity Of Announce- 1~65535 1024
NACA-
ment User Analyzer
PACITY
For example, configure the MGCF office capacity. Select the

default value for all parameters. The command is as follows:

SET MSCSCAPACITY;
END OF STEPS

Postrequisite 1. Configure the OMP startup parameters through a serial port.
2. Synchronize the capacity planning table to the foreground.
3. Restart OMP and the realted MP boards.
4. Synchronize all the tables to the foreground again.
Note:
It is required to synchronize the office capacity table to the fore-
ground twice. After the first synchronization, wait 5~10 minutes
for the OMP to complete the disk saving, and then restart the
OMP. When the OMP starts successfully, it is required to
synchronize the capacity tables to the OMP again. After the first
synchronization, only the space of the capacity table on the OMP
is established, but the table contents are not added. After the
second synchronization, the table contents are synchronization.
Configuring Service Data Area

� The physical configuration is completed.
Context Perform this procedure to configure the service data area. Gener-
ally, it adopts the default value, except in special cases.
system tree.
SET:NEID=11;
2. Configure the service data area. The command is SET DATA
SIZE.
Table 19 shows the description of main parameters in the SET
DATASIZE command.

37
TABLE 19 PARAMETERS IN THE SET DATASIZE COMMAND
Parameter Parameter
Instruction
Name Description
One-MSC
multi-MGW call
model, including Select QMALLOW when a
AMONLY(Associ- call needs three MGWs under
CMODEL ated Mode the MSCS to provide
Only) and bearers. Otherwise, select
QAMAL- AMONLY
LOW(Quasi-as-
sociated Mode
Allowed)
Configure it as 10 when
the MSCS is associated
with one MGW to conform
a network, or in a full IP
Number of BCBM networking mode.
BCBMNUM Configure
data areas
it as 3600 when the end
office adopts the multi-call
model. Configure it as 12400
when the tandem office and
gateway office adopt the
multi-call model.
Type an integer ranging
from 1 to 10000, which
Number of is associated with
DSTCDNUM
destination codes the destination-code
traffic-statistics in the
performance statistics.
Maximum number
Integer numbers ranging
CTSTNUM of mixed flow of
from 100 to 11000
traffic
CTSTINDEXS CTST index size Integer numbers ranging
IZE (KB) from 16 to 4096
VMSCNO7 Number of Integer numbers ranging

NUM VMSC/OMP module from 2000 to 10000
NO7 call data area
Number of CMP
Integer numbers ranging
CMPNO7NUM module NO7 call from 10000 to 30000
data area
Example: Configure a service data area. The MGCF is associ-

ated with an MGW. The number of destination codes is 4096.
Other parameters adopt the default value. The specific com-
mand is as follows.
SET DATASIZE:CMODEL=AMONLY,BCBMNUM=10,DSTCD
NUM=4096;
END OF STEPS


Version Loading
All physical boards need the software to support the running. If
the same physical board is loaded with different running
software, it will be with different functions. At first, the physical
board is not loaded with the software supporting the running, so
it is required to load it by manual.
The version files of the OMP module are obtained from the OMC
server via FTP. For the version files of other boards (including
RPU), they are obtained from OMP during the restart. The steps
to load the version files are as follows:
� Load the version files that are needed by the board from the
configured version file directory to the version database of the
OMC server.
� Add the version files in the version database into the fore-
ground OMP.
� Add the corresponding records into the database table related
to the version files, so the other boards could obtain the
version files from OMP according to these records.
� During restarting the board, compare the existing version files
with the old version files on OMP and check whether they are
consistent. If they are the same, adopt the old version fiels;
otherwise, download the new version files from OMP.

39
Overview
Configuration Figure 12 shows the loading flow of a board version files.
Flow
FIGURE 12 FLOW OF LOADING VERSION FILES
Flow Description
Steps Operations Instructions
Creating the
1 Make sure the version number and path of
version file
the version files to be loaded.
directory
Generate the ompcfgX.ini (X is the ID of

Creating OMP corresponded exchange) boot file on the
2
boot files OMM server. OMP board loads its version
files according to this file.

Steps Operations Instructions
Configuring the Configures some parameter information

3 OMP startup
for OMP board to communicate with OMM
parameters via server during startup.
serial port
After OMP board is started, the OMP

Configuring OMP global data should be configured to make
4 sure that the foreground/background
global data
IP addresses are in the same network
section.
After the data configuration is completed,

Synchronizing the configuration data stored on the OMM
5 server are synchronized to the foreground
all tables
for foreground NEs to get the configuration
data from the OMM server.
6 Loading version Manually loads the version files required

files for board running.
Creating Version File Directory

� The version file has been prepared.
� The physical configuration and the capacity configuration are
completed.
Context Perform this procedure to create the version ID and version path
of the version file to be loaded.
Steps 1. On the NetNumen M30 window, select menus Views > Pro-
fessional Maintenance to enter the Professional Mainte-
nance window.
2. In the left pane, double-click the exchange node in the Pro-
fessional Maintenance tree. Select Version Management
> Version Mainenance to show the Version Maintenance
tab in the right pane, as shown inFigure 13.

41
FIGURE 13 VERSION LOADING
3. On the Load Version tab, Click the button on the sub-tool-

bar to pop up the Config Version Path tab, as shown in
Figure 14.
FIGURE 14 CONFIGURING VERSION PATH
4. Right-click the list on the Config Version Path tab, and select
Create from the short-cut menu. A new blank entry is
created on the Config Version Path tab, as show in Figure
15.

FIGURE 15 ADDING NEW BLANK ENTRY
5. Double-click the Version Name on the tab, and type the ver-
sion name (the version name format is V0.00.00.B0, in which,
0 indicates digital and B indicates character), which should be
consistent with the version name of the version file, as show
in Figure 16.
FIGURE 16 CONFIGURING VERSION NAME

43
6. On the Config Version Path tab, double-click the blank entry

in the File Path column. The button appears.
7. Click the button and then the OPEN dialog will pop up. Select
the save path for the version file, the version file path
appears in the File Path entry, as shown in Figure 17.
FIGURE 17 VERSION FILE PATH
8. After setting the path, it is required to save the setting. On the

Config Version Path tab, right click any item and then
select the Save button. After the successful saving, the Save
Successfully dialog appears. Click the OK button.
END OF STEPS
Result The correct Version Name and File Path appears on the the
Ver- sion Maintenance tab.
Creating OMP Boot Files

� Version file directory is configured.
Context To create an OMP boot file is to generate an ompcfgX.ini boot file
on the OMM server, of which the “X” is the number of the corre-
sponding exchange. This file contains the file names of CPU and
FPGA required for normal running of OMP module.
The CPU files and the FPGA files required by OMP are listed in
Table 20.

TABLE 20 VERSION DESCRIPTION OF OMP BOOT FILE
OMP CPU
Version Type Version File Name
Type
CPU MSCS_MPX86_MP_X86_CS_Z_T.
BIN
MPX86
FPGA MPX86_05_040202_FPGA_105
. RBF
CPU MSCS_MPX86_2_MP_P4_CS_Z_
T.BIN
CENTRINO
FPGA MPX862_04_040704_FPGA_109
. RBF
Steps 1. On the NetNumen M30 window, select menus Views > Pro-
fessional Maintenance to enter the Professional Mainte-
nance window.
> Version Mainenance to show the Version Mainenance
tab in the right pane, as shown in Figure 18.
FIGURE 18 LOAD VERSION
3. On the Version Mainenance tab, select the version name

from the pull-down list of the Version, as shown in Figure 19.

45
FIGURE 19 VERSION LIST
4. On the Version Mainenance tab, press the CTRL key while

selecting the CPU file and FPGA file required by the OMP,
which are listed in Table 20. Right-click the selected version
files, and then select Create OMP Ini File from the shortcut
menu, as shown in Figure 20.
FIGURE 20 CREATING OMP BOOT FILES
5. After the OMP boot file is created successfully, the message

area prompts that OMP boot files are created successfully,
click OK, as show in Figure 21.

FIGURE 21 SUCCESSFUL INFOMATION
END OF STEPS
Result The boot file and version file appear in directory \zxwomcs\ums-
svr on the OMM server.
Configuring OMP Running

Parameters via Serial Port
� The serial cable has been prepared.
� The OMP boot file has been created.
� The hyper-terminal has been installed on the computer.
Context Perform this procedure to configure some parameters, including
OMM address, OMC server address, office ID, FTP user
name/password and startup mode. These parameters are
required by OMP board to communicate with the OMM server
Steps
during startup.
1. Connect one end of RS232 serial cable to serial port of debug-
ging computer, another end to debug port of OMP backboard.
2. On the debugging computer, click Start > Programs >
Accessories > Communications > Hyper Terminal in the
Windows OS, as shown in Figure 22.

47
FIGURE 22 CONNECTION DESCRIPTION
3. After click OK, the following figure pops up. Select the serial
port connected to the foreground and then click OK, as shown
in Figure 23.
FIGURE 23 CONNECT TO DIALOG BOX
4. On the COM1 dialog box, click the Restore Defaults button,

and then click OK, as shown in Figure 24

FIGURE 24 COM1 PROPERTIES
5. After entering the hyper-terminal, if there is no words, restart

the OMP board. When the Press any key to stop auto-boot...
prompt appears after entering hyper-terminal, press any key
instantly to stop automatic booting and then to configure the
OMP parameters, as shown in Figure 25.
FIGURE 25 PRESS ANY KEY TO STOP AUTO-BOOT
6. If the Boot Password (3GPLAT or 3gplat) appears, as shown in

Figure 26, type the password 3gplat and press Enter.

49
FIGURE 26 BOOT PASSWORD
7. When the 3GPlat Boot appears, type 1 to select Config MP-

net parameters (only for Omp and Cmp), and then press
Enter, as shown in Figure 27.
FIGURE 27 3GPLAT BOOT
8. Open the Config selection window, type 1 to select Set Omp

(or Cmp)’s Omc IP.MAC.Gateway IP, and then press

FIGURE 28 CONFIG SELECTION
9. Enter the OMP’s OMC Ip Address window, and type the IP

address 192.168.X.1 in which, the X indicates the office
direction ID of the office, and then Press Enter, as shown in
Figure 29.
FIGURE 29 ENTER OMP’S OMC IP ADDRESS
10. Enter the Enter OMP’s OMC Mac address window, type the
hardware address 00.208.208.161.00.X planned by OMP, in
which, the X indicates the office ID of the office, as shown in
Figure 30. Press Enter.

51
FIGURE 30 ENTER OMP’S OMM MAC ADDRESS
11. Enter the Enter OMP’s Gateway Ip address window, type

the network gateway IP address of the OMM server, or press
Enter to skip this configuration, as shown in Figure 31.
FIGURE 31 ENTER OMP’S GATEWAY IP ADDRESS
12. Enter the Enter OMC Server IP Address address window,

type the IP address of the OMM server, and press Enter, or
press Enter directly to skip this configuration, as shown in
Figure 32.

FIGURE 32 OMC SERVER IP ADDRESS
13. Enter the Config selection window, type 2, and then press
14. Enter the Enter OMC IP Address window, type the IP

address of the OMM server, and then press Enter, as shown
in Figure 34.

53
FIGURE 34 OMM IP ADDRESS
15. Enter the Enter OMC FTPSVR User Name window, type the
default FTP name uep, and then press Enter. Then the Enter
OMC FTPSVR User Password window will pop up, type the
default FTP password uep and press Enter, as shown in
Figure 35.
FIGURE 35 FTP CONFIG
16. Enter the Enter OMC FTPSVR File Path window, press Enter
to skip this configuration, and then enter the boot file config-
uration window.
17. Type the boot file name ompcfgX.ini, in which, the X
indicates the office direction ID of this office, then press

FIGURE 36 OMPCFG FILE
18. Enter the Config selection window and type 3, as shown in

Figure 37.
19. Enter the Set OMP Boot Type window, type 0 and then
press

55
FIGURE 38 OMP BOOT TYPE
20. Enter the Config selection window and then type 4, as

shown in Figure 39.
21. Enter the Enter Bureau No. window, type the office direction
ID, and then press Enter, as shown in Figure 40.

FIGURE 40 BUREAU NO.
22. Enter the Config selection window and then type 5, as

shown in Figure 41.
23. Enter the 3GPlat Boot configuration window, type 0 and

then press Enter, as shown in Figure 42.

57
FIGURE 42 3GPLAT BOOT
END OF STEPS
Result When the OMP starts up automatically, it will download the

version file and the FPGA file from the OMM server. The OMP
board runs normally, and the RUN indicator on the OMP board
flashes slowly.
Configuring OMP Global Data

� The OMM server and the local maintenance terminal are in-
stalled correctly.
� OMP startup parameters are configured.
Context After OMP board is started, the OMP global data should be config-
ured to make sure that the foreground/background IP addresses
are in the same network section. For example, the IP of the OMM
server is 192.4.1.1, and the IP of the foreground is 192.168.79.1.
In order to ensure that the IP address of the foreground and that
of the background are in the same network section, it is required
to set the MASK as 255.0.0.0.
system tree.
SET:NEID=11;
2. Set the global data OMP configuration, the command is SET
OMP.
Table 21 describes the parameters in this command SET
OMP.

TABLE 21 PARAMETERS IN THE SET OMP COMMAND
OMP It indicates the valid IP address. Enter

OMPIP background it according to the actual conditions.
IP address The background can access the OMP
through this IP address
OMP
MASK Configure the address range of OMP.
background
Types it according to the real
IP mask
condition
GATE- OMP to OMM If there is no gateway, it can be the

WAY gateway sub-network address of OMMSERVER
OMCIP OMC server It indicates the valid IP address. Enter

sub network it according to the actual conditions
Example: Configure the global data OMP information with the

following requirements.
� OMP IP address: 192.168.4.1
� OMP subnet address to the background IP:
255.255.0.0
� Gateway IP address: 192.168.1.1
� OMM server IP address:
192.168.79.1 The command is as
follows:
SET OMP:OMPIP=192.168.4.1 MASK=255.255.0.0, GATE
WAY=192.168.1.1, OMCIP=192.168.79.1;
Result After
E the
ND OF command is executed, the SUCCESS result is shown in
STEPS
Synchronizing All Tables

� The OMM server and the local maintenance terminal are in-
stalled correctly.
Context To synchronize the data is to send the data saved in the OMM
server to the foreground so that the foreground network element
can obtain the data from the OMM server. Only the admin sub-
scriber can synchronize all the tables.
system tree.
SET:NEID=11;

59
2. Synchronize all the tables. The command is SYNA.

Table 22 describes the parameters in this command SYNA.
TABLE 22 PARAMETERS IN THE SYNA COMMAND
Parameter Explanation Instruction
for designating the name
of the user whose data are
USERNAME User Name transferred, with a
length ranging from 0 to
50
characters. If it is left blank,
the table data of admin's
own are transferred.
STYPE Transmission type Select ALL
for designating the
module(s) to be transferred.
Up to 127 modules can
be selected, which is
MODULES Module list represented by a decimal
numeral, and separated
with & (for example,
MODULES=1&3&4).
Empty string indicates all
modules.
It is an optional parameter,
with a default of 600.
Adjust this duration
Response timeout according to the actual
TIMEOUT
(100ms) requirements. Set a longer
timeout duration when the
data are large, otherwise,
timeout failure may occur
It is an optional parameter.
Save when
SAVE Usually the default value YES
completed
is selected.
Sync to slave
TOSLAVE In general, the default value
when completed
YES is selected.
Example: Admin synchronization data synchronizes all the ta-

bles. The command is as follows.
SYNA:STYPE=ALL,TIMEOUT=600,SAVE=YES,TOSLAVE=Y
ES;
END OF STEPS


Postrequisite It is required to restart the OMP board.
Note:
It is required to resynchronize the data for three times and
restart the OMP board for two times. Before the restart, it is
required to confirm whether the synchronized table is saved. The
save operation may take three to five minutes. Two methods
are available.
� Check the disk saving status of the foreground on the OMM
client.
� Check whether the usage ratio of the foreground CPU is about
3% with the GetCpu command.
Checking Operations
1. Select Start > Run, then the Run dialog box will pop up.
2. Type CMD and then press Enter to enter the CMD dialog box.
3. Type telnet 192.168.X.1, in which, the X indicates the office
direction ID, and then press Enter.
4. Type the user name zte and the password zte, and then
press
Enter for two times, as shown in Figure 43.
FIGURE 43 USER NAME AND PASSWORD
5. Type SCSSHowMcmInfo to check the status of the board and

then press Enter, as shown in Figure 44.

61
FIGURE 44 STATUS
The printed status of the board is MASTER and Work, which

means that the OMP board runs normally.
Loading Version Files

� All the tables are synchronized.
� The version files of each board are ready.
� The foreground and background are correctly connected.
Context A physical board initially does not load its version files, so you
need to load them manually.
Table 23 lists the board version files.
TABLE 23 BOARD VERSION FILES
Physical Logical Instruc-

Version
Board Board Version File Name
Type tions
Type Type
MSCS_MPX86_2_RPU Version
MPX86_2 RPU CPU
_P4_CS_Z_T.BIN file of
RPU
Version
MSCS_MPX86_2_MP_
MPX86_2 MP CPU file
P4_CS_Z_T.BIN
of
SMP
Version
MSCS_UIM_2_UIM_75
UIM_2 UIM CPU file
5_CS_Z_T.BIN
of
UIMC
CPU MSCS_MNIC_2_SIG_I
Version
PI_23XX_CS_Z_T.BIN
MNIC_2 SIPI file
UC_MSCSERVER_MNI of
MICRO- SIPI
CODE C 2_SIG_IPI_CS T.
UOF

Physical Logical Version Instruc-

Board Board Version File Name
Type tions
Type Type
SPB_2 SPB CPU MSCS_SPB_2_SPB_82 Version

60_CS_Z_T.BIN file of
SPB
CPU MSCS_MNIC_2_USI_2
3XX_CS_Z_T.BIN Version
MNIC_2 USI
MICRO- UC_MSCSERVER_MNI file of USI
CODE C_2_USI_CS T.UOF
Version
MSCS_CHUB_CHUB_8
CHUB CHUB CPU file
245_CS_Z_T.BIN
of
CHUB
It is not
required
CLKG - - - to
load
the
ver-
Steps sion files
1. On the NetNumen(TM) M30 MSCS/MGW window, select
Views > Professional Maintenance to enter the Profes-
sional Maintenance window.
> Version Mainenance to show the Version Mainenance
tab in the right pane, as shown in Figure 45.
FIGURE 45 VERSION MAINENANCE
3. On the Version Mainenance tab, select the version name

from the Version pull-down list, as shown in Figure 46.

63
FIGURE 46 VERSION LIST
4. On the Version Maintenance tab, press down the CTRL key,

and select all the version files (the version files required by
each board are shown in Table 23) required by the foreground
board, as shown in Figure 47.
FIGURE 47 BATCH VERSION LOADING BY DEFAULT
5. Right click the selected version files and select the shortcut
menu Batch Load Default Version. The Switch Process

window will pop up, which displays the process of the version
file (that is the multicast process).
END OF STEPS
Result After the version loading is completed, the board will restart. The
board compares its version files, and obtains its required version
files. After the version files are loaded, the board is in normal
running status. The RUN indicator on the front panel of the board
will flash at 1 Hz.
Postrequisite It is required to synchronize the data.
Verifications
1. Judge whether the board runs normally through the indica-
tors on the panel. Table 24 lists the indicator statuses of each
board.
TABLE 24 BOARD INDICATOR STATUSES
Na- Color Mean- Instruction Remarks

me ings
Flashing at 5 Hz: the

board is being
RUN powered on. When all the
RUN Green indicators on
indicator Flashing at 1 Hz: the board are
the board is running ON, probably
normally. the board
hardware
On: The board is is faulty,
Active/ active the board
ACT Green standby
Off: The board is data is not
indicator
standby configured, or
the boot file
On: The board gives of the does
an alarm. not match the
ALM Red Alarm
version files.
indicator Off: The board gives
no alarm.
2. On the Version Query tab, check whether the version file

number of the board is correct, thus to verify whether the
version files are loaded correctly.
Creating MGCF Tones in

Batches
� The tone scripts are loaded.

65
Context Perform this procedure to create the tone-related data on the

MGCF side in batches, including tone ID, service key and its
relation to tone ID and other tone packet configuration.
All the tone packet configurations are created in batches, except
interconnection conversion of external service keys that is config-
ured manually with the ADD SVRTRANSKEY command.
system tree.
SET:NEID=11;
2. Create MGCF tones in batches. The command is BADD
STONE.
Table 25 describes main parameters in the BADD STONE
command.
TABLE 25 PARAMETERS IN THE BADD STONE COMMAND
Parameter
Name
Voice type, includes
� ALL: All configuration of
tone
� ICP: tone service
� KD: the relationship
between the call type
and the KD
In general, the
� LANGDES: language
ALL option
description string
TYPE is selected,
� MSGID: external MSGID, indicating
relation to inter service that all
key the tone types are
created in
batches.
� TONEID: the service
tone ID to the protocol
package
� TONEIN: service key and
its relation to tone ID
� TONEPLAYMT: the
method of playing tones
Example: Create the batch processing of all the MGCF tones.

BADD STONE:TYPE=ALL;
END OF STEPS


Office
Information
Configuration
Overview
Table 26 shows the office information configuration flow.
TABLE 26 OFFICE INFORMATION CONFIGURATION
Steps Topic Instructions Command
The local SPC

configuration
includes 14-bit
Creating local SPC configuration,
1 24-bit SPC ADD OPC
signaling point
configuration and
the upper-layer
user configuration
of MTP3.
Configure some
parameters of the
local exchange,
Creating the local including the
2 exchange type, ADD LOFC
office configuration
signaling point
type, MTP3 test
code, and other
parameters.
Creating Local Office Signaling Point

� You know the 14-bit SPC, 24-bit SPC, and the local toll area
code.
Context Signaling Point Code (SPC) is a unique code for identifying each
node in the signaling network. The local SPC configuration
includes 14-bit SPC configuration, 24-bit SPC configuration and
the upper- layer user configuration of MTP3. If the multi-SPC
networking is adopted, it is required to create multiple local
signaling points with different network types.
system tree.

67
SET:NEID=11;
2. Create the local office signaling point. The command is ADD
OPC.
Table 27 describes the main parameters in the ADD OPC com-
mand.
TABLE 27 PARAMETERS IN THE ADD OPC COMMAND

Name tion
The signaling network

where the local office It is a mandatory
NET runs, which has the parameter. It ranges
same signaling network from 1 to 8. In general,
type of the adjacent 1 is selected.
office configured later.
It is a mandatory
NAME parameter, with a length
User-defined alias
ranging from 1 to 50
characters.
It is an optional
The toll zone code of the
RC parameter. Do not
place where the local
add 0 ahead of an area
office is located
code
It is an optional
parameter. By default,
Signaling point code select TRIPLE_DEC,
SPCFMT
format which is a three-section
decimal number in
888/383 format.
14-bit SPC of local

OPC14 office, which is provided
by the operator It is configured
according to the
24-bit SPC of local signaling point planning.
OPC24 office, which is provided
by the operator
Toll dialing prefix. It is 0

PREFIX Dialing prefix
for China.
Select the application

types of this signaling
point, not unrelated
subscribers. According
Protocols supported by to different network
APPTYPE types, Select H248
local office
User for Mn Interface,
select BICC User, TUP
User, ISUP User for
inter-office signaling
point code.


Name tion
This field is not used

when the local office is
interconnected with a
TDM office. It is
configured as 0. When
Network appearance this signaling point is
NETAPP interconnected with
used in M3UA layer
an IP signaling point
with the same network
type, you need to
negotiate this field with
the opposite end for
consistency.
When NOUSE is chosen,

if the NETAPP field is 0,
the network appearance
is ineffective; if the
Identification field used NETAPP field is not 0,
to configure whether the the network appearance
network appearance is is effective.
INFO effective. Three modes
can be chosen, including When NETAPP is
NOUSE, NETAPP and chosen, the network
NONETAPP. appearance is effective.
When NONETAPP
is chosen, the
network appearance
is ineffective.
Configure whether the

network corresponding
TAG Other attributes to the office has the
ISNI function and
translation node.
Example: Create a 24-bit signaling point with the following

requirements.
� Direct-associated office: MSCS, CSCF, BGCF
� Signaling point type: 24-bit signaling point
� SPC: 3.11.1
� Application type: ISUP, SCCP, BICC, and TUP
� Alias: NET1.
ADD OPC:NET=1,NAME="NET1",SPCFMT=TRIPLE_DEC,O
PC24="3.11.1",APPTYPE="BICC"&"ISUP"&"SCCP"&"TUP",R
C="25",PREFIX="0",NETAPP=0,INFO=NONETAPP,DMIDX
=0;
Example: Add a 14-bit signaling point that is interconnected
with IM-MGW through Mn interface with the following require-
ments.
� SPC: 1.11.1

69
� Application type: H.248

� Alias: NET2
ADD OPC:NET=2,NAME="NET2",SPCFMT=TRIPLE_DEC,OP
C14="1.11.1",APPTYPE="H.248",RC="25",PREFIX="0",NE
TAPP=0,INFO=NONETAPP,DMIDX=0;
END OF STEPS

Creating Local Office Configuration

� The local office signaling point is created.
Context Perform this procedure to configure some parameters of the local
exchange, including the exchange type, signaling point type and
other parameters.
system tree.
SET:NEID=11;
2. Create the local office configuration. The command is ADD
LOFC.
Table 28 describes the parameters in the ADD LOFC
command.
TABLE 28 PARAMETERS IN THE ADD LOFC COMMAND

Parameter Parameter Descrip-
Instruction
Name tion
Local office type,
including It is a mandatory
� LOCAL (Local parameter. Several
Exchange) options can be selected.
� DOMTOLL (National Configure this parameter
OFFTYPE Toll Exchange) according to actual
type.
� INTTOLL In general, select Local
(International Toll Exchange, National
Exchange) Toll Exchange and
� OA (In One MGCF Exchange when
Area) MSCS serves as MGCF.
� UM (User
Telephone)


Name tion
� R2NAT (R2 National
Exchange)
� R2INT (R2
International
Exchange)
� MGCF
(MGCF
Exchange)
It is a mandatory
parameter for
designating the network
NET Network type type ID of the local
office. In this case, one
network type is
configured.
It is a mandatory
SEQ Sequence in area parameter with a default
of 0, ranging from 0 to
255.
It is an optional
character-type
parameter with a
TCODE Test code length not more than
15 characters. This
parameter can contain
0~9, *, and #, with a
default of 1234
Signaling point type, It is an optional

SPTYPE including SEP, STP, and parameter.
STEP Select STEP
It is an optional
parameter, with a default
RESTART Signaling point restart of YES. The default
value indicates that this
function is enabled
Languages of the office,

including:
� DEFAULT
� FRENCH
The default value is
LANG
� ENGLISH DEFAULT.
� GERMAN
� RUSSIAN
� SPAISH

71

Name tion
The restart time when
the signaling point used
as STIP (the unit is
RSTTIME Reset Time(ms) ms). It is an integral
parameter, ranging
from 100 to 59900, the
default value is 10000.
Not more than 50
NAME characters. It is the
Alias
name customized by a
user for easy
memory.
Example: Configure the local exchange with the following re-

quirements.
� Office type: LOCAL&DOMTOLL&MGCF
� Network type No.: 1
� Signaling point type: STEP
Default. The command is as
follows:
ADD
LOFC:OFCTYPE="LOCAL"&"D
OMTOLL"&"MGCF",NET
=1,SEQ=0,TCODE="1234",SPTYPE=STEP,LANG=DEFAUL
T,RESTART=YES,RSTTIME=10000,T19=68,T20=60,T21
=64;
END OF STEPS


Chapter
3
Resource Configuration
Table of Contents
Resource Planning ............................................................. 73
Configuring Resource Attributes........................................... 73
Resource Planning
It is very important to make the overall resource planning in ad-
vance no matter whether common networking, region-system
networking, or dual-homing networking is adopted.
The basic principle of resource allocation is as follows:
1. Do not add unused resources in the resource management
system.
For example, if it is not required to configure the “SIP called
number analysis selector”, do not configure the corresponding
resources.
2. Allocate the required resources on a basis of sections to avoid
too separate resource allocation.
For example, when the “Office ID” resource is allocated to 5
areas, each area is allocated with 100*N adjacent office IDs.
Each section has 100 adjacent office IDs, and N can be
different in different areas.
3. Add moderate surpluses for required resources, and do not
use up them.
For example, if the “Office ID” resource is allocated to 5
areas, do not allocate all 2048 adjacent office IDs, except
that each area really has 400 adjacent offices to be
configured. If the “Office ID” resource in one area is
insufficient after a period of time, separately allocate one
section of (100) adjacent office IDs to this area.
Configuring Resource
Attributes

73
� The overall resource planning is made.

Context The MGCF has authority-division and area-division function, so it
is required to allocate different resource attributes for different
areas before configuring the data. If the area is not divided, all
the resource attributes can be configured in the common area.
Table 29 lists the resource types, key fields and value ranges in
the MGCF resource management system.
TABLE 29 RESOURCE TYPES, KEY FIELDS AND VALUE RANGES OF

THE MGCF
Configura- Resource
Key Fields Minimum Maximum
tion Types
Items
Office data Adjacent
configura- Office ID 1 3000
office
tion
Signaling
Link set No. 1 1024
linkset
Signaling Signaling 1 2000

route route
No.
Protocol con- SCTP SCTP ID 1 2048
figuration
ASP ASP ID 1 2048
AS AS ID 1 640
M3UA
M3UA static
static route 1 640
route
ID
Node
Topolog
Topolog 1 2048
Topology y node
y Config
configura- ID.
tion
Voice Codec Templat 1 255
Template e ID
Trunk
Trunk group group 1 4000
number
Outgoing Route No. 1 20000
route
Trunk rout- Outgoing Route set
ing configu- 1 3000
route No.
ration set
Outgoing Route 1 3000
route chain chain ID
Chain
Chain analysis analysis 1 3000
index

Chapter 3 Resource Configuration
Configura- Resource Key Fields Minimum Maximum

tion Types
Items
Automatic Re-routing
Re- 1 1000
route set
routing
Route Set
Number Number
Pre-analysis Pre- 1 1000
Selector analysis
Selector
Number Number
Analysis Analysis 1 1000
Entrance Entrance
Number Number
1 4096
Analysis Analysis
Number Selector Selector
analysis Template Template

of Number of Number 1 65535
Analysis Analysis
Selector Selector
Number Number
Transfor Transfor 1 2048
m Index m Index
Black
Black White 1 1000
White List
List Selector
Selector
SIP Called
Number 1 1000
Selector
Analysis
Selector
Location Area Location 1 65534

Area ID
Access con-
figuration Emergency Emergency
Call Center call center 1 255
Index index
Welcom
Welcome 1 128
Messages e
Message
Service con- Code
figuration
Camel In-
Camel Access
forma- 1 255
Subscription
tion Index
Information
Steps Number
1. On the NetNumen (TM) M30 window, select menus Views
> Resource Management, and the Resource
Management
window appears, as shown in Figure 48 .

75
FIGURE 48 AREA TREE
2. In Area Tree, right click the area where resources need to be

added under the MSCS. Click the shortcut menu Add re-
source, as shown in Figure 49.
FIGURE 49 ADDING RESOURCES
3. The Add Resource dialog box appears, as shown in Figure 50.

The parameter description is shown in Table 29.

Chapter 3 Resource Configuration
FIGURE 50 RESOURCE ADDING DIALOG BOX
4. Select the resource type to be added from the field Resource

Type drop-down list box, and input the corresponding
parameters. Click the Add button, and the added resource
is displayed in the resource list.
5. After all kinds of required resource types are configured, click
the Confirm button to exit the resource configuration.
END OF STEPS
Result Resource types display on the Resource Management window.

77

Chapter
4
MGCF-IM-MGW
Interconnection Data
Configuration
Table of Contents
Overview.......................................................................... 79
Interface IP Address Configuration ....................................... 81
BFD Configuration (Optional) .............................................. 87
Creating a Static Route ...................................................... 90
Adjacent Office and Topology Configuration ...........................
92 SIGTRAN Configuration ....................................................
106
H.248 Configuration......................................................... 119
Overview
Description Mn interface is the interface between MGCF and IM-MGW. It
usually adopts the IP bearer, and its protocol stack adopts the
BICC/M3UA/SCTP/IP mode.
Configuration Figure 51 shows the flow of configuring the interconnection data
Flow between MGCF and IM-MGW.

79
FIGURE 51 FLOW OF MGCF-IM-MGW INTERCONNECTION

CONFIGURATION
Description The flow of MGCF-IM-MGW interconnection data is shown in Table

30.
TABLE 30 FLOW DESCRIPTION
According to the IP address planning

Interface IP address , configure the loopback interface
1
configuration address, SIPI interface address, and
USI interface address.
BFD parameters are configured

BFD configuration when load-sharing networking mode
2
(optional) is adopted. BFD is not required for
active/standby networking mode.

Chapter 4 MGCF-IM-MGW Interconnection Data Configuration
It is configured when the service IP

3 Creating static route address of local signaling plane and
PE interface address are not in the
same network section .
Adjacent office and It is to create adjacent office and

4 topological node
topological node .
configuration
5 SIGTRAN configuration It is configured when IP bearer is

adopted.
6 H.248 configuration It is only configured for Mn/Mc

interface.
Interface IP
Address
Configuration
Overview
Interface IP addresses are planned according to the actual net-
working applications. The IP address of Nc, Mj/Mg interfaces can
be configuration independently, or share with the Mn interface ad-
dress.
Table 31
TABLE 31 INTERFACE IP ADDRESS CONFIGURATION
Steps Operations Instruction Command

Create the serv- INTERFACE
Creating a ice address on LOOPBACK
1
Loop- back the RPU loopback
Interface port. ADD IP
ADDRESS
Creating an SIPI Create IP ad-

dress to some INTERFACE
2 Interface Ad-
dress physical port of ADD IP ADDRESS
this SIPI board
Create a
virtual
Creating a Vir- interface ad- INTERFACE
3 tual Interface dress. MGCF
Address is ADD IP ADDRESS
interconnected
to a SIP office
through its vir-
tual interface.

81
Creating a Loopback Interface

� The RPU module configuration is completed, and the RPU
works normally.
Context Configuring the loopback interface means configuring the service
address on the RPU loopback port. Since the service address of
Mc interface can use ports 1 and 2, it is recommended that each
port is configured with one IP address.
system tree.
SET:NEID=11;
2. Enter the RPU loop back interface. The command is INTERF
ACE LOOPBACK.
Port represents the port number, ranging from 1 to 128.
Example: Enter the loop-back interface whose port number is
1.
INTERFACE LOOPBACK:PORT=1;
3. Create the loopback interface address. The command is ADD
IP ADDRESS.
Table 32 describes the main parameters in the ADD IP AD-
DRESS command.
TABLE 32 PARAMETERS IN THE ADD IP ADDRESS COMMAND
Parameter Parameter
Instruction
Name Description
It is a mandatory
IP IP address parameter. The IP address
of the loop-back address.
It is a mandatory
MASK Mask parameter of 32-bit.
In general, it is
255.255.255.255.
BROADCAS- It is an optional
Broadcast address parameter. In general, it
TIP
is 255.255.255.255.
Example: Create a loop back address with the following re-

quirements.
� IP address: 192.168.11.11
� Subnet mask: 255.255.255.255.


ADD IP ADDRESS:ADDRESS="192.168.11.11",MASK="255
.255.255.255",BROADCASTIP="255.255.255.255";
4. Save the online configured data. Otherwise, these will loss
when the RPU is restarted. The command is SAVE ONLINED
ATA;.
5.Exit the interface configuration mode. The command is EXIT;
END OF STEPS

Creating an SIPI Interface Address

� The SIPI unit is created.
Context MGCF is interconnected to IM-MGW on the CE through its SIPI
board. The online configuration of SIPI board interface is to
assign an IP address to some physical port of this SIPI board.
system tree.
SET:NEID=11;
2. Enter the SIPI board interface configuration mode. The com-
mand is INTERFACE.
Table 33 describes the main parameters in the INTERFACE
command.
TABLE 33 INTERFACE REAL INTERFACE

Name Description
SUBSYS- It is a mandatory parameter.

Subsystem ID
TEM Select the default value 0.
MODULE It is a mandatory parameter.

Module No.
Select the default value 1.
It is a mandatory parameter. It
is the unit number of the real
UNIT Unit No. interface. Select the unit number
of the board corresponded by the
interface.

83

Name Description
It is a mandatory parameter. Real

SUNIT Subunit No interface’s sub-unit number fixedly
adopts 1.
It is a mandatory parameter. The

port number refers to the network
interface serial number of the
PORT Port number SIPI rear board for connecting to
the external. The four network
interfaces are numbered 1 to 4
from top to bottom. Only the first
port is used.
Example: Enter the interface address of SIPI board. The con-

figuration requirements are as follows.
� Unit number: 321
� Sub-unit number: 1
� Port number: 1
� Home module number: No.1 OMP
module. The command is as follows.
INTERFACE:SUBSYSTEM=0,MODULE=1,UNIT=321,SUNI
T=1,PORT=1;
3. Create the interface address of the SIPI. The command is ADD
IP ADDRESS.
Table 34 describes the main parameters in the ADD IP ADDR
ESS command.

Name Description
IP IP address The Mn interface address of SIPI
board
It is a mandatory parameter. The

MASK Subnet mask real interface subnet address of
corresponding interface board
BROADCAS- Broadcast corresponding to the broadcast
TIP address address of the real address of the
corresponding interface board.
Example: Create the interface address of the SIPI. The config-

ured parameters are as follows.
� IP address: 192.168.1.11
� Subnet mask: 255.255.255.248
� Broadcast address:
255.255.255.255. The command is as
follows.

ADD IP ADDRESS:ADDRESS="192.168.1.11",MASK="255.
255.255.248",BROADCASTIP="255.255.255.255";
when the RPU is restarted. The command is SAVE ONLINED
ATA;.
END OF STEPS

Creating a Virtual Interface Address

� Physical configuration of SMP module is completed.
Context MGCF is interconnected to a SIP office through its virtual
interface.
Steps MML Terminal window or select a NE from the system tree
system tree.
SET:NEID=11;
2. Enter the virtual interface configuration mode. The command
is INTERFACE.
Table 35 describes the main parameters in the INTERFACE
command.
TABLE 35 INTERFACE VIRTUAL INTERFACE

Name Description
SUBSYS- It is a mandatory parameter.

Subsystem ID The changeless value for virtual
TEM
address is 255.
MODULE Module No. Select the SMP which processes
the IP signaling.
UNIT Unit No. The changeless value for virtual
address is 65535.
SUNIT Subunit No The changeless value for virtual
address is 255.

85

Name Description
PORT Port number The changeless value for virtual
address is 65530.
Example: Enter the vitual interface address. The configuration

requirements are as follows.
� Subsystem number: 255
� Module number: 3
� Unit number: 65535
� Sub-unit number: 255
� Port number: 65530
INTERFACE:SUBSYSTEM=255,MODULE=3,UNIT=65535,S
UNIT=255,PORT=65530;
3. Create a virtual interface address. The command is ADD IP
ADDRESS.
Table 36 describes the main parameters in the ADD IP AD-
DRESS command.

Name Description
It is a mandatory
IP IP address parameter. The IP address
of the virtual interface
address.
It is a mandatory
MASK Mask parameter of 32-bit.
In general, it is
255.255.255.255.
BROADCAS- It is an optional
Broadcast address parameter. In general, it
TIP
is 255.255.255.255.
Example: Create a virtual address with the following require-

ments.
� IP address: 10.1.44.77
� Subnet mask: 255.255.255.255.
� Broadcast address:
255.255.255.255 The command is as
follows.
ADD IP ADDRESS:IP="10.1.44.77",MASK="255.255.255.2
55",BROADCASTIP="255.255.255.255";


when the RPU is restarted.The command is SAVE ONLINEDA
TA;.
END OF STEPS

BFD
Configuration
(Optional)
Overview
Definition Bidirectional Forwarding Detection (BFD) can greatly accelerate
the fault detection speed and enhance the recovery function. Cur-
rently, EFD function is mainly used to quickly detect the link sta-
tus of soft-switching equipment. It can not only find the link fault
quickly, but also inform the equipment that initiates this detection
to handle this fault.
BFD Function In general, BFD function is configured in the load-sharing
Configuration networking mode. One interface is configured with a BFD
session.
The BFD authentication
Create a BFD entry is configured only ADD BFD
1 when the authentication
authentication AUTH
to the BFD session is
required.
Configure the mapping
Create a BFD relationship between the ADD BFD
2 real address of the local
session
SIPI interface board SESSION
and the router
interface.
Creating BFD Authentication

The MML Terminal window is opened.
Context The BFD authentication is created only when the authentication
to the BFD session is required.

87
Note:
Authentication type and Key of both ends must be consistent.

system tree.
SET:NEID=11;
2. Create BFD authentication. The command is ADD BFD AUTH.
Table 37 describes the parameters in the ADD BFD AUTH
command.
TABLE 37 PARAMETERS IN THE ADD BFD AUTH COMMAND
Parameter Parameter
Instruction
Name Description
Authentication including SIMPLE, MD5,
AUTHTYPE
type METIC_MD5, SHA1, and
METIC_SHA
AUTHKEYID Authentication It is a mandatory parameter. Type

ID an integer within 1~255.
KEY KEY Enter it according to different
authentication types.
Example: Create BFD authentication with the following re-

quirements.
� Authentication type: SIMPLE
� Authentication ID: 1
� KEY: 1.
The command is as follows:
ADD BFD AUTH:AUTHTYPE=SIMPLE,AUTHKEYID=1,KEY
="1";
END OF STEPS

Creating a BFD Session


Context Perform this procedure to configure the mapping relationship be-

tween the real address of the local SIPI interface board and the
router interface.
system tree.
SET:NEID=11;
2. Create BFD session. The command is ADD BFD SESSION.
Table 38 describes the parameters in the ADD BFD SESSION
command.
TABLE 38 PARAMETERS IN THE ADD BFD SESSION COMMAND

Name Description
It is a mandatory
SRCIP Local address of
parameter. Types the
BFD session
interface address of SIPI.
It is a mandatory
Remote address of parameter. Types
DSTIP
BFD session the address of the
corresponding router
It is a mandatory
parameter. Includes
MULTIHOP Multi hop flag SINGLE_HOP and
MULTIHOP. In general,
select SINGLE_HOP
ranging from 100000 to
10000000.
DESMINT Min-transmit
- interval The router produced by
XINTVAL (ms) different manufacturers is
configured with different
values.
REQMINR- Min-receive Both ends of the BFD

XINTVAL interval (ms) session should be
consistent.
Type an integer ranging
Detect from 2 to 255.
DETECTMULT
accumulator
The recommended value is
2
OPTMODE Work mode It is an optional parameter.

Select ASYNCHRONOUS
AUTHID Authentication ID The parameter ranges from

1 to 255
CHGOVER Change Over YES can be selected

89
Example: Create the BFD session when SIPI interface board is

connected with the router. The requirements are as follows.
� Local address of BFD session: 10.0.74.4
� Remote address of BFD session: 10.0.74.1
� Single hop flag: SINGLE_HOP
� Working mode:
Asynchronous. The command is
as follows:
ADD BFD SESSION:SRCIP="10.0.74.4",DSTIP="10.0.74.1
",MULTIHOP=SINGLE_HOP,DESMINTXINTVAL=100000,R
EQMINRXINTVAL=100000,DETECTMULT=3,OPTMODE=A
SYNCHRONOUS;
END OF STEPS
Creating a Static Route

� The interface address is created.
� The BFD parameters are created when load-sharing
networking mode is adopted.
Context Static route is created when the service IP address of local sig-
naling plane and PE interface address are not in the same net-
work section. Under the active/standby working mode, a destina-
tion address needs to be configured with a route only. Under the
load-sharing working mode, a destination address usually needs
to be configured with two routes.
system tree.
SET:NEID=11;
2. Create a static route. The command is ADD IP ROUTE.
Table 39 describes the parameters in the ADD IP ROUTE
command.

TABLE 39 PARAMETERS IN THE ADD IP ROUTE COMMAND
Parameter Parameter
Instruction
Name Description
NETPRE Net prefix Type the network section of the
opposite-end equipment service
address according to the network
planning. Its prefix should match
its mask
MASK Mask
indicating the router interface
NEXTHOP Next hop IP address (VRRP address). Type the
gateway address to the opposite
end office
DISTANCE Distance It is an optional parameter with a

default of 1, ranging from 1 to 254
Enable BFD general, select NO. Only when next
BFDDETECT
Detect hop is IP address, BFDDETECT
option is in effect
Example: Create the static route to the opposite end with the
� Working mode: active/standby mode
� Service address of the opposite equipment:
11.11.11.1
� Mask: 255.255.255.0
� Next hop IP:
10.0.74.1. The command is
as follows:
ADD IP
ROUTE:NETPRE="11.11.11.1",MASK="255.255.
255.0",NEXTHOP="10.0.74.1",DISTANCE=1,BFDDETECT
=NO;
Example: Create two static routes to the opposite end with
the following requirements.
� Working mode: load-sharing mode
� Service address of the opposite equipment:
11.11.11.1
� Mask: 255.255.255.0
� Next hop IP: 10.0.74.1 and
10.0.74.2. The command is as follows:
ADD IP
=NO;
ADD IP
=NO; Confidential and Proprietary Information of ZTE CORPORATION
91
END OF STEPS

Adjacent Office and

Topology Configuration
Overview
Introduction Adjacent office configuration means configuring the neighboring
office of the local office. There are two association modes, direct
association and quasi-association.
If the adjacent office is regarded as a node in the whole network
topology when the local office is in the center, topological node
configuration means adding the topological node of its adjacent
office in the local office. The topological nodes configured on
MGCF include IM-MGW, CSCF, BGCF, MGCF, and MSCS.
Table 40 shows adjacent office and topology configuration.
TABLE 40 ADJACENT AND TOPOLOGY CONFIGURATION
Creating an Create the basic in-

1 MGW adja- formation of MGW ADD ADJOFC
cent office adjacent office.
Creating an Create the encoding

2 MGW voice and decoding speech ADD CODECTPL
CODEC tem- type modules sup-
plate ported by IM-MGW.
Creating Create the topol-

3 a topology ogy relationship be- ADD TOPO
node tween MGCF node
and IM-MGW node.
The inter-MGW
Creating in- bearer mode is con-
ter-MGW figured when the Nb ADD
4 interfaces between
bear MGWBEAR MOD
mode several IM-MGWs
(optional) under the same
MGCF are connected.
Creating an IM-MGW Adjacent Office


� The physical IP connection between the MGCF and the IM-

MGW is clear, which is implemented by the connection
between the FE1 interfaces on the rear board of the SIPI
boards of these two NEs.
� The signaling interworking data is planned and negotiated.
� The basic configuration of the local office is completed.
� The range of adjacent office number is configured in the re-
source management.
Context Perform this procedure to configure the basic information of IM-
MGW adjacent office.
system tree.
SET:NEID=11;
2. Create an IM-MGW adjacent office. The command is ADD
ADJOFC.
Table 41 describes the main parameters in the ADD ADJOFC
command.
TABLE 41 PARAMETERS IN THE ADD ADJOFC COMMAND
Parameter Parameter
Instruction
Name Description
A mandatory parameter,
indicating the identification
number of the adjacent
office, and ranging from 1
ID Office ID to 3000. In general, it is
configured as the exchange
ID of the adjacent office
during the all-network
planning
NAME User-defined alias It is a mandatory

parameter. Type a
customized name
indicating the network
type of the SPC used for
connecting the local office
NET Network type to the adjacent office when
the local office is
configured
with several SPs. The
default is the network type
of this SP when there is only
one SP in the local office
It is a mandatory
The type of adjacent parameter. Select MGW for
OFCTYPE the
office
IM-MGW bearing H.248
signaling. Select SGW for
another IM-MGW office

93

Name Description
SPCFMT SPC format Select TRIPLE_DEC
It is a mandatory
parameter. Select it based
SPCTYPE SPC type on the SPC type of the
adjacent office according to
the signaling point
planning. In China, all the
DPC Destination SPC NEs adopt the 24-bit SPC
indicating the local toll zone
RC Area code code of the adjacent office.
This parameter has impact
on the area code added by
the calling number
Association type,
including:
� AM_SURE
(direct
connection mode) It is an optional parameter.
ASSOTYPE
� AM_QUASI (half Select AM_SURE
direct connection
mode)
� AM_NONE (none
connection mode)
Select SEP (signaling end
Signaling point type, point) for the IM-MGW
SPTYPE including SEP, STP bearing H248 signaling.
and STEP Select STEP (signaling
transition /end point) for
another IM-MGW office
Subservice function,
including
� INTERNA-
TIONAL (Inter-
national signaling
point code)
� INTERNA-
TIONAL
STANDBY (In-
ternational It is an optional parameter.
SSF standby signaling In general, NATIONAL is
point code) selected at home.
� NATIONAL
(National
signaling point
code)
� NATIONAL
STANDBY
(National
standby
signaling point
code).


Name Description
Office Attribute,
including:
ISNI (Has ISNI
Function)
TAG It is an optional parameter
TRANS (Translate
Node)
TEST (Need Test
Info:0X02/0X01)
It is used to set whether the
MTP3 link actively initiates
TEST Test flag the link test after entering
the service status. In most
cases, this parameter is
selected.
with a default of NO. It
is used for SCCP to judge
whether to use the LUDT
message.
The maximum length of a
broadband link message
is 4,000, and that of a
narrowband link message
BANDFLAG Broadband attribute is 255. Because the MTP
layer does not have the
segmentation function,
the
incorrect configuration of
this parameter probably
causes the long packet to
be discarded.
Select YES when all the
links between two SPs are
SIGTRAN or ATM signaling
links.
Protocol Type,
including: It is an optional parameter.
The CHINA and the ITU
� CHINA are used for the NO.7
(China) signaling networking of the
ITU standard and the ANSI
PRTCTYPE � ITU (Interna-
is used for the NO.7
tional Telecom-
signaling networking of the
munications
American standard. In
Union)
general, select CHINA for
� ANSI (American the domestic office and
National select ITU for the
Standards international office
Institute)

95

Name Description
within 0~65535. In
general, select the default
value 65535. It is valid
when the protocol type
CLST Cluster ID of the adjacent office is
“ANSI”. The signaling point
connected to the signaling
transfer point belongs to
the corresponding cluster.
The cluster ID is configured
in the command ADD CLST
Office Info, including:
CIC_PCM (CIC starts
the load sharing
according to the PCM
code mode)
BLOCK (Manual block
status)
EVEN_CIC (The
office controls the It is an optional parameter
INFO even CIC when CIC and the default value is
resource contention CIC_PCM
occurs)
CALLING ( Calling
transform is allowed)
CALLED (Called
MOD24_CIC (CIC
mode with 24 mode)
TEST (Dynamic
observation)
RELATE- It is an optional parameter
Related Office ID
DOFC1 ranging from 0 to 3000
Office Extend Info,
including:
� SIGBRDCST
(Support Signa
ling Broadcast
Message)
� MTP (Hongkong
MTP Standard)
INFOEX � DUPU ( Screen It is an optional parameter
DUPU message)
�
SUA_REC_DT1
(Receive SUA
message and
handle it as DT1
message)
�
SUA_SND_DT1
(Send SUA
message and
handle it as DT1


Name Description
message without
SN.)
�
OPEN_TG_RES
(Open outter
trunk group
resource)
For example, create an IM-MGW adjacent office. The office ID

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

Creating an MGW Voice CODEC

Template
� The range of the MGW encoding and decoding speech
template numbers is configured in the resource management
configuration.
Context Perform this procedure to configure the encoding and decoding
speech type modules supported by MGW. In general, MSCS is
configured with a default common encoding and decoding
speech template.
system tree.
SET:NEID=11;
2. Create the MGW voice CODEC template. The command is
ADD CODECTPL.
Table 42 describes the main parameters in the ADD CODEC
TPL command.

97
TABLE 42 PARAMETERS IN THE ADD CODECTPL COMMAND
Parameter Parameter
Instruction
Name Description
Templat for defining an encoding and
ID
e decoding speech template,
number ranging from 1 to 255.
It is a mandatory parameter for

The group specifying the OID format and
GRPID number of the encoding and decoding type list.
speech coding. Up to eight types can be defined
in an encoding and decoding
template.

Valid option, setting whether this encoding
VALFG including YES and decoding speech template is
(valid) and NO valid.
(invalid)
Select YES

specify an Organization Identifier
(OID).
It has the following parameters.
OID OID � OID_NONE: No OID
� OID_ITU_T: ITU_T
� OID_ETSI: ETSI
� OID_IETF: IETF
ITU_T CODEC It is an optional parameter. In

ITYPE general, ITUT_G711A_64 is
type
selected.
ETSI CODEC general, ETSI_UMTS_AMR
ETYPE
type and ETSI_UMTS_AMR_2 are
selected.
Activated It is an optional parameter. In

ACTRATE general, the default value is
CODEC rate
selected
Supported It is an optional parameter. In

SUPRATE general, the default value is
CODEC rate
selected
ACS optimized
OM general, the default value is
mode
selected
Example: Configure an MGW encoding and decoding speech

template with the following requirements.
� Template ID: 1
� CODEC group number: 1
� Valid option: YES

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

� The encoding and decoding speech template is configured.
� The range of the topological node number is configured in the
resource management.
Context Perform this procedure to configure the topology relationship be-
tween MGCF node and IM-MGW node. This command is used to
configure the adjacent NE information, including equipment type,
bearer type and attributes, user plane version, encoding and de-
coding template, and other information.
For Mn interface, only the adjacent office bearing H.248 protocol
is configured as a topological node.
system tree.
SET:NEID=11;
2. Create an IM-MGW topological node. The command is ADD
TOPO.
Table 43 describes the main parameters in the ADD TOPO
command.

99
TABLE 43 PARAMETERS IN THE ADD TOPO COMMAND
Parameter Parameter
Instruction
Name Description
to define ID of this node,
Topological node ranging from 1 to 2,048.
ID
ID It is recommended that the ID
and office No. of a topological
node are consistent
for specifying the office ID of
this topological node. This
parameter must be defined by
OFCID Office ID the ADD ADJOFC command
first.
In this case, type the actual
IM-MGW office number
NAME Alias for naming this topological
node, with a length ranging
from 1 to 50 characters.
for specify the CODEC
template used by this
CODECID CODEC identity topological node. This
parameter must be defined
by the ADD CODECTPL
command first.
This parameter is used to

specify the NE type of this
ETYPE Equipment type topological node.
Select R4GW for an MGW
node
PROTTYPE Protocol type Select H.248 for Mn interface.
It is the IP protocol version

supported between nodes.
IP version of the Select IPV4 or IPV6
IPVER
node according to the actual
conditions. Currently, IPV4 is
supported.
This parameter is only valid

for the node with the type
of R4GW (MGW). The bearer
types supported by MGW
are BNCAAL1, BNCAAL2,
ATTR Bearer attributes BNCAAL1S, BNCIPRTP,
and BNCTDM. MGW can one
or more of these types of
bearers.
In general, select BNCAAL2,
BNCIPRTP, and BNCTDM


Name Description
This parameter is used to set
User plane the user plane version of
UPVER protocol version this node.
of RNC or MGW
In general, select V2
Extended
attributes (tunnel
mode), This parameter is used to set
including: which tunnel mode is adopted
� NOTUNL for bearer establishment when
(None tunnel this node supports the IP/RTP
ATTR2 mode) bearer. The default value is
NOTUNL (None tunnel
� RTUNL mode).
(Rapid tunnel In general, select DTUNL
mode) (Delay tunnel mode) for an
� DTUNL MGW topological node.
(Delay tunnel
mode)
Signaling transfer
mode, including: which mode is used by the
topology for reporting when
TRFMOD MCINTF (Mc it detects CNG or CED fax
interface signal signals.
transfer
The default value is MCINTF
mode)
Error SDU
control, including
options:
YES: The user
plane entity im-
plements error
inspection, and
sets the FQC bit
position accord-
ing to the result.
It will transmit
all frames in-
cludes the error
frames to the This parameter regulates the
user plane layer. handling method of the user
During a call, the plane for error frames. It is
UPERRCTRL error packet con- only valid for MGW-type and
trol parameter RNC-type topological node.
delerrsdu=Yes, The default value is YES
which is delivered
by the terminal
established by
MGW on the Mc
interface. The
error packet con-
trol parameter
deliveryOfErro-
neousSDU is YES,
NA, NA during
RAB assignment.
NO: The user
plane entity im-
plements the
error inspection.

101

Name Description
It will directly
discard the error
frame. During
a call, the er-
ror packet con-
trol parameter
delerrsdu=No,
which is delivered
by the terminal
established by
MGW on the Mc
interface. The
error packet con-
trol parameter
deliveryOfErro-
neousSDU is NO,
NA, NA during
RAB assignment.
INVALIDTION:
The user plane
entity does not
implement the
error inspection.
During a call, the
error packet con-
trol parameter
delerrsdu=NA,
which is delivered
by the terminal
established by
MGW on the Mc
interface. The
error packet con-
trol parameter
deliveryOfErro-
neousSDU is NA,
NA, NA during
RAB assignment.
Tandem office This parameter is used to set
send DTMF whether the tandem office
DTMFTC use TC mode, uses the TC resources during
including two DTMF number delivery.
options, NO
and The default value is NO
YES
It contains the following
options.
� SMGWCON (Standard
MGW congestion MGW congestion event)
MGWCON reporting
capability � CMGWCON (Custom MGW
congestion event).
SMGWCON.
Example: Create a topological node with the following require-

ments.
� MGW office ID: 101
� Equipment type: R4 gateway

� Protocol type: H248

� Supported user plane protocol version: V2
� CODEC ID: 1.
ADD TOPO:ID=101,OFCID=101,NAME="IM-MGW101",CO
DECID=1,ETYPE=R4GW,PROTTYPE=H248,IPVER=IPV4,A
TTR="BNCAAL2"&"BNCIPRTP"&"BNCTDM",UPVER="V2",ATT
R2=NOTUNL,TRFMOD=MCINTF,UPERRCTRL=YES,DTMFTC
=NO,MGWCON=SMGWCON,AUTOFAX=YES,OOBTC=NO,B
CUID=0,SENDCAP=NO,G711TRAN=NO,BICCDTMF=TRAN
SPARENT,IPBCP2833=BYMGW,BICCDTMPPER=0,AOIPPR
O=PRIVATE;
END OF STEPS

Creating Inter-MGW Bear Mode

� The MGW topological node is configured.
Context The inter-MGW bearer mode is configured when the Nb interfaces
between several IM-MGWs under the same MGCF are connected.
system tree.
SET:NEID=11;
2. Create the inter-MGW bearer mode. The command is ADD
MGWBEARMOD.
Table 44 describes the main parameters in the ADD MGWBE
ARMOD command.
TABLE 44 PARAMETERS IN THE ADD MGWBEARMOD COMMAND
Parameter Parameter
Instruction
Name Description
Type the gateway node ID
MGWPAIR MGW node pair configured in the topological
node configuration.
Bearer attribute
The parameter specifies the
ATTR between
bearer attribute between
MGWs, the
MGWs. Select RTP or TDM
options
include:

103

Name Description
AAL1(support
bncAAL1)
AAL2(support
bncAAL2)
AAL1S (support according to the type of Nb
interface bearer.
nbcAAL1Struct)
RTP (support
bncIPRTP)
TDM(support
bncTDM)
Type of
tone code AMRONLY represents the
between AMR encoding and decoding
CTYPE MGWs, mode is used only. When
the options G.711 and other encoding
including: and decoding modes are
allowed, select GENERAL
GENERAL
AMRONL
Y
“Adjacent office alias of
NAME Alias gateway 1-Adjacent office
alias of gateway 2”
AAL1 bearer The parameter specifies the

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

AAL2 rate (%) of the AAL2 bearer
type rate(%)
AAL1STRUCT The parameter specifies the
AAL1S bearer type rate (%) of the AAL1 STRUCT
rate(%) bearer between two
gateways
IPRTP bearer The parameter specifies the

RTP rate (%) of the IPRTP bearer
type
rate(%) between two gateways
TDM bearer type The parameter specifies the

TDM rate (%) of the TDM bearer
rate(%)
Top-priority
direct link
topology, the
DIRECT options include: The default is NO
NO;
YES


Name Description
User plane
mode for
multi-gateway
IP bearer,
the The default is
UPMODE options TRANSPARENT
include:
TRANSPAR-
ENT(transparent
mode)
SUPPORT(sup-
port mode)
Public IP The parameter is used to set
IPNET network domain the public IP network domain
index index (ADD IPDOMAIN)
G711 that is
forced to use
the transparent
G711TRAN mode. Options The default is NO
include:
NO;
YES
Example: Configure the bearer mode between two IM-MGWs
with the following requirements.
� MGW 1 node ID: 101
� MGW 2 node ID: 201
� Bearer mode: RTP
� Type of tone code between IM-MGWS: AMRONLY
� Encoding and decoding template ID: 1
� Alias: IM-MGW101-IM-MGW201
� Other parameters: default
value. The specific command is as
follows.
ADD
MGWBEARMOD:MGWPAIR="101"-"201",ATTR="RT
P",CTYPE=AMRONLY,AAL1=0,AAL2=0,AAL1S=0,RTP=10
0,TDM=0,DIRECT=YES,UPMODE=TRANSPARENT,NAME="I
M-MGW101-IM-MGW201",G711TRAN=NO;
Result E
After the
STEPS

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

Configuration Figure 52 shows the flow of SIGTRAN configuration.

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

configuration by following the procedure specified below.
Create an
association ADD SCTPC
1 Creating an SCTP
between two ONN
offices
Configure the
one-to-one
relationship
2 Creating an ASP between the ADD ASP
ASP and the
association.
ASP is one of
instances of AS.

107

Configure the
3 Creating an AS tag, user type, ADD AS
subsystem type
of AS
Configure
the mapping
Creating an M3UA relationship
4 between the ADD M3UART
static route
M3UA static
route and
the
AS.
Locate one
service to
Creating the a routing ADD SIOLO
5 table that
SIO-Locating-AS is CAS
maintained by
the ASP
under the AS.
SCTP Planning
The signaling carried by associations between MSCS and MGW is
as follows.
1. If the association bears the H248 signaling between MGCF
and IM-MGW, the H248/M3UA/SCTP bearer is adopted
usually, and the H248/SCTP bearer is supported.
2. The association bears the ISUP, TUP, and SCCP signaling
between MGCF and MSC/PSTN (MGW acts as an agent or
transfers the signaling). M3UA/SCTP adopts the (ISUP, TUP,
SCCP)/M3UA/SCTP bearer.
If the MTP3 direct-associated office does not exist on MGW,
the SCTP configuration is not required.
According to the rules regulated in SPC configuration rules, both
MGCF and IM-MGW adopts different combinations of signaling
points and network types for the three bearer modes mentioned
above. That is, an MGCF is configured with three adjacent offices
on IM-MGW, and one group of associations is configured between
every two adjacent offices for bearing different services.
The number of associations is related with the signaling network-
ing, equipment capacity, and configured SMP number. It is also
limited by the configuration. For example, an AS can be config-
ured with up to 16 SCTP associations.
Creating an SCTP
� The physical configuration of the SMP module is completed.

� The SCTP flag is configured in the resource management.

Context The SCTP connection is called as association, which is of one-to-
one correspondence with ASP. It can be equivalent to the com-
munication link used by the AS. An SMP can support up to 128
associations. When multiple BCTC shelves are configured, associ-
ations must share the load in each shelf.
system tree.
SET:NEID=11;
2. Create the SCTP connection. The command is ADD SCTPCO
NN.
Table 45 describes the chief parameters of the ADD SCTPC
ONN command.
TABLE 45 PARAMETERS IN THE ADD SCTPCONN COMMAND
Parameter Parameter
Instruction
Name Description
indicating the number of the
signaling module homed by this
SCTP association. Select the
MODULE Module No. SMP module number. Each SMP
can support up to 128
associations. The associations
under the same AS are required
sharing load on SMP modules as
more as possible.
designating the office No. of the
SCTP opposite direct-associated association.
OFCID
office ID Type the IM-MGW adjacent
office
No. specified in the adjacent
office configuration.
Bearer protocol
types,
including
� M2UA
� M2PA
� M3UA is used to identify the upper-
� SUA layer protocol type borne by the
PROT SCTP association. In general,
� H248 M3UA is selected. M2UA is
� BICC selected when IM-MGW
transfers the signaling with the
� IUA M2UA mode.
� DHCTRL
� SIP
� DIM

109

Name Description
� V5UA
� H245
SCTP application For Mn interface, MGCF is
attributes. configured as CLT, and IM-MGW
Options include:
is configured as SVR. For
ROLE SVR: SCTP is Nc interface, this should be
used as server negotiated by both sides. For
CLT: SCTP is example, the small signaling
used as client point serves as CLT, and the big
signaling point serves as SVR
designates the service address
of local end of this association,
with a format of Local IP
address type-VPN of local IP
address-Local IP address
LOCADDR Local IP address
Local IP address type: IPv4 and
IPv6
VPN of local IP address: Rang
from 0 to 65535
Local IP address: the format is
xxx.yyy.zzz.mmm
Local port is the local SCTP port number of
LOCPORT
number the association, ranging from 1
to 65535.
designates the service address
of remote end of this
association, with a format of
Remote
IP address type-VPN of
Opposite IP remote IP address-Remote
REMADDR
address IP address
Remote IP address type: IPv4
and IPv6
VPN of remote IP address: Rang
from 0 to 65535
Remote IP address: the format
is xxx.yyy.zzz.mmm
Opposite port is the opposite SCTP port
REMPORT
number number of the association,
It is a mandatory parameter with

NAME Alias a length ranging from 1 to 50
characters.
It is an optional parameter. It is
the global serial number of the
ID SCTP ID SCTP association, ranging from 1
to 2048. Configure it according
to the association planning.

Example: Create the SCTP connection for the Mn interface

� Bearer protocol: M3UA
� Application attribute: CLT
� SCTP signaling processing module number: 3
� Local port number: 2001
� Opposite port number: 2001
� Local IP address: 192.168.1.11
� Opposite IP address: 192.168.1.31
� SCTP association ID: 1
value. The command is as follows.
ADD
SCTPCONN:MODULE=3,OFCID=101,PROT=M3UA,R
OLE=CLT,LOCADDR="IPv4"-"0"-"192.168.1.11",LOCPORT
=2001,REMADDR="IPv4"-"0"-"192.168.1.31",REMPORT=2
001,NAME="IM-MGW101-1",ID=1,INSTRM=16,OUTSTRM
=16,MAXRTRY=5,MAXRTO=500,MINRTO=50,INITRTO=1
00,HB=500,FIXNH=NO,SCTPMAXRTRYNUM=10,DELAYA
CK=20,MAXBURST=4,PRIMARYPATH=REMIP1,PMTU=0,B
REAKTIME=0,PDTHRESH=0,MINCWND=0,PLTIMER=1
0,MPPLTHRD=2,DPLEN=MTU,CB=200;
END OF STEPS

Creating an ASP
� The SCTP association information configuration is completed.
� The range of the ASP configuration identification is configured
in the resource management configuration.
Context Perform this procedure to define the one-to-one relationship be-
tween the ASP and the association. ASP is one of instances of AS.
system tree.
SET:NEID=11;
2. Create an ASP. The command is ADD ASP.

111
Table 46 describes the main parameters in the ADD ASP

command.
TABLE 46 PARAMETERS IN THE ADD ASP COMMAND
Parameter Parameter
Instruction
Name Description
ASSOCID SCTP ID Type the association ID
configured in the SCTP
connection configuration.
with a lengthen ranging from
NAME Alias 1 to 50 characters. It may
be named with a format of
“Adjacent office alias-SCTP
number”.
ID ASP ID
It is recommended to be
consistent with ASSOCID.
used to set whether the ASP is
ISLOOP ASP self-loop ID self-looped.
Select the default value NO
used set whether the ASP is in
blocking state.
ISLOCK ASP blocking flag
Blocking is used for
management. Select the
default value NO
Example: Configure the ASP between MGCF and IM-MGW for

Mn interface with the following requirements.
� SCTP association ID: 1
� ASP configuration ID: 1
� User alias: MGW101-
1 The command is as
follows.
ADD
ASP:ASSOCID=1,NAME="
MGW101-1",ID=1,ISLOOP
Result =NO,ISLOCK=NO;
After the command is executed, the SUCCESS result is shown in
the
E NDExecute
OF STEPSResult column of the History Command pane.

Creating an AS
� The ASP configuration is finished.
Context The AS provides the transmission channels for upper-layer ser-
vices. For example, H248 and TUP/ISUP are different services.
They use different AS for transmission. The AS can use one or
more associations for communication.
system tree.
SET:NEID=11;
2. Create the AS. The command is ADD AS.
Table 47 describes the main parameters in the ADD AS com-
mand.
TABLE 47 PARAMETERS IN THE ADD AS COMMAND
Parameter Parameter
Instruction
Name Description
It indicates the protocol

type of a bearer. In
Supported general, M3UA is selected
PROT adaptation layer according to the
protocols networking planning. It is
configured as M2UA when
MGW transfers the
signaling with M2UA mode.
It is associated with the
ASPID ASP ID ASP ID configured in the
ASP configuration.
It is a mandatory
NAME Alias parameter. The alias
customized by the user.
It is an optional
parameter. It is the unique
identification of the AS. In
ID AS ID general, it is the same as
that of the ASP for easy
memory. The parameter
ranges from 1 to 640
EXISTCTX Whether the routing It is an optional parameter.

context ID exists The routing context is
unique in the network.
This parameter must
be consistent with the
CTXID Routing context ID AS configuration of the
opposite-end. Its default
value is NO

113

Name Description
For Mn interface, MGCF
generally serves as
IPSP_Client, and IM-MGW
serves as IPSP_Server.
Usage tag. Options When IM-MGW acts as a
include:
SGW, the AS at the MGCF
SGP side serves as ASP, and the
ASTAG AS at the SGW side serves
as SGP.
ASP
For Nc interface, this should
SRV (IPSP server) be negotiated by both
CLT (IPSP client) sides. For example, the
small signaling point serves
as IPSP_Client, and the big
signaling point serves as
IPSP_Server.
It defines the upper-layer
User types user types supported by
supported by AS. the AS. Currently, there are
ASUP Options include TUP, eight types of users.
ISUP, BICC, H.248,
ALCAP SCCP, PCA, User type is not configured
NNSF and ALL when IM-MGW transfers
the signaling with the M2UA
mode
Types of subsystem.
Options include
NO_SSN (subsystem
SSN excluded
(null)), SCCP, REV2
(standby), ISUP,
OMAP, MAP, HLR,
VLR, MSC, EIR, AUC,
REV11(standby),
INAP, USSD, VLRA,
SGSN_BSCAP,
RANAP, RNSAP, Types of subsystem
SSN GMLC_MAP, CAP, supported by application
GSMSCF_MAP, server (AS).
SIWF_MAP, SGSN_
MAP, GGSN_MAP,
IP (intelligent
peripherals),
SMC, SSP_SCP,
BSC_BSSAP_LE,
MSC_BSSAP_LE,
SMLC_BSSAP_LE,
BSS_O_M_A ,
BSSAP_A and
RVE255.


Name Description
The supported service
modes include:
� OVERRIDE (Over-ride
mode)
� LOAD (Load share
mode).
In the over-ride mode,
only one ASP is in the
ASMD Service modes activated statue. In this
supported case, only one ASP needs
be configured. In the load
sharing mode, N ASPs
should be configured in
the activated working
statue, and K ASPs should
be configured in the
deactivated standby statue.
The value of N+K is not
more than the number of
ASPs actually configured
The parameter ranges from
0 to 64.
The N+K should be equal to
The N value in load the number of ASP under
NVAL
sharing mode AS.
The N value indicates that
AS comes into service when
N ASPs are put into
service.
The parameter ranges from
0 to 63.
The N+K should be equal to
The K value in load the number of ASP under
KVAL AS.
sharing mode
The K value indicates that
AS is out of service when K
ASPs are used as standby
ASP.
Example: Configure the AS between MGCF and IM-MGW for

Mn interface with the following requirements.
� Supported adaptation layer protocol: M3UA
� AS configuration ID: 1
� Supported user type: H248
� ASP ID: 1
� Usage Tag: CLT
� Alias: H248

115
ADD AS:PROT=M3UA,ASPID="1",NAME="H248",ID=1,EX
ISTCTX=NO,ASTAG=CLT,ASUP="H248",ASMD=LOAD,NVA
L=1,KVAL=0;
END OF STEPS

Creating an M3UA Static Route

� The AS configuration is finished.
� The range of the M3UA static route identification is configured
in the resource management configuration.
Context Perform this procedure to configure the mapping relationship be-
tween the M3UA static route and the AS. An M3UA static route
can be used by up to 64 SIO-locating-ASs. Otherwise, configuring
more M3UA static routes is required.
system tree.
SET:NEID=11;
2. Create the M3UA static route. The command is ADD
M3UART. Table 48 describes the main parameters in the
ADD M3UART
command.
TABLE 48 PARAMETERS IN THE ADD M3UART COMMAND

Name Description
ID of M3UA indicating the serial number of the
ID M3UA static route ID, ranging from
static route
1 to 640. In general, it is the
same as the AS ID.
ASID AS ID corresponding to the AS ID
specified in the ADD AS command.
Nature: routes are directly sorted

Alignment according by the ASP marshalling
mode of sequence in the routing table.
MODE routes. Local: It is unnecessary to realize
Options the algorithm in the background.
include The background just needs to
BYTURN make the alignment according to
S, the Nature option.


Name Description
BYTURNS: in the routing table,
the routes at the odd-bit position
are sorted by the serial number of
LOCAL and the activated ASP, and the routes
NATURE. at the even-bit position are sorted
inversely by the serial number of
the activated ASP
The default is BYTURNS.
NAME Alias defined by a user, with a length
ranging from 1 to 50 characters.
Example: Create an M3UA static route for Mn interface with

the following requirements.
� M3UA static route ID: 1
� AS ID: 1
� User alias: IM-MGW101
ADD M3UART:ID=1,ASID=1,MODE=BYTURNS,NAME="IM
-MGW101";
END OF STEPS

Creating the SIO Locate AS

� The M3UA static route configuration is completed.
� The range of the SIO-locating-AS configuration ID is
configured in the resource management configuration.
Context The configuration of SIO-locating-AS is used to locate one service
to a routing table that is maintained by the ASP under the AS.
On MGCF, H248 protocol is generally configured between MGCF
and IM-MGW, and ISUP, TUP, and SCCP protocols are configured
between MGCF and other adjacent offices that are switched by
IM-MGW.
A routing key describes a set of No.7 signaling parameters and
parameter values. The corresponded AS is selected according to
the message attributes, thus to select a route for the message.

117
The message attributes include DPC+NET+OPC+SIO. The DPC

represents the destination SPC, the NET represents the network
type, OPC represents the original SPC, and the SIO represents
the service information octet.
system tree.
SET:NEID=11;
2. Create the SIO-locate-AS. The command is ADD SIOLOCAS.
Table 49 describes the main parameters in the ADD SIOLO
CAS command.
TABLE 49 PARAMETERS IN THE ADD SIOLOCAS COMMAND

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

Alias
is the alias customized by the
user
indicating the subscriber type
Service belonged by the transmitted
indication. message. Different user types can
Options be located to the same AS under
SIO include TUP, the precondition that the AS must
ISUP, BICC, support these user types.
H.248, ALCAP,
SCCP,PCA Select H.248 for Mn interface,
and NNSF BICC for Nc interface, and TUP or
ISUP for the 2G MSC/PSTN office
transferred through MGW.
indicating the adjacent office ID
Destination corresponded by the destination
OFCID adjacent office signaling point of the M3UA.
ID It needs to associate with the
adjacent office ID in the adjacent
office configuration.
It is the adjacent office ID
corresponding to the M3UA
originating signaling point. If
0 (indicating the local office) is
Original selected, it indicates that the
OPOFCID adjacent office message is sent from the local
ID office, and the routing context
is routed according to
DPC+NET+OPC+SIO. If 65535
(invalid) is selected, it
indicates
that the OPC field is invalid,
and


Name Description
the routing context is routed
according to DPC+NET+SIO
PCM system It is an optional parameter. It

PCM ranges from 0 to 65535, with a
number
default of 65535 (invalid).
It corresponds to the ID specified

ID 1 of M3UA in the M3UA static route
RT1 configuration. RT1 is a mandatory
static route
parameter. In general, RT1 is
required. When the optimum
route mode is adopted, RT1 is set
as an active route, and RT2 is set
as a standby route.
ID 2 of M3UA
RT2
static route
Example: Create SIO-locate-AS between MGCF and IM—MGW

� IM-MGW office ID: 101
� Destination adjacent office ID: 101
� Service indication: H248
� M3UA static route ID: 1.
ADD SIOLOCAS:ID=1,NAME="IM-MGW-
H248",SIO=H24
8,OFCID=101,OPOFCID=65535,PCM=65535,RT1=1,RT2
=0;
END OF STEPS

H.248 Configuration
Overview
Description H.248 protocol is used on Mn interface. It provides the following
functions.
� Under the control of MGC, it can establish, modify and release
the media channel in the MG, and can control the attributes of
bearer and user plane.
� It reports the events in the MG to the MGC.
� It maintains the office and terminal status between MGC and
MG.

119
Configuration Figure 53 shows the configuration flow of H.248 protocol.

Flow
FIGURE 53 CONFIGURATION FLOW
Flow Description The H.248 configuration procedures are as follows:
Creating MGC Cofigure the data

1 related to the ADD MGCSCFG
static data
MGCF and H.248.
Configure the
Creating an template used
2 MGW static data by the MGW ADD MGSTPL
template static data
configuration.
Configure the
Creating MGW static data for
3 ADD MGSCFG
static data each IM-MGW
under the MGCF.


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

� The data configuration of the local office is completed.
Context Perform this procedure to set the data related to the MSCS and
H.248.
system tree.
SET:NEID=11;
2. Create the MGC static data. The command is ADD MGCSCFG.
Table 50 describes the main parameters in the ADD
MGCSCFG
command.
TABLE 50 PARAMETERS IN THE ADD MGCSCFG COMMAND

Name Description
Select the supported MEGACO
MEGACO version version number, which must
MEGACO
number be consistent with that
negotiated with the MGW. The
default value is 1
Service activation It is an optional parameter,

ACTTM ranging from 0 to 3600, with
detection
timer(s) a default of 600

121

Name Description
ACTCHK Service activation It is an optional parameter,

detection switch being activated by default.
MGW answer It is an optional parameter,

WAITTM waiting timer ranging from 0 to 65535, with
(ms) a default of 7800
PEND retry It is an optional parameter,

PTRYNUM ranging from 1 to 255, with a
times(t)
default of 5
PEND retry time It is an optional parameter,

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

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

Creating MGW Static Data Template

Context Perform this procedure to set the template used by the MGW
static data configuration.
system tree.
SET:NEID=11;

2. Create an MGW static data template. The command is ADD

MGSTPL.
Table 51 describes the main parameters in the ADD MGSTPL
command.
TABLE 51 PARAMETERS IN THE ADD MGSTPL COMMAND

Name Description
This is a mandatory parameter

NAME Alias with a length ranging from 1 to
50 characters. It can be
consistent with the office name.
Static data
ID The number of a template,
template
number
MEGACO This parameter must be

MEGACO consistent with that negotiated
version number
with the MGW.
Gateway
ACTCHK activation It is configured as ON by default
detection switch
Transient
PRTTM It ranges from 1 to 180. Type
protection timer
the default value 10
(s)
Transient
PRT protection It is configured as ON by default.
switch
Interval of It ranges from 0 to 3600, with a

PENDTM PEND messages
default of 200
(ms)
Maximum
LNGTM It ranges from 0 to 65535, with
existence time
a default of 15000
(ms)
RTRNTM Retransmissio It ranges from 0 to 65535, with

n timer (ms) a default of 3800
Maximum
It ranges from 0 to 15, with a
MTRNNUM transmission
default of 1
times
� FIXED: Duration unchange-

Retransmissio able
TRNMD
n mode � UNFIXED: Duration change-
able
H.248 protocol It must be consistent with that

CTYPE negotiated with the MGW data
coding mode
configuration
Example: Add an MGW static data template with the following

requirements.

123
� Template ID: 1
� User name: IM-MGW101
value. The specific command is as
follows.
ADD MGSTPL:NAME="IM-
MGW101",MEGACO=1,ACTCHK
=ON,PRTTM=10,PRT=ON,PENDTM=200,LNGTM=15000,R
TRNTM=3800,MTRNNUM=1,TRNMD=UNFIXED,CTYPE=TE
Result XT;
the
E NDExecute Result column ofOF
the History Command pane. STEPS
Creating MGW Static Data

� The MGW static data template is configured.
� The MGCF voice batch processing is finished.
Context Perform this procedure to configure the static data for each IM-
MGW under the MGCF.
system tree.
SET:NEID=11;
2. Create MGW static data. The command is ADD MGSCFG.
Table 52 describes the main parameters in the ADD MGSCFG
command.
TABLE 52 PARAMETERS IN THE ADD MGSCFG COMMAND
Parameter Parameter
Instruction
Name Description
for configuring the node
number of this gateway,
ID Gateway number ranging from 1 to 2048. It is
associated with the node ID
specified by the ADD TOPO
command.
Static data It is a mandatory parameter

TPLID associated with the
template number
template number
configured on


Name Description
the IM-MGW static data
template configuration.
Service tone ranging from 0 to 65535.
TONEID It uses the template ID
template ID
specified in the BADD
STONE command.
Language ranging from 0 to 65535.
LANGID description It uses the template ID
template ID specified in the BADD
STONE command.
NAME Alias ranging from 0 to 50
characters. It may be the
same as the office name
BKMGC Backup MGC It is an optional parameter,

information with a default of NULL
Threshold of It is an optional parameter,

PKGLOST package loss rate ranging from 0 to 10000,
(0.01%) with a default of 10
Threshold of It is an optional parameter,

JIT network jittering ranging from 0 to 10000,
(ms) with a default of 50
Threshold of
DELAY ranging from 0 to 5000, with
network delay (ms)
a default of 200
for setting whether this
MGW MGW tandem MGW is used for the tandem
function. Type the default
value NO
Example: Create static data for an MGW with the following

requirements.
� Static configuration template ID: 1
� Alias: IM-MGW101
ADD MGSCFG:ID=101,NAME="IM-MGW101",TPLID=1,TO
NEID=1,LANGID=1,PKGLOST=10,JIT=50,DELAY=200,M
GW=NO;
END OF STEPS


125
Creating a TID Analyzer

Context The TID analysis configuration is necessary for the H.248 server
to perform the character string conversion of the CIC. The H.248
server converts the CIC on the server to the corresponding char-
acter string according to the mode configured by the TID
analysis. Then it sends this character string to the gateway's
H.248 for analyzing and operating the corresponded CIC. Since
the form of the terminals used by the Mn interface is relatively
fixed currently, you may adopt the default configuration.
system tree.
SET:NEID=11;
2. Create the TID analyzer. The command is ADD TIDANL.
Table 53 describes the main parameters in the ADD TIDANL
command.
TABLE 53 PARAMETERS IN THE ADD TIDANL COMMAND

Name Description
NAME ranging from 1 to 50
User alias
characters. It may be the
same as the office name.
It is the global number of
PREV TID analyzer index the current analyzer for
TID analyzer entry to use,
TIDPFX TID prefix It is an optional parameter

with a default of TDM
with a default of TRUNK
(trunk type).
Analysis result
flag. Options Example: “TDM_5/1” is a
include USER, trunk terminal form. “TDM”
TAG is the TID prefix, “_” is the
TRUNK, RTP,
ATM, ROOT and PCM separation mark, “5” is
PCM+IDX. the PCM number, "/” is the
IDX (time slot index) is the
separation mark, and “1” is
the time slot number


Name Description
PCMSPR PCM flag It is an optional parameter,

with a default of “ ”.
IDXSPR IDX flag It is an optional parameter,

with a default of “/”.
ranging from 0 to 255, with a
PCMPOS1 PCM start location default of 1, indicating that
the PCM number starts from
the first digit of the PCM flag.
PCMPOS2 PCM end location default of 0. Since there is a
PCM flag, the End Location is
meaningless.
IDXPOS1 IDX start location default of 1, indicating that
the time slot number starts
from the first digit of the IDX
flag.
ranging from 0 to 255, with
IDXPOS2 IDX end location a default of 0. Since there is
an IDX flag, the End Location
is meaningless.
Example: Create a TID analyzer with the following require-

ments.
� TID index: 1
value. The command is:
ADD TIDANL:NAME="IM-MGW101",PREV=1,TIDPFX="TD
M",TAG=TRUNK,PCMSPR="_",IDXSPR="/",PCMPOS1=1,P
CMPOS2=0,IDXPOS1=1,IDXPOS2=0;
END OF STEPS

Creating a TID Analysis Entrance


127
� The TID analyzer configuration is completed.

Context Perform this procedure to configure a TID analyzer entrance.
system tree.
SET:NEID=11;
2. Create a TID analysis entrance. The command is ADD TIDEN
TR.
TIDENTR
command.
TABLE 54 PARAMETERS IN THE ADD TIDENTR COMMAND

Name Description
It is a mandatory parameter. It is
ND Gateway the node ID allocated by the
topological node configuration.
TID analyzer associating the TID analyzer ID
TIDENTID
index specified in the TID analyzer
configuration.
By default, the system already

TID template creates a TID template whose ID is
TIDTPLID
number 1. You may query it with the
SHOW
TIDTPL command.
It is a mandatory parameter with
NAME a length ranging from 0 to 50
User Alias
characters. It may be the same as
the office name.
Example: Create a TID analyzer entry with the following re-

quirements.
� TID analyzer index: 1
� TID template ID: 1
ADD TIDENTR:ND=101,TIDENTID=1,TIDTPLID=1,NAME
="IM-MGW101";
END OF STEPS


Chapter
5
MGCF-SIP Office
Configuration
Table of Contents
Overview........................................................................ 129
SIPCC Data Configuration ................................................. 130
SIP Protocol Stack Configuration........................................ 141
Creating an RTP Trunk Group ............................................ 160
Overview
The configuration flow of MGCF-SIP office interconnection data is
shown in Table 55.
TABLE 55 FLOW DESCRIPTION
No. Operations Instructions

Including local office data
configuration, adjacent office
SIP call control data data configuration, SIP office
1 direction data configuration,
configuration
TOPO configuration, trunk data
configuration, and number analysis
data configuration
Including IP link data configuration,
host data configuration, adjacent
host data configuration, UDP bear
2 SIP protocol stack data configuration, SIP signaling
data data configuration, IP distribution
configuration policy data configuration, SIP
signaling route data configuration,
and SIP signaling route set data
configuration

129
SIPCC Data Configuration

Overview
This section introduces how to configure the signaling
interworking with the adjacent offices through the SIP protocol.
Create the IP
protocol stack for
the IP interface
over the SIP INTERFACE
1 Interface address protocol, and
configuration configure virtual ADD IP
interface address, ADDRESS
refer to Creating
a Virtual Interface
Address
Create the static
route for the IP
Creating a static interface over
2 ADD IP ROUTE
route the SIP protocol,
refer to Creating
a
Static Route
Create an
Creating a SIP adjacent office
3 connected with ADD ADJOFC
adjacent office
the MGCF through
SIP protocol
Create a SIP
Creating a SIP office office direction
4 connected with ADD SIPOFC
direction
the MGCF through
SIP protocol.
Create the
topology
Creating SIP relationship
5 adjacent office between MGCF ADD TOPO
topology node node and SIP
adjacent office
node
Creating a SIP Adjacent Office

� The exchange ID to be configured is known.
� The local office data configuration is completed.
� The adjacent office ID range is set in the Resource Manage-
ment system.

Chapter 5 MGCF-SIP Office Interconnection Data Configuration
Context This section introduces how to configure an adjacent office

connected with the MGCF through SIP protocol, which is I-CSCF,
S-CSCF, P-CSCF or BGCF in general.
system tree.
SET:NEID=11;
2. Create an adjacent office (such as CSCF or BGCF) connected
with the MGCF through SIP protocol by executing command
ADD ADJOFC.
The explanation of the main parameters in command ADD
ADJOFC is shown in Table 56.
TABLE 56 PARAMETERS FOR CREATING A SIP ADJACENT

OFFICE
Parameter Parameter
Instruction
Name Description
ID During the whole network
Office ID
planning, this parameter is
generally configured to
the adjacent office ID
NAME Alias It is a mandatory parameter,

defined by users
Select the network type
of the SPC used for the
connection between the
local office and the
adjacent
office when the local office
is configured with multiple
NET Network type signaling points. If the local
office is only configured
with only one signaling
point, the network type
of this signaling point is
selected by default. For the
adjacent office connected
with the MGCF through SIP
protocol, this parameter is
meaningless
SPCFMT Signaling Point Code TRIPLE_DEC is selected by

Format default
SPCTYPE Signaling Point Code Configure it according to the

type signaling point plan

131

Name Description
It is the SPC used for the
connection between the
local office and the
adjacent office. For the
DPC Signaling Point Code adjacent office connected
with the MGCF through
SIP
protocol, this parameter
needs not be configured and
is meaningless. Just enter a
non-zero value
Enter the code of the area
RC Area code where the adjacent office is
located. This parameter has
influence on the area code
added for the calling
number
Configure the adjacent
OFCTYPE Office Type office connected with the
MSCS through SIP protocol
to LOCAL&DOMTOLL&IP
Select
AM_SURE (associated
ASSOTYPE Association type mode), or AM_QUASI
(quasi-associated mode)
according to the networking
condition
Signaling point type, Select it according to the
SPTYPE including SEP, STP, role of the adjacent office in
and STEP the signaling network
including
� INTERNA-
TIONAL (Inter-
national signaling
point code)
� INTERNA-
TIONAL
STANDBY (Inter-
national standby It is an optional parameter.
SSF signaling point NATIONAL is generally
code) selected in China
� NATIONAL
(National
signaling point
code)
� NATIONAL
STANDBY
(National
standby
signaling point
code).


Name Description
Office Attribute,
including:
ISNI (Has ISNI
Function)
TRANS (Translate
Node)
TEST (Need Test
Info:0X02/0X01)
In general, select this
parameter, which is used to
TEST Test flag set whether the MTP3 link
actively initiates the link
test after going into service
status
message.
narrowband link message
BANDFLAG Broadband Attribute is 255. Because the MTP
the
causes the long packet to be
discarded.
links.
Protocol types,
including: CHINA and ITU are used
for the NO.7 signaling
� CHINA
networking of the ITU
(China) standards. ANSI is used for
PRTCTYPE � ITU (International the No.7 signaling
Telecommunica- networking of the American
tions Union) standards.
In general, national offices
� ANSI (American
select CHINA, while
National
international offices select
Standards
ITU
Institute).

133

Name Description
within 0~65535. In general,
select the default value
65535. It is valid when the
protocol type of the
CLST Cluster ID adjacent office is “ANSI”.
The signaling point
CIC_PCM (CIC starts
the load sharing
code mode)
BLOCK (Manual block
status)
EVEN_CIC (The
office controls the It is an optional parameter
INFO even CIC when CIC and the default value is
resource contention CIC_PCM
occurs)
CALLING (Calling
CALLED (Called
MOD24_CIC (CIC
mode with 24 mode)
TEST (Dynamic
observation)
Related Office ID
Office Extend Info,
including:
� SIGBRDCST
(Support Signa
ling Broadcast
Message)
� MTP (Hongkong
MTP Standard)
INFOEX � DUPU ( Screen It is an optional parameter
DUPU message)
�
SUA_REC_DT1
(Receive SUA
message and
handle it as DT1
message)
�
SUA_SND_DT1
(Send SUA
message and
handle it as DT1


Name Description
message without
SN.)
�
OPEN_TG_RES
(Open outter
trunk group
resource)
For example, add the S-CSCF. The office ID is 12, the office
type is LOCAL&DOMTOLL&IP, the signaling point code type
is 24, the signaling point code is 3.12.1, the area code is 25,
the association type is AM_SURE, the signalng point type is
SEP. For the other parameters, adopt the default value. The
command is as follows:
ADD ADJOFC:ID=12,NAME="SCSCF",NET=1,OFCTYPE="L
OCAL"&"DOMTOLL"&"IP",SPCFMT=TRIPLE_DEC,SPCTYPE=2
4,DPC="3.12.1",RC="25",ASSOTYPE=AM_SURE,SPTYPE
=SEP,SSF=NATIONAL,SUBPROTTYPE=DEFAULT,TEST=YE
S,BANDFLAG=YES,PRTCTYPE=CHINA,CLST=65535,INFO
="CIC_PCM",RELATEDOFC1=0;
END OF STEPS

Creating SIP Office Direction

� The local office data is configured.
� The SIP adjacent office is configured.
Context This section introduces how to create a SIP office direction con-
nected with the MGCF through SIP protocol.
system tree.
SET:NEID=11;
2. Create a SIP office direction. The command is ADD SIPOFC.
Table 57 describes the main parameters in the ADD SIPOFC
command.

135
TABLE 57 PARAMETERS IN THE COMMAND ADD SIPOFC

Name tion
It is a mandatory pa-
rameter, ranging from
OFCID Office ID 1 to 3000. Adopt the
SIP adjacent office ID
configured in the ADD
ADJOFC command
URL type, includes
� TEL: TEL format It is an optional param-
URL eter with a default value
� URI: SIP URI URI
format
� IP: SIP IP format
MGCF Charging Mode,
includes It is an optional param-
BTYPE eter with a default value
� IN: Inner Bill IN
� Rf: Rf Bill
ENOPT Select SIP ESSO&SIP

Enable Option
PRECOND
Example: Create a S-CSCF SIP office with the following re-

quirements.
� SIP office ID: 12
� URL type: URI
� MGCF charging mode: IN
� Enable option: SIP ESSO& SIP
PRECOND The specific command is as
follows.
ADD
SIPOFC:OFCID=12,URL=URI,BYPASS=NO,BYPASS
PCT=80,BYPASSPRD=5,BYPASSTLEN=30,BYPASSLEV=L
N,BYPASSCALLNUM=1,BTYPE=IN,OVERLAP=RINVT,CFIN
FO=HIS,PBRTFMT=EQUAL,DTMF=IN,FMT4733=97,SIPRE
L=NO,ENOPT="SIP ESSO"&"SIP PRECOND";
Result E
After the
STEPS
Creating SIP Adjacent Office

Topology Node
� The encoding and decoding speech template is configured.

� The range of the topological node number is configured in the

resource management.
Context Perform this procedure to create the topology relationship
between MGCF node and SIP adjacent office node. This
command is used to configure the adjacent NE information,
including equipment type, bearer type and attributes, user plane
version, encoding and decoding template, and other
Steps
information.
system tree.
SET:NEID=11;
2. Create a SIP adjacent office topology node. The command is
ADD TOPO.
command.
TABLE 58 PARAMETERS IN THE ADD TOPO COMMAND
Parameter Parameter
Instruction
Name Description
to define ID of this node,
Topological node ranging from 1 to 2,048.
ID
ID It is recommended that the ID
and office No. of a topological
node are consistent
for specifying the office ID of
this topological node. This
OFCID Office ID
the ADD ADJOFC command
first.
In this case, type the actual
IM-MGW office number
NAME Alias for naming this topological
node, with a length ranging
from 1 to 50 characters.
for specify the CODEC
template used by this
CODECID CODEC identity topological node. This
by the ADD CODECTPL
command first.

137

Name Description
specify the NE type of this
ETYPE Equipment type topological node.
Select R4GW for an MGW
node
PROTTYPE Protocol type Select H.248 for Mn interface.
It is the IP protocol version
IP version of the Select IPV4 or IPV6
IPVER
node according to the actual
conditions. Currently, IPV4 is
supported.
of R4GW (MGW). The bearer
types supported by MGW
are BNCAAL1, BNCAAL2,
ATTR Bearer attributes BNCAAL1S, BNCIPRTP,
and BNCTDM. MGW can one
or more of these types of
bearers.
In general, select BNCAAL2,
BNCIPRTP, and BNCTDM
User plane the user plane version of
UPVER protocol version this node.
of RNC or MGW
In general, select V2
Extended
attributes (tunnel
mode), This parameter is used to set
including: which tunnel mode is adopted
� NOTUNL for bearer establishment when
(None tunnel this node supports the IP/RTP
ATTR2 mode) bearer. The default value is
NOTUNL (None tunnel
� RTUNL mode).
(Rapid tunnel In general, select DTUNL
mode) (Delay tunnel mode) for an
� DTUNL MGW topological node.
(Delay tunnel
mode)
Signaling transfer
which mode is used by the
mode, including:
topology for reporting when
TRFMOD MCINTF (Mc it detects CNG or CED fax
interface signal signals.
transfer
The default value is MCINTF
mode)


Name Description
Error SDU
control, including
options:
YES: The user
plane entity im-
plements error
inspection, and
sets the FQC bit
position accord-
ing to the result.
It will transmit
all frames in-
cludes the error
frames to the
user plane layer.
During a call, the
error packet con-
trol parameter
delerrsdu=Yes,
which is delivered
by the terminal
established by
MGW on the Mc
interface. The
error packet con-
trol parameter
deliveryOfErro-
neousSDU is YES, This parameter regulates the
NA, NA during handling method of the user
RAB assignment. plane for error frames. It is
UPERRCTRL
NO: The user only valid for MGW-type and
plane entity im- RNC-type topological node.
plements the The default value is YES
error inspection.
It will directly
discard the error
frame. During
a call, the er-
ror packet con-
trol parameter
delerrsdu=No,
which is delivered
by the terminal
established by
MGW on the Mc
interface. The
error packet con-
trol parameter
deliveryOfErro-
neousSDU is NO,
NA, NA during
RAB assignment.
INVALIDTION:
The user plane
entity does not
implement the
error inspection.
During a call, the
error packet con-
trol parameter
delerrsdu=NA,
which is delivered

139

Name Description
by the terminal
established by
MGW on the Mc
interface. The
error packet con-
trol parameter
deliveryOfErro-
neousSDU is NA,
NA, NA during
RAB assignment.
Tandem office This parameter is used to set
send DTMF whether the tandem office
DTMFTC use TC mode, uses the TC resources during
including two DTMF number delivery.
options, NO
and The default value is NO
YES
It contains the following
options.
� SMGWCON (Standard
MGW congestion MGW congestion event)
MGWCON reporting
capability � CMGWCON (Custom MGW
congestion event).
SMGWCON.
Example: Create a topological node with the following require-

ments.
� Equipment type: R4 gateway
� Protocol type: H248
� Supported user plane protocol version: V2
� CODEC ID: 1.
ADD
TOPO:ID=12,OFCID=12,NAME="SCSCF",CODECID
=1,ETYPE=MSCVLR,PROTTYPE=SIP,IPVER=IPV4,ATTR
="BNCIPRTP",ATTR2=NOTUNL,TRFMOD=MCINTF,UPERRCT
RL=YES,DTMFTC=NO,MGWCON=SMGWCON,AUTOFAX=YE
S,OOBTC=NO,BCUID=0,SENDCAP=NO,G711TRAN=NO,BI
CCDTMF=TRANSPARENT,IPBCP2833=BYMGW,BICCDTMP
PER=0,AOIPPRO=PRIVATE;
Result END OF STEPS


SIP Protocol
Stack
Configuration
Overview
When the MSCS serves as a MGCF, after the local office data con-
figuration is completed, it is required to add the basic SIP config-
uration, including the following contents.
Create an IP
1 Creating an IP link bearer link used ADD IPLINK
for SIP signaling.
Configure the
Setting the capacity for a SIP
2 capacity for a module SET SIPCAPA
SIP module according to the
system capacity
Creating a domain Creating the
3 where the MGCF domain of MGCF ADD REALM
belongs system
Creating MFCF
Creating a MGCF
4 host name, type ADD HOST
host
and IP address
A routing selector
is a set of multiple
number analyses,
Creating route used to store
5 the analyses ADD RTSEL
selector
of MSISDN, IP
numbers and
domain addresses
in the IMS
domain
Service groups are
Creating a service used to specify
6 ADD SRVG
group the routing
selector for a
number.
Create an
Creating an adjacent host
7 ADD ADJHOST
adjacent host (CSCF or BGCF)
of the MGCF.
Create two modes

8 of UDP bear: ADD UDPBR
Creating UDP bear
LOCAL_VALID and
REMOTE_VALID

141

For the adjacent
office
Creating a SIP connected with
9 the MGCF ADD SIPLNK
signaling link
through SIP, it
is required to
configure SIP
signaling links.
Create signaling
routes. Each SIP
Creating a SIP signaling route
10 ADD SIPRT
signaling route contains at most
12 SIP signaling
links.
Create signaling
route sets. Each
Creating a SIP SIP signaling
11 ADD SIPRTS
signaling route set route set contains
at most 4 SIP
signaling routes.
When the MGCF
can be configured
with multiple IP
Creating IP addresses, the SIP
12 on each IP needs ADD IPDPLC
Distribution Policy
to be distributed
to different
signaling SMP
modules for
processing.
The URI analysis
Creating URI is used to analyze
13 ADD URI
analysis domain names
on routes.
Creating an IP Link
� The SIP adjacent office is created.
� The SMP module with SIP attribute is added.
Context This section introduces how to create an IP bearer link used for
SIP signaling. Different bearer information is configured for
different peer-end addresses.
system tree.
SET:NEID=11;

2. Create an IP link used for SIP signaling transfer by executing

command ADD IPLINK.
IPLINK is shown in Table 59.
TABLE 59 PARAMETERS IN THE ADD IPLINK COMMAND

Name Description
Peer-end Enter ID of the adjacent office
OFCID adjacent office connected with this link, which is
ID associated with the adjacent office
ID configured in the adjacent
office configuration
is the No. of the SMP module
MODULE Module No. where the Socket associated with
the IP link belongs, which should
be consistent with MODULE in
command ADD MODULE
It is a mandatory parameter, which

ID IP link ID is an integer, ranging from 1 to
1024. It is used to identify an IP
link. It cannot be repeated
It is a mandatory parameter. Input

the IP address of the local end of
LOCIP Local IP this link, in the format of “Local IP
type-Local IP VPN-Local IP
address”. At present, the IPV4
address type is used in general
LOCPORT Local port No. It is usually set to 5060
It is a mandatory parameter. Input

the IP address of the peer end of
this link, in the format of “Peer-
REMIP Peer-end IP end IP address type-Peer-end IP
address VPN-Peer-end IP address”.
At present, the IPV4 address type
is used in general
REMPORT Peer-end port It is usually set to 5060

No.
It is the transfer protocol type

Transfer used by this link, which can be set
PRO to TCP or UDP. The transfer
protocol type
protocol type should be consistent
with that used by the peer-end IP
link
If the PRO is configured as TCP,
TCP this option can set the local end
TCPROTO connection as the CLT (client) or the SVR
type (server) of the TCP. If the PRO
is configured as UDP, it is not
required to configure this option

143

Name Description
Duration (ms)
TSTIMER If it is not required to test the link,
of the link test set it to 0
timer
Example: Create a bearer link between the MGCF and the S-

CSCF with the following requirements.
� S-CSCF office ID: 12
� No. of the SMP module managing this link: 3
� User alias: IPLINK-12
� IP link ID: 12
� Local IP: 10.1.44.77
� Peer-end IP: 10.1.33.11
� Local port No. and peer-end port No.: 5060
� Transfer protocol type: UDP
� Other parameters: Adopt the default
values. The command is:
ADD IPLINK:OFCID=12,MODULE=3,NAME="IPLINK-12",I
D=12,LOCIP="IPv4"-"0"-"10.1.44.77",LOCPORT=5060,RE
MIP="IPv4"-"0"-"10.1.33.11",REMPORT=5060,PRO=UDP,T
CPROTO=NULL,TSTIMER=0;
END OF STEPS

Setting the Capacity for a SIP

Module
� The exchange ID to be configured is given.
� The SMP module with SIP attribute is added.
Context This section introduces how to set the capacity for a SIP module
according to the system capacity.
system tree.
SET:NEID=11;
2. Set the capacity for the SIP module by executing command
SET SIPCAPA.

The explanation of the main parameters in command SET

SIPC APA is shown in Table 60.
TABLE 60 PARAMETERS IN THE SET SIPCAPA COMMAND
Parameter Parameter
Instruction
Name Description
SIP SOCKET data which is an integer, ranging
SIPSOCKET from 1 to 1024. It is
area capacity
configured according to the
system capacity
SIP TR data area which is an integer, ranging
SIPTR from 1 to 30000. It is
capacity
system capacity
SIP TU data area which is an integer, ranging
SIPTU from 1 to 15000. It is
capacity
system capacity
SIP TUMSG data which is an integer, ranging
SIPTUMSG from 1 to 7000. It is
area capacity
system capacity
Example: Set the capacity for the SIP module with the follow-
ing requirements.
� SIP SOCKET data area capacity: 128
� SIP TU data area capacity: 15000
� SIP TU data area capacity: 9000
� SIP TUMSG data area capacity:
4000 The command is as follows.
SET SIPCAPA:SIPSOCKET=128,SIPTR=15000,SIPTU=90
00,SIPTUMSG=4000;
END OF STEPS

Creating a Domain where the MGCF

Belongs

145

Context The MGCF system can be configured with one or more domains.
In general, it is configured with one domain.
system tree.
SET:NEID=11;
2. Create a domain by executing command ADD REALM.
REALM is shown in Table 61.
TABLE 61 PARAMETERS IN THE ADD REALM COMMAND
Parameter Parameter
Instruction
Name Description
It is an integer, ranging from 1

ID Domain ID to 65534. In general, the MGCF
is configured with one domain
whose ID is set to 1
consisting of 1 to 63 characters.
REALM Domain name When the host name is set, it
is required to add the domain
name of the host after it
Example: Add a domain with the following requirements.

� Domain ID: 1
� Domain name:
zte.com The command is
as follows.
ADD
REALM:ID=1,REALM="zte
Result .com";
the
E NDExecute
OF STEPSResult column of the History Command pane.
Creating a MGCF Host

Context The host name of the local office must be configured when the
SIP function is used. The MGCF can have one or more hosts, and
each host belongs to one domain. When SIP messages are sent,
the host information is used to construct the parameter contents
in messages “From” and “Contact”.


system tree.
SET:NEID=11;
2. Create a MGCF host by executing command ADD HOST.
HOST is shown in Table 62.
TABLE 62 PARAMETERS IN THE ADD HOST COMMAND
Parameter Parameter
Instruction
Name Description
It is the ID of this host, which is an

ID Host ID integer, ranging from 1 to 65534.
It can not be repeated
The host name is composed of
HOST Host name short description and domain
name. For example, a host name
is host1.zte.com, where zte.com is
the domain name
IPV4 IPV4 IPV4 address of this host
IPV6 IPV6 IPV6 address of this host
Example: Add a host with the following requirements.

� Host ID: 1
� Host name: host1.zte.com
� IPV4 address:
11.11.11.1. The command is:
ADD HOST:ID=1,HOST="host1.zte.com",IPV4="11.11.11.
1";
END OF STEPS

Creating Route Selector

Context To implement the MGCF function, SIP routing selectors must be
configured. A routing selector is a set of multiple number
analyses, used to store the analyses of MSISDN, IP numbers
and domain

147
addresses in the IMS domain. In general, one routing selector is

configured.
system tree.
SET:NEID=11;
2. Create a SIP routing selector by executing command ADD
RTSEL.
RTSEL is shown in Table 63.
TABLE 63 PARAMETERS IN THE ADD RTSEL COMMAND
Parameter Parameter Description Instruction

Name
It is a mandatory
ID SIP route selector ID parameter, which is
an integer, ranging
from
1 to 65534
It is a mandatory
parameter, consisting
SIP routing selector of 0~50 characters.
NAME
name It is
used to specify a routing
selector to make it easily
recognized
Example: Create a SIP route selector with the following re-
quirements.
� SIP route selector ID: 1
� SIP route selector name:
RTS1. The command is:
ADD RTSEL:ID=1,
NAME="RTS1";
END OF STEPS
Creating Service Group

� The routing selector is added.
Context Service groups are used to specify the routing selector for a num-
ber. Service groups are used by SIP signaling links and entry
poli-

cies. If more service groups are needed, add new service groups
after setting the default service group.
system tree.
SET:NEID=11;
2. Creating a service group by executing command ADD SRVG.
SRVG is shown in Table 64.
TABLE 64 PARAMETERS IN THE ADD SRVG COMMAND
Parame- Parameter Instruction

Service It is the service group ID, which is an

ID integer, ranging from 1 to 65534. It is
group ID
numbered from 1
Service
NAME consisting of 1~50 characters. It is
group name
used to specify a service group
Routing Enter the routing selector ID, which

RTSEL is associated with the ID in command
selector ADD RTSEL
CHGID Charge Policy It is an integer, ranging from 1 to

Index 65535
Inter
It is an optional parameter, consisting
IOI Operator
of 0~63 characters.
Identifier
Example: Create a service group with the following require-

ments.
� Service group ID: 1
� Corresponding route selector ID of the service group:
1
� The service group is not associated with the billing
policy. The command is:
ADD SRVG:NAME="SRVG1",ID=1,RTSEL=1;
END OF STEPS
Creating an Adjacent Host


149

Context This section introduces how to create an adjacent host (CSCF or
BGCF) of the MGCF. Multiple adjacent hosts can belong to the
same adjacent office. Each SIP signaling link corresponds to one
adjacent host of the MGCF, and it refers to the host ID of the
adjacent host.
system tree.
SET:NEID=11;
2. Create an adjacent host by executing command ADD ADJHO
ST.
ADJHOST is shown in Table 65.
TABLE 65 PARAMETERS IN THE ADD ADJHOST COMMAND
Parameter Parameter
Instruction
Name Description
It is the ID of the adjacent

Adjacent host office where the adjacent host
ID belongs, which is consistent
ID
with the ID in command ADD
ADJOFC.
It should be consistent with that
of the peer end. The host name
HOSTNAME Host name is composed of short
description and domain name.
For example, a host name is
scscf.zte.com, where zte.com is
the domain name
It consists of 0 to 63 characters.
It is the name of the domain
REALM Domain name where the adjacent host
belongs, which should be
consistent with that of the peer
end
If the URL in ADD SIPOFC
is not configured as URI, this
Service Group option can be set to the default
SRVGRP service group number. If URL
Number
in ADD SIPOFC is configured
as URI, selected the related
service group number
Example: Create a SCSCF adjacent office with the following

requirements.
� Adjacent host name: SCSCF
� Adjacent host ID: 12

� Name of the domain where the host belongs: zte.com

� Topology level: UPPER
� Service group
number: 1 The command is:
ADD ADJHOST:ID=12,HOSTNAME="SCSCF",REALM="zte.
com",SRVGRP=1;
END OF STEPS

Creating UDP Bear

Context This section introduces how to create a UDP bear. Two modes of
UDP bear are required to be configured. LOCAL_VALID mode of
UDP bear is for relating the local UDP bear ID in ADD IPDPLC
command. REMOTE_VALID mode of UDP bear is for relating the
remote UDP bear ID in ADD SIPLNK command.
system tree.
SET:NEID=11;
2. Create UDP bear. The command is ADD UDPBR.
UDPBR is shown in Table 66.
TABLE 66 PARAMETERS IN THE ADD UDPBR COMMAND

Name Description
It is a mandatory
ID Bear ID parameter to define
bear ID, ranging from
1 to 65,535.
It is an optional
parameter for naming
NAME Alias the bear, with a length
characters.

151

Name Description
UDP IP Mode, includes

� LOCAL_VALID: The default value is
IPMODE Local IP valid LOCAL_VALID.
� REMOTE_VALID:
Remote IP valid
Select the adjacent

ADJHOST Adjacent Host host ID configured in
ADD ADJHOST
Select the IP link ID

IPLINK IP Link ID configured in ADD
IPLINK
Destination IP Address
Type, includes
DSTADDRTYPE � IPV4: IPV4 addres Currently, IPV4 is

type supported.
� IPV6: IPV6 addres
type
DSTV4ADDR Destination IPV4 Destination IPV4

address
DSTVPN Destination VPN ID Destination VPN ID
DSTPORT Destination port Destination port
Example, Create a UDP bear with the following requirements.

� Bear ID: 1
� Alias: LOCAL
� UDP IP Mode: LOCAL_VALID
ADD UDPBR:ID=1,NAME="LOCAL",IPMODE=LOCAL_VALI
D,ADJHOST=0,IPLINK=12,DSTADDRTYPE=IPV4,DSTVPN
=0,DSTPORT=0;
Example, Create a UDP bear with the following requirements.
� Bear ID: 2
� Alias: REMOTE
� UDP IP Mode: REMOTE_VALID
ADD UDPBR:ID=2,NAME="REMOTE",IPMODE=REMOTE_V
ALID,ADJHOST=12,IPLINK=0,DSTADDRTYPE=IPV4,DSTV
4ADDR="10.1.33.11",DSTVPN=0,DSTPORT=5060;
END OF STEPS


Creating a SIP Signaling Link

� The adjacent host is added.
Context Signaling links are the physical channels bearing signaling mes-
sages. For the adjacent office connected with the MGCF through
SIP, it is required to configure SIP signaling links.
system tree.
SET:NEID=11;
2. Create a SIP signaling link by executing command ADD SIPL
NK.
SIPLNK is shown in Table 67.
TABLE 67 PARAMETERS IN THE ADD SIPLNK COOMMAND

It is the SIP signaling link ID,

which is an integer, ranging
ID Signaling link ID from 1 to 65534. It is referred
to in the SIP signaling route
configuration
NAME Signaling link
consisting of 0~50 characters. It
name
is the SIP signaling link name
is the IP link ID associated with
BRID Bearer ID this SIP signaling link, which
is consistent with the ID in
command ADD IPLINK
It is the interval of sending link

heartbeat test messages, used
Sending Heart to test the link connection. It
HBTIME
Beat Interval(s) ranges from 0 to 3600 (s). If this
option is set to 0, means disable
heartbeat monitor.
Example: Create a SIP signaling link with the following

requirements.
� Link ID: 12
� Link name: SCSCFLINK

153
� Bear ID: 2
� Adjacent office connected with this link: S-
CSCF The command is:
ADD SIPLNK:ID=12,NAME="SCSCFLINK",BRID=2,HBTIM
E=0,NORMALHBTIME=120,UNUSECNT=3,USECNT=3;
END OF STEPS

Creating a SIP Signaling Route

� The SIP signaling link is configured.
Context For the adjacent office connected with the MGCF through SIP, it
is required to create signaling routes. Each SIP signaling route
contains at most 12 SIP signaling links.
system tree.
SET:NEID=11;
2. Create a SIP signaling route by executing command ADD
SIPRT.
SIPRT is shown in Table 68.
TABLE 68 PARAMETERS IN THE ADD SIPRT COMMAND
Parame-
Parameter
ter De- Instruction
Name
scription
It is the SIP signaling route ID, which

ID Route ID is an integer, ranging from 1 to
65534. It is referred to in the SIP
signaling route group configuration
Route It is a mandatory parameter,

NAME consisting of 0~50 characters. It is
name the SIP signaling route name
It is a mandatory parameter. It is the

Link policy for selecting SIP links managed
SPLC selecting by the signaling route. It can be
policy configured to SEQ and RND. SEQ
indicates that links are selected based

Parameter Parame-
ter De- Instruction
Name
scription
on priority, while RND indicates that
links are selected based on order
It is a mandatory parameter. It is the

ID of the SIP signaling link managed
Signaling by the SIP signaling route. It is
LNK consistent with the ID in command
link ID
ADD SIPLNK. One SIP signaling
route can be configured with at most
12 links
Example: Create a SIP signaling route with the following re-

quirements.
� Route ID: 12.
� Signaling route name: SCSCFR
� Link selecting policy: SEQ
� Signaling link ID:
12 The command is:
ADD
SIPRT:ID=12,NAME="SCSCFR",SPLC=SEQ,LNK="1 2";
END OF STEPS

Creating a SIP signaling Route Set

� The SIP signaling route is configured.
Context For the adjacent office connected with the MGCF through SIP, it is
required to create signaling route sets. Each SIP signaling route
group contains at most 4 SIP signaling routes.
system tree.
SET:NEID=11;
2. Create a SIP signaling route set by executing command ADD
SIPRTS.
SIPRTS is shown in Table 69.

155
TABLE 69 PARAMETERS IN THE ADD SIPRTS COMMAND
Parame- Parameter
Instruction
ID Route group ID from 1 to 65534. It is the
SIP signaling route group ID,
which cannot be repeated in
the system
NAME Route group name consisting of 0~50 characters.
It is the SIP signaling route
group name
Route Select Policy,
includes
RTPLC
� SEQ: with a default value of SEQ
Sequential
� PCT: Percent
It is the ID of the SIP
signaling route managed by
the SIP signaling route group.
SIPRT Route ID It
is consistent with the ID in
command ADD SIPRT. One
SIP signaling route group can
be configured with at most 4
routes
Example: Create a SIP signaling route group with the

� Route ID: 12
� Signaling route group name: SCSCFRS
� Route Select Policy: Sequential
� Route group ID:
12. The command is:
ADD SIPRTS:ID=12,NAME="SCSCFRS",RTPLC=SEQ,SIPR
T="12"-"0";
END OF STEPS

Creating IP Distribution Policy

� The number of exchange to be configured is known.
� The SIP access address is configured.

�The MML Terminal window is opened.

Context When the MGCF can be configured with multiple IP addresses, the
SIP on each IP needs to be distributed to different signaling SMP
modules for processing. The IP distribution policy implements the
service allocation of the signaling SMP module processing SIP.
system tree.
SET:NEID=11;
2. Create IP distribution policy by executing command ADD
IPDP LC.
IPDPLC is shown in Table 70.
TABLE 70 PARAMETERS IN THE ADD IPDPLC COMMAND
Parameter Parameter
Instruction
Name Description
ID IP distribution It is an integer, ranging from 1

policy ID to 65535
IP distribution consisting of 1~50 characters.
NAME
policy name It is the IP distribution policy
name
It is the IP address type of the

local office, which can be set to
IPV4 or IPV6. When it is set
ADDRTYPE IP address type to IPV4, configure the IPV4
subnet and subnet mask. When
it is set to IPV6, configure the
IPV6 subnet and subnet mask
It is the subnet number of the

IPV4 address of the local office.
V4NET IPV4 subnet When ADDRTYPE is set to
IPV4, the IPV4 address needs
to be configured
It is the subnet number of the

V6NET IPV6 subnet When ADDRTYPE is set to
IPV6, the subnet number of
the IPV6 address needs to be
configure
It is the subnet mask of the

V4MSK IPV4 subnet mask When ADDRTYPE is set to
IPV4,, the subnet mask of the
IPV4 address needs to be
configure
It is the subnet mask of the

V6MSK IPV6 subnet mask IPV6 address of the local office.
When ADDRTYPE is set to

157

Name Description
IPV6, the subnet mask of
the IPV6 address needs to be
configure
Distribution
policies of UDP,
including:
DEF: Default
distribution
UPLC Selct PRIROR or LOAD-
PRIROR: SHARE, DO NOT select DEF.
Excellent choice
priority
LOADSHARE:
Load share
priority
UDPID UDP Bear ID Select the Bear ID configured

in ADD UDPBR command
Example: Create an IP distribution policy with the following

requirements.
� IP distribution policy name: MGCF11
� IP distribution policy ID: 1
� The local office uses the IPV4 address
� IPV4 subnet: 10.1.33.11
� IPV4 subnet mask: 255.255.255.0
� UDP distribution policy: Excellent choice priority
� UDP Bear
ID: 1 The
command is:
ADD IPDPLC:ID=1,NAME="MGCF11",ADDRTYPE=IPV4,V
4NET="10.1.33.11",V4MSK="255.255.255.0",PORT=0,UPL
C=PRIROR,UDPID="1";
END OF STEPS
Creating URI Analysis

� The number of exchange to be configured is known.
� The outgoing SIP signaling route group is added.
� The routing selector is added.

Context The URI analysis is used to analyze domain names on routes. Dif-
ferent URI numbers can be analyzed to different results.
system tree.
SET:NEID=11;
2. Create URI analysis by executing command ADD URI.
URI
is shown in Table 71.
TABLE 71 PARAMETERS IN THE ADD URI COMMAND

Name tion
It is a mandatory
parameter, which should
RTSEL Routing selector be consistent with the
ID in command ADD
RTSEL
It is a mandatory
Uniform Resource parameter, consisting
URI of 1~50 characters. It
Identifier
is the analyzed domain
name
SIP methods, including

� ACK
� BYE
� CANCEL
� INFO
� INVITE
� MESSAGE It is a mandatory
parameter. In general,
METHOD � NOTIFY it is configured to ACK,
BYE, CANCEL, INVITE,
� OPTIONS PRACK, or UPDATE
� PRACK
� PUBLISH
� REFER
� REGISTER
� SUBSCRIBE
� UPDATE
It is the outgoing route

SIP signaling routing group ID, which is
SIPRTS
group associated with the ID in
command ADD SIPRTS
Example: Create URI analysis with the following

requirements.

159
� Routing selector: 1
� Uniform Resource Identifier: scscf.zte.com
� SIP method: ACK&BYE&CANCEL&INVITE&PRACK&UP-
DATE
� SIP signaling route group: 12 (pointing to S-CSCF)
ADD
"&"BYE"&"CANCEL"&"INVITE"&"PRACK"&"UPDATE",SIPRTS
URI:RTSEL=1,URI="scscf.zte.com",METHOD=
=12;
"ACK
END OF STEPS

Creating an RTP Trunk

Group
� The adjacent SIP office to which the trunk group points is cre-
ated.
� The trunk group No. range is set in the resource management
system.
Context When the MSCS servers as a MGCF, the MGCF needs to control
the IP resources from the IM-MGW to the IMS domain through
the RTP trunk group configuration data. In this case, SIP trunk
groups need to be configured.
system tree.
SET:NEID=11;
2. Creating 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 72.

TABLE 72 PARAMETERS IN THE ADD TG RTP COMMAND
Parameter Parameter
Instruction
Name Description
It is a mandatory
parameter. It is used to
define a trunk group.
TG Trunk group ID This trunk group can be
BICC trunk group or SIP
trunk group. It is a
global
unified number
It is a mandatory
specify the corresponding
ID of the office where
OFC office of the trunk group.
the trunk group
This parameter must be
belongs
defined by command ADD
ADJOFC at first. Then it
can be indexed here
consisting of 0~50
NAME User alias characters. It is used
to specifically describe a
trunk group to make it
easily recognized
It is a mandatory
parameter, which is an
integer, ranging from 1
Module where the
MODULE to 127. It is used to
trunk group belongs specify the SMP module
of
processing traffic on this
trunk group
Inter-office line
signal identification,
including
SIGLINE � BICC (BICC Select SIP for the MGCF.
signaling)
� SIP (SIP
signaling)
Trunk group types,
including the following
three types:
IN (incoming trunk
group): Indicates
that the local office
processes the It is an optional parameter.
incoming calls from BIDIR is selected by
KIND the peer-end office. default. It should be
OUT (outgoing trunk negotiated with the
group): Indicates peer-end office.
only processes the
outgoing calls to the
peer-end office.
BIDIR (Two-way
trunk group):
Indicates that the
local

161

Name Description
office processes both
the incoming calls
from the peer-end
office and the
peer-end office
Bearer establishment
direction, including
the following three
types:
NODIR (No
direction): The
inter-office bearer
is established It is an optional parameter.
BWAY without For RTP trunk groups, it
direction. is set according to the
network plan of operators
BACK: The inter-office
bearer is established
based on the
backward mode.
FORWD: The
inter-office bearer
is established based
on the forward
mode
Threshold for overload
THD ranging from 0 to 100, with
control
a default of 100
Circuit selecting
modes, including:
MIN: Every time
when the system
selects a trunk circuit,
it always begins with
the circuit with the
minimum number.
This mode can
implement the
preferred plan of trunk
circuits. It is an optional parameter,
with a default of CYC. In
MAX: Every time general, the signaling point
when the system with big code prefers the
selects a trunk circuit, circuit with an even
CICSEL it always begins with number, while the one with
the circuit with the small code prefers the
maximum number. circuit with an odd number.
This mode can It should be negotiated
implement the with the peer-end office
circuits.
CYC: Every time when
the system selects
a trunk circuit, it
always begins with the
circuit next to the one
previously selected.
Suppose the numbers
of the trunk circuits
in a trunk group in
ascending order are
“TKC0, TKC1, …. ,


Name Description
TKCn”. If TKC0 is
selected at the first
time, the system will
select the trunk circuit
in the order of “TKC0
TKC1…TKCnTK
C0TKC1…TKCn”.
ODD: Every time
when the system
it always selects the
circuit with an odd
number.
EVEN: Every time
when the system
circuit with an even
number.
IDLE: Every time
when the system
idlest circuit.
BUSY: Every time
when the system
busiest circuit
which is an integer ranging
from 0 to 4096, with a
default of 0. When the
local office has the GMSC
DAS DAS for the called function, this DAS is used
number to analyze the called
number from other offices.
When the called number is
from the BSC office, this
DAS is meaningless, and
does not need to be
configured
It is used get the name of
the IMS domain where
the called party is located
through analyzing the
called number during a
SIP outgoing call. If the
outgoing SIP trunk group
DAS for the domain is configured with this
SIPDAS name of the called DAS, the “invite” message
number during SIP during a SIP outgoing call
outgoing calls can only contain SIP URL
mode. If the outgoing SIP
trunk group is not
configured with this DAS,
configure the URLOPT in
the SIP adjacent office
configuration to decide
whether the outgoing call
uses TEL or SIP URL
mode.

163

Name Description
After this DAS is used
on this trunk group, all
outgoing calls on this
trunk group will get the
corresponding domain
name according to the
called number, and then
form a SIP URL
OPDAS DAS for the calling function, this DAS is used
number to analyze the calling
When the calling number is
does not need to be
configured
Example: Create a SIP trunk group with the following require-

ments.
� Trunk group ID: 12
� ID of the office where the trunk group belongs: 12
� User alias: SCSCF
� No. of the module processing the trunk group: 0
� Inter-office line signal identification: SIP
� SIP route set: 12
ADD TG RTP:TG=12,OFC=12,MODULE=0,NAME="SCSCF
",SIGLINE=SIP,KIND=BIDIR,BWAY=NODIR,THD=100,CI
CSEL=CYC,DAS=0,SIPDAS=0,OPDAS=0,PREDAS=0,DDI
=0,OPDDI=0,MINNAT=0,MAXNAT=26,MININT=0,MAXI
NT=26,INREG=INVALID,OUTREG=INVALID,COLEN=10,B
USYRATE=100,ROAMDAS=0,Q850CCIDX=0,SMENTERID
=0,MLPPDM=4294967295,SIPRUTS=12,DISINDEX=0;
END OF STEPS


Chapter
6
MGCF-Other-Exchange
Configuration
Table of Contents
Networking Mode............................................................. 165
Office Interconnection in IP Domain ................................... 166
TDM Office Interconnection ............................................... 181
Networking Mode
Overview When MGCF is interconnected with the equipment (such as MSCS,
2G MSC/PSTN) at the network side, the interfaces between them
fall into TDM-type or IP-type according to different bearer modes,
as described in Table 73. These interfaces may also fall into
direct- associated mode and quasi-associated mode according to
their connection method. You should select the corresponding
configuration method according to the actual networking
condition.
TABLE 73 BEARER MODES OF MAIN INTERFACES
Interconnected Equipment Interface Bearer Mode
MSCS Nc IP
2G MSC/PSTN Ai TDM/IP
Take the interconnection between 2G MSC and MGCF/IM-MGW for

example. When the traffic bearer is TDM bearer or IP bearer, 2G
MSC is directly connected with IM-MGW. However, the signaling
modes between 2G MSC and MGCF divide into the following three
types.
1. 2G MSC is connected with MGCF in TDM bearer mode.
When 2G MSC is interconnected with the MGCF in TDM bearer
mode, they only transmit the narrowband signaling.
i. 2G MSC<->MGCF
2G MSC is directly associated with MGCF in a TDM bearer
mode.

165
ii. 2G MSC<->STP<->MGCF
2G MSC is quasi-associated with MGCF through STP in
TDM bearer mode.
This method is applicable to the interconnection between two
devices in the circuit domain, which requires configuring the
narrow-band signaling processing board SPB on MGCF.
2. 2G MSC is connected with MGCF in an IP bearer mode.
2G MSC is directly connected with MGCF in an IP bearer
mode. The signaling between them is transmitted through
SIGTRAN. The upper-layer signaling, such as BICC, is borne
through M3UA/SCTP or SCTP. This method is applicable to the
interconnection between two devices in the IP domain.
3. 2G MSC is connected with MGCF in IP bearer and TDM bearer
modes.
The signaling adaptation between 2G MSC and MGCF is imple-
mented through an intermediate node, which is IM-MGW usu-
ally. The signaling is transmitted by the path of 2G MSC<-
>IM- MGW<->MGCF, where the narrow-band signaling is
transmitted between 2G MSC and IM-MGW, and SIGTRAN is
transmitted between IM-MGW and MGCF.
The signaling may also be switched on IM-MGW in M3UA or
M2UA mode.
� When MGCF and IM-MGW adopt different signaling points,
M3UA transfer mode is usually adopted.
� When MGCF and IM-MGW adopt the same signaling point,
M3UA proxy mode is usually adopted.
� When MGCF and IM-MGW adopt the same signaling point,
and MGCF manages several IM-MGWs that are all con-
nected with MGCF, M2UA transfer mode may be adopted.
Office Interconnection in IP
Domain
Overview
Introduction This section describes the procedure for configuring the office in-
terconnection in the IP domain.
There are the following three interconnection modes in the IP do-
main.
1. Direct-associated office in the IP domain
The office is directly connected with MGCF in IP bearer mode.
2. M3UA-transferred office

Chapter 6 MGCF-Other-Exchange Interconnection Data Configuration
MGCF and its opposite-end office provide IP and TDM bear-

ers respectively. The signaling between them is transferred by
IM-MGW in M3UA mode.
3. M2UA-transferred office
MGCF and its opposite-end office provide IP and TDM bear-
ers respectively. The signaling between them is transferred by
IM-MGW in M2UA mode.
Direct-Associated Office
Configuration in IP Domain
The direct-associated office in the IP domain is the office directly
connected with MGCF in the IP bearer mode. For example, MGCF
and MSCS are connected through an Nc interface.
Overview
Configuration Figure 54 shows the flow of configuring a direct-associated office
Flow in the IP domain.
FIGURE 54 FLOW OF CONFIGURING A DIRECT-ASSOCIATED

OFFICE IN IP DOMAIN
Flow Description Perform the following steps.

167

Create other
interconnected office
Creating an at the network side,
1 ADD ADJOFC
Adjacent Office except for IM-MGW.
Select a different
adjacent office type.
The topological node of
Creating an MSCS the opposite-end
2 MSCS office is ADD TOPO
Topological Node
configured during the
Nc interface
configuration.
It is similar to the
SIGTRAN protocol SIGTRAN configuration -
3
configuration on the Mn interface,
refer to Overview.
Creating an Adjacent Office

� The signaling interworking data planning and negotiation be-
tween MSCS and other office are completed.
� The data configuration of local office is completed.
Context Perform this procedure to configure the basic information of an
inteconnected adjacent office.
system tree.
SET:NEID=11;
2. Create an adjacent office. The command is ADD ADJOFC.
Table 74 describes the main parameters in the ADD ADJOFC
command.
TABLE 74 PARAMETERS IN THE ADD ADJOFC COMMAND
Parameter Parameter
Instruction
Name Description
indicating the identification
number of the adjacent
office, and ranging from 1
ID Office ID to 3000. In general, it is
configured as the exchange
ID of the adjacent office
during the all-network
planning


Name Description
NAME User-defined alias It is a mandatory

parameter. Type a
customized name
indicating the network
type of the SPC used for
connecting the local office
NET Network type to the adjacent office when
the local office is
configured
with several SPs. The
default is the network type
of this SP when there is only
one SP in the local office
OFCTYPE The type of adjacent It is a mandatory parameter.

office
SPCFMT SPC format Select TRIPLE_DEC
It is a mandatory
parameter. Select it based
SPCTYPE SPC type on the SPC type of the
adjacent office according to
DPC Destination SPC the signaling point
planning. In China, all the
NEs adopt the 24-bit SPC
indicating the local toll zone
RC Area code code of the adjacent office.
This parameter has impact
on the area code added by
the calling number
Association type,
including:
� AM_SURE
(direct
connection mode) It is an optional parameter.
ASSOTYPE
� AM_QUASI (half Select AM_SURE
direct connection
mode)
� AM_NONE (none
connection
mode)
Select SEP (signaling end
Signaling point type, point), STEP (signaling
SPTYPE including SEP, STP transfer/end point) or STP
and STEP (signaling transfer point)
according to the role of
the adjacent office in the
signaling network.

169

Name Description
including
� INTERNA-
TIONAL (Inter-
national signaling
point code)
� INTERNA-
TIONAL
STANDBY (In-
ternational It is an optional parameter.
SSF standby signaling In general, NATIONAL is
point code) selected at home.
� NATIONAL
(National
signaling point
code)
� NATIONAL
STANDBY
(National
standby
signaling point
code).
Office Attribute,
including:
ISNI (Has ISNI
Function)
TRANS (Translate
Node)
TEST (Need Test
Info:0X02/0X01)
It is used to set whether the
MTP3 link actively initiates
TEST Test flag the link test after entering
the service status. In most
cases, this parameter is
selected.
message.
BANDFLAG Broadband attribute narrowband link message
is 255. Because the MTP
the
causes the long packet to
be discarded.


Name Description
links.
Protocol Type,
including: It is an optional parameter.
The CHINA and the ITU
� CHINA (China) are used for the NO.7
� ITU (Interna- signaling networking of the
tional Telecom- ITU standard and the ANSI
PRTCTYPE munications is used for the NO.7
Union) signaling networking of the
American standard. In
� ANSI (American general, select CHINA for
National the domestic office and
Standards select ITU for the
Institute) international office
within 0~65535. In
general, select the default
value 65535. It is valid
when the protocol type
CLST Cluster ID of the adjacent office is
“ANSI”. The signaling point

CIC_PCM (CIC starts
the load sharing
code mode)
BLOCK (Manual block
status)
EVEN_CIC (The
office controls the
even CIC when CIC It is an optional parameter
INFO resource contention and the default value is
occurs) CIC_PCM
CALLING ( Calling
CALLED (Called
MOD24_CIC (CIC
mode with 24 mode)
TEST (Dynamic
observation)

171

Name Description
Related Office ID
Office Extend Info,
including:
� SIGBRDCST
(Support Signa
ling Broadcast
Message)
� MTP (Hongkong
MTP Standard)
� DUPU ( Screen
DUPU message)
�
INFOEX SUA_REC_DT1 It is an optional parameter
(Receive SUA
message and
handle it as DT1
message)
�
SUA_SND_DT1
(Send SUA message
and handle it as
DT1 message
without SN.)
�
OPEN_TG_RES
(Open outter
trunk group
resource)
For example, configure the MSCS adjacent office. The net-
work type is 1, the alias is MSCS105, the signaling point code
is 3.105.1 the signaling point code format is 24, the associ-
ation type is AM_SURE, and the office type is LOCAL&DOM-
TOLL&OA&MSCSERVER For other parameters, select the de-
fault value. The command is as follows:
ADD ADJOFC:ID=105,NAME="MSCS105",NET=1,OFCTYP
E="LOCAL"&"DOMTOLL"&"OA"&"MSCSERVER",SPCFMT=TR
IPLE_DEC,SPCTYPE=24,DPC="3.105.1",RC="25",ASSOTY
PE=AM_SURE,SPTYPE=SEP,SSF=NATIONAL,SUBPROTTYP
E=DEFAULT,TEST=YES,BANDFLAG=NO,PRTCTYPE=CHIN
A,CLST=65535,INFO="CIC_PCM",RELATEDOFC1=0;
END OF STEPS

Creating an MSCS Topological Node

� The encoding and decoding speech template configuration is
completed.

� The range of topological nodes is configured in the resource

management.
Context For Nc interface, the topological node of the opposite-end MSCS
office needs to be configured.
system tree.
SET:NEID=11;
2. Configure an MSCS topological node. The command is ADD
TOPO.
command.
TABLE 75 PARAMETERS IN THEADD TOPO COMMAND

Name Description
It is a mandatory
parameter. For identifying
this node with a serial
ID Topological node ID number, ranging from 1 to
3000.
It is recommended to be
consistent with the office ID
of this node
It is a mandatory
parameter for specify the
office ID of this topological
OFCID Office ID node. This parameter must
be defined by the ADD
ADJOFC command first.
Type the MSCS office ID
conditions.
It is a mandatory
NAME Alias parameter for describing a
topological node, with a
length ranging from 1 to
50 characters.
It is a mandatory
parameter for specify the
CODEC template used by
CODECID CODEC identity this topological node. This
by the ADD CODECTPL
command first.
specify the NE equipment
ETYPE Equipment type type of this topological
node. Select MSCS for an
MSCS device.
PROTTYPE Protocol type Select BICC for an Nc

interface.

173

Name Description
This parameter indicates

the IP protocol version
IPVER IP version of the node Select IPV4 or IPV6
conditions. Currently, it is
usually configured as IPV4

ATTR Bearer attributes of R4GW (MGW). You need
not to configure it for an
MSCS topological node.
Extended attributes
(tunnel mode),
including: This parameter sets which
tunnel mode is used for
� NOTUNL (None setting up a bearer when
ATTR2 tunnel mode) this node supports the
� RTUNL (Rapid IP/RTP bearer, with a
tunnel mode) default of NOTUNL (None
tunnel mode).
� DTUNL (Delay
tunnel mode)

Signaling transfer set that mode used by
mode, including: the topology for reporting
TRFMOD MCINTF (Mc the detected CNG or CED
interface signal fax signals, with a default
transfer mode) of MCINTF (Mc interface
signal transfer mode).
This parameter designates

Tandem office send
whether TC resources are
DTMF use TC mode,
DTMFTC used during DTMF number
including NO (No)
and YES (Yes) delivery, with a default of
NO
MGW congestion
reporting capability, This parameter designates
including SMGWCON the MGW congestion
MGWCON (standard MGW reporting capability, with
congestion event) a default of SMGWCON
and CMGWCON (standard MGW
(custom MGW congestion
congestion event) event).
Example: Create an MSCS topological node with the following

requirements.
� MSCS office ID: 105
� Equipment type: MSCS
� Protocol type: BICC
� CODEC ID: 1
� Other parameters: Default.

ADD TOPO:ID=105,OFCID=105,NAME="MSCS105",CODE
CID=1,ETYPE=MSCS,PROTTYPE=BICC,IPVER=IPV4,ATT
O=PRIVATE;
END OF STEPS

M3UA-Transferred Office
Configuration
Description MGCF and its opposite-end office provide IP and TDM bearers re-
spectively. The signaling between them is transferred by IM-MGW
in M3UA mode.
Networking mode Take the quasi-associated networking (M3UA-based) between
MGCF and 2G MSC/PSTN for example. Figure 55 shows its
interface protocol stack.
FIGURE 55 QUASI-ASSOCIATED NETWORKING BETWEEN MSCS

AND 2G MSC/PSTN (BASED ON M3UA)
The connection between MGCF and IM-MGW is in the IP bearer

mode, and the connection between IM-MGW and 2G MSC/PSTN is
in the TDM bearer mode. Therefore, to configure the interworking
data between MGCF and 2G MSC/PSTN, you only need to create
a 2G MSC/PSTN adjacent office on the MGCF, and to configure
the SIGTRAN data between MGCF and IM-MGW to make the IM-
MGW complete the signaling transit. In this case, the IM-MGW
serves as a signaling gateway, working in a switching mode.
Configuration Figure 56 shows the flow of configuring an M3UA transit
exchange.
Description

175
FIGURE 56 FLOW OF M3UA TRANSIT EXCHANGE
Perform the
following steps. Steps Operations Configuration Reference
Description
Create other interconnected
office at the network side,
except for IM-MGW. Select
Creating an a different adjacent office Creating an
1 adjacent type. It is required that the Adjacent
office network type of this Office
adjacent office is consistent
with the IM-MGW network
type configured for this
group of associations.
Based on the principles
of SCTP Planning, specify
the office ID parameter
in the SIO-locating-AS
SIGTRAN configuration to be
2 consistent with the office Overview
configuration
ID
of the adjacent office that is
switched through IM-MGW,
when the association
between IM-MGW and
MGCF is configured.

M2UA-Transferred Office
Configuration
Overview
Introduction MGCF and its opposite-end office provide IP and TDM bearers re-
spectively. The signaling between them is transferred by IM-MGW
in M2UA mode.
Networking mode Take the quasi-associated networking (M2UA-based) between
MGCF and 2G MSC/PSTN as an example. Figure 57 shows its
interface protocol stack.
FIGURE 57 QUASI-ASSOCIATED NETWORKING BETWEEN MGCF

AND 2G MSC/PSTN (BASED ON M2UA)
The connection between MGCF and IM-MGW is in the IP bearer

mode, and the connection between IM-MGW and 2G MSC/PSTN is
in the TDM bearer mode. When the signaling is transferred in the
M2UA mode, IM-MGW serves as SG to only complete the adapta-
tion of the MTP2-layer protocol, and transparently transmits the
MTP3 layer protocols to the MGCF for processing. Therefore, you
only need to configure the No. 7 signaling data on the MGCF,
which are transmitted to the adjacent office.
Configuration flow Figure 58 shows the flow of configuring an M2UA transit
exchange.

177
FIGURE 58 FLOW OF M2UA TRANSIT EXCHANGE

Steps Operations Instruction Reference

Create other
interconnected office at Creating an
Creating an
1 the network side, except Adjacent
adjacent office
for MGW. Select a Office
different adjacent office
type.
OFCID: select the
Creating an adjacent office ID Creating an
2 configured in Step 1.
SCTP SCTP
PROT: Select M2UA
3 Creating an - Creating an
ASP ASP
PROT: Select M2UA
EXISTCTX: No routing
context is configured Creating an
4 Creating an AS
ASTAG: Select ASP on AS
MSCS.
ASUP: Select NULL
Select the type of this
Creating a signaling link set Creating a
5 signaling link according toits signaling Signaling Link
set link type. In general, Set
select N64 (64K
narrowband link set).
6 Creating an - Creating an
M2UA IP link M2UA IP Link
Creating a
Creating a -
7 Signaling
signaling route
Route
Creating a Creating a
8 - Signaling
signaling office
Office
Creating an M2UA IP Link

� The signaling link group configuration is completed.
Context When IM-MGW forwards signaling in the M2UA mode, the M2UA
IP link connection to the adjacent office should be configured.
The signaling link is accessed through SIPI board, and SIGTRAN
protocol is used for transmission.
system tree.
SET:NEID=11;
2. Create an M2UA IP link. The command is ADD M2UAIPLNK.

179
Table 76 describes the main parameters in the ADD M2UAIP

LNK command.
TABLE 76 PARAMETERS IN THE ADD M2UAIPLNK COMMAND
Parameter Parameter
Instruction
Name Description
Type the link set No. of this
Signaling link set link, ranging from 1 to
LKSID
ID 1024.Which is associated
with
the ID of the signaling link set
that is created
to configure the SLC of this
Signaling link set signaling link. It needs to be
SLC
code consistent with the SLC of
the same signaling link of the
opposite-end office
MODULE Type the No. the SMP module
SMP module No.
that processes this link,
Type the AS No. used by this
ASID Destination AS ID signaling link, ranging from 1
to 640. In this case, type the
AS ID whose adaptation layer
is M2UA
ID Link number designating the global No. of
the signaling link on the
MSCS. It ranges from 1 to
5000
NAME Alias for describing the name of
this signaling link for easy
identification
Interface ID
type, including
INT(Integer The parameter indicates the
IIDTYPE Type), interface ID type. Currently,
TEXT(Text only the integer type is
Type and supported.
BOTH(Integer
and Text Type)
IID Interface ID The parameter ranges from 0

to 4294967295
Self loop,
including options: The parameter indicates
LOOP NO(Not Self whether the link is at a self
Loop) and loop status.
YES(Self Loop)
Example: Create an M2UA IP signaling link connecting to a 2G

MSC office with the following requirements.

� Link set ID: 2

� SMP module No.: 3
� Destination AS ID: 2
� Link No.: 2
� Alias: MSC
� ID of it in the signaling link set: 0
ADD M2UAIPLNK:LKSID=2,SLC=0,MODULE=3,ASID=2,I
D=2,NAME="MSC",IIDTYPE=INT,LOOP=NO;
END OF STEPS

TDM Office Interconnection

Overview
Introduction TDM office refers to the office connecting with MGCF through TDM
bearer. To configure a direct-associated office, you need to
configure signaling link set, signaling link, signaling route, and
signaling office. To configure a quasi-associated office, you only
need to configure the signaling office.
Configuration Figure 59 shows the flow of configuring the interconnection data
Flow between MGCF and TDM office.

181
FIGURE 59 TDM OFFICE INTERCONNECTION CONFIGURATION

FLOW
Configure a
Creating signaling narrowband
1 signaling link set ADD N7LKS
link set
to the adjacent
office.
Configure a
Create SPB narrowband
2 signaling link ADD N7LNKE1
signaling link
to the adjacent
office.


The signaling
routing
configuration
is used for
3 Create signaling specifying the ADD N7ROUTE
route signaling link
set
to be selected and
the method when
the signaling
selects a route.
Configure the
correspondence
Create signaling between the
4 destination ADD N7OFC
office
signaling office
and the signaling
route.
Creating a Signaling Link Set

� The adjacent office configuration is completed.
� The data configuration of local office is completed.
� The range of signaling link set is configured in the resource
management.
Context Perform this procedure to configure a narrowband signaling link
set to the adjacent office, including 64k signaling link set, 2M
signaling link set, N×64k signaling link set.
When configuring the signaling link set connected by TDM, you
may select N64, NN64, and N2M.
� 64k indicates that the narrow-band signaling link in this sig-
naling link set only seizures one time slot on one E1 line, with
64 Kbps bandwidth.
� N×64K indicates that the narrow-band signaling link in this
signaling link set seizures N consecutive time slots on one E1
line (8≤n≤25).
� 2M indicates that the narrow-band signaling link in this signal-
ing link set seizures all 31 time slots on one E1 line (time slot
0 is unavailable), with 1.984Mbps bandwidth.
system tree.
SET:NEID=11;
2. Create a signaling link set. The command is ADD N7LKS.

183
Table 77 describes the main parameters in the ADD N7LKS

command.
TABLE 77 PARAMETERS IN THE ADD N7LKS COMMAND
Parameter
Name
It is a mandatory
parameter. Type the
Direct-associated office adjacent office ID of
OFCID this signaling link set,
of the signaling link
set which is specified in
the adjacent office
configuration.
This parameter indicates

the types of the signaling
links in this signaling
TYPE Signaling link set type link set. Select N64 for
a 64K signaling link,
NN64 for an n×64K
signaling link, and N2M
for a 2M signaling link.
It is a mandatory
parameter. It designates
ID Signaling link set ID the signaling link set
No. for distinguishing
signaling link sets,
This parameter
Link error revision, designates the error
including: correction method of the
BASIC (basic error signaling links in this
revision, transit delay ≤ set. In general, select
15 ms): all the signaling BASIC. In general,
links use this method for BASIC is selected when
relatively short transit the line transit delay
LECM is less than 15ms, and
delay, except for satellite
PCR is selected when
links.
the line transit delay
PCR (Preventive Cyclic is greater than 15ms.
Retransmission: transit For a 2M signaling
delay≥15 ms): Satellite link,
links use this method for BASIC must be selected.
it has a relatively long This parameter shall be
transit delay. consistent with that of
the opposite end through
negotiation.
It is a mandatory
parameter describing
NAME Alias the name of this
signaling link set for
easy identification.
Example: Create a signaling link set connected TDM office 104

� TDM office ID: 104
� Signaling link set No.: 1
� Group type: 64K narrowband link set

� Link error revision: Basic error revision

� Alias: TDM-1.
ADD N7LKS:OFCID=104,TYPE=N64,ID=1,LECM=BASIC,N
AME="TDM-1";
END OF STEPS

Creating an SPB-Accessed Signaling

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

system tree.
SET:NEID=11;
2. Create an SPB-accessed signaling link. The command is ADD
N7LNKE1
N7LNKE1
command.

185
TABLE 78 PARAMETERS IN THE ADD N7LNKE1 COMMAND
Parameter Parameter
Instruction
Name Description
designating the signaling link
Signaling link set No. of this signaling link.
LKSID
set ID It is associated with the ID of
the signaling link set that is
configured.
This parameter designates the

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

E1 number of number of the E1 where the
E1 signaling link is located, ranging
the SPB board
from 9 to 25. By default, it is
numbered from 9
64k signaling link: the time slot

number of the signaling link is 16
Start timeslot N×64k signaling link: its start
TS
number of time slot ranges from 1 to 31
E1
2M signaling link: Its start time
slot is 1


Name Description
Configure the number of the time
slots occupied by the signaling
link.
64K signaling link: Its time slot
Quantity of amount is 1.
TSNUM
timeslots
N×64K signaling link: Its time
slot amount is N.
2M signaling link: Its time slot
amount is 31.
Miscellaneous
information,
including:
E1: This
link uses
the E1-type
interface.
N64KT1:
This link uses
the T1-type
interface, with
64K normal Configure the interface type and
INFO coding mode. coding mode of this link. In
I64KT1: This general, it is an E1 link.
link uses
the T1-type
interface,
with
64K reversal
phase coding
mode.
56KT1: This
link uses
the T1-type
interface, with
54K coding
mode.
Example: Create an SPB-accessed signaling link with the fol-

lowing requirements.
� SMP module No.: 3
� Signaling link alias: TDM-1
� SPB board unit No.: 721
� Start time slot number of E1: 1
� Time slot amount: 1
� Signaling link No.: 0

187
ADD N7LNKE1:LKSID=1,SLC=0,MODULE=3,NAME="TDM
-1",ID=1,SPBUNT=721,CPU=1,E1=9,TS=16,TSNUM=1,LO
OP=NO,INFO=E1,FCPLTHR=255;
END OF STEPS

Creating a Signaling Route

� The range of signaling route ID is configured in the resource
management.
Context The signaling routing configuration is used for specifying the sig-
naling link set to be selected and the method when the signaling
selects a route. The signaling route to a direct-associated office
only contains the signaling link sets to this office. The signaling
route to a quasi-associated office contains one or two signaling
link sets to the intermediate office.
system tree.
SET:NEID=11;
2. Create a signaling route. The command is ADD N7ROUTE.
N7ROUTE
command.
TABLE 79 PARAMETERS IN THE ADD N7ROUTE COMMAND
Parameter Parameter
Instruction
Name Description
NAME Alias designating a signaling route
for easy identification.
The signaling route contains

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

link set contained by the
LKSID2 Signaling link set 2 signaling route. At least
either LKSID1 or LKSID2
is not equal to zero and
contains signaling links. If


Name Description
only one signaling link set
exists, type 0

the serial number of the
signaling route, ranging from
Signaling route 1 to 2000. When there
ID is only one signaling link
number
set, this parameter may be
configured to be consistent
with the signaling link set
number.

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

Arrangement mode the rules that should be
LPMIN in a signaling link obeyed when the signaling
set. Refer to Table links in a signaling link set
80 for its options. are sorted. RAND (random
order) is recommended
Sort manually,
The parameter indicates
including NO(Need
MANUAL whether to manually sort the
Not Manual)
signaling routes of the two
and YES(Need
link groups
Manual):
The maximum number

of instance is 16. The
format is <INDEX>-
LINKS Link list
<LINK>,
representing the alignment
order and link number
respectively.
TABLE 80 ARRANGEMENT MODE OF SIGNALING SETS
Mode Meanings Instruction
RAND Random Random arrangement mode

arrangement mode
Selecting links between two

SLS0 Select On
link sets according to Bit 0 of
SLS_BIT0
SLS
Select On Selecting links between two

SLS1 link sets according to Bit 1 of
SLS_BIT1
SLS

189
Mode Meanings Instruction

Select On
SLS2 link sets according to Bit 2 of
SLS_BIT2
SLS

SLS3 Select On
SLS_BIT3 link sets according to Bit 3 of
SLS
Select On Selecting links between two

SLS01 link sets according to Bits 0
SLS_BIT0-1
and 1 of SLS

Select On
SLS_BIT1-2
and 2 of SLS

Select On
SLS_BIT2-3
and 3 of SLS
Example: Create a signaling route with the following require-

ments.
� Alias: TDM
� Signaling route No.: 1
ADD
N7ROUTE:NAME="TDM",LKSID1=1,LKSID2=0,ID
=1,LPM=RAND,LPMIN=RAND,MANUAL=NO;
END OF STEPS
Creating a Signaling Office

� The signaling route configuration is completed.
Context Perform this procedure for configuring the correspondence be-
tween the destination signaling office and the signaling route.
system tree.
SET:NEID=11;

2. Create a signaling office. The command is ADD N7OFC. Table

81 describes the main parameters in the ADD N7OFC
command.
TABLE 81 PARAMETERS IN THE ADD N7OFC COMMAND

Name tion
It is a mandatory
ID Signaling route office parameter. Type the
adjacent office No. of
the destination office
This parameter It is a mandatory
designates the serial parameter. Configure
RT1 number of the direct the serial number of the
route to the destination direct route to this
adjacent office. office, ranging from 1 to
2000
Alternate route 1,
indicating the serial
RT2 number of the first
alternate route to the
destination adjacent
office.
Alternate route 2,
number of the second This parameter ranges
alternate route to the from 0 to 2000.
RT3 destination adjacent Select up to three
office. This parameter available alternate
is configured when only routes according to the
the first alternate route actual conditions. When
is already configured. there is no alternate
route, configure it as 0.
Alternate route 3,
number of the third
alternate route to the
RT4 destination adjacent
office. This parameter is
configured when only
the second alternate
route is already
configured.
It is a mandatory
parameter. This
NAME Alias parameter designates
the name of the
signaling office for
easy identification
Example: Create a signaling office to a TDM adjacent office

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

191


Chapter
7
Basic Service Data
Configuration
Table of Contents
Overview........................................................................ 193
Number Analysis Configuration .......................................... 193
Trunk Data Configuration .................................................. 235
Route Data Configuration.................................................. 258
Overview
The configuration flow of basic service data is as follows:
No. Operations
1 Number analysis configuration
2 Trunk data configuration
3 Route data configuration
Number
Analysis
Configuration
If the SIP address format is TEL/IP, the SIP number analysis is
the same with the ordinary number analysis.
If the SIP address format is URI, besides the ordinary number
analysis, a URI analysis configuration is required.
ZXWN MSCS system provides seven number analyzers: new ser-
vice number analyzer, CENTREX number analyzer, private-
network number analyzer, special-service number analyzer, local-
network number analyzer, national toll-service number analyzer,
and international toll-service number analyzer. For a specified
DAS, numbers pass each type of analyzers specified by this
DAS in a fixed order. The analyzers strictly follow the following
order to perform number analysis, as shown in Figure 60.

193
FIGURE 60 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 82.
TABLE 82 DAS FOR PRE-ANALYZING THE CALLED NUMBER
Analyzer Analyzed Number

Entry Analysis Result
If call restriction is
required, analyze it to
“pre-analysis ending, and
call rejected”
If no call restriction is
10193 + 0 + local area required, analyze it to
code “pre-analysis normally
ending”, and delete
New “10193 + 0 + local area
service code” from the change
number index of the called
analyzer number
Analyze it to
“pre-analysis normally
ending”, and delete
10193 + 0 + non-local 10193 from the change
area code index of the called
number.
Whether to add 10193 to
the called-number index

Chapter 7 Basic Service Data Configuration
Analyzer Analyzed Number

Entry Analysis Result
10193 + G network
number section
in the CDR depends

on the CDR filling
10193 + C network requirements on the

number section billing center
2. Originating DAS: used to analyze the called number in the lo-

cal-office-originated call, as shown in Table 83.
TABLE 83 ORIGINATING DAS
Analyzer Analyzed Number Analysis Result

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

Local- by the subsequent
network analyzers
number
Analyze it to
analyzer the local-network
Local PSTN number outgoing/local-call
service, pointing to
the gateway office

195
Analyzer Analyzed Number Analysis Result

Entry
Analyze it to
Local number section of the local-network
other mobile network outgoing/local-call
the gateway office
Analyze it to the
Non-local number section automatic service in
of other mobile network the national toll region,
pointing to the tandem
office of the local
province
Number section of the Analyze it to the MSC
local mobile network common service
Vacant number
0 All numbers are analyzed

by the subsequent
analyzers
Analyze it to
National
0 + Local area code + the local-network
toll-service
number
analyzer
the gateway office
Analyze it to the
automatic service in
0 + Non-local area code the national toll region,
pointing to the tandem
office of the local
province
Inter-
national Analyze it to the
00 + International
toll-serv- international toll
number
ice number automatic service
analyzer
3. Forwarding DAS: used to analyze the number to which the call

is forwarded, as shown in Table 84.
TABLE 84 FORWARDING DAS
Analyzer Entry Analyzed Number Analysis Result
Vacant number
0 All numbers are

analyzed by the
Local-network subsequent analyzers
number analyzer
Analyze it to
the local-network
the gateway office


Analyze it to
Local number section the local-network
of other mobile outgoing/local-call
network service, pointing to
the gateway office
Analyze it to the
Non-local number automatic service
section of other in the national toll
region, pointing to
mobile network the
tandem office of the
local province
Number section of the Analyze it to the MSC
local mobile network common service
Vacant number
0 All numbers are

analyzed by the
subsequent analyzers
Analyze it to
0 + Local area code + the local-network
National toll- outgoing/local-call
service number Local PSTN number
analyzer the gateway office
Analyze it to the
automatic service
0 + Non-local area in the national toll
code region, pointing to
the
tandem office of the
local province
4. Roaming DAS: used to analyze the roaming number in the re-

sponse message to the routing information query message, as
shown in Table 85. It is unnecessary to analysis the CC in na-
tional roaming numbers.
TABLE 85 ROAMING DAS

Roaming number
section of the local Analyze it to the local
service area in the MSC service
local office
Analyze it to the
outgoing service of
Local-network the local MSC.
number analyzer Roaming number Note: The roaming
section of non-local DAS is used when
service area in the there is no direct
local office voice channel
between MGWs
(switched through the
T office) in the region
networking

197
National other Analyze it to the

roaming sections national toll call
Analyze it to the
00 + International
international toll
number
automatic service
Overview
Description This section only introduces the basic steps of number analysis.
Data The related operations of the number analysis configuration are
Configura-
as follows.
tion
Steps Operations Commands
1 Creating a number analyzer ADD ENTR

entrance
2 Creating a DAS ADD DAS
3 Creating the default DAS SET LDASTMPLT

template of the local office
4 Creating a DAS template ADD ACRTMPLT

(optional)
5 Creating the called numbers ADD TPDNAL

analysis
Creating Number Analysis Entrance

� The number analysis entrance range is set in the resource
management system.
Context Configuring number analysis entrance means specifying an ID for
each type of number analyzers.
system tree.
SET:NEID=11;
2. Create a number analysis entrance by executing command A
DD ENTR.


ENTR is shown in Table 86.
TABLE 86 PARAMETERS IN THE ADD ENTR COMMAND

Name tion
It is an optional
ID Analyzer entry parameter, which is
an integer, ranging
from
1 to 1000
It is a mandatory
NAME User alias parameter, consisting of
0~50 characters
It is an optional
TYPE Analyzer entry type parameter. Refer
to Table 87 for the
configuration
description
Number analysis result
under this analyzer,
including
� CALLED (analysis
on called numbers)
� CALLING (analysis
on calling numbers)
� FORWARD
(analysis on calling
numbers during call
forwarding) It is an optional
NTYPE � OPIMSI (analysis parameter, with CALLED
on calling IMSI as the default value. In
numbers) general, select CALLED
� TPIMSI (analysis
on called IMSI
numbers)
� FWDIMSI (analysis
on IMSI numbers
during call
forwarding)
� RDCALLED
(Redirecting Number
Analysis)
It is an optional
parameter, which is
an integer, ranging
VMSCIDX Virtual MSC index from 0 to 65535.
Enter
it according to the
actual condition. The
default value is 0 (public
domain)

199
TABLE 87 ANALYZER ENTRY TYPES
Parameter Parameter Configuration

Name Description Description
After this analyzer
is configured, if the
New service number number is not
NEWSRV
analyzer matched
in this analyzer, it is
sent to the next entry
for analysis
CENTREX CENTREX number This analyzer is not

analyzer configured
PRINET Private-network This analyzer is not

number analyzer configured
After this analyzer
is configured, if the
Special-service number number is not
SPECSRV
analyzer matched
in this analyzer, it is is
sent to the next entry
for analysis
After this analyzer
Local-network number is configured, if the
LOCAL number is not
analyzer matched
in this analyzer, the
analysis ends
After this analyzer
National toll-service is configured, if the
NATIONAL number is not
number analyzer matched
in this analyzer, the
analysis ends
International After the number

INTER is analyzed in this
toll-service number
analyzer, the
analyzer analysis
ends with the
Example: Create a number analysis entrance
� Number analyzer entry ID: 1
� User alias: Entr1
� Number analyzer entry type: Local number analyzer
� Analyzed number type: Called
number. The command is:
ADD ENTR:ID=1,NAME="Entr1",TYPE=LOCAL,NTYPE=CAL
LED;
END OF STEPS


Creating Number Analysis Selector

� The Nnumber analysis selector (DAS) range is set in the re-
source management system.
� The number analyzer entry is configured.
Context The DAS is the collection of various number analyzer entries,
specifying the order and rule of performing number analysis.
Table 88 lists common DASs.
TABLE 88 COMMON DAS
Parameter Configuration
Parameter Description
Name Description
Used to analyze the called

MS MS originating number when an MS
originates a call
Used to analyze roaming

Mobile station roaming
MSRN numbers or handover
number
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
Used to analyze the

Forwarding number
FWD third-party number to
analysis
which the call is
forwarded
Used for the number
pre-analysis function,
PREDAS Number pre-analysis standardizing called
numbers, and
performing
call restriction based on
numbers

system tree.
SET:NEID=11;
2. Create number analysis selector by executing command ADD
DAS.
DAS

201
TABLE 89 PARAMETERS IN THE ADD DAS COMMAND
Parameter Name Parameter

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

analyzer entry
CENTR CENTREX number

analyzer entry
Private-network
PRINET number analyzer
entry
Special-service
SPECSRV number analyzer Enter the number
entry analyzer entry IDs
contained by a DAS
Local-network
LOCAL number analyzer
entry
National toll-service
NATIONAL number analyzer
entry
International
INTER toll-service number
analyzer entry
Example: Create a MS originating DAS with the following re-

quirements.
� DAS ID: 101
� User alias: MSQH
� Local number analyzer entry: 1
ADD
DAS:ID=101,NAME="MSQH",NEWSRV=0,CE
NTR
=0,PRINET=0,SPECSRV=0,LOCAL=1,NATIONAL=0,INTE
R=0;
Result END OF STEPS


Setting the Template of Number

Analysis Selector of the Current
Office
� The DAS is configured.
Context Configuring the default DAS template of the local office means
configuring the DAS used for local-office service processing.
system tree.
SET:NEID=11;
2. Setting the template of number analysis selector of the
current office by executing command SET LDASTMPLT.
The explanation of the main parameters in command SET
LDASTMPLT is shown in Table 90.
TABLE 90 PARAMETERS IN THE SET LDASTMPLT COMMAND

Name Description
It is an optional parameter, which
is an integer, ranging from 0
to 4096. It is used to analyze
the called number when an MS
originates a call. If the called
party is a mobile subscriber,
MS-Originating the MSC needs to query the
MS
Selector routing information from the
corresponding HLR. If the called
party is a fixed subscriber, the
MSC connect the call to the
corresponding local exchange
or toll exchange according to
location of the called party
is an integer, ranging from 0
to 4096. It is used to analyze
the MSRN returned from the
Roaming HLR, and judge whether the call
MSRN Number belongs to the local-office mobile
Selector 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

203

Name Description
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

is an integer, ranging from 0 to
4096.
Optimal
Routing When it is set that the local office
OR supports preferred routing in the
Number global variable control system,
configure this DAS for
Selector international roaming call and the
forwarding service

4096.
Calling Number It is used to analyze the calling
CNG
Selector number in outgoing calls to
implement traffic division of
the calling number and calling
number change function

Lawful is an integer, ranging from 0 to
LI Interception 4096.
Number
Selector It is used for the interception
service

IP IP Call Selector 4096.
It is used for the IP telephone
service

Incoming Call is an integer, ranging from 0 to
ICBCNG Limit Calling 4096.
Number It is used for the incoming call
restriction service
Personal It is an optional parameter, which

Back Ring is an integer, ranging from 0 to
PBRT 4096.
Tone Number
Selector It is used for the PBRT service
Default Forward It is an optional parameter, which

FWD Number is an integer, ranging from 0 to
Selector 4096
Default Forward It is an optional parameter, which

FWDCNG Calling Number is an integer, ranging from 0 to
Selector 4096


Name Description
MS Category It is an optional parameter, which

ROUTCAT1 1 Originating is an integer, ranging from 0 to
Selector 4096

Selector 4096

Selector 4096

Selector 4096

Selector 4096
Calling IMSI It is an optional parameter, which

IMSIOPDAS Number is an integer, ranging from 0 to
Selector 4096
Overlay It is an optional parameter, which

OVERLAY Number is an integer, ranging from 0 to
4096
Selector
SHLR Service It is an optional parameter, which

SHLRSKEY is an integer, ranging from 0 to
Key Selector
4096
Called IMSI It is an optional parameter, which

IMSITPDAS Number is an integer, ranging from 0 to
Selector 4096
Forward It is an optional parameter, which

IMSIFWDAS IMSI Number is an integer, ranging from 0 to
Selector 4096
TESTCALL Test Call It is an optional parameter, which

- DAS Number is an integer, ranging from 0 to
Selector 4096
Multimedia It is an optional parameter, which

MBRT Back Ring Tone is an integer, ranging from 0 to
Number 4096
International It is an optional parameter, which

INTPREDAS Number is an integer, ranging from 0 to
Pre-analysis 4096
Originating
PREDAS Number
Pre-
Analysis 1000
Selector
Default It is an optional parameter, which
RECNCTDAS Reconnection is an integer, ranging from 0 to
Number 4096
Selector

205

Name Description
CAMELDNA- CAMEL Caller It is an optional parameter, which

LIDX Number is an integer, ranging from 0 to
Selector Index 1000
Caller
SSDAS Supplementary is an integer, ranging from 0 to
Service Code 1000
Selector Index
ASCODE It is an optional parameter, which

ASCODEDAS is an integer, ranging from 0 to
Selector Index
4096
Example: Configure the default DAS template of the local

office with the following requirements.
� MS originating DAS: 101
� MSRN DAS: 201
� Forwarding DAS:
301. The command is:
SET
LDASTMPLT:MS=101,M
SRN=201,FWD=301;
Result E ND OF STEPS
Creating Templet of Number Analysis

Selector (Optional)
Context It is required to configure multiple DAS templates in the dual-
homing or regional networking.
system tree.
SET:NEID=11;
2. Create templet of number analysis selector by executing com-
mand ADD ACRTMPLT.
ACRTMPLT is shown in Table 91.

TABLE 91 PARAMETERS IN THE ADD ACRTMPLT COMMAND

Name tion
It is a mandatory
Analysis Selector
TPLIDX parameter, ranging
Templet Index
from 1~65535
It is a mandatory
NAME User alias parameter, consisting
of 1~50 characters
It is an optional
parameter, which is
an integer, ranging
used to analyze the
called number when
an
MS originates a call.
If the called party is a
MS MS-Originating Selector mobile subscriber, the
MSC needs to query
the routing
information
from the corresponding
HLR. If the called party
is a fixed subscriber,
the MSC connect the
call to the
corresponding local
exchange or toll
exchange according to
location of the called
party
It is an optional
integer, ranging from 0
to 4096. It is used to
analyze the MSRN
returned from the HLR,
and judge whether
the call belongs to
the local-office mobile
service or outgoing
mobile service based
on this number. If the
call belongs
to the local-office
Roaming Number mobile service, this
MSRN
Selector 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

207

Name tion
It is an optional
parameter, which is
an integer, ranging
from 0 to 4096.
When it is set that the
OR Optimal Routing local office supports
Number Selector preferred routing in the
global variable control
system, configure this
DAS for international
roaming call and the
forwarding service
It is an optional
parameter, which is
an integer, ranging
from 0 to 4096.
It is used to analyze
CNG Calling Number Selector the calling number
in outgoing calls
to implement traffic
division of the calling
number and calling
number change
function
It is an optional
parameter, which is
Lawful Interception an integer, ranging
LI from 0 to 4096.
Number Selector
It is used for the
interception service
It is an optional
parameter, which is
an integer, ranging
IP IP Call Selector from 0 to 4096.
It is used for the IP
telephone service
It is an optional
parameter, which is
an integer, ranging
ICBCNG Incoming Call Limit from 0 to 4096.
Calling Number
It is used for the
incoming call restriction
service
It is an optional
parameter, which is
Personal Back Ring an integer, ranging
PBRT from 0 to 4096.
Tone Number Selector
It is used for the PBRT
service
It is an optional
Default Forward parameter, which is
FWD
Number Selector an integer, ranging
from 0 to 4096


Name tion
It is an optional
Default Forward Calling parameter, which is
FWDCNG
from 0 to 4096
It is an optional
MS Category 1 parameter, which is
ROUTCAT1
Originating Selector an integer, ranging
from 0 to 4096
It is an optional
ROUTCAT2
from 0 to 4096
It is an optional
ROUTCAT3
from 0 to 4096
It is an optional
ROUTCAT4
from 0 to 4096
It is an optional
ROUTCAT5
from 0 to 4096
It is an optional
Calling IMSI Number parameter, which is
IMSIOPDAS
Selector an integer, ranging
from 0 to 4096
It is an optional
Overlay Number parameter, which is
OVERLAY
from 0 to 4096
It is an optional
SHLR Service Key parameter, which is
SHLRSKEY
from 0 to 4096
It is an optional
Called IMSI Number parameter, which is
IMSITPDAS
from 0 to 4096
It is an optional
Forward IMSI Number parameter, which is
IMSIFWDAS
from 0 to 4096
It is an optional
Test Call Number parameter, which is
TESTCALLDAS
from 0 to 4096

209

Name tion
It is an optional
Multimedia Back Ring parameter, which is
MBRT
Tone Number an integer, ranging
from 0 to 4096
It is an optional
International Number parameter, which is
INTPREDAS
Pre-analysis an integer, ranging
from 0 to 4096
It is an optional
Originating Number parameter, which is
PREDAS
Pre-Analysis Selector an integer, ranging
from 0 to 1000
It is an optional
Default Reconnection parameter, which is
RECNCTDAS
from 0 to 4096
It is an optional
CAMELDNA- CAMEL Caller Number parameter, which is
LIDX Selector Index an integer, ranging
from 0 to 1000
It is an optional
Caller Supplementary
SSDAS Service Code Selector parameter, which is
Index an integer, ranging
from 0 to 1000
It is an optional
ASCODEDAS parameter, which is
ASCODE Selector Index
an integer, ranging
from 0 to 4096
Example: Create a DAS template with the following require-

ments.
� DAS template ID: 1
� User alias: VMSC1
� MS originating DAS: 101
� MSRN DAS: 201
� Preferred routing DAS: 301
� Calling number DAS: 401
ADD
ACRTMPLT:TPLIDX=1,NAME="VMSC1",MS=101,M
SRN=201,OR=301,CNG=401,LI=0,IP=0,CBCNG=0,PBRT
=0,CFU=0,CFUCNG=0,CFNDUB=0,CFNDUBCNG=0,CFUD
UB=0,CFUDUBCNG=0,CFNRC_E=0,CFNRCCNG_E=0,CF
NRC_L=0,CFNRCCNG_L=0,CFNRY=0,CFNRYCNG=0,CD
=0,CDCNG=0,FWD=0,FWDCNG=0,CNGVIGW=0,FWDV
I
GW=0,INTRA=0,ROUTCAT1=0,ROUTCAT2=0,ROUTCA
T3
=0,ROUTCAT4=0,ROUTCAT5=0,IMSIOPDAS=0,OVERLA
210 Y=0,LIIGW=0,SHLRSKEY=0,IMSITPDAS=0,IMSIFWDAS
=0,MBRT=0,INTPREDAS=0,PREDAS=0,CFPRE=0,CFUPR
E=0,NDUBPRE=0,UDUBPRE=0,CFNRCE_PRE=0,CFNRCL_
PRE=0,CFNRYPRE=0,CDPRE=0,MORCPRE=0,GMSCRCPR
E=0,CFRCPRE=0,MTRCPRE=0,RECNCTDAS=0,CAMELDN
ALIDX=0,SSDAS=0,ASCODEDAS=0;
END OF STEPS

Creating Called Number Analysis

� The number analyzer entry is configured.
Context This section introduces how to configure number analysis for pre-
fixes of called numbers and roaming numbers. The called number
analysis determines the subsequent service procedures of the
Steps
call.
system tree.
SET:NEID=11;
2. Create the called number analysis by executing command
ADD TPDNAL.
TPDNAL is shown in Table 92.
TABLE 92 PARAMETERS IN THE ADD TPDNAL COMMAND

Name Description
which is an integer, ranging from
Number 1 to 1000. Select the
ENTR corresponding analyzer entry of
analyzer entry
the analyzed number prefix. For
local calls, select the
corresponding analyzer entry of
the local number analyzer
consisting of 1~20 digits. Input
the prefix of the called number,
Analyzer whose length must make it be
DIGIT distinguished in the local office.
number
For intra-office calls, it is required
to configure both the prefix of
the called number and that of the
local-office roaming number

211

Name Description
consisting of 0~50 characters.
NAME User alias It is used to specifically describe
the called number analysis to
make it easily recognized
It is used to specify the index
number of the special analysis
result rule for the associated called
number. This parameter must
be defined by command ADD
CEDSPECRL at first. Then it can
be indexed here. This parameter
is configured to implement the
routing service based on number
length. When the system performs
Special analysis analysis on the called number,
SPECRST it automatically matches the
result rule
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
number of the special analysis
result of the associated called
number. This parameter must be
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
Special analysis performs
SPECIDX analysis on the called number,
result index
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


Name Description
used to specify the service type
triggered by this number, and
determine the direction of this
Call service call. The system adopts “vacant
CAT types, including number” by default.
the options in
The called number of the local
office is analyzed to LOL
(Outgoing/local service of the
local
network).
When the call service type is
vacant number, local-network
local-office/common service, MSC
local-network local-office service,
Mobile Number Portability (MNP),
or H323 call, number analysis
result 1 must be fixed to 0. When
the call service type is outgoing
call or toll call, number analysis
result 1 is used to specify the
index number of the outgoing
route chain.
“equal access: CIC of the operator
where the subscriber is located” or
“equal access: non-local-network
CIC”, number analysis result 1 is
used to specify the index number
of the outgoing route chain.
“OVERLAY prefix incoming
service”, number analysis
Number result
RST1 analysis result 1 is used to specify the index
1 number of the outgoing route
chain. When the call service type
is “OVERLAY: CAMEL service
triggered by MO”, or “OVERLAY:
CAMEL service triggered by MT”,
number analysis result 1 is used
to specify the index number of
the
outgoing route chain.
When the call service type is “IP
service”, “IP mobile service”, or
“independent IP service” number
analysis result 1 is used to specify
the index number of the outgoing
route chain.
When the call service type is “MNP
outgoing routing” number
analysis result 1 is used to specify
the index number of the outgoing
route chain.
“Outgoing paid special service” or
“Outgoing free special service”,
to specify the index number of the
outgoing route chain.

213

Name Description
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.
“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
command ADD SSPN at first.
Then it can be indexed here.
When the call service type is “Tone
play service, CAT_SEND_TONE”,
to specify the ID of the tone to be
played
number of CAMEL access
subscription information of the
calling subscriber. This
command ADD CAINFO at
first.
Then it can be indexed here. When
the call service type is “equal
Number access: CIC of the operator where
RST2 analysis result the subscriber is located” or “equal
2 access: non-local-network CIC,
this parameter must be
configured.
“OVERLAY: CAMEL service
triggered by MO”, or
“OVERLAY:
configured. When the call service
type is other types except the
above-listed, number analysis
result 2 must be fixed to 0
number of CAMEL access
subscription information of the
called subscriber. This parameter
must be defined by command
ADD CAINFO at first. Then it can
Number be indexed here.
RST3 analysis result When the call service type is
3 “OVERLAY: CAMEL service
triggered by MO”, or
“OVERLAY:
configured. When the call service
above-listed, number analysis
result 3 must be fixed to 0


Name Description
It is used to specify the analysis
index number of the route chain.
This parameter must be defined
by command ADD CHAINAL at
first. Then it can be indexed. This
parameter takes effect only when
Route chanin the call service type is outgoing
CHAINAL service (including various outgoing
analysis index
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
When the call service type is “MNP
Length of the outgoing routing”, it is configured
RNLEN carried routing to the length of the carried routing
number number. When the call service
above-listed, it must be fixed to 0
is an integer 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.
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,
Minimum digit the system considers that the
MINLEN length of number format is wrong, and
numbers releases the call.
During a local-office-originated
call, if the received digits are
shorter than this length, the
system considers that the number
format is wrong, and releases the
call.
For the OVERLAY prefix incoming
service, the system gets the
length of the OVERLAY prefix
according to the minimum digit
length of numbers. Therefore, it is
required to configure the
minimum digit length of numbers
to the length of the OVERLAY
prefix. Otherwise, procedures
cannot be correctly processed

215

Name Description
is an integer 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.
During an incoming call, it is
the basis of whether to wait
for subsequent digits. If the
Maximum received digits reach this
MAXLEN digit length of length,
numbers the system does not wait for
subsequent digits.
During a local-office-originated
call, if the received digits are
longer than this length, the system
determines whether to continue
or release the call according to
flag “No call when the called
number exceeds the length” in
the option enabling configuration.
If the system determines to
continue the call, it cuts the
exceeding digits
OVERLAY
priority,
including:
NO (No
priority):
Trigger the
intelligent
service based
on CSI at It is used to the priority
first, and relationship between triggering
then trigger the intelligent service based on
the intelligent CSI and triggering the intelligent
service again service based on OVERLAY. The
OVLYPRI
based on system adopts “no priority” by
OVERLAY default. When the call service
HCSI (Higher type is “OVERLAY: CAMEL service
than the CSI triggered by MO”, this parameter
in priority): is effective. Otherwise, this
Trigger the parameter is ineffective
intelligent
service based
on OVERLAY
at first, and
then trigger
the intelligent
service again
based on CSI


Name Description
Voice channel
release mode,
including:
CING (calling
control
release):
The calling
party controls
whether to
release the
call. In this
mode, when
only the called
party hooks on,
the call still
can continue.
CED (called
control
release):
The called It is an optional parameter. It
party controls indicates a resource release mode
whether to when subscribers hook on. In
REL release the general, select NO. Select CED for
call. In this such special numbers as 110 and
mode, when 119
only the calling
party hooks
on, the call
still can
continue.
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
It is an optional parameter, with
a default of 1. For calls to other
Type of the office in the local network, select
NET destination the signaling network where the
network destination office is located. For
intra-office calls, this option is
meaningless.

217

Name Description
Number
address
attribute,
including:
DEF (default
attribute): Do
not replace
the address
attribute of
the analyzed
number.
INT
(international
number):
Replace the
address
attribute of
the analyzed
number with
international It is an optional parameter. It
number. is used to replace the address
NAT (national attribute of the analyzed
NAT
number): number.
Replace the In general, it is set to DEF, or is
address set according to the requirements
attribute of of the peer end
the analyzed
number with
national (valid)
number. LOC
(local
number):
Replace the
address
attribute of
the analyzed
number with
local number.
UNK (attribute
unknown):
Replace the
address
attribute of
the analyzed
number with
unknown
Transforming
the calling
number again,
including:
NO (Not used to specify whether it is
allowed): It is allowed to transform the calling
OPDDI- not allowed to number again in the subsequent
CONT transform the call procedures when the calling
calling number number was already
again in the transformed
subsequent call once. The system adopts NO by
procedures. default
YES (allowed):
It is allowed
to transform
the


Name Description
calling number
again in the
subsequent call
procedures.
Transforming
the called
number again,
including:
NO (Not
allowed): It is It is an optional parameter. It is
not allowed to used to specify whether it is
transform the allowed to transform the called
TPDDI- called number number again in the subsequent
CONT again in the call procedures when the called
subsequent call number was already
procedures. transformed
YES (allowed): once. The system adopts NO by
It is allowed to default
transform the
called number
again in the
subsequent call
procedures
the number stream transform
Calling-number index of the calling-number
immediate transform.
OPDDI immediate Immediate
transform
transform immediately makes the
index
calling number transformed. This
command ADD DDI at first. Then
it can be indexed here
Called-number index of the called-number
immediate transform.
TPDDI immediate Immediate
transform
transform immediately makes the
index
called number transformed. This
index of the calling-number
delay
transform. Delay transform takes
effects in the IAM message at the
Calling-number outgoing side instead of making
OPDLYDDI delay the calling number transformed
transform immediately. This parameter must
index be defined by command ADD DDI
at first. Then it can be indexed
here.
According to the IAM message at
the outgoing side, perform the
calling-number delay transform
here, and then perform the

219

Name Description
calling-number delay transform in
the number pre-analysis
index of the called-number
Called-number immediate transform.
TPDLYDDI delay Immediate
transform transform immediately makes the
index called number transformed. This
It is the number stream transform
index of the called number in the
B-interface outgoing call request message
number between the MSC and the VLR.
DDIOVERB The transform purpose is to
transform
index facilitate the VLR judging the toll
call authority. This parameter
ADD DDI at first. Then it can be
indexed here
Whether to
support the
interworking
between video
calls, including:
LSUP:
Local-network
subscribers
support the
interworking
between
video calls by
default). The It is an optional parameter. It is
call continues. used to specify whether to support
IWVEDIO
the interworking between video
OSUP: calls. The default value is LSUP
Subscribers in
other networks
support the
interworking
between video
calls). The call
continues.
ONSUP:
Subscribers
in other
networks do
not support
the
interworking
It is used to specify the maximum
call duration allowed for a call.
Maximum When the duration of a call
reaches
TIMELMT call duration
the maximum call duration, the
(minute)
system automatically release the
call. If it is unnecessary to restrict
the maximum call duration, adopt
the default value of 0


Name Description
It is an optional parameter. It
is used to specify the DAS for
analyzing the called number
again
when the call service type is
AUXDAS Assistant DAS outgoing service, and when the
connection between the local office
and the mutually-backed-up office
is broken in the mutual backup
dual-homing networking. This
command ADD DAS at first. Then
Sending A6 It is used to specify the number

of digits that the system receives
signal after
receiving enough to send A6 signal to the
A6 front office. This parameter only
how many
digits during takes effect during incoming
incoming calls using Channel Associated
calls Signaling (CAS)

Toll prefix + is an integer, ranging from 0
PFXLEN to 15. When the call service
Area code
length type is national/international toll
service, this parameter needs to
be configured
Enabled In general, select CCS7
options Refer (Automatically sending the
ENOPT calling number when using
to Table 94 for CCS7
details
for outgoing services) and (No call
when the called number exceeds
the maximum digit length)
It is used to specify the bearer
analysis result index number of
the called number associated with
the fax service. This parameter
must be defined by command ADD
BEARRST at first. Then it can be
indexed here. This parameter
FAXIDX Fax analysis is configured to implement the
resutl index routing service based on the
bearer capability. For the fax
service,
if the associated bearer analysis
result index of the called number
is configured, the call adopts the
associated bearer analysis result
of the called number, thus flexible
routing is implemented

221

Name Description

the called number associated
with the analog video service.
by command ADD BEARRST at
first. Then it can be indexed here.
Analog video This parameter is configured to
AVIDX analysis result implement the routing service
index based on the bearer capability.
For the analog video service, if
the associated bearer analysis

with the digital video service. This
command ADD BEARRST at first.
Then it can be indexed here. This
Digital video parameter is configured to
DVIDX analysis result implement the routing service
For the digital video service, if
the associated bearer analysis

the called number associated with
the analog data service. This
Analog data This parameter is configured to
ADATAIDX analysis result implement the routing service
For the analog data service, if the
index of the called number is
configured, the call adopts the


Name Description
with the digital data service. This
Digital data This parameter is configured to
DDATAIDX analysis result implement the routing service
For the digital data service, if the
index of the called number is
configured, the call adopts the
Whether to
play the DDC
tone,
including: It is used to specify whether to
play the DDC tone in the local
NONE (Not office. The system adopts
playing the NONE by default. The purpose
DDC tone): It of configuring whether to play
DDCPLAY is not required the DDC tone in the number
to play the analysis configuration is to
DDC tone in avoid
the local no tone play or repeated tone play
office. caused by inconsistent tone play
PLAY (Playing configuration during inter-office
the DDC tone): DDC calls
It is required
to play the
DDC tone in
the local
office.
Voice Activity
Detection
(VAD) flag,
including:
CLOSE: Not
starting the It is used to specify whether to
VAD VAD function. start the VAD function. The system
OPEN: Start- adopts INVALIDby default
ing the VAD
function.INVA-
LID: The VAD
function is in-
valid
It is used to specify between which
opposite-end MGW and the local
MGW the TDM backup route is
adopted. The QOSs between the
Opposite-end local MGW and all opposite-end
OPPMGWID MGWs can be found through
MGW ID
automatic test calls. When the
QOS difference between the
opposite-end MGW and the local
MGW is specified, the call adopts
the TDM backup route

223

Name Description
Call type
priority,
including:
INVALID
: The It is used to specify the call
call priority is priority. The system adopts
invalid. INVALID by default. The call
HIGHEST: priority has two functions. In one
The case, in the softswitch office in
call has the the toll softswitch network, the
highest priority. voice coding format can be
CALLSERV- dynamically selected according to
PRILVL HIGHER: The
call has a the call priority and the load on
priority one the IP bearer network. In another
level lower than case, based on the combined
the highest information of office ID and
priority. priority configured in the number
analysis configuration, the final
NORMAL: priority of a call is got to perform
The call has load control
a priority one
level lower
than the
higher
priority.
LOW: The call
has the
lowest
priority
It is used to specify the re-routing
route chain ID. This parameter
ADD RERTS at first. Then it
can be indexed here. When flag
RRTO in enabled options takes
effect, the re-routing route chain
takes effect too. For an outgoing
call procedure, if the call fails,
and the corresponding failure
cause is configured with “Enabling
rerouting for failure” in the R_ICP
configuration, re-select the route
Re-routing from this route chain according to
RERTS the re-routing route chain.
route chain
For an incoming call using ISUP,
TUP, or BICC signaling, when the
call procedure is an outgoing
procedure, and the call fails
before
the IAM message is sent, the
re-routing route chain serves as
the standby route, and is not
controlled by RRTO.
If route chain analysis is
configured, the re-routing
route chain here is invalid.
In this
case, use the re-routing route
chain configured in the route chain
analysis


Name Description
It is used to specify whether the

outgoing route chain got from
number analysis is an inter-MGW
route chain. The system select
Inter-MGW NO by default. If YES is selected,
route chain or the routes in the outgoing route
not, including: chains will not be selected for the
NO: The outgoing route. The outgoing
outgoing route route will be got after perform
chain got number analysis again according
from number to the associated called number
analysis is not DAS configured in the outgoing
INCHAIN an inter-MGW route chain.
route chain. This parameter is used in the
YES: The following cases:
outgoing route One virtual outgoing route chain
chain got is got based on number analysis
from number at first, and then the real outgoing
analysis is route is got based on the called
an inter-MGW
number DAS associated with the
route chain
virtual outgoing route chain.
When one MSCS controls multiple
areas, the outgoing route chain
facilitates subscriber management
It is used to specify the set of

recommended MGWs for outgoing
service. In the case of multiple IP
domains, if one MSCS manages
multiple MGWs, and these MGWs
belong to different IP domains,
RECMDMG- Recommended the set of recommended MGWs
WNODEID MGW nodes for outgoing service needs to be
configured. The MGW set here
should be a sub-set of the MGW
set supported by outgoing service.
by command ADD TOPO at first.
Then it can be indexed here
TABLE 93 CALL SERVICE TYPES
Call
Service Meanings Description
Types
Indicates that the subsequent call
NULL Vacant number procedures are processed based
on the procedure of processing
vacant numbers
Local-
LLC network local-
procedures are processed based
office/commo
n on the local service procedure
service

225
Call
Types
Indicates that the subsequent

Local-network call procedures are processed
LOL outgoing/local- based on the local-call service
call service procedure. The mobile-to-fixed
local outgoing call service is
usually analyzed to this type

Local-network call procedures are processed
based on the local rural (network)
LORU outgoing call service procedure.
outgoing/rural
(network) call The mobile-to-fixed rural
service outgoing call service is usually
analyzed to this type

Domestic toll procedures are processed based
DWTM (intra-region) on the domestic toll (intra-region)
manual service manual service procedure. In
general, it is not recommended to
configure this service type

DWTA (intra-region) on the domestic toll (intra-region)
automatic automatic service procedure. In
service general, it is not recommended to

DBTM (inter-region) on the domestic toll (inter-region)
manual service manual service procedure. In
general, it is not recommended to

DBTA (inter-region) on the domestic toll (inter-region)
automatic automatic service procedure. The
service domestic toll call service is

International procedures are processed based
INTM toll manual on the international toll manual
service service procedure. In general, it
is not recommended to configure
this service type

International call procedures are processed
INTA toll automatic based on the international toll
service automatic service procedure. The
international toll call service is

Call
Types

call procedures are processed
Local-office paid based on the local-office paid
LSPA
special service special service procedure. The
local-office paid special service is

Local-office free based on the local-office free
LSFR
local-office free special service is

Outgoing paid on the outgoing paid special
OUPA
special service service procedure. The outgoing
paid special service is usually

Outgoing free based on the outgoing free
OUFR
outgoing free special service is

Additional based on the additional service
DEPS
service procedure. In general, it is not
recommended to configure this
service type

Intra-office
CENTL call within
the CENTREX on the intra-office call procedure
business within the CENTREX business
group group.

Outgoing call
CENTO within the
on the outgoing call procedure
CENTREX
business within the CENTREX business
group group

Intelligent
TELCA procedures are processed based
Ntwork service
call on the intelligent network service
call procedure
Equal access: Indicates that the subsequent

CIC of the call procedures are processed
EQACL operator where based on the procedure of “Equal
the subscriber is access: CIC of the operator where
located the subscriber is located”

227
Call
Types

Equal access:
EQACO call procedures are processed
non-local-
based on the procedure of “Equal
network CIC
access: non-local-network CIC”

based on the tone play service
Tone play serv- procedure. After calling the
STONE ice, CAT_SEND- number that is analyzed to this
_TONE type, the system will directly play
the tone according to the tone
ID configured in number analysis
result 1

Toll DDC based on the toll DDC incoming
DDCI call service procedure. The toll
incoming call
incoming DDC call that needs to
be routed in the local office is

on the local DDC call service
DDCC Local DDC call procedure. The local DDC call
(dialing the MSISDN number) that
needs to be routed in the local
office is analyzed to this type

Toll DDC based on the toll DDC outgoing
DDCO
outgoing call call service procedure. The toll
outgoing DDC call is analyzed to
this type

Local DDC based on the local DDC outgoing
DDCCO
outgoing call call service procedure. The local
outgoing DDC call is analyzed to
this type

MSC common on the MSC common service
MSCO procedure. The call (dialing the
service
MSISDN number) that needs to
be routed in the local office is

MSC local-
network
based on the MSC local-network
MSLL local-office
service (only local-office service procedure. It
is used to analyze the roaming
for roaming
numbers) numbers and handover numbers
of the local office

Call
Types

MSC local
outgoing procedures are processed based
MSLO service (only on the local outgoing service
procedure. The local outgoing call
for roaming
of roaming numbers is analyzed
numbers)
to this type

Calling-number
CINRE procedures are processed based
incoming call
on the calling-number incoming
restriction
call restriction procedure

MSC national call procedures are processed
MSLTE toll call (only based on the MSC national toll
for roaming call service procedure. The toll
numbers) outgoing call of roaming numbers
is analyzed to this type
Automatic Indicates that the subsequent

AAC call procedures are processed
response
number based on the automatic response
number service procedure

OVERLAY procedures are processed based
OVPRE prefix incoming on the OVERLAY prefix incoming
service service procedure. The OVERLAY
prefix incoming call is analyzed to
this type

OVERLAY call procedures are processed based
OVCS on the OVERLAY call service
service
procedure. It is used for the IGW
system
MSC Indicates that the subsequent

international call procedures are processed
MSITE toll call (only based on the MSC international
for roaming toll call service procedure. The
numbers) international toll outgoing call is

IP procedures are processed based
IP fixed service
on the IP fixed service procedure.
It is used for the IGW system

SSP charging
SSP procedures are processed based
and
on the SSP charging and querying
querying
service service procedure.
Non-SSP
NSSP charging and Reserved
querying service

229
Call
Types

IP mobile based on the IP mobile service
IPMO
service procedure. The IP service in the
mobile system is analyzed to this
type
IP service dialed
INSIP by intelligent- Reserved
network
subscribers

Independent IP on the independent IP service
ALIP
service procedure. The independent IP
incoming call is analyzed to this
type
OVERLAY: Indicates that the subsequent call

OVMO MO-triggered procedures are processed based
CAMEL service on the “OVERLAY: MO-triggered
CAMEL service” procedure
OVERLAY: Indicates that the subsequent call

OVMT MT-triggered procedures are processed based
CAMEL service on the “OVERLAY: MT-triggered
CAMEL service” procedure

MNP Mobile number
portability
on the MNP service procedure

MNP MNP procedures are processed based
MNPR outgoing routing on the MNP outgoing routing
service procedure

SIP outgoing procedures are processed based
SIPO
call on the SIP outgoing call service
procedure

H323 call procedures are processed
H323 call
based on the H323 call service
procedure.

Mobile
MOIMC procedures are processed based
emergency
on the mobile emergency special
special service
service procedure

Call
Types

Independent based on the independent SSP
SSSP SSP outgoing outgoing service procedure. The
service SSSP (Independent SSP outgoing
service) in the analysis result of
the called number is used for the
IGW system
IGW Indicates that the subsequent

IGWA supplementary call procedures are processed
service (only for based on the IGW supplementary
IGW) service procedure
A new DAS is got through number

DAS service
DASA (virtual IGW) analysis, which is used for the
(only for IGW) subsequent analysis of the called
number

Local valid CIC procedures are processed based
OCIC on the local valid CIC service
service
procedure. This parameter is
reserved
Outgoing
paid special
OUPAOD service (can
on the outgoing paid special
be dialed by
service (can be dialed by the
the
defaulting defaulting subscribers) procedure
subscribers)
Local-office procedures are processed based
LINTS intelligent on the local-office intelligent
service service procedure. It is used for
the IGW system
SHLR querying Indicates that the subsequent call

SHLRQ service (only for procedures are processed based
IGW) on the SHLR querying service
procedure

IGW common based on the IGW common
IGWC service (only for service procedure. The call to
IGW) PHS subscribers, which needs to
be routed in the local office, is
IGWSSP Indicates that the subsequent call

ISSPQ charging and procedures are processed based
querying service on the IGW SSP charging and
(only for IGW) querying service procedure
IGW local-office Indicates that the subsequent

IGWLF call procedures are processed
free special
based on the IGW local-office free
service
special service procedure

231
Call
Types

IGW local-office
IGWLP call procedures are processed
paid special
based on the IGW local-office
service
paid special service procedure
IGWOVERLAY Indicates that the subsequent

IGWOV prefix incoming call procedures are processed
service based on the IGWOVERLAY prefix
incoming service procedure

IGW toll DDC procedures are processed based
IGWDDCIN
incoming call on the IGW toll DDC incoming call
service procedure

IGWDDCL- IGW local DDC procedures are processed based
OCAL call on the IGW local DDC call service
procedure

TEST Test call procedures are processed based
on the test call service procedure.
It is used to analyze test calls
TABLE 94 ENABLED OPTIONS
Enabled Meanings Description

Options
It indicates whether the
outgoing TUP signaling
carries the calling
number. When the local
office actively sends the
calling number, it sends
an IAI message of TUP
signaling to the peer-end
Automatically sending office, carrying the
CCS7 the calling number when calling number.
using CCS7 for outgoing Otherwise, the local
services office sends an IAM
message of TUP
signaling to the peer-end
office, not carrying
the calling number.
For ISUP signaling, it
indicates whether the
local MSC number is
filled in the location
number information
Indicates whether to
set the type of the
calling subscriber in the
Changing the type of outgoing IAM message
CHGK
calling subscribers of
ISUP or BICC signaling
to the calling subscriber
types flexibly configured
in security variables

Options
Indicates that the
analyzed number is
CHGN Changing the number changed, and the system
notifies the calling
subscriber by playing
the tone
DELA Delayed dialing of the Reserved

special service
166-voice- Indicates that the call

MAIL is a 166-voice-mailbox
mailbox service
service
NSCP Not waiting for SCP Reserved

responses
For incoming calls
using ISUP, TUP, or
BICC signaling, the
call procedure is an
outgoing call
RRTO Rerouting after outgoing procedure.
failure When the local office
does not receives a REL
message after sending
an outgoing IAM
message to the peer-
end office, this option
control whether
rerouting is allowed
NETF IN forward message Reserved
VNUM Virtual number Reserved
HRA High rate Reserved
Indicates whether the
call triggers the IN
service of the calling
number. This option is
used for the case where
Not triggering IN service the IN service of the
NTC
of the calling number calling number cannot
be triggered when the
call to the IN subscriber
is forwarded or when
some special numbers
are dialed
No call when the called system releases the call
NCEL number exceeds the if the analyzed number
length exceeds the configured
maximum digit length
call is an incoming
Interception number call returned from the
LSIN
incoming interception center.
This
option is only used in the
IGW system

233

Options
local office sends a
ringing message of the
called subscriber and a
“connect” message to
Sending the “connect” the calling subscriber
CON message in advance at the same time (that
(only for IGW) is, sends a “connect”
message to the calling
subscriber before the
called subscriber
answers
the call). This option is
only used in the IGW
system
number section needs
to be transformed in
the SHLR during call
origination. In the SHLR
mixed networking,
common call origination
procedures need to
interact with the SHLR
SHLRF Not triggering SHLR to get the calling
query logic number, and the
called physical number.
However, in the specific
calls, the called number
needs no transform. In
this case, select this
option in the number
analysis result. This
option is only used in the
IGW system
incoming call restrain
the SHLR from returning
the IN access code. This
option is used to prevent
repeatedly triggering IN
services. This option is
only used in the IGW
SHLRG Over net number in SHLR system

routing query in the
SHLR is forcibly
performed during IP
Needing to judge the IP calls. This option is only
JUDG resource used in the IGW system
Indicates whether
incoming calls trigger
the HOMEBOX service
in the local office. This
Restraining HOMEBOX option is only used in
REBO service the
IGW system
Example: Configure the called number analysis with the fol-
lowing requirements.

� Analyzer entry: 1
� User alias: TPDNAL1
� Analyzed number: 13902099
� Call service type: MSC common service
ADD
TPDNAL:ENTR=1,DIGIT="13902099",NAME="TPDN
AL1",SPECRST=0,SPECIDX=0,CAT=MSCO,RST1=0,RST2
=0,RST3=0,CHAINAL=0,RNLEN=0,MINLEN=3,MAXLEN
=20,OVLYPRI=NO,REL=NO,NET=1,NAT=DEF,OPDDICO
NT=NO,TPDDICONT=NO,OPDDI=0,TPDDI=0,OPDLYDD
I=0,TPDLYDDI=0,DDIOVERB=0,IWVIDEO=LSUP,TIMEL
MT=0,AUXDAS=0,A6=0,PFXLEN=0,INSRV=INM,FAXIDX
=0,AVIDX=0,DVIDX=0,ADATAIDX=0,DDATAIDX=0,DD
C
PLAY=NONE,VAD=CLOSE,CALLSERVPRILVL=INVALID,RE
RTS=0,INCHAIN=NO,BICT=NO,ICT=0,ICTT=10,GNM=NO
RMAL,STBILL=INVALID,HOPDAS=0;
Example: Configure the roaming number analysis of the local
office with the following requirements.
� Analyzer entry: 1
� User alias: TPDNAL1
� Analyzed number: 15902099
� Call service type: MSC local service
ADD
TPDNAL:ENTR=1,DIGIT="15902099",NAME="TPDN
AL2",SPECRST=0,SPECIDX=0,CAT=MSLL,RST1=0,RST2
=0,RST3=0,CHAINAL=0,RNLEN=0,MINLEN=3,MAXLEN
=20,OVLYPRI=NO,REL=NO,NET=1,NAT=DEF,OPDDICO
NT=NO,TPDDICONT=NO,OPDDI=0,TPDDI=0,OPDLYDD
I=0,TPDLYDDI=0,DDIOVERB=0,IWVIDEO=LSUP,TIMEL
MT=0,AUXDAS=0,A6=0,PFXLEN=0,INSRV=INM,FAXIDX
=0,AVIDX=0,DVIDX=0,ADATAIDX=0,DDATAIDX=0,DD
C
PLAY=NONE,VAD=CLOSE,CALLSERVPRILVL=INVALID,RE
RTS=0,INCHAIN=NO,BICT=NO,ICT=0,ICTT=10,GNM=NO
RMAL,STBILL=INVALID,HOPDAS=0;
Trunk Data Configuration

END OF STEPS
Overview
The related operations of the trunk data configuration are as fol-
lows.

235

When the A
interface and Ai
interface adopts
Creating a DT the TDM bearer,
or when MGWs ADD TG DT
trunk group
are interconnected
through the TDM
bearer, configure
DT
trunk groups
1 Creating an When the ATM
ATM trunk bearer is adopted ADD TG ATM
between MGWs,
group
configure ATM trunk
groups
When the IP bearer
is adopted
between MGWs,
Creating a RTP configure BICC ADD TG RTP
trunk group trunk groups.
When the MSCS
servers as a MGCF,
configure SIP trunk
groups for MGWs
DT, ATM, and RTP
Creating a PCM trunk groups all ADD SPCM
system need to be
configured with PCM
systems
When the MGWs
managed by
2 one MSCS are
interconnected
through TDM
Creating a circuits, no
PCM system trunk ADD INPCM
between MGWs group or trunk
route needs to
be configured,
and only PCM
systems between
the MGWs need
Creating a DT Trunk Group to
be configured

� The adjacent office to which the trunk group points is created.
system.
Context When the Ai interface adopts the TDM bearer, or when IM-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 2G MSC/PSTN office

(4~8 trunk groups are recommended). To implement load
sharing, it is required to allocate roughly the same number of Ai
interface circuits to each CMP module.
system tree.
SET:NEID=11;
2. Create a DT trunk group by executing command ADD TG DT.
DT is shown in Table 95.
TABLE 95 PARAMETERS IN THE ADD TG DT COMMAND

Name tion
It is a mandatory
parameter. It is used
to define a trunk
TG Trunk group ID group, and needs to be
planned in the resource
management system
in advance
It is a mandatory
parameter. It is
used to specify the
corresponding
OFC ID of the office where office of
the trunk group belongs the trunk group. This
parameter must be
defined by command
ADD ADJOFC at first.
Then it can be indexed
here
It is a mandatory
parameter. It indicates
Module where the trunk a service module.
MODULE Different trunk groups
group belongs
to the same office
need to be allocated to
different CMP modules
It is a mandatory
Node No. of the MGW parameter. Select the
ND where the trunk group MGW topology node
belongs connected with the 2G
MSC/PSTN node
It is an optional
of 0~50 characters. It
NAME User alias is used to specifically
describe a trunk group
to make it easily
recognized

237

Name tion
Inter-office line signal
identification. Options
include:
� BSC: BSC Ground
Circuit
� TUP: Interoffice
Common Channel
Signaling TUP It is an optional
� ISUP: Interoffice identify the line type of
Common Channel this trunk. Select it
SIGLINE
Signaling ISUP according to inter-office
� DLC1: Interoffice signaling. For the Ai
Channel Associated interface, select ISUP
Signaling or TUP
DL/DC(1)
� R2: R2 Signaling
� BICC: BICC Type
� ANU: ANU Signaling
� SORMUP: SORMUP
Signaling
Trunk group types,
three types:
IN (incoming trunk
group): Indicates
processes the
incoming
calls from the peer-end
office. It is an optional
parameter. If BSC
OUT (outgoing trunk is selected for the
KIND group): Indicates that inter-office line
the local office only signal
processes the outgoing identification, it must be
calls to the peer-end configured to BIDIR
office.
BIDIR (Two-way trunk
group): Indicates
processes both the
incoming calls from the
peer-end office and
the outgoing calls to
the peer-end office


Name tion
direction, including the
following three types:
NODIR: The inter-office
without direction. It is an optional
BWAY BACK: The inter-office parameter. Select
bearer is established NODIR for DT trunk
based on the backward groups
mode.
FORWD: The
inter-office bearer is
established based on
the forward mode
It is an optional
parameter, ranging from
Overload control 0 to 100, with a default
THD of 100. This parameter
threshold
takes effect when levels
of congestion occur and
load control is required
Circuit selecting modes,
including:
MIN: Every time when
the system selects a
trunk circuit, it always
begins with the circuit
with the minimum
number. This mode can
implement the preferred
plan of trunk circuits.
MAX: Every time when
the system selects a It is an optional
trunk circuit, it always parameter. It is used to
begins with the circuit specify the trunk circuit
with the maximum selecting policy of the
number. This mode can system within this trunk
implement the preferred group, with a default of
plan of trunk circuits. CYC. If this No.7 trunk
CICSEL group is a two-way
CYC: Every time when trunk group, it is
the system selects recommended to set the
a trunk circuit, it
circuit selecting mode
always begins with to ODD/EVEN mode
the circuit next to the to prevent contention
one previously when two exchanges
selected.
select circuits
Suppose the numbers
of the trunk circuits in a
trunk group in
ascending order are
“TKC0, TKC1,
…. , TKCn”. If TKC0
is selected at the first
in the order of “TKC0T
KC1…TKCnTKC0
TKC1…TKCn”.
ODD: Every time when

239

Name tion
selects the circuit with
an odd number.
EVEN: Every time when
an even number.
IDLE: Every time when
selects the idlest circuit.
BUSY: Every time when
selects the busiest
circuit
It is an optional
to analyze the called
DAS for the called number in an incoming
DAS call. This parameter
number
must be defined by
command ADD DAS at
first. Then it can be
indexed here
It is used get the name

of the IMS domain
DAS for the domain where the called party
name of the called is located through
SIPDAS analyzing the called
number during a SIP
outgoing call number during a SIP
outgoing call. It is only
used for RTP trunk
groups
the calling number in
DAS for the calling an incoming call. This
OPDAS parameter must be
number
defined by command
ADD DAS at first. Then
It is used to pre-analyze
the called number in
an incoming call. This
PREDAS DAS for pre-analyzing parameter must be
the called number defined by command
ADD PREDAS at first.
here


Name tion
It is the index of
the incoming called
number transform.
DDI Incoming called number This
transform ID
parameter must be
defined by command
ADD DDI at first. Then
It is the index of
the incoming calling
number transform.
OPDDI Incoming calling This
number transform ID
parameter must be
defined by command
It is an optional
parameter, which is
an integer ranging
from
Minimum national
MINNAT 0 to 26, with a default
number length
of 0. It is used to
specify the minimum
digit length of the
national incoming call
It is an optional
parameter, which is
an integer ranging
from
Maximum national
MAXNAT 0 to 26, with a default
number length
of 26. It is used to
specify the maximum
digit length of the
It is an optional
parameter, which is
an integer ranging
from
MININT Minimum international 0 to 26, with a default
number length of 0. It is used to
specify the minimum
digit length of the
called number during an
international incoming
call
It is an optional
parameter, which is
an integer ranging
from
MAXINT Maximum international 0 to 26, with a default
number length of 26. It is used to
specify the maximum
digit length of the
called number during an
call

241

Name tion
Incoming register
signaling flag, including It is an optional
INREG options: INVALID, parameter, with a
MFC, MFP, DTMF, DP default of INVALID
and MF
Outgoing register
signaling flag, including It is an optional
OUTREG options: INVALID, parameter, with a
MFC, MFP, DTMF, DP default of INVALID
and MF
It is an optional
The maximum length of parameter. It ranges
COLEN
CAS calling number from 1 to 32, with a
end default of 10.
It is an optional
integer ranging from
1 to 100, with a
default of 100. After
the trunk circuit usage
is configured, when
the
ratio of busy circuits to
all circuits in this trunk
BUSYRATE Trunk circuit usage group exceeds this
value, congestion occurs
in this trunk group.
After the congestion
is relieved, report the
trunk congestion times
and congestion duration
in the performance
statistics. This
parameter does not
take effect when it is
configured to 100
It is an optional
parameter. After this
DAS is configured, if
the local office serves
as a GMSC, this DAS
ROAMDAS DAS for roaming is preferred for the
numbers returned roaming
numbers. Otherwise,
the roaming number
DAS configured in
the number analysis
template is used


Name tion
It is an optional
Q850 customization parameter. It ranges
Q850CCIDX
index from 0 to 65535, with a
default of 0.
It is an optional
parameter, associated
ID of signaling with the inter-office
SMENTERID signaling modification
modification entrance
entrance. It ranges
default of 0
Example: Create a DT trunk group to the 2G MSC office with

the following requirements:
� User alias: MSC28
� No. of the CMP module where the trunk group
belongs: 3
� MGW topology node No.: 101
ADD TG
DT:TG=28,OFC=28,MODULE=5,ND=101,NAM
E
="MSC28",SIGLINE=ISUP,KIND=BIDIR,BWAY=NODIR,TH
D=100,CICSEL=ODD,DAS=0,SIPDAS=0,OPDAS=0,PRED
AS=0,DDI=0,OPDDI=0,MINNAT=0,MAXNAT=26,MININT
=0,MAXINT=26,INREG=INVALID,OUTREG=INVALID,COLE
N=10,BUSYRATE=100,ROAMDAS=0,Q850CCIDX=0,SME
NTERID=0,MLPPDM=4294967295,DISINDEX=0;
E ND OF STEPS
Creating an ATM Trunk Group

system.
� The adjacent MGW office to which the trunk group points is
created.
Context When the ATM bearer is adopted between MGWs, configure ATM
trunk groups.

243

system tree.
SET:NEID=11;
2. Create an ATM trunk group by executing command ADD TG
ATM.
ATM is shown in Table 96.
TABLE 96 PARAMETERS IN THE ADD TG ATM COMMAND

Name tion
It is a mandatory
to define an ATM trunk
TG Trunk group ID group, and needs to be
planned in the resource
management system
in advance. It is a
global unified number
It is a mandatory
parameter, ranging
used to specify the
ID of the office where corresponding office of
OFC the trunk group. This
the trunk group belongs
parameter must be
defined by command
ADD ADJOFC at first.
here
It is an optional
of 0~50 characters.
NAME User alias
It is used to specifically
describe a trunk group
to make it easily
recognized
It is a mandatory
parameter, which is
an integer, ranging
MODULE Module where the trunk from
group belongs
1 to 127. It is used to
specify the SMP module
of processing traffic on
this trunk group
It is a mandatory
parameter, which is
an integer, ranging
Node No. of the MGW from
ND where the trunk group 1~2048. It is used to
belongs specify the topology
node No. of the MGW
providing bearer, which
is controlled by the local
MGCF


Name tion
It is an optional
Inter-office line signal parameter. It is used to
SIGLINE identification, including identify the line type of
BICC (BICC signaling) this trunk, with a default
of BICC
Trunk group types,

three types:
IN (incoming trunk
group): Indicates that
the local office processes
the incoming calls from It is an optional
the peer-end office. parameter. It is used
OUT (outgoing trunk to specify the call
group): Indicates that connection direction
KIND in this trunk group in
the local office only
processes the outgoing the local office, with a
calls to the peer-end default of BIDIR. It
office. should be negotiated
with the peer-end
BIDIR (Two-way trunk office
group): Indicates that
the local office processes
both the incoming calls
from the peer-end office
and the outgoing calls
to the peer-end office
direction, including the
following three types:
NODIR (No direction):
The inter-office bearer
It is an optional
is established without
direction.
BWAY specify the inter-office
BACK: The inter-office bearer establishment
bearer is established direction, with a default
based on the backward of NODIR
mode.
FORWD: The
inter-office bearer is
established based on the
forward mode
It is an optional
parameter, ranging from
Overload control 0 to 100, with a default
THD of 100. This parameter
threshold
takes effect when levels
of congestion occur and
load control is required

245

Name tion
Circuit selecting modes,
including:
MIN: Every time when
with the minimum
MAX: Every time when
with the maximum
the system selects It is an optional
a trunk circuit, it parameter. It is used to
always begins with specify the trunk circuit
the circuit next to the selecting policy of the
one previously system within this trunk
selected. group, with a default
Suppose the numbers of CYC. If this trunk
CICSEL of the trunk circuits in a group is a two-way
trunk group in ascending trunk group, it is
order are “TKC0, TKC1, recommended to set the
…. , TKCn”. If TKC0 circuit selecting mode
is selected at the first to ODD/EVEN mode to
time, the system will prevent contention when
select the trunk circuit in two exchanges select
the order of circuits
“TKC0TKC 1…
TKCnTKC0TK
C1…TKCn”.
ODD: Every time when
an odd number.
EVEN: Every time when
an even number.
IDLE: Every time when
selects the idlest circuit.
BUSY: Every time when
selects the busiest
circuit


Name tion
It is an optional
DAS for the called number in an incoming
DAS call. This parameter
number
must be defined by
command ADD DAS at
first. Then it can be
indexed here
It is used get the name
of the IMS domain
DAS for the domain where the called party
name of the called is located through
SIPDAS analyzing the called
number during SIP
outgoing calls number during a SIP
outgoing call. It is only
used for RTP trunk
groups
the calling number in
DAS for the calling an incoming call. This
OPDAS parameter must be
number
defined by command
ADD DAS at first. Then
It is used to pre-analyze
the called number in
an incoming call. This
DAS for pre-analyzing parameter must be
PREDAS
the called number defined by command
ADD PREDAS at first.
here
It is the index of
the incoming called
number transform.
DDI Incoming called number This
transform ID
parameter must be
defined by command
It is the index of
the incoming calling
number transform.
OPDDI Incoming calling number This
transform ID
parameter must be
defined by command
It is an optional
integer ranging from 0
Minimum national to 26, with a default of
MINNAT
number length 0. It is used to specify
the minimum digit
length of the called
number during a

247

Name tion
It is an optional
Maximum national to 26, with a default of
MAXNAT
number length 26. It is used to specify
the maximum digit
number during a
It is an optional
Minimum international to 26, with a default of
MININT 0. It is used to specify
number length
the minimum digit
length
of the called number
during an international
incoming call
It is an optional
Maximum international to 26, with a default of
MAXINT 26. It is used to specify
number length
the maximum digit
number during an
call
Incoming register
signaling flag. Options It is an optional
INREG include: parameter, with a
default value of
INVALID INVALID
Outgoing register
signaling flag. Options It is an optional
OUTREG include: parameter, with a
default value of
INVALID INVALID
It is an optional
The maximum length of parameter. It ranges
COLEN
CAS calling number from 1 to 32, with a
end default of 10.
It is an optional
integer ranging from
1 to 100, with a
default of 100. After
the trunk circuit usage
is configured, when
the
BUSYRATE Trunk circuit usage ratio of busy circuits
to all circuits in this
trunk group exceeds
this
value, congestion occurs
in this trunk group.
After the congestion
is relieved, report the
trunk congestion times
and congestion duration
in the performance
248 Confidential and Proprietary Information of ZTE CORPORATION statistics. This

Name tion
parameter does not
take effect when it is
configured to 100
It is an optional
parameter. After this
DAS is configured, if
the local office serves
as a GMSC, this DAS
ROAMDAS DAS for roaming is preferred for the
numbers returned roaming
numbers. Otherwise,
the roaming number
DAS configured in
the number analysis
template is used
It is an optional
Q850 customization parameter. It ranges
Q850CCIDX
index from 0 to 65535, with a
default of 0.
IIt is an optional
parameter, associated
ID of signaling with the inter-office
SMENTERID signaling modification
modification entrance
entrance. It ranges
default of 0
Example: Create an ATM trunk group with the following re-

quirements.
� User alias: MGW102
� MGW topology node No.: 101
� Inter-office line signal identification: BICC
ADD TG ATM:TG=102,OFC=102,MODULE=5,ND=101,NA
ME="MGW102",SIGLINE=BICC,KIND=BIDIR,BWAY=NODI
R,THD=100,CICSEL=ODD,DAS=0,SIPDAS=0,OPDAS=0,P
REDAS=0,DDI=0,OPDDI=0,MINNAT=0,MAXNAT=26,M
ININT=0,MAXINT=26,INREG=INVALID,OUTREG=INVALI
D,COLEN=10,BUSYRATE=100,ROAMDAS=0,Q850CCIDX
=0,SMENTERID=0,MLPPDM=4294967295,DISINDEX=0;
END OF STEPS


249
Creating RTP Trunk Group

� The adjacent IM-MGW office to which the trunk group points
is created.
system.
Context When the IP bearer is adopted between MGWs, configure RTP
trunk groups, which are BICC trunk groups.
system tree.
SET:NEID=11;
2. Creating a RTP trunk group by executing command ADD TG
RTP.
RTP is shown in Table 97.
TABLE 97 PARAMETERS IN THE ADD TG RTP COMMAND
Parameter Parameter
Instruction
Name Description
It is a mandatory
define a trunk group.
TG Trunk group ID This trunk group can be
BICC trunk group or SIP
trunk group. It is a
global
unified number
It is a mandatory
ID of the office where specify the corresponding
OFC the trunk group office of the trunk group.
belongs This parameter must be
ADJOFC at first. Then it
can be indexed here
consisting of 0~50
NAME User alias characters. It is used
to specifically describe a
trunk group to make it
easily recognized


Name Description
It is a mandatory
Module where the integer, ranging from 1
MODULE to 127. It is used to
trunk group belongs
specify the SMP module
of
processing traffic on this
trunk group
Inter-office line
signal identification,
including
SIGLINE � BICC (BICC Select SIP for the MGCF.
signaling)
� SIP (SIP
signaling)
Trunk group types,
three types:
IN (incoming trunk
group): Indicates
processes the
incoming calls from
the peer-end office.
OUT (outgoing trunk It is an optional parameter.
group): Indicates BIDIR is selected by
KIND that the local office default. It should be
only processes the negotiated with the
outgoing calls to the peer-end office.
peer-end office.
BIDIR (Two-way
trunk group):
Indicates that the
local office processes
both the incoming
calls from the peer-
end office and the
peer-end office
direction, including
the following three
types:
NODIR (No
direction): The
inter-office bearer It is an optional parameter.
is established
BWAY without For RTP trunk groups, it
direction. is set according to the
network plan of operators
BACK: The inter-office
based on the
backward mode.
FORWD: The
inter-office bearer
is established based
on the forward
mode

251

Name Description
Threshold for overload It is an optional parameter,

THD ranging from 0 to 100, with
control
a default of 100
Circuit selecting
modes, including:
MIN: Every time
when the system
minimum number.
This mode can
implement the
circuits.
MAX: Every time
when the system
maximum number.
This mode can
implement the
circuits.
the system selects
a trunk circuit, it It is an optional parameter,
always begins with the with a default of CYC. In
circuit next to the one general, the signaling point
previously selected. with big code prefers the
CICSEL Suppose the numbers circuit with an even
of the trunk circuits number, while the one with
in a trunk group in small code prefers the
ascending order are circuit with an odd number.
“TKC0, TKC1, …. , It should be negotiated
TKCn”. If TKC0 is with the peer-end office
selected at the first
in the order of “TKC0
TKC1…TKCnTK
C0TKC1…TKCn”.
ODD: Every time
when the system
circuit with an odd
number.
EVEN: Every time
when the system
circuit with an even
number.
IDLE: Every time
when the system
idlest circuit.


Name Description
BUSY: Every time
when the system
busiest circuit
DAS DAS for the called function, this DAS is used
number to analyze the called
When the called number is
does not need to be
configured
It is used get the name of
the IMS domain where
the called party is located
through analyzing the
SIP outgoing call. If the
outgoing SIP trunk group
is configured with this
DAS, the “invite” message
during a SIP outgoing call
can only contain SIP URL
DAS for the domain mode. If the outgoing SIP
name of the called trunk group is not
SIPDAS configured with this DAS,
number during SIP
outgoing calls configure the URLOPT in
the SIP adjacent office
configuration to decide
whether the outgoing call
uses TEL or SIP URL
mode.
After this DAS is used
on this trunk group, all
outgoing calls on this
trunk group will get the
corresponding domain
name according to the
called number, and then
form a SIP URL
OPDAS DAS for the calling function, this DAS is used
number to analyze the calling
When the calling number is
does not need to be
configured

253
Example: Create a RTP trunk group with the following require-

ments.
� User alias: IM-MGW102
� Inter-office line signal identification: BICC
ADD TG
RTP:TG=1,OFC=102,MODULE=5,NAME="IM-M
GW102",SIGLINE=BICC,KIND=BIDIR,BWAY=NODIR,THD
=100,CICSEL=CYC,DAS=0,SIPDAS=0,OPDAS=0,PREDA
S=0,DDI=0,OPDDI=0,MINNAT=0,MAXNAT=26,MININT
=0,MAXINT=26,INREG=INVALID,OUTREG=INVALID,COLE
N=10,BUSYRATE=100,ROAMDAS=0,Q850CCIDX=0,SME
NTERID=0,MLPPDM=4294967295,SIPRUTS=0,DISINDEX
=0;
END OF STEPS

Creating PCM
� The DT, ATM, or RTP trunk group is configured.
Context The PCM system management data associate the resources on
the MGW with the signaling on the MGCF.
system tree.
SET:NEID=11;
2. Create PCM by executing command ADD SPCM.
SPCM is shown in Table 98.

TABLE 98 PARAMETERS IN THE ADD SPCM COMMAND
Parameter Parameter
Instruction
Name Description
from 1~1000. Select the
trunk group where this PCM
No. of the trunk system belongs from the list
group where of configured trunk groups. It
TG is used to specify the trunk
the PCM system
belongs 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
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.
When the inter-office line
identification of a trunk group
PCM PCM system No. is TUP or ISUP, the PCM
system No. ranges from 0 to
127.
is BICC, the PCM system No.
ranges from 0 to 5999.
is BSC or ANU, the PCM
system No. ranges from 0 to
2047
It is an optional parameter. If
PCM systems belong to a DT
trunk group, this parameter
Number of created needs not be configured. If
NUM
PCM systems PCM systems belong to a RTP
or ATM trunk group, select
the number the created PCM
systems
PCM No. in the

MGW It is an optional parameter. If
the PCM system belongs to a
The corresponding RTP or ATM trunk group, this
trunk group can parameter needs not be
MGWPCM invoke the PCM configured. If the PCM system
resources between belongs to a DT trunk group,
the start PCM No. select the corresponding PCM
in the MGW and the No. in the MGW
end PCM No.

255

Name Description
consisting of 1~50
NAME User alias characters. It is used to
specifically describe the PCM
system configuration to
consisting of 1~50
characters. For DT trunk
E1 E1 identification groups, describes the E1
with any characters, which
can be set to “DTB/SDTB unit
No.-E1 No.”
Digital Distribution consisting of 1~50
DDF Frame (DDF) characters. For DT trunk
location description groups, the DDF location
description can be set to
“Frame No.-Row No.-Port
No.”
Example: Create PCM to the 2G MSC office with the following

requirements:
� No. of the trunk group where the PCM system belongs:
28
� PCM No.: 1
� PCM No. in the MGW: 1-1
� User alias: 2G
MSC1-1. The command is:
ADD SPCM:TG=28,PCM=0,MGWPCM="1"-"1",INFO=6553
5,NAME="2G MSC1-1";
END OF STEPS
Configure a PCM System between

MGWs
� The bearer mode between the MGWs is configured in the
topology configuration.
Context When the MGWs managed by one MGCF are interconnected
through TDM circuits, it is required to configure the PCM systems
between the MGWs. Since the MGWs are interconnected within

the MGCF, 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.
system tree.
SET:NEID=11;
2. Create a PCM system between MGWs by executing command
ADD INPCM.
INPCM is shown in Table 99.
TABLE 99 PARAMETERS IN THE ADD INPCM COMMAND

Name Description
ND1 MGW1 node No. Enter the topology node No. of
MGW1
ND2 MGW2 node No. Enter the topology node No. of
MGW2
PCM PCM system No. Enter the PCM system No. in the
MSCS
PCM No. in It is a mandatory parameter.

ND1PCM Enter the PCM system No. in
MGW1
MGW1
PCM No. in It is a mandatory parameter.

ND2PCM Enter the PCM system No. in
MGW2
MGW2
Management
MODULE Select the No. of the CMP module
module No.
of managing this PCM system
PCMTYPE PCM type It is an optional parameter, with a

default of E1

NAME User alias is in the format of “Adjacent office
MGW1 user alias-Adjacent office
MGW2 user alias-PCM system
No.”
ND1E1 E1 identification can be set to “DTB/SDTB unit
No.-E1 No.”
DDF location It is an optional parameter, which

ND1DDF can be set to “Frame No.-Row
description
No.-Port No.”

257

Name Description

ND2E1 MGW2 E1 ID can be set to “DTB/SDTB unit
No.-E1 No.”
Description of It is an optional parameter, which

ND2DDF MGW2 DDF can be set to “Frame No.-Row
location No.-Port No.”
Example: Add a PCM system between MGWs with the

� PCM system No.: 0
� PCM No. in MGW1 and MGW2: 1
� Management module No.: 3
� User alias: MGW1-
MGW2. The command is:
ADD INPCM:ND1=101,ND2=102,PCM=0,ND1PCM=1,ND2
PCM=1,MODULE=3,PCMTYPE=E1,NAME="MGW1-MGW2";
END OF STEPS

Route Data Configuration

Overview
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 correspon-
dence with the trunk group.
Data Configura- The related operations of the routing data configuration are as
tion follows.

Creating an Each trunk group

1 corresponds to an ADD RT
outgoing route
outgoing route.
Each route
Creating an belongs to a
2 outgoing route route group, and ADD RTS
set each route
group contains
at most 12
routes.
Each outgoing
route group
Creating an belongs to an
3 outgoing route outgoing route ADD CHAIN
chain chain, and each
route chain
contains at most
4 route groups.
Creating a Route
� The outgoing route No. range is set in the resource manage-
ment system.
Context Each trunk group corresponds to an outgoing route.
system tree.
SET:NEID=11;
2. Create route by executing command ADD RT.
The explanation of the main parameters in command ADD RT
TABLE 100 PARAMETERS IN THE ADD RT COMMAND
Parame- Parameter
Instruction
from 1~2000. It exclusively
RT Route No. identifies a route. To facilitate
management, the route No. is
configured to be consistent with
the trunk group No.

259

TG Trunk group No. corresponding to the trunk
group No. in the trunk group
configuration
which is an integer ranging from
Called number 0 to 2048, with a default of 0.
DDI transform index The called number is
during transformed according to this
outgoing calls index during outgoing calls. This
index has no influence on the
incoming calls through this
trunk
which is an integer ranging from
Calling number 0 to 2048, with a default of 0.
OPDDI transform index The calling number is
during transformed according to this
outgoing calls index during outgoing calls. This
index has no influence on the
incoming calls through this
trunk
Whether to delete
It is an optional parameter, with
the prefix of the
a default of NO. If YES is
DLPFX calling number selected, the prefix of the calling
during outgoing number (such as 0/00) will be
calls, including
deleted during outgoing calls
NO and YES
NAME User alias It is an optional parameter,

Example: Create an outgoing route with the following require-

ments.
� Route No.: 28
� Trunk group No.: 28
� User alias:
Rout28. The command
is:
ADD RT:RT=28,TG=28,DDI=0,OPDDI=0,DLPFX=NO,NAM
E="ROUT28",HOPCNT=0,RERTS=0,CLISETIDX=65535;
END OF STEPS
Creating a Route Set

� The outgoing route No. is created.


Context Each route belongs to a route group, and each route group con-
tains at most 12 routes.
Note:
Each outgoing route group can be configured with at most 12
outgoing routes, performing load sharing based on the poll or
percentage mode. One outgoing route can be allocated to
different adjacent offices (such as TMSC1 and TMSC2), thus to
implement traffic load sharing to different offices.

system tree.
SET:NEID=11;
2. Create a route set by executing command ADD RTS.
RTS
TABLE 101 PARAMETERS IN THE ADD RTS COMMAND
Parameter Parameter
Instruction
Name Description
RTS Route group No. which is an integer, ranging
from 1~3000. It is used to
identify a route group
NAME User alias It is used to specifically
describe a route group to
t is an optional parameter. It
is in the format of “No.-Route
No.-Load sharing proportion.
When the percentage is set to
0, the poll mode is adopted.
SEQ: No., which is the location
of the route in the route
Route No. and group.
RTPER load sharing RTVAL: Route No., associated
proportion list with the route group. This
by command ADD RT at first.
PERVAL: Load sharing
proportion of each route in the
route group. If it is set to 0
for all routes by default, the
load is evenly allocated to each
route

261
Example: Create an route set with the following requirements.

� Route group No.: 28
� User alias: Rout28
� Locaiton: 1
� Route No.: 28
�
Percentage: 0.
The command is:
ADD RTS:RTS=28,NAME="ROUT28",RTPER="1"-"28"-"0";
END OF STEPS

Creating an Outgoing Route Chain

� The outgoing route chain No. range is set in the resource
management system.
Context Each outgoing route group belongs to an outgoing route chain,
and each route chain contains at most 4 route groups.
system tree.
SET:NEID=11;
2. Create an outgoing route chain by executing command ADD
CHAIN.
CHAIN is shown in Table 102.
TABLE 102 PARAMETERS IN THE ADD CHAIN COMMAND

Name
It is a mandatory
parameter, which is
an integer, ranging
CHAIN Route chain No. from
1 to 3000. It is used
to define an outgoing
route chain. When it is
configured in the
number
analysis configuration,
it


Name
is associated to the route
chain configured here
It is an optional
NAME User alias of 0~50 characters. It
is used to specifically
describe a route chain
to
make it easily
recognized
Whether the preference
policy is supported in the
MGW, including:
NO: When 2B occurs,
the calls in the same It is an optional
MGW are not preferred, parameter, with a default
PRINODE and routing is performed of YES. It is a policy
according to other for selecting the rouging
routing policies of the route
system instead.
YES: When 2B occurs,
the calls in the same
MGW are preferred
No. of route group 1,
used to set the route
group with the highest
RTS1 priority in a route chain
during routing. One
route chain can be
configured with at most
4 route groups
It is an optional
parameter. Select route
group with the level-2
groups according to the
priority order. Select
during routing. One
route group 1 fist. Only
route chain can be
when the circuits in route
group 1 are used up
4 route groups or all the circuits are
No. of route group 3, unavailable, the circuits
used to set the route in route group 2 can be
group with the level-3 selected. Only when the
priority in a route chain circuits in route group
RTS3 2 are used up or all the
during routing. One
route chain can be circuits are unavailable,
configured with at most the circuits in route
4 route groups group 3 can be selected

group with the level-4
during routing. One
route chain can be
4 route groups

263

Name
It is an optional
Route Selection Policy parameter. Select the
RTPLC route selection policy
Number
number configured in
ADD RTPLC command
It is an optional
number in an incoming
call. This parameter
must be defined by
DAS for the called command ADD DAS
TPDAS
number 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
Example: Create an outgoing route chain with the following

requirements.
� Route chain No.: 28
� User alias: RLink28
� No. of Route group 1: 28
ADD
CHAIN:CHAIN=28,NAME="RLink28",PRINODE=YE
S,RTS1=28,RTS2=0,RTS3=0,RTS4=0,RTPLC=0,TPDAS
=0;
END OF STEPS


Chapter
8
Configuration Instance
Table of Contents
Overview........................................................................ 265
Local Office Data Configuration.......................................... 266
Resource Attribute Configuration ....................................... 270
Adjacent IM-MGW Office Interconnection Data Configura-
tion ............................................................................... 271
Adjacent SCSCF Office Interconnection Data Configura-
tion ............................................................................... 274
Basic Service Data Configuration ....................................... 276
Data Synchronization ....................................................... 277
MGCF-IM-MGW Interconnection Debugging Procedure .......... 277
Overview
Introduction This chapter introduces the local office configuration procedure
and office interconnection data configuration procedure by taking
the example of creating a MGCF pilot office. Figure 61 shows the
networking diagram.
FIGURE 61 NETWORKING DIAGRAM
Note: Real lines indicate bearer connections, while dashed lines

indicate signaling connections
The MGCF is directly connected with the CSCF/BGCF/IM-MGW
through the IP bearer. The MGCF and IM-MGW can be intercon-
nected with the R4 CS through different signaling points.

265
According to the networking condition shown in Figure 61, the

operator is required to provide the negotiation data listed in
Table 103 and Table 104.
TABLE 103 NEGOTIATION DATA INSTANCE
NE Parameter Attributes
Office ID 11
Signaling point type of the 24-bit

local office
MGCF
SPC of the local office 3.11.1
Call prefix of the test 8613902099

number
Office ID 31
IM-MGW Signaling point type of the 24-bit

local office
Office ID 12
CSCF Signaling point type of the 24-bit

local office
TABLE 104 SIGTRAN IP ADDRESS INSTANCE OF THE MC

INTERFACE
Parameter Attributes
IP of the loop-back interface at 192.168.11.11/32

the MGCF side
IP of the SIPI interface at the 192.168.1.11/16

MGCF side

the IM-MGW side

IM-MGW side
Local Office
Data
Configuration
The procedure of the local office data
configuration is as follows:

Chapter 8 Configuration Instance
Steps Operations
1 Local exchange configuration
2 Physical configuration
3 Capacity configuration
4 Version loading
5 Office data configuration
Local Exchange Configuration

Data Planning Table 105 lists the parameters in the local exchange
configuration.
TABLE 105 DATA PLANNING OF THE LOCAL EXCHANGE
CONFIGURATION
Configuration Parameters Configuration Description
Office ID 11
Exchange type MSCS
User alias MGCF11
Command ADD NE:ID=11,TYPE=MSCS,MESUBTYPE=NONE,NAME="MG

CF11",VENDOR="ZTE",STATE=0;
Physical Configuration
Data Planning When the MSCS office uses only one shelf, the board layout of the
BCTC shelf is shown in Figure 62. Table 106 lists the data
planning of the physical configuration.
FIGURE 62 BOARD LAYOUT OF THE BCTC SHELF

267
TABLE 106 DATA PLANNING OF THE PHYSICAL CONFIGURATION
U-
Type Slot Module Backup
Board CPU nit
No. No. Mode
No.
CEN- No. 1 1+1 activ

- Slots 11 - OMP
OMP TR-
and 12
INO No.2 e/standby
RPU mode
UIM2_GC Slots 9 1+1 activ

UIMC - 921 -
S_755 and 10
e/standby
mode
CEN- Slots 7 1+1 activ
SMP - TR- - 3, 4
and 8
INO e/standby
mode
SIPI SIPI_NC - Slot 3 321 - No backup
SPB SPB2_826 - Slot 5 521 - No backup

Command 0_8260C4
1. Select an exchange.
SET:NEID=11;
2. Create a shelf.
ADD SHELF:RACK=1,SHELF=2,TYPE=BCTC;
3. Create UIM units
ADD
=UIM2_GCS_755,BKMODE=ONEPLUSONE,CLK1=16383,CL
K2=16383;
4. Create modules.
ADD
MODULE:LOC="1"-"2"-"7",MODULE="3",FUNC1="S
MP"&"MSCBASECMP"&"SIP",CPUTYPE=CENTRINO,BKMODE
=NO;
5. Create an SPB unit.
ADD
383;
6. Create an SIPI unit.
ADD
Capacity Configuration
=SIPI_NC,BKMODE=NO,CLK1=16383,CLK2=16383;
Data Planning Table 107 lists the parameters in the capacity and load sharing
configuration.

TABLE 107 DATA PLANNING OF THE CAPACITY CONFIGURATION
Office capacity Adopts the default value
Service data area The number of destination codes

is 4096
Command 1. Configure the MSCS office capacity.

SET MSCSCAPACITY;
For the subsequent steps, refer to Configuring the MGCF
Office Capacity.
2. Configure the service data area.
SET DATASIZE:CMODEL=AMONLY,BCBMNUM=10,DSTCD
NUM=4096;
Version Loading
After the physical configuration and capacity configuration are
completed, it is required to load the board version in order to let
the foreground board run normally. For the steps of loading the
version files, refer to Overview.
Office Data Configuration

Data Planning Table 108 lists the parameters in the office data configuration.
TABLE 108 DATA PLANNING OF THE OFFICE DATA

CONFIGURATION
Network type 1
Area code 25
Signaling point type of the local 24-bit

office
Exchange type Local exchange/toll ex-

change/MGCF exchange
Signaling point type STEP
Command 1. Create the signaling point of the local office.

ADD OPC:NET=1,NAME="NET1",SPCFMT=TRIPLE_DEC,O
PC24="3.11.1",APPTYPE="BICC"&"ISUP"&"SCCP"&"TUP",R

269
C="25",PREFIX="0",NETAPP=0,INFO=NONETAPP,DMIDX
=0;
2. Create the local exchange attributes.
ADD
LOFC:OFCTYPE="LOCAL"&"DOMTOLL"&"MGCF",NET
=1,SEQ=0,TCODE="1234",SPTYPE=STEP,LANG=DEFAUL
T,RESTART=YES,RSTTIME=10000,T19=68,T20=60,T21
=64;
3. Set SIP module capacity
SET SIPCAPA:SIPSOCKET=16,SIPTR=16,SIPTU=128,SIP
TUMSG=3000;
4. Create realm
ADD REALM:ID=1,REALM="zte.com";
5. Create host
ADD HOST:ID=1,HOST="host1.zte.com",IPV4="11.11.11.
1";
Resource
Attribute
Resource Planning Configuration
The instance
TABLE of resource
109 RESOURCE attributeINSTANCE
PLANNING configuration is shown in Table
109.
Configura- Resource
Key Fields Minimum Maximum
tion Types
Items
Office data
configura- Adjacent Adjacent
tion office office 1 20
ID
Node Topolog
Topolog
Topology y node 1 20
y Config ID.
configura-
tion
Voice Codec
Template ID
Template 1 10
SCTP SCTP ID 1 20
ASP ASP ID 1 20
AS AS ID 1 20
Protocol
configura- M3UA static M3UA static
tion route route ID 1 5
Signaling
Link set No.
linkset 1 20

Configura- Resource Key Fields Minimum Maximum

tion Types
Items
Signaling Signaling
route route 1 20
No.
Number Number
Analysis Analysis 1 300
Selector Selector
Number Number
Analysis Analysis
Entrance Entrance 1 50
Adjacent IM-MGW Office
Configuration
Data Planning Table 110 lists the parameters in the adjacent-MGW-office inter-
connection data configuration.
TABLE 110 PARAMETERS IN THE ADJACENT MGW OFFICE

INTERCONNECTION DATA CONFIGURATION

the MGCF side

MGCF side

the IM-MGW side

IM-MGW side
Adjacent IM-MGW office ID 101
Adjacent IM-MGW office type MGW
Association mode AM_SURE (Associated)
IM-MGW topology node No. 3
Signaling point type of the 14-bit

IM-MGW
SPC of the IM-MGW 1.31.1
The coding/decoding template No.

Tone coding/decoding template is 1.
No. The ETSI coding/decoding type is
ETSI_UMTS_AMR_2.

271

The supported coding/decoding
rates are “5.90K” and “6.70K”.
The activated coding/decoding
rates are “5.90K” and “6.70K”
SCTP ID 1
ASP ID 1
AS ID 1
M3UA static route ID 1
SIO-locating-AS ID 1
TID analyzer index 1
TID command template No. It is 1 by default
Command 1. Create the loop-back interface.

INTERFACE LOOPBACK:PORT=1;
ADD IP ADDRESS:ADDRESS="192.168.11.11",MASK="255
.255.255.255",BROADCASTIP="255.255.255.255";
SAVE ONLINEDATA;
EXIT;
2. Create the SIPI
interface address.
INTERFACE:SUBSYSTEM=0,MODULE=1,UNIT=321,SUNI
T=1,PORT=1;
ADD IP ADDRESS:ADDRESS="192.168.1.11",MASK="255.
255.255.248",BROADCASTIP="255.255.255.255";
SAVE ONLINEDATA;
EXIT;
3. Create an adjacent
IM-MGW office.
ADD ADJOFC:ID=101,NAME="IM-MGW1",NET=2,OFCTYP
E=MGW,SPCFMT=TRIPLE_DEC,SPCTYPE=14,DPC="1.31.1
",RC="25",ASSOTYPE=AM_SURE,SPTYPE=SEP,SSF=NATIO
NAL
STANDBY,SUBPROTTYPE=DEFAULT,TEST=YES,BAND
FLAG=YES,PRTCTYPE=CHINA,CLST=65535,INFO="CIC_P
ADD
CM",RELATEDOFC1=0;
CODECTPL:ID=1,GRPID=GRPID1,VALFG=YES,OID
4. Create a tone coding/decoding template.
=OID_ETSI,ETYPE=ETSI_UMTS_AMR_2,ACTRATE="Rate59
0"&"Rate670",SUPRATE="Rate590"&"Rate670",OM=YES;
5. Create a IM-MGW topology node.
ADD TOPO:ID=101,OFCID=101,NAME="IM-MGW101",CO
DECID=1,ETYPE=R4GW,PROTTYPE=H248,IPVER=IPV4,A
TTR="BNCAAL2"&"BNCIPRTP"&"BNCTDM",UPVER="V2",ATT

O=PRIVATE;
6. Create the SCTP.
ADD
SCTPCONN:MODULE=3,OFCID=101,PROT=M3UA,R
OLE=CLT,LOCADDR="IPv4"-"0"-"192.168.1.11",LOCPORT
=2001,REMADDR="IPv4"-"0"-"192.168.1.31",REMPORT=2
001,NAME="IM-MGW101-1",ID=1,INSTRM=16,OUTSTRM
=16,MAXRTRY=5,MAXRTO=500,MINRTO=50,INITRTO=1
00,HB=500,FIXNH=NO,SCTPMAXRTRYNUM=10,DELAYA
CK=20,MAXBURST=4,PRIMARYPATH=REMIP1,PMTU=0,B
REAKTIME=3,PDTHRESH=0,MINCWND=0,PLTIMER=1
0,MPPLTHRD=2,DPLEN=MTU,CB=200;
7. Create the ASP.
ADD ASP:ASSOCID=1,NAME="IM-MGW101-1",ID=1,ISLO
OP=NO,ISLOCK=NO;
8. Create the AS.
ADD AS:PROT=M3UA,ASPID="1",NAME="H248",ID=1,EX
ISTCTX=NO,ASTAG=CLT,ASUP="H248",ASMD=LOAD,NVA
L=1,KVAL=0;
9. Create a M3UA static route.
ADD M3UART:ID=1,ASID=1,MODE=BYTURNS,NAME="IM
-MGW101";
10. Create the SIO-locating-AS.
ADD SIOLOCAS:ID=1,NAME="IM-MGW-H248",SIO=H24
8,OFCID=101,OPOFCID=65535,PCM=65535,RT1=1,RT2
=0;
11. Create MGCF tones in batches.
BADD STONE:TYPE=ALL;
12. Create the MGC static data.
ADD MGCSCFG:MEGACO=1,ACTTM=600,ACTCHK=ON,W
AITTM=7800,PTRYNUM=5,PTRYTM=4000,CTXLIVETM=1
200,MGACTTM=600;
13. Create the IM-MGW static data template.
ADD MGSTPL:NAME="IM-MGW101",ID=1,MEGACO=1,AC
TCHK=ON,PRTTM=10,PRT=ON,PENDTM=200,LNGTM=15
000,RTRNTM=3800,MTRNNUM=1,TRNMD=UNFIXED,CTYP
E=TEXT;
14. Create the IM-MGW static data.
ADD MGSCFG:ID=101,NAME="IM-MGW101",TPLID=1,TO
NEID=1,LANGID=1,PKGLOST=10,JIT=50,DELAY=200,M
GW=NO;
15. Create the TID analyzer.
ADD TIDANL:NAME="IM-MGW101",PREV=1,TIDPFX="TD
M",TAG=TRUNK,PCMSPR="_",IDXSPR="/",PCMPOS1=1,P
CMPOS2=0,IDXPOS1=1,IDXPOS2=0;
16. Create the TID analysis entrance.
ADD TIDENTR:ND=101,TIDENTID=1,TIDTPLID=1,NAME
="MGW101";

273
Adjacent SCSCF Office

Configuration
Data Planning Table 111 lists the parameters in the adjacent-SCSCF-office inter-
connection data configuration.
TABLE 111 PARAMETERS IN THE ADJACENT SCSCF OFFICE

INTERCONNECTION DATA CONFIGURATION
IP of the virtual interface at the 10.1.44.77

MGCF side
IP of the virtual interface at the 10.1.33.11

CSCF side
Adjacent CSCF office ID 12
Adjacent CSCF office type "LOCAL"&"DOMTOLL"&"IP"
Association mode AM_SURE (Associated)
CSCF topology node No. 12
Signaling point type of the CSCF 24-bit
SPC of the CSCF 2.12.1
IP link No. 12
Route selector 1
Service group 1
CSCF adjacent host 12
UDP bear ID 1 (Local valid), 2 (Remote valid)
SIP signaling link ID 12
SIP route ID 12
SIP route set ID 12
Command 1. Create an SCSCF adjacent office.

ADD ADJOFC:ID=12,NAME="SCSCF",NET=1,OFCTYPE="L
OCAL"&"DOMTOLL"&"IP",SPCFMT=TRIPLE_DEC,SPCTYPE=2
4,DPC="2.12.1",RC="25",ASSOTYPE=AM_SURE,SPTYPE
=SEP,SSF=NATIONAL,SUBPROTTYPE=DEFAULT,TEST=YE
S,BANDFLAG=YES,PRTCTYPE=CHINA,CLST=65535,INFO
="CIC_PCM",RELATEDOFC1=0;
2. Create an SCSCF topology node.

ADD
TOPO:ID=12,OFCID=12,NAME="SCSCF",CODECID
=1,ETYPE=MSCVLR,PROTTYPE=SIP,IPVER=IPV4,ATTR
="BNCIPRTP",ATTR2=NOTUNL,TRFMOD=MCINTF,UPERRCT
RL=YES,DTMFTC=NO,MGWCON=SMGWCON,AUTOFAX=YE
S,OOBTC=NO,BCUID=0,SENDCAP=NO,G711TRAN=NO,BI
CCDTMF=TRANSPARENT,IPBCP2833=BYMGW,BICCDTMP
PER=0,AOIPPRO=PRIVATE;
3. Create a SIP office direction.
ADD
SIPOFC:OFCID=12,URL=URI,BYPASS=NO,BYPASS
PCT=80,BYPASSPRD=5,BYPASSTLEN=30,BYPASSLEV=L
N,BYPASSCALLNUM=1,BTYPE=IN,OVERLAP=RINVT,CFIN
FO=HIS,PBRTFMT=EQUAL,DTMF=IN,FMT4733=97,SIPRE
L=NO,ENOPT="SIP_ESSO"&"SIP_PRECOND"&"T30"&"FCPL";
4. Create an IP link.
ADD IPLINK:OFCID=12,MODULE=3,NAME="IPLINK-12",I
D=12,LOCIP="IPv4"-"0"-"10.1.44.77",LOCPORT=5060,RE
MIP="IPv4"-"0"-"10.1.33.11",REMPORT=5060,PRO=UDP,T
CPROTO=CLT,TSTIMER=15000;
5. Create an adjacent host.
ADD ADJHOST:ID=12,HOSTNAME="SCSCF",REALM="zte.
com",SRVGRP=1;
6. Create a local valid UDP bear.
ADD UDPBR:ID=1,NAME="LOCAL",IPMODE=LOCAL_VALI
D,ADJHOST=0,IPLINK=12,DSTADDRTYPE=IPV4,DSTVPN
=0,DSTPORT=0;
Create a remote valid UDP bear.
ADD UDPBR:ID=2,NAME="REMOTE",IPMODE=REMOTE_V
ALID,ADJHOST=12,IPLINK=0,DSTADDRTYPE=IPV4,DSTV
4ADDR="10.1.33.11",DSTVPN=0,DSTPORT=5060;
7. Create SIP signaling link.
ADD SIPLNK:ID=12,NAME="SCSCFLINK",BRID=2,HBTIM
E=0,NORMALHBTIME=120,UNUSECNT=3,USECNT=3;
8. Create SIP signaling route.
ADD SIPRT:ID=12,NAME="SCSCFR",SPLC=SEQ,LNK="1
2";
9. Create SIP signaling route set.
ADD SIPRTS:ID=12,NAME="SCSCFRS",RTPLC=SEQ,SIPR
T="12"-"100";

275
Basic Service
Data Configuration
Call Data Configuration
Data Planning Table 112 lists the parameters in the call data configuration.
TABLE 112 PARAMETERS IN THE CALL DATA CONFIGURATION
Configuration Configuration Description

Parameters
Number analyzer entry 1 (Local number analyzer)
DAS Originating DAS 101
Call prefix of the test 8613902099

number
Call service type 13902099: LOL (Outgoing/Local service

of the local network)
Command 1. Create a number analysis entrance.

ADD ENTR:ID=1,NAME="LOCAL",TYPE=LOCAL,NTYPE=CA
LLED;
2. Create a DAS.
ADD
DAS:ID=101,NAME="MSQH",NEWSRV=0,CENTR
=0,PRINET=0,SPECSRV=0,LOCAL=1,NATIONAL=0,INTE
R=0;
3. Set the default DAS template of the local office.
SET LDASTMPLT:MS=101,MSRN=201;
4. Create the called number analysis.
ADD TPDNAL:ENTR=1,DIGIT="13902099",SPECRST=0,S
PECIDX=0,CAT=LOL,RST1=1,RST2=0,RST3=0,CHAINA
L=0,RNLEN=0,MINLEN=3,MAXLEN=20,OVLYPRI=NO,R
EL=NO,NET=1,NAT=DEF,OPDDICONT=NO,TPDDICONT
=NO,OPDDI=0,TPDDI=0,OPDLYDDI=0,TPDLYDDI=0,DD
IOVERB=0,IWVIDEO=LSUP,TIMELMT=0,AUXDAS=0,A6
=0,PFXLEN=0,INSRV=INM,FAXIDX=0,AVIDX=0,DVIDX
=0,ADATAIDX=0,DDATAIDX=0,DDCPLAY=NONE,VAD=IN
VALID,CALLSERVPRILVL=INVALID,RERTS=0,INCHAIN=N
O,BICT=NO,ICT=0,ICTT=10,GNM=NORMAL,STBILL=INVA
LID,HOPDAS=0,MCA=NO,IVVR=NO,WANTL=0,IMSCENTR
=NO;

SIP Service Data Configuration

Data Planning Table 113 lists the parameters in the SIP service data configura-
tion.
TABLE 113 PARAMETERS IN THE SIP SERVICE DATA

CONFIGURATION
IP distribution policy ID 1
V4NET 10.1.33.11
URI scscf.zte.com
SIP method ACK"&"BYE"&"CANCEL"&"INVITE

"&"PRACK"&"UPDATE
UDP distribution policy Excellent choice priority
UDP bear ID 1
Command 1. Create IP distribution policy.

ADD IPDPLC:ID=1,NAME="MGCF11",ADDRTYPE=IPV4,V
4NET="10.1.33.11",V4MSK="255.255.255.0",PORT=0,UPL
C=PRIROR,UDPID="1";
2. Create URI analysis.
ADD URI:RTSEL=1,URI="scscf.zte.com",METHOD="ACK
"&"BYE"&"CANCEL"&"INVITE"&"PRACK"&"UPDATE",SIPRTS
=12;
Data Synchronization
Command SYNA:STYPE=ALL,TIMEOUT=600,SAVE=YES,TOSLAVE=YES;
MGCF-IM-MGW
Interconnection Debugging
Procedure
After data of the IM-MGW are configured on the MGCF, the com-
mon procedures for data debugging are as follows.

277
1 Checking the IM-MGW office Check whether the IM-MGW

status office is accessible
When the office is

Checking the physical inaccessible, first confirm
2
connection whether there is any
hardware problem
After the hardware problem

3 Debugging the SCTP is removed, confirm whether
there is any problem in the
SCTP association
After the problem in the

SCTP association is
4 Debugging the M3UA removed, confirm whether
there is any problem in
upper-layer M3UA signaling
link
After the problem on the
Confirming the working M3UA layer is removed,
5
status of the IM-MGW check the H.248 gateway
configuration
Checking the IM-MGW Office Status

Prerequisites The IM-MGW adjacent office data configuration is completed.
Context Check whether the office is accessible is the first step for debug-
ging. This section introduces the detailed procedures for checking
whether the IM-MGW office is accessible.
Steps 1. On the NetNumen M30 window, select menus Views >
MML Terminal to enter the MML Terminal window.
to specify the MGCF exchange to be configured.
3. Enter the following command on the MML Terminal window,
and click Execute to query the status of the adjacent IM-
MGW office. OFC is the adjacent IM-MGW office ID.
SHOW OFCSTAT:OFC=101;
Note:
You can check whether the office is accessible, and the status
of the SIGTRAN signaling on the Dinamic management
page of the View window.
END OF STEPS
Result The Command Execute Result shows the M3UA Office State
is Reachable.
Postrequisite If the office is inaccessible, check the physical connection.

Checking the Physical Connection

Prerequisites The IM-MGW adjacent office data configuration is completed.
Context If it is found that the adjacent IM-MGW office is not reachable on
the NetNumen M30 window, confirm whether the physical
connection between the MGCF and the IM-MGW is normal.
Steps 1. When the MGCF is connected with the IM-MGW through HUB,
the straight network cable should be adopted. When the
MGCF is directly connected with the IM-MGW, the crossover
network cable should be adopted.
END OF STEPS
Result The physical connection is normal when the indicators Link1 and
Link3 on the SIPI board are always on.
Debugging the SCTP

Prerequisites � The IM-MGW adjacent office data configuration is completed.
� The physical connection is normal between MGCF and IM-
MGW.
Context � The MML Terminal window is opened.

If the physical connection is normal, debug the SCTP.
1. On the NetNumen M30 window, select menus Views >
Steps
3. Enter the following command on the command terminal, and
click Execute to query the STCP status. ASSOCID is the as-
sociation ID.
SHOW SCTPSTAT:ASSOCID=1;
END OF STEPS
Result The Command Execute Result shows the SCTP Status is Es-
tablished.
Postrequisite If the association is not established, check whether the IP
address configuration of the port is correct.
Debugging the M3UA

Prerequisites � The IM-MGW adjacent office data configuration is completed.
� The physical connection is normal between MGCF and IM-
MGW.
� The association between MGCF and IM-MGW is established.

279
�The MML Terminal window is opened. If

Context the SCTP is established, debug the M3UA.
The physical status of the ASP is decided by the association sta-
tus. After the association is established, the ASPs at the both
ends perform handshaking of the service status maintenance
message “ASPTM”. If the handshaking is successful, the service
Steps
can be used.
1. On the NetNumen M30 window, select menus Views >
and click Execute to query the ASP status. ASID is the AS
ID, and ASPID is the ASP ID.
SHOW ASPSTAT:ASID=1,ASPID=1;
and click Execute to query the AS status. ASID is the AS ID.
SHOW ASSTAT:ASID=1;
END OF STEPS
Result � When the ASP status in active, ASP Status Active should be
displayed.
� When the AS status in normal, AS Status Active should be
displayed.
Confirming the Working Status of the

IM-MGW
Context After the office direction to the IM-MGW is debugged successfully,
the status of the IM-MGW is not guaranteed to be normal. This
section introduces the method of confirming the working status of
the IM-MGW.
After the data for connection between the MGCF and the IM-MGW
are configured and the equipment is started, the IM-MGW will
actively register the gateway information to the MGCF. This topic
describes the method of confirming the working status of the IM-
MGW.
Steps 1. On the NetNumen M30 window, select menus Views >
and click Execute to query the registration status of the gate-
way.

SHOW MGWSTAT;
END OF STEPS
Result The Command Execute Result shows the MGW Status is In

Service.
Postrequisite When the working status of the gateway is exceptional, check
whether the corresponding parameters in the H248 configuration
and the SIGTRAN configuration on the MGCF and the IM-MGW
are consistent and meet the requirements.
H.248/SCTP Problem Location

Method
For two NEs adopting SIGTRAN networking, to judge whether the
bottom-layer link is reliable, it is necessary to confirm whether
two connections are normal. One is the connection between two
SIG_IPIs, and the other is the control channel between the
SIG_IPI and the SMP.
� Debugging the IP protocol stack
Debugging the connection between two SIG_IPIs means de-
bugging the IP protocol stack. When the physical connection
is normal, connect one computer to HUB or to SIGIPI through
the crossover network cable. Ping the IP addresses of the
SIPI interface and the loop-back interface of the local end,
and those of the opposite end. When the IP protocol stack is
correctly configured, these IP addresses should be pinged
successfully. If they cannot be pinged successfully, confirm
whether the IP protocol stack is correctly configured.
� Debugging the basic SCTP connection information
After the protocol stack is normal, it is necessary to check
data in the SCTP configuration , including whether the
protocol type, the server and the client are normal; whether
the office ID, IP address, and port number are correct; and
whether the port number is repeated.
M3UA Problem Location Method

When the status of the lower-layer association is normal, and the
status of the AS/ASP is abnormal, it is necessary to confirm
whether AS data, ASP data, and SIO-locating-AS data are cor-
rectly configured, and whether the interconnecting parameters
between the local office and the opposite-end office are consis-
tent.

281

Figure
Figure 1 IMS NETWORKING ................................................. 1

Figure 2 OVERALL FLOW OF THE MGCF DATA CONFIGURATION ..
3 Figure 3 START PROCESS OF THE OMM SERVER .....................
5 Figure 4 START INFORMATION OF THE OMM SERVER...............
5 Figure 5 LOGIN Window ......................................................
6 Figure 6 NETNUMEN M30 MSCS/MGW OMM SYSTEM
WINDOW.. 7 Figure 7 MML Terminal
Window .......................................... 8
Figure 8 MML TERMINAL Window .......................................... 9
Figure 9 COMMAND EXECUTION OPERATIONS ....................... 10
Figure 10 LOCAL OFFICE DATA CONFIGURATION FLOW...........
14 Figure 11 PHYSICAL CONFIGURATION
FLOW ......................... 18
Figure 12 FLOW OF LOADING VERSION FILES ....................... 40
Figure 13 VERSION LOADING.............................................. 42
Figure 14 CONFIGURING VERSION PATH ..............................
42
Figure 15 Adding New Blank Entry ....................................... 43
Figure 16 Configuring Version Name..................................... 43
Figure 17 VERSION FILE PATH............................................. 44
Figure 18 Load Version....................................................... 45
Figure 19 Version List......................................................... 46
Figure 20 CREATING OMP BOOT FILES ................................. 46
Figure 21 Successful Infomation .......................................... 47
Figure 22 CONNECTION DESCRIPTION ................................. 48
Figure 23 CONNECT TO DIALOG BOX ................................... 48
Figure 24 COM1 PROPERTIES .............................................. 49
Figure 25 PRESS ANY KEY TO STOP AUTO-BOOT....................
49 Figure 26 BOOT
PASSWORD................................................ 50
Figure 27 3GPLAT BOOT ..................................................... 50
Figure 28 CONFIG SELECTION............................................. 51
Figure 29 ENTER OMP’S OMC IP ADDRESS ............................ 51
Figure 30 ENTER OMP’S OMM MAC ADDRESS ........................ 52
Figure 31 ENTER OMP’S GATEWAY IP ADDRESS ..................... 52
Figure 32 OMC SERVER IP ADDRESS....................................
283
Figure 34 OMM IP ADDRESS ............................................... 54
Figure 35 FTP CONFIG........................................................ 54

Figure 36 OMPCFG FILE...................................................... 55
Figure 38 OMP BOOT TYPE .................................................. 56
Figure 40 BUREAU NO. ....................................................... 57
Figure 42 3GPLAT BOOT ..................................................... 58
Figure 43 USER NAME AND PASSWORD ................................
61 Figure 44
STATUS .............................................................. 62
Figure 45 Version Mainenance ............................................. 63
Figure 46 Version List......................................................... 64
Figure 47 BATCH VERSION LOADING BY DEFAULT ..................
64 Figure 48 AREA
TREE ......................................................... 76
Figure 49 ADDING RESOURCES ........................................... 76
Figure 50 RESOURCE ADDING DIALOG BOX ..........................
77 Figure 51 FLOW OF MGCF-IM-MGW INTERCONNECTION
CONFIGURATION ............................................... 80
Figure 52 SIGTRAN CONFIGURATION FLOW ........................
107 Figure 53 CONFIGURATION
FLOW ...................................... 120 Figure 54 FLOW OF
CONFIGURING A DIRECT-ASSOCIATED
OFFICE IN IP DOMAIN ...................................... 167
Figure 55 QUASI-ASSOCIATED NETWORKING BETWEEN
MSCS AND 2G MSC/PSTN (BASED ON M3UA) ......
175 Figure 56 FLOW OF M3UA TRANSIT
EXCHANGE ................... 176 Figure 57 QUASI-ASSOCIATED
NETWORKING BETWEEN
MGCF AND 2G MSC/PSTN (BASED ON M2UA) ...... 177
Figure 58 FLOW OF M2UA TRANSIT EXCHANGE ...................
178 Figure 59 TDM OFFICE INTERCONNECTION CONFIGURATION
FLOW............................................................. 182
Figure 60 ANALYSIS ORDER OF NUMBER ANALYZERS ........... 194
Figure 61 NETWORKING DIAGRAM..................................... 265
Figure 62 BOARD LAYOUT OF THE BCTC SHELF ...................
267

Tabl
e
Table 1 LOGIN PARAMETER DESCRIPTION.............................. 6
Table 2 PARAMETERS IN THE SYNA COMMAND ..................... 11
Table 3 PARAMETERS IN THE SYN COMMAND........................ 11
Table 4 PARAMETERS IN THE ADD NE COMMAND ..................
16 Table 5 PARAMETERS IN THE SET PCINFO
COMMAND ........... 17 Table 6 PARAMETERS IN THE ADD RACK
COMMAND .............. 20 Table 7 PARAMETERS IN THE ADD
SHELF COMMAND............. 21 Table 8 PARAMETERS IN THE
ADD UNIT COMMAND .............. 22 Table 9 PARAMETERS IN
THE ADD MODULE COMMAND ......... 24 Table 10 MGCF BOARD
TYPES ............................................. 25 Table 11 PARAMETER
IN THE ADD UNIT COMMAND .............. 27 Table 12
PARAMETERS IN THE ADD UNIT COMMAND............. 28 Table
13 PARAMETERS IN THE ADD UNIT COMMAND............. 30
Table 14 PARAMETERS IN THE ADD UNIT COMMAND............. 31
Table 15 PARAMETERS IN THE ADD UNIT COMMAND.............
32 Table 16 PARAMETER IN THE ADD SVRINF
COMMAND........... 34 Table 17 CAPACITY
CONFIGURATION.................................... 34
Table 18 Office Capacity Configuration Parameters ................. 35
Table 19 PARAMETERS IN THE SET DATASIZE COMMAND ......
38 Table 20 VERSION DESCRIPTION OF OMP BOOT
FILE ............. 45 Table 21 PARAMETERS IN THE SET OMP
COMMAND .............. 59 Table 22 PARAMETERS IN THE SYNA
COMMAND.................... 60 Table 23 Board Version
Files................................................ 62 Table 24 BOARD
INDICATOR STATUSES ................................ 65 Table 25
PARAMETERS IN THE BADD STONE COMMAND ........ 66
Table 26 Office Information Configuration ............................. 67
Table 27 PARAMETERS IN THE ADD OPC COMMAND ..............
68 Table 28 PARAMETERS IN THE ADD LOFC
COMMAND ............ 70 Table 29 RESOURCE TYPES, KEY FIELDS
AND VALUE RANGES
OF THE MGCF.................................................... 74
Table 30 FLOW DESCRIPTION.............................................. 80
Table 31 INTERFACE IP ADDRESS CONFIGURATION................ 81
Table 32Confidential
PARAMETERS IN THE Information
and Proprietary ADD IP ADDRESS COMMAND...
of ZTE CORPORATION
285
82 Table 33 INTERFACE REAL
INTERFACE ................................ 83
Table 34 PARAMETERS IN THE ADD IP ADDRESS COMMAND...

84 Table 35 INTERFACE VIRTUAL
INTERFACE ........................... 85 Table 36 PARAMETERS IN THE
ADD IP ADDRESS COMMAND... 86 Table 37 PARAMETERS IN
THE ADD BFD AUTH COMMAND ..... 88 Table 38 PARAMETERS
IN THE ADD BFD SESSION
COMMAND ........................................................ 89
Table 39 PARAMETERS IN THE ADD IP ROUTE COMMAND......
91 Table 40 ADJACENT AND TOPOLOGY
CONFIGURATION............ 92 Table 41 PARAMETERS IN THE ADD
ADJOFC COMMAND ........ 93 Table 42 PARAMETERS IN THE
ADD CODECTPL COMMAND .... 98 Table 43 PARAMETERS IN
THE ADD TOPO COMMAND .......... 100 Table 44 PARAMETERS
IN THE ADD MGWBEARMOD
COMMAND ...................................................... 103
Table 45 PARAMETERS IN THE ADD SCTPCONN COMMAND ..
109 Table 46 PARAMETERS IN THE ADD ASP
COMMAND ............ 112 Table 47 PARAMETERS IN THE ADD AS
COMMAND .............. 113 Table 48 PARAMETERS IN THE ADD
M3UART COMMAND...... 116 Table 49 PARAMETERS IN THE
ADD SIOLOCAS COMMAND... 118 Table 50 PARAMETERS IN THE
ADD MGCSCFG COMMAND.... 121 Table 51 PARAMETERS IN
THE ADD MGSTPL COMMAND ...... 123 Table 52 PARAMETERS
IN THE ADD MGSCFG COMMAND...... 124 Table 53
PARAMETERS IN THE ADD TIDANL COMMAND....... 126 Table
54 PARAMETERS IN THE ADD TIDENTR COMMAND..... 128
Table 55 FLOW DESCRIPTION............................................ 129
Table 56 PARAMETERS FOR CREATING A SIP ADJACENT
OFFICE .......................................................... 131
Table 57 PARAMETERS IN THE COMMAND ADD SIPOFC ....... 136
Table 58 PARAMETERS IN THE ADD TOPO COMMAND ..........
137 Table 59 PARAMETERS IN THE ADD IPLINK
COMMAND ....... 143 Table 60 PARAMETERS IN THE SET
SIPCAPA COMMAND...... 145 Table 61 PARAMETERS IN THE
ADD REALM COMMAND ........ 146 Table 62 PARAMETERS IN
THE ADD HOST COMMAND .......... 147 Table 63 PARAMETERS
IN THE ADD RTSEL COMMAND ......... 148 Table 64
PARAMETERS IN THE ADD SRVG COMMAND .......... 149 Table
65 PARAMETERS IN THE ADD ADJHOST COMMAND .... 150
Table 66 PARAMETERS IN THE ADD UDPBR COMMAND........ 151
Table 67 PARAMETERS IN THE ADD SIPLNK COOMMAND.....
153 Table 68 PARAMETERS IN THE ADD SIPRT
286 COMMAND
Confidential and Proprietary .........
Information 154CORPORATION
of ZTE Table 69 PARAMETERS IN THE ADD
SIPRTS COMMAND ....... 156 Table 70 PARAMETERS IN THE
ADD IPDPLC COMMAND ....... 157
Tables
Table 71 PARAMETERS IN THE ADD URI COMMAND............. 159

Table 72 PARAMETERS IN THE ADD TG RTP COMMAND .......
161 Table 73 BEARER MODES OF MAIN
INTERFACES .................. 165 Table 74 PARAMETERS IN THE
ADD ADJOFC COMMAND ...... 168 Table 75 PARAMETERS IN
THEADD TOPO COMMAND........... 173 Table 76 PARAMETERS
IN THE ADD M2UAIPLNK
COMMAND ...................................................... 180
Table 77 PARAMETERS IN THE ADD N7LKS COMMAND ........
184 Table 78 PARAMETERS IN THE ADD N7LNKE1
COMMAND .... 186 Table 79 PARAMETERS IN THE ADD
N7ROUTE COMMAND.... 188 Table 80 ARRANGEMENT MODE OF
SIGNALING SETS............ 189 Table 81 PARAMETERS IN THE
ADD N7OFC COMMAND ........ 191 Table 82 DAS FOR PRE-
ANALYZING THE CALLED NUMBER ..... 194 Table 83
ORIGINATING DAS.............................................. 195
Table 84 FORWARDING
DAS.............................................. 196
Table 85 ROAMING
DAS.................................................... 197 Table 86
PARAMETERS IN THE ADD ENTR COMMAND .......... 199 Table
87 ANALYZER ENTRY TYPES ...................................... 200
Table 88 COMMON
DAS .................................................... 201 Table 89
PARAMETERS IN THE ADD DAS COMMAND ............ 202 Table
90 PARAMETERS IN THE SET LDASTMPLT COMMAND .. 203
Table 91 PARAMETERS IN THE ADD ACRTMPLT COMMAND .. 207
Table 92 PARAMETERS IN THE ADD TPDNAL COMMAND ......
211 Table 93 CALL SERVICE TYPES ..........................................
225
Table 94 ENABLED
OPTIONS ............................................. 232 Table 95
PARAMETERS IN THE ADD TG DT COMMAND ......... 237 Table
96 PARAMETERS IN THE ADD TG ATM COMMAND ....... 244
Table 97 PARAMETERS IN THE ADD TG RTP COMMAND ....... 250
Table 98 PARAMETERS IN THE ADD SPCM COMMAND ..........
255 Table 99 PARAMETERS IN THE ADD INPCM
COMMAND ........ 257 Table 100 PARAMETERS IN THE ADD RT
COMMAND............. 259 Table 101 PARAMETERS IN THE ADD
RTS COMMAND........... 261 Table 102 PARAMETERS IN THE
ADD CHAIN COMMAND ...... 262 Table 103 NEGOTIATION DATA
INSTANCE ........................... 266 Table 104 SIGTRAN IP
ADDRESSConfidential
INSTANCE OF THE MC
and Proprietary Information of ZTE CORPORATION
287
INTERFACE ..................................................... 266
Table 105 DATA PLANNING OF THE LOCAL EXCHANGE
CONFIGURATION ............................................. 267
Table 107 DATA PLANNING OF THE CAPACITY

CONFIGURATION ............................................. 269
Table 108 DATA PLANNING OF THE OFFICE DATA
CONFIGURATION ............................................. 269
Table 109 RESOURCE PLANNING INSTANCE ........................ 270
Table 110 PARAMETERS IN THE ADJACENT MGW OFFICE
INTERCONNECTION DATA CONFIGURATION ........ 271
Table 111 PARAMETERS IN THE ADJACENT SCSCF OFFICE
INTERCONNECTION DATA CONFIGURATION ........ 274
Table 112 PARAMETERS IN THE CALL DATA CONFIGURATION ..
276 Table 113 PARAMETERS IN THE SIP SERVICE DATA
CONFIGURATION ...................................
.......... 277

Index
A MML Terminal......................4
Active/standby mode .........
29 Active/standby
networking...................... 80 N
Address planning ............... Network section ................ 81
80
Adjacent office ..................
81
B O
OMM Client .........................4
Background ........................2
OMM server ........................2
BFD configuration ..............
80
C P
Cable connection .................2 Physical configuration ........ 18
Commissioning.................. 29 Protocol stack ................... 79
crossover network
cable ............................ 279
Crossover network Q
cable ............................ 281 Quasi-associated ............. 177
D R
Data configuration ...............4
Data Synchronization ...........4 Rack ..................................2
H S
H248 configuration ............ SCTP configuration .......... 281
81 Shelf..................................2
Hardware installation ...........2 Signaling Route ...............
179
I SIGTRAN........................ 281
Inter-office ....................... 29 SIGTRAN configuration....... 81
Interconnection
data ........................... 3, 79 T
IP address ...................... 281
Topological node................ 81
IP protocol stack ............. 281 Topological node
configuration ...................
81
L
LAN ...................................2
Link ............................... 281
Load-sharing .................... 80
Load-sharing mode............
29 local office ......................
281 Loop-back
interface ......... 281
M
M3UA............................. 280

289

PDF SJ 20100211152857 007 ZXWN Mscs v30921 MSC Server Data Configuration Guidemgcf

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PDF SJ 20100211152857 007 ZXWN Mscs v30921 MSC Server Data Configuration Guidemgcf

Uploaded by

Copyright:

Available Formats

ZXWN MSCS

Copyright © 2010 ZTE CORPORATION.

Revision No. Revision Date Revision Reason

Serial Number: SJ-20100211152857-007

About This Manual............................................. I

Confidential and Proprietary Information of ZTE CORPORATION I

MGCF-Other-Exchange Interconnection Data

Confidential and Proprietary Information of ZTE CORPORATION V

This page is intentionally blank.

VI Confidential and Proprietary Information of ZTE CORPORATION

Describes the overall flow of the

Describes the physical

Confidential and Proprietary Information of ZTE CORPORATION I

Chapter 3, Resource Describes MGCF resource planning

Chapter 4, MGCF-IM-MGW Describes the signaling

Chapter 5, MGCF-SIP Office Describes the signaling

Describes the signaling

Describes the basic data

Chapter 8, Configuration Sets MGCF trial office as an

Italics References to other Manuals and documents.

“Quotes” Links on screens.

Bold Menus, menu options, function names, input fields,

CAPS Keys on the keyboard and buttons on screens and

Note: Provides additional information about a certain

Checkpoint: Indicates that a particular step needs to

Tip: Indicates a suggestion or hint to make things

II Confidential and Proprietary Information of ZTE CORPORATION

Mouse operation conventions are listed as follows:

Click Refers to clicking the primary mouse button (usually the

Double- Refers to quickly clicking the primary mouse button

Right-click Refers to clicking the secondary mouse button (usually

Confidential and Proprietary Information of ZTE CORPORATION III

This page is intentionally blank.

IV Confidential and Proprietary Information of ZTE CORPORATION

To minimize the environmental impact and take more

The ZXWN MGCF manufactured by ZTE CORPORATION meet the

Confidential and Proprietary Information of ZTE CORPORATION I

This page is intentionally blank.

II Confidential and Proprietary Information of ZTE CORPORATION

FIGURE 1 IMS NETWORKING

Confidential and Proprietary Information of ZTE CORPORATION

Overall Flow of MGCF Data

2 Confidential and Proprietary Information of ZTE CORPORATION

FIGURE 2 OVERALL FLOW OF THE MGCF DATA CONFIGURATION

Flow Description The flow description of MGCF data configuration is shown in .

Steps Operations Description

Perform local exchange configuration,

MGCF-SIP office Configure the SIP signaling

Confidential and Proprietary Information of ZTE CORPORATION

Steps Operations Description

MGCF-other Configure the signaling interconnection

5 Basic service data Configure the data related to the SIP

Basic Operations of the

1 Logging in the OMM Client

2 Entering the MML Terminal

3 Operations on the MML Terminal

Logging in the OMM Client

4 Confidential and Proprietary Information of ZTE CORPORATION

FIGURE 3 START PROCESS OF THE OMM SERVER

2. After the OMM server starts successfully, the prompt messages

FIGURE 4 START INFORMATION OF THE OMM SERVER

3. On the server, click Start > Programs > ZXWN-CS (OMM)

Confidential and Proprietary Information of ZTE CORPORATION