CM3G-302-E1 Introduction To The ZXC10 MSCe Data Configuration

CM3G-302-E1 Introduction to the ZXC10
MSCe Data Configuration
Course Objective：
·Familiar with the configuration and modification of MSCe system
data, office date, and trunk data etc.
Contents
1 Overview ..................................................................................................................................................... 1
1.1 Overview of Configuration Management System............................................................................. 1
1.2 Basic Configuration Sequence .......................................................................................................... 1
2 Node Configuration.................................................................................................................................... 5
2.1 Overview........................................................................................................................................... 5
2.2 Main Interface ................................................................................................................................... 6
2.3 Physical Configuration...................................................................................................................... 7
2.3.1 Configuring Racks ................................................................................................................. 9
2.3.2 Configuring Shelves............................................................................................................. 11
2.3.3 Configuring Boards.............................................................................................................. 13
2.3.4 Configuring Module Types .................................................................................................. 19
2.3.5 Configuring Capacity Planning Parameters ......................................................................... 25
2.3.6 Configuring Module/Board Relationship............................................................................. 26
2.3.7 Configuring IP Interfaces ..................................................................................................... 29
2.3.8 Configuring IP Static Routes................................................................................................ 32
2.4 Office Configuration ....................................................................................................................... 35
2.4.1 Local Office Configuration .................................................................................................. 36
2.4.2 Signaling Configuration ....................................................................................................... 37
2.4.3 Adjacent Office Configuration ............................................................................................. 39
2.4.4 SIP Office Configuration...................................................................................................... 42
2.4.5 Verification........................................................................................................................... 45
2.5 No. 7 Data Configuration―MTP Configuration............................................................................. 45
2.5.1 Configuring Signaling Link Groups..................................................................................... 46
i
2.5.2 Configuring Signaling Links ................................................................................................49
2.5.3 Configuring Signaling Routes ..............................................................................................51
2.5.4 Configuring Signaling Office IDs.........................................................................................53
2.5.5 Verification ...........................................................................................................................55
2.6 No. 7 Data Configuration―SCCP Configuration............................................................................55
2.6.1 Configuring GT Translation Selectors ..................................................................................56
2.6.2 Configuring GT Translation Data .........................................................................................60
2.6.3 Verification ...........................................................................................................................65
2.7 No. 7 Data Configuration―SSN Configuration..............................................................................65
2.8 No. 7 Data Configuration―Narrow-band Signaling Configuration................................................69
2.9 Sigtran Configuration ......................................................................................................................71
2.9.1 Configuring SCTP Basic Connection ...................................................................................71
2.9.2 Configuring ASPs .................................................................................................................75
2.9.3 Configuring ASs ...................................................................................................................77
2.9.4 Configuring SIO Positioning ASs.........................................................................................80
2.9.5 Verification ...........................................................................................................................82
3 MSCe Configuration ................................................................................................................................83
3.1 Overview .........................................................................................................................................83
3.2 Main Interface..................................................................................................................................83
3.3 Number Analysis Configuration ......................................................................................................84
3.3.1 Digit Analysis Selector Configuration ..................................................................................86
3.3.2 Analyzer Entry Configuration...............................................................................................89
3.3.3 Examples of Number Analysis Configuration ......................................................................98
3.3.4 SCP/GT Address Index Configuration................................................................................102
3.3.5 Number Transform/Display Selector ..................................................................................104
3.3.6 Number Transform/Display ................................................................................................107
ii
3.3.7 Result Verification.............................................................................................................. 110
3.4 Topological Relation Configuration.............................................................................................. 110
3.4.1 Coding/Decoding Type Configuration ................................................................................111
3.4.2 Device Node Configuration ............................................................................................... 113
3.4.3 BSC-MGW Relationship Configuration ............................................................................ 116
3.4.4 SIP Transfer Protocol Configuration .................................................................................. 119
3.4.5 DIGITMAP Module Configuration.................................................................................... 122
3.4.6 Encoding Name Configuration........................................................................................... 125
3.5 Trunk Management ....................................................................................................................... 126
3.5.1 Trunk Group Configuration................................................................................................ 127
3.5.2 PCM Configuration............................................................................................................ 135
3.5.3 Outgoing Route .................................................................................................................. 137
3.5.4 Outgoing Route Set ............................................................................................................ 138
3.5.5 Outgoing Route Chain........................................................................................................ 140
3.5.6 Inner-office MGW Topological Relation Configuration .................................................... 143
3.5.7 Virtual CIC Configuration.................................................................................................. 145
3.6 Handoff Office Configuration ....................................................................................................... 148
3.7 Mobile Office Configuration......................................................................................................... 150
3.7.1 Mobile Office Capacity...................................................................................................... 151
3.7.2 Mobile Data Configuration ................................................................................................ 152
3.7.3 MSC ID Configuration....................................................................................................... 158
3.7.4 VMSC Configuration ......................................................................................................... 160
3.7.5 CDMA Data Configuration ................................................................................................ 163
3.7.6 IMSI Configuration............................................................................................................ 165
iii
3.7.7 MIN ....................................................................................................................................166
3.7.8 Result Verification ..............................................................................................................167
3.8 Mobile Area Code Configuration ..................................................................................................167
3.8.1 Location Area......................................................................................................................168
3.8.2 Global Cell..........................................................................................................................170
3.8.3 VMSC Location Management ............................................................................................171
3.8.4 Cell ID ................................................................................................................................173
3.8.5 Special Service Group ........................................................................................................175
3.8.6 Special Service Group Template.........................................................................................177
3.8.7 Result Verification ..............................................................................................................178
3.9 BSC Configuration ........................................................................................................................178
3.10 Mobile Number Analysis Configuration......................................................................................181
3.10.1 Mobile Number Analysis ..................................................................................................181
3.10.2 Local Area Number...........................................................................................................184
3.10.3 Other Number ...................................................................................................................185
3.10.4 Result Verification ............................................................................................................187
3.11 Numbering Plan ...........................................................................................................................187
3.12 VLR Configuration ......................................................................................................................190
3.12.1 VLR System Parameter Configuration .............................................................................191
3.12.2 IMSI Segmental Table Configuration ...............................................................................193
3.12.3 TLDN Segmental Table Configuration.............................................................................195
3.12.4 TRN Segmental Table Configuration................................................................................197
3.12.5 Result Verification ............................................................................................................199
3.13 Tone Resource Configuration ......................................................................................................199
3.13.1 Language Template Configuration....................................................................................201
3.13.2 Tone Mode Configuration.................................................................................................202
iv
3.13.3 Service Key Conversion................................................................................................... 203
3.13.4 Result Verification............................................................................................................ 204
3.14 Pulse Charge Configuration ........................................................................................................ 204
3.14.1 Subscriber Group Configuration ...................................................................................... 205
3.14.2 Number Prefix Group....................................................................................................... 207
3.14.3 Common-time Discount Configuration............................................................................ 209
3.14.4 Holiday Discount Configuration ...................................................................................... 211
3.14.5 Rate Configuration ........................................................................................................... 213
3.14.6 Group Rate Configuration................................................................................................ 216
3.14.7 Supplementary Service Rate Configuration ..................................................................... 218
3.15 OTA Configuration...................................................................................................................... 220
4 Configuration Tools................................................................................................................................ 223
4.1 Overview....................................................................................................................................... 223
4.2 Main Interface ............................................................................................................................... 223
4.3 Data Synchronization .................................................................................................................... 224
4.4 Backup and Restoration ................................................................................................................ 226
4.5 Security Variable ........................................................................................................................... 229
v
1 Overview
Key points
Basic configuration sequence
1.1 Overview of Configuration Management System

The data configuration management system is a database management system with
complete functions and is used to manage the resources of the switch. It has visual and
friendly interfaces and provides the required configuration data for the normal
operation of the MSCe, such as the system subscriber capacity, inter-office signaling
mode, and supported service types. The data configuration determines the operation
mode and status of the switch. It is the core part of the whole MSCe system and the
most frequently used part in the background maintenance system.
1.2 Basic Configuration Sequence

The ZXC10-MSCe configuration database is very large, and the data are complicated
and interrelated. Therefore, data must be configured in a specific order. Figure 1.2-1
shows the basic configuration sequence of the ZXC10-MSCe.
1
CM3G-302-E1 Introduction to the ZXC10 MSCe Data Configuration
Physical
configuration
Office
configuration
No. 7 data
configuration
Sigtran
configuration
Mobile office
configuration
Handoff office
configuration
Topological relation
configuration
Trunk management
configuration
BSC
configuration
Mobile area code

configuration
Other
configurations
Data
synchronization
Figure 1.2-1 Basic Data Configuration Sequence of the MSCe
Specific steps:
1. To configure a shelf, follow this procedure: module->rack->shelf->board, and

then configure the IP address used for association.
2
Chapter 1 Overview
2. When configuring the local office, do not select a selector temporarily.
3. Configure the signaling link to each office direction.
4. Configure the association with each office direction.
5. Configure related data for the mobile office, involving planning capacity for
mobile office, mobile data configuration, MSC ID configuration, and VMSC
configuration. Do not select the number analysis selector temporarily.
6. Build the trunk group relationship between the adjacent office and the local
office, and configure the handoff office.
7. Configure inter-office topology relationship, including the relationship between

the BSC and the MGW, configuration of the device node connecting offices,
codec configuration for the inter-office communication, and SIP configuration
for inter-MSCe communication.
8. Configure the trunk routes between MSCe and other offices. Do not select the
number analysis selector temporarily.
9. Configure the route relationship between the MSCe and the BSC.
10. Configure mobile area codes, including location area, global cell, area code,
special service template, special service group, and VMSC location.
11. Other data configuration: After steps 1-9, configure other data. Other data
configuration involves GT data configuration, number analysis configuration,
H248 configuration, SIP configuration, numbering GT data, code scheme
configuration, VLR configuration, KD-KB-ICP configuration, voice resource
configuration, pulse charging configuration, OTA configuration, and so on.
Steps 1-11 constitute the basic configuration procedure of the ZXC10 MSCe.
After completing the basic configuration, you also need to perform the
subsequent operations:
12. Check the running state of the office, and ensure the correct data configuration.
13. Perform data synchronization on the R_CONST table, and then synchronize the
data to the foreground by synchronizing the whole table.
14. Back up the data and make a report.
For the operation & maintenance system of the ZXC10 MSCe, basic configuration is
3
the basis of operation and maintenance, so you shall be familiar with it.
4
2 Node Configuration
Key points
· Node configuration
· Unit configuration
· Network connection configuration
· System node configuration
· Office capacity configuration
· No. 7 data configuration
· Sigtran configuration
2.1 Overview
The node configuration involves:
· Browsing the physical structure of an exchange (including the hierarchy of

modules, racks, shelves, and boards).
· Modifying the physical configuration of an exchange (for example,

adding/modifying/deleting modules, racks, shelves, and circuit boards).
· Adding/modifying/deleting No. 7 data, office configuration data, and Sigtran

configuration data.
To configure a node, follow this procedure: module->rack->shelf->board. To delete the

node, follow the opposite procedure. When configuring or deleting a node, follow the
corresponding procedure strictly.
When configuring a new office, follow this procedure to implement physical

configuration:
1. Add new rack
2. Add new subrack according to the physical shelves.
3. Configure circuit boards for the shelves.

5
4. Configure module attribute for the MP board.
5. Configure module/board relationship.
6. Configure IP interface, timezone, timer, summer time, CPU overload threshold,

and NE parameters.
7. Configure offices, including local office, signaling, adjacent office, and SIP
office direction, and do not select the number analysis selector temporarily.
8. Configure No. 7 data. To configure M2UA and M2PA, configure Sigtran first.
9. Configure Sigtran.
2.2 Main Interface

On the main interface of the ZTE unified network management platform, select
Application > Configuration Management, as shown in Figure 2.2-1.
Figure 2.2-1 Configuration Management Main Interface
The interface of the configuration management subsystem consists of menu bar, toolbar,
configuration navigation tree, main window, and status bar.
6
Chapter 1 Overview
In the left pane, click the root node OMC on the configuration navigation tree to
expand the second layer, click the second-layer node until the configuration navigation
tree is fully expanded.
Figure 2.2-2 shows the fully expanded configuration tree when no data is configured.
Figure 2.2-2 Fully Expanded Configuration Navigation Tree–No Data Configured
2.3 Physical Configuration

1. Tasks and functions of physical configuration
7
Physical structure is the basis for the running of the system. Therefore, physical
configuration is the prerequisite to any other configuration, and it shall be
completed first.
The tasks of physical configuration are to build an environment corresponding to

the foreground physical structure at the background by configuring the
following data and to manage the environment.
· The physical attributes, physical positions, and hierarchy of the physical

hardware (shelf, rack, slot, and board), which are the principal part of physical
configuration..
· Logical data, including unit, HW, sub-unit, and the ports to be used. The logical
data is configured based on the physical data according to the requirements of
the foreground and the background.
· Independent data of each module. It is formed by transferring the logical data to

the foreground and the background.
Therefore, the physical configuration has the following functions:
· Browsing the physical structure of an exchange (the hierarchy of modules, racks,

shelves, circuit boards, and so on).
· Modifying the physical configuration of an exchange (for example,

adding/modifying/deleting modules, racks, shelves, circuit boards, and so on).
· Implementing unit configuration, including the configuration of units, HW,

sub-units, and ports.
2. Procedure for physical configuration
When implementing physical configuration, follow this procedure:

rack->shelf->slot.
When implementing physical configuration for a new office, follow this

procedure:
1) Add an IP rack for the module.
2) Add shelves for the newly added IP rack according to the actual physical
hardware. The type of the MSCe shelf shall be configured as control shelf.
3) Add circuit boards for the newly added shelves.
8
Chapter 1 Overview
4) Configure planning parameters such as module type and module capacity for the
MP board.
4) Configure module/board relationship for all other boards except MP boards.
5) Configure IP address and static route.
6) When deleting the configuration, follow the opposite procedure.
S Caution:
The configuration data of the system is very complicated and mutually associated.
Therefore, when implementing or deleting configuration, follow the corresponding
procedure strictly.
2.3.1 Configuring Racks
1. Objective
In the physical configuration window, select a module, add or delete an IP rack.

After adding an IP rack, configure its attributes to offer environment for the
configuration of shelves and slots.
2. Preliminary setup
· The OMC server and the OMC client run well.
· The database is connected well.
· If you want to delete a rack, the rack shall exist and be configured with no shelf
or circuit board.
3. Detailed procedure for adding a rack
1) Open the interface.
On the configuration management main interface, right-click Physical

configuration under Node configuration, and then select Add IP Rack. The
Add Rack dialog box appears, as shown in Figure 2.3-1.
9
Figure 2.3-1 Adding a Rack
Rack: Number of the rack. It ranges from 1 to 16. In configuring a new

exchange, the rack number starts from 1 by default. If the OMP board needs to
be configured in the new rack, the rack number shall be 1.
RackType: Type of the rack. By default, it is an IP rack.
2) Configure a new rack.
In the Add Rack dialog box, select the desired rack number and type, and then
click OK.
To abort the addition, click Cancel.
4. Verify the addition.
After the rack is added successfully, "IP Rack[1]" appear under Physical
configuration on the configuration navigation tree. Click IP Rack[1], and the
configuration of the IP rack appears in the right panel. By default, the four
shelves (1, 2, 3, and 4 from top to bottom) are empty, as shown in Figure 2.3-2.
10
Chapter 1 Overview
Figure 2.3-2 Newly Added IP Rack
Right-click at any position in the physical configuration window. The shortcut

menu for rack configuration appears, as shown in Figure 2.3-3
Figure 2.3-3 Shortcut Menu for Rack Configuration.
2.3.2 Configuring Shelves
1. Objective
In the physical configuration window, select a rack (for example, IP Rack[1],

and then add or delete a shelf. After adding a shelf, configure its attributes to
offer environment for slot configuration.
· The rack is configured successfully.
11
· If you want to delete a shelf, the shelf shall exist and be configured with no
circuit board.
3. Detailed procedure for adding a shelf
1) Open the rack physical configuration window.
Expand the configuration navigation tree, and then click the desired rack (for
example, IP Rack[1]) to display the physical configuration window,.
2) Open the shelf configuration interface.
In the rack physical configuration window, right-click at any position of a shelf,

and then select Add Shelf. The Add Shelf dialog box appears, as shown in
Figure 2.3-14
Figure 2.3-4 Adding a Shelf
Shelf: Number of the shelf on which you right-click. If the shelf needs to be
configured with the OMP board of the MSCe network element (NE), you shall
select shelf 2.
ShelfType: Type of the shelf where the MSCe NE is located. By default, it is a

control shelf.
3) Configure a new shelf.
In the Add Shelf dialog box, select the desired shelf number and type, and then
12
Chapter 1 Overview
click OK.
After the shelf is added, the shelf configuration appears in the rack (for example,
IP Rack[1]) configuration window. By default, all the slots (1~17) are empty, as
shown in Figure 2.3-5.
Figure 2.3-5 Rack Configuration Window-Newly Added Shelf 2
Right-click at any position of the added shelf. The shortcut menu for shelf
configuration appears, as shown in Figure 2.3-4.
Figure 2.3-4 Shortcut Menu for Shelf Configuration
2.3.3 Configuring Boards
1. Objective
13
In the physical configuration window, select a shelf (for example, shelf 2 on IP

Rack[1]), add a board for each slot, and then configure physical attributes for
each boar; or delete an existing board.
Because each board corresponds to one slot, board configuration is also called
"slot configuration".
There are various boards in the MSCe system. Table 2.3-1 shows their names,
types, and functions.
Table 2.3-1 Boards in the MSCe System
Board Relationship with

Meaning Type Function Default Slot
Name Module
The OMP provides external operation and OMP: 11
OMP/ Main processing maintenance Ethernet interface to connect with and 12;
MPX86
SMP unit the background. The SMP implements functions SMP: 5 and
call control and H.248 signaling processing. 6.
It is the signaling switching center of the control
It belongs to a
Universal interface subrack. It completes information exchange
UIMC UIM 9 and 10 module
card between the circuit boards and offers control
containing OMP.
Ethernet channels for external connection.
Multi-function It provides centralized access for 39/xx It belongs to a
IPI/SIG network interface MNIC interfaces, zz interfaces, and the universal server 3 and 4 module
board interfaces. containing OMP.
It belongs to a
Signaling It processes HDLC and the layers below MTP-2
SPB SPB 17 module
processing board of multiple channels of No. 7 signaling.
containing OMP.
It belongs to a
Charging interface It transfers the CDRs from the SMP to the
CIB MPX86 1 and 2 module
board charging server for processing.
containing OMP.
Control plane It belongs to a
It converges the control flows between multiple
CHUB interconnection CHUB 15 and 16 module
shelves
board containing OMP.
It belongs to a
CLKG Clock generator CLKG It provides clock signal for the MSCe system. 13 and 14 module
containing OMP.
In general, follow the procedure below to configure the boards.
1) UIM board. In the MSCe, the UIM board is UIMC board whose SBType is
"SBT_3G_2CPU" (see Figure 2.3-7). The UIMC shall be configured in pair in
14
Chapter 1 Overview
slots 9 and 10.
2) MP boards, including OMP and SMP. The MP boards shall be configured in pair.
3) SIG_IPI board. It shall be configured in pair.
4) CIB board. It shall be configured in pair.
5) Other boards. The CHUB and the PWRD shall be configured in pair. If only one
shelf is used, CHUB needs not to be configured.
y Note:
Pair configuration is to configure two boards of the same type and their configurations
are the same. First configure a board in the odd slot (the active slot by default). And
when you configure a board in the even slot on the right, the system only offers a board
of the same type for selection.
· The shelf is configured successfully.
· If you want to delete a board, the board shall exist and be not configured.
3. Detailed procedure for adding a board.
1) Open the rack physical configuration window.
Expand the configuration navigation tree, and then click the desired rack (for
example, IP Rack[1]).
2) Open the board addition interface.
In the rack physical configuration window, right-click the desired slot on a shelf,
and then select Add Board. The Add Board dialog box appears, as shown in
Figure 2.3-7.
15
Figure 2.3-7 Adding a Board
MP Board: In general, select the MP board whose SBType is "SBT_3G_2CPU".
3) Add a board.
On the Add Board interface, select the desired board, and then click OK. To
abort the addition, click Cancel.
Repeat Steps 2 and 3 to add other boards for the shelf.
S Caution:
In adding a board, the board slot shall correspond to the board type. For details, see
ZXC10 MSCe(V2.0) cdma2000 Mobile Switching Center Emulator Hardware
Manual.
If the board is inserted in the improper slot, an error message is displayed.
16
Chapter 1 Overview
1) View the configuration interface.
After the board is added, the physical configuration window appears, as shown
in Figure 2.3-8.
Figure 2.3-8 Physical Configuration Window After Board Addition
2) View board information.
Configure the board after the board is added. You can double-click the board to
view its configuration information.
After you double-click the UIM board, the UIM board information interface
appears as shown in Figure 2.3-9. "Unit" indicates the insertion sequence of the
board; for example, "1" indicates that type 1 board is inserted in the slot. For the
MP boards, no unit number is available.
17
Figure 2.3-9 UIM Board Information
Right-click the MP board, the shortcut menu appears, as shown in Figure 2.3-10.
Figure 2.3-10 Shortcut Menu for MP Configuration
Right-click at any other board except MP, the shortcut menu appears as shown in
Figure 2.3-11.
18
Chapter 1 Overview
Figure 2.3-11 Shortcut Menu for Other Boards
2.3.4 Configuring Module Types
1. Objective
In the MSCe(V2.0) system, each MPX86 board has two CPUs to offer the
function of one or more types of processing modules, including OMP, SMP,
CMP, MPU, and RPU (for the functions of the modules, see ZXC10 MSCe
(V2.0) cdma2000 Mobile Switching Center Emulator Hardware Manual).
After MP is added, no module type information is available by default, as shown

in Figure 2.3-52.
Figure 2.3-52 Default MP Information-No Module Type Configuration
19
The task of configuring module type is to specify the relationship between the
CPU in a MP and the above processing modules. After the configuration data is
synchronized to the foreground, the system loads the configured module type for
each CPU to offer the functions of the corresponding module.
The following principles show how to configure module type for the CPU in a
MP according to the system requirements:
· For module types containing OMP, for example MT_3G_OMP and

MT_3G_OMP_SMP_CMP (OMP, SMP and CMP are combined), you can only
configure CPU 1 in the MP board in slot 11 in shelf 2 on rack 1.
· In principle, other CPUs can be configured with any other module types. In
general, CPU 2 in the MP board in slot 11 in shelf 2 on rack 1 is configured with
the MT_3G_RPU module type.
· The MP board is added successfully.
· If you want to delete a module type, the module type shall exist.
3. Detailed procedure for configuring a module type.
The following example shows how to configure a module type for CPU 1 in the
MP board in slot 11 in shelf 2 on rack 1.
1) Open the module type configuration interface.
In the physical configuration window, right-click the desired MP board, and then
select Configure Module Type (see Figure 2.3-10). The Configure module
type interface appears, as shown in Figure 2.3-63.
20
Chapter 1 Overview
Figure 2.3-63 Configuring a Module Type
CpuNo: CPU number in the MP board. For the MP/2 board, there are two CPUs,
and they are numbered 1 and 2.
Module: Number corresponding to a module type. It is automatically generated

after you select a module type.
ModuleType: The program modules that can run on the MP board, including
OMP, SMP, CMP, MPU, RPU, and their combinations, as shown in Figure
2.3-74.
2) Enter the module information configuration interface.
On the module type configuration interface (see Figure 2.3-63), select the first
record, and then double-click the ModuleType field. The module information
configuration interface appears, as shown in Figure 2.3-74.
21
Figure 2.3-74 Configuring Module Information
3) Configure module information
In the MP module type list on the module information configuration interface,

select "MT_3G_OMP_SMP_CMP" for CPU 1, and then click OK.
To abort the configuration, click Cancel.
Repeat Steps 2 and 3 to configure a module type for CPU 2. Here, select
"MT_3G_RPU".
When configuring the module types, follow the above mentioned principles;
otherwise, an error message is displayed.
Figure 2.3-85 shows the error message displayed when the OMP module type is
not configured for the specified CPU.
22
Chapter 1 Overview
Figure 2.3-85 Incorrect Configuration of OMP Module Type
4) End the configuration.
After the configuration, click OK on the module information configuration

interface to return to the module type configuration interface. The module type
configuration of the MP board is displayed, as shown in Figure 2.3-96.
Figure 2.3-96 Completing the Module Type Configuration
Description of the above figure: CPU 1 in the selected MP offers the functions
of the OMP, SMP, and CMP modules; CPU 2 offers the functions of the RPU
module.
Click Close.
y Note:
You only need to configure the module type for either MP board in the MP pair; the
23
system configures the module type for another MP automatically; and the
configurations of the two MP boards are the same. This holds tree for the configuration
of the capacity planning data.
4. Verify the configuration.
After configuring the module type for the MP board, double-click the MP board
to view the module type information, as shown in Figure 2.3-107.
According to the above description, the module type configurations of the MP

pair shall be the same.
Figure 2.3-107 MPX86 Board Information-After the Configuration of Module Type
S Caution:
Only the MP boards support this configuration item.
To modify a module type, delete it, and then add a new one. For the procedure, see the
24
Chapter 1 Overview
above description.
2.3.5 Configuring Capacity Planning Parameters
1. Objective
To configure capacity planning data for MP board.
· The MP board is added successfully.
3. Detailed procedure
1) Open the interface for configuring the capacity planning data.
In the physical configuration window, right-click the desired MP board, and then
select Configure Content Const (see Figure 2.3-10). The Configure Content
Const interface appears, as shown in Figure 2.3-118.
25
Figure 2.3-118 Configuring Capacity Planning Parameters
Module: It refers to the module number on the Configure module type

interface.
From OMP: To download data from the OMP, select "Yes"; otherwise, select
"No".
VUserMax: The maximum number of the users supported by the module.
VOffice: The maximum number of the adjacent offices that can be configured
for the local office.
2) Configure capacity planning parameters.
Select the desired module number, configure the capacity parameters, and then
click Apply.
After applying the configuration, click Close.
y Note:
Only the MP boards support this configuration item.
2.3.6 Configuring Module/Board Relationship
1. Objective
To configure module types for other boards except MP. Each board can only
belong to one module type.
· The module type and capacity planning parameters of the MP boards are
configured.
· The board is added successfully.
3. Detailed procedure for configuring module/board relationship.
1) Open the interface for configuring module/board relationship.
26
Chapter 1 Overview
In the physical configuration window, right-click the desired board (for example,
the UIMC board), and then select Configure module/unit relationship (see
Figure 2.3-11). The Configure module/unit relationship interface appears, as
Figure 2.3-129 Configuring Module/Board Relationship
2) Configure module/unit relationship.
In the Available Module area, select the desired module type, and then click
Add. The selected module type appears in the Module which has been
connected to Unit area, as shown in Figure 2.3-.
27
Figure 2.3-20 Completing the Configuration of Module/Unit Relationship
Description: The board belongs to the OMP_SMP_CMP module type.
Click Close to return to the physical configuration window.
y Note:
You only need to configure the module type for either board in the board pair; the
system configures the module type for another board automatically; and the
configurations of the two boards are the same.
4. Verify the configuration.
In the physical configuration window, double-click the board (for example, the
UIMC board) configured with the module/board relationship. The board
information interface shows the configured module/board relationship, as shown
in Figure 2.3-21.
28
Chapter 1 Overview
Figure 2.3-21 UIM Board Information Interface-After the Configuration of Module/Board
Relationship
S Caution:
To modify the module/board relationship, delete it, and then add it again. For the
procedure, see the above description.
2.3.7 Configuring IP Interfaces
1. Objective
To configure necessary IP addresses for establishing association.
· The board is added successfully.
29
3. Configure an IP interface.
1) Open the IP interface configuration interface.

configuration under Node configuration on the configuration navigation tree,
and then select Configure IP Interface. The Configure IP Interface dialog box
appears, as shown in Figure 2.3-132.
Figure 2.3-132 Configuring an IP Interface
2) Configure an IP interface.
In the Unit or Module Info of Configurable Interface area, select the desired
record, and then click Add IP Interface, as shown in Figure 2.3-143.
30
Chapter 1 Overview
Figure 2.3-143 Adding an IP Interface
Port: Accept the default value. It is not necessary to modify it.
IpNo: One port can be configured with four IP addresses. The IP addresses are
distinguished by IP numbers.
IpAddr: IP address of the port. In general, configure the interface address of the
SMP as a virtual address.
SubnetMask: Mask of the interface IP address. In general, it is 255.255.255.255

for a virtual address.
BroadcastAddr: Accept the default value. It is not necessary to modify it.
MAC: The MAC address corresponding to the IP address. The first four parts of
the MAC address are fixed and cannot be modified; the range of the fifth part is
D0~FF; and the range of the six part is not limited. In general, the MAC address
of a virtual address is 00-00-00-00-00-00.
After completing the configuration, click OK to return to the IP interface

configuration interface, as shown in Figure 2.3-154.
31
Figure 2.3-154 Completing the Configuration of IP Interface
2.3.8 Configuring IP Static Routes
1. Objective
If the IP addresses of two offices are not within the same subnet, the static routes
shall be configured to ensure normal communication.
· The IP interface is configured.
3. Configure an IP static route.
1) Open the interface for configuring IP static route.

32
Chapter 1 Overview
and then select Configure IP Static Route. The Configure IP Static Route
interface appears, as shown in Figure 2.3-165.
Figure 2.3-165 Configuring an IP Static Route
2) Configure an IP static route.
On the Configure IP Static Route interface, click Add to display the Add IP
Static Route dialog box, as shown in Figure 2.3-176.
33
Figure 2.3-176 Adding an IP Static Route
RoutePrefix: Network prefix of the route address.
SubnetMask: Mask of the route address.
Hoporintf: Flag of the next hop. Accept the default value.
NextHop: IP address of the next hop.
Distance: Management distance of the route. It is 1 by default.
Tag: Tag value of the route. It is 3 by default.
After completing the configuration, click Close, as shown in Figure 2.3-187.
34
Chapter 1 Overview
Figure 2.3-187 Ending the Configuration
4. Verify the configuration

and then select Configure IP Static Route. The Configure IP Static Route
2.4 Office Configuration

1. Objective
· To configure network data and signaling for the local office.
· To configure network data for the adjacent office.
· To configure SIP office direction.
· The physical configuration of the local office is completed.
35
2.4.1 Local Office Configuration
1. Open the interface.
On the configuration management main interface, select Office configuration

under Node configuration on the configuration navigation tree. The Office
Configuration interface appears in the right pane, and the Configuration of
Local Office tab is displayed by default, as shown in Figure 2.4-1.
Figure 2.4-1 Configuration of Local Office
: Adds configuration.
: Modifies configuration.
: Deletes configuration.
Test Code: Set any number sequence (it can be up to 15 digits). It is used for the
test message between the local office and adjacent office.
Exchange Office Type: Select one or more options as required
Basic Network Type: Currently, the switching networks include China Telecom
Network (CTCN), China Mobile Communication Network, China Unicom
36
Chapter 1 Overview
Communication Network (CUCN), Railway Telecom Network (RLTN), and so

on. Select the network type of the local office as required.
Interface Network Type: The network type when the NE serves as the interface
network.
SPC Type: Select one option as required.
Restart Time: Set it as required. When Signaling End Point SEP is selected, it is
not necessary to configure Restart Time.
2. Configure local office.
Enter or select the desired data, and then click to complete the
configuration. The interface as shown in 错误！未找到引用源。2 appears.
Figure 2.4-2 Completing Configuration of Local Office
2.4.2 Signaling Configuration
In the office configuration window (see Figure 2.4-1), click the Signaling
Configuration tab. Figure 2.4-3 shows an example of signaling configuration.
37
Figure 2.4-3 Signaling Configuration
Network Type: It displays the network type configured on the Configuration of

Local Office tab.
14-/24-SPC: Select 14-bit SPC or 24-bit SPC. The ZXC10 MSCe is compatible
with the two code types. A code of either type consists of three subcodes.
Network Appearance: The network appearance of the exchange office. In

general, it is set as 3 for Unicom network.
Region Code: It identifies a region.
User Type: It indicates the user type that can be processed in the signaling
system. Multiple options can be selected. In general, select "H248 User" for the
MSCe NE.
2. Configure signaling data.
Enter or select the desired data, and then click to complete the signaling
configuration.
38
Chapter 1 Overview
2.4.3 Adjacent Office Configuration
An adjacent office refers to an office that has signaling links to the local office.
Configuring adjacent office is to build the signaling link relationship between the local
office and the adjacent office.
In the office configuration window (see Figure 2.4-1), click the Adjacent Office
Configuration tab, as shown in Figure 2.4-4.
Figure 2.4-4 Adjacent Office Configuration
Office ID: A number that identifies the adjaent office. The value range is 1~256.
Adjacent Office Name: The name of the adjacent office set by the user to
facilitate management.
Sub-service Field (SSF): It is a concept in the SS7 signaling system, including

domestic SPC, reserved domestic SPC, international SPC, and reserved
international SPC.
Signaling Point Code (SPC): Select 14-bit SPC or 24-bit SPC. The ZXC10
MSCe is compatible with the two code types. In China, the 24-bit SPC is used.
39
The SPC is in decimal system and binary system. After you enter the decimal
code, the binary code is automatically obtained.
Adjacent Office Network Type: It indicates the type of the adjacent office:
Unicom network, Mobile network etc.
Toll Area Code: The code of the area in which the adjacent office is located.
SPC Type: The type of the SPC: Signaling End Point (SEP), Signaling Transfer
Point (STP), and Signaling End/Transfer Point (STEP).
SS7: The options include China standard, ITU-T standard, and ANSI standard.
Connection Mode: If there are associated/direct signaling links between the local
office and the adjacent office, select Associated; otherwise, select
Quasi-associated.
Domain Type: The domain type used by the services between the local office
and the adjacent office. The options include SCN (circuit domain) and IP
domain. The IP domain can be used between 3G equipment only.
Mark: Describes the code type and other attributes of the network.
Adjacent Office Type: It indicates the type of the adjacent office. Select it as
required.
2. Add an adjacent office.
1) Open the interface for adding an adjacent office.
On the Adjacent Office Configuration tab (see Figure 2.4-4), click to

display the Add adjacent office information interface. For the parameters on
the interface, see “Open the interface” in this section ("Adjacent Office ID" is
the "Office ID" on the Adjacent Office Configuration tab).
2) Add an adjacent office.
On the Add adjacent office information interface, enter the desired parameters,
as shown in Figure 2.4-5.
40
Chapter 1 Overview
Figure 2.4-5 Adding an Adjacent Office
Click OK. A dialog box prompts that the addition succeeds.
Click OK to return to the Add adjacent office information interface. You can
add other adjacent offices in the same way.
3) Query information about the newly added adjacent office.
On the Adjacent Office Configuration interface, select the desired office ID

(for example, 1) to display its configuration information, as shown in Figure
2.4-6.
41
Figure 2.4-6 Configuration Information About the Newly Added Adjacent Office
2.4.4 SIP Office Configuration
SIP office refers to an adjacent office that has SIP connections to the local office.
In the office configuration window (see Figure 2.4-1), click the SIP Office
42
Chapter 1 Overview
Figure 2.4-7 SIP Office Configuration
Office ID: It uniquely identifies the adjacent office that has SIP connections to
the local office. The adjacent office shall exist.
IP Address: IP address of the opposite interface board.
DAS: It displays the configured number analysis selector.
3. Add a SIP office.
1) Open the interface for adding a SIP office
On the SIP Office Configuration tab, click to display the Add SIP office
interface. For the parameters on the interface, see “Open the interface” in this
section.
2) Add a SIP office.
On the Add SIP office interface, enter the desired parameters, as shown in
Figure 2.4-8.
Select the desired office ID from the Office ID drop-down list. Set other
parameters except IP address when configuring number analysis, and then select
them here.
43
Figure 2.4-8 Adding an SIP Office
Click OK. A dialog box prompts that the addition succeeds.
Click OK to return to the Add SIP office interface. You can add other SIP
offices in the same way.
The Add SIP office interface displays the newly added SIP office, as shown in
Figure 2.4-9.
44
Chapter 1 Overview
Figure 2.4-9 Configuration Information About the Newly Added SIP Office
2.4.5 Verification
Log out the configuration management subsystem, log in again, and then check
whether the configuration data of the local office is saved in the database or not.
2.5 No. 7 Data Configuration―MTP Configuration

1. Objective
As the bottom layer of the SS7 system, the message transfer part (MTP)
provides reliable signaling transfer for the user part. MTP configuration involves
configuring signaling link group, signaling link, signaling route, and signaling
office direction used for the message transfer between the local office and the
adjacent office.
· The communication between the foreground and the background is normal.
· The physical configuration is completed.
45
· The adjacent office is configured.
3. Procedure
To configure MTP, follow this procedure: signaling link group->signaling

link->signaling route->signaling office direction. To delete MTP configuration,
follow the opposite procedure.
1) Configure the adjacent office, and determine the adjacent office ID.
2) Configure signaling link group. One adjacent office corresponds to one signaling
link group.
3) Configure signaling link, that is, allocate signaling link for the signaling link
group.
4) Configure signaling route, that is, allocate signaling link group for the signaling
route. The load sharing mode can be used.
5) Configure signaling office, that is, allocate signaling route for signaling office.
The active/standby mode can be used.
S Caution:
When configuring the attributes for an adjacent office, ensure that No. 7 signaling type
and the subprotocol type match. If they mismatch, the signaling link might be abnormal.
In general, for the domestic signaling network in China, configure the No. 7 protocol
type as China standard and the subprotocol type as the default mode.
2.5.1 Configuring Signaling Link Groups
Click MTP configuration under No. 7 data configuration on the configuration

navigation tree. The MTP Configuration interface appears, and the Signaling
Link Group Configuration tab is displayed by default, as shown in Figure
2.5-1.
46
Chapter 1 Overview
Figure 2.5-1 MTP Management
Signaling Link Group: A set of all the signaling links that connect two signaling
points. Several signaling links between the local office and a certain adjacent
office constitutes a signaling link group. Maximum there can be 16 signaling
links in a signaling link group.
Associated Office ID: The ID of the adjacent office associated with the signaling
link group. It is set during the adjacent office configuration.
Link Number: It is automatically generated after the signaling links are

configured.
Signaling Link Group Type: It is set when configuring the signaling link. It is
automatically generated after the signaling link is configured.
2. Configure a signaling link group.
In Figure 2.5-1, click on the toolbar to display the Add signaling link
group interface, as shown in Figure 2.5-2.
47
Figure 2.5-2 Adding a Signaling Link Group
Select the desired signaling link group and the corresponding associated office
ID, and then click OK. The interface as shown in Figure 2.5-3 appears.
Repeat the procedure to add multiple signaling link groups.
Figure 2.5-3 Information About the Newly Added Signaling Link Group
48
Chapter 1 Overview
y Note:
A signaling link group can be deleted only when it contains no signaling link and does
not exist in the signaling route.
One signaling link group corresponds to one office direction.
2.5.2 Configuring Signaling Links
In Figure 2.5-1, click the Signaling Link Configuration tab, as shown in Figure
2.5-4.
Figure 2.5-4 Signaling Link Configuration
Signaling Link No.: It is allocated by the system in a unified manner.
Signaling Link Group: Number of the signaling link group to which the
signaling link belongs.
Module No.: Number of the module where the signaling link is located.
Link Code: The code of a signaling link in the signaling link group. The value
range is 0 ~ 15.
49
Carrier Link Type: The options include TDM Signaling Link 1, TDM Signaling
Link 2 and IP Signaling Link. If you select TDM Signaling Link 1, the signaling
link is connected through the SPB board. If you select TDM Signaling Link 2,
the signaling link is connected through the DTB board.
Signaling Link Type: The options include 64k narrow-band signaling link and
2M narrow-band signaling link.
Whether link is self-loop or not: Select whether to implement self-loop or not.

Note that this option works only after the physical link is self-looped.
2. Configure a signaling link.
In Figure 2.5-4, click on the toolbar to display the interface as shown in

Figure 2.5-5.
Figure 2.5-5 Adding a Signaling Link
Select the desired signaling link number and the signaling link group to which
the signaling link belongs. Select the link code and module number of the
signaling link. Select the desired carrier link type and signaling link type.
y Note:
You can add multiple signaling links on the Add signaling link interface.
50
Chapter 1 Overview
S Caution:
The selected link code shall be the same as the link code of the opposite office;
otherwise, the signaling link might be abnormal.
A signaling link can be deleted only after it is deactivated.
2.5.3 Configuring Signaling Routes
In Figure 2.5-1, click the Signaling Route Configuration tab, as shown in

Figure 2.5-6.
Figure 2.5-6 Signaling Route Configuration
Signaling Route No.: The route number allocated by the system in a unified
manner.
Signaling Link Group 1 and Signaling Link Group 2: One signaling route can
contain two signaling link groups. They are respectively specified here.
Link Alignment Mode: The alignment mode of the signaling links in the
signaling route. In general, select Random Order.
51
2. Configure a signaling route.

Figure 2.5-7.
Figure 2.5-7 Adding a Signaling Route
Select the desired signaling route number and route attribute (the included
signaling link group and the link alignment mode).
After you select the signaling link group and the link alignment mode, the
arrangement of the links is displayed in the right pane. Click OK.
52
Chapter 1 Overview
Repeat the procedure to add multiple signaling routes.
Figure 2.5-8 Information About the Newly Added Signaling Route
y Note:
The alignment mode of the signaling links between different signaling link groups
contained in the signaling route reflects the load sharing between different signaling
link groups and among different signaling links.
2.5.4 Configuring Signaling Office IDs
In Figure 2.5-1, click the Signaling Office ID Configuration tab, as shown in

Figure 2.5-9.
53
Figure 2.5-9 Signaling Office ID Configuration
Signaling Office ID: The signaling office number allocated by the system in a
unified manner.
Normal Route: The signaling route that is preferred in normal case. In general, it
is the shortest one among all the signaling routes to the opposite office.
Assistant Route 1: If the normal route is not available, this route is used. In
general, it is longer than the normal route.
Assistant Route 2: If Assistant Route 1 is not available, this route is used. In

general, it is longer than Assistant Route 1.
Assistant Route 3: If Assistant Route 2 is not available, this route is used. In

general, it is longer than Assistant Route 2.
2. Configuring a signaling office ID.

Figure 2.5-10.
54
Chapter 1 Overview
Figure 2.5-10 Adding a Signaling Office ID
Select the desired signaling office ID, and then select the desired routing mode,
including Assistant Route 1, Assistant Route 2, and Assistant Route 3.
Repeat the procedure to add multiple signaling office IDs.
2.5.5 Verification
Close the MTP data configuration, restart it, and then check whether the configuration
data is saved in the database or not.
2.6 No. 7 Data Configuration―SCCP Configuration

1. Objective
To the switching side of the CDMA communication system, the MAP signaling
between entities is transferred through SCCP. Upon receiving MAP
application-layer messages, the SCCP sends, receives, and transfers them
according to the routing label in them. The SCCP sends messages over the
network path in two modes:
· Routing by DPC+SSN. In this mode, after arriving at the intermediate node, the
signaling is directly sent through the MTP layer.
55
· Routing by GT. This mode is used if the source signaling point and some STPs
do not know the final DPC.
The task of SCCP configuration is to configure the routing label of the GT

number provided by the application layer into the GT form or the DPC+SSN
form. This facilitates the SCCP routing and ensures the accurate transfer of
signaling messages between the nodes in the signaling network.
In general, four types of GT numbers need to be configured: MSC/VLR number,

HLR number, mobile directory number (MDN), and IMSI.
For the above four number types, the principle for selecting GT is to select the
shortest prefix of the number that can identify different office directions and
analyze it.
2.6.1 Configuring GT Translation Selectors
On the configuration management main interface, select SCCP configuration

under No. 7 data configuration, which is under Node configuration. The
SCCP configuration interface appears in the right pane, and the GT Translation
Selector Configuration tab is displayed by default, as shown in Figure 2.6-1.
56
Chapter 1 Overview
Figure 2.6-1 GT Translation Selector Configuration
: Adds a GT translation selector.
: Modifies a GT translation selector.
: Deletes a GT translation selector.
: Copies GT data. It is only available on the GT Translation Data tab.
: Imports GT data from a file. It is only available on the GT Translation

Data tab.
: Exports GT data to a file. It is only available on the GT Translation

Data tab.
2. Add a GT translation selector.
1) Open the interface for adding a GT translation selector.
On the GT Translation Selector Configuration tab, click . The Add GT

translation selector interface appears, as shown in Figure 2.6-2.
57
Figure 2.6-2 Adding a GT Translation Selector
· GT Translation Selector: It uniquely identifies a GT translation selector. The

value range is 1~255. In general, configure GT translation selector 1 first. The
number of a configured GT translation selector does not appear in the
drop-down list.
· GT Type: There are four GT types: GT1~GT4. In general, select GT4.
· Address Attribute: The options include National Number and International

Number. In general, select International Number.
· Numbering Plan: The numbering plan of the GT translation selector.
· GT Translation Selector Type: It can be configured as 0 or 128 (the difference is

that the processed messages are different.
· National Minimum/Maximum Bit Length: The minimum/maximum bit length of
58
Chapter 1 Overview
the national GT number.
· International Minimum/Maximum Bit Length: The minimum/maximum bit

length of the international GT number.
· Country Code: If a GT numbers includes a country code, it is treated as a

national GT number, and the national maximum/minimum bit length is used for
GT translation; otherwise, the international maximum/minimum bit length is
used for GT translation.
· Use default GT when GT is not found In general, if no SCCP GT number is

found in the selector, the translation fails. After you select this option, the
translation result is replaced with that of the default GT number. Before
selecting this option, ensure that the default GT number is added for the selector.
You can configure the default GT when configuring the selector attributes.
2) Configure a GT translation selector.
After setting the desired parameters, click OK. The added GT translation
selector is displayed on the GT Translation Selector Configuration tab, as
Figure 2.6-3 Information About the Newly Added GT Translation Selector
59
Repeat Step 2 to add multiple GT translation selectors.
y Note:
In general, at least two GT translation selectors need to be configured. Set the

numbering plan of GT translation selector 1 to ISDN/Numbering Plan(1) for telephone
call; set the numbering plan of GT translation selector 2 to PLMN Numbering Plan(6)
for mobility management, call route request, and so on.
If the SMS function needs to be supported, GT translation selectors 3 and 4 also need
to be added.
Queries the added GT translation selectors.
After the GT translation selectors are added, they appear on the GT Translation
Selector Configuration tab, which is similar to Figure 2.6-3.
2.6.2 Configuring GT Translation Data
In the SCCP configuration window (see Figure 2.6-1), click the GT Translation
Data tab, as shown in Figure 2.6-4.
Figure 2.6-4 GT Translation Data
60
Chapter 1 Overview
· GT Translation Selector: The entrance for the GT translation. It is a part of the

GT.
· GT Code: It is available on the GT data addition and modification interfaces.

The smallest GT number prefix of the number configured for the selector. It is a
part of the GT.
· SPC Office ID: The office direction for which the signaling is sent. This DPC
can belong to STP or the final DPC.
· Routing Indicator: The options include Routing by GT and Routing by

DPC+SSN. Their differences have been stated earlier.
· Subsystem No. (SSN): Number of the subsystem.
· GT Indicator: It is used for routing by GT.
2. Add GT translation data.
1) Open the interface for adding GT translation data.
On the GT Translation Data tab, click . The Add GT translation data

Figure 2.6-5 Adding GT Translation Data
2) Configure GT translation data.
Set the desired parameters, and then click OK.
61
Repeat the procedure to add more GT translation data.
3) Query added GT translation data.
After the GT data is added, it appears on the GT Translation Data tab, as

Figure 2.6-6 Newly Added GT Translation Data
3. Copy GT data.
1) Open the interface for copying GT data.
On the GT Translation Data tab, click . The GT data copy interface

appears, as shown in Figure 2.6-7.
62
Chapter 1 Overview
Figure 2.6-7 Copying GT Data
Source Number Selector: The selector from which the data is copied.
Destination Number Selector: The selector to which the data is copied.
2) Copy GT translation data from the source number selector to the destination
number selector.
Select the desired source number selector and destination number selector from
the respective drop-down lists. The list below the drop-down list displays the GT
data of the selected selector.
In the list below the Source Number Selector drop-down list, select the desired
GT data, and then click > to copy it to the list below the Destination Number
Selector drop-down list.
You can click >> to copy all the numbers of the source number selector to the
destination number selector.
4. Import GT translation data.
On the GT Translation Data tab, click to display the interface as shown

in Figure 2.6-8.
63
Figure 2.6-8 Importing GT Translation Data
Select the file that saves the GT data, and then click Open. The system
automatically imports the GT data to the file and prompts the operation result
(success or failure)
5. Export the GT translation data.
On the GT Translation Data tab, click to display the interface as shown

in Figure 2.6-9.
64
Chapter 1 Overview
Figure 2.6-9 Exporting GT Translation Data
Select the directory and file for saving the GT data to be exported, and then click
Save. The system automatically exports the GT data to the file and prompts the
operation result (success or failure).
If the file for saving the data to be exported is unavailable, you can enter the
desired file name, and the system automatically creates the file and exports the
data to the file.
2.6.3 Verification
Log out of the configuration management subsystem, log in again, and then check
whether the SCCP configuration data is saved in the database or not.
2.7 No. 7 Data Configuration―SSN Configuration

1. Objective
SSN is the local addressing information used by the SCCP. It is used to identify
each SCCP user of a node. The SSCP can send messages to the subsystems and
the related functional units can work normally only when a correct SSN is
configured.
65
The SSN data in the system is automatically generated after the adjacent office
configuration is completed. In general, it needs not to be configured separately.
To meet some special requirements, the following introduces how to add, modify,
and delete SSN. Table 2.7-1 shows the subsystems that need to be configured for
different types of offices.
Table 2.7-1 Subsystems That Need to Be Configured for Different Types of Offices
SSN
SSN Name BSC MSC/VLR HLR/HLRe SC SCP/SCPe SGW AUC SCF OTAF MGW MSCe MPC
No.
No subsystem is
0 √ √ √ √ √ √ √ √ √ √ √ √
included.
SCCP
1 √ √ √ √ √ √ √ √ √ √ √ √
management
2 Reserved
3 ISDN user part
4 OAM part √ √ √ √ √ √ √ √ √ √ √ √
5 Mobile user part
6 HLR √
7 VLR √ √
8 MSC √ √
Equipment
9 identification
center
Authentication
10
center
11 Reserved
Intelligent
12 network √
application part
Short message
238 √
subsystem
Mobile intelligent
239 √
SSP/SCP
BSC
250 √
(BSSAP-LE)
MSC
251
(BSSAP-LE)
252 SMLC
66
Chapter 1 Overview
SSN
SSN Name BSC MSC/VLR HLR/HLRe SC SCP/SCPe SGW AUC SCF OTAF MGW MSCe MPC
No.
(BSSAP-LE)
BSS operation &
253 √
maintenance part
254 BSS application √
255 Reserved
· The adjacent office configuration is completed.
3. Detailed procedure
On the configuration management main interface, select SSN configuration

under No. 7 data configuration, which is under Node configuration. The SSN
configuration interface appears in the right pane, and no configuration record is
available, as shown in Figure 2.7-1.
67
Figure 2.7-1 SSN Configuration
· Office ID: The office ID corresponding to a signaling point. The value range is
0~255.
· SSN Code: See Table 2.7-1.
· With standby subsystem: 0 indicates that no standby subsystem is available, and

1 indicates that a standby subsystem is available.
· Standby SSN Office ID: The value range is 0~255.
· Standby SSN Code: It is the same as the active SSN code.
2) Add a subsystem.
In the SSN configuration window (see Figure 2.7-1), click . The Add SSN
Configuration dialog box appears, as shown in Figure 2.7-2. For the parameters
on the interface, see “Open the interface” in this section.
Figure 2.7-2 Adding a Subsystem
Configure the desired parameters, and then click OK.
Repeat the procedure to add multiple signaling subsystems.
Click Cancel or at the upper right corner to return to the GT SSN

configuration window. The added subsystem is displayed.
68
Chapter 1 Overview
y Note:
In general, the SSN configuration is automatically generated after the adjacent office
configuration is completed. Do not modify the SSN configuration if unnecessary.
4. Verification
Log out from the configuration management subsystem, log in again, and then
check whether the SSN configuration data is saved in the database or not.
2.8 No. 7 Data Configuration―Narrow-band Signaling Configuration

1. Objective
To configure the MTP3 bearer links to ensure the normal communication of the
signaling links.
· The communication between the foreground and the background is normal.
· The MTP configuration is completed.
· The Sigtran configuration is completed.
3. Configure a type 1 narrow-band signaling link.
Click Narrow-band signaling configuration under No. 7 data configuration

on the configuration navigation tree. The narrow-band signaling link
configuration interface appears, as shown in Figure 2.8-1.
69
Figure 2.8-1 Narrow-band Signaling Link Configuration
Signaling Link No.: It is configured during the MTP configuration.
SPB Unit No.: It is automatically generated during the board configuration in

the physical configuration.
CPU No.: Set it according to the situation. In general, set it to CPU 1.
SPB E1 No.: Configure it according to the physical connection.
Originating TS No.: Configure it according to the physical connection. Ensure

that it is the same at both sides.
TS number: It is generated by the system.
y Note:
Type 1 narrow-band signaling link configuration is to configure the signaling links that
are connected through the SPB board.
2) Add a type 1 narrow-band signaling link.

Figure 2.8-2.
70
Chapter 1 Overview
Figure 2.8-2 Adding a Narrow-band Signaling Link
Repeat the procedure to add multiple narrow-band signaling links.
2.9 Sigtran Configuration

1. Objective
Associations are established between the MSCe and the MGW and between the
MSCes to communicate well with the MGW and other MSCes.
· The adjacent office configuration is completed.
2.9.1 Configuring SCTP Basic Connection
On the configuration management main interface, select Sigtran configuration

under Node configuration on the navigation tree. The Sigtran configuration
interface appears in the right pane, the SCTP Basic Connection Configuration
tab is displayed by default, and no record is available, as shown in Figure 2.9-1.
71
Figure 2.9-1 SCTP Basic Connection Configuration
2. Add a SCTP basic connection.
1) Open the interface for adding a SCTP basic connection.
On the SCTP Basic Connection Configuration tab (see Figure 2.9-1), click
. The Add SCTP basic connection interface appears, as shown in Figure

2.9-2.
72
Chapter 1 Overview
Figure 2.9-2 Adding a SCTP Basic Connection
SCTP Association ID: Global number of the association.
Module No.: Number of the module to which the association belongs.
SCTP Protocol Type: Type of the protocol above the SCTP. The options include
M3UA, M2UA, SUA, M2PA, IUA, H248, and so on. For the association used
by M3UA, select M3UA.
Opposite-end Office ID: ID of the opposite office of the association.
MSC Server ID: It uniquely identifies a MSC Server.
Coupling Application Property: Select it according to the situation. If one end is

the client side, select the other end as the server side.
Local Port No.: Local port number used for establishing the association.
Opposite-end Port No.: Opposite port number used for establishing the
association.
Incoming/Outgoing Stream Number: Incoming/outgoing stream number of the
73
association. Stream is a unidirectional logical channel in the association. The

data transferred over the same stream is in order.
Maximum Retry Times: The SCTP offers reliable message transfer through the
retransmission mechanism. This configuration item specifies the maximum
retransmission times of the SCTP. If it is exceeded, the system reports the
transmission failure.
Local IP Address: Virtual IP address of the MP. At most four local IP addresses
can be configured.
Opposite-end IP Address: IP address of the opposite end (namely, the

corresponding virtual IP address).
2) Configure a SCTP basic connection.
Set the desired parameters, and then click OK, as shown in Figure 2.9-3.
Figure 2.9-3 Configuring SCTP Basic Connection
Repeat the procedure to add multiple SCTP basic connections.
3) Query the added SCTP basic connection.
After the addition, the configuration records are displayed on the SCTP Basic
74
Chapter 1 Overview
Connection Configuration tab.
2.9.2 Configuring ASPs

1． Open the interface.
In the Sigtran configuration window (see Figure 2.9-1), click the ASP
Configuration tab, as shown in Figure 2.9-4. No record is available.
Figure 2.9-4 ASP Configuration
Application Server Process ID: Global number of the ASP.
SCTP Association ID: It is configured during the SCTP basic connection

configuration. Select it according to the situation.
Self-loop or not: Select whether to implement ASP self-loop or not.
Locked or not: Select whether to lock the ASP or not.
2． Add an ASP.
1） Open the interface for adding an ASP.
On the ASP Configuration tab, click . The Add ASP information
75
Figure 2.9-5 Adding an ASP
2） Configure the ASP.
Repeat the procedure to add multiple ASPs.
Click Cancel or at the upper right corner to cancel the configuration.
3） Query the added ASP.
After the addition, the configuration records are displayed on the ASP
76
Chapter 1 Overview
Figure 2.9-6 Querying Added ASPs
2.9.3 Configuring ASs

In the Sigtran configuration window (see Figure 2.9-1), click the AS

77
Figure 2.9-7 AS Configuration
Application Server No.: Global number of the AS.
Adjacent Office ID: It is configured during the adjacent office onfiguration.

Select it according to the situation.
Routing Context ID: The ID negotiated by two NEs for uniquely identifying an
AS. It can be any value, but it shall be the same at both sides.
Adapting Layer Protocol: The options include M2UA, M3UA, SUA, and IUA.
Usage ID: The options include SGP, IPSP_SERVER, IPSP_CLIENT, and ASP.
Server Mode: The options include OVERRIDE and Load Balancing. Select it
according to the situation.
Load Balancing Mode N/K Value: The load balancing value is N+K. N indicates
that one AS requires at least N ASPs; otherwise the AS cannot run normally.
Application Server Supported User Type/Subsystem: This option is available

after Adapting Layer Protocol is selected.
78
Chapter 1 Overview
Application Server Process ID: It is configured during the ASP configuration.

2． Add an AS.
1） Open the interface for adding an AS.
On the AS Configuration tab, click . The Add AS information interface

appears, as shown in Figure 2.9-8. For the parameters on the interface, see
“Open the interface” in this section.
Figure 2.9-8 Adding an AS
2） Configure the AS.
Repeat the procedure to add multiple ASs.
3） Query the added AS.
79
After the addition, the configuration records are displayed on the AS

Figure 2.9-9 Querying Added ASs
2.9.4 Configuring SIO Positioning ASs

In the Sigtran configuration window (see Figure 2.9-1), click the AS

Configuration of SIO Positioning tab, as shown in Figure 2.9-10. No record is
available.
80
Chapter 1 Overview
Figure 2.9-10 AS Configuration of SIO Positioning
Office ID: It is configured during the adjacent office configuration.
Service Indicator: It identifies the opposite-end user type of the AS. The options
include SCCP, TUP, ISUP, BICC, ALCAP, and H248.
Application Server No.: Global number of the corresponding AS.
2． Add a SIO positioning AS.
1） Open the interface for adding a SIO positioning AS
On the AS Configuration of SIO Positioning tab, click . The Add AS

Configuration of SIO Positioning interface appears. For the parameters on the
interface, see “Open the interface” in this section.
2） Configure the SIO positioning AS.
Repeat the procedure to add multiple SIO positioning ASs.
Figure 2.9-11 shows an example of adding a SIO positioning AS.
81
Figure 2.9-11 Adding a SIO Positioning AS
Click Cancel or at the upper right corner to cancel the configuration.
3） Query the added SIO positioning AS.
After the addition, the configuration records are displayed on the AS

Configuration of SIO Positioning tab.
2.9.5 Verification
Log out from the configuration management subsystem, log in again, and then check
whether the Sigtran masking configuration data is saved in the database or not.
82
3 MSCe Configuration
Key points
· Number analysis configuration
· Topological relation configuration
· SIP configuration
· H.248 configuration
· Trunk management
· Handoff office data configuration
· Mobile office configuration
· Mobile area code configuration
· BSC configuration
· Numbering plan
· Mobile number analysis
· VLR configuration
· KD-KB-ICP table configuration
· Tone resource configuration
· Pulse charge configuration
· OTA configuration
3.1 Overview
This section describes the data categories for the MSCe.
3.2 Main Interface

In the Configuration Management interface, expand the navigation tree to display the
MSCe configuration interface as shown in Figure 3.2-1.
83
Figure 3.2-1 MSCe Configuration Interface
3.3 Number Analysis Configuration

1. Purpose
Number analysis configuration (involving number analysis, mobile number

analysis and GT analysis) is to determine the network addressing and service
processing modes of each number to ensure that the switch can perform
signaling interaction and speech channel connection correctly.
Numbers are the basis of the switch for network addressing. There are two kinds
84
Chapter 3 MSCe Configuration
of numbers in the mobile switch:
Subscriber number: including fixed line subscriber number and mobile

subscriber number.
Network number: including temporary local directory number (TLDN),

MSC/VLR number, HLR number, and so on.
Numbers are analyzed by the analyzers specified by selectors in a fixed

sequence. Among the analyzers, the last one is called as “subsequent number
analyzer” (excluding the null analyzer).
The diagram below shows the analysis sequence of the number analyzers.
Number analysis
Number stream result
New service number analyzer End
Non new service Non new service

CENTREX service number analyzer
Non CENTREX service Non CENTREX service
Private service number analyzer
Non private network Non private network service

service
Special service number analyzer
Non special service Non special service
Local network service number analyzer
Non local network service Non local network service

National toll service number analyzer
Non national toll service Non national toll service

International toll service number
analyzer
Figure 3.3-1 Usage of Seven Number Analyzers
In analysis of any specific number, analyzers need to collaborate with each other.
For example, if the previous analyzer has analyzed and deleted the toll prefix,
the subsequent analyzers do not need to analyze the toll prefix.
The Number Analysis interface includes two forms: digit analysis selector and
analyzer entry. The specific structure is shown in Figure 3.3-2.
85
Number analysis selector: include adding, modifying and deleting selectors
Add analyzer entry
Delete analyzer entry

Number analysis
Analyzed number attribute
Analysis entry Include adding, modifying and deleting analyzed numbers
Analyzed number template operations:

Include adding, modifying and deleting analyzed number in a template
Reloading numbers from a single analyzer, saving template and loading template
Figure 3.3-2 Number Analysis Structure
2. Preparations
Both the O&M server and the O&M client work normally.
The database is connected normally.
The physical configuration has been completed.
The local office configuration has been completed.
3.3.1 Digit Analysis Selector Configuration
1. Interface operations
In the Configuration Management interface, select MSCE configuration Æ

Digit analysis configuration from the navigation tree. The Digit Analysis
Configuration window is displayed on the right side, and the DAS tab page is
displayed by default without any configuration record initially, as shown in
Figure 3.3-3.
86
Figure 3.3-3 Number Analysis Interface (Digit Analysis Selector)
There are at most 99 analyzer entries for a digit analysis selector. Table 3.3-1
lists the values of each analyzer entry.
Table 3.3-1 Values of Analysis Selectors
Analysis Selector Value

New service analyzer entry 1, 5–8192
CENTREX analyzer entry 5–8192
Special service analyzer entry 2, 5–8192
Private network analyzer entry 5–8192
Local network analyzer entry 5–8192
National toll analyzer entry 3, 5–8192
International toll analyzer entry 4, 5–8192
Null 0
If the value of an analyzer entry is 0, the analyzer is not configured and numbers
will not be analyzed by this analyzer.
2. Adding digit analysis selector
1) Enter the interface for adding a digit analysis selector.
87
Click on the DAS tab to display the Add DAS dialog box.
2) Add a digit analysis selector.
In the Add DAS dialog box, select various number analysis entries and then
click OK to add a digit analysis selector.
You can repeat the above steps to add multiple digit analysis selectors.
Figure 3.3-4 shows how to add a digit analysis selector.
Figure 3.3-4 Adding a DAS
You can click Cancel or click the button on the upper right corner to end
this configuration.
3) Querying the new digit analysis selector
After a digit analysis selector is added, select the number of the new digit
analysis selector in the Digit Analysis Select (DAS) area to display the
configuration information on the DAS tab, as shown in Figure 3.3-5.
88
Figure 3.3-5 Querying the Added Digit Analysis Selector
3.3.2 Analyzer Entry Configuration
In the Digit Analysis Configuration window, select the Analysis Entry tab to
switch to the corresponding page where no configuration record is available
initially, as shown in Figure 3.3-6.
89
Figure 3.3-6 Analyzer Entry Configuration
Analysis Entry: can be selected from the drop-down box.
Analyzer Type: refer to Table 3.3-1.
2. Adding an analyzer entry
1) Enter the configuration interface.
Click on the Analysis Entry page. The Create Analysis Entry dialog box
is displayed. For parameters description, refer to “Interface operations” above.
2) Configure the analysis entry information.
In the Create Analysis Entry dialog box, select the configuration data and then
click OK to add an analyzer entry.
You can repeat the above steps to add multiple analyzer entries.
Figure 3.3-7 shows how to add an analyzer entry.
90
Figure 3.3-7 Creating an Analyzer Entry
Due to the addition of virtual MSCes, the number configurations in multiple

analyzers are nearly consistent. Therefore, to create an analyzer, you can copy
the data from the existing analyzer entry and then make simple modifications to
number configurations.
3) Query the added analyzer entry.
After an analyzer entry is created, its configuration records will be displayed on

the Analysis Entry page as shown in Figure 3.3-8.
91
Figure 3.3-8 Querying Configuration of the Added Analyzer Entry
y Note
It is recommended to configure these analyzer entries: 2 special service number

analyzer, 3 national toll number analyzer, 4 international toll number analyzer, 5 local
number analyzer, 6 local number analyzer and 7 local number analyzer.
Usually the No. 5 analyzer is taken as the local call originating analyzer, No. 6 is taken
as the local call terminating analyzer, and No.7 is taken as the local roaming number
analyzer.
All values above are recommended values.
3. Importing the analyzer entry data in batches
On the Analysis Entry page, click to display the Open dialog box as
92
Figure 3.3-9 Opening Files in Batches
Select the files storing analyzer entry configurations, and click Open. Then the
system imports the data from the selected files and prompts whether the data is
imported successfully or not.
y Note:
Be careful to use the importing function! Before importing the data, ensure that the
data is in the specified format. Besides, back up the configuration data first, so that the
data can be restored in case failure of the imported data or the imported numbers are
incorrect.
4. Exporting the analyzer entry data in batches
On the Analysis Entry page, click to display the Save dialog box as
93
Figure 3.3-10 Exporting Analyzer Entry Data in Batches
Select the file storing analyzer entry configurations, and click Open. Then, the
system automatically exports the data to the selected file and prompts whether
the data is exported successfully or not.
If the exported file does not exist, select the exporting directory first, and input
the file name. Then the system will automatically create the specified file and
export the data.
5. Properties of analyzed number
1) Enter the analyzed number properties interface
On the Analysis Entry page, select an analysis entry and click Analyze
Number to display the Digit Analysis Management interface as shown in
Figure 3.3-11.
94
Figure 3.3-11 Analyzing Number
Analyzed Number: including the mobile subscriber number, TLDN, local fixed
line subscriber number, toll fixed line subscriber number and special service
number.
Call Service Type: determined by actual number type
Analysis Finish Mark: four types (the latter three are frequently used):
Analysis finished, do not analyze any more: the most frequently used option,
indicating that the number analysis has completed
Analysis finished, all digits will be analyzed in next analyzer: for flexible
handling when the same digit analysis selector has multiple analysis entries.
For example, if the special service numbers beginning with 1 (such as 110) have
been analyzed in the former analyzer and you want the next analyzer to analyze
the numbers beginning with 2, select this option in the former analyzer. In this
way, the further analysis will be made by the next analyzer. Otherwise, the
numbers beginning with 2 will be discarded.
Analysis finished, remaining digits will be analyzed in next analyzer: for

flexible handling when the same digit analysis selector has multiple analysis
entries.
For example, when the toll numbers contain the prefix 0, select this option in the
previous analyzer if the next analyzer does not analyze the numbers containing
95
the digit 0.
Outgoing route chain: the outgoing route chain used for dialing an outgoing call,
which is configured in Trunk Management
Number transform: conducts number transformation on the calling party side or

the called party side. Number transformation (calling party) is to transform the
analyzed number (can be either the calling number or the called number) on the
calling party side (namely OPCC). Number transformation (called party) is to
transform the analyzed number (can be either the calling number or the called
number) on the called party side (namely TPCC).
Minimum number stream length, Maximum number stream length: any number
whose length is between the maximum and minimum number stream lengths is
an invalid number.
Length of Toll Prefix + Area Code: for example, 0755 is 4 digits long.
Multiple number coexisted: indicating that one analyzed number is contained in

another analyzed number.
Number Address Attribute: including subscriber number, domestic number and

international number
Voice Channel Recovery Mode: including Calling MS controls recovery, Caller

MS controls recovery and Mutually non-controlled recovery. Please query the
SS7 system for details.
Signaling mode selection: including SS7 and associated channel signaling mode.
If Send subscriber number actively when using CSS7 for outgoing call is
selected, the IAI message is sent between offices; otherwise, the IAM message
is sent.
IN Service Implementation Mode: including IN Mode/Intelligent Outgoing and

Intelligent Platform Mode/200
2) Add an analyzed number
Click Add in the Analyzed Number Management interface (in Figure 3.3-11).
The Add analyzed number type dialog box is displayed, as shown in Figure
3.3-12.
96
Figure 3.3-12 Adding an Analyzed Number
Input the related data according to actual conditions, and then click OK to add
an analyzed number. This number will be displayed in the Analyzed Number
list in the Digit Analysis Management interface as shown in Figure 3.3-13.
Figure 3.3-13 Adding an Analyzed Number Succeeded
You can repeat the above steps to add multiple numbers to be analyzed.
97
3.3.3 Examples of Number Analysis Configuration
1. A local mobile subscriber dials a local mobile subscriber
Select the local network analyzer entry and click in Figure 3.3-6. A dialog
box is displayed as shown in Figure 3.3-14.
Figure 3.3-14 Adding a Local Network Analyzed Number
Select 0 in Office ID index, which means handling by the local office. For other
options, refer to the parameter descriptions above.
Input or select the parameters in the above figure and click OK to add an
analyzed number.
To transform the analyzed number, click the button …. A dialog box is

displayed as shown in Figure 3.3-15.
98
Figure 3.3-15 Transforming Number Stream
Select Number Stream Transform Mode and Number Address Attribute, input
Starting Position, Deleted/Modified Digit and Added/Modified Number, and
click OK.
y Note:
For the local mobile calls, it is recommended to configure the key parameters as
follows:
Call service type: MSC normal service
Destination network type: consistent with the network type configured for the selected
office direction
Office ID index: 0
Number address attribute: Domestic number
Analysis finish mark: Analysis finished, do not analyze any more
2. A local mobile subscriber dials a local PSTN subscriber
Select the local network selector and click in Figure 3.3-6. A dialog box is
99
Figure 3.3-16 Adding a Local Network Analyzed Number (Local Call Number)
Input or select the parameters and click OK to add an analyzed number.
y Note:
For the local outgoing calls, it is recommended to configure the key parameters as
follows:
Call service type: Local network outgoing/local
Destination network type: consistent with the network type configured for the selected
office direction
Outgoing route link number: filled according to actual conditions
Number address attribute: Local call number
To send calling number, select Send subscriber number actively when using CSS7
for outgoing call.
3. A local mobile subscriber dials a domestic/international toll number
Select an analyzer entry (such as 3 national toll analyzer entry) and click in
Figure 3.3-6. A dialog box is displayed as shown in Figure 3.3-17.
100
Figure 3.3-17 Adding a Domestic Toll Analyzed Number
y Note:
For the national/international outgoing toll calls, it is recommended to configure the

key parameters as follows:
Call service type: National toll (intraregion/interregion) automatically or international

toll automatically
Destination network type: type of the destination network
Number address attribute: National/international number
To send calling number, select Send subscriber number actively when using CSS7
for outgoing call.
4. Analyze a roaming number
Select an analyzer entry (such as 7 local network analyzer entry) and click
in Figure 3.3-6. A dialog box is displayed as shown in Figure 3.3-18.
101
Figure 3.3-18 Adding a Roaming Analyzed Number
y Note:
For the roaming calls, it is recommended to configure the key parameters as follows:
Call service type: There are two cases. In case there are multiple MSCes in the local
place, the TLDN segment that other local MSCes belong to is analyzed as MSC local
outgoing service, and the TLDN segment of this MSCe is analyzed as MSC local office
service. In case there is only one MSCe in the local place, the TLDN segment that
belongs to this MSC is analyzed as the MSC local office service.
Destination network type: filled according to actual conditions
Number address attribute: Domestic number
3.3.4 SCP/GT Address Index Configuration
The SCP GT data is used for IN subscribers to address the SCP.
In the Digit Analysis Configuration window (in Figure 3.3-3), select the
102
SCP/GT Address Index tab to switch to the corresponding page where no

configuration record is available initially as shown in Figure 3.3-19.
Figure 3.3-19 Configuring SCP/GT Address Index
SCP/GT Address Configuration Index: serial number of the SCP/GT index,

which is added automatically
SCP Address: the GT address of SCP, used for addressing the IN subscribers
within the local office managed by the SCP
Service Key: can be configured the same as that in Service Key Transform
2. Add a SCP/GT address index
1) Enter the interface for adding SCP/GT address indexes
Click on the SCP/GT Address Index page. The Add SCP/GT Address
Index dialog box is displayed. For parameter descriptions, refer to “Interface
operations” above.
2) Configure the SCP/GT address index
In the Add SCP/GT Address Index dialog box, input the configuration data and
click OK to add a SCP/GT address index.
103
You can repeat the above steps to add multiple SCP/GT address indexes.
this configuration.
3) Query the added SCP/GT address index
After a SCP/GT address index is added, its configuration records will be

displayed on the SCP/GT Address Index page as shown in Figure 3.3-20.
Figure 3.3-20 Querying Added SCP/GT Address Index
3.3.5 Number Transform/Display Selector
In the Digit Analysis Configuration window (in Figure 3.3-3), select Number
Transform/Display Selector tab to switch the corresponding page where no
configuration record is available initially, as shown in Figure 3.3-21.
104
Figure 3.3-21 Number Transform/Display Selector
Number stream transform mode: including six modes: add, delete, modify,
replace all, and so on.
Selector type: including ten types such as MAP calling number transform
selector, display number transform selector, trunk calling number incoming
transform selector, SIP calling number incoming transform selector, and so on.
Starting position: indicating which digit numbers are added, modified or deleted
in the number stream.
Added/modified digit: 5-digit number at most
2. Add a number transform/display selector
1) Enter the interface for adding number transform/display selectors
Click on the Number Transform/Display Selector page to display the

Add number transform/display selector dialog box. For parameter
descriptions, refer to “Interface Operations” above.
2) Configure a number transform/display selector
In the Add number transform/display selector dialog box, input the
105
configuration data and click OK to add a number transform/display selector.
You can repeat the above steps to add multiple number transform/display
selectors.
Figure 3.3-22 shows how to add a number transform/display selector.
Figure 3.3-22 Adding a Number Transform/Display Selector
3) Query the added number transform/display selector
After a number transform/display selector is added, its configuration records will

be displayed on the Number Transform/Display Selector page, as shown in
Figure 3.3-23.
106
Figure 3.3-23 Querying the Added Number Transform/Display Selector
3.3.6 Number Transform/Display
In the Digit Analysis Configuration window (in Figure 3.3-3), select Number
Transform/Display tab to switch to the corresponding page where no
107
Figure 3.3-24 Number Transform/Display
Number selector: available only when the number transform/display selector has
been configured
The selector uses default ddi: if this option is selected, the settings of the selector
are consistent with those of the number selector in the number transform/display
selector configuration.
2. Adding number transform/display
1) Enter the interface for adding number transform/display
Click on the Number Transform/Display page to display the Add

number transform/display number dialog box. You can refer to “Interface
operations” for parameter descriptions.
2) Configure number transform/display
In the Add number transform/display number dialog box, input the

configuration data and click OK to add a number transform/display
configuration.
You can repeat the above steps to add multiple number transform/display
108
configurations.
Figure 3.3-25 shows an example of how to add number transform/display.
Figure 3.3-25 Add a Number Transform/Display
this configuration.
3) Query the added number transform/display
After number transform/display is added, its configuration records will be

displayed on the Number Transform/Display page, as shown in Figure 3.3-26.
109
Figure 3.3-26 Querying the Added Number Transform/Display
3.3.7 Result Verification
Exit the configuration management subsystem first, and then log in again to query
whether the number analysis configuration data is saved in the database or not.
3.4 Topological Relation Configuration

1. Purpose
Configure the inter-office topological relation, inter-office SIP related data and
encoding/decoding data, including the coding/decoding type configuration,
equipment node configuration, BSC-to-MGW configuration and so on.
2. Preparations
The SS7 data configuration has been completed.
110
3.4.1 Coding/Decoding Type Configuration

Topological relation configuration from the navigation tree. The Topological
Relation Configuration window is displayed on the right side, and the
Coding/Decoding Type Configuration tab is displayed by default without any
configuration record initially, as shown in Figure 3.4-1.
Figure 3.4-1 Coding/Decoding Type Configuration
Coding/Decoding ID: the global ID for coding/decoding
Code type: see Figure 3.4-2
2. Adding a coding/decoding type
1) Enter the interface for adding coding/decoding types
Click on the Coding/Decoding Type Configuration page. The Add

coding/decoding type dialog box is displayed. For parameter descriptions, refer
to “Interface operations” above.
2) Configure the voice coding/decoding type
111
In the Add coding/decoding type dialog box, input the Coding/Decoding ID

and select one or multiple coding/decoding types (by pressing and hold the
SHIFT key) in the Code Type to be selected list and then click OK to add a
voice coding/decoding type.
You can repeat the above steps to add multiple voice coding/decoding types.
Figure 3.4-2 shows how to add a voice coding/decoding type.
Figure 3.4-2 Adding a Coding/Decoding Type
this configuration.
3) Query the added coding/decoding type
After a voice coding/decoding type is added, its configuration record is

displayed on the Coding/Decoding Type Configuration page as shown in
Figure 3.4-3.
112
Figure 3.4-3 Querying the Added Coding/Decoding Type
3.4.2 Device Node Configuration
In the Topological Relation Configuration window (in Figure 3.4-1), select the
Device Node Configuration tab to switch to the corresponding page where no
113
Figure 3.4-4 Device Node Configuration
Device type: including MGW, MSCe, BSC, etc. select any according to actual
requirements.
Protocol type: including five types: BICC, H248, SIP, H323 and MGCP
Code ID: configured in Coding/Decoding Type Configuration
Tag 1: five modes including URI adopts number domain mode. URI adopts
number IP mode is usually adopted.
DIGITMAP module ID: configured in DIGITMAP Module Configuration
Tag 2: which items are optional depends upon device types.
Auxiliary protocol property: is available only when the Protocol Type is set to
SIP.
Carrier property: support RTF bearer or TDM bearer
2. Adding a device node
1) Enter the interface for adding device nodes
Click on the Device Node Configuration page. The Add device node
dialog box is displayed. For parameter descriptions, refer to “Interface
2) Configure device node information
In the Add device node dialog box, input the configuration data and click OK
to add a device node. Figure 3.4-5 shows how to add a device node.
114
Figure 3.4-5 Adding a Device Node
You can repeat the above steps to add multiple device nodes.
this configuration.
3) Query the added device node
After a device node is added, its configuration record will be displayed on the
Device Node Configuration page as shown in Figure 3.4-6.
115
Figure 3.4-6 Querying the Added Device Node
3.4.3 BSC-MGW Relationship Configuration
BSC-MGW Relationship Configuration tab to switch to the corresponding
page where no configuration record is available initially, as shown in Figure
3.4-7.
116
Figure 3.4-7 BSC-MGW Relationship Configuration
BSC node ID: can be selected only when the BSC node ID is configured in
Device Node Configuration
MGW node ID: can be selected only when the MGW node ID is configured in
Device Node Configuration. You can select these parameters according to
actual requirements.
2. Adding a BSC-MGW relationship
1) Enter the interface for adding BSC-MGW relationships
Click on the BSC-MGW Relationship Configuration page. The Add

bsc-mgw relationship dialog box is displayed. For parameter descriptions, refer
2) Add a BSC-MGW relationship
In the Add bsc-mgw relationship dialog box, input the configuration data and
click OK to add a BSC-MGW relationship. Figure 3.4-8 shows how to add a
BSC-MGW relationship.
117
Figure 3.4-8 Adding a BSC-MGW Relationship
You can repeat the above steps to add multiple BSC-MGW relationships.
this configuration.
3) Query the added BSC-MGW relationship
After a BSC-MGW relation is added, its configuration record will be displayed

on the BSC-MGW Relationship Configuration page as shown in Figure 3.4-9.
Figure 3.4-9 Querying the Added BSC-MGW Relationship
118
3.4.4 SIP Transfer Protocol Configuration
SIP Transfer Protocol Configuration tab to switch to the corresponding page
where no configuration record is available initially, as shown in Figure 3.4-10.
Figure 3.4-10 TCP Connection Configuration
IP link: the No. that uniquely identifies a TCP/IP link
Opposite-end office ID: the No. of the opposite end office that establishes a TCP
connection with the local office
Local IP/Opposite-end IP: configured on the interface where the IP protocol

stack is configured. This address is the address of the SIGIPI board connecting
both ends.
Local port: if the opposite end is set to originate a TCP connection in TCP
Connection Type, the local port number must be 5060.
Opposite-end port: if the local end is set to originate a TCP connection in TCP
Connection Type, the opposite-end port number must be 5060.
119
Module managing this link: the No. of the module that manages the link
Application transfer protocol: TCP or UDP
TCP connection type: local end originating TCP connection or opposite end
originating TCP connection. You can select either according to actual
requirements.
Link detection timer: the interval of link detection
2. Adding a TCP connection
1) Enter the interface for adding TCP connections
Click on the SIP Transfer Protocol Configuration page. The Add SIP
transfer protocol configuration dialog box is displayed. For parameter
descriptions, refer to “Interface operations” above.
2) Add a TCP connection
In the Add SIP transfer protocol configuration dialog box, input the
configuration data and click OK to add a TCP connection. Figure 3.4-11 shows
how to add a TCP connection.
120
Figure 3.4-11 Adding a TCP Connection
You can repeat the above steps to add multiple TCP connections.
this configuration.
3) Query the added TCP connection
After a TCP connection is added, its configuration record will be displayed on

the SIP Transfer Protocol Configuration page as shown in Figure 3.4-12.
121
Figure 3.4-12 Querying the Added TCP Connection
3.4.5 DIGITMAP Module Configuration
To implement the R2 function, you need to configure the DIGITMAP module.
DIGITMAP Module Configuration tab to switch to the corresponding page
where no configuration record is available initially, as shown in Figure 3.4-13.
122
Figure 3.4-13 DIGITMAP Module Configuration
DIGITMAP module ID: the No. that uniquely identifies the DIGITMAP module,
ranging from 1 to 127
DIGITMAP string: usually the quantity of DIGITMAP strings is exactly the

quantity of numbers. One “x” is used to indicate one digit in a number. For
example, if the number is 13312349994, fill in “(xxxxxxxxxxx)” in this option.
Up to 255 characters can be input.
Start timer: the timer from the beginning of number transfer to the successful
transfer of the first digit. The default value is 20.
Short timer: the minimum transfer time between digits. If the time is later than
this time, the transfer ends. The default value is 8.
Long timer: the maximum for transferring a number
2. Adding a DIGITMAP module
1) Enter the interface for adding DIGITMAP modules
2) Click on the DIGITMAP Module Configuration page. The Add

DIGITMAP module configuration dialog box is displayed. For parameter
123
3) Add a DIGITMAP module
In the Add DIGITMAP module configuration dialog box, input the

configuration data and click OK to add a DIGITMAP module. Figure 3.4-11
shows how to add a DIGITMAP module.
Figure 3.4-14 Adding a DIGITMAP Module
You can repeat the above steps to add multiple DIGITMAP modules.
this configuration.
4) Query the added DIGITMAP module
After a DIGITMAP module is added, its configuration record will be displayed

on the DIGITMAP Module Configuration page as shown in Figure 3.4-15.
124
Figure 3.4-15 Querying the Added DIGITMAP Module
3.4.6 Encoding Name Configuration
It covers the eight formats for coding/decoding negotiation.
Encoding Name Configuration tab to switch to the corresponding page where
no configuration record is available initially, as shown in Figure 3.4-16.
125
Figure 3.4-16 Encoding Name Configuration
y Note:
This interface is automatically generated after the system is installed. Do not change
the configurations arbitrarily.
whether the topological relation configuration data is saved in the database or not.
3.5 Trunk Management

1. Purpose
In the ZXC10 MSCe system, all outgoing routes of a destination code are
identified by outgoing route links. And each outgoing route link includes 4
outgoing route sets. Each route set consists of multiple routes. Each route
corresponds to a trunk group. Each trunk group can belong to different routes,
enabling independent routing for trunk circuit groups. Route trunk groups in the
same route set share traffic loads. The relations among the route links, route sets,
126
routes and trunk groups are shown in the diagram below.
Route Trunk
chain group
1:m 1:k
Route 1:n
route
set
Figure 3.5-1 Relationship Among Route Link, Route set, Route and Trunk Group
2. Preparations
The number analysis configuration has been completed.
The device node ID has been configured in Topological Relation

Configuration.
3.5.1 Trunk Group Configuration
A trunk circuit group, trunk group for short, is a collection of the circuits with identical
properties (channel transmission, inter-office circuit selection) between a switching
module and an adjacent exchange.
The management of trunk groups complies with the following rules.
A trunk group is restricted to be within a switching module.
Up to 250 trunk groups inside a switching module are numbered in a unified manner.
The trunk groups inside different switching modules are numbered independently.
The above rules, in combination with route data, guarantee easy and flexible
127
management of trunk circuits and implement unified load sharing.

Trunk management configuration from the navigation tree. By default, the
Trunk Management Configuration tab page is displayed on the right side
without any configuration record initially, as shown in Figure 3.5-12.
Figure 3.5-2 Trunk Group Configuration
1) Basic attributes
On the Trunk Group page, select the Basic Attributes tab to display the basic
attributes of the trunk group, as shown in Figure 3.5-12.
The meanings of parameters are listed below.
Group kind: including incoming group, outgoing group and both-way group.
Channel type: totally 14 types such as digital channel and analog channel
Line signaling: totally 43 types such as inter-office common and associated

channel signaling
128
Circuit ID: including trunk circuit, A-interface circuit, and changeover circuit
Office ID: the ID of the adjacent office that has been added in Switch Office
Configuration
MGW node ID: the device node No. added in Topological Relation
Configuration
Incoming DAS: specify how the TUP or ISUP handles incoming numbers. The
digit analysis selector that is configured in Digit Analysis should be selected.
OP incoming DAS or OP outgoing DAS: available only when the trunk OP

incoming/outgoing DAS is selected in Digit Transform/Display Selector
TP incoming DAS or TP outgoing DAS: available only when the trunk TP

incoming/outgoing DAS is selected in Digit Transform/Display Selector
Outgoing (Incoming) addressing signaling: including MFC, MFP, DTMF, DP

and MF
Trunk group name: description of a trunk group
Trunk routing type: totally seven types: from odd to even, from most idle, from
big to small, first in first out, cyclic selection, from even to odd, from most busy,
and from small to big
2) Indicators
On the Trunk Group page, select the Indicators tab to display the indicators
used by the trunk group on the Indicators page, as shown in Figure 3.5-3.
129
Figure 3.5-3 Trunk Group Configuration (Indicators Page)
There are 63 kinds of indicators used by trunk groups, as listed in Table 3.5-1.
Table 3.5-1 Indicators
Serial No. Classification:

1 (Incoming) play secondary dial tone DT2
2 Trunk charging (for inter-office trunk settlement)
3 (Incoming) calling numbers available
4 Echo suppressor included
5 In test, select the digit analysis selector for test
6 Satellite circuit included
7 (Incoming) OPR trunk
8 (Malicious call) incoming A6 signal followed by KA signal
9 Continuity test included
(Incoming) send busy signal to caller from the line when the called is
10
busy
11 (Incoming) Send idle signal to caller
12 (Incoming) send ring back tone to caller from the line
(Incoming) play re-ringing signal to the called party through receiving
13
line
14 (Incoming) send initial number for verification upon incoming office
15 (Incoming) send line busy signal at insertion of a call
130

16 (Outgoing) ringing signal sent to the calling party over receiving line
17 (Outgoing) send re-ringing signal to the called from the line
(Outgoing) receive first digit of number to acknowledge (to determine
18
whether to stop the dial tone)
(Outgoing) send ring back tone to caller on behalf of downstream office
19
when the called is idle
(Outgoing) Downstream office sends dial tone after seizure is
20
acknowledged
21 Receive called offhook signal
22 (Outgoing) send called onhook signal to the calling party
23 (Incoming) register is busy at call insertion
24 (Incoming) the opposite office is a semiautomatic console (KD=1)
25 Receive called line busy or reached signal (A3)
26 (Outgoing) the outgoing trunk is to connect the voice platform
27 (Outgoing) the outgoing trunk is to connect the voice mailbox
(Incoming) calls can be connected when there is no calling number at
28
incoming office
29 (Incoming) send request code
30 Analog trunk (bearer trunk)is going to send seizure verification code
31 (Incoming) user group traffic console on calls
32 Restrict maximum call duration
33 Toll call originating office + area code
34 TUP not support full-digit channel
35 TUP not include calling number in GSM message
36 TUP includes incomplete calling number in GSM message
37 Calling side is CAS, called side is No.7, caller ID display restricted
38 Important user using the trunk
39 TUP originates UNN while playing vacant number tone
40 TUP not request calling number immediately upon receiving of IAM
41 Incoming announcement is allowed in call failure
42 Always not request calling information GRQ request at incoming IAI
43 Busy tone detection required for associated channel trunk
44 Is incoming trunk black list
45 Is incoming trunk white list
46 Is monitoring trunk group
47 (Incoming) support IN service triggering
48 Add
49 IDA-M signaling sending/receiving caller number
50 (Incoming) judge equal access
131

51 (Incoming) change calling number attribute based on length
52 (Incoming) incoming calls restricted by calling number
53 ISUP message parameters simplified
54 (Outgoing) original called number not included
55 Is MGW trunk
56 Generate transit bill
57 Play announcement at incoming call failure
58 Send original number at CAS incoming call forwarding
59 Is toll trunk
60 (Incoming) add prefix before called number
61 (Outgoing) called number + country code
62 (Incoming) delete local country code and prefix from called number
63 Send metering pulse
Indicators can be configured according to the specific conditions of the opposite

office. For example, if the opposite office is a wired office, you can select
indicator 4 (include echo suppressor) (DTEC board should be physically
configured) to cancel the echo arising from line 2 and 4 transform.
3) Trunk group attributes
In the Trunk Group page, select Trunk Group Attributes tab to display the
attributes of the trunk group in the Trunk Group Attributes page, as shown in
Figure 3.5-4.
132
Figure 3.5-4 Trunk Circuit Group (Trunk Group Attributes Page)
There are eight kinds of trunk group attributes, as listed in Table 3.5-2.
Table 3.5-2 Trunk Group Attributes
Serial No. Classification

1 CDMA13K voice
2 CDMAEVRC voice
3 CDMA asynchronous data rate set 1
4 CDMA asynchronous data rate set 2
5 CDMAG3 fax rate set 1
6 CDMAG3 fax rate set 2
7 CDMA short message rate set 1
8 CDMA short message rate set 2
The trunk group attributes can be configured according to the specific conditions
of the opposite office only after the Circuit ID is set to Switching Circuit in the
Basic Attributes page.
2. Adding a trunk group
1) Enter the interface for adding trunk groups
133
Click in the Trunk Group page. The Add trunk group dialog box is
displayed. For parameter descriptions, refer to “Interface operations” above.
2) Add a trunk group
In the Add trunk group dialog box, select the module No. for a trunk group,
and configure the parameters in the Basic Attributes, Indicators and Trunk
Group Attributes pages respectively. After setting all parameters, click OK to
add a trunk group. Figure 3.5-5 shows how to add a trunk group.
Figure 3.5-5 Adding a Trunk Group
134
You can repeat the above steps to add multiple trunk groups.
You can click Cancel or click the button in the upper right corner to end
this configuration.
3) Query the added trunk group.
After a trunk group is added, its configuration record will be displayed in the
Trunk Group page.
3.5.2 PCM Configuration
You can configure the PCM after the trunk group is configured.
In the Trunk Management Configuration window (in Figure 3.5-2), select the
PCM Configuration tab to switch to the corresponding page. By default there
is no configuration record initially, as shown in Figure 3.5-6.
Figure 3.5-6 Trunk Circuit Allocation
Trunk group: configured in Trunk Group page. Once the trunk group No. is set,
Office ID and MGW Node ID will adopt default values.
135
PCM: It must be the corresponding PCM number of the BSC or PSTN. In

addition, the PCMs to the same office should not be identical.
MGW PCM: It must be the corresponding E1 No. on the MGW. In addition, the
PCMs of the same MGW should not be identical.
Add PCM in batch: after this option is selected, you only need to input the PCM
start/end No. and MGW start/end No. and the system will generate the PCM
configuration by default.
Allocate CIC by default: after this option is selected, the system will allocate
CIC by default; otherwise, you need to add CIC manually.
2. Adding a PCM
1) Enter the interface for adding PCMs.
Click in the PCM Configuration page. The Add PSM Configuration

2) Add a PCM.
In the Add PSM Configuration dialog box, input the configuration data and
click OK to add a PCM. Figure 3.5-7 shows how to add a PCM.
Figure 3.5-7 Adding a PCM
You can repeat the above steps to add multiple PCMs.
136
this configuration.
3) Query the added PCM.
After a PCM is added, its configuration record will be displayed in the PCM
Configuration page.
3.5.3 Outgoing Route
Outgoing Route tab to switch to the corresponding page. By default, there is no
Figure 3.5-8 Outgoing Route Configuration
Outpulsing method: used for associated channel signaling
Trunk group: configured in the Trunk Group page
2. Adding an outgoing route
1) Enter the interface for adding outgoing routes.
137
Click in the Outgoing Route page. The Add outgoing route dialog box
is displayed. For parameter descriptions, refer to “Interface operations” above.
2) Add an outgoing route.
In the Add outgoing route dialog box, input the configuration data and click
OK to add an outgoing route. Figure 3.5-9 shows how to add an outgoing route.
Figure 3.5-9 Adding an Outgoing Route
You can repeat the above steps to add multiple outgoing routes.
this configuration.
3) Query the added outgoing route.
After an outgoing route is added, its configuration record will be displayed in

the Outgoing Route page.
3.5.4 Outgoing Route Set
As stated in “Purpose”, an outgoing route set is a collection of the routes of one level.
One route set consists of at least one and at most 12 routes of the same level.
138
There is a sequence between routes. Besides, route numbers can be repeatedly used to
balance traffic.
Outgoing Route Set tab to switch to the corresponding page. There is no
Figure 3.5-10 Outgoing Route Set
In the Outgoing Route Set page, you can select the route set No. to query its
route members.
2. Adding an outgoing route set
1) Enter the interface for adding outgoing route sets.
Click in the Outgoing Route Set page. The Add outgoing route set
dialog box is displayed.
2) Add an outgoing route set.
In the Add outgoing route set dialog box, input the configuration data and click
139
OK to add an outgoing route set. Figure 3.5-11 shows how to add an outgoing
route set.
Figure 3.5-11 Adding an Outgoing Route Set
You can repeat the above steps to add multiple outgoing route sets.
this configuration.
3) Query the added outgoing route set.
After an outgoing route set is added, its configuration record will be displayed in
the Outgoing Route Set page.
3.5.5 Outgoing Route Chain
The management of route chains complies with the rules below.
One outgoing route chain consists of at least one and at most 12 outgoing route sets.
There is a sequence between route sets. Besides, route sets can be repeatedly
numbered.
If the previous route set is not selected, all the route sets followed are not selected.
140
Outgoing Route Chain tab to switch to the corresponding page. There is no
Figure 3.5-12 Outgoing Route Chain Configuration (Chain Components Page)
Chain: the number uniquely identifying an outgoing route chain
Circuit type: it must be consistent with that configured in Trunk Group
1) Chain components
In the Outgoing Route Chain page (in Figure 3.5-12), select the Chain
Components tab to display the components of an outgoing route chain in the
Route Components page, as shown in Figure 3.5-12.
2) Dynamic chain for outgoing
In the Outgoing Route Chain page (in Figure 3.5-12), select the Dynamic
Chain for Outgoing tab to display the Dynamic Chain for Outgoing page, as
141
Figure 3.5-13 Outgoing Route Chain Configuration (Dynamic Chain for Outgoing Page)
On weekly basis, an outgoing route chain routes at most three times at most
based on three time zones every day. That is, a route chain varies by time.
The three time zones are classified in this way:
(00:00, time1) – from 00:00 of the very day to time1, the first time zone. A
change route chain No. is selected.
(time1, time2)– from time1 of the very day to time2, the second time zone. A
(time2, 23:59) – from time2 of the very day to 23:59, the third time zone. A
Among them, hour ranges from 0 to 23, and minute ranges from 0 to 59. Time1
is the first time of the very day, and time2 is the second time.
2. Adding an outgoing route chain
To add or modify the Dynamic Chain for Outgoing, select whether to activate
the time change flag and then select or modify the time zones and change route
chain No. according to actual requirements.
142
3.5.6 Inner-office MGW Topological Relation Configuration
Inner-office MGW Topological Relation Configuration tab to switch to the
corresponding page. There is no configuration record initially, as shown in
Figure 3.5-14.
Figure 3.5-14 Inner-Office MGW Topological Relation Configuration
Node 1/Node 2: configured in Device Node Configuration
Carrier link type: including two types: TDM and IP
Matched trunk groups: automatically generated after the Node 1, Node 2 and
Carrier Link Type are configured
In the Inner-office MGW Topological Relation Configuration page (in Figure

3.5-14), you can select one record to query the matched trunk groups.
2. Adding a MGW topological relation
1) Enter the interface for adding intra-office MGW topological relations.
143
Click in the Inner-office MGW Topological Relation Configuration

page. The Add Inner-office MGW Topological Relation Configuration dialog
box is displayed. For parameter descriptions, refer to “Interface operations”
above.
2) Add a MGW topological relation
In the Add Inner-office MGW Topological Relation Configuration dialog

box, input the configuration data and then click OK to add a MGW topological
relation. Figure 3.5-15 shows how to add a MGW topological relation.
Figure 3.5-15 Adding a MGW Topological Relation
You can repeat the above steps to add multiple MGW topological relations.
this configuration.
3) Query the added MGW topological relation.
After a MGW topological relation is added, its configuration record will be
144
displayed in the Inner-office MGW Topological Relation Configuration page

Figure 3.5-16 Querying the Added MGW Topological Relation
3.5.7 Virtual CIC Configuration
The virtual CIC is used for switching over IP between 3G MSCes.
Virtual CIC Configuration tab to switch to the corresponding page. There is
no configuration record initially, as shown in Figure 3.5-17.
145
Figure 3.5-17 Virtual CIC Configuration
Office ID: the ID of the handoff office
CIC No.: the unified number of a circuit in the office
Trunk group: the trunk group No. of the circuit with the Circuit Type being
Handoff Office in Trunk Group page
CIC start ID: the start No. of CIC
CIC number: the quantity of the CICs to be added
2. Adding a virtual CIC
1) Enter the interface for adding virtual CICs
Click in the Virtual CIC Configuration page. The Add Virtual CIC
Configuration dialog box is displayed.
2) Add a virtual CIC.
In the Add Virtual CIC Configuration dialog box, input the configuration data
and click OK to add a virtual CIC. Figure 3.5-18 shows how to add a virtual
CIC.
146
Figure 3.5-18 Adding a Virtual CIC
You can repeat the above steps to add multiple virtual CICs.
this configuration.
3) Query the added virtual CIC
After a virtual CIC is added, its configuration record will be displayed in the
Virtual CIC Configuration page as shown in Figure 3.5-19.
147
Figure 3.5-19 Querying the Added Virtual CIC
whether the trunk management configuration data is saved in the database or not.
3.6 Handoff Office Configuration

1. Purpose
Establish a correspondence relation for the trunk groups between the adjacent
handoff office and the local office, to enable mobile phones for hand over
between the local office and the adjacent handoff office.
2. Preparations
The foreground and background can communicate normally.
The adjacent office has been configured.
The outgoing route chain has been configured.
In the Configuration Management interface, select MSCE configuration >

Handoff office configuration from the navigation tree. By default, the Handoff
Office Configuration tab page is displayed on the right side without any
148
Figure 3.6-1 Handoff Office Configuration
Handoff office ID: the office direction No. of the handoff office
Switching circuit route link: the route ID of the switching circuit, which is
configured in Outgoing Route Chain
System ID: the system ID of the opposite handoff office
Exchange number: the switch No. of the opposite handoff office
MSC number: the MSCIN No. of the opposite office, which is used for
addressing in GT mode
Connection mode: 1: direct connection, 0: virtual connection
Addressing mode: 0: addressing in SPC mode, 1: addressing in GT mode
4. Adding a handoff office
1) Enter the interface for adding handoff offices.
The Handoff Office Configuration interface is shown in Figure 3.6-1. For

parameter descriptions, refer to “Interface operations” above.
2) Add a handoff office.
149
Click , input the parameters and click OK to complete the addition.
You can repeat the above steps to add multiple handoff offices.
this configuration.
3) Query the added handoff office.
After a handoff office is added, its configuration record will be displayed in the
Handoff Office Configuration page as shown in Figure 3.6-2.
Figure 3.6-2 Querying the Added Handoff Office
3.7 Mobile Office Configuration

1. Purpose
A mobile subscriber can roam over the entire CDMA network. Therefore, the
MSCe office of the mobile subscriber can implement mobile communication
only when it is connected with other offices in the network.
2. Preparations
150
The BSC configuration has been configured.
3.7.1 Mobile Office Capacity
An overall planning is required to determine the capacity of the office before

deployment.
The mobile office capacity configuration is to define the capacities of the MSCe in the
local office.
Once this option is determined, no addition, modification or deletion is required.

Mobile office configuration from the navigation tree. By default, the Mobile
Office Configuration tab page is displayed on the right side without any
151
Figure 3.7-1 Mobile Office Capacity Planning
The parameters in this page specify the maximum configurable quantity of each
module. You just need to input the module No. to be added and select the
module reference type to define the capacity of the module.
2. Selecting default settings
In the Mobile Office Capacity page, click Default Setting and the system will
add the recommended value of the module.
Click Modify. The office capacity is added successfully.
3.7.2 Mobile Data Configuration
In the Mobile Office Configuration window, select the Mobile Data

Configuration tab to switch to the corresponding page. There is no
152
Figure 3.7-2 Mobile Data Configuration
MSC number and VLR number: input according to actual conditions to shield
some GT attributes
Cluster control routing: used at outgoing to balance the outgoing traffic of each
module in multi-module office. This option is usually selected in multi-module
networking.
This office type: selected according to actual conditions. Multiple choices are
allowed.
Country code: for example, the country code of China is 86
Mobile service access number: 13x, for example, China Unicom’s CDMA
network uses 133 at present
Mobile country code: for example, the mobile country code of China is 460
Mobile network code: contains at most two digits
The roaming prompt access number, failed call prompt access number and SMC
cooperate to provide the roaming prompt and failed call VAS. They are
configured according to actual conditions.
153
Besides, the subscriber number length, international toll prefix, PPC prefix and
operator can be selected according to actual conditions.
2. Configuring mobile country code
Click in the Mobile Data Configuration page. The Mobile Country

Code Configuration dialog box is displayed without any configuration record
initially as shown in Figure 3.7-3.
Figure 3.7-3 Mobile Country Code Configuration
The Mobile Country Code Configuration is used to configure the

correspondence between the mobile country code and the country code,
preparing for international roaming. The supplementary service ID specifies the
GT for the supplementary service is transferred as the MDN number (0) or as
the IMSI number (1).
1) Add a mobile country code.
Click Add in the Mobile Country Code Configuration dialog box. The Add
mobile country code dialog box is displayed. Input the configuration data and
click OK to add a mobile country code. Figure 3.7-4 shows how to add a mobile
country code.
154
Figure 3.7-4 Adding a Mobile Country Code
You can repeat the above steps to add multiple mobile country codes.
this configuration.
After a mobile country code is added, return to the Mobile Country Code
Configuration dialog box, and you can find the added record.
2) Delete a mobile country code.
In the Mobile Country Code Configuration dialog box, select the

configuration record to be deleted and click Delete to delete a mobile country
code.
3. Adding a mobile number prefix
The mobile number prefix is the characteristic of the mobile number. This prefix
is very important. Please configure it correctly.
Click in the Mobile Data Configuration. The Mobile Number Prefix

Information window is displayed. There is one configuration record initially, as
155
Figure 3.7-5 Mobile Number Prefix
1) Add a mobile number prefix.
Click Add in the Mobile Number Prefix Information window. The Add
mobile number prefix window is displayed as shown in Figure 3.7-6.
Figure 3.7-6 Adding a Mobile Number Prefix
Click OK to input a mobile number prefix. A prompt is displayed as shown in

Figure 3.7-7.
156
Figure 3.7-7 Prompt for Adding a Mobile Number Prefix
Click OK to complete the addition. The added mobile number prefix is

displayed in the Mobile Number Prefix Information window.
4. Adding a SMC number
Click in the Mobile Data Configuration. The SMC Number

Configuration interface is displayed without any configuration record initially,
Figure 3.7-8 SMC Number Configuration
1) Add a SMC number.
Click Add in the SMC Number Configuration interface. The Add SMC
number is displayed. Input the configuration data and click OK to add a SMC
157
number. Figure 3.7-9 shows how to add a SMC number.
Figure 3.7-9 Adding a SMC Number
You can repeat the above steps to add multiple SMC numbers.
this configuration.
After a SMC number is added, return to the SMC Number Configuration

interface, and you can find the added record.
2) Delete a SMC number.
In the SMC Number Configuration interface, select the SMC number to be

deleted and click Delete.
3.7.3 MSC ID Configuration
In the Mobile Office Configuration window (in Figure 3.5-2), select the MSC
ID Configuration tab to switch to the corresponding page. There is no
158
Figure 3.7-10 MSC ID Configuration
MSC ID: generated by default, unchangeable
System ID: set according to actual conditions
TLDN prefix: 10 digits prefix of the TLDN, allocated to the subscriber in an

inter-office call. Still three digits are left and ranges from 000 to 999, which can
be acquired randomly.
2. Adding a MSC ID
Click in the MSC ID Configuration page. The Add MSCID dialog box
is displayed. For parameter descriptions, refer to “Interface operations” above.
Input the configuration data and click OK to add a MSC ID. Figure 3.7-11
shows how to add a MSC ID.
159
Figure 3.7-11 Adding a MSC ID
You can repeat the above steps to add multiple MSC IDs.
Click Cancel or in the upper right corner to end this configuration. Return
to the MSC ID Configuration page, and you can find the added record.
3.7.4 VMSC Configuration
As a complete object, the physical configuration and resource management of MSC are
performed uniformly on a platform. The virtual MSC means to manage the related
attributes of a city (such as the toll area number, toll area ID, etc) according to the
physical locations of the switch, thus it seems that a virtual MSC serves the users in
each city.
In the Mobile Office Configuration window, select the VMSC Configuration

tab to switch to the corresponding page. There is no configuration record
160
Figure 3.7-12 VMSC Configuration
Virtual MSC ID: the virtual MSC flag, ranging from 1 to 16
Toll area code: the code of the toll area of the corresponding city of the virtual
MSC
Toll area ID: the ID of the corresponding city of the virtual MSC
Each virtual MSC requires digit analysis selector. That is, the corresponding
virtual MSC digit analysis selector of each city should be configured according
to the actual conditions.
The digit analysis selectors restrict how to handle when the switch receives the
calling numbers from users or from other switches. If Number Analysis is not
configured, these options cannot be selected temporarily until the Number
Analysis is configured. Here:
DAS1 (MS originating) means how to determine the call type and how to handle
when the switch receives a call from the MS. If the called party is a mobile
subscriber, MSC needs to query the route information to the corresponding HLR.
If the called party is a wired subscriber, the MSC needs to connect the call to the
corresponding local office or toll office based on the local call or toll call.
161
DAS2 (roaming number) means how to handle when the switch receives the
roaming number provided by the HLR. When the MSC receives the roaming
numbers from HLR, this DAS will judge whether the number is a local mobile
service or an outgoing mobile service. If it is a local service, send it to the
corresponding module for handling. If it is an outgoing service, select the
corresponding route chain for call connection.
DAS3 (special subscriber) means to analyze numbers for special subscribers

(such as military network subscribers).
DAS4 (IP analysis) means to analyze the numbers dialed through IP service.
DAS8 (MAP calling MS DAS) needs to be configured only when the switch
supports special Overlay CAMEL service.
2. Adding a VMSC
Click in the VMSC Configuration page. The Add VMSC dialog box is
Input the MSC ID, toll area code and toll area ID, select the corresponding DAS,
and then click OK to add a VMSC. The diagram below shows how to add a
VMSC.
162
Figure 3.7-13 Adding a Virtual MSC
You can repeat the above steps to add multiple virtual MSCs.
Click Cancel or in the upper right corner to end this configuration. Return
to the VMSC Configuration page, and you can find the added configuration
record.
3.7.5 CDMA Data Configuration
In the Mobile Office Configuration window, select the CDMA Data

Configuration tab to switch to the corresponding page as shown in Figure
3.7-14.
163
Figure 3.7-14 CDMA Data Configuration
Network ID (NID): consisting of 16 bytes. 0 and 65535 of the NID are reserved.
0 represents the base stations in a SID area that does not belong to a specific
NID area. 65535 indicates that mobile subscribers can roam over the whole SID
area. The allocation of NID is managed by each local network.
MDN MS DAS: identifying the switch in the local system
Maximum switchover node number of local office: restricts the quantity of the
nodes of the local office MSs that can be switched over. The Maximum
switchover node depth of local office restricts the quantity of the nodes of the
MSs that can be switched over at one time.
Maximum message retransmitting times: the maximum retransmitting times of

switchover messages
Get time from GPS configuration: related parameter settings taken by the clock,
including the BSC office from which the clock is to be taken, clock automatic
update time and allowed time difference
Feature code begins with “*”: the feature code begins with “*” or with “#”.
164
3.7.6 IMSI Configuration
In the Mobile Office Configuration window, select the IMSI Configuration

tab to switch to the corresponding page. There is no configuration record
Figure 3.7-15 IMSI Configuration
IMSI number: the IMSI number that needs to be configured
Virtual MSC ID: configured in VMSC Configuration
2. Adding an IMSI
Click in the IMSI Configuration page. The Add IMSI dialog box is
Input the configuration data and click OK to add an IMSI.
You can repeat the above steps to add multiple IMSIs.
Click Cancel or the button in the upper right corner to end the configuration.
Return to the IMSI Configuration, and you can find the added configuration
165
record.
3.7.7 MIN
In the Mobile Office Configuration window, select the MIN tab to switch to
the corresponding page. There is no configuration record initially, as shown in
Figure 3.7-16.
Figure 3.7-16 MIN Configuration
2. Adding a MIN
Click in the MIN page. The Add MIN dialog box is displayed. For
Input the configuration data and click OK to add a MIN.
You can repeat the above steps to add multiple MINs.
Click OK or the button in the upper right corner to end this configuration.
Return to the MIN page, and you can find the added configuration record.
166
whether the mobile office configuration data is saved in the database or not.
3.8 Mobile Area Code Configuration

1. Purpose
Configure the mobile area code.
2. Preparations
The BSC data configuration has been completed.
3. Detailed procedures
There are five options in Mobile Location Area Configuration: location area,
global cell, cell ID, special service group and VMSC location management.
Select the Location Area tab, and the interface shown below is displayed.
167
Figure 3.8-1 Location Area Configuration
3.8.1 Location Area
The location area states the correspondences between numbers and their location areas.
It includes the following three major functions.
Enables the system to page the called MS correctly.
Helps the switch to search for the previous VLR of the MS in location update.
Helps the switch to identify the related MSC numbers of destination cells in inter-office
switchover.
A location area number consists of the MCC, MNC and LAC. It is identified with the
LAIID inside the switch.
Two kinds of correspondences for location area numbers: the correspondence between
the location area and BSC of the local mobile switch, and the correspondence between
the MSC and VLR number of the adjacent location area.
Two kinds of location areas are required for location area management: the location
area of the local mobile switch and the adjacent location area of the local mobile
switch.
168
1. Adding a location area
Click Add in the Location Area interface. The dialog box shown in Figure
3.8-2 is displayed.
Figure 3.8-2 Adding a Location Area
Input the MCC, MNC, MSC number and VLR number, and input the location
area code in Location Area ID. If the location area belongs to the MSC, select
the corresponding BSC in Connected BSC Office ID. If the location area
belongs to the adjacent MSC, the Connected BSC Office ID field is
unavailable.
Finally, select the connected BSC and click OK to add the location area. At most
there are eight BSCs.
You can repeat the above steps to add multiple location areas.
Click Cancel or the button in the upper right corner to end the addition.
Return to the Location Area page, and you can find the added configuration
record.
169
3.8.2 Global Cell
The global cell management describes the correspondences between all global cells and
corresponding BSCs in the MSC. A global cell ID consists of the MCC, MNC, LAC
and CI.
In the Mobile Area Code Configuration (in Figure 3.8-1) interface, select the
Global Cell tab as shown in Figure 3.8-3.
Figure 3.8-3 Global Cell Management
2. Adding a global cell
Click Add in the Global Cell interface. The dialog box is displayed as shown in
Figure 3.8-4.
170
Figure 3.8-4 Adding a Global Cell
Input the parameters with reference to Figure 3.8-1. Select the connected BSC,
and click OK to complete the addition.
Click Cancel or the button in the upper right corner to end this
configuration. Return to the Global Cell page, and you can find the added
configuration record.
3.8.3 VMSC Location Management
In the Mobile Location Area Code Configuration interface, select VMSC

Location Management tab. There is no configuration record initially as shown
in Figure 3.8-5. This page shows the correspondence between the global cells
and virtual MSC and configures the global cells belonging to VMSC.
171
Figure 3.8-5 VMSC Location Management
LAI ID: configured in Location Area
CI: unchangeable, generated by the system by default
2. Adding a VMSC location
Click Add in the VMSC Location Management interface. A dialog box is

172
Figure 3.8-6 Adding a VMSC Location
The VMSC location management configuration aims for LAIs. You should input
the data, select the VMSC ID, and click OK to complete the addition.
You can repeat the above steps to add multiple location areas.
configuration. Return to the VMSC Location Management page, and you can
find the added configuration record.
3.8.4 Cell ID
The cell ID is used when the local MSC/VLR provides cell subscription restriction
service.
Cell subscription is a service restricting usage of MS. If the restriction location

information of a subscriber is set in the HLR, the VLR will judge whether the
subscriber can register according to the data in the Cell ID when the subscriber roams
to this MSC/VLR.
In the Mobile Area Configuration interface, select the Cell ID tab. The
interface is as shown in Figure 3.8-7.
173
Figure 3.8-7 Cell ID Configuration
2. Adding a cell ID
Click Add in the interface. A dialog box is displayed as shown in Figure 3.8-8.
Figure 3.8-8 Adding a Cell ID

174
The zone code is an identifier for a zone. It should be input according to actual
requirements. Then, you can click OK to add the cell ID.
You can repeat the above steps to add multiple cell IDs.
configuration. Return to the Cell ID page, and you can find the added
configuration record.
3.8.5 Special Service Group
In the Mobile Area Configuration interface, select the Special Service Group
tab. The interface is as shown in Figure 3.8-9.
Figure 3.8-9 Special Service Group Configuration
The Special Service Group configuration is to provide the nearest access method
to the special service. This option can be used together with the special service
number analysis in Number Analysis to connect the special service in a specific
location area for the MS to a fixed phone or a mobile phone.
175
For example, if the special service group is configured as shown in Figure

3.8-10, the call dialed in location area 0001 will be connected to the phone on
operator console 2122 corresponding to special service template 1 when 110 is
selected for the special service user group in the special service number analysis
entry of the originating digit analysis selector.
Figure 3.8-10 Special Service Group Configuration
2. Adding a special service group
Click Add in the Special Service Group interface. A dialog box is displayed as
There are two kinds of special service groups: based on LAI and based on CI.
The LAI has a large scope, and CI has a small one. Input the parameters
according to interface prompts and click OK to complete the addition.
You can repeat the above steps to add multiple special services.
configuration. Return to the VMSC Location Management page, and you can
find the added configuration record.
176
3.8.6 Special Service Group Template
In the Mobile Area Code Configuration interface, select the Special Service
Group Template tab. There is no corresponding configuration record initially.
The tab page is displayed as shown in Figure 3.8-11.
Figure 3.8-11 Special Service Group Template
2. Adding a special service group template
Click Add in the Special Service Group Template interface. A dialog box is
177
Figure 3.8-12 Adding a Special Service Group Template
Input the parameters and click OK to complete the addition.
You can repeat the above steps to add multiple special service group templates.
configuration. Return to the Special Service Group Template page, and you
can find the added configuration record.
whether the mobile area code configuration data is saved in the database or not.
3.9 BSC Configuration

1. Purpose
In the mobile switching system, the mobile switch controls one or multiple
BSCs that are connected through a digital trunk. BSC data configuration is to
establish the correspondences between route chains between the MSCe (or
MGW) and the BSC.
2. Preparations
178
The outgoing link chains have been configured in Trunk Management.

BSC configuration, and the BSC Configuration window is displayed on the
right side. There is no configuration record initially as shown in Figure 3.9-1.
Figure 3.9-1 BSC Configuration
BSC ID: the office direction of the BSC ID.
Version information: specifies the standard the BSC adopts. The BSC 95 adopts
the IOS20, and the BSC 1X adopts the IOS40.
BSC type: including 2G BSC and 3G BSC
179
Supported service of BSC: some ground circuit management services supported

by BSC, usually all are selected
Route chain: this option can be selected only when the circuit ID of the outgoing
route chain is set to A-interface circuit in Trunk Management.
4. Adding a BSC
1) Enter the interface for adding a BSC.
Click in the BSC Configuration window. The Add BSC Configuration

dialog box is displayed. For the parameter descriptions, refer to the “Interface
2) Add a BSC.
Input the configuration data and click OK to add a BSC. Figure 3.9-2 shows
how to add a BSC.
Figure 3.9-2 Adding a BSC
You can repeat the above steps to add multiple BSCs.
180
configuration. Return to the BSC Configuration page, and you can find the
added configuration record.
5. Result Verification
Exit the configuration management subsystem first, and then log in again to
query whether the BSC configuration data is saved in the database or not
3.10 Mobile Number Analysis Configuration

1. Purpose
Configure the mobile number analysis, local toll area code, number roaming
analysis, operator configuration and other number configuration relating to
mobile number analysis.
2. Preparations
3.10.1 Mobile number analysis

Mobile number analysis configuration from the navigation tree. By default,
the Mobile Number Analysis tab page is displayed on the right side without any
181
Figure 3.10-1 Mobile Number Analysis
Analyzed digit: the mobile number to be analyzed
Diversion method: the mode for changing mobile numbers, including add, delete
and replace
Starting position: the starting position of number stream transform
Deleted/Modified bit: the length of the deleted/modified number stream
Added/Modified number: starting position of the number that begins to be

added or modified from the transform
GT type: the type of GT, usually GT4
Code plan: the code plan of mobile numbers, usually Land Numbering Plan is
selected
Address attribute: usually international number
2. Adding a mobile number analysis
1) Enter the interface for adding mobile number analysis.
Click in the Mobile Number Analysis Configuration window. The Add

mobile number analysis dialog box is displayed. For parameter descriptions,
182
refer to “Interface operations” above.
2) Add a mobile number analysis.
Input the configuration data. The configuration interface is as shown in Figure

3.10-2.
Figure 3.10-2 Adding a Mobile Number Analysis
In the Add mobile number analysis interface, click OK to add the current
configuration.
You can repeat the above steps to add multiple mobile number analysis.
this configuration.
3) Query the added mobile number analysis
After a mobile number analysis is added, its configuration record will be

displayed in the Mobile Number Analysis Configuration window.
183
3.10.2 Local Area Number

Mobile number analysis configuration from the navigation tree. The Mobile
Number Analysis Configuration window is displayed on the right side. By
default, the Local Area Number tab page is displayed without any
Figure 3.10-3 Local Area Number
2. Adding a local area number
1) Enter the interface for adding local area numbers.
Click in the Local Area Number window. The Add local area number
analysis dialog box is displayed. For parameter descriptions, refer to “Interface
2) Add a local area number.
184

3.10-4.
Figure 3.10-4 Adding a Local Area Number
In the Add local area number analysis interface, click OK to add the current
configuration.
You can repeat the above steps to add multiple local area numbers.
this configuration.
3) Query the added local area number
After a local area number is added, its configuration record will be displayed in
the Mobile Number Analysis Configuration window.
3.10.3 Other Number

Mobile number analysis configuration from the navigation tree. The Mobile
Number Analysis Configuration window is displayed on the right side. Select
the Other Number tab to switch to the corresponding page. By default, there is
no configuration record initially, as shown in Figure 3.10-5.
185
Figure 3.10-5 Other Number Configuration
Analysis result: totally eight kinds: Information service center, secretary station,
caller paid call, local subscriber, public CDMA WLL, support IS848 HLR GT,
pulse charge subscriber and polarity reversed line
2. Adding other numbers
1) Enter the interface for adding other numbers.
Click in the Other Number page. The Add other number dialog box is
2) Add other numbers.

3.10-6.
186
Figure 3.10-6 Adding Other Numbers
In the Add other number interface, click OK to add the current configuration.
You can repeat the above steps to add multiple other numbers.
this configuration.
3) Query the added number
After a number is added, its configuration record will be displayed in the Other
Number page.
whether the mobile number analysis data is saved in the database or not.
3.11 Numbering Plan

1. Purpose
187
The numbering plan data describes the numbering plans for different mobile
number types. The numbering plan management involves adding, deleting and
modifying numbering plan data. Its data has been set by default when the system
is installed. Usually no change is required. If there is a special requirement, you
can adopt the configuration methods as follows.
2. Preparations

Numbering plan configuration from the navigation tree. By default, the
Numbering Plan Configuration window is displayed on the right side without
any configuration record initially, as shown in Figure 3.11-1.
Figure 3.11-1 Numbering Plan Management
y Note:
By default, all parameters on this interface have been set when the system is installed.
Usually no modification is required.
188
Mobile number type: listed in Table 3.11-1
Table 3.11-1 Mobile Number Types
Serial No. Type

1 Mobile subscriber MDN
2 SGSN number
3 Other special number
4 HON
5 BS ID
6 Global cell ID
7 TMSI
8 Mobile subscriber roaming number
9 Mobile subscriber ISDN number
10 Temporary local subscriber number
Numbering plan: listed in Table 3.11-2.
Table 3.11-2 Numbering Plans
Serial No. Plan

1 Not defined
2 ISDN/telephone numbering plan (1)
3 Data numbering plan (3)
4 Telex numbering plan (4)
5 Land mobile numbering plan (6)
6 National numbering plan (8)
7 Private numbering plan (9)
Address type: national number and international number
3. Adding a numbering plan
1) Enter the interface for adding numbering plans.
Click in the Numbering Plan window. The Add numbering plan dialog
above
2) Add a numbering plan.
Here, adding a mobile subscriber MDN is taken as an example. Select the

configuration data. The configuration interface is as shown in Figure 3.11-2.
189
Figure 3.11-2 Adding a Numbering Plan
The subscriber number types that have been configured are not displayed in the
Mobile Number Type drop-down list.
3) Add a numbering plan.
Click OK in the Add numbering plan dialog box to add the current
configuration.
this configuration.
4) Query the added numbering plan.
Repeat steps 2 and 3 to add multiple numbering plans.
After a numbering plan is added, its configuration record will be displayed in the
Numbering Plan window.
query whether the numbering plan configuration data is saved in the database or
not.
3.12 VLR Configuration

1. Purpose
Configuring the VLR configuration, including the VLR system parameter

configuration, IMSI segmental table configuration, TLDN segmental
configuration and TRN configuration. The system parameters usually have been
190
determined during commissioning. They can be queried but no modification is

required.
2. Preparations

VLR configuration from the navigation tree. By default, the VLR
Configuration window is displayed on the right side without any configuration
record initially, as shown in Figure 3.12-1.
Figure 3.12-1 VLR Configuration (System Parameter Window)
3.12.1 VLR System Parameter Configuration
By default, the System Parameter tab page is displayed in the VLR

Configuration window (or enter this page after selecting the System
191
Parameter tab). The default data configuration is displayed, as shown in Figure

3.12-1.
The VLR system parameters are described as follows.
BSC periodical location update time: the VLR will consider that the subscriber
is unreachable (beyond the range of this VLR) when the subscriber location has
not been updated within BSC periodical location update time + VLR location
update protection time.
Inactive user deletion duration: if a subscriber has not registered to the VLR or
not updated the location within a period of time, the VLR will delete the
subscriber’s record.
Roaming user deletion duration: if the subscriber has not released the roaming
number when it reaches the preset time, the roaming number will be released
forcefully.
TRN head: used for OTA service
System connect need AC parameters: the subscriber inquires authentication

parameters from the HLR during registration, for authentication purpose.
Signal encrypt: encrypts signaling
Tone encrypt: encrypts tones
Can execute CAVE: the VLR can execute the authentication algorithm
Sharing SSD: the VLR can conduct SSD sharing
Denial period type: after some time since registered to the VLR, the subscriber
must request the registration information again from the HLR to make calls to be
connected.
Cycle: Other denial types except Each Call and Pre-defined use denial values.
Predefined means that the time interval has been specified beforehand and it is
unnecessary to specify the period.
8 Tips
The default configurations in the page are preferred data. They are for your reference.
192
3.12.2 IMSI Segmental Table Configuration
In the VLR Configuration window, select the IMSI Segmental Table tab to
switch to the corresponding page as shown in Figure 3.12-2.
Figure 3.12-2 IMSI Segmental Table
Mod remainder: ranging from 0 to 63
Default assign mod remainder: the default IMSI segmental table includes 64
records, and the mod remainder ranges from 0 to 63.
Primary module: usually managed by primary module No.
Secondary module: when the primary module works normally, the secondary
module will not run. When the primary module is faulty, the secondary module
will take over the services.
2. Adding an IMSI segmental table
1) Enter the interface for adding IMSI segmental tables.
Click in the IMSI Segmental Table page. The Add IMSI segmental
193
table dialog box is displayed. For parameter descriptions, refer to “Interface

2) Add an IMSI segmental table.
Here, default assign mod remainder is taken as an example. Input the

configuration. The configuration interface is as shown in Figure 3.12-3.
Figure 3.12-3 Adding an IMSI Segmental Table
3) Add an IMSI segmental table.
In the Add IMSI segmental table dialog box, click OK to add the current
configuration.
this configuration.
4) Query the added IMSI segmental table.
194
After an IMSI segmental table is added, its configuration record will be

displayed in the IMSI Segmental Table page, as shown in Figure 3.12-4.
Figure 3.12-4 Querying the Added IMSI Segmental Table
3.12.3 TLDN Segmental Table Configuration
In the VLR Configuration window, select the TLDN Segmental Table tab to
195
Figure 3.12-5 TLDN Segmental Table Configuration
Module: the module No. allocated according to the TLDN
Beginning TLDN segmental granularity: the beginning value of the TLDN

segmental granularity
Ending TLDN segmental granularity: the ending value of the TLDN segmental
granularity. Used for matching the last three digits of the TLDN, to select the
management module No.
2. Adding, modifying and deleting a TLDN segmental table
The operations and procedures are just the same as the adding, modifying and
deleting operations described in the IMSI Segmental Table page. For detailed
procedures, please refer to that section.
For parameter details about adding and modifying, please refer to “Interface
operations” in this section.
Figure 3.12-6 shows how to configure the TLDN segmental table.
196
Figure 3.12-6 Adding a TLDN Segmental Table
3.12.4 TRN Segmental Table Configuration
To meet the requirements of the new function points of OTA, the TRN segmental table
must be configured.
In the VLR Configuration window, select the TRN Segmental Table tab to
197
Figure 3.12-7 TRN Segmental Table Configuration
Module: the module No. allocated according to the TRN
Beginning TRN segmental granularity: the beginning value of the TRN

segmental granularity
Ending TRN segmental granularity: the ending value of the TRN segmental
granularity. Used for matching with the last two digits of the TRN, to select the
management module No.
2. Adding a TRN segmental table
1) Enter the interface for adding TRN segmental tables.
Click in the TRN Segmental Table page. The Add TRN segmental table
2) Configure the data of a TRN segmental segment
Here, default assign mod remainder is taken as an example. Input the

configuration. The configuration interface is as shown in Figure 3.12-8.
198
Figure 3.12-8 Adding a TRN Segmental Table
3) Add a configuration record.
In the Add TRN segment dialog box, click OK to add the current configuration.
this configuration.
4) Query the added configuration record.
After a TRN segment is added, its configuration record will be displayed in the
TRN Segmental Table page, as shown in Figure 3.12-8.
whether the VLR configuration data is saved in the database or not.
3.13 Tone Resource Configuration

1. Purpose
Configure tone resources to ensure that tones can be played normally.
2. Preparations
199

Tone resource configuration from the navigation tree, and the Tone Resource
Configuration window is displayed on the right side, as shown in Figure
3.13-1.
Figure 3.13-1 Tone Resource Configuration (Language Template Page)
Language temlpate No.: the code of the language template
Language type: totally 10 language types: language combination 1 to 10
Language code: the code of the language
y Note:
The interface data is configured by default.
After the system works normally, do not change any configuration at will because an
incorrect change may result in announcement failure.
200
3.13.1 Language Template Configuration
The Language Template tab page is displayed (or by selecting the Language
Template tab) in the Tone Resource Confgiuration window by default, as
2. Adding a language template
1) Enter the interface for adding language templates
Click in the Language Template page. For parameter descriptions, please

refer to “Interface operations” in this section.
2) Configure a language template.
Adding the language template 2 is taken as an example. The configuration

interface is as shown in Figure 3.13-2.
Figure 3.13-2 Adding a Language Template
3) Add a language template.
Click OK in the Add language template interface to add the current

configuration.
this configuration.
4) Query the added language template.
201
You can repeat steps 2 and 3 to add multiple language templates.
After a language template is added, its configuration record will be displayed in

the Language Template page.
3.13.2 Tone Mode Configuration
In the Tone Resource Configuration window, select the Tone Mode tab to
switch to the corresponding page. There is one configuration record initially, as
Figure 3.13-3 Tone Mode Configuration
Tone mode: generated by the system by default. No modification is allowed.
Language type: totally 10 language types: language combination 1 to 10
Loop times: announcement times
Tone duration: 2000 by default, changeable
Tone interval: time interval between two tones
Notify tone completion: three types: notification upon timeout, notification upon
event interruption and notification upon new signal description interruption
202
2. Adding, modifying and deleting a tone mode
deleting operations described in the IMSI Segmental Table page. For detailed
3.13.3 Service Key Conversion
In the Tone Resource Configuration window, select the Service Key

Conversion tab to switch to the corresponding page. There is no configuration
record initially as shown in Figure 3.13-4.
Figure 3.13-4 Service Key Conversion
Other manufacturer’s service key: the code of other manufacturer’s service key
Service type: totally four types: PPC, FPH, VPN and supplementary service
Service key: usually the service key code of PPC is 128, FPH is 129, VPN is
130, and supplementary service is 990.
203
y Note:
Do not change any configuration at will after the system works normally.
2. Adding, modifying and deleting service key conversion
deleting operations described in the Language Template page. For detailed
Figure 3.13-5 shows how to convert service keys.
Figure 3.13-5 Adding Service Key Conversion
whether the tone resource configuration data is saved in the database or not.
3.14 Pulse Charge Configuration

1. Purpose
The pulse charge function is to determine the fee of subscribers through the
pulse quantity. The BCM can send pulse messages to the A-interface and then
204
accumulate the pulse quantity in each call. Usually each subscriber is allocated
to some software charge accumulators to accumulate the quantity of pulses of
the subscribers, thus determining the fee for the subscribers. The configuration
module configures the charging algorithm and synchronizes it to the foreground
database subsystem.
2. Preparations
3.14.1 Subscriber Group Configuration

Pulse charge configuration from the navigation tree, and the Pulse Charge
Configuration window is displayed on the right side. By default, the
Subscriber Group Configuration tab page is displayed without any
Figure 3.14-1 Subscriber Group Configuration
205
Subscriber group ID: the No. of the subscriber group
Subscriber group type: including local subscriber, outgoing subscriber, and

special subscriber
Subscriber group name: description of a subscriber group
2. Adding a subscriber group
1) Enter the interface for adding subscriber groups.
Click in the Subscriber Group Configuration page. The Add

subscriber group information dialog box is displayed. For parameter
2) Add a user group.
In the Add subscriber group information dialog box, input the configuration
data and click OK to add a subscriber group. Figure 3.14-2 shows a
configuration example.
Figure 3.14-2 Adding a User Group
this configuration.
3) Query the added device node
After a subscriber group is added, its configuration record will be displayed in
206
the Subscriber Group Configuration page.
3. Modifying a subscriber group
1) Enter the interface for modifying subscriber groups.
In the Subscriber Group Configuration page, select the configuration record
to be modified and click . The Modify subscriber group information

dialog box is displayed as shown in Figure 3.14-3.
Figure 3.14-3 Modifying a Subscriber Group
3.14.2 Number Prefix Group
You can query subscriber groups according to subscriber number prefixes, to charge
the calls of different types.

Pulse charge configuration from the navigation tree, and the Pulse Charge
Configuration window is displayed on the right side. Select the Number Prefix
Configuration tab to switch to the corresponding page where no configuration
record is available initially, as shown in Figure 3.14-4.
207
Figure 3.14-4 Number Prefix Configuration
Number prefix: the prefix of a number
Number type: including local subscriber, outgoing subscriber and special

subscriber
Subscriber group name: the name of the subscriber group corresponding to the
number type
2. Adding a number prefix group
1) Enter the interface for adding number prefix groups.
Click in the Number Prefix Configuration page to display the Add

number prefix dialog box. You can refer to “Interface operations” for parameter
descriptions.
2) Configure a number prefix group.
In the Add number prefix dialog box, input the configuration data and click
OK to add a number prefix. Figure 3.14-5 shows a configuration example.
208
Figure 3.14-5 Adding a Number Prefix
You can repeat the above steps to add multiple number prefixes.
this configuration.
3) Query the added number prefix.
After a number prefix is added, its configuration record will be displayed in the
Number Prefix Configuration page.
3.14.3 Common-time Discount Configuration

Pulse charge configuration from the navigation tree. The Pulse Charge
Configuration window is displayed on the right side. Select the Common-time
Discount Configuration tab to switch to the corresponding page. By default,
there is no configuration record initially, as shown in Figure 3.14-6.
209
Figure 3.14-6 Common-time Discount Configuration
Discount ID: ranging from 1 to 255
Discount date: eight types: every day, Monday, Tuesday, Wednesday, Thursday,
Friday, Saturday, and Sunday:
Discount type: discount by percentage or by actual period
Discount zone number: the quantity of discount zones, ranging from 1 to 16
Time point 1 to time point 17: time point 1 and time point 2 form a discount
zone. And by analogy, other discount zones are formed.
Discount rate: the unit of discount rate. If the discount is based on percentage,
the unit is “%”; if the discount is based on actual period, the unit is “10ms”.
Discount zone 1 to discount zone 16: set a discount rate for discount zones 1 to
16. But usually only some of the zones are used
2. Adding common-time discount
1) Enter the interface for adding common-hour discounts.
Click in the Common-hour Discount Configuration page. The Add

common-time discount information dialog box is displayed. For parameter
210
2) Configuring the common-hour discount information.
In the Add common-hour discount configuration dialog box, input the

configuration data and click OK to add a common-hour discount. Figure 3.14-7
shows a configuration example.
Figure 3.14-7 Adding a Common-hour Discount
You can repeat the above steps to add multiple common-time discounts.
this configuration.
3) Query the added common-hour discount.
After a common-hour discount is added, its configuration record is displayed in

the Common-hour Discount Configuration page.
3.14.4 Holiday Discount Configuration

Pulse charge configuration from the navigation tree to display the Pulse
Charge Configuration window. Then, select the Holiday Discount
211
Figure 3.14-8 Holiday Discount Configuration
Discount ID: ranging from 1 to 255
Discount date: in a format of month and day
Discount type: discount by percentage or by actual period
Discount zone number: the quantity of discount zones, ranging from 1 to 16
Time point 1 to time point 17: time point 1 and time point 2 form a discount
zone. And by analogy, the rest can be formed.
Discount rate: the unit of discount rate. If the discount is based on percentage,
the unit is “%”; if the discount is based on actual period, the unit is “10ms”.
Discount zone 1 to discount zone 16: set a discount rate for discount zones from
1 to 16. But usually only some of them are used
2. Adding a holiday discount
1) Enter the interface for adding a holiday discounts.
Click in the Holiday Discount Configuration page. The Add holiday

discount information dialog box is displayed. For parameter descriptions, refer
212
2) Configure the holiday discount information.
In the Add holiday discount information dialog box, input the configuration
data and click OK to add a holiday discount. Figure 3.14-9 shows a
configuration example
Figure 3.14-9 Adding a Holiday Discount
You can repeat the above steps to add multiple holiday discounts.
this configuration.
3) Query the added holiday discounts.
After a holiday discount is added, its configuration record will be displayed in

the Holiday Discount Configuration page.
3.14.5 Rate Configuration

Configuration window is displayed on the right side. Select the Rate
213
Figure 3.14-10 Rate Configuration
Rate ID: the No. of the charge rate
Use charging level 1/2/3/4: the charging level to be enabled
Duration of free: the duration when calls are free of charge, in 10 ms.
Duration of lowest consumption: the duration of the lowest consumption , in 10

ms.
Pulses number in lowest consumption duration: the quantity of pulses sent

during the lowest consumption duration
Duration of periodically sending pulses: the duration of periodically sent pulses

during normal consumption, in 10 ms
Pulses number in each period: the quantity of the pulses to be sent in a period
Discount method: four kinds: no discount, common-time discount, holiday

discount, and both
Discount ID: selected according to the discount method
2. Adding a holiday discount
1) Enter the interface for adding rate information.

214
Click in the Rate Configuration page. The Add rate information dialog
above.
2) Add a rate.
In the Add rate information dialog box, input the configuration data and click
OK to add a rate. Figure 3.14-11 shows a configuration example.
Figure 3.14-11 Adding a Rate
You can repeat the above steps to add multiple rates.
215
this configuration.
3) Query the added rate.
After a rate is added, its configuration record will be displayed in the Rate
Configuration page.
3.14.6 Group Rate Configuration
This configuration is used to query a subscriber’s rate ID according to the subscriber

group.

Configuration window is displayed on the right side. Select the Group Rate
Figure 3.14-12 Group Rate Configuration
216
Calling group name: the group name of the calling party
Called group name: the group name of the called party
Rate ID: the No. of the rate
2. Adding a group rate
1) Enter the interface for adding group rates.
Click in the Group Rate Configuration page. The Add group rate
information dialog box is displayed. For parameter descriptions, refer to
“Interface operations” above.
2) Add a group rate.
In the Add group rate information dialog box, input the configuration data and
click OK to add a group rate. Figure 3.14-13 shows a configuration example.
Figure 3.14-13 Adding a Group Rate
You can repeat the above steps to add multiple group rates.
this configuration.
217
3) Query the added group rate.
After a group rate is added, its configuration record will be displayed in the
Group Rate Configuration page as shown in Figure 3.14-14.
Figure 3.14-14 Querying the Added Group Rate
3.14.7 Supplementary Service Rate Configuration
This configuration is used to query a subscriber’s rate ID according to the

supplementary service code.

Configuration window is displayed on the right side. Select the
Supplementary Service Rate Configuration tab to switch to the corresponding
page. There is no configuration record initially, as shown in Figure 3.14-15.
218
Figure 3.14-15 Supplementary Service Rate Configuration
Supplementary service number: input the supplementary service code
Number of pulses: the quantity of the pulses to be sent
2. Adding a supplementary service rate
1) Enter the interface for adding supplementary service rates.
Click in the Supplementary Service Rate Configuration page. The Add

supplementary service rate information dialog box is displayed. For
2) Add a supplementary service rate.
In the Add supplementary service rate information dialog box, input the
configuration data and click OK to add a supplementary service rate. Figure
3.14-16 shows a configuration example.
219
Figure 3.14-16 Adding a Supplementary Service Rate
You can repeat the above steps to add multiple supplementary service rates.
this configuration.
3) Query the added supplementary service rate.
After a supplementary service rate is added, its configuration record will be

displayed in the Supplementary Service Rate Configuration page.
3.15 OTA Configuration

1. Purpose
The OTA configuration is to allocate OTA numbers.
2. Preparations

OTA configuration from the navigation tree. By default, the OTA
Configuration tab page is displayed on the right side without any configuration
record initially, as shown in Figure 3.15-1.
220
Figure 3.15-1 OTA Configuration
OTA number: when dialed, this number will be connected to the customer
service center.
MDN of CSC: the phone number of the customer service center
4. Adding an OTA number
1) Enter the interface for adding OTA numbers.
Click in the OTA Configuration page. The Add OTA number dialog
above.
2) Add an OTA number.
In the Add OTA number dialog box, input the configuration data and click OK
to add an OTA number. Figure 3.15-2 shows a configuration example.
221
Figure 3.15-2 Adding an OTA
You can repeat the above steps to add multiple OTA numbers.
this configuration.
3) Query the added OTA number.
After an OTA number is added, its configuration record will be displayed in the
OTA Configuration page.
222
4 Configuration Tools
Key points
· Data synchronization
· Data backup and restoration
· Security variable
4.1 Overview
The ZXC10-MSCe data configuration covers two parts:
Background subsystem in Client/Server architecture (centering on the server)
Foreground No.7 front PC subsystem
A great amount of data configured and modified by the background subsystem is saved
in the database. The configuration data will be effective only after it is sent to the
foreground subsystem.
Data synchronization is to transfer the data from the background subsystem to the
foreground subsystem to make the user’s configuration data effective.
Data backup is to back up the configured data and save as files.
Data restoration is to restore the backup data to the system. In data restoration, the
original data will be overwritten. If unnecessary, try to avoid this operation.
Security variable management is to maintain some global variables in the foreground

NE module.
4.2 Main Interface

On the main Configuration Management interface, expand the navigation tree to
display the configuration tools interface as shown in Figure 4.2-1.
223
Figure 4.2-1 Configuration Tools
4.3 Data Synchronization

1. Purpose
Transfer the data from the background to the foreground subsystem to make the
user’s configuration data effective.
There are three modes for data synchronization.
Transfer all tables. Due to the low transfer speed, this option is usually not used
unless for commissioning.
Transfer the R_CONST table to the foreground.
Transfer the changed table. That is, transfer the changed data tables only to the
foreground. It is used to transfer some modified tables independently, trying to
reduce data transfer loads upon the system.
2. Preparations
The data has been configured (some data can also be synchronized).
In the Configuration Management interface, select Configuration Tools >

Data synchronization from the navigation tree. The Data Synchronization
224
Chapter 4 Configuration Tools
window is displayed as shown in Figure 4.3-1.
Figure 4.3-1 Data Synchronization
: Select all. Selects all records in the module information.
: Clear all. Not select any record in the module information.
: Data synchronization. Synchronizes the background database to the

foreground.
: Synchronization notification. Through this function, other functional

modules (such as alarm management) can be notified about the changes to
configuration data.
Module: listing the information of all modules that can be used for transmission
Progress: Displaying the transmission progress during synchronization, and

displaying some prompts in case of synchronization failure
Transmission mode: implementing the total transmission mode
Synchronization tables: synchronizing R_CONST table, all tables or changed
225
tables
Synchronization option: selecting Primary/Secondary or Save to Disk
Timer: synchronization timeout timer. When the synchronization time is more

than this value, the synchronization fails.
4. Data synchronization
Select the module, synchronization tables and synchronization option, input the
Timer value, and click . The prompt for your confirmation is displayed.
Click OK to begin synchronizing the data to the foreground.
To send the data to one module of the switch only, you can select the specified
module for independent transmission.
y Note:
When synchronizing data for the first time, be sure to synchronize the R_CONST table
first and then synchronize all tables.
5. Result verification
Query whether the data tables are consistent with those defined in the
background through the probe.
4.4 Backup and Restoration

1. Purpose
Backup is to back up the configuration data of the system to disks.
Restoration is to restore the data files stored on the disks to the system.
2. Preparations
The data has been configured (or a part of data has been configured).

Backup and restoration from the navigation tree. The Backup/Restoration
226
Figure 4.4-1 Backup and Restoration
: Backs up the database
: Restores the database
: Refreshes the interface
4. Data backup
1) In the MSCe Backup/Restoration Main Interface, select Backup to file and

input the SQL file name.
2) Click Backup. The Choose hint dialog box is displayed, as shown in Figure
4.4-2.
227
Figure 4.4-2 Data Backup
Click OK, and the system backs up the database to the specified SQL file.
3) After the backup is completed, the Hint information dialog box is displayed,
prompting the successful backup. The backup file is saved in C:\Backup\Msce.
Figure 4.4-3 Successful Backup Prompt
5. Restoration
1) In the MSCe Backup/Restoration Main Interface, select Restore from file, and
input the SQL file name or select a file directly in the interface.
2) Click Restore. The Choose hint dialog box is displayed, as shown in Figure
4.4-4.
Figure 4.4-4 Confirming Restoration
3) Click OK, and the system will restore the data saved in the SQL file to the
228
system database automatically.
4) After the restoration is completed, a dialog box is displayed prompting the

successful restoration.
Figure 4.4-5 Successful Restoration Prompt
check whether the database backup file exists and whether the data restored
from the backup file is saved in the database.
4.5 Security Variable

1. Purpose
Security variable management is to maintain some global variables in the

foreground NE module.
2. Preparations

Security variable from the navigation tree. The Security Variable Control
229
Figure 4.5-1 Security Variable Control
: Identity secrecy. For setting the identity secrecy parameters in modules
: A-interface variable control. For setting the A-interface parameters in

modules and for flow control
: BCM variable control. For setting basic conversation module related

parameters in modules and implementing service control on the basic call part
: Service control variable. For setting service variable related parameters in

modules to change the supported services
: Send parameter. For sending the modified data to the foreground
4. Identity secrecy
In the Security Variable Control window, select modules and click to

switch to the identity secrecy interface to display the identity secrecy parameters
related to the selected modules.
230
Figure 4.5-2 Identity Secrecy Configuration
Name: lists all parameters relating to identity secrecy
Value: the current value of each parameter
Value range: range of each parameter
Description: simply describes the functions of each parameter
Double-click the data in the interface and modify it according to prompts. Click
to complete identity secrecy settings.
5. A-interface variable configuration
In the Security Variable Control window, select modules and click to

switch to the A-interface variable control interface to display the A-interface
variable parameters related to the selected modules.
231
Figure 4.5-3 A-interface Variable Configuration
Name: lists all parameters of A-interface variables
to complete A-interface variable settings.
6. BCM variable configuration
In the Security Variable Control window, select modules and click . The
BCM variable configuration window is displayed, showing the BCM variable
parameters related to the selected modules.
232
Figure 4.5-4 BCM Variable Configuration
Name: lists all parameters of BCM variables
to complete BCM variable settings.
7. Service variable configuration
In the Security Variable Control window, select modules and click . The
service variable configuration window is displayed, showing the service variable
parameters related to the selected modules.
233
Figure 4.5-5 Service Variable Configuration
Name: lists all parameters of BCM variables
to complete service variable settings.
8. Sending security variable parameter
In the Security Variable Control window, click , and a prompt is displayed

234
Figure 4.5-6 Confirmation Prompt
Click OK, to send the variables of the module to the foreground. If successful,
the data will be saved to the server.
Or, click Cancel to cancel the operation.
9. Result verification
Query whether the data tables are consistent with those defined in the
background through the probe.
235

CM3G-302-E1 Introduction To The ZXC10 MSCe Data Configuration

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

CM3G-302-E1 Introduction To The ZXC10 MSCe Data Configuration

Uploaded by

Copyright:

Available Formats

CM3G-302-E1 Introduction to the ZXC10

MSCe Data Configuration

1.1 Overview of Configuration Management System............................................................................. 1

1.2 Basic Configuration Sequence .......................................................................................................... 1

2.2 Main Interface ................................................................................................................................... 6

2.3 Physical Configuration...................................................................................................................... 7

2.3.1 Configuring Racks ................................................................................................................. 9

2.3.2 Configuring Shelves............................................................................................................. 11

2.3.3 Configuring Boards.............................................................................................................. 13

2.3.4 Configuring Module Types .................................................................................................. 19

2.3.5 Configuring Capacity Planning Parameters ......................................................................... 25

2.3.6 Configuring Module/Board Relationship............................................................................. 26

2.3.7 Configuring IP Interfaces ..................................................................................................... 29

2.3.8 Configuring IP Static Routes................................................................................................ 32

2.4 Office Configuration ....................................................................................................................... 35

2.4.1 Local Office Configuration .................................................................................................. 36

2.4.2 Signaling Configuration ....................................................................................................... 37

2.4.3 Adjacent Office Configuration ............................................................................................. 39

2.4.4 SIP Office Configuration...................................................................................................... 42

2.5 No. 7 Data Configuration―MTP Configuration............................................................................. 45

2.5.1 Configuring Signaling Link Groups..................................................................................... 46

2.5.3 Configuring Signaling Routes ..............................................................................................51

2.5.4 Configuring Signaling Office IDs.........................................................................................53

2.5.5 Verification ...........................................................................................................................55

2.6 No. 7 Data Configuration―SCCP Configuration............................................................................55

2.6.1 Configuring GT Translation Selectors ..................................................................................56

2.6.2 Configuring GT Translation Data .........................................................................................60

2.6.3 Verification ...........................................................................................................................65

2.7 No. 7 Data Configuration―SSN Configuration..............................................................................65

2.8 No. 7 Data Configuration―Narrow-band Signaling Configuration................................................69

2.9 Sigtran Configuration ......................................................................................................................71

2.9.1 Configuring SCTP Basic Connection ...................................................................................71

2.9.2 Configuring ASPs .................................................................................................................75

2.9.3 Configuring ASs ...................................................................................................................77

2.9.4 Configuring SIO Positioning ASs.........................................................................................80

2.9.5 Verification ...........................................................................................................................82

3 MSCe Configuration ................................................................................................................................83

3.1 Overview .........................................................................................................................................83

3.2 Main Interface..................................................................................................................................83

3.3 Number Analysis Configuration ......................................................................................................84

3.3.1 Digit Analysis Selector Configuration ..................................................................................86

3.3.2 Analyzer Entry Configuration...............................................................................................89

3.3.3 Examples of Number Analysis Configuration ......................................................................98

3.3.4 SCP/GT Address Index Configuration................................................................................102

3.3.5 Number Transform/Display Selector ..................................................................................104

3.3.6 Number Transform/Display ................................................................................................107

3.4 Topological Relation Configuration.............................................................................................. 110

3.4.1 Coding/Decoding Type Configuration ................................................................................111

3.4.2 Device Node Configuration ............................................................................................... 113

3.4.3 BSC-MGW Relationship Configuration ............................................................................ 116

3.4.4 SIP Transfer Protocol Configuration .................................................................................. 119

3.4.5 DIGITMAP Module Configuration.................................................................................... 122

3.4.6 Encoding Name Configuration........................................................................................... 125

3.4.7 Result Verification.............................................................................................................. 126

3.5 Trunk Management ....................................................................................................................... 126

3.5.1 Trunk Group Configuration................................................................................................ 127

3.5.2 PCM Configuration............................................................................................................ 135

3.5.3 Outgoing Route .................................................................................................................. 137

3.5.4 Outgoing Route Set ............................................................................................................ 138

3.5.5 Outgoing Route Chain........................................................................................................ 140

3.5.6 Inner-office MGW Topological Relation Configuration .................................................... 143

3.5.7 Virtual CIC Configuration.................................................................................................. 145

3.5.8 Result Verification.............................................................................................................. 148