UMG8900 CONFIGURACIÓN 307315391-01-Initial-Configuration-V300R010C03-02 PDF

U-SYS SoftX3000 SoftSwitch System
V300R010C03
Initial Configuration
Issue 02
Date 2010-09-14
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2010. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 02 (2010-09-14) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
Initial Configuration About This Document
About This Document
Related Versions
The following table lists the product versions related to this document.
Product Name Version
U-SYS SoftX3000 V300R010C03
Intended Audience
This document describes the data configuration process and methods, database structure, and
database operations of the SoftX3000.
This document is intended for:
l Data configuration engineers
l Maintenance engineers
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Changes in Issue 01 (2010-03-25)

First commercial release.
Changes in Issue 02 (2010-09-14)

Second commercial release.
Issue 02 (2010-09-14) Huawei Proprietary and Confidential iii

Initial Configuration Contents
Contents
About This Document...................................................................................................................iii

1 Data Configuration Procedure.................................................................................................1-1
2 Planning Data.............................................................................................................................2-1
2.1 Planning the Bearer Network IP Address.......................................................................................................2-2
2.2 Planning the Equipment Data..........................................................................................................................2-7
2.2.1 Planning the Cabinet Data......................................................................................................................2-8
2.2.2 Planning the Subrack Data.....................................................................................................................2-9
2.2.3 Planning the Board Data......................................................................................................................2-10
2.2.4 Planning the Module Number..............................................................................................................2-13
2.3 Planning the Local Office Data.....................................................................................................................2-14
2.3.1 Naming Rules.......................................................................................................................................2-15
2.3.2 Planning the DN Set and Call Source Code Data................................................................................2-19
2.3.3 Planning the Signaling Data.................................................................................................................2-21
2.3.4 Planning the Trunk Data......................................................................................................................2-25
2.3.5 Planning the Prefix - based Routing Data............................................................................................2-31
2.3.6 Planning the Number Analysis Data....................................................................................................2-33
2.3.7 Planning the MGW Data......................................................................................................................2-35
2.3.8 Planning the NGN Device Login Data.................................................................................................2-36
3 Configuring Basic Data............................................................................................................. 3-1

3.1 Configuring Hardware Data............................................................................................................................3-2
3.2 Configuring Local Office Data.......................................................................................................................3-8
3.3 Configuring Charging Data...........................................................................................................................3-17
4 Configuring Data for Subscriber Access Networking........................................................ 4-1

4.1 Configuring Data to Interwork with IAD........................................................................................................4-2
4.1.1 Configuring Data to Interwork with IAD (Through MGCP/H.248)......................................................4-2
4.1.2 Configuring Data to Interwork with IAD (Through H.323)................................................................4-14
4.2 Configuring Data to Interwork with AMG (Through MGCP/H.248)...........................................................4-19
4.3 Configuring Data to Interwork with UMG...................................................................................................4-31
4.3.1 Configuring Data to Interwork with UMG8900 (Connected with RSP Subscriber Frame Device)....4-31
4.3.2 Configuring Data to Interwork with UMG8900 (Connected with V5 AN Device).............................4-36
4.3.3 Configuring Data to Interwork with UMG8900 (Connected with Wireless Access Device)..............4-45
4.4 Configuring Data to Interwork with MTA (Through NCS)..........................................................................4-52
Issue 02 (2010-09-14) Huawei Proprietary and Confidential v

Contents Initial Configuration
5 Configuring Data to Interwork with MRS............................................................................5-1

5.1 Configuring Data to Interwork with Embedded MRS ...................................................................................5-2
5.2 Configuring Data to Interwork with MRS6100.............................................................................................. 5-9
5.3 Configuring Data to Interwork with MRFP6600..........................................................................................5-13
6 Configuring Data to Interwork with Subscriber Terminal...............................................6-1

6.1 Configuring Data to Interwork with SIP Terminal......................................................................................... 6-2
6.2 Configuring Data to Interwork with H.323 Terminal.....................................................................................6-6
6.3 Configuring Data for Controlling the Roaming of Multimedia Terminals (IP)............................................6-10
6.4 Configuring Data to Interwork with Typical Terminals...............................................................................6-13
6.4.1 Configuring Data to Interwork with Pingtel Terminal.........................................................................6-13
6.4.2 Configuring to Interwork with Vizufon 4500 Terminal.......................................................................6-19
6.4.3 Configuring Data to Interwork with ViewPoint 8220 Terminal..........................................................6-21
7 Configuring Subscriber Data...................................................................................................7-1

8 Configuring Data to Interwork with Other Networks.......................................................8-1
8.1 Configuring Data to Interwork with IN...........................................................................................................8-2
8.1.1 Configuring Data to Interwork with SCP (M3UA - MTP)....................................................................8-2
8.1.2 Configuring Data to Interwork with SCP (M3UA - M3UA) ................................................................8-8
8.1.3 Configuring Data to Interwork with SCP (INAP over IP)...................................................................8-13
8.2 Configuring Data to Interwork with PSTN...................................................................................................8-19
8.2.1 Configuring Data to Interwork with PSTN (M2UA - MTP)...............................................................8-20
8.2.2 Configuring Data to Interwork with PSTN (M3UA - MTP)...............................................................8-33
8.3 Configuring Data to Interwork with H.323 Network....................................................................................8-45
8.3.1 Configuring Data to Interwork with H.323 Network (GK - GW)........................................................8-46
8.3.2 Configuring Data to Interwork with H.323 Network (GK - Upper-Level GK)...................................8-51
8.3.3 Configuring Data to Interwork with H.323 Network (GW - Outer GK).............................................8-57
8.4 Configuring Data to Interwork with HFC Network......................................................................................8-63
8.5 Configuring Data to Interwork with Other Softswitches..............................................................................8-67
8.5.1 Configuring Data to Interwork with Other Softswitches (Through SIP Trunk)..................................8-67
8.5.2 Configuring Data to Interwork with Other Softswitches (Through H.323 Trunk)..............................8-71
8.5.3 Configuring Data to Interwork with Other Softswitches (Through Russia CAS)...............................8-75
8.6 Configuring Data to Interwork with IP SMS GW (Through SIP)................................................................8-83
9 Configuring Data to Interwork with Other Service Devices.............................................9-1

9.1 Configuring Data to Interwork with PBX.......................................................................................................9-2
9.1.1 Configuring Data to Interwork with the PBX (Through the PRA Trunk).............................................9-2
9.1.2 Configuring Data to Interwork with the PBX (Through the R2 Trunk)..............................................9-12
9.1.3 Configuring Data to Interwork with PBX (Through the AT0 Trunk)..................................................9-19
9.1.4 Configuring Data to Interwork with the PBX (Through the Loop Trunk) ..........................................9-24
9.1.5 Configuring Data to Interwork with the PBX (Through the SIP Trunk).............................................9-31
9.2 Configuring Data to Interwork with IP U-Path.............................................................................................9-35
9.3 Configuring Data to Interwork with ISDN U-Path.......................................................................................9-43
9.4 Configuring Data to Interwork with the AS (Through SIP)..........................................................................9-49
vi Huawei Proprietary and Confidential Issue 02 (2010-09-14)

9.5 Configuring Data to Interwork with the SHLR.............................................................................................9-53
10 Typical Networking Configuration Examples.................................................................10-1

10.1 Configuring Dual Homing Data (Active/Standby Mode)...........................................................................10-2
10.2 Configuring Dual Homing Data (Load-Sharing Mode)..............................................................................10-6
10.3 Configuring Smart Network Data.............................................................................................................10-35
10.4 Configuring Smart Network Data (with the SCPs Working in the Active/Standby Mode).....................10-44
10.5 Configuring Multi-SPC Network Data.....................................................................................................10-50
10.6 Configuring Multi-Area-Code Data .........................................................................................................10-56
10.7 Configuring MOIP Networking Data........................................................................................................10-60
10.8 Configuring Data for Blended Application of Public and Private Networks............................................10-75
11 Typical Data Configuration Example.................................................................................11-1

11.1 Configuring Charging Data.........................................................................................................................11-2
11.1.1 Configuring Centralized Charging Data............................................................................................11-2
11.1.2 Configuring Distinctive Charging Data.............................................................................................11-4
11.1.3 Configuring Multi-Time-Zone Charging Data...................................................................................11-7
11.1.4 Configuring Called Group Charging Data.........................................................................................11-8
11.1.5 Configuring Third Party Charging Data.............................................................................................11-9
11.1.6 Configuring Centrex Charging Data................................................................................................11-12
11.1.7 Configuring Supplementary Service Charging Data........................................................................11-16
11.1.8 Configuring Instant Charging Data (Charging Rate) ......................................................................11-17
11.1.9 Configuring Instant Charging Data (KC16 Public Telephone) .......................................................11-21
11.1.10 Configuring Instant Charging Data (Polarity Reversal Public Telephone) ...................................11-22
11.1.11 Configuring Instant Charging Data (Trunk Charging Pulse) ........................................................11-23
11.1.12 Configuring CRG Charging Data...................................................................................................11-24
11.1.13 Configuring IN Service Charging Data..........................................................................................11-28
11.2 Configuration Example of Number Analysis Data...................................................................................11-31
11.2.1 Configuring Digitmap Data..............................................................................................................11-31
11.2.2 Configuring Release Mode Data......................................................................................................11-36
11.2.3 Configuring Caller Number Change Data........................................................................................11-37
11.2.4 Configuring Called Number Change Data.......................................................................................11-40
11.2.5 Configuring PBX Pilot Number Change Data.................................................................................11-44
11.2.6 Configuring Special Called Number Change Data..........................................................................11-45
11.2.7 Configuring Caller Number Analysis Data......................................................................................11-46
11.2.8 Prefix Processing Data.....................................................................................................................11-50
11.2.9 Configuring Failure Processing Data...............................................................................................11-55
11.2.10 Configuring Trunk Group Bearer Data..........................................................................................11-65
11.3 Configuration Example of Route Data......................................................................................................11-67
11.3.1 Configuring Load-Sharing Routing Data.........................................................................................11-67
11.3.2 Configuring Alternative Routing Data.............................................................................................11-69
11.3.3 Configuring Dynamic Routing Data................................................................................................11-71
11.3.4 Configuring Route Tree Data...........................................................................................................11-76
11.3.5 Configuring Special Routing Data...................................................................................................11-79
Issue 02 (2010-09-14) Huawei Proprietary and Confidential vii

Contents Initial Configuration
11.3.6 Configuring M3UA Signaling Route Data.......................................................................................11-83

11.3.7 Dual Homing Data of Signaling Link in Priority Routing Mode.....................................................11-87
11.3.8 Super Trunk Routing Data...............................................................................................................11-91
11.4 Trunk Configuration Examples.................................................................................................................11-94
11.4.1 Configuring Single PCM Port to Bear Multiple Trunk Groups (Same Office Direction)...............11-94
11.4.2 Configuring Single PCM Port to Bear Multiple Trunk Groups (Multiple Office Directions).......11-100
11.4.3 Configuring Multiple SIP Trunks Between Two IP Addresses.....................................................11-103
11.4.4 Configuring Trunk-Specified Dialing Test Data............................................................................11-107
11.5 Configuration Example of Call Barring Data.........................................................................................11-114
11.5.1 Configuring Caller Number Discrimination Data..........................................................................11-114
11.5.2 Configuring Inter-Group Call Barring Data...................................................................................11-118
11.5.3 Configuring Black/White List Data...............................................................................................11-120
11.5.4 Configuring Called Number Barring Group Data..........................................................................11-121
11.5.5 Configuring Time-based Call Barring Data...................................................................................11-123
11.5.6 Configuring Nested Dialing Data...................................................................................................11-124
11.5.7 Configuring IGC Call Barring Data...............................................................................................11-125
11.5.8 Configuring Barring on a Certain Proportion of Calls Destined to a Specified Prefix over the Designated
Trunk.........................................................................................................................................................11-126
11.5.9 Configuring Call Congestion Barring Data....................................................................................11-127
11.6 Configuration Example of Network Management Data..........................................................................11-128
11.6.1 Configuring Network Management Instruction Data.....................................................................11-129
11.6.2 Configuring Low Level Call Gapping Control..............................................................................11-130
11.6.3 Configuring NTP Client Data........................................................................................................11-131
11.7 Configuration Example of Equal Access Data........................................................................................11-131
11.8 Configuration Example of Remote Network Access Data......................................................................11-133
12 Relations Between Database Tables...................................................................................12-1

12.1 Relations Between Hardware Data Tables..................................................................................................12-2
12.2 Relations Between Local Office Data Tables.............................................................................................12-2
12.3 Relations Between Subscriber Data Tables.................................................................................................12-3
12.4 Relations Between Number Analysis Data Tables......................................................................................12-4
12.5 Relations Between Billing Data Tables......................................................................................................12-5
12.6 Relations Between Signaling Data Tables..................................................................................................12-6
12.6.1 Relations Between M2UA Signaling Data Tables.............................................................................12-6
12.6.2 Relations Between M3UA Signaling Data Tables.............................................................................12-7
12.6.3 Relations Between V5UA Signaling Data Tables..............................................................................12-8
12.6.4 Relations Between IUA Signaling Data Tables.................................................................................12-9
12.6.5 Relations Between MTP Signaling Data Tables..............................................................................12-10
12.6.6 Relations Between SCCP Signaling Data Tables............................................................................12-11
12.6.7 Relations Between V5 Signaling Data Tables.................................................................................12-12
12.6.8 Relations Between PRA Signaling Data Tables..............................................................................12-13
12.6.9 Relations Between COPS Signaling Data Tables............................................................................12-14
12.7 Relations Between Route Data Tables......................................................................................................12-15
viii Huawei Proprietary and Confidential Issue 02 (2010-09-14)

12.8 Relations Between Trunk Circuit Data Tables..........................................................................................12-16

12.8.1 Relations Between N0.7 Trunk Circuit Data Tables........................................................................12-17
12.8.2 Relations Between R2 Trunk Circuit Data Tables...........................................................................12-17
12.8.3 Relations Between PRA Trunk Circuit Data Tables........................................................................12-18
12.8.4 Relations Between AT0 Trunk Circuit Data Tables........................................................................12-19
12.8.5 Relations Between V5 Trunk Circuit Data Tables...........................................................................12-19
Issue 02 (2010-09-14) Huawei Proprietary and Confidential ix

Initial Configuration Figures
Figures
Figure 1-1 Data configuration procedure.............................................................................................................1-1

Figure 3-1 Board configuration in the basic subrack........................................................................................... 3-3
Figure 3-2 Typical configuration of boards in the expansion subrack.................................................................3-3
Figure 4-1 IAD adopting MGCP/H.248 to interwork with the SoftX3000..........................................................4-2
Figure 4-2 IAD adopting H.323 to interwork with the SoftX3000 ...................................................................4-14
Figure 4-3 AMG adopting MGCP/H.248 to interwork with the SoftX3000 ....................................................4-20
Figure 4-4 UMG8900 (connected with the RSP subscriber frame device) acting as an AMG..........................4-32
Figure 4-5 UMG8900 (connected with the V5 AN device) acting as an AMG.................................................4-37
Figure 4-6 UMG8900 (connected with the wireless access device) acting as an AMG....................................4-45
Figure 4-7 MTA adopting NCS to interwork with the SoftX3000....................................................................4-52
Figure 5-1 Configuration of an embedded MRS..................................................................................................5-2
Figure 5-2 Typical networking model for the SoftX3000 to interwork with the MRS6100................................5-9
Figure 5-3 Typical networking model for the SoftX3000 to interwork with the MRFP6600...........................5-14
Figure 6-1 Typical networking model for SIP terminals interworking with the SoftX3000............................... 6-2
Figure 6-2 Typical networking model for H.323 terminals interworking with the SoftX3000...........................6-6
Figure 6-3 Typical networking for roaming of multimedia terminals...............................................................6-10
Figure 6-4 Phone information configuration interface.......................................................................................6-16
Figure 6-5 Configuring the phone number length..............................................................................................6-16
Figure 6-6 Configuring SIP data........................................................................................................................6-17
Figure 6-7 Configuring authentication data.......................................................................................................6-18
Figure 6-8 SIP-URL configuration interface......................................................................................................6-18
Figure 6-9 Configuring SIP-URL information...................................................................................................6-19
Figure 6-10 Operation panel of the ViewPoint 8220.........................................................................................6-23
Figure 6-11 Network interface...........................................................................................................................6-23
Figure 6-12 User interface..................................................................................................................................6-24
Figure 8-1 Typical networking model for the SoftX3000 to interwork with the SCP (M3UA - MTP) ............. 8-2
Figure 8-2 Typical networking model for the SoftX3000 to interwork with the SCP (M3UA - M3UA) .......... 8-8
Figure 8-3 Typical networking model for the SoftX3000 to interwork with the SCP/SMCP (INAP over IP)
.............................................................................................................................................................................8-13
Figure 8-4 Typical networking model for the SoftX3000 to interwork with the PSTN (M2UA - MTP) .........8-20
Figure 8-5 Typical networking model for the SoftX3000 to interwork with the PSTN (M3UA - MTP) .........8-34
Figure 8-6 Typical networking model for the SoftX3000 to interwork with an H.323 network (GK - GW)
.............................................................................................................................................................................8-46
Issue 02 (2010-09-14) Huawei Proprietary and Confidential xi

Figures Initial Configuration
Figure 8-7 Typical networking model for the SoftX3000 to interwork with an H.323 network (GK - upper-level
GK) .....................................................................................................................................................................8-51
Figure 8-8 Typical networking model for the SoftX3000 to interwork with an H.323 network (GW - outer GK)
.............................................................................................................................................................................8-58
Figure 8-9 Typical networking model for the SoftX3000 to interwork with the HFC......................................8-63
Figure 8-10 Typical networking model for the SoftX3000 to interwork with other softswitch (through SIP trunk)
.............................................................................................................................................................................8-68
Figure 8-11 Typical networking model for the SoftX3000 to interwork with other softswitch (through H.323 trunk)
.............................................................................................................................................................................8-72
Figure 8-12 Typical networking model for the SoftX3000 to interwork with another softswitch (through Russia
CAS) ...................................................................................................................................................................8-76
Figure 8-13 Typical networking model for the SoftX3000 to interwork with the IP SMS GW (through SIP)
.............................................................................................................................................................................8-84
Figure 9-1 Typical networking model for the SoftX3000 to interwork with the PBX (through PRA) ..............9-2
Figure 9-2 Typical networking model for the SoftX3000 to interwork with the PBX (through the R2 trunk)
.............................................................................................................................................................................9-12
Figure 9-3 Typical networking model for the SoftX3000 to interwork with the PBX (through the AT0 trunk)
.............................................................................................................................................................................9-19
Figure 9-4 Typical networking model for the SoftX3000 to interwork with the PBX (through the loop trunk)
.............................................................................................................................................................................9-25
Figure 9-5 Typical networking model for the SoftX3000 to interwork with the PBX (through the SIP trunk)
.............................................................................................................................................................................9-31
Figure 9-6 Typical networking model for the IP U-Path interworking with the SoftX3000 ............................9-36
Figure 9-7 Typical networking model for the ISDN U-Path interworking with the SoftX3000......................9-43
Figure 9-8 Typical networking model for the SoftX3000 to interwork with the AS (through SIP) .................9-49
Figure 9-9 Typical networking model for the SoftX3000 to interwork with the SHLR....................................9-53
Figure 10-1 Networking diagram of the dynamic dual homing solution in active/standby mode.....................10-2
Figure 10-2 Networking diagram of the dynamic dual homing solution in load sharing mode........................10-6
Figure 10-3 Networking for the smart network solution..................................................................................10-36
Figure 10-4 Networking for the smart network solution..................................................................................10-45
Figure 10-5 Networking in which the SoftX3000 acts as the gateway office .................................................10-50
Figure 10-6 Networking for multi-area-code application of the SoftX3000....................................................10-56
Figure 10-7 Relation among the call source, local DN set and global DN set ................................................10-60
Figure 10-8 MOIP networking model..............................................................................................................10-61
Figure 10-9 SoftX3000 equipment configuration (basic frame)......................................................................10-62
Figure 10-10 Networking for the blended application of public and private networks in the SoftX3000.......10-76
Figure 11-1 Network of the CRG charging......................................................................................................11-25
Figure 11-2 Networking of the application scenario........................................................................................11-54
Figure 11-3 Typical networking where SoftX3000 A functions as a tandem office........................................11-63
Figure 11-4 Structure of the route tree.............................................................................................................11-63
Figure 11-5 Networking model of a local network (1).....................................................................................11-68
Figure 11-6 Networking model of a local network (2).....................................................................................11-69
Figure 11-7 Networking model of a local network..........................................................................................11-72
Figure 11-8 Networking model of a local network..........................................................................................11-74
Figure 11-9 Route tree planning.......................................................................................................................11-76
xii Huawei Proprietary and Confidential Issue 02 (2010-09-14)

Initial Configuration Figures
Figure 11-10 Route tree planning.....................................................................................................................11-77

Figure 11-11 Routes for outgoing toll calls originated from end office A.......................................................11-80
Figure 11-12 Route for toll calls from toll office C to end office A................................................................11-82
Figure 11-13 Signaling networking model of a local network (1)...................................................................11-84
Figure 11-14 Signaling networking model of a local network (2)...................................................................11-85
Figure 11-15 Networking model of the priority routing mode........................................................................11-88
Figure 11-16 Networking when the super trunk is used..................................................................................11-92
Figure 11-17 Typical networking when a single PCM port bears multiple trunk groups (same office direction)
...........................................................................................................................................................................11-95
Figure 11-18 Typical networking when configuring a single PCM port to bear multiple trunk groups (multiple
office directions).............................................................................................................................................11-101
Figure 11-19 Network on which multiple SIP trunks are configured between two IP addresses..................11-103
Figure 11-20 Networking model when the SoftX3000 acts as a gateway office...........................................11-119
Figure 11-21 Typical networking of the SoftX3000 trunk nested dialing feature ........................................11-125
Figure 11-22 Typical networking of the SoftX3000 call barring feature ......................................................11-126
Figure 11-23 Typical networking of barring on a certain proportion of calls destined to a specified prefix over the
designated trunk on the SoftX3000 ................................................................................................................11-127
Figure 11-24 Network of the equal access service.........................................................................................11-132
Figure 11-25 Network of remote network access service in IN mode...........................................................11-134
Figure 12-1 Relations between hardware data tables ........................................................................................12-2
Figure 12-2 Relations between local office data tables......................................................................................12-3
Figure 12-3 Relations between subscriber data tables.......................................................................................12-4
Figure 12-4 Relations between number analysis data tables..............................................................................12-5
Figure 12-5 Relations between billing data tables.............................................................................................12-6
Figure 12-6 Relations between M2UA signaling data tables.............................................................................12-7
Figure 12-7 Relations between M3UA signaling data tables.............................................................................12-8
Figure 12-8 Relations between V5UA signaling data tables..............................................................................12-9
Figure 12-9 Relations between IUA signaling data tables...............................................................................12-10
Figure 12-10 Relations between MTP signaling data tables............................................................................12-11
Figure 12-11 Relations between SCCP signaling data tables..........................................................................12-12
Figure 12-12 Relations between V5 signaling data tables...............................................................................12-13
Figure 12-13 Relations between PRA signaling data tables............................................................................12-14
Figure 12-14 Relations between COPS signaling data tables..........................................................................12-15
Figure 12-15 Relations between route data tables............................................................................................12-16
Figure 12-16 Relations between N0.7 trunk circuit data tables.......................................................................12-17
Figure 12-17 Relations between R2 trunk circuit data tables...........................................................................12-18
Figure 12-18 Relations between PRA trunk circuit data tables.......................................................................12-18
Figure 12-19 Relations between AT0 trunk circuit data tables........................................................................12-19
Figure 12-20 Relations between V5 trunk circuit data tables..........................................................................12-19
Issue 02 (2010-09-14) Huawei Proprietary and Confidential xiii

Initial Configuration Tables
Tables
Table 2-1 Local IP address of the NGN device on the bearer network................................................................2-2
Table 2-2 Bearer network IP addresses required by UMG8900...........................................................................2-4
Table 2-3 IP address required by the MediaX3600 server ..................................................................................2-5
Table 2-4 Maintenance network IP address required by the remote end.............................................................2-7
Table 2-5 Cabinet data planning principle...........................................................................................................2-8
Table 2-6 Subrack data planning principle...........................................................................................................2-9
Table 2-7 Board data planning principle............................................................................................................2-12
Table 2-8 Module number planning principle....................................................................................................2-14
Table 2-9 Signaling data of the Local Office.....................................................................................................2-21
Table 2-10 SCTP port number allocation principles..........................................................................................2-23
Table 2-11 Link data plan...................................................................................................................................2-23
Table 2-12 Trunk data numbering plan..............................................................................................................2-25
Table 2-13 Prefix, route selection and route numbering table............................................................................2-28
Table 2-14 Trunk data planning table.................................................................................................................2-30
Table 2-15 MGW description.............................................................................................................................2-35
Table 3-1 Information to be collected before configuring the hardware data......................................................3-2
Table 3-2 Basic information about key boards in the basic subrack....................................................................3-4
Table 3-3 Basic information of key boards in the expansion subrack..................................................................3-4
Table 3-4 Data to be collected before configuring the local office data..............................................................3-9
Table 3-5 Basic charging data............................................................................................................................3-18
Table 3-6 Additional charging data (optional)...................................................................................................3-21
Table 4-1 Data to be collected before configuring the data between the SoftX3000 and the IAD......................4-3
Table 4-2 Data to be collected before configuring the data between the SoftX3000 and the IAD....................4-15
Table 4-3 Data to be collected before configuring the data between the SoftX3000 and the AMG..................4-20
Table 4-4 Data to be collected before configuring the data between the SoftX3000 and the UMG8900..........4-32
Table 4-6 Data to be collected before configuring the data between the SoftX3000 and the V5 AN device....4-42
Table 4-8 Data to be collected before configuring the data between the SoftX3000 and the wireless access device
.............................................................................................................................................................................4-49
Table 4-9 Data to be collected before configuring the data between the SoftX3000 and the MTA..................4-53
Table 5-1 Data to be collected before configuring the data between the SoftX3000 and the embedded MRS
...............................................................................................................................................................................5-2
Table 5-2 Data to be collected before configuring the data between the SoftX3000 and the MRS6100.............5-9
Issue 02 (2010-09-14) Huawei Proprietary and Confidential xv

Tables Initial Configuration
Table 5-3 Data to be collected before configuring the data between the SoftX3000 and the MRFP6600........ 5-15
Table 6-1 Data to be collected before configuring the data between the SoftX3000 and the SIP terminals.......6-3
Table 6-2 Data to be collected before configuring the data between the SoftX3000 and the H.323 terminals
...............................................................................................................................................................................6-7
Table 6-3 Data to be negotiated before configuring data on the SoftX3000......................................................6-11
Table 6-4 Data to be collected before configuring the data between the SoftX3000 and the Pingtel terminal
.............................................................................................................................................................................6-14
Table 6-5 Data to be collected before configuring the data between the SoftX3000 and the Vizufon 4500 terminals
.............................................................................................................................................................................6-20
Table 6-6 Data to be collected before configuring the data between the SoftX3000 and the ViewPoint 8220
terminals..............................................................................................................................................................6-22
Table 7-1 Data for voice service subscribers........................................................................................................7-1
Table 7-2 Data of multimedia service subscribers...............................................................................................7-2
Table 7-3 Data for wide area Centrex subscribers................................................................................................7-3
Table 7-4 Data for BRA subscribers....................................................................................................................7-3
Table 7-5 Data for PRA subscribers.....................................................................................................................7-4
Table 8-1 Data for signaling interaction between the SoftX3000 and the SG7000.............................................8-3
Table 8-2 Data for signaling interaction between the SoftX3000 and the SCP...................................................8-5
Table 8-3 Data for signaling interaction between the SoftX3000 and the SCP...................................................8-9
Table 8-4 Data for signaling interaction between the SoftX3000 and the SCP................................................. 8-14
Table 8-5 Data for interworking between the SoftX3000 and the UMG8900...................................................8-21
Table 8-6 Data for interworking between the SoftX3000 and the PSTN switch............................................... 8-27
Table 8-8 Data for interworking between the SoftX3000 and the SG7000....................................................... 8-37
Table 8-9 Data for interworking between the SoftX3000 and the PSTN switch............................................... 8-39
Table 8-10 Data for interworking between the SoftX3000 and the A8010 Expert............................................8-47
Table 8-11 Data for interworking between the SoftX3000 and the A8010 Expert............................................8-52
Table 8-12 Data for interworking between the SoftX3000 and the outer GK....................................................8-58
Table 8-13 Data for interworking between the SoftX3000 and the CMTS........................................................8-64
Table 8-14 Data for interworking between the SoftX3000 and the EMTA.......................................................8-65
Table 8-15 Data for interworking between the SoftX3000 and other softswitches (through SIP trunk)...........8-68
Table 8-16 Data for interworking between the SoftX3000 and other softswitches (through H.323 trunk).......8-72
Table 8-17 Data for interworking between the SoftX3000 and other softswitches (through Russia CAS).......8-77
Table 8-18 Data for interworking between the SoftX3000 and the IP SMS GW (through SIP)....................... 8-85
Table 9-1 Data for interworking between the SoftX3000 and the UMG8900.....................................................9-3
Table 9-2 Data for interworking between the SoftX3000 and the PBX...............................................................9-6
Table 9-4 Data for interworking between the SoftX3000 and the PBX.............................................................9-16
Table 9-9 Data for interworking between the SoftX3000 and the PBX through the SIP trunk.........................9-32
xvi Huawei Proprietary and Confidential Issue 02 (2010-09-14)

Initial Configuration Tables
Table 9-10 Data for interworking between the SoftX3000 and the IP U-Path...................................................9-36
Table 9-11 Data for interworking between the SoftX3000 and the AMG.........................................................9-37
Table 9-12 Data for interworking between the SoftX3000 and the ISDN U-Path.............................................9-44
Table 9-13 Data for interworking between the SoftX3000 and the AS through SIP.........................................9-50
Table 9-14 Data for interworking between the SoftX3000 and the SHLR........................................................9-54
Table 10-1 Dual homing data to be planned.......................................................................................................10-3
Table 10-2 Principles for configuring the dual homing data..............................................................................10-8
Table 10-3 Data for interworking between the SoftX3000 and the SCP.........................................................10-37
Table 10-4 Data for interworking between the SoftX3000 and the SHLR......................................................10-37
Table 10-5 Data for interworking between the SoftX3000 and the SCP.........................................................10-46
Table 10-6 Basic data of the multi-SPC function.............................................................................................10-51
Table 10-7 Basic data of the multi-area-code function....................................................................................10-57
Table 10-8 Basic information of major boards.................................................................................................10-62
Table 10-9 Data for interworking between the SoftX3000 and the UMG8900...............................................10-63
Table 10-10 Data for interworking between the SoftX3000 and the PSTN switch.........................................10-64
Table 10-11 Data for interworking between the SoftX3000 and the MRS6100..............................................10-65
Table 10-12 Data for interworking between the SoftX3000 and the CRBT server.........................................10-65
Table 10-13 Data need to be planned for the blended application of public and private networks.................10-77
Table 11-1 Charging strategies for supplementary services.............................................................................11-16
Table 11-2 Charging requirements...................................................................................................................11-18
Table 11-3 Data to be planned before configuring the IN service...................................................................11-29
Table 11-4 Digitmap configuration requirements............................................................................................11-31
Table 11-5 Plan for selecting routes from end office A to end office B..........................................................11-72
Table 11-6 Plan for selecting routes from end office A to end office B..........................................................11-74
Table 11-7 Description of route tree planning..................................................................................................11-77
Table 11-8 Data planning.................................................................................................................................11-92
Table 11-9 Inter-group barring relationship...................................................................................................11-118
Table 11-10 Inter-group barring relationship.................................................................................................11-121
Table 11-11 Call barring based on CPU overload levels and call priorities..................................................11-128
Issue 02 (2010-09-14) Huawei Proprietary and Confidential xvii

Initial Configuration 1 Data Configuration Procedure
1 Data Configuration Procedure
Context
During office deployment, data planning and configuration need to be performed according to
the procedure shown in Figure 1-1.
Figure 1-1 Data configuration procedure

Configure Configure
Start Plan data End
basic data interworking data
Plan the IP Configure data for

Configure interworking with
address of the
bearer subnet hardware data the access
equipment
Plan hardware Configure local Configure data for

interworking with
data office data the MRS
Plan local Configure Configure data for

interworking with
office data charging data the terminal
Configure
subscriber data
Configure data for

interworking with
other networks
Configure data for

interworking with
other service
devices
Issue 02 (2010-09-14) Huawei Proprietary and Confidential 1-1

1 Data Configuration Procedure Initial Configuration
1-2 Huawei Proprietary and Confidential Issue 02 (2010-09-14)

Initial Configuration 2 Planning Data
2 Planning Data
About This Chapter
2.1 Planning the Bearer Network IP Address

2.2 Planning the Equipment Data
2.3 Planning the Local Office Data

2 Planning Data Initial Configuration
2.1 Planning the Bearer Network IP Address

In the deployment process, you should have an overall understanding of the data of the NGN
offices. The aspects that require your attention are as follows:
l The home networks of the devices such as IP public network, VPN service network, and
DCN maintenance network.
l The IP addresses of the devices, MGW IP address, and IP address discarded during the
allocation of subnets.
l Fixed IP addresses of the devices. The combination of the IP public network and VPN
service network is the recommended networking mode because a large number of IP
addresses can be saved.
NOTE
l Key devices must use the public network IP addresses. For example, public network IP addresses
can be used on the private VPN service network devices for saving capacity for further expansion.
l Terminals such as the IAD use the private network IP addresses.
For facilitating the IP address segment allocation, the NGN devices on the bearer network can
be divided into local end devices and remote end devices.
l Local end device

SoftX3000, TMG8010, and AMG5000
l Remote end device
– AG (UMG8900 and IAD)
– TG (UMG8900 and TMG8010)
– H.323 and SIP terminals (OpenEye, MediaX3600, and ViewPoint 8220)
– Remote maintenance terminal (EWS and WS)
IP Address Planning Principle for the Local End Device
Table 2-1 Local IP address of the NGN device on the bearer network
Device Planning Principle
SoftX3000 A pair of IFMIs working in active/standby mode require an IP address.
TMG8010 A TMG8010 requires an IP address.
AMG5000 An AMG5000 requires an IP address.
UA5000 Each UA5000 requires one IP address for the narrowband applications
and another IP address for the broadband applications.
NOTE
On the NGN network, the UA5000 usually serves as an AG, that is, a narrowband
device.
Embedded MRS An MRP subboard of the MRI requires an IP address. An MRI has two
MRP subboards. Therefore, an MRI requires two IP addresses.

MRS6100 l For signaling: A pair of MCCUs working in active/standby mode

require an IP address.
l For media: An MRP subboard of the MSU requires an IP address.
An MSU has two MRP subboards. Therefore, an MSU requires two
IP addresses.
l An EAI of the VPS requires an IP address.
SG7000 A pair of SBPIs working in active/standby mode require an IP address.

A VIEB requires an FE interface.
N2000 UMS A N2000 UMS requires an IP address for managing the devices on the
bearer network and managing the inband network signaling.
SBC A Eudemon2000 SBC requires an IP address on each interface. Note

the network connected with each interface.
Firewall When adopting the route mode, the Eudemon firewall uses one IP
address for each interface. When adopting the transparent mode, the
Eudemon firewall does not need any IP address.
RM9000 A RM9000 requires an IP address. The BNI of the NPB provides an FE

port to connect to the network.
IADMS The IP address requirement is the same as that for the N2000 UMS. If
IADMS and N2000 UMS are installed on the same server, no additional
IP address needs to be prepared.
U-NICA The TELLIN U-NICA requires four fixed IP addresses and four floating
IP addresses.
l Each node of the dual systems requires a fixed IP address.
l The TC requires a fixed IP address.
l The WS requires a fixed IP address.
l The AS, SMS server, WWW server, and Database server require
four floating IP addresses.
UC The number of IP addresses occupied by the UC is related to the

composition of the server group. Usually, 2 to 4 bearer network IP
addresses are required.
SHLR One pair of SBPIs of SHLR9200 working in active/standby mode

requires an IP address. When the device needs to provide the 3G HLR
or PHS HLR function, it needs to be configured with the SDUI and one
IP address. The back interface board is VIEB, which provides one FE
interface.
SCP An SCP requires an IP address.
SAU A USAU requires an IP address.
SMC A ViewPoint MediaCentre SMC requires an IP address.

MCU A ViewPoint MediaCentre MCU requires two IP addresses, one for

signaling and the other for media.
IAD An IAD requires an IP address. It can support DHCP. The IAD116E of

Huawei does not support PPPoE.
Terminal phone set One packet terminal (H.323 and SIP) requires an IP address. It can
support DHCP. H323IAD is also included.
U-Path&Console One U-Path&Console requires one IP address.
IP Address Planning for the Remote End Devices

The UMG8900 has the following requirements on the IP address:
l The priority level of the local office (host office) is: partly central forwarding -> non-central
forwarding -> central forwarding.
l The priority level of the end office (non-host office) application is: partly central forwarding
-> central forwarding -> non-central forwarding.
The above is the principle for the large-capacity UMG8900. The principle for the small-capacity
UMG8900 is similar to that of the large-capacity UMG8900. When SIGTRAN signaling is
transmitted through the MIR port and the OMU NM data is transmitted through the OMC port,
the two ports should be connected to different VLANs of the LAN Switch and the IP addresses
must be in different network segments.
Table 2-2 Bearer network IP addresses required by UMG8900

Networking
Type Planning Principle
Single-subrack Only the FG1O is configured on the large-capacity UMG8900.

system l Maintenance is implemented through the OMC port on the back
board FNET of the FOMU.
l Signaling and media are transmitted through the GE port on the back
board FG1O of the FHRU.
Configure the FE8T board or the subboard for the large-capacity

UMG8900 and medium-capacity UMG8900.
l Maintenance is implemented through the OMC port on the FOMU/
FOMB.
l Media is transmitted through the GE port on the FHRU/FHRC or
one or multiple FE ports on the FHRU/FHRC.
l Signaling is transmitted through the Ethernet port on the FHRU/
FHRC. The signaling and bearer network interfaces use different FE
ports. H.248 and SIGTRAN signaling can use the same FE port or
multiple FE ports.

Networking
Type Planning Principle
Other conditions
l When the traffic of the large-capacity UMG8900 is low,
maintenance is implemented and signaling is transmitted through
the OMC port on the FNET.
l When the traffic of the large-capacity UMG8900 is heavy,
maintenance is implemented through the OMC port on the FNET.
IP addresses can be configured on the interfaces of the PPU. UA
signaling can also be transmitted through the interface of the SPF,
namely, the MIR interface of the FNET.
l For the medium-capacity UMG8900, maintenance is implemented
through the OMC interface on the FTNC, and signaling is
transmitted through the MC interface on the FTNC.
l For the mini-UMG8900, set modes of centralized forwarding
(convergence, dichotomy, and trisection) according to the actual
conditions. Different modes determine the interface for transmitting
signaling.
– Convergence indicates that signaling, bearer and maintenance
messages are transmitted through the bearer interface on the
VPD.
– Dichotomy indicates that bearer and maintenance messages are
transmitted through the OMC interface.
– Trisection indicates that maintenance messages are transmitted
through the debugging interface on the VPD.
Multi-subrack You can perform central forwarding by using the FMPU/FMPB in the
system central switching subrack. That is, the cable outlet is the OMC port of
the back board FNET of the FMPU or the OMC port of the back board
FTNC of the FMPB.
l Maintenance is implemented through the OMC port on the back
board FNET of the FOMU.
l Media is transmitted through the GE port on the FHRU/FHRC or
one or multiple FE ports on the FHRU/FHRC.
l Signaling is transmitted through the OMC port on the back board
FNET of the FMPU or the MC port on the FTNC.
Table 2-3 IP address required by the MediaX3600 server

Virtual IP Intra-Group IP
Host Name Address Address Planning Principle
media1 media1_web Media1_web_test Seven IP addresses are required.

0
media2 media2_web Media1_web_test

1

Virtual IP Intra-Group IP
Host Name Address Address Planning Principle
Media2_web_test NOTE
0 Note that the IP addresses must be public
network IP addresses in the same
Media2_web_test network segment. The MediaX3600
provides the web access through the
1 ipmp_web address. If the public network
IP addresses are limited, private network
IP addresses can be used. At that time,
only three public network IP addresses
need to be used (the firewall is set to the
NAT mode and occupies two IP
addresses; the WEB occupies one IP
address).
media1 media1_sip Media1_sip_test0 Seven IP addresses are required.

NOTE
Media1_sip_test1 Note that the IP addresses must be in the
same network segment of the original
media2 media2_sip Media2_sip_test0 NGN signaling network. The
MediaX3000 interworks SIP signaling
Media2_sip_test1 with the SoftX3000 through the
ipmp_sip address.
media1 media1_alarm Media1_alarm_te Seven IP addresses are required.

st0 NOTE
Note that the IP addresses must be in the
Media1_alarm_te same network segment of the original
st1 NGN NM network. The MediaX3000
communicates with the NM platform
media2 media2_alarm Media2_alarm_te through the ipmp_alarm address.
st0
Media2_alarm_te
st1
media1 media1_igwb Media1_igwb_tes Because there is only one iGWB

t0 server, one IP address of charging
network segment is required.
media2 media2_igwb Media1_igwb_tes
NOTE
t1 Note that seven private network IP
addresses in the same user-defined
Media2_igwb_tes network segment can be used as the
t0 communication addresses between the
MediaX server and the iGWB. To
Media2_igwb_tes standardize data setting, it is
t1 recommended that you can apply for the
charging network segment address of the
original NGN.
The maintenance network IP address needs to be provided for the BAM of SoftX3000, BAM of
SG7000, BAM of SHLR9200 BAM of USAU, BAM of UMG8900, BAM of MRS6100, N2000
UMS, IADMS, WS, iGWB, and EWS.

Table 2-4 Maintenance network IP address required by the remote end

SoftX3000 The BAM of the SoftX3000 requires an IP address.
iGWB One set of iGWBs (active and standby) usually require an IP address that is
used to connect to the WS.
One set of iGWBs (active and standby) usually require two IP addresses that
are used to connect to the billing center.
SG7000 The BAM of the SG7000 requires an IP address.
SHLR9200 l Stand-alone server: The BAM of the SHLR9200 requires an IP address.

l Dual-node system: The BAM of the SHLR9200 requires four IP
addresses.
USAU The BAM of the USAU requires an IP address.
MRS6100 The EAM (BAM) of the MRS6100 requires an IP address.
UMG8900 The OMU (BAM) of the UMG8900 requires an IP address.
N2000 UMS An N2000 UMS requires an IP address.
IADMS An IADMS requires an IP address.

NOTE
If the IADMS and the N2000 UMS are installed on the same server, no additional IP
address needs to be prepared.
EWS An EWS requires an IP address.
WS A WS requires an IP address.
UC The number of IP addresses occupied by the UC is related to the composition

of the server group. Usually, 2 to 4 maintenance network IP addresses are
required.
RM9000 A RM9000 requires an IP address.

NOTE
There is one FE port for each back board (BSI board) of the SYS board. This can meet
the networking requirement of the network management.
2.2 Planning the Equipment Data
2.2.1 Planning the Cabinet Data

2.2.2 Planning the Subrack Data
2.2.3 Planning the Board Data
2.2.4 Planning the Module Number

2.2.1 Planning the Cabinet Data

The SoftX3000 can be installed with up to 10 racks numbered from 0 to 9. If each rack is in full
configuration, five racks are sufficient to provide the maximum system capacity.
Cabinet data planning principle
Racks of the same SoftX3000 observe the same numbering scheme. The rack where the
integrated configuration cabinet resides is constantly numbered 0. Other racks are numbered in
sequence (from left to right or from right to left).
Table 2-5 Cabinet data planning principle

Data Planning Principle MML Commands
Shelf number It uniquely identifies a rack. ADD SHF

Racks of the same SoftX3000
observe the same numbering
scheme. A maximum of 10
racks, ranging from 0 to 9,
can be configured for a
SoftX3000.
Row number It specifies the position of the ADD SHF

rack in the telecommunica-
Column number tions room.
PDB location It specifies the location ADD SHF

number of the subrack, which
contains the SMUI
monitoring the power
distribution box (PDB) in the
rack. The value ranges from
0 to 3. The default value is 2.
Physically, the subrack that
manages the PDB is the one
containing the SIUI. The
setting of this parameter must
be consistent with the actual
cable connection. Otherwise,
the PDB status will not be
correctly reported. PDB
location is set to 2 for the
integrated configuration
cabinet and value 0 for the
service processing cabinet.

PDB type It specifies whether the -48 V ADD SHF

DC input power or -60 V DC
input power is used to run the
PDB in the rack. The default
value is -48V. This parameter
indirectly defines the
overvoltage or undervoltage
alarm threshold for the PDB.
NOTE
When the SoftX3000 is used in
Russia and former AIS
countries, it is set to -60V
according to the requirement.
2.2.2 Planning the Subrack Data

A maximum of 18 Open Standards Telecom Architecture (OSTA) Platform subracks can be
configured for the SoftX3000. The subracks are numbered 0 to 17.
Subrack data planning principle
Subracks of the same SoftX3000 observe the same numbering scheme.
l The subracks are numbered from the bottom to the top in a rack.
l The subracks in different racks are numbered in ascending order of the rack numbers.
Table 2-6 Subrack data planning principle

Subrack number It uniquely identifies a ADD FRM

subrack. Subracks of the
same SoftX3000 observe the
same numbering scheme.
Numbers 0 and 5 are
allocated to the basic
subrack. Other numbers are
allocated to expansion
subracks.
The subrack number is
determined by the 8-digit
DIP switch S3 on the SIUI.
The subrack number
configured in the database
must be the same as that
determined by the DIP switch
S3.

Location number The location number ADD FRM

identifies the position of a
subrack in a rack. A
maximum of four subracks
can be configured in each
rack and are numbered from
0 to 3 in a rack from the
bottom to the top.
In the integrated
configuration cabinet (in rack
0), location numbers of the
BAM and iGWB are
constantly set to 0 and 1
respectively. Therefore, the
location numbers of subracks
in the integrated
configuration cabinet can
only be 2 and 3. Otherwise,
the subrack status cannot be
displayed on the BAM.
The subrack numbers of the
service processing cabinet
can be configured based on
the actual situation.
2.2.3 Planning the Board Data

The hardware structure of all the subracks of the SoftX3000 is the same. The SoftX3000 boards
are divided into front boards and back boards based on their plug-in direction. There are 21 slots,
both in the front and at the back of the subrack, numbering from 0 to 20.
Type Position Mandatory or Full Remarks

Optional Configuration
(Pairs)
FCCU Front Mandatory 40 -
IFMI Front Mandatory 4 -
SMUI Front Mandatory - Configured

according to the
default
configuration in
each subrack.

Type Position Mandatory or Full Remarks

Optional Configuration
(Pairs)
MRCA Front Optional - Configured

when the
MRCA board
functions as an
independent
media resource
server.
BSGI Front Optional - Configured

according to the
carrier's
requirements.
MSGI Front Optional - Configured

according to the
carrier's
requirements.
CDBI Front Mandatory 2 -
ALUI Front Mandatory - Configured

according to the
default
configuration in
each subrack.
BFII Back Mandatory - Back board of

the IFMI board
SIUI Back Mandatory - Back board of

the SMUI board
MRIA Back Optional - Configured

when the
MRCA board
functions as an
independent
media resource
server.
HSCI Back Mandatory - Configured

according to the
default
configuration in
each subrack.
UPWR Front and back Mandatory - Configured

according to the
default
configuration in
each subrack.

Board data planning principle

l The front boards are numbered in sequence from left to right.
l The back boards are numbered from right to left so that the front and back boards are
numbered consistently.
Table 2-7 Board data planning principle

Slot number It specifies the number of the ADD BRD

slot in which the board is
located. The configuration of
slots must comply with the
corresponding standard.
Extra boards must be
removed.
l Slots 6 through 9 and 16
through 20 are constantly
for the SMUI, SIUI,
HSCI, ALUI, and UPWR
boards.
l The active/standby
boards are located in
adjacent slots. The active
boards occupy the even
slots and the standby
boards occupy the odd
slots. The active/standby
slots are 0/1, 2/3, 4/5, 6/8,
10/11, 12/13, and 14/15.
l The BFII is unnecessarily
configured separately.
When you add the IFMI,
the system automatically
adds the BFII in the same
slot of the back half
subrack.
l The MRIA is
unnecessarily configured
separately. When you add
the MRCA, the system
automatically adds the
MRIA in the same slot of
the back half subrack.

Assistant slot number For the boards working in ADD BRD

active/standby mode, this
parameter is used to specify
the slot number of the
standby board. If this
parameter is set to 255, it
means that the board works in
non active/standby mode.
That is, no standby board is
required.
l The FCCUs, MSGIs,
IFMIs, and CDBIs are
configured in active/
standby mode. Each pair
of active/standby boards
are allocated with a
module number.
l The BSGIs are configured
in load balancing mode.
Each BSGI is allocated
with a module number.
The slot number of the
standby BSGI is set to
255.
l In SoftX3000
V300R601C03
(restricted version),
V300R601C05, and later
versions, the MSGIs are
configured in load
balancing mode. That is,
each MSGI is allocated a
module number and the
slot number of the
standby MSGI is set to
255.
NOTE
A pair of assistant boards
working in the active/standby
mode can be configured in
either adjacent slots or in non-
adjacent slots, but the boards
must be in the same subrack.
2.2.4 Planning the Module Number

Module number planning principle

l The active/standby boards are allocated with the same module number.
l A maximum of four pairs of IFMIs can be configured.
Table 2-8 Module number planning principle

Module number The module numbering plan ADD BRD

for boards are as follow:
l SMUI: 2 to 21
(automatically assigned
by the system when a
subrack is added)
l FCCU: 22 to 101
l CDBI: 102 to 131
l IFMI: 132 to 135
l BSGI: 136 to 211
l MSGI: 211 to 136
l MRCA: 212 to 247
2.3 Planning the Local Office Data

The required data is as follows:
l Switch ID
l Local office DN set
l Local DN set
l Country code
l Area code
l National area code
l Call source code
l Call source name
l Route selection code
l Failure source code
l Number segment
It is recommended that you record the data in a table.
2.3.1 Naming Rules
2.3.2 Planning the DN Set and Call Source Code Data
2.3.3 Planning the Signaling Data
2.3.4 Planning the Trunk Data
2.3.5 Planning the Prefix - based Routing Data
2.3.6 Planning the Number Analysis Data

2.3.7 Planning the MGW Data

2.3.8 Planning the NGN Device Login Data
2.3.1 Naming Rules

Naming Rules for the BAM/EWS
Network card name
After the installation, the BAM and the iGWB have four network cards. You are suggested to
name them separately to facilitate the check and modification of the network configurations.
The network cards of the BAM and the EWS are named as follows:
l NIC0: plane 0 (172.20.200.0)
l NIC1: plane 1 (172.30.200.0)
l NIC2: Maintenance
l NIC3: Backup
Office name
The office name must be set based on the actual situation. It must not be named "HW-SoftX",
which is the default name. You are suggested to name the office in the following format:
Location-SoftX3000-serial number.
To modify the office name, you need to modify the STXBAM.INI file in the BAM. There is a
line that says "BureauName =xxxx" under "[System]" in the STXBAM.ini file, where xxxx
refers to the office name. For example, the SS1 office in the Beijing branch of China CNC is
named BJ-SoftX3000-1.
Name of the maintenance workstation
For ADD WS, if the workstation is used by a single operator, you are suggested to name it with
the name of the maintenance person. If the workstation is used by several operators, you are
advised to name them as workstation_1, workstation_2, or workstation_3.
Naming Suggestions
General suggestions
l Names can describe the objects. Therefore, the names must be clear and unique.
l The names must indicate the location (the city or region) of the devices, the gateway type,
and the gateway number. If the devices are located in a dual-homing network, the names
must also indicate the work mode (for example, active/standby) of the devices.
l The parameters in the MML commands are character strings (an English letter is considered
as a character). If the length of names is limited, simplify the name without affecting the
understanding.
l The office can be named with the full name or the abbreviation of the city.
– The offices in the capital cities of the provinces can be named with the abbreviation of
the cities. For example, Beijing is simplified as BJ, Chengdu as CD, Shijiazhuang as
SJZ, Huhehaote as HHHT, Wulumuqi as WLMQ, and Haerbin as HRB.
– For the offices in the non-capital cities, name the offices with the full names of the cities
and capitalize the first letter, for example, Dandong, Quanzhou, Wuhu, and Maanshan.
Detailed suggestions

The naming conventions are as follows:
Data Naming Convention MML Suggested Naming Format

Comman
d
Location It specifies the geographical ADD Abbreviation of the city name -

name location of the telecommunica- SHF telecommunications room name
tions room. The length of the
location name cannot exceed
25 characters.
Local It specifies the local office. The SET OFI Abbreviation of the city name -
office length of the local office name SoftX3000 number
name cannot exceed six characters.
Local DN If there are a few local DN sets, ADD Refer to the local office name.
set name the local DN set name can be LDNSET
the same as the local office
name. If there are multiple
local DN sets, you can refer to
the local network names to
name these local DN sets.
Call The length of the call source ADD l If a trunk is considered as the
source name cannot exceed 26 CALLSR call source, set the call source
name characters. The call source C name in the format of call
name can be filled based on the source type-location area ID-
call source attribute. office type.
l If a subscriber is considered
as the call source, set the call
source name in the format of
call source type-location area
ID.


Comman
d
Equipmen l For the MGW adopting the ADD For the MGW adopting the
t ID MGCP protocol, the MGW/ MGCP protocol, set the
equipment ID can be ADD equipment ID in the format of
determined based on the MMTE simplified spelling of the city-
negotiation result between location area name-MGW type,
the SoftX3000 and the MGW ID, and simplified name
MGW. For the purpose of of the carrier.
convenient maintenance,
the equipment ID must
contain the information
about the location area,
MGW type, and MGW ID.
l For the MGW adopting the
H.248 protocol, the
equipment ID is constantly
set to the IP address of the
MGW: 2944.
l For the multimedia
terminals adopting the SIP
and H.323 protocols, the
equipment ID is usually set
to the number of the
terminal.
MGW It describes an MGW to ADD Simplified spelling of the city-

descriptio facilitate maintenance. The MGW MGW location area-MGW type,
n length of the MGW description MGW ID, and simplified name
cannot exceed 64 characters. of the carrier.
The MGW description must
contain the information about
the MGW location area, MGW
type, and MGW ID.
SG The length of the SG ADD SG Refer to the MGW description

descriptio description cannot exceed 16
n characters. The SG description
must be consistent with the TG/
UMG8900 description of the
embedded signaling gateway.
Local The length of the local entity ADD Active/standby flag-local office
entity name cannot exceed 16 M3LE name-local signaling point
name characters. The local entity number
name must contain the
information about the active/
standby work mode, local
office name, and local
signaling point number.


Comman
d
Destinatio The length of the destination ADD Active/standby flag-peer city-

n entity entity name cannot exceed 16 M3DE peer office type (including SG,
name characters. The destination DC1, DC2, GW, and LS)
entity name must contain the
information about the office
name and office category. It
also must contain the
information about the active/
standby work mode, peer city,
and peer office type.
Linkset The length of the linkset name ADD Active/standby flag-peer city-
name cannot exceed 16 characters. It N7LKS/ peer office type-LS1 (LS1
contains the information about ADD indicates the linkset number
the active/standby work mode, M3LKS because an office may have
peer city, peer office type, and multiple linksets after the
linkset. capacity expansion.)
Link The length of the link name ADD Active/standby flag-peer city-
name cannot exceed 16 characters. It N7LKS/ peer office type-L1 (L1 indicates
contains the information about ADD the link number because an office
the active/standby work mode, M3LKS may have multiple links.)
peer city, peer office type, and
link.
M3UA The length of the M3UA route ADD Active/standby flag-peer city-
route name cannot exceed 16 M3RT peer office type-R1 (R1 indicates
name characters. It contains the the route number, that is, the
information about the active/ route with the highest priority)
standby work mode, peer city,
peer office type, and route.
Office The length of the office ADD Trunk type (including ISUP and
direction direction name cannot exceed OFC SIP) -peer city-peer office type
name 16 characters. The office (including DC1, DC2, GW, and
direction name must contain LS)/peer office name
the information about the peer
office name and peer office
category.
Subroute The length of the subroute ADD Trunk group type of the
name name cannot exceed 16 SRT subroute-peer city-peer office
characters. The subroute name type/peer office name-subroute
must be the same as the direct number (subroute 1 indicates the
office direction name. If first subroute.)
multiple subroutes are destined
for an office, the subroutes are
distinguished by suffixes, for
example, subroute 1 and
subroute 2.


Comman
d
Route The length of the route name ADD Trunk group type-peer city-peer
name cannot exceed 16 characters. N7RT office type
The route name must be the
same as the direct office
direction name.
Trunk The length of the trunk group ADD Trunk group type (including
group name cannot exceed 16 N7TG ISUP and SIP) -peer city-peer
name characters. The trunk group office type (including SS, DC1,
name must contain the DC2, GW, and LS)/peer office
information about the trunk name-trunk group number
group type.
2.3.2 Planning the DN Set and Call Source Code Data

Planning the DN Set Data
The DN set planning principles are as follows:
DN Set Type Planning Principle Obtaining Method Remarks
Global DN set A global DN set is Planned by the carriers The global DN sets are
allocated to a used for the
dedicated network. independent networks
The number of global in an office.
DN sets is the same as
the number of
independent networks
of the local office.
Local DN set A local DN set is Planned by the carriers The local DN sets are
allocated to a local used for the multi-area
network. The number code configuration in
of local DN sets is the the local office.
same as the number of
local networks of the
local office.
Planning the Call Source Code Data

The call source code planning principles are as follows:

Office Type Planning Principle Obtaining Method
Tandem l If the plan of allocating a call source code Planned by the carriers
office to each area code cannot meet the
requirement (for example, calling numbers
are required to have different prefixes), a
call source code can be allocated to each end
office.
l Each end office, toll office, SSP, and
gateway office are allocated with different
call source codes. For the purpose of
network evolution, it is recommended that
a call source segment be allocated to a local
network.
End office l When the numbering plan of the subscriber Planned by the carriers
integrated call source codes is independent from that
with the of the trunk call source codes, the subscriber
tandem office call source codes are numbered from 0.
After the numbering of the subscriber call
source codes is complete, the trunk call
source codes are numbered in sequence
following the last subscriber call source
code.
l In cross-network mode, if a trunk is used by
multiple networks, it is recommended that a
private local DN set with a virtual area code
be allocated to the trunk. The shared call
source codes are stored in this local DN set
and are numbered from 0 in ascending
order.
Example of DN Set and Call Source Code Numbering

A tandem office serves four cities, A, B, C, and D. The numbering plans of the DN sets and call
source codes are as follows:
Local Call Local DN Global DN Description

Network Source Set Set
Code
City A 0-199 0 1 City A is allocated 200 call source

(29) codes. End offices, toll offices,
SSP, and gateway offices are
allocated different call source
codes.

Local Call Local DN Global DN Description

Network Source Set Set
Code
City B 200-299 1 1 City B is allocated 100 call source

codes.
City C 300-399 2 1 City C is allocated 100 call source

codes.
City D 400-499 3 1 City D is allocated 100 call source

codes.
2.3.3 Planning the Signaling Data

Planning the Local Signaling Data
Table 2-9 shows the signaling data of the local office.
Table 2-9 Signaling data of the Local Office

Data to Be MML Commands Obtaining Method
Planned
Local SPC SET OFI Planned by the carriers
Local ADD OFC Planned by the carriers

signaling
point index
Local entity ADD M3LE Planned by the carriers

M3LE index
Planning the Link Data

Link data numbering rules

Data Planning Principle Remarks
DSP The DSP index of the STP ranges from 0 to 9 and Set the DPC of the trunks in
index is allocated from 0 in ascending order. the PS domain such as non-
Other DSPs are numbered from 10 corresponding SS7 trunks to 000000 and the
to the office direction numbers. trunks must be allocated with
different office direction
The STP flag can be set to True only when the numbers.
DSP is an STP, and the adjacent flag can be set to
True only for the DSP of the direct signaling link.
The DPC indexes must correspond to the office
direction numbers.
Linkset The MTP linkset numbers correspond to the DSP If a signaling point does not
number indexes and are numbered in ascending order. have a direct link, reserve the
linkset number range
corresponding to the
signaling point.
MTP The inter-office MTP route numbers are the same -

route as the linkset numbers.
number
Mask When selecting different linksets in the same The linkset selection mask
office direction, the SoftX3000 uses the cannot be the same as the link
remainder selection algorithm and thus can selection mask. It is
automatically select a valid linkset if the decimal suggested to set digit 1 in two
value of the linkset selection mask is equal to or masks at different bit
greater than the value of the total number of positions. For example, if the
linksets in an office direction minus 1. linkset selection mask is
When selecting different links in the same linkset, 0110, set the link selection
the SoftX3000 also uses the remainder selection mask to 1001. Set the mask
algorithm and thus can automatically select a with the guidance from the
valid link if the decimal value of the link selection mask description document.
mask is equal to or greater than the value of the
total number of links in a linkset minus 1.
MTP/ The link numbers are allocated in ascending The combination of the local
M2UA/ order. For the consideration of security, the links SCTP port and the local IP
M3UA/ to the same signaling point cannot be allocated to address of the M2UA,
IUA link the same BSGI module. M3UA, IUA, or V5UA link
number The MTP, M2UA, M3UA, IUA, and V5UA links must be unique.
are named in the format of BSGI module number
+ link number.
Each BSGI module supports a maximum of 32
MTP links, 32 M2UA links, 32 IUA links, 32
V5UA links, or 64 M3UA links.
The BSGI board is responsible for processing the
H.248 protocol. Therefore, if the BSGI modules
are sufficient, configure the links evenly on each
module to avoid full configuration of a certain
module.

Data Planning Principle Remarks
SCTP The port number segments are allocated to -

port different SCTP subscribers (M2UA, M3UA,
number IUA, and V5UA) to avoid the problems such as
port number conflict or ultra-high CPU usage.
For details, see Table 2-10.
Table 2-10 SCTP port number allocation principles
Protocol
Type Port Number Range Remarks
M3UA 2905-3999 Allocated from 2905 in ascending

order
M2UA 2904-2000 Allocated from 2904 in

descending order.
IUA 4000-4999 Allocated from 4000 in ascending

order
V5UA 5000-5999 Allocated from 5000 in ascending

order
Link data planning
The link data plan is shown in Table 2-11.
Table 2-11 Link data plan
Link Data to Be Planned MML Commands Obtaining Method

Type
M2U l SG index ADD M2LKS and ADD Planned by Huawei

A link l M2LKS linkset M2LNK technical support engineers
index
l M2LNK linkset
index
l BSGI module
number
MTP l MTP3 DSP index ADD N7DSP, ADD The signaling point data is
link l MTP3 DPC N7LKS, and ADD planned by carriers and
N7LNK others are planned by
l MTP3 linkset index Huawei technical support
l MTP3 link index engineers.
l M2LNK linkset
index

Link Data to Be Planned MML Commands Obtaining Method

Type
V5U l SG index ADD SG, ADD Planned by Huawei

A link l V5UALKS linkset V5UALKS, , and ADD technical support engineers
index V5UALNK
l V5UALKS link
index
l BSGI module
number
V5 l V5 interface ID ADD V5I Planned by Huawei

signal l FCCU module technical support engineers
ing
l Trunk group number
l Primary link circuit
number
l Logical C channel
number of the
primary link
l Secondary link
circuit number
IUA l SG index ADD SG, ADD Planned by Huawei

link l IUA linkset index IUALKS, and ADD technical support engineers
IUALNK
l IUALNK link index
l BSGI module
number
PRA l Signaling link ADD PRALNK and Planned by Huawei

link number ADD IUALKS technical support engineers
l Signaling link circuit
number
l FCCU Module
number
l IUA linkset index
SCCP l SCCP remote ADD SCCPDSP and The signaling point data is
link signaling point index ADD SCCPSSN planned by carriers and
l Remote SPC others are planned by
Huawei technical support
l SCCP remote SPC engineers.
l SCCP subsystem
index

2.3.4 Planning the Trunk Data

Trunk Data Numbering Rules
In a new office, the SoftX3000 connects to a toll office, MS1, MS2, MS3, and PS trunk through
TUP/ISUP, NO.1, SIP, and R2 respectively. The SoftX3000 also serves the PRA and V5
subscribers. Table 2-12 describes the trunk data numbering plan.
Table 2-12 Trunk data numbering plan

Data Planning Principle Example Value Remarks
Office l All the office l The office direction of At present, PRA and R2
directio directions are the PS trunk is offices are not widely
n numbered numbered 0. deployed. Therefore, the
uniformly. l The office direction of PRA and R2 offices are
l The office the toll office is numbered together with the
direction number numbered 100. SS7 office.
of the PS trunk l The office directions of
ranges from 0 to MS1, MS2, and MS3
99. Other office are numbered 101, 102,
directions are and 103.
numbered from
100. The office directions with
other attributes are
numbered sequentially.

Subrou l The trunk group l Subroute/trunk group l If an office uses both No.
te/trunk number is the number of the PS trunk 1 and SS7 trunks, the
group same as the office: 0 subroutes/trunk groups
subroute number. l Subroute/trunk group are numbered in the same
l The subroute/ number range of the segment. The SS7
trunk group toll office: 100-109 subroutes/trunk groups
number of the PS are numbered in
l Subroute/trunk group ascending order and the
trunk office number range of MS1:
ranges from 0 to No.1 subroutes/trunk
110-119 groups are numbered in
99. The subroute/
trunk group l Subroute/trunk group descending order. When
number of other number range of MS2: modules and trunk
office directions 120-129 circuits are added, the
are numbered l Subroute/trunk group number of new trunk
from 100. number range of MS3: groups are subsequently
130-139 allocated within the
l A trunk is original number segment.
allocated to an The same rule is
office direction. applicable to others. l The range of the subroute
in the toll office is
l The subroute and 100-109 is because one
trunk group to office direction may
every office contain multiple
direction are subroutes, which will be
numbered from numbered as 100, 101,
100. By default, and 102. Normally, when
each office an office direction has
direction is only one ISUP, only one
allocated with 10 subroute number is used,
subroutes. such as 100, 110, or 120,
and others are all
reserved.

Route l The route l For the PS trunk office, For details, see the Prefix,
selectio selection code/ the route selection code route selection and route
n code/ route number of ranges from 0 to 99 and numbering table.
route the PS trunk office the route number
number ranges from 0 to ranges from 0 to 99.
99. The route l For the toll office, the
selection code/ route selection code
route number of ranges from 100 to 109
other office and the route number
directions are ranges from 100 to
numbered from 109.
100.
l For MS1, the route
l The route selection code ranges
selection code and from 110 to 119 and the
route number to route number ranges
every office from 110 to 119.
direction are
numbered from l For MS2, the route
100. By default, selection code ranges
each office from 120 to 129 and the
direction is route number ranges
allocated with 10 from 120 to 129.
subroutes. l For MS3, the route
selection code ranges
from 130 to 139 and the
route number ranges
from 130 to 139.
The same rule is
applicable to others.
Local The local office information is configured based on the actual situation. The local
office area code and country code must be set without the prefixes 0 and 00.
inform
ation
Trunk The trunk charging source code and subscriber charging source code are numbered
chargin separately. The trunk charging source code is numbered from 50.
g
source
code
Time For details, see the description of ADD TMIDX.

index

Table 2-13 Prefix, route selection and route numbering table.

Prefix Type Numbering Method
The prefix of the toll office is l If the route corresponding to the route selection code for
used for the first route call prefix 0 is the first subroute and no second subroute is
selection. configured, the route selection code is 100, the route
number is 100, and the subroute number is 100.
l If the route corresponding to the route selection code for
call prefix 222 is the first subroute and the second subroute
is MS1, the route selection code is 101, the route number
is 100, the first subroute number is 100, and the second
subroute number is 110.
call prefix 224 is the first subroute, the second subroute is
MS2, and the third subroute is MS3, the route selection
code is 103, the route number is 103, the first subroute
number is 103, the second subroute number is 120, and the
third subroute number is 130.
The prefix of MS1 is used for l If the route corresponding to the route selection code for
the first route selection. call prefix 333 is the first subroute and no second subroute
is configured, the route selection code is 110, the route
is the toll office, the route selection code is 112, the route
number is 112, the first subroute number is 110, and the
second subroute number is 100.
call prefix 336 is the first subroute, the second subroute is
MS2, and the third subroute is MS4, the route selection
code is 13, the route number is 113, the first subroute
number is 110, the second subroute number is 120, and the
third subroute number is 140.

Prefix Type Numbering Method
The prefix of MS2 is used for l If the route corresponding to the route selection code for
the first route selection. call prefix 444 is the first subroute and no second subroute
is configured, the route selection code is 120, the route
is the toll office, the route selection code is 122, the route
number is 122, the first subroute number is 120, and the
second subroute number is 100.
Planning the Trunk Data

The data to be planned is as follows:

Table 2-14 Trunk data planning table

Trunk Data to Be MML Obtaining Description
Data Planned Commands Method
Planning
Table
Type
TDM trunk l Home ADD V5TG, l If the carrier If a parameter is

data SoftX3000 ADD N7TG, has special assigned a
planning l Trunk group ADD requirements special value,
table name PRATG, for the highlight the
and ADD numbering of parameter in the
l Optical interface N1TG the trunk and table.
ID trunk office If a SoftX3000
l E1 ID direction, the configured with
l Subrack number- TDM trunk multiple IFMIs
slot number- data planning interwork with
optical interface table is another
ID-2 Mbit/s planned by the SoftX3000
trunk ID carrier. through the SIP-
l If the carrier T trunks, it is
l Board group
does not have recommended
number
special that multiple SIP-
l Start TID requirement, T trunks be
l End TID Huawei can configured for
determine the the IFMIs.
l Primary/
TDM trunk
secondary
data planning
SoftX3000
table.
l FCCU module
number
l Office direction
l Location area
l SPC
l Link SLC
l OPC of the
primary SS
circuit
l OPC of the
secondary SS
circuit
l Start CIC off the
primary circuit
l End CIC off the
primary circuit
l Start CIC off the
secondary circuit
l End CIC off the
secondary circuit

Trunk Data to Be MML Obtaining Description

Data Planned Commands Method
Planning
Table
Type
l System ID of the
office
l Start CIC
l End CIC
l Active flag of the
SoftX3000
l Continuity check
result
l Designated trunk
dialing test
PS trunk l Trunk group ADD

data table l Call source code SIPTG
(SIP)
l Route number
l Local IP address
l Peer URI
l Whether
supporting
heartbeat
messages
l Active/standby
flag
l Supporting SIP-
T
PS trunk l Trunk group ADD

data table l Call source code H323TG
(H.323)
l Route number
l Trunk type
l IP Address
l Calling trunk
port
l RAS trunk port
l GK entity type
l GK ID
2.3.5 Planning the Prefix - based Routing Data

Carrier needs to plan the following data for each end office:

l Call prefix
l Routing information
l Subroute selection mode
l Percentage of traffic over each subroute
l Service type
l Service attribute
l Charging information
l Release mode
l Maximum and minimum number length
The principles for the prefix and routing data planning are as follows:
Data Type Planning Principle
Prefix l The prefixes shared by all location areas are configured as the wildcard
in local DN set 65534.
l The private prefixes of each location area are configured in the local DN
set separately.
l To configure different routes for the same prefix, you need to configure
different route selection codes for these routes. For details, see the
description of the route analysis data planning.
Route l Prefixes are configured with different route selection codes.

analysis data l When two call sources in the same DN set originate calls to the same
planning outgoing call prefix in this DN set, if the route selection strategies are
different, different route selection source codes must be allocated to the
two call sources.
– Route selection source codes are differentiated for different call
sources based on the following scenarios:
– Calls are made in end offices, in toll offices, in gateway offices,
and through SIP-T trunk groups.
– The prefix returned by the SSP to the SoftX3000 is the same as the
prefix sent from the end office.
– The peer office communicates with the local office through the
SIP-T (I) alternative speech channels.
– The PSTN trunk group has special requirements for the outgoing
calls.
– To reduce the route analysis data, plan the route selection code and
route selection source code data based on the preceding principles.
The route selection code and route selection source code data has the
same range as the call source code data, which facilitates the data
maintenance.
For details, see the description of ADD CNACLD.

2.3.6 Planning the Number Analysis Data

The SoftX3000 supports a large number of data change types. To plan the number analysis data,
list the required data in a table based on the data change type.
Type Data Required MML Commands Obtaining Method
Number l Number change index ADD DNC Planned by the carriers

change l Number change type
table
l Change location
l Change length
l Nature of address
indicator
l New number
DN set l Call source ADD PFXPRO Planned by the carriers

processi l DN set
ng table
l Call prefix
l Method of sending tone
l Failure processing flag
l New DN set
l Called number change
index
l Caller number change
index
l Reanalysis
l Tone type
l Failure cause code
Call l Call source code ADD CFPRO Planned by the carriers

Failure l Call prefix
Processi
ng table l Failure cause configure
l Failure cause value
l Caller category
l Service attribute
l Transmission capability
l Processing type
l FailureSender

Trunk l Trunk group number ADD TGLD Planned by the carriers

group l Call source code
bearer
table l Local DN Set
l Call prefix
l Trunk group bearer
index
l Trunk seizure point
index
index
Caller l Caller number ADD CNACLR Planned by the carriers

number l Call source code
analysis
table l Call prefix
l Function code
l Route selection source
code
l Caller category
l Route selection source
code
l Caller category
index
index
l Preselection access code
index
l Reanalysis flag

Number l Call source code ADD CALLSRC Planned by the carriers

preparati l Pre-received digits
on table
l Local DN Set
l All number change index
l International number
change index
l National number change
index
l Subscriber number
change index
l Caller address
discrimination
2.3.7 Planning the MGW Data

Obtaining Method
l If the SoftX3000 interworks with the existing MGW, the MGW data must be planned by
carriers.
l If the MGW is newly interconnected with the SoftX3000, ask the MGW side to provide
the related MGW data to be planned on the SoftX3000.
Planning Principle
l When the SoftX3000 is configured with multiple pairs of IFMIs, balance the loads of the
MGWs among these pairs of IFMIs for the purpose of reducing security risks.
l When the SoftX3000 is configured with multiple pairs of FCCUs, the MGWs are managed
by different FCCUs to ensure system security.
l The MGW IDs must be planned uniformly to facilitate routine management.
Data Planning
Table 2-15 shows the data planning table. For details about the data and specifications, see the
description of ADD MGW.
Table 2-15 MGW description

MGW Data
Equip gatew MGW Local Local IP Remot FCCU Maste Remar

ment ay descri IP port addres e port modul r/ ks
ID type ption addres s of the e Slave
s gatew numbe type
ay r

NOTE
If other parameters are required, add the corresponding column in the table.
2.3.8 Planning the NGN Device Login Data

The required login information is as follows:
Data Required Obtaining Method
Device name Planned by the carriers
Username used on the client for login Planned by the carriers
Password used on the client for login Planned by the carriers
Username of the operating system Planned by the carriers
Password of the operating system Planned by the carriers
Username of the database Planned by the carriers
Password of the database Planned by the carriers
Installation serial No. Delivered with the device to be installed

Initial Configuration 3 Configuring Basic Data
3 Configuring Basic Data
About This Chapter
Basic data includes equipment data, office data, and charging data. The basic data is the basis
for configuring the database. It specifies global data, such as equipment components, physical
port parameters, basic office information, and charging policies.
The key parameters defined during the basic data configuration include the module number of
a board, IP address of an FE port, local DN set, call source code, charging source code, and
charging selection code. The key parameters are often used later during data configuration. After
you configure the data for the database, you cannot modify or remove these key parameters.
These actions are limited by the stored procedure of the database.
Therefore, you must pay special attention to the planning of the basic data. For details, refer to
the Data Configuration Engineering Specifications provided by Huawei, the purpose of which
is to facilitate the management and maintenance of the database and the extension of the database
during system capacity expansion or software upgrade.
The basic data configuration during deployment and system expansion is performed in batches.
For details about how to perform the batch operation, see Executing a Configuration Script File.
3.1 Configuring Hardware Data
3.2 Configuring Local Office Data
3.3 Configuring Charging Data

3 Configuring Basic Data Initial Configuration
3.1 Configuring Hardware Data

Scenarios
You need to configure the hardware data in the following scenarios:
l Office deployment
l Cabinet expansion
l Subrack expansion
l Board expansion
Prerequisites
Conditions
l You have the administrative rights.

l You have logged in to the LMT of the SoftX3000.
Data
The hardware data to be configured include rack data, subrack data, hardware type, board data,
software loading switch, FE port data, and CDB functions.
Before you configure the hardware data, you need to collect the information described in Table
3-1.
Table 3-1 Information to be collected before configuring the hardware data
Item Remarks
Diagram of device panel configuration It provides the types, location, and numbers
of hardware components, such as racks,
frames, and boards.
Module numbers of boards They are used for planning the module
numbers of the IFMI, CDBI, FCCU, BSGI,
MSGI, and MRCA boards in a unified
manner.
Networking scheme of the bearer network It is used for configuring the IP address of the
FE port and IP routing data.
l Diagram of device panel configuration

In this example, the SoftX3000 is configured with one basic subrack and one expansion
subrack. They are located in subracks 2 and 3 in the integrated configuration cabinet
respectively. Figure 3-1 and Figure 3-2 show the board configuration.

Figure 3-1 Board configuration in the basic subrack
Back B B S H S H U U
Boards F F I S I S P P
I I U C U C W W
I I I I I I R R
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
I I F F F F S S C C B B M M A U U
Front F F C C C C M M D D S S S S L P P
Boards M M C C C C U U B B G G G G U W W
I I U U U U I I I I I I I I I R R
Figure 3-2 Typical configuration of boards in the expansion subrack
S H S H U U
Back I S I S P P
Boards U C U C W W
I I I I R R
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
F F S S B B M M A U U
Front C C M M S S S S L P P
Boards C C U U G G G G U W W
U U I I I I I I I R R
l Basic information about key boards

Table 3-2 Basic information about key boards in the basic subrack
Subrack Subrack Rack Position - -
Type No. Number Number
Basic 0 0 2 - -
subrack
Board Type Subrack No. Slot Position Module Assistant

Number Number Number Board Slot
Number
IFMI 0 0 Front 132 1
IFMI 0 1 Front 132 0
FCCU 0 2 Front 22 3
FCCU 0 3 Front 22 2
FCCU 0 4 Front 23 5
FCCU 0 5 Front 23 4
CDBI 0 10 Front 102 11
CDBI 0 11 Front 102 10
BSGI 0 12 Front 136 255
BSGI 0 13 Front 137 255
MSGI 0 14 Front 135 15
ALUI 0 16 Front - -
SMUI 0 6 Front- - -
SMUI 0 8 Front - -
Table 3-3 Basic information of key boards in the expansion subrack

Expansion 1 0 3 - -
subrack
Board Type Subrack No. Slot Position Module Assistant

Number Number Number Board Slot
Number
FCCU 1 0 Front 32 1
FCCU 1 1 Front 32 0


BSGI 1 10 Front 211 255
BSGI 1 11 Front 210 255
ALUI 1 16 Front - -
SMUI 1 6 Front - -
SMUI 1 8 Front - -
Documents
Before configuring the local office data, you must plan the related data based on the requirements
in the Specifications for Data Configuration provided by the Global Technical Service
Department of Huawei.
Workflow
The procedure for configuring hardware data is as follows:
1. Configure basic hardware data.
2. Configure the FE port and CDB function.
3. Configure the protocol dispatching ability and the IFMI access control list. (Optional)
Procedure
Step 1 Configure basic hardware data.
1. Add the rack.
ADD SHF: SHN=Shelf number, ZN=Zone number, RN=Row number, CN=Column

number, PL=PDB location, PT=PDB type;
NOTE
If PDB location in the command is set to 2, it indicates that the basic subrack controls the PDB of
the rack.
2. Add the subrack.
ADD FRM: FN=Frame number, SHN=Shelf number, PN=Position number;
NOTE
For the basic subrack in the integrated configuration cabinet, Frame number is always set to 0 and
Position number in the rack is always set to 2.
3. Add the board.
ADD BRD: FN=Frame number, SLN=Slot number, LOC=Location, FRBT=Front Board

type, MN=Module number, ASS=Assistant board slot number;

NOTE
l SMUI: 2 to 21 (auto assigned by the system)

l FCCU: 22 to 101
l CDBI: 102 to 131
l IFMI/BSGI/MSGI: 132 to 211
Step 2 Configure the FE port and CDB function.

1. Add the FE port configuration.
ADD FECFG: MN=IFMI module number, IP="IP address", MSK="Subnet mask",

DGW="Default gateway";
NOTE
l When you add the FE port configuration, set the default gateway address to the IP address of the
router.
l The SoftX3000 is connected to the default router (gateway) through the FE port, and then
communicates with other IP devices through the router. You must correctly set the IP address of
the default router serving the FE port; otherwise, the SoftX3000 cannot communicate with the
IP devices.
2. Add the CDB function configuration.
ADD CDBFUNC: CDPM=CDBI module number, FCF=Function configuration;
NOTE
a. One CDB function can be configured only on one pair of CDBI boards. One pair of CDBI boards
can be configured with several CDB functions.
b. The CDB function consumes system memories. Therefore, when only one pair of CDBI boards
are configured, do not configure all the CDB functions. When configuring the CDB function,
you can follow the following principles:
l In the NGN architecture, you are advised to configure the following CDB functions:
subscriber location, trunk hunting, MGW resource management, black and white list, IPN
card number, BSGI dispatching, special called number change, RACF function, CLI analysis
function, special DN analysis, monitor, preselection function, and general change DN
function.
l In the pre-IMS architecture, you are advised to configure the following CDB functions:
subscriber location, trunk hunting, MGW resource management, BSGI dispatching, SACP,
STCP, automatic call back, NGN user location, and route selection. Generally, the pre-IMS
architecture is not used.
l If LiteFME is configured in the NGN architecture, you are advised to configure two pairs of
CDBIs and configure the home database function on one pair of the CDBIs independently.
l When the softswitch serves as an AGCF, you are advised to configure the following CDB
functions: subscriber location, trunk hunting, MGW resource management, and BSGI
dispatching.
c. When two pairs of CDBIs are configured, you must assign different central database functions
to the two pairs based on the load-sharing principle. In the NGN architecture, you are advised to
configure the trunk hunting and subscriber location functions on different CDBIs. In the pre-IMS
architecture, you are advised to configure the SACP and STCP functions on different CDBIs. If
LiteFME is configured in the NGN architecture,you are advised to configure two pairs of CDBIs
and configure the home database function on one pair of the CDBIs independently.
d. In the pre-IMS architecture, you must configure both the trunk hunting and route status
management functions and configure them on the same pair of CDBIs.
e. If all the CDB functions are required, you must configure two pairs of CDBIs and configure the
CDB functions on different modules.
f. Run the command of "FMT" after runned this command, and restrat the board of CDBI.

Step 3 Configure the protocol dispatching ability and the IFM access control list. (Optional)
1. Configure the protocol dispatching ability.
SET DPA: MN=BSGI/MSGI module number, DA=Protocol Dispatch ability;
NOTE
l When you use the ADD BRD command to add boards, the system has automatically set the
default protocol dispatch ability for the BSGI and MSGI. The default values are:
a. BSGI: MGCP, H.248 and SCTP.
b. MSGI: TRIP, STUN, MIDCOM, Original call, iDo, SMC and RADIUS.
l Generally, you can use the default settings directly. To enable a module to dispatch one or several
protocols, use SET DPA.
2. Add an IFM access control list.
ADD IFMACL: IFMMN=IFMI module number, MINMN=Start BSGI/MSGI module
number, MAXMN=End BSGI/MSGI module number;
NOTE
It is used to add IFM access control list data in the configuration database. The IFM access control
list is used to separate the signaling channels between the specified IFMI module and the BSGI/
MSGI module. Therefore, the signaling grouping can be achieved.
----End
Example
Task Description
This task enables the SoftX3000 to fulfill the following application requirements:
l Supporting 150 thousand subscribers
l Supporting 270 thousands trunk circuits
l Supporting IP bearer
l Supporting the board of the 750B type
Scripts
//Add the rack
ADD SHF: SHN=0, LT="FRM0", ZN=1, RN=1, CN=1, PL=2, PT=PDB48V;
//Add the subrack

ADD FRM: FN=0, SHN=0, PN=2; ADD FRM: FN=1, SHN=0, PN=3;
//Add the board

ADD BRD: FN=0, SLN=0, LOC=FRONT, FRBT=IFMI, MN=132, ASS=1;
ADD BRD: FN=0, SLN=2, LOC=FRONT, FRBT=FCCU, MN=22, ASS=3;
ADD BRD: FN=0, SLN=10, LOC=FRONT, FRBT=CDBI, MN=102, ASS=15;
ADD BRD: FN=0, SLN=12, LOC=FRONT, FRBT=BSGI, MN=136;
ADD BRD: FN=0, SLN=14, LOC=FRONT, FRBT=MSGI, MN=135, ASS=15;

ADD BRD: FN=0, SLN=16, LOC=FRONT, FRBT=ALUI;

ADD BRD: FN=1, SLN=16, LOC=FRONT, FRBT=ALUI;
//Add the FE port data

ADD FECFG: MN=132, IP="191.160.150.30", MSK="255.255.255.0",
DGW="191.160.150.1";
Add the CDB function configuration.

ADD CDBFUNC: CDPM=102,
FCF=LOC-1&TK-1&MGWR-1&BWLIST-1&IPN-1&DISP-1&SPDNC-1&RACF-1&CLANA-1&UC-0&S
PANA-1&KS-0&SACP-0&STCP-0&MONITOR-1&ACB-0&UL-1&RTS-0&PRESEL-1&CDN-1&COPS-
0&HDB-0&ASF-0&CXCONT-0&AUTHDATA-0;
Additional Information
Related tasks
Commissioning of Local Office Hardware
Related concepts
For the information about the relations between the hardware data tables, see 12.1 Relations
Between Hardware Data Tables
3.2 Configuring Local Office Data

Scenarios
You need to configure the local office data in the following scenarios:
l Office deployment
l Cabinet expansion
Prerequisites
Conditions
Data
The local office data is the basic data of the SoftX3000. It includes the time zone, signaling point
code, global DN set, local DN set, country code (region code), national toll area code, and call
source.
Before configuring the data, you must collect the data listed in Table 3-4.

Table 3-4 Data to be collected before configuring the local office data
Category Parameter Example Value How to Obtain Description
Name
Time Zone Time zone index 0 The value is a It identifies the

informatio system initial time zone to
n value. which the local
office belongs,
that is the default
time zone of the
system. The value
ranges from 0 to
254. The
configuration
principle of this
parameter is:
l If the carrier
uses the preset
time zone of
the system
(GMT-13:00
to GMT
+13:00), the
operator can
enter the
mapping time
zone index
(0-26). You
can run LST
TMZCFG to
query the time
zones
represented by
each time
zone index.
l If the carrier
uses the
customized
time zone, this
parameter
must be
defined in
ADD
TMZCFG.
Data about Signaling point 112222 (in 24-bit The value is -

the code of the local code format) determined by the
signaling office (national carrier.
points of network)
the local
office


Name
Local Global DN set 0 The value is a The global DN set

office data system initial is predefined to 0
value. during the system
initialization.
Therefore, the
global DN set can
be directly
referenced in the
subsequent data
configuration. If
other global DN
sets are required,
you need to run
ADD NCODE to
define these
global DN sets.
Local DN set 0 The value is It defines the local

determined by the DN set used
carrier. during the called
number analysis.
Country code/ 86 The value is a The country code

region code system initial (region code) has
value. been predefined
during system
initialization.
Therefore, you
need not to
specify it again. If
the local office
needs to be
configured with
multiple country
codes or multiple
region codes, run
ADD NCODE to
add country codes
or region codes.


Name
National toll area 10 The value is a Normally, the

code system initial national toll area
value. code has been
predefined during
system
initialization.
Therefore, you
need not specify it
again. If the local
office needs to be
configured with
multiple country
codes or multiple
region codes or to
be used in area
outside China,
run ADD
ACODE to add
national toll area
codes.
National toll call 0 The value is Normally, the

prefix determined by the national toll call
carrier. prefix has been
predefined during
International toll 00 The value is system
prefix determined by the initialization.
carrier. Therefore, you
need not specify it
again. If the local
office needs to be
configured with
multiple country
codes or multiple
region codes or to
be used in area
outside China,
run ADD
PFXTOL to add
national toll call
prefixes.


Name
DigitMap [2-8]xxxxxx| The value is The system

13xxxxxxxxx| determined by the supports the
0xxxxxxxxx| carrier. DigitMap with a
9xxxx|1[0124-9] maximum length
x|E|F|x.F|[0-9].L of 10000
(H.248 protocol) characters.
Running the
command once
can add 2000
characters to the
DigitMap.
Call Call source code 0 The value is One SoftX3000

source determined by the can be configured
data carrier. with only one call
source code.


Name
Call source name CALL_SRC0 The value is It is used to

determined by the identify a call
carrier. source within the
SoftX3000. The
principles for
configuring the
call source code
and call source
name are as
follows:
l If you do not
use the default
setting when
specifying the
call source
name, you
need to use a
call source
name that is
unique in the
local office
records.
l You need to
specify at least
one item
between the
call source
code and the
call source
name.
l If the call
source name is
specified but
not the call
source code,
the system
will
automatically
generate a
unique call
source code
for the call
source name.


Name
Pre-received 3 The value is It specifies the

digits determined by the minimum number
carrier. of digits the
SoftX3000
should receive
before triggering
the number
analysis process.
The principles for
setting the
parameter are as
follows:
l For ordinary
subscribers,
this parameter
is generally
set to 3. For
instance,
when you dial
28970001, as
soon as the
first three
digits 289 are
dialed, the
system starts
the number
analysis.
l For Centrex
subscribers, it
is usually set
to 1. When the
outgoing
prefix is
dialed, the
second dialing
tone is played.
Thus, an
additional call
source must
be set for
Centrex
subscribers.
Documents

Workflow
The procedure for configuring local office data is as follows:
1. Configure the local signaling point.
2. Configure the local office data.
3. Configure the call source data.
Procedure
Step 1 Configure the local signaling point.
SET OFI: OFN="Local office name", LOT=Local office type, NN=National network valid,
NN2=National reserved network valid, SN1=First search network, SN2=Second search
network, NPC="National network code", NP2C="National reserved network code",
NNS=National network structure, NN2S=National reserved network structure, STP=STP
function, TMZ=Time zone index;
NOTE
l If the multi-SPC function is required, run ADD OFI to add SPCs.

ADD OFI: IDX=OPC index, NI=Network indicator, OPC="OPC", MSTYPE=Master/Slave type;
l If the carrier uses the customized time zone, this parameter must be defined in ADD TMZCFG.
ADD TMZCFG: TZ=Time zone index, BCTZ=Benchmark time zone, TOFFSET=Time offset,
TZNAME="Time zone name";
Step 2 Configure the local office data.

1. Add a country code or region code. (Optional)
ADD NCODE: P=DN set, NC=Country/Region code, NN="Country/Region name";
2. Add the toll prefix description. (Optional)
ADD PFXTOL: P=DN set, NC=Country/Region code, NTP=National toll prefix,
ITP=International toll prefix;
3. Add a national toll area code. (Optional)
ADD ACODE: P=DN set, NC=Country/Region code, AC=National area code, AN="City
name", DC=District code;
4. Add a DigitMap.
ADD DMAP: PROTYPE=Protocol type, DMAPIDX=DigitMap index,
PARTIDX=DigitMap part, DMAP="DigitMap";
5. Add a local DN set.
ADD LDNSET: LP=Local DN set, LDN="Local DN set name", P=DN set, NC=Country/
Region code, AC=National area code, DC=District code, DGMAPIDX=H248 digit map
index, MDGMAPIDX=MGCP digit map index, MSTYPE=Master/Slave type;
Step 3 Configure the call source data.
ADD CALLSRC: CSC=Call source code, CSCNAME="Call source name", PRDN=Pre-
received digits, LP=Local DN set, LDN="Local DN set name", RSSC=Route selection source
code, FSC=Failure source code, DCF=Number preparation, UCFLAG=UC analysis flag,
VCC=Change caller number flag;
----End

Example 1
Task Description
l The local office is an end office located in China.
NOTE
When the local office serves as an end office location in China, the global DN set, country/Region
code, toll prefix, and national toll area code are predefined during system initialization. Therefore,
you do not need to specify them again.
l The local office is configured with only one SPC (national network).
Scripts
//Set the local office information.
SET OFI: OFN="beijing", LOT=CMPX, NN=YES, SN1=NAT, SN2=NAT, NPC="112222",
NNS=SP24, STP=YES, TMZ=40, SGCR=NO;
//Add a DigitMap.
ADD DMAP: PROTYPE=H248, DMAPIDX=0, PARTIDX=0, DMAP="[2-8]xxxxxx|
13xxxxxxxxx|0xxxxxxxxx|9xxxx|1[0124-9]x|E|F|x.F|[0-9].L";
//Add a local DN set.

ADD LDNSET: LP=0, LDN="name", NC=K'86, AC=K'10, DGMAPIDX=0, MSTYPE=MASTER;
//Add a call source code.

ADD CALLSRC: CSC=0, CSCNAME="CALL_SRC0", PRDN=3, LP=0, LDN="name",
RSSC=1, FSC=1, DCF=YES, UCFLAG=NO, VCC=YES;
Example 2
Task Description
l The local office is an end office located in Berlin.
l The local office is configured with only one SPC (national network).
Scripts
//Set the local office information.
SET OFI: OFN="SS1", LOT=CMPX, NN=YES, SN1=NAT, SN2=NAT, NPC="112222",
NNS=SP24, STP=YES, TMZ=0, SGCR=NO;
//Add a country code or region code.

ADD NCODE: NC=K'49, NN="Germany";
//Add the toll prefix description.

ADD PFXTOL: NC=K'49, NTP=K'0, ITP=K'00;
//Add a national toll area code.

ADD ACODE: NC=K'49, AC=K'30, AN="Berlin", DC=2;
//Add a DigitMap.

ADD DMAP: PROTYPE=H248, DMAPIDX=0, PARTIDX=0, DMAP="[2-8]xxxxxx|

13xxxxxxxxx|0xxxxxxxxx|9xxxx|1[0124-9]x|E|F|x.F|[0-9].L";
//Add a local DN set.

ADD LDNSET: LP=1, LDN="name", NC=K'49, AC=K'30, DGMAPIDX=0, MSTYPE=MASTER;
//Add a call source code.

ADD CALLSRC: CSC=0, CSCNAME="CALL_SRC0", PRDN=3, LP=1, LDN="name",
RSSC=1, FSC=1, DCF=YES, UCFLAG=NO, VCC=YES;
Related tasks
Local Office Commissioning
Related concepts
For the information about the relations between the local office data tables, see 12.2 Relations
Between Local Office Data Tables.
Scenarios
During the office deployment, you need to configure charging data based on the charging plan
of the carrier.
Prerequisites
Conditions
l You have completed the configuration of basic data.
Data

Table 3-5 Basic charging data

Category Paramet Example How to Obtain Description
er Name Value
Charging Charging 0 The value is determined by A charging case is a

case case the carrier. group of charging
methods applied to a
certain type of calls.
For example:
l When Charging
case is set to 0, it
indicates that the
calling party is
charged based on
CDRs.
l When Charging
case is set to 1, it
indicates that the
charging is based
on the number of
pulses, which is
usually used on
public phones.
Charging Charging 0 The value is determined by You can set Charging

mode case the carrier. mode to enable the
The value is obtained SoftX3000 to apply
through the LST different charging
CHGANA command. cases based on the
date or time zone.
Date Normal The value is determined by This parameter can

category workday the carrier. divide date into
You need to set the date in different categories,
advance by running ADD based on which
DCAT. different charging
cases can be applied.


er Name Value
Intra- Caller 0 The value is determined by This parameter

office charging the carrier. enables the
group source SoftX3000 to apply
charging code different charging
cases to the caller and
the callee.
l For intra-office
calls, Caller
charging source
code defines the
charging source
code of the caller
and Callee
charging source
code defines the
charging source
code of the callee.
l For trunk
incoming calls,
Caller charging
source code
defines the
charging source
code of the trunk
and Callee
charging source
code defines the
charging source
code of the callee.
l For trunk outgoing
calls, the system
applies the intra-
office group
charging method,
which does not
vary based on the
destination code.
Called 0 The value is determined by -

charging the carrier.
source
code
Bearer All voice The value is determined by -

capability service the carrier.
Codec All codecs The value is determined by -

the carrier.


er Name Value
Charging 0 The value is determined by -

case the carrier.
The value is obtained
through the LST
CHGANA command.
Charging Charging 0 The value is determined by This parameter

case index selection the carrier. enables the
code The value is obtained SoftX3000 to choose
through the LST the charging case
CNACLD command. based on prefixes.
Callee 0 The value is determined by -

charging the carrier.
source
code
Bearer All The value is determined by -

capability the carrier.
Bill type All bill type The value is determined by -

the carrier.

the carrier.

case the carrier.
through the LST
CHGANA command.
Called Callee 0 The value is determined by This parameter

group charging the carrier. enables the
charging source SoftX3000 to choose
code the charging case
based on the callees.
Bearer All voice The value is determined by -

capability service the carrier.

the carrier.

case the carrier.
through the LST
CHGANA command.


er Name Value
Suppleme Suppleme Register The value is determined by -

ntary ntary wakeup call the carrier.
service service
charging
source the carrier.
code
Charge Detailed The value is determined by -

method ticket the carrier.
Table 3-6 Additional charging data (optional)
Category Parameter Example How to Obtain Description

Name Value
Additional Additional 0 The value is determined by the This

fee charging fee carrier. parameter
mode charging enables the
mode carrier to
charge
additional fee
besides the
basic fee.
Start 60 The value is determined by the -

interval carrier.
Start fee 10 The value is determined by the -

carrier.
Additional Charging 1 The value is determined by the -

fee charging case carrier.
mode The value is obtained through
the LST PLUSPAY
command.
Workflow
The procedure for configuring charging data is as follows:
1. Add charging case analysis data.
2. Modify a charging mode.
3. Add intra-office group charging data.
4. Adding a charging case index.
5. Add called group charging data.

6. Add supplementary service charging data.

7. Add an additional fee charging mode.
8. Modify the additional fee charging mode.
Procedure
Step 1 Add charging case analysis data.
ADD CHGANA: CHA=Charging case, PAY=Payer, CHGT=Charging method;
Step 2 Modify a charging mode.
MOD CHGMODE: CHA=Charging case, DAT=Date category;
Step 3 Add intra-office group charging data.
ADD CHGGRP: RCHS=Caller charging source code, CLDG=Callee charging source code,
LOAD=Bearer capability, CODEC=Codec, CHA=Charging case;
Step 4 Adding a charging case index.
ADD CHGIDX: CHSC=Charging selection code, RCHS=Caller charging source code,

LOAD=Bearer capability, BT=Bill type, CODEC=Codec, CHA=Charging case;
Step 5 Add called group charging data.
ADD CHGCLD: DCHS=Callee charging source code, LOAD=Bearer capability,

CODEC=Codec, CHA=Charging case;
Step 6 Add supplementary service charging data.
ADD CHGSS: NS=Supplementary service, RCHS=Charging source code,

CHGMOD=Charging method;
Step 7 Add an additional fee charging mode.
ADD PLUSPAY: ACHT=Additional fee charging mode, TA=Start interval, MA=Start fee;
Step 8 Modify the additional fee charging mode.
MOD PLUSMOD: CHA=Charging case, DAT=Date category;
----End
Example
Task Description
The local SoftX3000 functions as an IP multimedia end office that serves both the voice service
subscribers and the IP multimedia service subscribers. The charging for the audio services
triggered by multimedia service subscribers and video services triggered by multimedia service
subscribers is different. Take calls within the local area as an example. The charging rate for the
IP audio service is 10 cents per minute and the charging rate for the IP audio service is 20 cents
per minute.
Scripts

//Add charging case analysis data. The record with Charging case set to 150 is used to charge
audio services based on meter table 1; the other record with Charging case set to 151 is used
to charge video services based on meter table 11.
ADD CHGANA: CHA=150, CHGT=PLSACC, CRM=TNSO; ADD CHGANA: CHA=151,
CHGT=PLSACC, MID=METER11, CRM=TNSO;
//Modify the charging mode.

MOD CHGMODE: CHA=150, DAT=NORMAL, TS1=00&00, TA1="60", PA1=1, TB1="60",
PB1=1, AGIO1=100, TS2=00&00; MOD CHGMODE: CHA=150, DAT=DTYPE1, TS1=00&00,
TA1="60", PA1=1, TB1="60", PB1=1, AGIO1=100, TS2=00&00; MOD CHGMODE:
CHA=150, DAT=DTYPE2, TS1=00&00, TA1="60", PA1=1, TB1="60", PB1=1,
AGIO1=100, TS2=00&00; MOD CHGMODE: CHA=151, DAT=NORMAL, TS1=00&00,
TA1="60", PA1=1, TB1="60", PB1=1, AGIO1=100, TS2=00&00; MOD CHGMODE:
CHA=151, DAT=DTYPE1, TS1=00&00, TA1="60", PA1=1, TB1="60", PB1=1,
AGIO1=100, TS2=00&00; MOD CHGMODE: CHA=151, DAT=DTYPE2, TS1=00&00,
TA1="60", PA1=1, TB1="60", PB1=1, AGIO1=100, TS2=00&00;
//Modify meter traffic rate record. Set the charging rate in meter table 1 to 10 cents per pulse;
set the charging rate in meter table 11 to 20 cents per pulse.
MOD MTRR: MID=METER1, RAT=10; MOD MTRR: MID=METER11, RAT=20;
//Add intra-office group charging data. The record with Charging case set to 150 is used for IP
audio services; the other record with Charging case set to 151 is used for IP video services.
ADD CHGGRP: RCHS=30, DCHS=254, LOAD=IPAUDIO, CODEC=ALL, CHA=150; ADD
CHGGRP: RCHS=30, DCHS=254, LOAD=IPVEDIO, CODEC=ALL, CHA=151;
NOTE
l To charge for IP audio services, set Bearer capability to IP audio and use the charging case 150.
l To charge for IP video services, set Bearer capability to IP video and use the charging case 151.
Related tasks
Configuration Example of Charging Data
Charging Data Commissioning
Related concepts
For details about the relations between charging data tables, see 12.5 Relations Between Billing
Data Tables.

Initial Configuration 4 Configuring Data for Subscriber Access Networking
4 Configuring Data for Subscriber Access

Networking
About This Chapter
4.1 Configuring Data to Interwork with IAD

4.2 Configuring Data to Interwork with AMG (Through MGCP/H.248)
4.3 Configuring Data to Interwork with UMG
4.4 Configuring Data to Interwork with MTA (Through NCS)

4 Configuring Data for Subscriber Access Networking Initial Configuration
4.1 Configuring Data to Interwork with IAD
4.1.1 Configuring Data to Interwork with IAD (Through MGCP/H.248)

4.1.2 Configuring Data to Interwork with IAD (Through H.323)
4.1.1 Configuring Data to Interwork with IAD (Through MGCP/H.

248)
Scenarios
An Integrated Access Device (IAD) can be connected to the SoftX3000 through an IP
metropolitan area network (MAN). In this case, the IAD provides analog subscriber line ports
of small capacity. Thus, you can provide voice services for subscribers in different locations
through the IP MAN. Figure 4-1 shows the typical networking model where an IAD adopts the
Media Gateway Control Protocol (MGCP/H.248) to interwork with the SoftX3000.
Figure 4-1 IAD adopting MGCP/H.248 to interwork with the SoftX3000
SoftX3000
SoftX3000 IAD
MGCP/H.248
MGCP H.248
MGCP/H.248 UDP TCP/SCTP

IP IP
IAD MAC MAC
User A User B User C User D
Prerequisites
Conditions

l Basic data configuration is complete.
Data
Before configuring the data on the SoftX3000, you must ensure that the settings of the key
parameters between the SoftX3000 and the IAD are consistent for interworking. Table 4-1 lists
these parameters.

Table 4-1 Data to be collected before configuring the data between the SoftX3000 and the IAD
Name Value
Protocol data Protocol type H.248 The value is -

negotiated with
the IAD.
Code type ABNF The value is It is one of the

negotiated with parameters used
the IAD. for interworking
with the media
gateway. It
specifies the
code type used
by the
transmission
protocol
between the
media gateway
and the
SoftX3000. The
option ABNF
indicates the text
format, and
ASN.1 indicates
the binary
format.
l For MGCP,
the
SoftX3000
only supports
ABNF.
l For H.248
protocol, the
SoftX3000
supports both
ABNF and
ASN.1. By
default, the
system
supports
ABNF.
The IP address Local IP 191.169.150.30/ The value is -

of the address 255.255.255.0 determined by
SoftX3000 the carrier.


Name Value
The data of the Equipment ID 211.169.150.2:2 The value is The SoftX3000

IAD 944 (H.248) determined by supports either
the carrier. format for the
equipment ID,
but the specific
format to be used
must be
negotiated with
the media
gateway side.
Otherwise, the
media gateway
may fail to
register.
Currently, the
media gateways
provided by
Huawei have the
following
formats for the
equipment ID.
l For the media
gateways
adopting
MGCP, such
as IAD,
AMG, MRS,
and MTA, the
equipment ID
is "domain
name". For
example,
huawei.com
and
iad0086.com.
l For the media
gateways
adopting H.
248 protocol,
such as IAD,
AMG, TMG
and UMG,
the
equipment ID
is "IP
address: Port
number". For
example,


Name Value
210.10.11.86
: 2944.
Remote IP 211.169.150.2/2 The value is -

address 55.255.255.0 determined by
the carrier.


Name Value
Remote port 2944(H.248) The value is It is one of the

with the media
gateway. It is
used to specify
the number of the
UDP port used
by the media
gateway to
communicate
with the
SoftX3000, that
is, the number of
the local UDP
port at the MG
side. Set it by the
following
principles:
l If the media
gateway
adopts
MGCP, the
remote port
number is
2427 by
default; If the
media
gateway
adopts H.248
protocol, the
remote port
number is
2944 by
default.
l If the media
gateway
adopts H.
248, the local
UDP port
number on
the
SoftX3000
side is 2944,
which cannot
be modified.
If the media
gateway


Name Value
adopts
MGCP, the
local UDP
port number
on the
SoftX3000
side is 2727
by default,
and you can
modify it
with the SET
MGCPPAR
A command.
l Despite the
protocol
(MGCP or H.
248) to be
adopted, the
local UDP
port number
at the media
gateway side
(that is, the
remote port
number on
the
SoftX3000
side) can be
configured
flexibly. It
can be
configured to
be the same
as, or
different
from the local
UDP port
number on
the
SoftX3000
side.
Codec list G.711A, G. The value is -

711μ, G.723.1, negotiated with
and G.729 the IAD.


Name Value
Hairpin Not Supported The value is It is one of the

connection negotiated with parameters used
with the media
gateway. It
determines
whether the
media gateway
supports hairpin
connection. By
default, the
system does not
support the
hairpin
connection
function.
l If you select
Supported,
the internal
switching
network of
the gateway
directly
implements
the media
stream
exchange
between the
internal
terminals of
the media
gateway.
However, the
external IP
packet
network still
implements
the media
stream
exchange
between
internal
terminal and
external
terminal.
l If you select
Not
Supported,


Name Value
the external
IP packet
network
implements
all the media
stream
exchanges.


Name Value
EC Supported The value is It is one of the

with the media
gateway. It
indicates
whether the
media gateway
has the Echo
Cancellation
function. By
default, the
system supports
the EC function.
The meaning of
the parameter
options are as
follows:
l If you select
Supported,
the media
gateway has
the EC
function. The
SoftX3000
can operate
the EC
resources on
the media
gateway
through the
MGCP or H.
248 protocol.
l If you select
Not
Supported,
the media
gateway does
not have the
EC function.
The
SoftX3000
cannot
operate the
EC resources
on the media
gateway
through the


Name Value
MGCP or H.
248 protocol.
NOTE
If you set the
special
attributes
parameter in the
command to No
Echo
Cancellation,
the SoftX3000
never delivers an
EC parameter
when operating
the media
gateway through
the MGCP or H.
248 protocol.
Special Detect the fax The value is -

attributes and modem negotiated with
signal tones the IAD.
Subscriber data Termination From 0 The value is -

ID negotiated with
the IAD.
Subscriber 6540010(TID is The value is -

number 0) determined by
6540011(TID is the carrier.
1)
6540012(TID is
2)
6540013(TID is
3)
Documents
Workflow
The procedure for configuring the data between the SoftX3000 and the IAD is as follows:
1. Configure the data of the Media Gateway.
2. Configure the subscriber data.
3. Configure the number analysis data.

Procedure
Step 1 Configure the data of the Media Gateway.
ADD MGW: EID="Equipment ID", GWTP=Gateway type, MGCMODULENO=FCCU/
AGCU/UACU module number, PTYPE=Protocol type, LA="Local IP address", RA1="Remote
IP address 1", RP=Remote port, LISTOFCODEC=Codec list, HAIRPIN= Hairpin connection,
EC=EC, CODETYPE=Code type, UCATT=Special attributes;
NOTE
l When the MGW is an IAD, the SoftX3000, by default, does not instruct the IAD to detect the fax and
modem signal tones of a terminal. Therefore, if a fax machine or modem is used, set the parameter
Special attributes correctly. Note that NOFX-0 indicates that the fax signal tones are to be detected.
l If the IAD adopts a dynamic IP address, the parameter Dynamic IP must be set to Support. In this
case, the value of the parameter Remote IP address 1 can be set to any valid value.
Step 2 Configure the subscriber data.

ADD VSBR: D=Subscriber number, LP=Local DN set, DID=Port type, MN=FCCU module
number, EID="Equipment ID", TID="Termination ID", CODEC=Codec prefer,
RCHS=Charging source code, CSC=Call source code, UTP=Subscriber type, NS=
Supplementary service;
NOTE
l For the IADs provided by different manufacturers, the numbering plans for the termination IDs of the
subscriber ports are different.
l To enable the CID function for ESL subscribers, select CLIP from the parameter Supplementary
service in this command.
Step 3 Configure the number analysis data.

ADD CNACLD: LP= Local DN set, PFX=Call prefix, MINL=Minimum number length,
MAXL=Maximum number length, CHSC=Charging selection code;
NOTE
l Configure a valid Charging selection code for each call prefix to guarantee reliable charging.
l The priority of the intra-office group charging mode is higher than that of the destination code charging
mode; therefore, in this example, the SoftX3000 selects the intra-office group charging mode when an
intra-office subscriber dials the intra-office prefix.
----End
Example 1
Task Description
l The interconnection is implemented through the H.248 protocol.
l Subscribers can dial each other.
l Subscribers have been provided with the CID service.
Scripts
//Add the IAD
ADD MGW: EID="211.169.150.2:2944", GWTP=IAD, MGCMODULENO=22, PTYPE=H248,
LA="190.169.150.30", RA1="211.169.150.2", RP=2944,

LISTOFCODEC=PCMA-1&PCMU-1&G7231-1&G729-1, HAIRPIN=NS, EC=TRUE,

CODETYPE=ABNF, UCATT=NOFX-0&NOM-0;
//Add the subscriber data

ADD VSBR: D=K'6540010, LP=0, DID=ESL, MN=22, EID="211.169.150.2:2944",
TID="0", CODEC=PCMA, RCHS=0, CSC=0, UTP=NRM, NS=CLIP-1;
//Add the number analysis data

ADD CNACLD: LP=0, PFX=K'654, MINL=7, MAXL=7, CHSC=0;
Example 2
Task Description
l The interconnection is implemented through the MGCP protocol.
Scripts
//Add the IAD
ADD MGW: EID="iad0086.com", GWTP=IAD, MGCMODULENO=22, PTYPE=MGCP,
LA="190.169.150.30", RA1="211.169.150.2", RP=2427,

ADD VSBR: D=K'6540010, LP=0, DID=ESL, MN=22, EID="iad0086.com", TID="0",
CODEC=PCMA, RCHS=0, CSC=0, UTP=NRM, NS=CLIP-1;

Related tasks
Commissioning the Interworking with the MGW (MGCP/H.248)
Related concepts
For the information about the relations between the subscriber data tables, see 12.3 Relations
Between Subscriber Data Tables

For the information about the relations between the number analysis data tables, see 12.4
Relations Between Number Analysis Data Tables
4.1.2 Configuring Data to Interwork with IAD (Through H.323)

Scenarios
An IAD can be connected to the SoftX3000 through an IP MAN. In this case, the IAD provides
a maximum of 48 analog subscriber line ports of small capacity. Thus, you can provide voice
services for subscribers in different locations through the IP MAN. Figure 4-2 shows the typical
networking model where an IAD adopts H.323 to interwork with the SoftX3000.
Figure 4-2 IAD adopting H.323 to interwork with the SoftX3000
SoftX3000
SoftX3000 IAD
H.323
H.323
H.323 TCP/UDP
IP
IAD MAC
Prerequisites
Conditions
Data
parameters between the SoftX3000 and the IAD are consistent for interworking. Table 4-2 lists
these parameters.

Table 4-2 Data to be collected before configuring the data between the SoftX3000 and the IAD
Name Value

determined by
the carrier.

The data of the Equipment ID shenzhen- The value is -

IAD H323IAD29-01 determined by
the carrier.


Name Value
Authorization Authorized by The value is It is one of the

type EID negotiated with parameters used
with the
multimedia
device. It
specifies the
registration/
authorization
type used by the
multimedia
device when
registering with
the SoftX3000.
The parameter
options are
described as
follows:
l No
authorization
:
Authorizatio
n is not
required.
l Authorized
by EID:
Authorizatio
n is
implemented
based on
"Equipment
ID +
Registration
password".
l Authorized
by IP:
Authorizatio
n is
implemented
based on "IP
address".
Authorization 123456 The value is -

password determined by
the carrier.

ID negotiated with
the IAD.


Name Value
Subscriber 6540020 (TID is The value is -

6540021 (TID is the carrier.
1)
6540022 (TID is
2)
6540023 (TID is
3)
Documents
Workflow
The procedure for configuring the data between the SoftX3000 and the IAD is as follows:
1. Configure the H.323 Protocol data.
Procedure
Step 1 Configure the H.323 Protocol data.
ADD H323SYS: SYSNM="System name";
ADD H323APP: MN=MSGI module number, IPDMN=IFMI module number, MTYP= MSGI
module type, CALLMINPRT= Call local minimum port value, CALLMAXPRT=Call local
maximum port value;

NOTE
l System name is the other name of the SoftX3000 used in the H.323 network. Set System name correctly;
otherwise, the SoftX3000 cannot interwork with the Gatekeeper (GK), Gateway (GW) or Multipoint
Control Unit (MCU) in the H.323 network.
l The SoftX3000 supports H.323 protocol dispatching through only one IFMI module.
l The system is equipped with only one MSGI. Therefore, the parameter MSGI module type in the
command must be set to RAS & CALL application.
l Call local minimum port value and Call local maximum port value are valid only when the MSGI
module processes call signaling. They specify the local TCP port number range available for the MSGI
module to process H.225.0 and H.245 protocols. The configuration principles are as follows:
l The minimum local port number or the maximum local port number can only be an integer from
1024 to 65535.
l It is recommended to set the local TCP port number range for each MSGI to the integral multiple
of 4000.
l It is not recommended that the local TCP port number range conflicts with other protocol TCP port
numbers in the database, for the variety of protocol messages transferred through the same FE port
(the IFMI board).
l If several MSGI modules need to process call signaling, the respective local TCP port number
ranges of the MSGI modules cannot repeat or conflict with each other.
ADD MMTE: EID="Equipment ID", IMSFLAG= IMS Flag, MN=FCCU module number, PT=
Protocol type, DT=Device type, AT= Authorization type, PASS=" Authorization password";
ADD MSBR: D= Subscriber number , LP=Local DN set, EID=" Equipment ID", TID=
Termination ID, RCHS=Charging source code, CSC=Call source code, NS=Supplementary
service;
NOTE
l When the SoftX3000 interworks with the H.323 IAD of Huawei, a subscriber's termination ID must
be set to the E.164 number (phone number) of the subscriber; otherwise, the subscriber cannot register
with the SoftX3000.
l To enable the CID function for H.323 subscribers, select CLIP from the parameter Supplementary
servicein this command.

NOTE
----End
Example
Introduction


Scripts
//Add the H.323 Protocol data

ADD H323SYS: SYSNM="SoftX3000";
ADD H323APP: MN=135, IPDMN=132, MTYP=RCAPP, CALLMINPRT=6000,
CALLMAXPRT=10000;
//Add the data of the Media Gateway

ADD MMTE: EID="shenzhen-H323IAD29-01", IMSFLAG=NO, MN=22, PT=H323,
DT=H323IAD, AT=ABE, PASS="123456";

ADD MSBR: D=K'6540020, LP=0, EID="shenzhen-H323IAD29-01",
TID="K'6540020", RCHS=0, CSC=0, UTP=NRM, NS=CLIP-1;

Related tasks
None.
Related concepts
4.2 Configuring Data to Interwork with AMG (Through

MGCP/H.248)
Scenarios
An access media gateway (AMG) can be connected to the SoftX3000 through an IP MAN. In
this case, the AMG provides analog subscriber line ports of medium capacity. (For example,
Huawei AMG5160 is able to provide a maximum of 160 ports.) Thus, you can provide voice
services for enterprise subscribers through the IP MAN. Figure 4-3 shows the typical networking
model where an AMG adopts MGCP/H.248 to interwork with the SoftX3000.

Figure 4-3 AMG adopting MGCP/H.248 to interwork with the SoftX3000
SoftX3000
SoftX3000 AMG
MGCP/H.248
MGCP H.248
MGCP/H.248 UDP TCP/SCTP

IP IP
AMG
MAC MAC
Prerequisites
Conditions
Data
parameters between the SoftX3000 and the AMG are consistent for interworking. Table 4-3
lists these parameters.
Table 4-3 Data to be collected before configuring the data between the SoftX3000 and the AMG
Name Value

negotiated with
the AMG.


Name Value
Code type ABNF The value is It is one of the

the AMG. for interworking
with the media
gateway. It
specifies the
code type used
by the
transmission
protocol
between the
media gateway
and the
SoftX3000. The
option ABNF
indicates the text
format, and
ASN.1 indicates
the binary
format.
l For MGCP,
the
SoftX3000
only supports
ABNF.
l For H.248
protocol, the
SoftX3000
supports both
ABNF and
ASN.1. By
default, the
system
supports
ABNF.



Name Value
The data of the Equipment ID 211.169.150.6:2 The value is The SoftX3000

AMG 944 (H.248) determined by supports either
the carrier. format for the
equipment ID,
but the specific
format to be used
must be
negotiated with
the media
gateway side.
Otherwise, the
media gateway
may fail to
register.
Currently, the
media gateways
provided by
Huawei have the
following
formats for the
equipment ID.
l For the media
gateways
adopting
MGCP, such
as IAD,
AMG, MRS,
and MTA, the
equipment ID
is "domain
name". For
example,
huawei.com
and
iad0086.com.
l For the media
gateways
adopting H.
248 protocol,
such as IAD,
AMG, TMG
and UMG,
the
equipment ID
is "IP
address: Port
number". For
example,


Name Value
210.10.11.86
: 2944.
Remote IP 211.169.150.6/2 The value is -

address 55.255.0.0 determined by
the carrier.


Name Value
Remote port 2944(H.248) The value is It is one of the

with the media
gateway. It is
used to specify
the number of the
UDP port used
by the media
gateway to
communicate
with the
SoftX3000, that
is, the number of
the local UDP
port at the MG
side. Set it by the
following
principles:
l If the media
gateway
adopts
MGCP, the
remote port
number is
2427 by
default; If the
media
gateway
adopts H.248
protocol, the
remote port
number is
2944 by
default.
l If the media
gateway
adopts H.
248, the local
UDP port
number at the
SoftX3000 is
2944, which
cannot be
modified. If
the media
gateway
adopts


Name Value
MGCP, the
local UDP
port number
at the
SoftX3000
side is 2727
by default,
and you can
modify it
with the SET
MGCPPAR
A command.
l Despite the
protocol
(MGCP or H.
248) to be
adopted, the
local UDP
port number
at the media
gateway side
(that is, the
remote port
number at the
SoftX3000
side) can be
configured
flexibly. It
can be
configured to
be the same
as or different
from the local
UDP port
number at the
SoftX3000
side.
Codec list G.711A, G. The value is -

711μ, G.723.1, negotiated with
G.729 the AMG.


Name Value
Hairpin Not Supported The value is It is one of the

connection negotiated with parameters used
with the media
gateway. It
determines
whether the
media gateway
supports hair pin
connection. By
default, the
system does not
support the
hairpin
connection
function.
l If you select
Supported,
the internal
switching
network of
the gateway
instead of by
the external
IP packet
network
directly
implements
the media
stream
exchange
between the
internal
terminals of
the media
gateway.
However, the
external IP
packet
network still
implements
the media
stream
exchange
between
internal
terminal and
external
terminal.


Name Value
l If you select
Not
Supported,
the external
IP packet
network
implements
all the media
stream
exchanges.


Name Value
EC Supported The value is It is one of the

with the media
gateway. It
indicates
whether the
media gateway
has the echo
cancellation
function. By
default, the
system supports
the EC function.
The meanings of
the parameter
options are as
follows:
l If you select
Supported,
the media
gateway has
the EC
function. The
SoftX3000
can operate
the EC
resources on
the media
gateway
through the
MGCP or H.
248 protocol.
l If you select
Not
Supported,
the media
gateway does
not have the
EC function.
The
SoftX3000
cannot
operate the
EC resources
on the media
gateway
through the


Name Value
MGCP or H.
248 protocol.
NOTE
If you set the
special
attributes
parameter in the
command to No
Echo
Cancellation,
the SoftX3000
never delivers an
EC parameter
when operating
the media
gateway through
the MGCP or H.
248 protocol.
Special Detect the fax The value is -

attributes and modem negotiated with
signal tones the AMG.

ID negotiated with
the AMG.
Subscriber 6540050(TID is The value is -

6540051(TID is the carrier.
1)
6540052(TID is
2)
6540053(TID is
3)
Documents
Workflow
The procedure for configuring the data between the SoftX3000 and the AMG is as follows:

Procedure
ADD MGW: EID="Equipment ID", GWTP=Gateway type, MGCMODULENO=FCCU/
AGCU/UACUmodule number, PTYPE=Protocol type, LA="Local IP address", RA1="Remote
IP address 1", RP=Remote port, LISTOFCODEC=Codec list, HAIRPIN= Hairpin connection,
EC=EC, CODETYPE=Code type, UCATT=Special attributes;
number, EID="Equipment ID", TID="Termination ID", CODEC=Codec prefer,
RCHS=Charging source code, CSC=Call source code, UTP=Subscriber type, NS=
Supplementary service;
NOTE
l To add a large number of subscribers to the AMG, run the batch command ADB VSBR. Thus, you
can improve data configuration efficiency.
l For the AMGs provided by different manufacturers, the numbering plans for the termination IDs of
the subscriber ports are different. In this example, the numbers start from 0.
service in this command.

NOTE
----End
Example
Task Description
Scripts
//Add the AMG
ADD MGW: EID="211.169.150.6:2944", GWTP=AG, MGCMODULENO=22, PTYPE=H248,
LA="190.169.150.30", RA1="211.169.150.6", RP=2944,




Related tasks
Related concepts
4.3 Configuring Data to Interwork with UMG
4.3.1 Configuring Data to Interwork with UMG8900 (Connected with RSP Subscriber Frame
Device)
4.3.2 Configuring Data to Interwork with UMG8900 (Connected with V5 AN Device)
4.3.3 Configuring Data to Interwork with UMG8900 (Connected with Wireless Access Device)
4.3.1 Configuring Data to Interwork with UMG8900 (Connected

with RSP Subscriber Frame Device)
Scenarios
When acting as an AMG, the UMG8900 can be connected to the Huawei RSP subscriber frame
device through E1. In this case, the UMG8900 provides analog or digital subscriber line ports
of large capacity. Thus, you can provide voice services and narrowband data services for
subscribers through the IP WAN. Figure 4-4 shows the typical networking model of the
UMG8900 (connected with the RSP subscriber frame device) acting as an AMG.

Figure 4-4 UMG8900 (connected with the RSP subscriber frame device) acting as an AMG
SoftX3000
IP MAN
H.248+IUA
UMG8900
Internal protocol /E1 interface
RSP subscriber frame
Subscriber A Subscriber B Subscriber C Subscriber D
As shown in Figure 4-4, the RSP subscriber frame is invisible to the SoftX3000. That is, when
you configure data on the SoftX3000 side, consider the UMG8900 and the RSP subscriber frame
as an AMG device that adopts H.248.
Prerequisites
Conditions

l You have successfully logged in to the LMT.
Data
Before configuring data on the SoftX3000 side, ensure that the parameters in Table 4-4 are
consistent between the SoftX3000 and the UMG8900.
Table 4-4 Data to be collected before configuring the data between the SoftX3000 and the
UMG8900
Catego Parameter Name Example How to Description

ry Obtain
MGW Protocol used for H.248 - -

Data interworking between the
SoftX3000 and the
UMG8900


ry Obtain
H.248 code type ASN.1 (binary - The H.248

mode) protocol of the
UMG8900
supports only
the binary
format.
Therefore,
Code type
must be set to
ASN.1.
IP address of the IFMI of 191.169.150.30/ It is planned by -

the SoftX3000 255.255.0.0 carriers.
H.248 IP address of the 211.169.150.7/2 It is planned by -

UMG8900 55.255.0.0 carriers.
SIGTRAN IP address of 211.169.150.8/2 It is planned by -

the UMG8900 55.255.0.0 carriers.
Local UDP port number 2944 It is planned by -

of H.248 on the carriers.
SoftX3000 side

of H.248 on the carriers.
UMG8900 side
Numbering plan of Starting from 0 It is planned by -

termination ID (RSP carriers.
subscriber port) of the
UMG8900
Speech codecs supported G.711A, G.711μ, - -

by the UMG8900 G.723.1, G.729
Whether the UMG8900 Yes - The UMG8900

supports hairpin supports the
connection hairpin
connection
function.
Therefore, set
Hairpin
connection to
Supported.
Whether the UMG8900 Yes - The UMG8900

supports the EC function supports EC,
fax, and
modem
functions.
Therefore, use


ry Obtain
Whether the UMG8900 Yes - the default

supports the detection of values of the
fax and modem signal options EC,
tones No Fax and No
Modem in the
Whether the UMG8900 Yes - parameter
supports the T.38 protocol Special
attributes and
set EC to the
default value.
IUA Local SCTP port number IUA link 0: 9900 It is planned by -

Data of IUA links on the IUA link 1: 9901 carriers.
SoftX3000 side (client)
Local SCTP port number 9900 It is planned by -

of IUA links on the carriers.
UMG8900 side (server)
Traffic mode of IUA links Load sharing It is planned by l Set Traffic

between the SoftX3000 mode carriers. mode to
and the UMG8900 Load-
sharing for
a linkset,
unless
specified
otherwise.
l The traffic
mode of the
linkset
must be
consistent
with that on
the SG side.
Otherwise,
none of the
IUA links
of the
linkset
works
normally.
Documents
Before configuring the local office data, you must plan the related data according to the
requirements in the Specifications for Data Configuration provided by the Global Technical
Service Department of Huawei.

Workflow
The procedure for configuring the data between the SoftX3000 and the UMG8900 (Connected
with RSP Subscriber Frame Device) is as follows:
1. Configure MGW Data.
2. Configure IUA Data.
Procedure
Step 1 Configure MGW Data.
ADD MGW: EID=Equipment ID, GWTP=Gateway type, MGWDESC=MGW description,
MGCMODULENO=FCCU/AGCU module number, PTYPE=Protocol type, LA=Local IP
address, RA1=Remote IP address 1, RP= Remote port, HAIRPIN=Hairpin connection,
CODETYPE=Code type, ET=Encryption type, SUPROOTPKG=Root Packge;
NOTE
l Regardless of whether the UMG8900 acts as an AG or a TG, the format of the parameter Equipment
ID must be "IP address:port number", and Gateway Type must be set to UMGW.
l You must set Remote IP address 1 to the IP address of the UMG8900 used for H.248, that is
211.169.150.7.
Step 2 Configure IUA Data.

1. Configure embedded SG
ADD SG: SGID=SG ID, SGNAME=SG name, SGTYPE=SG type, EID=Equipment ID;
2. Configure IUA linkset
ADD IUALKS: LSX=Linkset index, LSNAME=Linkset name, TM= Traffic mode,
DT=Device type, MN=FCCU module number, SGID=Signaling gateway ID;
3. Configure IUA link
ADD IUALNK: MN=BSGI module number, LNKN=Link number, LSX=Linkset index,
LOCPORT=Local port, LOCIP1=Local IP address 1, PEERIP1=Peer IP address 1;
NOTE
l You must set Peer IP address 1 to the IP address of the UMG8900 used for SIGTRAN.
l If the system is configured with two BSGI modules, allocate the two IUA links to each of them.
This guarantees reliability of the IUA links.
----End
Example
Introduction
In this example, you must configure data on the SoftX3000 side to meet the following
requirements:
Two IUA links are configured between the SoftX3000 and the UMG8900 for carrying the DSS1
signaling services in load sharing mode.
Scripts
//Configure MGW Data.

ADD MGW: EID="211.169.150.7:2944", GWTP=UMGW, MGWDESC="shenzhen-

UMG8900-01", MGCMODULENO=22, LA="191.169.150.30", RA1="211.169.150.7",
RP=2944, LISTOFCODEC=PCMA-1&PCMU-1&G7231-1&G729-1&T38-1, HAIRPIN=S,
CODETYPE=ASN;
//Configure IUA Data.

ADD SG: SGID=1, SGNAME="IUA SG", SGTYPE=emb, EID="211.169.150.7:2944";
ADD IUALKS: LSX=1, LSNAME="IUA LinkSet 1", TM=LOADSHARE, DT=BRA, MN=22,
SGID=1;
ADD IUALNK: MN=136, LNKN=0, LSX=1, LOCPORT=9900, LOCIP1="191.169.150.30",
PEERIP1="211.169.150.8";
PEERIP1="211.169.150.8";
Related tasks
Commissioning the Interworking with Other Networks (PRA)
Related concepts
None.

with V5 AN Device)
Scenarios
When acting as an AMG, the UMG8900 can be connected to the standard V5 AN device through
E1. In this case, the UMG8900 provides analog or digital subscriber line ports of large capacity.
Thus, you can provide voice services for subscribers through the IP WAN. Figure 4-5 shows
the typical networking model of the UMG8900 (connected with the V5 AN device) acting as an
AMG.

Figure 4-5 UMG8900 (connected with the V5 AN device) acting as an AMG
SoftX3000
IP MAN
H.248+V5UA
UMG8900
V5/E1 interface
V5 AN device
As shown in Figure 4-5, the SoftX3000 provides V5UA links to connect with the UMG8900.
Through the UMG8900 (with embedded SG functions), the SoftX3000 exchanges V5 signaling
with the V5 AN device. The SoftX3000 controls the UMG8900 to convert voice media streams.
Prerequisites
Conditions
Data
consistent between the SoftX3000 and the UMG8900, and the parameters in Table 4-6 are
consistent between the SoftX3000 and the V5 AN device.

UMG8900
Category Parameter Name Example How to Descriptio
Obtain n
MGW Protocol used for interworking H.248 - -

Data between the SoftX3000 and the
UMG8900
H.248 code type ASN.1 - The H.248

(binary protocol of
mode) the
UMG8900
supports
only the
binary
format.
Therefore,
Code type
must be set
to ASN.1.
IP address of the IFMI of the 191.169.150 It is planned -

SoftX3000 . by carriers.
30/255.255.
0.0
H.248 IP address of the 211.169.150 It is planned -

UMG8900 . by carriers.
9/255.255.0.
0
SIGTRAN IP address of the 211.169.150 It is planned -

UMG8900 . by carriers.
10/255.255.
0.0
Local UDP port number of H. 2944 It is planned -

248 on the SoftX3000 side by carriers.
Local UDP port number of H. 2944 It is planned -

248 on the UMG8900 side by carriers.
Speech codecs supported by the G.711A, G. - -

UMG8900 711μ, G.
723.1, G.729


Obtain n
Whether the UMG8900 supports Yes It is planned The

hairpin connection by carriers. UMG8900
supports the
hairpin
connection
function.
Therefore,
set Hairpin
connection
to
Supported.
Whether the UMG8900 supports Yes It is planned The

the EC function by carriers. UMG8900
supports EC,
Whether the UMG8900 supports Yes It is planned fax, and
the detection of fax and modem by carriers. modem
signal tones functions.
Whether the UMG8900 supports Yes It is planned Therefore,
the T.38 protocol by carriers. use the
default
values of the
options EC,
No Fax and
No Modem
in the
parameter
Special
attributes .
E1 numbering plan on the Starting It is planned -

UMG8900 side from 0 by carriers.
Numbering plan of termination Starting It is planned -

ID (E1 timeslot) of the from 0 by carriers.
UMG8900
V5UA Local SCTP port number of V5UA link It is planned -

Data V5UA links on the SoftX3000 0: 5675 by carriers.
side (client) V5UA link
1: 5676
Local SCTP port number of 5675 It is planned -

V5UA links on the UMG8900 by carriers.
side (server)


Obtain n
Traffic mode of V5UA links Load sharing It is planned l Set

between the SoftX3000 and the mode by carriers. Traffic
UMG8900 mode to
Load-
sharing
for a
linkset,
unless
specified
otherwis
e.
l The
traffic
mode of
the
linkset
must be
consisten
t with that
on the SG
side.
Otherwis
e, none of
the IUA
links of
the
linkset
works
normally
.


Obtain n
V5 Trunk E1 number of the V5 trunk group 0-1 It is planned Start E1

Data on the SoftX3000 side by carriers. number and
End E1
number are
the universal
logical
numbers of
E1 trunk
circuits, such
as SS7, PRA,
R2, and V5,
in an FCCU
module. The
physical
numbers of
the E1 trunk
circuits on
the
UMG8900
side are
defined by
Start MG
E1 ID.
E1 link ID corresponding to the 0-1 - V5UA

V5 trunk group on the linkset
UMG8900 side number is
one of the
parameters
used for
interworking
between the
SoftX3000
and the V5
AN device.
NOTE
The V5.2 protocol applies different encapsulation methods to L3 addresses of PSTN and ISDN subscribers.
Therefore, L3 addresses of PSTN and ISDN subscribers in the same V5 trunk group are numbered
separately. This means that the numbers can be the same for L3 addresses of PSTN and ISDN subscribers.

Table 4-6 Data to be collected before configuring the data between the SoftX3000 and the V5
AN device
Category Parameter Name Example How to Description

Obtain
V5 Interface V5 interface type V5.2 interface - -

Data
V5 interface ID 5678 It is planned by -
carriers.
V5 link ID of the start E1 15 It is planned by -

carriers.
Primary link circuit 16 It is planned by -

number (on the carriers.
SoftX3000 side)
Termination ID of the 16 It is planned by -

primary link circuit carriers.
number (on the
UMG8900 side)
Logical C-channel ID of 12345 It is planned by -

the primary link carriers.
Secondary link circuit 48 It is planned by -

number (on the carriers.
SoftX3000 side)
Termination ID of the 48 It is planned by -

secondary link circuit carriers.
number (on the
UMG8900 side)
Protection group type Protection It is planned by -

group 1 carriers.
Documents
Workflow
The procedure for configuring the data between the SoftX3000 and the UMG8900(Connected
with V5 AN Device) is as follows:
2. Configure V5UA Data.
3. Configure V5 Trunk Data.
4. Configure V5 Interface Data.

Procedure
NOTE
l You must set Remote IP address 1 to the IP address of the UMG8900 used for H.248, that is,
211.169.150.9.
Step 2 Configure V5UA Data.

2. Configure V5UA linkset
ADD V5UALKS: LSX=Linkset index, LSNAME=Linkset name, TM=Traffic mode,
SGID=Signaling gateway ID;
NOTE
l Set Traffic mode to Load-sharing for a linkset, unless specified otherwise.

l The traffic mode of the linkset must be consistent with that on the SG side. Otherwise, none of
the V5UA links of the linkset works normally.
3. Configure V5UA link
ADD V5UALNK: MN=BSGI module number, LNKN=Link number, LSX=Linkset index,
LOCPORT=Local port number, LOCIP1=Local IP address 1, PEERPORT=Peer port
number, PEERIP1=Peer IP address 1;
NOTE
l You must set Peer IP address 1 to the IP address of the UMG8900 used for SIGTRAN, that is,
211.169.150.10.
l If the system is configured with two BSGI modules, allocate the two V5UA links to each of them.
Step 3 Configure V5 Trunk Data.

1. Configure V5 trunk group
ADD V5TG: TGID=Trunk group number, MGEID=Equipment ID, TGN=Trunk group
name;
2. Configure V5 trunk circuit
ADD V5TKC:MN=FCCU module number, SEN=Start E1 number, EEN=End E1 number,
TGID=Trunk group number, SLNKID=Start E1 link ID, LNKS=V5UA linkset number,
TID=Start MG termination ID, SMGEID=Start MG E1 link ID;
NOTE
The absolute value of the difference between the start circuit number (0) and the start termination ID must
be a multiple of 32, such as 0, 32, 64, and 96.
Step 4 Configure V5 Interface Data.

ADD V5I: V5IID=V5 interface ID, TGID=Trunk group number, PNUM=Primary link circuit
number, MID=Primary link logical C-channel ID, IFTP=Interface type, BS=Protection group
type, SNUM=Secondary link circuit number;
----End
Example
Introduction
requirements:
l Two E1 channels (two V5 links) are configured between the SoftX3000 and the V5 AN
device through the UMG8900.
l Two V5UA links are configured between the SoftX3000 and the UMG8900 for carrying
the V5 signaling services in load sharing mode.
Scripts

CODETYPE=ASN;
//Configure V5UA Data.

ADD SG: SGID=5, SGNAME="V5UA SG", SGTYPE=emb, EID="211.169.150.9:2944";
ADD V5UALKS: LSX=0, LSNAME="V5UA LinkSet", TM=LOADSHARE, SGID=5;
ADD V5UALNK: MN=136, LNKN=0, LSX=0, LOCPORT=5675,
LOCIP1="191.169.150.30", PEERPORT=5675, PEERIP1="211.169.150.10";
LOCIP1="191.169.150.30", PEERPORT=5676, PEERIP1="211.169.150.10";
//Configure V5 Trunk Data.

ADD V5TG: TGID=5, MGEID="211.169.150.9:2944", TGN="V5TG";
ADD V5TKC: MN=22, SEN=0, EEN=1, TGID=5, SLNKID=15, LNKS=0, TID="0",
SMGEID=0;
//Configure V5 Interface Data.

ADD V5I: V5IID=5678, TGID=5, PNUM=16, MID=12345, IFTP=V52, BS=B1, SNUM=48;
Related tasks
Commissioning the Interworking with Other Networks (V5)
Related concepts
For the information about the relations between the local office data tables, see
l 12.6.3 Relations Between V5UA Signaling Data Tables
l 12.8.5 Relations Between V5 Trunk Circuit Data Tables


with Wireless Access Device)
Scenarios
When acting as an AMG, the UMG8900 communicates with wireless access devices through
the A+ interface. The UMG8900 is used to provide ports for mobile subscribers so that carriers
can provide voice services for mobile subscribers through the IP MAN. Figure 4-6 shows the
typical networking model of the UMG8900 (connected with the wireless access device) acting
as an AMG.
Figure 4-6 UMG8900 (connected with the wireless access device) acting as an AMG
SoftX3000
H.248/V5UA
UMG8900
A+
RAC6610
Abis
BTS3606
Um
Mobile Mobile
Subscriber A Subscriber B
As shown in Figure 4-6, the SoftX3000 provides V5UA links to connect with the UMG8900.
Through the UMG8900 (with embedded SG functions), the SoftX3000 communicates with the
wireless access device. The SoftX3000 controls the UMG8900 to convert voice media streams.

Prerequisites
Conditions
Data
consistent between the SoftX3000 and the wireless access device.
UMG8900
Categor Parameter Example How to Obtain Description
y Name
MGW Protocol used H.248 - -

Data for
interworking
between the
SoftX3000 and
the UMG8900
H.248 code ASN.1 (binary - The H.248

type mode) protocol of the
UMG8900
supports only the
binary format.
Therefore, Code
type must be set to
ASN.1.
IP address of 191.169.150.30/25 It is planned by -

the IFMI of the 5.255.0.0 carriers.
SoftX3000
H.248 IP 211.169.150.9/255 It is planned by -

address of the .255.0.0 carriers.
UMG8900
SIGTRAN IP 211.169.150.10/25 It is planned by -

address of the 5.255.0.0 carriers.
UMG8900
Local UDP port 2944 It is planned by -

number of H. carriers.
248 on the
SoftX3000 side

number of H. carriers.
248 on the
UMG8900 side


y Name
Speech codecs G.711A, G.711μ, - -

supported by G.723.1, G.729
the UMG8900
Whether the Yes It is planned by The UMG8900

UMG8900 It is planned by carriers. supports the
supports carriers. hairpin connection
hairpin function.
connection Therefore, set
Hairpin
connection to
Supported.
Whether the Yes It is planned by The UMG8900

UMG8900 carriers. supports EC, fax,
supports the EC and modem
function functions.
Therefore, use the
Whether the Yes It is planned by default values of
UMG8900 carriers. the options EC, No
supports the Fax and No
detection of fax Modem in the
and modem parameter Special
signal tones attributes and set
Whether the Yes It is planned by EC to the default
UMG8900 carriers. value.
supports the T.
38 protocol
E1 numbering Starting from 0 It is planned by -

plan on the carriers.
UMG8900 side
Numbering Starting from 0 It is planned by -

plan of carriers.
termination ID
(E1 timeslot) of
the UMG8900
V5UA Local SCTP V5UA link 0: 5675 It is planned by -

Data port number of V5UA link 1: 5676 carriers.
V5UA links on
the SoftX3000
side (client)
Local SCTP 5675 It is planned by -

port number of carriers.
V5UA links on
the UMG8900
side (server)


y Name
Traffic mode of Load sharing mode It is planned by l Set Traffic

V5UA links carriers. mode to Load-
between the sharing for a
SoftX3000 and linkset, unless
the UMG8900 specified
otherwise.
l The traffic
mode of the
linkset must be
consistent with
that on the SG
side.
Otherwise,
none of the
IUA links of
the linkset
works
normally.
V5 Trunk E1 number of 0-1 It is planned by Start E1 number

Data the V5 trunk carriers. and End E1
group on the number are the
SoftX3000 side universal logical
numbers of E1
trunk circuits, such
as SS7, PRA, R2,
and V5, in an
FCCU module.
The physical
numbers of the E1
trunk circuits on
the UMG8900 side
are defined by
Start MG E1 ID.
E1 link ID 0-1 It is planned by V5UA linkset

corresponding carriers. number is one of
to the V5 trunk the parameters
group on the used for
UMG8900 side interworking
between the
SoftX3000 and the
V5 AN device.

wireless access device
Categ Parameter Example How to Obtain Description
ory Name
A+ Interface type V5.2 - -

Interfac interface
e Data
Interface ID 0 It is planned by carriers. -
Link ID of the 15 It is planned by carriers. -

start E1
Primary link 16 It is planned by carriers. -

circuit number
(on the
SoftX3000 side)
Termination ID 16 It is planned by carriers. -

of the primary
link circuit
number (on the
UMG8900 side)
Logical C- 0 It is planned by carriers. -

channel ID of the
primary link
Protection group - It is planned by carriers. -

type
Documents
Workflow
The procedure for configuring the data between the SoftX3000 and the UMG8900 (Connected
with Wireless Access Device) is as follows:
2. Configure V5UA Data.
3. Configure V5 Trunk Data.
4. Configure A+ Interface Data.
Procedure


NOTE
l Irrespective of whether the UMG8900 acts as an AG or a TG, the format of the parameter Equipment
211.169.150.9.
Step 2 Configure V5UA Data.

2. Configure V5UA linkset
ADD V5UALKS: LSX=Linkset index, LSNAME=Linkset name, TM=Traffic mode,

NOTE

the V5UA links of the linkset works normally.
3. Configure V5UA link
ADD V5UALNK: MN=BSGI module number, LNKN=Link number, LSX=Linkset index,

LOCPORT=Local port number, LOCIP1=Local IP address 1, PEERPORT=Peer port
number, PEERIP1=Peer IP address 1;
NOTE
l You must set Peer IP address 1 to the IP address of the UMG8900 used for SIGTRAN, that is,
211.169.150.10.
l If the system is configured with two BSGI modules, allocate the two V5UA links to each of them.
Step 3 Configure V5 Trunk Data.

1. Configure V5 trunk group
ADD V5TG: TGID=Trunk group number, MGEID=Equipment ID, TGN=Trunk group

name;
2. Configure V5 trunk circuit
ADD V5TKC: MN=FCCU module number, SEN=Start E1 number, EEN=End E1 number,

TGID=Trunk group number, SLNKID=Start E1 link ID, LNKS=V5UA linkset number,
TID=Start MG termination ID, SMGEID=Start MG E1 link ID;
NOTE
The absolute value of the difference between the start circuit number (0) and the start termination ID must
be a multiple of 32, such as 0, 32, 64, and 96.
Step 4 Configure A+ Interface Data.
ADD V5I: V5IID=V5 interface ID, TGID=Trunk group number, PNUM=Primary link circuit
number, MID=Primary link logical C-channel ID, IFTP=Interface type, BS=Protection group
type, SNUM=Secondary link circuit number, SCA=Special Call Attribute, TYPE=Interface WS
Type, GRPNO=GRPNO;

NOTE
l When configuring the A+ interface, you must select A_PLUS and CBA for Special Call Attribute.
l When configuring the A+ interface, you must configure RAC group number. The V5 interface IDs
configured for different office directions must be unique. The V5 interface IDs configured on the same
SoftX3000 must be unique too.
l You can configure multiple A+ interface groups between the SoftX3000 and the RAC.
----End
Example
Introduction
requirements:
l Two E1 channels are enabled between the SoftX3000 and the wireless access device
through the UMG8900.
l Two V5UA links are enabled between the SoftX3000 and the UMG8900 for bearing A+
interface services in load sharing mode.
Scripts

CODETYPE=ASN, ET=NO;
//Configure V5UA Data.

ADD SG: SGID=5, SGTYPE=emb, EID="211.169.150.9:2944";
ADD V5UALKS: LSX=0, LSNAME="V5UA LinkSet", SGID=5;
LOCIP1="191.169.150.30", PEERIP1="211.169.150.10";
LOCIP1="191.169.150.30", PEERIP1="211.169.150.10";
//Configure V5 Trunk Data.

ADD V5TG: TGID=5, MGEID="211.169.150.9:2944";
ADD V5TKC: MN=22, SEN=0, EEN=1, TGID=5, SLNKID=15, LNKS=0, TID="0",
SMGEID=0;
//Configure A+ Interface Data.

ADD V5I: V5IID=0, TGID=5, PNUM=16, MID=0, BS=NONE, SCA=CBA-1, TYPE=APLUS,
GRPNO=0;
Related tasks
Related concepts

l 12.6.3 Relations Between V5UA Signaling Data Tables

l 12.8.5 Relations Between V5 Trunk Circuit Data Tables
4.4 Configuring Data to Interwork with MTA (Through

NCS)
Scenarios
The media terminal adapter (MTA) is used to transmit data, voice and video services to the IP
packet network through the cable network. It is an access device loaded with the Network-Based
Call Signaling (NCS) protocol. The NCS is developed and extended from MGCP.
There are two types of MTAs:
l SMTA: It is connected to the cable modem through a network cable.
l EMTA: It is built in the cable modem.
In actual application, the EMTA is often used, as shown in Figure 4-7.
Figure 4-7 MTA adopting NCS to interwork with the SoftX3000
SoftX3000
IP MAN
DNS OSS
CMTS
HFC
Network
NCS
EMTA
Subscriber A Subscriber B
Devices are connected to the system through cables. Therefore, to enable ordinary phones to
connect to the IP MAN through the EMTA, you must configure the cable modem terminal system

(CMTS), the domain name server (DNS), and the operating support system (OSS) for the
networking as show in Figure 4-7. When searching for the call agent (the SoftX3000), the EMTA
needs to obtain the IP address of the call agent by resolving the DNS domain name of the call
agent.
Prerequisites
Conditions

Data
consistent between the SoftX3000 and the MTA.
Table 4-9 Data to be collected before configuring the data between the SoftX3000 and the MTA

Obtain
MGW Data Protocol used for NCS - -

interworking between
the SoftX3000 and the
MTA
IP address of the IFMI of 191.169.150.3 It is planned by -

the SoftX3000 0/255.255.0.0 carriers.
IP address of the MTA 211.169.150.3 It is planned by -

/255.255.0.0 carriers.
Domain name of the shenzhen- It is planned by -

MTA mta003-01.co carriers.
m

of NCS on the carriers.
SoftX3000 side

of NCS on the MTA side carriers.
Interface name of the aaln It is planned by -

MTA carriers.
Numbering plan of Starting from 1 It is planned by -

termination ID carriers.
(subscriber port) of the
MTA
Speech codecs G.711A, G. - -

supported by the MTA 711μ, G.723.1,
G.729


Obtain
Whether the MTA No It is planned by -

supports hairpin carriers.
connection
Whether the MTA Yes It is planned by -

supports the EC function carriers.
Whether the MTA Yes It is planned by -

supports the detection of carriers.
fax and modem signal
tones
Whether the MTA No It is planned by -

supports the T.38 carriers.
protocol
Subscriber Phone number of 6540201 It is planned by -

Data subscriber A (whose carriers.
termination ID is 1)
Phone number of 6540202 It is planned by -

subscriber B (whose carriers.
termination ID is 2)
Documents
Workflow
The procedure for configuring the data between the SoftX3000 and the MTA is as follows:

2. Configure Subscriber Data.
3. Configure Number Analysis Data.
Procedure
1. Configure CMTS
ADD CMTS: CMTSI=CMTS Index, CMTSID=CMTS Identify, CMTSI=CMTS IP

address;
2. Configure COPS Link

ADD COPSLNK: COPSLINKNO=COPSLink Index, MSGMNO=MSG Module

Number,CMTSI=CMTS Index, IFMMNO=IFM Module Number, LOCALPORT=Local
Port;
3. Configure Media Gateway
ADD MGW: EID=Equipment ID, GWTP=Gateway type, MGWDESC=MGW
description, MGCMODULENO=FCCU/AGCU module number, PTYPE=Protocol type,
LA=Local IP address, RA1=Remote IP address 1, RP= Remote port, ET=Encryption type,
SUPROOTPKG=Root Packge;
NOTE
l The NCS protocol is extended based on MGCP. Therefore, if the MGW is an MTA, Protocol type
must be set to MGCP, and Equipment ID must be set to a domain name. You are advised to set the
domain name in the format of "office name-MGW type-number". In the given example, Equipment
ID is set to shenzhen-mta003-01.com.
l When the gateway is an AG or an IAD, the default value of TDM termination ID prefix index is 2.
It indicates that the TDM termination ID (the interface name) is the default value aaln/.
Step 2 Configure Subscriber Data.

number, EID=Equipment ID, TID=Termination ID, CODEC=Codec prefer, RCHS=Charging
source code, CSC=Call source code, NS=Supplementary service;
NOTE
l For the MTAs provided by different manufacturers, the numbering plans for the termination IDs of the
subscriber ports are different. In the given example, the numbers start from 1.
service.
Step 3 Configure Number Analysis Data.

ADD CNACLD: PFX=Call prefix, MINL=Minimum number length, MAXL=Maximum
number length, CHSC=Charging selection code, EA=Enhanced attribute,
SDESCRIPTION=Description;
NOTE
Configure a valid Charging selection code for each call prefix to guarantee reliable charging.
----End
Example
Introduction
In the this example, you must configure data on the SoftX3000 side to meet the following
requirements:
l All the subscribers can call each other.
l All the subscribers are configured with the CID function.
Scripts
ADD CMTS: CMTSI=0, CMTSID="motorola", IP="191.150.1.33";
ADD COPSLNK: COPSLINKNO=0, MSGMNO=136, CMTSI=0, IFMMNO=132,
LOCALPORT=3000;

ADD MGW: EID="shenzhen-mta003-01.com", GWTP=MTA, MGWDESC="mta003-01",

MGCMODULENO=22, PTYPE=MGCP, LA="191.169.150.30", RA1="211.169.150.3",
RP=2427, LISTOFCODEC=PCMA-1&PCMU-1&G723-1&G729-1, UCATT=NOFX-0&NOM-0,
ET=NO, CMTSIDX=0, MEDSSEC=TRUE, SUPROOTPKG=NS;
//Configure Subscriber Data.

ADD VSBR: D=K'6540201, LP=0, DID=ESL, MN=22, EID="shenzhen-
mta003-01.com", TID="1", CODEC=PCMA, RCHS=65, CSC=0, NS=CLIP-1;
ADD VSBR: D=K'6540202, LP=0, DID=ESL, MN=22, EID="shenzhen-
mta003-01.com", TID="2", CODEC=PCMA, RCHS=65, CSC=0, NS=CLIP-1;
//Configure Number Analysis Data.

ADD CNACLD: PFX=K'654, MINL=7, MAXL=7, CHSC=0, EA=NO,
SDESCRIPTION="Office_654";
Related tasks
Related concepts
l 12.3 Relations Between Subscriber Data Tables
l 12.4 Relations Between Number Analysis Data Tables

Initial Configuration 5 Configuring Data to Interwork with MRS
5 Configuring Data to Interwork with MRS
About This Chapter
5.1 Configuring Data to Interwork with Embedded MRS

5.2 Configuring Data to Interwork with MRS6100
5.3 Configuring Data to Interwork with MRFP6600

5 Configuring Data to Interwork with MRS Initial Configuration
5.1 Configuring Data to Interwork with Embedded MRS

Scenarios
In the actual deployment, all boards of the embedded MRS occupy a frame exclusively. In normal
cases, the embedded MRS is in frame 3 in the ICC. Figure 5-1 shows the embedded MRS
configuration when two MRCA boards are configured.
Figure 5-1 Configuration of an embedded MRS

Back boards
M M S H S H U U
R R I S I S P P
I I U C U C W W
A A I I I I R R
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
M M S S U U
R R M M P P
C C U U W W
A A I I R R
Front boards
Prerequisites
Conditions
Data
consistent between the SoftX3000 and the embedded MRS.
embedded MRS

Obtain
Data on the Protocol used for MGCP - -

Embedded interworking between
MRS Side the SoftX3000 and the
(Including MRS
Equipment
Data and


Obtain
MGC MGCP code type ABNF (text - -

Data) format)
IP address of the IFMI 191.169.150.30 It is planned by -

of the SoftX3000 /255.255.0.0 carriers.

number of MGCP on carriers.
the SoftX3000 side

the embedded MRS
Whether the embedded Yes It is planned by -

MRS supports the EC carriers.
function

supported by the 711μ, G.723.1,
embedded MRS G.729A
Internal IP address of 172.20.200.212 It is planned by -

the MRCA in slot 0 /255.255.0.0 carriers.
Domain name of the mrc212.huawei It is planned by -

MRCA in slot 0 .com carriers.
Interface name of the ms/cnf It is planned by -

MRCA in slot 0 carriers.
Internal IP address of 172.20.200.213 It is planned by -

the MRCA in slot 1 /255.255.0.0 carriers.
Domain name of the mrc213.huawei It is planned by -

MRCA in slot 1 .com carriers.

MRCA in slot 1 carriers.
IP address of the MRP 191.169.150.20 It is planned by -

lower-subboard in slot 1/255.255.0.0 carriers.
0

upper-subboard in slot 2/255.255.0.0 carriers.
0

lower-subboard in slot 3/255.255.0.0 carriers.
1


Obtain

upper-subboard in slot 4/255.255.0.0 carriers.
1
Default route address 191.169.150.25 It is planned by -

of the MRP subboard 3 carriers.
Documents
Workflow
The procedure for configuring the data between the SoftX3000 and the Embedded MRS is as
follows:
1. Configure Data on the Embedded MRS Side (Including Equipment Data and MGC Data).
2. Configure Data on the SoftX3000 Side (MRS Resource Data).
Procedure
Step 1 Configure Data on the Embedded MRS Side (Including Equipment Data and MGC Data).
1. Configure Frame.
ADD FRM: FN=Frame number, SHN=Shelf number, PN=Position number;

2. Configure MRCA Board.
ADD BRD: FN=Frame number, SLN=Slot number, LOC=Location, FRBT=Back Board

type, MN=Module number, ASS=Assistant board slot number;
NOTE
The MRCA board cannot work in active/standby mode. Therefore, Assistant board slot number
must be set to 255.
3. Configure MRC Configuration.
ADD MRCCFG: MN=MRCA module number, DFL=Default language, MGCP=MGC

port, MRCP=MRC port, MRCDN=MRC domain name, MGCIP4=MGC IPv4 address,
MGCMODULENO=FCCU module number, INTERFACENAME=TDM termination ID
prefix index, CAPABILITY=Resource capability, LISTOFCODEC=Codec list;
NOTE
l The IP address of the MGC must be that of the FE port on the mapping IFMI board.
l In actual networking, one MRCA board is the same as an MRS. Therefore, configure data for each
MRCA board.
l In this command, the default value of TDM termination ID prefix index is 3. This indicates that the
TDM termination ID (the interface name) is the default value ms/cnf/.

4. Configure MRP Configuration.

ADD MRPCFG: MBID=MRCA module number, BID=MRP board location, MIP=MRP
IP address, IPM=MRP IP mask, MRPDR=MRP default router address;
NOTE
l Guarantee that all MRP subboards are connected to the network normally.
l Configure a unique IP address for each MRP subboard.
l Set the IP address of the default router (gateway) of the MRP subboard correctly. Otherwise, the
embedded MRS cannot play announcements normally.
5. Configure MRC Voice File.
ADD MRCV: FN=Voice file name, UMF=Upload to MRP flag;
NOTE
Hundreds of voices files are to be loaded. A large number of script files are compiled when loading
voice files to the embedded MRS by running ADD MRCV. To prevent errors and save time, the
SoftX3000 has preset the mapping script files in the path D:\Data\voice on the BAM hard disk. You
can use the script files directly for data configuration. To load all voice files to the embedded MRS,
use the file mrc all voice file script.txt.
Step 2 Configure Data on the SoftX3000 Side (MRS Resource Data).

ADD TONEID: EID=Equipment ID, TONEID=Tone ID, FILENAME=File name;
NOTE
By default, the system adds the mapping table (33 records) for the commonly-used tone IDs and voice files
after you run ADD MRCCFG to add an MRC. To add the mapping between all tone IDs and voice files,
run the script mentioned in the section earlier.
----End
Example
Introduction
requirements:
l The SoftX3000 can support basic tones and supplementary service announcements.
l The SoftX3000 can support announcement playing and digit collection functions for IN
services.
Scripts
//Configure Data on the Embedded MRS Side (Including Equipment Data and MGC Data).
ADD FRM: FN=1, SHN=0, PN=3;
ADD BRD: FN=1, SLN=0, LOC=FRONT, FRBT=MRCA, MN=212, ASS=255;
ADD BRD: FN=1, SLN=1, LOC=FRONT, FRBT=MRCA, MN=213, ASS=255;
ADD MRCCFG: MN=212, DFL=CHI, MGCP=2727, MRCP=2427,

MRCDN="mrc212.huawei.com", MGCIP4="191.169.150.30", MGCMODULENO=22,
CAPABILITY=TONE-1&PA-1&SENDDTMF-1&DETECTDTMF-1&MPTY-1,
LISTOFCODEC=PCMA-1&PCMU-1&G7231-1;
ADD MRCCFG: MN=213, DFL=CHI, MGCP=2727, MRCP=2427,
MRCDN="mrc213.huawei.com", MGCIP4="191.169.150.30", MGCMODULENO=22,
CAPABILITY=TONE-1&PA-1&SENDDTMF-1&DETECTDTMF-1&MPTY-1,

LISTOFCODEC=PCMA-1&PCMU-1&G7231-1;
ADD MRPCFG: MBID=212, BID=LMRPB, MIP="191.169.150.201",

IPM="255.255.0.0", MRPDR="191.169.150.253";
ADD MRPCFG: MBID=212, BID=UMRPB, MIP="191.169.150.202",
IPM="255.255.0.0", MRPDR="191.169.150.253";
ADD MRPCFG: MBID=213, BID=LMRPB, MIP="191.169.150.203",
IPM="255.255.0.0", MRPDR="191.169.150.253";
ADD MRPCFG: MBID=213, BID=UMRPB, MIP="191.169.150.204",
IPM="255.255.0.0", MRPDR="191.169.150.253";
//Load voice files to the embedded MRS. (The loaded files are part of
voice files.)
ADD MRCV: FN="HWF0010004.chi", UMF=1;
ADD MRCV: FN="HWF001000B.chi", UMF=1;
ADD MRCV: FN="HWF001000C.chi", UMF=1;
ADD MRCV: FN="HWF001000D.chi", UMF=1;
ADD MRCV: FN="HWF001002E.chi", UMF=1;
ADD MRCV: FN="HWF001012F.chi", UMF=1;
ADD MRCV: FN="HWF001020A.chi", UMF=1;
ADD MRCV: FN="HWF001020E.chi", UMF=1;
ADD MRCV: FN="HWFF800002.chi", UMF=1;
ADD MRCV: FN="HWFF80001C.chi", UMF=1;
ADD MRCV: FN="HWFF80007E.chi", UMF=1;
ADD MRCV: FN="HWFF400002.eng", UMF=1;
ADD MRCV: FN="HWFF40001C.eng", UMF=1;
ADD MRCV: FN="HWFF40007E.eng", UMF=1;
//Configure Data on the SoftX3000 Side (MRS Resource Data).

ADD TONEID: EID="mrc212.huawei.com", TONEID=TID_0X0003, FILENAME=3;
ADD TONEID: EID="mrc212.huawei.com", TONEID=TID_0X000A, FILENAME=10;
ADD TONEID: EID="mrc212.huawei.com", TONEID=TID_0x002f, FILENAME=47;
ADD TONEID: EID="mrc212.huawei.com", TONEID=TID_0x0204, FILENAME=516;


ADD TONEID: EID="mrc212.huawei.com", TONEID=TID_0x021a, FILENAME=538;
ADD TONEID: EID="mrc212.huawei.com", TONEID=TID_0x021b, FILENAME=539;
ADD TONEID: EID="mrc212.huawei.com", TONEID=TID_0x021c, FILENAME=540;
ADD TONEID: EID="mrc212.huawei.com", TONEID=TID_0x021d, FILENAME=541;
ADD TONEID: EID="mrc212.huawei.com", TONEID=TID_0x021e, FILENAME=542;
ADD TONEID: EID="mrc213.huawei.com", TONEID=TID_0X0003, FILENAME=3;

ADD TONEID: EID="mrc213.huawei.com", TONEID=TID_0X000A, FILENAME=10;


Related tasks
Commissioning the Interworking with the MRS (MGCP/H.248)
Related concepts

12.1 Relations Between Hardware Data Tables.

MRS Voice Categories
5.2 Configuring Data to Interwork with MRS6100
Scenarios
When the SoftX3000 interworks with the MRS6100, MGCP or H.248 is used as the control
signaling. Figure 5-2 shows the typical networking model.
Figure 5-2 Typical networking model for the SoftX3000 to interwork with the MRS6100
SoftX3000 MRS6100
MGCP
IP MAN
H.248
Prerequisites
Conditions
Data
consistent between the SoftX3000 and the MRS6100.
MRS6100
Obtain
Media Protocol used for MGCP or H. - -

Gateway interworking between 248
Data the SoftX3000 and the
MRS6100
MGCP/H.248 code ABNF - -

type
IP address of the IFMI 191.169.150.3 It is planned by -

of the SoftX3000 0/255.255.0.0 carriers.
IP address of the 191.169.150.6 It is planned by -

MCCU of the 1/255.255.0.0 carriers.
MRS6100


Obtain

the SoftX3000 side

the MRS6100 side
Domain name of the mrs6100.huaw It is planned by -

MRS6100 ei.com carriers.

MRS6100 carriers.
Whether the MRS6100 Yes It is planned by -

supports the EC carriers.
function

supported by the 711μ, G.723.1,
MRS6100 G.729A
Documents
Workflow
The procedure for configuring the data between the SoftX3000 and the MRS6100 is as follows:
1. Configure Media Gateway.
2. Configure mapping between rarely used tone IDs and voice files.
Procedure
Step 1 Configure Media Gateway.
MGCMODULENO=FCCU/AGCU/UACU module number, PTYPE=Protocol type, LA=Local
IP address, RA1=Remote IP address 1, RP=Remote port, ET=Encryption type,
SUPROOTPKG=Root Packge, MGWFCFLAG=H248.11 flow control;

NOTE
If a carrier uses an MRS gateway provided by Huawei, the format of the equipment ID is as follows:
l When Protocol type is set to H248, Equipment ID is in the format of "IP address:port number", for
example, 191.169.150.2:2944.
l When Protocol type is set to MGCP, Equipment ID is in the format of "domain name", for example,
mrs6100.huawei.com.
l Remote IP address 1 must be set to the IP address of the MCCU of the MRS6100. In the given example,
Remote IP address 1 is set to 191.169.150.2.
Step 2 Configure mapping between rarely used tone IDs and voice files.
ADD TONEID: EID="191.169.150.2:2944", TONEID=TID_0X0003, FILENAME=3;
ADD TONEID: EID="191.169.150.2:2944", TONEID=TID_0X000A, FILENAME=10;
ADD TONEID: EID="191.169.150.2:2944", TONEID=TID_0x002f, FILENAME=47;
ADD TONEID: EID="191.169.150.2:2944", TONEID=TID_0x0204, FILENAME=516;
ADD TONEID: EID="191.169.150.2:2944", TONEID=TID_0x021a, FILENAME=538;
ADD TONEID: EID="191.169.150.2:2944", TONEID=TID_0x021b, FILENAME=539;
ADD TONEID: EID="191.169.150.2:2944", TONEID=TID_0x021c, FILENAME=540;
ADD TONEID: EID="191.169.150.2:2944", TONEID=TID_0x021d, FILENAME=541;
ADD TONEID: EID="191.169.150.2:2944", TONEID=TID_0x021e, FILENAME=542;


NOTE
By default, the system adds the mapping table (33 records) for the commonly-used tone IDs and voice files
after you run ADD MGW to add an MRS gateway. To add the mapping between all tone IDs and voice
files, run the script mentioned in the section earlier.
----End
Example
Introduction
requirements:
l The SoftX3000 can support basic tones and supplementary service announcements.
l The SoftX3000 can support announcement playing and digit collection functions for IN
services.
Scripts
//Configure Media Gateway.
ADD MGW: EID="191.169.150.2:2944", GWTP=MRS, MGWDESC="MRS6100",
MGCMODULENO=22, PTYPE=H248, LA="191.169.150.30", RA1="191.169.150.2",
ET=NO, SUPROOTPKG=NS, MGWFCFLAG=FALSE;
//Configure mapping between rarely used tone IDs and voice files.
ADD TONEID: EID="191.169.150.2:2944", TONEID=TID_0X0003, FILENAME=3;
ADD TONEID: EID="191.169.150.2:2944", TONEID=TID_0X000A, FILENAME=10;


Related tasks
Commissioning the Interworking with the MRS (MGCP/H.248)
Related concepts
5.3 Configuring Data to Interwork with MRFP6600

Scenarios
When the SoftX3000 interworks with the MRFP6600, H.248 is used as the control signaling.
Figure 5-3 shows the typical networking model.
Figure 5-3 Typical networking model for the SoftX3000 to interwork with the MRFP6600
UA
MRFP6600
H
.2
48
H.248
MGCP
MGC UMG
INAP
SCP IAD
NOTE
l This topic is applicable to India BSNL only.

l The announcement can be played in Indian with the charge in Rupee.
Prerequisites
Conditions

Data
consistent between the SoftX3000 and the MRFP6600.
CAUTION
The IP addresses and masks mentioned are for examples only. In actual application, make the
configuration in compliance with the data planned for the local office.

MRFP6600

Value Obtain
Media Protocol used for H.248 - -

gateway data interworking between
MRFP6600
H.248 code type ASN.1 (binary - -

mode)
IP address of the IFMI 160.11.11.1/2 It is planned -

of the SoftX3000 55.255.0.0 by carriers.
Local port number on 2944 It is planned -

the SoftX3000 side by carriers.
IP address of the 160.11.11.224 It is planned -

MRFP6600 /255.255.0.0 by carriers.
Reserved IP address of 160.11.11.225 It is planned -

the MRFP6600 /255.255.0.0 by carriers.
Local port number on 2944 It is planned -

the MRFP6600 side by carriers.
Whether the Yes - -

MRFP6600 supports H.
248.9
Documents
Workflow
The procedure for configuring the data between the SoftX3000 and the MRFP6600 is as follows:
l Configure media gateway.
l Configure PBX virtual subscriber.
Procedure
Step 1 Configure media gateway.

IP address, RA1=Remote IP address 1, RP=Remote port, ET=Encryption type,
SUPROOTPKG=Root Packge, MGWFCFLAG=H248.11 flow control;

Step 2 Configure PBX virtual subscriber.

1. ADD PBX: GDN=PBX pilot number, LP=Local DN set, VF=Virtual flag, PNC=Pay
Number Control;
2. ADD VPSBR: LP=Local DN set, MN=FCCU module number, SPSN=Start equipment
number, EPSN=End equipment number, RCHS=Charging source code, CSC=Call source
code, GDN=PBX pilot number;
----End
Example
Task Description
This task enables the SoftX3000 to fulfill the following application requirements.
l The SoftX3000 is configured to support the H248.9 gateway (MRFP6600) for playing the
announcement.
l The interworking between the SoftX3000 and the gateway is normal.
Scripts
//Configure media gateway.
ADD MGW: EID="160.11.11.224:2944", GWTP=MRS, MGCMODULENO=22, PTYPE=H248,
LA="160.11.11.1", RA1="160.11.11.224", RA2="160.11.11.225",RP=2944,
CODETYPE=ASN, UCATT=SUPTH2489-1, ET=NO, SUPROOTPKG=NS, MGWFCFLAG=FALSE;
//Configure PBX virtual subscriber.

ADD PBX: GDN=K'1234, LP=0, VF=YES, PNC=NOCHG;
ADD VPSBR: LP=0, MN=22, SPSN=45, EPSN=45, RCHS=0, CSC=0, GDN=K'1234;
Related tasks
Related concepts

Initial Configuration 6 Configuring Data to Interwork with Subscriber Terminal
6 Configuring Data to Interwork with

Subscriber Terminal
About This Chapter
6.1 Configuring Data to Interwork with SIP Terminal

6.2 Configuring Data to Interwork with H.323 Terminal
6.3 Configuring Data for Controlling the Roaming of Multimedia Terminals (IP)
6.4 Configuring Data to Interwork with Typical Terminals

6 Configuring Data to Interwork with Subscriber Terminal Initial Configuration
6.1 Configuring Data to Interwork with SIP Terminal
Scenarios
A SIP terminal can be connected to the SoftX3000 through an IP MAN. In this case, the SIP
terminal provides subscribers with multimedia services, including voice, data, and video
services. Figure 6-1 shows the typical networking model where SIP terminals adopt SIP to
interwork with the SoftX3000.
Figure 6-1 Typical networking model for SIP terminals interworking with the SoftX3000
SoftX3000
IP MAN
SIP
Broadband
AN sevice
As shown in Figure 6-1, subscribers A and B use SIP hard terminals such as SIP phones.
Subscribers C and D use SIP soft terminals such as the OpenEye of Huawei. Regardless of the
types of SIP terminals, the data configuration processes on the SoftX3000 side are the same.
Prerequisites
Conditions

Data
consistent between the SoftX3000 and the SIP terminals.

Table 6-1 Data to be collected before configuring the data between the SoftX3000 and the SIP
terminals
Obtain
SIP Protocol Protocol used for SIP - -

Data interworking between
SIP terminals
Well-known port 5060 It is planned by -

number of SIP carriers.
STUN Data IP address of the IFMI 191.169.150.3 It is planned by -

of the SoftX3000 0/255.255.0.0 carriers.
Subscriber Registered subscriber 8780001 It is planned by -

Data name (equipment ID) of carriers.
subscriber A
Registered password of 112233 It is planned by -

subscriber A carriers.

subscriber A carriers.
Registered subscriber 8780002 It is planned by -

name (equipment ID) of carriers.
subscriber B

subscriber B carriers.

subscriber B carriers.

subscriber C

subscriber C carriers.

subscriber C carriers.

subscriber D

subscriber D carriers.

subscriber D carriers.

Documents
Workflow
The procedure for configuring the data between the SoftX3000 and the SIP Terminal is as
follows:
1. Configure SIP Protocol Data.
2. Configure STUN Data.
Procedure
Step 1 Configure SIP Protocol Data.
1. Set SIP Global Configuration
SET SIPCFG:;
2. Set SIP Local Port
SET SIPLP: MN=MSGI module number, PORT=Port;
NOTE
The first SIP message sent from a SIP terminal to the SoftX3000 carries the SIP well-known port
number 5060. After receiving the SIP message, the IFMI sends the message in load sharing mode to
the MSGI. Then, the IFMI of the SoftX3000 sends a SIP message that carries the local port number
5061 configured for the MSGI. The SIP terminal receives the returned SIP message and sends
messages that contain the local port number 5061 configured for the MSGI. After receiving the
messages, the IFMI of the SoftX3000 directly sends the messages to the MSGI whose local port
number is 5061.
Step 2 Configure STUN Data.

ADD STUNDISP: FMN=IFMI module number;
NOTE
l When a SIP terminal is the OpenEye of Huawei and the IP address of the SIP terminal is in a private
network segment, the local port of the STUN protocol must be added on the SoftX3000 side. This
guarantees that the SoftX3000 and the SIP terminal interwork correctly.
l By default, all MSGI modules are able to dispatch the STUN protocol. If the default configuration has
been modified, run SET DPA to reset it.

ADD MMTE: EID=Equipment ID, MN=FCCU module number, PT=SIP, IFMMN=IFMI
module number, AT=Authorization type, PASS=Authorization password;
NOTE
Equipment ID equals the registered subscriber name of SIP. Authentication password equals the
registered password of SIP.


ADD MSBR: D=Subscriber number, LP=Local DN set, EID=Equipment ID, RCHS=Charging
NOTE
----End
Example
Introduction
requirements:
Scripts
//Configure SIP Protocol Data.
SET SIPLP: MN=211, PORT=5061;
SET SIPCFG:;
//Configure STUN Data.

ADD STUNDISP: FMN=132;

ADD MMTE: EID="8780001", MN=22, PT=SIP, IFMMN=132, PASS="111223", AT=ABE;

ADD MSBR: D=K'8780001, LP=0, EID="8780001", RCHS=87, CSC=0, NS=CLIP-1;

ADD CNACLD: PFX=K'878, MINL=7, MAXL=7, CHSC=0, SDESCRIPTION="Office_878";
Related tasks
Commissioning the Interworking with Other Networks (SIP)
Related concepts

6.2 Configuring Data to Interwork with H.323 Terminal
Scenarios
An H.323 terminal can be connected to the SoftX3000 through an IP MAN. In this case, the H.
323 terminal provides subscribers with multimedia services, including voice, data, and video
services. Figure 6-2 shows the typical networking model where H.323 terminals adopt H.323
to interwork with the SoftX3000.
Figure 6-2 Typical networking model for H.323 terminals interworking with the SoftX3000
SoftX3000
IP MAN
H.323
Broadband
AN sevice
As shown in Figure 6-2, subscribers A and B use H.323 hard terminals such as H.323 phones.
Subscribers C and D use H.323 soft terminals such as the OpenEye of Huawei. Regardless of
the types of H.323 terminals, the data configuration processes on the SoftX3000 side are the
same.
Prerequisites
Conditions
Data
consistent between the SoftX3000 and the H.323 terminals.

Table 6-2 Data to be collected before configuring the data between the SoftX3000 and the H.
323 terminals
Obtain
H.323 Protocol used for H.323 - -

Protocol Data interworking between
H.323 terminals
STUN Data IP address of the IFMI 191.169.150.3 It is planned -

of the SoftX3000 0/255.255.0.0 by carriers.
Subscriber Equipment ID of 8780011 It is planned -

Data subscriber A (the same by carriers.
with phone number)
Registered password of 556677 It is planned -

subscriber A by carriers.
Phone number of 8780011 It is planned -

subscriber A by carriers.
Equipment ID of 8780012 It is planned -

subscriber B (the same by carriers.
with phone number)

subscriber B by carriers.

subscriber B by carriers.

subscriber C (the same by carriers.
with phone number)

subscriber C by carriers.

subscriber C by carriers.

subscriber D (the same by carriers.
with phone number)

subscriber D by carriers.

subscriber D by carriers.
Documents

Workflow
The procedure for configuring the data between the SoftX3000 and the H.323 terminals is as
follows:
1. Configure H.323 Protocol Data.
2. Modify Public Parameters.
3. Configure STUN Data.
Procedure
Step 1 Configure H.323 Protocol Data.
1. Configure H323 System Information
ADD H323SYS: SYSNM=System name;
NOTE
System name is the other name of the SoftX3000 used in the H.323 network. Set System name
correctly; otherwise, the SoftX3000 cannot interwork with the GK, GW, or MCU in the H.323
network.
2. Configure H323 Application Information
ADD H323APP: MN=MSGI module number, IPDMN=IFMI module number,
MTYP=MSGI module type, CALLMINPRT=Call local minimum port value,
CALLMAXPRT=Call local maximum port value;
NOTE
l The system is equipped with only one MSGI. Therefore, the parameter MSGI module type must
be set to RAS & CALL application.
Step 2 Modifying Public Parameters

MOD PUBPRM: ID=Parameter, VAL=Value;
Step 3 Configure STUN Data.
ADD STUNDISP: FMN=IFMI module number, MMN=MSGI module number;
NOTE
l When an H.323 terminal is the OpenEye of Huawei and the IP address of the H.323 terminal is in a
private network segment, the local port of the STUN protocol must be added on the SoftX3000 side.
This guarantees that the SoftX3000 and the H.323 terminal interwork correctly.
l By default, all MSGI modules are able to dispatch the STUN protocol. If the default configuration has
been modified, run SET DPA to reset it.

ADD MMTE: EID=Equipment ID, MN=FCCU module number, PT=Protocol type,

DT=Device type, AT=Authorization type, PASS=Authorization password;
NOTE
l When a multimedia terminal adopts H.323, Equipment ID must be consistent with the equipment ID
(such as the phone number) of the H.323 terminal.
l DT must be set to Terminal, which is different from that set for the H.323 IAD.

ADD MSBR: D=Subscriber number, LP=Local DN set, EID=Equipment ID, RCHS=Charging
NOTE
----End
Example
Introduction
requirements:
Scripts
//Configure H.323 Protocol Data.

CALLMAXPRT=10000;
//Modifying Public Parameters

MOD PUBPRM: ID=P45, VAL=1;
//Configure STUN Data.

ADD STUNDISP: FMN=132, MMN=211;

ADD MMTE: EID="8780011", MN=22, PT=H323, DT=TERMINAL, PASS="556677",
AT=ABE;
AT=ABE;
AT=ABE;
AT=ABE;



ADD CNACLD: PFX=K'878, MINL=7, MAXL=7, CHSC=0, SDESCRIPTION="Office_878";
Related tasks
Commissioning the Interworking with Other Networks (H.323)
Related concepts
6.3 Configuring Data for Controlling the Roaming of

Multimedia Terminals (IP)
Scenarios
The NGN adopts the IP bear network. Therefore, an end user can register with the SoftX3000
by using different IP addresses in different areas. Configuring the roaming control data of
multimedia terminals allows carriers to control the roaming and call authority of terminals in a
range of IP addresses. Figure 6-3 shows the typical networking.
Figure 6-3 Typical networking for roaming of multimedia terminals
SoftX3000
IAD

The MGW transfers the actual IP address (registration address) of a terminal that registers with
the SoftX3000 through the MGW to a roaming IP address. Then, the MGW sends the roaming
IP address to the SoftX3000. At present, the SIP or MGCP protocol is used between the MGW
and the SoftX3000.
If a terminal directly registers with the SoftX3000, the roaming IP address is the same as the
registration IP address.
The SoftX3000 records the original charging information in the CDRs and does not process the
charging of calls related to roaming subscribers.
Impact on the System

This operation has no adverse impact on the system.
Prerequisites
Conditions
l You have administrator rights.

l You have logged in to the LMT.
Data
Table 6-3 lists the data to be negotiated before configuring data on the SoftX3000.
Table 6-3 Data to be negotiated before configuring data on the SoftX3000
Category Parameter Example How to Description

Value Obtain
IP address field IP address 61.1.2.3 to Obtain from The IP address

segment 61.1.2.240 carriers. segment to be
configured with
the roaming
authority.
Document
Before configuring the data, you must plan the related data according to the requirements in the
Specifications for Data Configuration provided by the Global Technical Service Department of
Huawei.
Procedure
The procedure for configuring the roaming data of terminals is as follows:
1. Configure the IP segment.

2. Configure the roaming mode.
3. Configure the data of a multimedia terminal or the MGW.

Procedure
Step 1 Configure the IP segment.
ADD IPSEG: OIPDM=Origin IP domain number, DMN=Origin IP domain name, SSA=Start

IP address, ESA=End IP address;
Step 2 Configure the roaming mode.
ADD RMODE: OIPDM=Original IP domain number, RIPDM=Roaming IP domain number,

ROR=Roaming right, ROTP=Roaming type;
Step 3 Configure the data of a multimedia terminal or the MGW.

l Configuring the data of a SIP terminal
ADD MMTE: EID=Equipment ID, MN=FCCU module number, IMSFLAG=IMS Flag,
PT=Protocol type, IFMMN=IFMI module number, PASS=Authorization password,
AT=Authorization type, OIPDM=Origin IP domain;
l Configuring the data of the MGW
MGCMODULENO=FCCU/AGCU/UACU module number, PTYPE=Protocol type,
LA=Local IP address, RA1=Remote IP address 1, RP=Remote port,
LISTOFCODEC=Codec list, OIPDM=Origin IP domain;
----End
Example 1
Task Description
Configure data on the SoftX3000 to meet the following requirements:
Grant a SIP terminal the local roaming authority.
Scripts
//Configure the IP segment.

ADD IPSEG: OIPDM=0, DMN="local1", SSA="61.1.2.3", ESA="61.1.2.240";
//Configure the roaming mode.

ADD RMODE: OIPDM=1, RIPDM=0, ROR=AR, ROTP=LR;
//Configure the data of the SIP terminal.

ADD MMTE: EID="1", MN=22, IMSFLAG=NO, PT=SIP, IFMMN=132, PASS="0000",
AT=ABE;
Example 2
Task Description
Configure data on the SoftX3000 to meet the following requirements:
Grant the MGW the local roaming authority.
Scripts

//Configure the IP segment.

//Configure the roaming mode.

ADD RMODE: OIPDM=1, RIPDM=0, ROR=AR, ROTP=LR;
//Configure the data of the MGW.

ADD MGW: EID="iad0086.com", GWTP=IAD, MGWDESC="iad0086", MGCMODULENO=22,
PTYPE=MGCP, LA="191.169.150.30", RA1="61.1.2.6", RP=2427,
LISTOFCODEC=PCMA-1, OIPDM=0;
Related Tasks
None.
Related Concepts
Terminal Roaming
6.4 Configuring Data to Interwork with Typical Terminals
6.4.1 Configuring Data to Interwork with Pingtel Terminal

6.4.2 Configuring to Interwork with Vizufon 4500 Terminal
6.4.3 Configuring Data to Interwork with ViewPoint 8220 Terminal
6.4.1 Configuring Data to Interwork with Pingtel Terminal
Scenarios
The Pingtel is a multimedia hard terminal that supports SIP. The following configurations are
applicable to Pingtel V2.1.8.6 (2003-04-10).
Prerequisites
Conditions
You have the administrative rights of the Pingtel terminal.
Data
consistent between the SoftX3000 and the Pingtel terminal.

Table 6-4 Data to be collected before configuring the data between the SoftX3000 and the Pingtel
terminal

Value Obtain
IP address of the IP address of the 191.169.150. It is planned -

SoftX3000 SoftX3000 30 by carriers.
IP address of the IP address of the 191.169.150. It is planned -

Pingtel terminal Pingtel terminal 251 by carriers.
Network mask of the 255.255.255. It is planned -

Pingtel terminal 0 by carriers.
Data for Login user name admin It is planned -

interworking (default) by carriers.
with the Pingtel
terminal Password None It is planned -
by carriers.
Length of number 7 digits It is planned -

by carriers.
Registration period of 120 seconds It is planned -

the Pingtel terminal by carriers.
TCP port number of 5060 It is planned -

the Pingtel terminal by carriers.
Number of the SIP 8780001 It is planned -

subscriber by carriers.
Sip SRL sip:8780001 It is planned -

@191.169.15 by carriers.
0.30
Documents
Workflow
The procedure for configuring the data between the SoftX3000 and the Pingtel terminal is as
follows:
1. Configure the IP address of the Pingtel terminal.

2. Configure data for interworking with the Pingtel terminal.
Procedure
Step 1 Configure the IP address of Pingtel terminal.

1. Press the MORE button at the top right corner of the Pingtel terminal.
The Applications interface is displayed on the telephone screen.
2. Press the first button at the top right corner of the screen, which maps Prefs on the screen.
The Preferences interface is displayed.
3. Press the first button at the top right corner of the screen, which maps Network Settings
on the screen. Enter the password and then press the OK button.
The Network Preferences interface is displayed.
4. Turn the rotary button on the right side of the Pingtel terminal. The positions of the
configuration items on the screen change. Set IP Address and Network Mask to the correct
positions on the screen.
5. Use the buttons on both sides of the screen to set or modify the related parameters. Assume
that the configurations are as follows:
l IP Address: 191.169.150.251
l Network Mask: 255.255.255.0
6. After configuring the previous information, the system prompts to restart the system. Press
the Restart button. The Pingtel terminal restarts to make the configurations valid.
Step 2 Configure data for interworking with the Pingtel terminal.
1. Log in.
a. Set the IP address of the PC to be in the same network segment as that of the Pingtel
terminal. Run the PING command on the PC to ensure that the network connection
is normal between the PC and the Pingtel terminal.
b. Start Internet Explorer (IE) browser on the PC. Enter http://191.169.150.251 in the
address box to log in to the management interface of the Pingtel terminal.
c. Enter the login user name admin (default value). No password is required.
2. Enter the phone information configuration interface.
On the homepage, choose Administration > Phone Configuration, as shown in Figure
6-4. The page for configuring phone information is displayed.

Figure 6-4 Phone information configuration interface
This interface covers all data related to the Pingtel terminal configuration. The interface is
long and not all the data can be displayed in a single screen; therefore, scroll down to
configure all the data.
3. Configure the phone number length.
Drag the scroll bar downward so that the heading Call Addressing is displayed, as shown
in Figure 6-5. Select a number length from the PHONESET_DIALPLAN_LENGTH
box. To facilitate dialing, set PHONESET_DIALPLAN_LENGTH to the length of a
local number. In this case, it is set to 7.
Figure 6-5 Configuring the phone number length

4. Configure SIP data.

Drag the scroll bar downward so that the heading SIP Servers is displayed, as shown in
Figure 6-6.
l Enter the IP address of the directory server (that is, the IP address of the SoftX3000) in
the SIP_DIRECTORY_SERVERS box. Assume that the IP address is
191.169.150.30.
l SIP_PROXY_SERVERS settings: No information is required here.
l Enter the registration period of the Pingtel terminal in the
SIP_REGISTER_PERIOD box. You are advised to set it to 120 seconds.
l Enter the TCP port number of the Pingtel terminal in the SIP_TCP_PORT box. It must
be consistent with the configuration on the SoftX3000 side. In this case, assume that
SIP_TCP_PORT is set to 5060.
Figure 6-6 Configuring SIP data
5. Configure authentication data.

Drag the scroll bar downward so that the heading Additional Parameters is displayed, as
shown in Figure 6-7.

Figure 6-7 Configuring authentication data
Enter the following authentication information in the blank column as displayed in Figure
6-7:
l PHONESET_EXTENSION: The telephone number of a SIP subscriber. In this case,

assume that it is 8780001.
l SIP_AUTHORIZE_PASSWORD.191.169.150.30: The registration password of a
SIP subscriber. In this case, assume that it is 112233. 191.169.150.30 refers to the IP
address of the SIP call server (that is, the IP address of the SoftX3000), which must be
set correctly.
l SIP_AUTHORIZE_USER.191.169.150.30: The registration name of a SIP
subscriber. In this case, assume that it is 8780001. 191.169.150.30 refers to the IP
address of the SIP call server (that is, the IP address of the SoftX3000), which must be
set correctly.
l SIP_REGISTRY_SERVERS: The IP address of the SIP registration server (that is,
the IP address of the SoftX3000). In this case, assume that it is 191.169.150.30.
6. Configure SIP-URL information.
a. Click the link device lines in Figure 6-7. The SIP-URL configuration interface is
displayed, as shown in Figure 6-8.
Figure 6-8 SIP-URL configuration interface
b. There are two configuration options for SIP-URL: Device Line and User Lines. Click
the link Add New Line or Edit. The Enter Line Information interface is displayed,
as shown in Figure 6-9.

Figure 6-9 Configuring SIP-URL information
c. Enter SIP-URL information in the Sip SRL box in the format of "sip:phone number
of a SIP subscriber@IP address of SIP registration server". In this case, assume that
it is sip:8780001@191.169.150.30. After the setting, click Update.
d. The system returns to the interface as shown in Figure 6-8. Click Save.
7. Save the configuration and reset the Pingtel terminal.
After all the configurations are completed, choose Administration > Phone
Configuration to enter the phone information configuration interface again. Click Save to
save the configuration. Click Restart to reset the Pingtel terminal.
----End
Related tasks
None.
Related concepts
None.
6.4.2 Configuring to Interwork with Vizufon 4500 Terminal
Scenarios
The Vizufon 4500 is a multimedia hard terminal that supports H.323 (fast start version). The
following configurations are applicable to Vizufon V1.2 (2003-11-14).
Prerequisites
Conditions
There are no special conditions for this operation.
Data
consistent between the SoftX3000 and the Vizufon 4500 terminals.

Vizufon 4500 terminals
Obtain
Data on the IP address of the 191.169.150.3 It is planned -

SoftX3000 primarily homed 0 by carriers.
SoftX3000
Equipment ID of the H. 8780011 It is planned -

323 terminal by carriers.
IP address of the 191.169.150.3 It is planned -

secondarily homed 1 by carriers.
SoftX3000
IP address of IP address of the 191.169.150.2 It is planned -

the Vizufon Vizufon 4500 terminal 52 by carriers.
4500 terminal
Subnet mask of the 255.255.255.0 It is planned -
Vizufon 4500 terminal by carriers.
Gateway 191.169.150.1 It is planned -

by carriers.
DNS address 0.0.0.0 It is planned -

by carriers.
Documents
Workflow
The procedure for configuring the data between the SoftX3000 and the Vizufon 4500 terminals
is as follows:
1. Configure the IP address of the Vizufon 4500 terminal.
2. Configure data for interworking with the Vizufon 4500 terminal.
Procedure
Step 1 Configure the IP address of Vizufon 4500
1. Press the ENT button at the bottom right corner of the Vizufon terminal.
The configuration menu is displayed on the telephone screen.
2. Press the left or right arrow button on the dialer to select the IP icon. Press the ENT button.
Enter the correct password as prompted by the system, and press ENT.
The IP configuration interface is displayed on the screen.
3. Press the left or right arrow button on the dialer to select the first item Default Setting, and
press ENT.

The Internet configuration interface is displayed on the screen.

4. Press the up or down arrow button to select a configuration sub-item and then press the
right or left arrow button to enter the mode for setting parameters or numbers. In this case,
assume that the configurations are as follows:
l Type: LAN (Static IP)
l IP address: 191.169.150.252
l Sub. Mask: 255.255.255.0
l Gateway: 191.169.150.1
l DNS address: 0.0.0.0
5. After completing the configurations, press the EXIT button to exit the system.
The system prompts "IP setting has been reconfigured. Save and apply new setting?"
6. Press YES. The Vizufon terminal restarts to make the configurations valid.
Step 2 Configure data for interworking with the Vizufon 4500 terminal.
1. Press the ENT button at the bottom right corner of the Vizufon terminal.
The configuration menu is displayed on the telephone screen.
2. Press the left or right arrow button on the dialer to select the IP icon. Press the ENT button.
Enter the correct password as prompted by the system, and press ENT.
The IP configuration interface is displayed on the screen.
3. Press the up or down arrow button on the dialer to select the second item Advanced
Setting, and press ENT.
The IP call setting interface is displayed on the screen.
4. Press the up or down arrow button to select a configuration sub-item and then press the
right or left arrow button to enter the mode for setting parameters or numbers. In this case,
assume that the configurations are as follows:
l GK address (that is, IP address of the primarily homed SoftX3000): 191.169.150.30
l H.323 ID (that is, equipment ID of the H.323 terminal): 8780011
l E.164 (that is, phone number of the H.323 terminal): 8780011
l Password (that is, registration password of the H.323 terminal).
l GK address 2 (that is, IP address of the secondarily homed SoftX3000).
5. After completing the configurations, press the EXIT button to exit the system.
The system prompts "IP setting has been reconfigured. Save and apply new setting?"
6. Press YES. The Vizufon terminal restarts to make the configurations valid.
----End
Related tasks
None.
Related concepts
None.
6.4.3 Configuring Data to Interwork with ViewPoint 8220 Terminal

Scenarios
The ViewPoint 8220 is a multimedia hard terminal that supports H.323 or SIP. The H.323
Viewpoint 8220 and the SIP Viewpoint 8220 are configured basically in the same way. The
configuration of the H.323 Viewpoint 8220 is described in this section. Refer to the related
description in this section when you configure the SIP Viewpoint 8220. The configuration
method is applicable to V600R420 B02D011 or a later version.
Prerequisites
Conditions
There are no special conditions for this operation.
Data
consistent between the SoftX3000 and the ViewPoint 8220 terminals.
ViewPoint 8220 terminals

Value Obtain
IP address of IP address of the 10.10.10.10 It is planned -

the SoftX3000 SoftX3000 by carriers.
Documents
Workflow
The procedure for configuring the data between the SoftX3000 and the ViewPoint 8220
terminals is as follows:
1. Configure IP address of the ViewPoint 8220 terminal.

2. Configure the data for interworking with the ViewPoint 8220 terminal.
Procedure
Step 1 Configure IP address of the ViewPoint 8220 terminal.
1. Enter the main menu.
Press OK (indicated by 6 in Figure 6-10) on the operation panel to enter the main menu.

Figure 6-10 Operation panel of the ViewPoint 8220
2. Configure the IP address of the ViewPoint 8220 terminal.
Select Network from the main menu. Set the related parameters according to the mode of
obtaining the IP address, as shown in Figure 6-11.
Figure 6-11 Network interface
l If the connection mode is ADSL dialup (PPPoE dialup) or LAN (PPPoE dialup),
configure the dialup account and the password.

l If the connection mode is ADSL dedicated line or LAN (fixed IP address), configure
the IP address, subnet mask, gateway address, and DNS address. (If there is no DNS
address, set the DNS address to 0.0.0.0.)
3. Save the configuration.
To save the configuration, press the direction keys on the operation panel to select Save on
the interface as shown in Figure 6-11. Press Confirm Menu on the operation panel.
Step 2 Configure data for interworking with ViewPoint 8220 terminal.
1. Configure basic registration information about the ViewPoint 8220.
Select User from the main menu as shown in Figure 6-12. Set the IP address of the
registration server, account, and password.
Figure 6-12 User interface
l Enter the IP address of the GK (that is, the IP address of the SoftX3000) in the Register
server box, for example, 10.10.10.10.
l Enter the equipment ID of the H.323 terminal (ViewPoint 8220) in the Number box.
l Enter the password of the H.323 terminal (ViewPoint 8220) in the Password box.
l Enter the name of a place or a person in the Nickname box. This name is displayed in
the conference list.
2. Save the configuration.
To save the configuration, press the direction keys on the operation panel to select Save on
the interface as shown in Figure 6-12. Press Confirm Menu on the operation panel. After
being reset, the ViewPoint 8220 can log in to SoftX3000.
----End
Related tasks
None.
Related concepts

None.

Initial Configuration 7 Configuring Subscriber Data
7 Configuring Subscriber Data
Scenarios
During the office deployment, you need to configure the subscriber data that is planned by the
carrier.
Prerequisites
Conditions
Data
Table 7-1 Data for voice service subscribers

Categor Parame Example How to Obtain Description
y ter Value
Name
Subscrib Subscri 65400100 The value is An example on adding

er data ber -6540013 determined by the subscriber number in one
number carrier. batch is provided in the
following content.
Local 0 The value is obtained The value is determined

DN set through the LST during the local office data
LDNSET command. planning.
Chargin 65 The value is obtained The value is determined

g source through the LST during the charging data
code CHGGRP and LST planning.
CHGIDX commands.

7 Configuring Subscriber Data Initial Configuration

y ter Value
Name
Call 0 The value is obtained The value is determined

source through the LST during the local office data
code CALLSRC command. planning.
FCCU FCCU 22 The value is obtained The value is determined

module module through the LST BRD during the hardware data
number number command. planning.
Access Equipm 211.169.1 The value is obtained The value is determined

equipme ent ID 50.2:2944 through the LST during the access equipment
nt data MGW command. planning.
Start 0 The value is obtained The value is determined

MG through the LST during the access equipment
terminat MGW command. planning.
ion ID
V5 V5 0 The value is obtained The value is determined

interface interfac through the LST V5I during the signaling data
ID e ID command. planning and is used for
adding V5 subscribers.
Table 7-2 Data of multimedia service subscribers

y ter Value
Name
Subscrib Subscri 6540201- The value is An example on adding

er data ber 6540202 determined by the subscriber number in one batch
number carrier. is provided in the following
content.
Local 0 The value is obtained The value is determined during

DN set through the LST the local office data
LDNSET command. planning.
Chargin 65 The value is obtained The value is determined during

g source through the LST the charging data planning.
code CHGGRP and LST
CHGIDX commands.
Call 0 The value is obtained The value is determined during

source through the LST the local office data
code CALLSRC planning.
command.


y ter Value
Name
Access Start 6540201 The value is obtained The value is determined during
equipme MG through the LST the access equipment
nt data terminat MMTE command. planning.
ion ID
Table 7-3 Data for wide area Centrex subscribers

er Name Value
Subscribe Subscrib 7780000-7 The value is determined An example on adding

r data er 780004 by the carrier. subscriber number in
number one batch is provided in
the following content.
Local DN 0 The value is obtained The value is

set through the LST determined during the
LDNSET command. local office data
planning.
Centrex 0 The value is obtained The value is

group through the LST determined during the
number CXGRP command. planning of the wide
area Centrex service.
Centrex 0 The value is obtained The value is

subgroup through the LST determined during the
number CXGRP command. planning of the wide
area Centrex service.
Table 7-4 Data for BRA subscribers

er Name Value
Subscriber Subscribe 6540062-6 The value is determined An example on adding

data r number 540064 by the carrier. subscriber number in
one batch is provided in

planning.


er Name Value
Charging 65 The value is obtained The value is

source through the LST determined during the
code CHGGRP and LST charging data
CHGIDX commands. planning.
Call 0 The value is obtained The value is

code CALLSRC command. local office data
planning.
Access Equipme 211.169.15 The value is obtained The value is

equipment nt ID 0.7:2944 through the LST MGW determined during the
data command. access equipment
planning.
Start MG 16,18 The value is obtained The value is

terminati through the LST MGW determined during the
on ID command. access equipment
planning.
ISDN data Linkset 0 The value is obtained The value is

index through the LST determined during the
IUALKS command. planning of network
interworking data.
Start 0 The value is determined The value is the start

interface by the carrier. interface ID in the IUA
ID linkset for the D
channel signaling
messages sent by the
BRA subscribers.
ISDN 1 The value is obtained -

index through the LST
ISDNDAT command.
Table 7-5 Data for PRA subscribers

er Name Value
Subscriber Subscribe 6540070-6 The value is determined An example on adding

data r number 540080 by the carrier. subscriber number in
one batch is provided in

planning.


er Name Value
Charging 65 The value is obtained The value is

code CHGGRP and LST charging data
CHGIDX commands. planning.
Call 0 The value is obtained The value is

code CALLSRC command. local office data
planning.
ISDN data PRA 1 The value is obtained The value is

trunk through the LST determined during the
group IUALKS command. planning of network
interworking data.
ISDN 2 The value is obtained -

index through the LST
ISDNDAT command.
Tools
Workflow
1. Add subscriber data.
Procedure
Step 1 Add subscriber data.
l Add voice service subscriber data.
ADB VSBR: SD=Start subscriber number, ED=End subscriber number, LP=Local DN set,
DID=ESL subscriber, MN=FCCU module number, EID=Equipment ID, STID=Start MG
termination ID, RCHS=Charging source code, CSC=Call source code, UTP=Ordinary,
CNTRX=False, PBX=False, CHG=False;
NOTE
When Nortel PBX device is used, select Caller on hook indicating signal for Software parameter
of service control.
l Add multimedia service subscriber data.
ADB MSBR: SD=Start subscriber number, ED=End subscriber number, LP=Local DN set,
DID=ESL subscriber, ET=Terminal, SEID=Start MG termination ID, RCHS=Charging
source code, CSC=Call source code, CTXA=False, PBXA=False, CA=False, EA=False;
l Add wide area Centrex subscriber data.
ADB WACSBR: LP=Local DN set, SD=Start subscriber number, ED=End subscriber
number, cxg= Centrex subgroup number, CXSG= Centrex subgroup numbe;
l Add BRA subscriber data.
ADB BRA: LP=Local DN set, SD=Start subscriber number, ED=End subscriber number,
IMS=NON-IMS, DID=BRA subscriber, EID=Equipment ID, STID=Start MG termination

ID, LKS=IUA linkset index, SIID=Start interface ID, ISDN=ISDN index, CSC=Call source
code, RCHS=Charging source code, CUGU=False;
l Add PRA subscriber data.
ADB PRA: LP=Local DN set, SD=Start subscriber number, ED=End subscriber data,
ISDN=ISDN index, LOCM=Trunk group, TRUNKGP=PRA trunk group, CSC=Call source
code, RCHS=Charging source code, CUGU=False;
----End
Example
Task Description
l Add data for ESL voice service subscribers whose numbers range from 6540010 to
6540013.
l Add data for the multimedia service subscribers whose numbers range from 6540201 to
6540202.
l Add data for the wide area Centrex subscribers whose numbers range from 7780000 to
7780004.
l Add data for BRA subscribers whose numbers range from 6540062 to 6540064.
l Add data for PRA subscribers whose numbers range from 6540070 to 6540080.
Scripts
//ADD data for ESL voice service subscribers.
ADB VSBR: SD=K'6540010, ED=K'6540013, LP=0, DID=ESL, MN=22,
EID="211.169.150.2:2944", STID="0", RCHS=65, CSC=0, UTP=NRM, CNTRX=NO,
PBX=NO, CHG=NO;
//Add data for multimedia service subscribers.
ADB MSBR: SD=K'6540201, ED=K'6540202, LP=0, ET=COM, SEID=K'6540201,
RCHS=65, CSC=0, CTXA=NO, PBXA=NO, CA=NO, EA=NO;
//Add data for wide area Centrex subscribers.
ADB WACSBR: LP=0, SD=K'7780000, ED=K'7780004, cxg=0, CXSG=0;
//Add data for BRA subscribers.
ADB BRA: LP=0, SD=K'6540062, ED=K'6540064, IMS=NON-IMS, DID=BRA,
EID="211.169.150.89:2944", STID="0", LKS=0, SIID=0, ISDN=1, CSC=0,
RCHS=65, CUGU=NO;
//Add data for PRA subscribers.
ADB PRA: LP=0, SD=K'6540070, ED=K'6540080, ISDN=2, LOCM=TG, TRUNKGP=1,
CSC=0, RCHS=65, CUGU=NO;
Related tasks
None.
Related concepts
12.3 Relations Between Subscriber Data Tables shows the referencing relation between the
key parameters in data tables.

Initial Configuration 8 Configuring Data to Interwork with Other Networks
8 Configuring Data to Interwork with Other

Networks
About This Chapter
8.1 Configuring Data to Interwork with IN

8.2 Configuring Data to Interwork with PSTN
8.3 Configuring Data to Interwork with H.323 Network
8.4 Configuring Data to Interwork with HFC Network
8.5 Configuring Data to Interwork with Other Softswitches
8.6 Configuring Data to Interwork with IP SMS GW (Through SIP)

8 Configuring Data to Interwork with Other Networks Initial Configuration
8.1 Configuring Data to Interwork with IN

8.1.1 Configuring Data to Interwork with SCP (M3UA - MTP)
8.1.2 Configuring Data to Interwork with SCP (M3UA - M3UA)
8.1.3 Configuring Data to Interwork with SCP (INAP over IP)
8.1.1 Configuring Data to Interwork with SCP (M3UA - MTP)

Scenarios
Before configuring Intelligent Network (IN) service data, configure signaling data for
interworking between the SoftX3000 and the SCP. Otherwise, IN services cannot be deployed.
Figure 8-1 shows a typical networking model where M3UA links carry INAP signaling (that
is, INAP/TCAP/SCCP/M3UA) on the SoftX3000 side and MTP links carry INAP signaling (that
is, INAP/TCAP/SCCP/MTP) on the SCP side.
Figure 8-1 Typical networking model for the SoftX3000 to interwork with the SCP (M3UA -
MTP)
SoftX3000 SG7000 SAU/USAU SCP
M3UA MTP
INAP INAP INAP

TCAP TCAP TCAP
SCCP SCCP SCCP
M3UA M3UA MTP3 MTP3
SCTP SCTP MTP2 MTP2
IP IP MTP1 MTP1
As shown in Figure 8-1, the SoftX3000 provides M3UA links to connect to the SG7000. The
SoftX3000 interworks with the SCP through the SG7000 by using the INAP signaling.
NOTE
If Huawei provides the SCP in the actual networking application, the device that provides MTP links on
the SCP side is the SAU (or USAU) of Huawei. Therefore, the data for signaling interaction between the
SoftX3000 and the SCP is actually the data used for signaling interaction between the SoftX3000 and the
SAU (or USAU).
Prerequisites
Conditions


Data
To achieve signaling interaction between the SoftX3000 and the SCP, configure the following
data on the SoftX3000:
l Data for signaling interaction between the SoftX3000 and the SG7000.
l Data for signaling interaction between the SoftX3000 and the SCP.
Assume that the data configuration planned is as shown in Table 8-1 and Table 8-2.
Table 8-1 Data for signaling interaction between the SoftX3000 and the SG7000
Categor Parameter Name Example Value How to Descriptio
y Obtain n
M3UA Signaling point code of 001122 The value is The value is

local local entity (National obtained determined
entity network) through the during the
data LST OFI local office
command. data
planning.
Route context 12345 The value -

must be
negotiated
with the
SG7000.
M3UA Signaling point code of 001177 The value -

destinati destination entity must be
on entity (National network) negotiated
data with the
SG7000.
M3UA Traffic mode Loadshare The value -

linkset must be
data negotiated
with the
SG7000.
Work mode ASP The value The

must be SoftX3000
negotiated interworks
with the with the
SG7000. SG7000 in
non-peer-to-
peer mode.
Therefore,
set Work
mode to
ASP on the
SG7000.


y Obtain n
M3UA BSGI module number 136 and 137 The value is The value is
link data obtained determined
through the during
LST BRD hardware
command. data
planning.
Local IP address1 191.169.150.30 The value is The value is

obtained determined
through the during
LST hardware
FECFG data
command. planning.
Peer IP address1 211.169.150.70 The value -

must be
negotiated
with the
SG7000.
Local port number Module 136: 2905 The value is If the system
Module 137: 2911 determined is configured
by the with two
carrier. BSGI
modules,
allocate the
two M3UA
links to each
of them. This
guarantees
reliability of
the M3UA
links.
Peer port number 2905 The value -

must be
negotiated
with the
SG7000.


y Obtain n
Client/Server mode Client side The value If the

must be SoftX3000
negotiated in the non-
with the peer-to-peer
SG7000. interworking
mode serves
as the
application
server, set
Client/
Server
mode to
Client side.
Table 8-2 Data for signaling interaction between the SoftX3000 and the SCP
Name Value Obtain
Data for Signaling point 001122 The value is The value is

signaling code of local obtained determined
interaction entity (National through the LST during the local
between the network) OFI command. office data
SoftX3000 and planning.
the SCP
Signaling point 110c0c The value must -
code of be negotiated
destination with the SCP.
entity (National
network)
SCCP sub- SCMG 0x01 The value must If Fixed

system number and INAP 0x0C be negotiated Intelligent
with the SCP. Network (FIN)
services are
deployed,
configure two
SSNs: SCMG
and INAP.
Signaling ITU-T The value must -

specification be negotiated
with the SCP.
Network National The value is -

indicator network determined by
the carrier.

Documents
Before configuring the data, you must plan the related data based on the requirements in the
Huawei.
Workflow
The procedure for configuring data to interwork with SCP is as follows:
1. Configure the M3UA data.
2. Configure the SCCP data.
Procedure
Step 1 Configure the M3UA data.
1. Add an M3UA local entity.
ADD M3LE: LEX=Local entity index, OPC=Signaling point code of local entity,
LET=Local entity type, RC=Route context;
NOTE
On the SoftX3000, LET is set to Application server.
2. Add an M3UA destination entity.
ADD M3DE: DEX=Destination entity index, LEX=Local entity index, DPC=Signaling

point code of destination entity, STPF=STP flag, DET=Destination entity type;
NOTE
l The SoftX3000 interworks with the SG7000 in non-peer-to-peer mode. Therefore, set
Destination entity type to Signaling gateway on the SG7000.
l The exchange of SS7 signaling between the SoftX3000 and the SCP is achieved through the
SG7000. Therefore, set Destination entity type to Signaling point on the SCP.
l On the signaling network, the SG7000 transfers signaling. Therefore, set STP flag to YES.
Otherwise, errors may occur when you add an M3UA route by running ADD M3RT.
3. Add an M3UA linkset.
ADD M3LKS: LSX=Linkset index, ADX=Adjacent destination entity index, WM=Work
mode;
4. Add an M3UA link.
ADD M3LNK: MN=BSGI module number, LNKN=Link number, LOCIP1=Local IP
address1, LOCPORT=Local port number, PEERIP1=Peer IP address1, PEERPORT=Peer
port number, CS=Client/Server mode, LSX=Linkset index;
5. Add an M3UA route to the SCP.
ADD M3RT: DEX=Destination entity index, LSX=Linkset index;
Step 2 Configure the SCCP data.

1. Add an SCCP destination signaling point.
ADD SCCPDSP: DPX=DSP index, NI=Network indicator, DPC=DPC, OPC=OPC;

2. Add an SCCP subsystem.
ADD SCCPSSN: SSNX=SSN index, NI=Network indicator, SSN=SCCP sub-system

number, SPC=SPC, OPC=OPC;

NOTE
The SPC parameter is the DPC of the corresponding subsystem, that is, the receiving end of local
SCCP messages. For each subsystem, you must define two DSPs, namely, SCCP remote SP and local
SP.
3. Add an SCP physical address.
ADD SCPADDR: SCP=SCP number, RT=Route flag, DPC=DPC;
NOTE
If the format of the SCP physical address is that of the SCP, set Route flag to Addressing by
DPC.
4. Add an SSP physical address.
ADD SSPADDR: SCP=SCP number, RT=Route flag, OPC=OPC address;
NOTE
If the format of the SSP physical address is that of the SCP, set Route flag to Addressing by
DPC.
----End
Example
Task Description
l Two M3UA links are established between the SoftX3000 and the SG7000. Both links carry
SS7 links in the load—balancing mode.
l The normal SCCP connection is established between the SoftX3000 and the SG7000.
Scripts
//Add an M3UA local entity.
ADD M3LE: LEX=0, LENAME="SoftX3000", OPC="001122", LET=AS, RC=12345;
//Add two M3UA destination entities.
ADD M3DE: DEX=10, LEX=0, DENAME="SG7000", DPC="001177", STPF=YES, DET=SG;
ADD M3DE: DEX=30, LEX=0, DENAME="SAU", DPC="110c0c", DET=SP;
//Add an M3UA linkset.
ADD M3LKS: LSX=0, LSNAME="To SG7000", ADX=10, WM=ASP;
//Add two M3UA links.
ADD M3LNK: MN=136, LNKN=0, LNKNAME="To SG7000 #0",
LOCIP1="191.169.150.30", LOCPORT=2905,
PEERIP1="211.169.150.70", PEERPORT=2905, CS=C, LSX=0;
LOCIP1="191.169.150.30", LOCPORT=2911,
//Add an M3UA route to the SCP.
ADD M3RT: RTNAME="To SAU", DEX=30, LSX=0;
//Add an SCCP destination signaling point.
ADD SCCPDSP: DPX=1, NI=NAT, DPC="110c0c", OPC="001122", DPNAME="SCP",
SHAREFLAG=NONE;
//Add an SCCP subsystem.
ADD SCCPSSN: SSNX=0, NI=NAT, SSN=SCMG, SPC="001122", OPC="001122",
SSNNAME="SSP to SSP";
ADD SCCPSSN: SSNX=1, NI=NAT, SSN=INAP, SPC="001122", OPC="001122",
ADD SCCPSSN: SSNX=2, NI=NAT, SSN=SCMG, SPC="110c0c", OPC="001122",
SSNNAME="SSP to SCP";
ADD SCCPSSN: SSNX=3, NI=NAT, SSN=INAP, SPC="110c0c", OPC="001122",

//Add an SCP physical address.

ADD SCPADDR: SCP=12, RT=DPC, DPC="110c0c";
//Add an SSP physical address.
ADD SSPADDR: SCP=12, RT=DPC, OPC="001122";
Related Tasks
Commissioning the Interworking with the SCP (M3UA)
Related Concepts
For details about the relations between M3UA data tables, see 12.6.2 Relations Between M3UA
Signaling Data Tables.
8.1.2 Configuring Data to Interwork with SCP (M3UA - M3UA)

Scenarios
Before configuring IN service data, configure signaling data for interworking between the
SoftX3000 and the SCP. Otherwise, IN services cannot be deployed. Figure 8-2 shows a typical
networking model where M3UA links carry INAP signaling (that is, INAP/TCAP/SCCP/
M3UA) on both the SoftX3000 side and the SCP side.
Figure 8-2 Typical networking model for the SoftX3000 to interwork with the SCP (M3UA -
M3UA)
SoftX3000 USAU SCP
M3UA M3UA
INAP INAP
TCAP TCAP
SCCP SCCP
M3UA M3UA
SCTP SCTP
IP IP
NOTE
If Huawei provides the SCP in the actual networking application, the device that provides M3UA links on
the SCP side is the USAU of Huawei. Therefore, the data for signaling interaction between the SoftX3000
and the SCP is actually that for signaling interaction between the SoftX3000 and the USAU.
Prerequisites
Conditions

Data
The SCP serves as only an SP. Therefore, to implement the interworking between the SoftX3000
and the SCP, you need to configure only the data for signaling interaction between the SoftX3000
and the SCP.
Assume that the data configuration planned is as shown in Table 8-3.

Name Value Obtain
M3UA local Signaling point 001122 The value is The value is

entity data code of local obtained determined
entity (National through the LST during the local
network) OFI command. office data
planning.
Route context 12345 The value must -

be negotiated
with the SCP.
M3UA Signaling point 110e0e The value must -

destination code of be negotiated
entity data destination with the SCP.
entity (National
network)

the carrier.
M3UA linkset M3UA link data Loadshare The value must -

data be negotiated
with the SCP.
Work mode IPSP The value must The SoftX3000

be negotiated and the SCP
with the SCP. interwork with
each other in
peer-to-peer
mode and the
SoftX3000 acts
as an AS.
Therefore, set
Work mode to
IPSP.
BSGI module 136 and 137 The value is The value is

number obtained determined
through the LST during
BRD command. hardware data
planning.


Name Value Obtain
M3UA link data Local IP 191.169.150.30 The value is The value is

address1 obtained determined
FECFG hardware data
command. planning.
Peer IP address1 211.169.150.35 The value must -

be negotiated
with the SCP.
Local port Module 136: The value is If the system is

number 2905 determined by configured with
Module 137: the carrier. two BSGI
2911 modules,
allocate the two
M3UA links to
each of them.
This guarantees
reliability of the
M3UA links.
Peer port 2905 The value must -

number be negotiated
with the SCP.
Client/Server Client side The value must If the

mode be negotiated SoftX3000
with the SCP. directly
interworks with
the SCP in peer-
to-peer mode
without the
involvement of
the signaling
gateway, set
Client/Server
mode to Client
side
SCCP SCCP sub- SCMG 0x01 The value must If Fixed

subsystem data system number and INAP 0x0C be negotiated Intelligent
with the SCP. Network (FIN)
services are
deployed,
configure two
SSNs: SCMG
and INAP.

with the SCP.


Name Value Obtain

the carrier.
Documents
Huawei.
Workflow
2. Configure the SCCP data.
Procedure
NOTE
On the SoftX3000, LET is set to Application server.
point code of destination entity, DET=Destination entity type;
NOTE
The SoftX3000 interworks with the SCP in peer-to-peer mode and the entity type of the SoftX3000 is AS.
Therefore, you need to set Destination entity type to Application server on the SCP.
ADD M3LKS: LSX=Linkset index, ADX=Adjacent destination entity index, TW=Traffic
mode, WM=Work mode;
NOTE
M3UA signaling links in the associated signaling mode exist between the SoftX3000 and the SCP.
Therefore, set Adjacent entity index to the destination entity index of the SCP.
5. Add an M3UA route to the SCP.

1. Add an SCCP destination signaling point.

ADD SCCPDSP: DPX=DSP index, NI=Network indicator, DPC=DPC, OPC=OPC;
number, SPC=SPC, OPC=OPC;
NOTE
The SPC parameter is the DPC of the corresponding subsystem, that is, the receiving end of local
SCCP messages. For each subsystem, you must define two DSPs, namely, SCCP remote SP and local
SP.
ADD SCPADDR: SCP=SCP number, RT=Route flag, DPC=DPC;
NOTE
If the format of the SCP physical address is that of the SCP, you need to set Route flag to Addressing
by DPC.
NOTE
If the format of the SSP physical address is that of the SCP, you need to set Route flag to Addressing
by DPC.
----End
Example
Task Description
l Two M3UA links are established between the SoftX3000 and the SCP. Both links carry
SS7 links in the load—balancing mode.
l The normal SCCP connection is established between the SoftX3000 and the SCP.
Scripts
///Add an M3UA local entity.
//Add an M3UA destination entity.
ADD M3DE: DEX=50, LEX=0, DENAME="USAU", DPC="110e0e", DET=AS;
//Add an M3UA linkset.
ADD M3LKS: LSX=1, LSNAME="To USAU", ADX=50, WM=IPSP;
ADD M3LNK: MN=136, LNKN=1, LNKNAME="To SCP #0", LOCIP1="191.169.150.30",
LOCPORT=2905,
ADD M3LNK: MN=137, LNKN=1, LNKNAME="To SCP #1", LOCIP1="191.169.150.30",
LOCPORT=2911,
//Add an M3UA route to the SCP.
ADD M3RT: RTNAME="To USAU", DEX=50, LSX=0;
//Add an SCCP destination signaling point.
ADD SCCPDSP: DPX=2, NI=NAT, DPC="110e0e", OPC="001122", DPNAME="SCP",
SHAREFLAG=NONE;


ADD SCCPSSN: SSNX=4, NI=NAT, SSN=SCMG, SPC="110e0e", OPC="001122",
ADD SCCPSSN: SSNX=5, NI=NAT, SSN=INAP, SPC="110e0e", OPC="001122",
ADD SCPADDR: SCP=12, RT=DPC, DPC="110e0e";
Related Tasks
Related Concepts
For details about the relations between M3UA data tables, see 12.6.2 Relations Between M3UA
Signaling Data Tables.
8.1.3 Configuring Data to Interwork with SCP (INAP over IP)
Scenarios
Before configuring IN service data, configure signaling data for interworking between the
SoftX3000 and the SCP. Otherwise, IN services cannot be deployed. Figure 8-3 shows a typical
networking model where IP links carry INAP signaling (that is, INAP/TCP/IP) on both the
SoftX3000 side and the SCP/Service Management Control Point (SMCP) side.
Figure 8-3 Typical networking model for the SoftX3000 to interwork with the SCP/SMCP
(INAP over IP)
SoftX3000 SCP/SMCP
INAP over IP
INAP INAP
TCP TCP
IP IP
As shown in Figure 8-3, the SoftX3000 interworks with the SCP/SMCP through an IP interface
(physical FE port) provided by the HSCI in a frame instead of the IFMI.
In actual networking, internal Ethernet cables of the HSCI of each frame are connected to 0#LAN
Switch and 1#LAN Switch of the ICC. Therefore, the IP interface for the SoftX3000 to interwork
with the SCP/SMCP is led out through the Ethernet cables from 0#LAN Switch and 1#LAN
Switch of the ICC.

Prerequisites
Conditions
Data
Name
SSP physical OPC address 001122 The value is The value is

address data obtained through determined
the LST OFI during the local
command. office data
planning.
SCP physical DPC 110f0f The value must -

address data be negotiated
with the SCP/
SMCP.
INAP INAP type Argentina The value is By default, the

protocol data determined by SoftX3000
the carrier. supports
interworking
with the SCP
using the C-
INAP protocol
only. To enable
the SoftX3000 to
interwork with
the SCPs using
other types of the
INAP protocol
(for example, R-
INAP), you need
to set this
parameter to the
corresponding
value.
Application Default The value must -

context be negotiated
with the SCP/
SMCP.


Name
INAP over FCCU module 22 and 23 The value is The value is

IP data number obtained through determined
the LST BRD during
command. hardware data
planning.
Local IP address Module 22: The value is For different

0 10.72.32.22 determined by FCCU modules,
Module 23: the carrier. the local IP
10.72.32.23 address 0 must be
different.
To guarantee
reliability of the
internal Ethernet
communication
system of the
SoftX3000, the
local IP address
can neither be
within
172.20.XXX.X
XX or
172.30.XXX.X
XX nor be in the
same network
segment as the IP
address of the
IFMI.
Remote IP 10.72.32.16 The value must In normal cases,

address 0 be negotiated the SoftX3000
with the SCP/ must be directly
SMCP. connected with
the SMCP. That
is, the virtual IP
address on the
SoftX3000 side
must be in the
same network
segment as the IP
address of the
SMCP.


Name
SCP connect Connect SMCP The value must If the SoftX3000

type or SCP be negotiated interworks with
(SMCP_SCP) with the SCP/ the SCP/SMCP
SMCP. in INAP over IP
mode, you must
set SCP connect
type to Connect
SMCP or SCP.
Otherwise, the
IN services
cannot be
provided.
Remote port 7779 The value must The SCP/SMCP

number be negotiated works in Server
with the SCP/ mode on TCP
SMCP. links. Therefore,
TCP links of
each FCCU
module of the
SoftX3000 can
use the same
remote port
number.
Default gateway 10.72.32.1 The value is -

determined by
the carrier.
Mask 255.255.255.0 The value is -

determined by
the carrier.
SCCP SCCP sub- SCMG and The value must If Fixed

subsystem system number INAP be negotiated Intelligent
data with the SCP/ Network (FIN)
SMCP. services are
deployed,
configure two
SSNs: SCMG
and INAP.

with the SCP/
SMCP.

the carrier.


Name
Module Range of module Module 22: The value must l Dialog

dialog dialog numbers 0-1999 be negotiated number is a
number data Module 23: with the SCP/ kind of
2000-3999 SMCP. resource.
Currently,
there are
6000 dialog
numbers
(numbered
from 0 to
5999)
available
between the
SoftX3000
and an
SMCP.
l By default,
after a start
dialog
number is set
for an FCCU
module, the
SoftX3000
defines an
end dialog
number for
the FCCU
module, that
is, end dialog
number =
start dialog
number +
1999.
l Dialog
numbers used
by all FCCU
modules must
be different.
Otherwise,
call loss may
occur.
Documents
Huawei.

Workflow
1. Modify the setting of P201. (Optional)
2. Set INAP protocol data. (Optional)
3. Add a INAP over IP record.
4. Add an MTP destination signaling point.
8. Add a module dialog number record.
Procedure
Step 1 Modify the setting of P201. (Optional)
NOTE
If INAP over IP is applied in networking, the SMCP connects with the SoftX3000 directly by default. If
the SCP connects with SoftX3000 directly, change bit 10 of SSP internal parameter 2 (P201) to 0 and to
keep the parameter consistent with the software configuration on the SCP side. Otherwise, IN services
cannot be used.
Step 2 Set INAP protocol data. (Optional)

SET INAPTP: ITP=INAP type, AC=Application context;
Step 3 Add a INAP over IP record.
ADD INAPOIP: MN=FCCU module number, MEM0=Local IP address 0, SCP0=Remote IP
address 0, RP=Remote port number, DG=Default gateway, MASK=Mask;
Step 4 Add an MTP destination signaling point.
ADD N7DSP: DPX=DSP index, DPC=DPC, OPC=OPC;
Step 5 Add an SCCP subsystem.
ADD SCCPSSN: SSNX=SSN index, NI=Network indicator, SSN=SCCP sub-system number,
SPC=SPC, OPC=OPC;
NOTE
The SPC parameter is the DPC of the corresponding subsystem, that is, the receiving end of local SCCP
messages. For each subsystem, you must define two DSPs, namely, SCCP remote SP and local SP.
Step 6 Add an SCP physical address.

ADD SCPADDR: SCP=SCP number, RT=Route flag, DPC=DPC, SSN=SSN, SCT=SCP
connect type;
NOTE
The SCCP subsystem number specified in this command must be associated with an SCCP subsystem (To
associate an SCCP subsystem with the SCCP subsystem number, run ADD SCCPSSN with SCCP sub-
system number specified to the one required). Otherwise, the interworking between the SoftX3000 and
the SCP fails.
Step 7 Add an SSP physical address.

Step 8 Add a module dialog number record.

ADD DLGNUM: MN=FCCU module number, SN=Start dialog number;
----End
Example
Task Description
l Two TCP links in INAP over IP mode are established between the SoftX3000 and the SCP.
l The normal TCP connection is established between the SoftX3000 and the SCP.
Scripts
//Modify the setting of P201. (Optional)
MOD FSFP: ID=201, ModType=P1, Bit=10, BitVal=0;
//Set INAP protocol type to Argentina. (Optional)
SET INAPTP: ITP=Argentina, AC=Def;
//Add INAP over IP records.
ADD INAPOIP: MN=22, MEM0="10.72.32.22", SCP0="10.72.32.16", RP=7779,
DG="10.72.32.1",
MASK="255.255.255.0";
ADD INAPOIP: MN=23, MEM0="10.72.32.23", SCP0="10.72.32.16", RP=7779,
DG="10.72.32.1",
MASK="255.255.255.0";
//Add an MTP destination signaling point.
ADD N7DSP: DPX=60, DPC="110f0f", OPC="001122", DPNAME="SCP_SMCP";
ADD SCCPSSN: SSNX=4, NI=NAT, SSN=SCMG, SPC="110f0f", OPC="001122",
ADD SCCPSSN: SSNX=5, NI=NAT, SSN=INAP, SPC="110f0f", OPC="001122",
ADD SCPADDR: SCP=15, RT=DPC, DPC="110f0f", SSN=INAP, SCT=SMCP_SCP;
//Add module dialog number records.
ADD DLGNUM: MN=22, SN=0;
ADD DLGNUM: MN=23, SN=2000;
Related Tasks
None.
Related Concepts
12.6.5 Relations Between MTP Signaling Data Tables
8.2 Configuring Data to Interwork with PSTN

8.2.1 Configuring Data to Interwork with PSTN (M2UA - MTP)

Scenarios
When interworking with the traditional PSTN, the SoftX3000 usually adopts SS7 as the inter-
office signaling. For a PSTN switch, SS7 is based only on MTP links. For the SoftX3000, SS7
is based on multiple types of bearers. Figure 8-4 shows a typical networking model where
MTP2-User Adaptation Layer (M2UA) links are used to carry SS7 signaling on the SoftX3000
side.
Figure 8-4 Typical networking model for the SoftX3000 to interwork with the PSTN (M2UA
- MTP)
SoftX3000 MGW PSTN switch

MTP link/
M2UA
SS7 trunk
ISUP ISUP
MTP3
MTP3
M2UA M2UA MTP2
SCTP SCTP MTP2
MTP1 MTP1
IP IP
As shown in Figure 8-4, the SoftX3000 provides M2UA links for connection to the MGW
(usually the UMG8900). The SoftX3000 interworks with the PSTN switch by using SS7
signaling through the UMG8900 (with embedded SG functions). For voice channels, the
SoftX3000 interworks with the PSTN switch by controlling the MGW.
Prerequisites
Conditions

Data
To achieve interworking between the SoftX3000 and the PSTN, configure the following
interworking data on the SoftX3000:
l Data for interworking between the SoftX3000 and the UMG8900

l Data for interworking between the SoftX3000 and the PSTN switch
Assume that the data configuration planned is as shown in Table 8-5 and Table 8-6.

Table 8-5 Data for interworking between the SoftX3000 and the UMG8900
Name Value Obtain
MGW data Equipment ID 211.169.150.41: The value must When the

2944 be negotiated UMG8900
with the adopts H.248,
UMG8900. the format of
parameter
Equipment ID
is "IP
address:port
number".
Gateway type UMGW The value is -

determined by
the carrier.
FCCU/AGCU/ 23 The value is The value is

UACU module obtained determined
number through the LST during
planning.
Code type ASN.1 The value must The H.248

be negotiated protocol of the
with the UMG8900
UMG8900. adopts the
binary format.
Therefore,
Code type must
be set to ASN.1.
Local IP address 191.169.150.30 The value is The value is

obtained determined
FECFG hardware data
command. planning.
Remote IP 211.169.150.41 The value must You must set

address 1 be negotiated Remote IP
with the address 1 to the
UMG8900. IP address of the
UMG8900 used
for H.248.
Remote port 2944 The value must -

be negotiated
with the
UMG8900.


Name Value Obtain
Override True The value must -

dynamic IP be negotiated
with the
UMG8900.
Hairpin Supported The value must The UMG8900

connection be negotiated in the given
with the example
UMG8900. supports hairpin
connection.
Therefore,
Hairpin
connection
must be set to
Supported. If
the UMG8900
does not support
hairpin
connection, set
Hairpin
connection to
Not supported.
EC Supported The value must -

be negotiated
with the
UMG8900.
Signaling SG type Embedded SG The value is In the given

gateway data provided by the example, the
carrier. embedded SG in
the UMG8900 is
used to process
the M2UA
protocol.
Therefore, SG
type must be set
to Embedded
SG, and
Equipment ID
must be set to
the equipment
ID of the
UMG8900.
M2UA linkset M2UA linkset 0 The value is -

data index and determined by
1 the carrier.


Name Value Obtain
Traffic mode Loadshare The value must Set Traffic

be negotiated mode to
with the Loadshare for a
UMG8900. linkset, unless
specified
otherwise. The
traffic mode of
the linkset must
be consistent
with that on the
SG side.
Otherwise, none
of the M2UA
links of the
linkset works
normally.
Interface ID Integer The value must -

type be negotiated
with the
UMG8900.
M2UA link data BSGI module M2UA linkset The value is The value is
number 0: 136 obtained determined
and through the LST during
M2UA linkset BRD command. hardware data
1: 137 planning.
Link number M2UA linkset The value is You must set all
0: 0 determined by the M2UA links
and the carrier. of an M2UA
M2UA linkset linkset on one
1: 1 BSGI module.
To guarantee
reliability of
M2UA links,
allocate M2UA
links from the
SoftX3000 to
the same
embedded SG to
different BSGI
modules.
Therefore, you
must configure
two M2UA
linksets.


Name Value Obtain
Local port M2UA linkset The value is -

number 0: 2904 determined by
M2UA linkset the carrier.
1: 2910

with the
UMG8900
(embedded with
the SG).
Peer IP address1 211.169.150.42 The value must You must set

be negotiated Peer IP
with the address1 to the
UMG8900 IP address of the
(embedded with UMG8900 used
the SG). for SIGTRAN.
MTP link data Link number M2UA linkset The value is Different
0: 0 determined by M2UA linksets
M2UA linkset the carrier. carry SS7 traffic
1: 1 of different
MTP links.
Therefore,
M2UA linkset
index of the two
MTP links must
be different.
Link type M64K The value must The SoftX3000

be negotiated uses M2UA to
with the carry SS7 traffic
UMG8900 on MTP links.
(embedded with Therefore, set
the SG). Link type to
M2UA 64kbit/s
link.


Name Value Obtain
Integer interface MTP linkset 0: The value must For an MTP link
ID 101 be negotiated with M2UA to
MTP linkset 1: with the carry SS7 traffic
102 UMG8900 (a logical link on
(embedded with the SoftX3000
the SG). side), the
interface ID is
mandatory.
Different MTP
links have
different
interface IDs
(integer).
Start circuit MTP linkset 0: The value must Start circuit

terminator ID 16 be negotiated termination ID
MTP linkset 1: with the is a parameter
48 UMG8900 used for
(embedded with interworking
the SG). with a trunk
MGW. Start
circuit
termination ID
identifies the
circuit slot
number of the
trunk circuit that
bears the MTP
link in the trunk
MGW to which
the trunk circuit
belongs. For
example, if
Start circuit
termination ID
is set to 16, it
indicates that
the MTP link
occupies
timeslot 16 of
E1 line 0 on the
UMG8900 side.


Name Value Obtain
Signaling link MTP linkset 0: 0 The value must If the self-loop

code MTP linkset 1: 1 be negotiated test is not used
with the PSTN. for the MTP
link, set
Signaling link
code send and
Signaling link
code to the same
value.
Otherwise, the
signaling
interaction fails.
Trunk circuit Start circuit Trunk group 40: The value must Start circuit
data termination ID 0 be negotiated termination ID
Trunk group 41: with the is a parameter
32 UMG8900. used for
interworking
with a trunk
MGW. Start
circuit
termination ID
identifies the
start circuit
timeslot of a
specified batch
of trunk circuits
in the resident
trunk MGW.
For example, if
Start circuit
terminator ID
is set to 32, it
indicates that
the trunk
circuits belong
to E1 1 on the
UMG8900 side.


Name Value Obtain
Route data Route priority 1 The value must Route priority

be negotiated is a parameter
with the PSTN. used to
determine the
priority of a
MTP linkset
(signaling
route). The
SoftX3000
preferentially
selects the
linkset with
higher priority
and selects the
linkset with
lower priority
only when the
higher-priority
linksets are not
available. The
value 0 indicates
the highest
priority.
Table 8-6 Data for interworking between the SoftX3000 and the PSTN switch
Name Value Obtain
Office direction Destination 1100bb The value must -

data point code be negotiated
with the PSTN.
Network National The value must -

indicator network be negotiated
with the PSTN.
Peer office type Toll,urban&rur The value must -

al call office be negotiated
with the PSTN.


Name Value Obtain
Peer office level Inferior The value must To avoid

be negotiated alternate routing
with the PSTN. between offices
of the same
level, set one
office to a lower
level. For
example, if the
local office is a
transit office
and the peer
office is an end
office, set Peer
office level to
Inferior.
Prefix data Call prefix 0840 The value is -

determined by
the carrier.
Service attribute National toll The value is -

determined by
the carrier.
Trunk data OPC 001122 The value is The value is

obtained determined
through the LST during the local
OFI command. office data
planning.
Trunk group 40 The value is -

number and determined by
41 the carrier.
National China The value must -

Variant be negotiated
with the PSTN.
Group direction Trunk group 40: The value is -

outgoing trunk determined by
Trunk group 41: the carrier.
incoming trunk
Circuit type ISUP The value is The signaling

determined by used by the SS7
the carrier. trunk is ISUP.
Therefore, set
Circuit type to
ISUP.


Name Value Obtain
Trunk circuit Start circuit Trunk group 40: The value is Start circuit
data number 64 determined by number and
Trunk group 41: the carrier. End circuit
96 number are the
universal
logical numbers
of E1 trunk
circuits, such as
SS7, PRA, R2,
and V5, in an
FCCU module.
The physical
numbers of the
E1 trunk circuits
on the
UMG8900 side
are defined by
Start circuit
termination
ID.
End circuit Trunk group 40: The value is -

number 95 determined by
127
Start CIC Trunk group 40: The value must -

0 be negotiated
Trunk group 41: with the PSTN.
32
Documents
Huawei.
Workflow
The procedure for configuring data to interwork with PSTN is as follows:
1. Configure the MGW data.
3. Configure the MTP data.
4. Configure routing data.
5. Configure SS7 trunk data.
6. Configure a number analysis data.

Procedure
Step 1 Configure the MGW data.
ADD MGW: EID=Equipment ID, GWTP=Gateway type, MGCMODULENO=FCCU/AGCU/
UACU module number, LA=Local IP address, RA1=Remote IP address 1, RP=Remote port,
HAIRPIN=Hairpin connection, CODETYPE=Code type, ET=Encryption type,
OWDYNA=Override dynamic IP;

1. Add an embedded signaling gateway.
ADD M2LKS: M2LSX=M2UA linkset index, LSNAME=Linkset name, SGID=Signaling
gateway ID, TM=Traffic mode, IFT=Interface ID type;
3. Add two M2UA links.
ADD M2LNK: MN=BSGI module number, LNKN=Link number, M2LSX=M2UA
linkset index, LOCPORT=Local port number, LOCIP1=Local IP address1,
PEERPORT=Peer port number, PEERIP1=Peer IP address1;
Step 3 Configure the MTP data.

1. Add an MTP destination signaling point.
ADD N7DSP: DPX=DSP index, NI=Network indicator, DPC=DPC, OPC=OPC,
DPNAME=DSP name;
2. Add an MTP linkset.
ADD N7LKS: LSX=Linkset index, ASPX=Adjacent DSP index, LSNAME=Linkset
name;
NOTE
The SoftX3000 and the PSTN switch adopt the SS7 associated signaling mode. Therefore, set
Adjacent DSP index to the SP index of the PSTN switch.
3. Add an MTP link.
ADD N7LNK: MN=BSGI module number, LNKN=Link number, LNKNAME=Link
name, LNKTYPE=Link type, M2LSX=M2UA linkset index, BINIFID=Integer interface
ID, LSX=Linkset index, SLC=Signaling link code, SLCS=Signaling link code send,
TID=Start circuit terminator ID;
NOTE
The value of BSGI module number must be the same as that specified in Step 2.3.
4. Add an MTP route to the PSTN switch.
ADD N7RT: LSX=Linkset index, DPX=DSP index, PRI=Route priority,
RTNAME=Route name, SEQ=Route sequence;
Step 4 Configure routing data.

1. Add the office direction to the PSTN switch.
ADD OFC: O=Office direction number, ON=Office direction name, DOT=Peer office
type, DOL=Peer office level, DPC1=Destination point code 1;
NOTE
This office direction has SS7 trunk circuits. Therefore, you must specify DPC. Otherwise, errors
occur when you add an SS7 trunk group by running ADD N7TG.

2. Add a subroute.
ADD SRT: SRC=Sub-route number, O=Office direction number, RENT=Is rented
subroute;
3. Add a route.
ADD RT: R=Route number, SR1=1st sub-route;
4. Add route analysis data for the route to the PSTN switch.
ADD RTANA: RSC=Route selection code, RSSC=Route selection source code,
RUT=Caller category, SAI=Service attribute, CLR=Caller access, TP=Transmission
capability, TM=Time mode, TMX=Time index, R=Route number, ISUP=Signaling as
prior;
NOTE
Set Caller category, Service attribute, Caller access, and Transmission capability to All
categories, unless specified otherwise.
Step 5 Configure SS7 trunk data.

1. Add an SS7 trunk group.
ADD N7TG: TG=Trunk group number, EID=Equipment ID, G=Group direction,
SRC=Sub-route number, CT=Circuit type, RCHS=Charging source code,
OTCS=Outgoing trunk charging source code, PRTFLG=National Variant, NOAA=NOA
attribute, ISM=ISUP mask, EA=Enhanced attribute;
NOTE
l If destination code charging is used for trunk groups, set Charging source code or Outgoing
trunk charging source code to the value of Caller charging source code in the ADD
CHGIDX command.
l To prevent the peer office from starting incoming calls through the outgoing trunks on the local
office side, define the charging source code and outgoing trunk charging source code for both
incoming and outgoing trunk groups on the local office side.
2. Add an SS7 trunk circuit.
ADD N7TKC: MN=FCCU module number, TG=Trunk group number, SC=Start circuit
number, EC=End circuit number, SCIC=Start CIC, TID=Start circuit terminator ID;
Step 6 Add a number analysis record.

ADD CNACLD: LP=Local DN set, PFX=Call prefix, CSTP=Service category, CSA=Service
attribute, RSC=Route selection code, MINL=Minimum number length, MAXL=Maximum
number length, CHSC=Charging selection code, EA=Enhanced attribute;
NOTE
l The prefix added represents outgoing calls. Therefore, set Route selection code to the value of Route
selection code in the ADD RTANA command.
l If destination code charging is used for the prefix, set Charging selection code to the value of Charging
selection code in the ADD CHGIDX command.
----End
Example
Task Description

l Two E1 circuits are set up for interworking between the SoftX3000 and the PSTN switch
l Two M2UA links are established between the SoftX3000 and the UMG8900. Two 64 kbit/
s MTP links are established between the UMG8900 and the PSTN switch. Each M2UA
link carries the SS7 signaling from one MTP link.
l Subscriber served by the SoftX3000 and subscribers served by the PSTN switch can make
calls to each other.
l Destination code charging is used for calls made by a subscriber served by the SoftX3000
to a subscriber served by the PSTN switch.
l Destination code charging is used for trunks from the SoftX3000 to the PSTN switch (for
settlement between carriers).
Scripts
//Add a UMG8900.
ADD MGW: EID="211.169.150.41:2944", GWTP=UMGW, MGWDESC="Shenzhen-
UMG8900-03",
MGCMODULENO=23, LA="191.169.150.30", RA1="211.169.150.41", RP=2944,
HAIRPIN=S,
CODETYPE=ASN, ET=NO, OWDYNA=TRUE;
//Add an embedded signaling gateway.

ADD SG: SGID=2, SGNAME="M2UA SG", SGTYPE=EMB, EID="211.169.150.41:2944";
//Add two M2UA linkset.

ADD M2LKS: M2LSX=0, LSNAME="M2UA LinkSet 0", SGID=2, TM=LOADSHARE,
IFT=INTEGER;
ADD M2LKS: M2LSX=1, LSNAME="M2UA LinkSet 1", SGID=2, TM=LOADSHARE,
IFT=INTEGER;

ADD M2LNK: MN=136, LNKN=0, M2LSX=0, LOCPORT=2904,
LOCIP1="191.169.150.30",
PEERIP1="211.169.150.42";
LOCIP1="191.169.150.30",
PEERIP1="211.169.150.42";
//Add an MTP destination signaling point.

ADD N7DSP: DPX=30, DPC="1100bb", DPNAME="E_office";
//Add an MTP linkset.

ADD N7LKS: LSX=1, ASPX=30, LSNAME="To E_office";
//Add two MTP links.

ADD N7LNK: MN=136, LNKN=0, LNKNAME="To E_office", LNKTYPE=M64K, M2LSX=0,
BINIFID=101, LSX=1, SLC=0, SLCS=0, TID=16;
ADD N7LNK: MN=137, LNKN=1, LNKNAME="To E_office", LNKTYPE=M64K, M2LSX=1,
//Add an MTP route to the PSTN switch.

ADD N7RT: LSX=1, DPX=30, PRI=1, RTNAME="To E_office";
//Add an office direction to the PSTN switch.

ADD OFC: O=40, ON="E_office", DOT=CMPX, DOL=LOW, DPC1="1100bb";
//Add a subroute.
ADD SRT: SRC=40, O=40, SRN="To E_office", RENT=URT;
//Add a route.
ADD RT: R=40, RN="To E_office", IDTP=UNKNOWN, NAMECFG=NO, SNCM=SRT,
SRST=SEQ, SR1=40,
STTP=INVALID, REM=NO;
//Add a route analysis record for the route to the PSTN switch.
ADD RTANA: RSC=84, RSSC=0, RUT=ALL, SAI=ALL, CLR=ALL, TP=ALL, TM=TMM,
TMX=0,
CST=ALL, CNPI=ALL, R=40, ISUP=NOCHG;
ADD N7TG: TG=40, EID="211.169.150.41:2944", G=OUT, SRC=40,
SOPC="001122",
CT=ISUP, RCHS=88, OTCS=99, PRTFLG=CN, NOAA=FALSE, ISM=FALSE, EA=FALSE;
ADD N7TG: TG=41, EID="211.169.150.41:2944", G=IN, SRC=40, SOPC="001122",
//Add SS7 trunk circuits.

ADD N7TKC: MN=23, TG=40, SC=64, EC=95, SCIC=0, SCF=FALSE, TID=0;
//Add a call prefix.

ADD CNACLD: LP=0, PFX=K'0840, CSTP=BASE, CSA=NTT, RSC=84, MINL=4,
MAXL=24, CHSC=0, EA=YES;
Related Tasks
Commissioning the Interworking with Other Networks (No.7)
Related Concepts
l For details about the relations between M2UA data tables, see 12.6.1 Relations Between
M2UA Signaling Data Tables.
l For details about the relations between MTP signaling data tables, see 12.6.5 Relations
Between MTP Signaling Data Tables.
l For details about the relations between route data tables, see 12.7 Relations Between Route
Data Tables.
l For details about the relations between SS7 trunk circuit tables. see 12.8.1 Relations
Between N0.7 Trunk Circuit Data Tables.
Scenarios
When interworking with the traditional PSTN, the SoftX3000 usually adopts SS7 as the inter-
office signaling. For a PSTN switch, SS7 is carried based on MTP links only. For the SoftX3000,
SS7 is based on multiple types of bearers. Figure 8-5 shows a typical networking model where
MTP3-User Adaptation Layer (M3UA) links are used to carry SS7 on the SoftX3000 side.

Figure 8-5 Typical networking model for the SoftX3000 to interwork with the PSTN (M3UA
- MTP)
SoftX3000 SG7000 STP
M3UA No.7
signaling
network
H.248
MTP link
MGW NO.7 trunk circuit PSTN switch
IP TDM
SoftX3000 SG7000 PSTN switch
ISUP ISUP
M3UA M3UA MTP3 MTP3
SCTP SCTP MTP2 MTP2
IP IP MTP1 MTP1
As shown in Figure 8-5, the SoftX3000 provides M3UA links for connection to the SG7000.
The SoftX3000 interworks with the PSTN switch by using SS7 signaling through the SG7000.
For voice channels, the SoftX3000 interworks with the PSTN switch by controlling the MGW
(usually the UMG8900).
Prerequisites
Conditions
Data
To achieve signaling interaction between the SoftX3000 and the PSTN switch, configure the
following data on the SoftX3000:
l Data for interworking between the SoftX3000 and the UMG8900
l Data for interworking between the SoftX3000 and the SG7000
l Data for interworking between the SoftX3000 and the PSTN switch
Assume that the data configuration planned is as shown in Table 8-7, Table 8-8, and Table
8-9.

Name Value Obtain
MGW data Equipment ID 211.169.150.41: The value must When the

2944 be negotiated UMG8900
with the adopts H.248,
UMG8900. the format of
parameter
Equipment ID
is "IP
address:port
number".
Gateway type UMGW The value is -

determined by
the carrier.
FCCU/AGCU/ 23 The value is The value is

UACU module obtained determined
number through the LST during
planning.
Code type ASN.1 The value must The H.248

be negotiated protocol of the
with the UMG8900
UMG8900. adopts the
binary format.
Therefore,
Code type must
be set to ASN.1.

obtained determined
FECFG hardware data
command. planning.
Remote IP 211.169.150.43 The value must You must set

address 1 be negotiated Remote IP
with the address 1 to the
UMG8900. IP address of the
UMG8900 used
for H.248.
Remote port 2944 The value must -

be negotiated
with the
UMG8900.


Name Value Obtain
Override True The value must -

dynamic IP be negotiated
with the
UMG8900.
Hairpin Supported The value must The UMG8900

connection be negotiated in the given
with the example
UMG8900. supports hairpin
connection.
Therefore,
Hairpin
connection
must be set to
Supported. If
the UMG8900
does not support
hairpin
connection, set
Hairpin
connection to
Not supported.
EC Supported The value must -

be negotiated
with the
UMG8900.
Trunk circuit Start circuit Trunk group 50: The value must Start circuit
data termination ID 0 be negotiated number and
Trunk group 51: with the End circuit
32 UMG8900. number are the
universal
logical numbers
of E1 trunk
circuits, such as
SS7, PRA, R2,
and V5, in an
FCCU module.
The physical
numbers of the
E1 trunk circuits
on the
UMG8900 side
are defined by
Start circuit
termination
ID.

Table 8-8 Data for interworking between the SoftX3000 and the SG7000

Name Value Obtain
M3UA local Signaling point 001122 The value is The value is

entity data code of local obtained determined
entity through the LST during the local
planning.
Local entity Application The value must -

type server be negotiated
with the SG.
Route context 12345 The value must -

be negotiated
with the SG.
M3UA Destination 10 The value is -

destination entity index 20 determined by
entity data the carrier.
Destination Destination The value must -

entity type entity 10: SG be negotiated
Destination with the SG and
entity 20: SP the PSTN.
Signaling point Destination The value must -

code of entity 10: be negotiated
destination 001177 with the SG and
entity Destination the PSTN.
entity 20:
1100cc
Client/Server National The value is -

mode network determined by
the carrier.
M3UA linkset Traffic mode Loadshare The value must The traffic mode
data be negotiated of the linkset
with the SG. must be
consistent with
that on the SG
side. Otherwise,
none of the
M3UA links of
the linkset
works normally.
Set Traffic
mode to
Loadshare for a
linkset, unless
specified
otherwise.


Name Value Obtain
Work mode ASP The value must The SoftX3000

be negotiated and the SG7000
with the SG. interwork with
each other in
non-peer-to-
peer mode and
the SoftX3000
acts as an AS.
Therefore, set
Work mode to
ASP.
M3UA link data BSGI module 136 and 137 The value is The value is
number obtained determined
planning.
Local IP 191.169.150.30 The value is The value is

address1 obtained determined
FECFG hardware data
command. planning.
Peer IP address1 211.169.150.70 The value must -

be negotiated
with the SG.
Local port Module 136: The value is If the system is

number 2905 determined by configured with
Module 137: the carrier. two BSGI
2911 modules,
allocate the two
M3UA links to
each of them.
This guarantees
reliability of the
M3UA links.

with the SG.


Name Value Obtain
Client/Server Client side The value must If the

mode be negotiated SoftX3000 in
with the SG. the non-peer-to-
peer
interworking
mode serves as
the application
server, set
Client/Server
mode to Client
side.
Name Value Obtain
Office direction Destination 1100cc The value must -

data point code be negotiated
with the PSTN.
Network National The value must -

indicator network be negotiated
with the PSTN.

with the PSTN.
Peer office level Superior The value must To avoid

of the same
level, set one
office to a
higher level. For
example, if the
local office and
the peer office
are both
gateway offices,
set Peer office
level to
Superior.
Prefix data Call prefix 0850 The value is -

determined by
the carrier.


Name Value Obtain
Service attribute National toll The value is -

determined by
the carrier.
Trunk data Trunk group 50 The value is -

number and determined by
51 the carrier.
OPC 001122 The value is The value is

obtained determined
through the LST during the local
planning.
National China The value must -

Variant be negotiated
with the PSTN.

incoming trunk
Circuit type ISUP The value is The signaling

determined by used by the SS7
the carrier. trunk is ISUP.
Therefore, set
Circuit type to
ISUP.


Name Value Obtain
Trunk circuit Start circuit Trunk group 50: The value is Start circuit
data number 128 determined by termination ID
Trunk group 51: the carrier. is a parameter
160 used for
interworking
with a trunk
MGW. Start
circuit
termination ID
identifies the
start circuit
timeslot of a
specified batch
of trunk circuits
in the resident
trunk MGW.
For example, if
Start circuit
terminator ID
is set to 32, it
indicates that
the trunk
circuits belong
to E1 1 on the
UMG8900 side.
End circuit Trunk group 50: The value is The absolute

number 159 determined by value of the
Trunk group 51: the carrier. difference
191 between the
start circuit
number and the
start circuit
termination ID
must be a
multiple of 32,
such as 0, 32, 64,
and 96.
Start CIC Trunk group 50: The value must -

0 be negotiated
Trunk group 51: with the PSTN.
32
Documents
Huawei.

Workflow
The procedure for configuring data to interwork with PSTN is as follows:
5. Add a number analysis record.
Procedure
HAIRPIN=Hairpin connection, CODETYPE=Code type, ET=Encryption type,
OWDYNA=Override dynamic IP;


point code of destination entity, STPF=STP flag, DET=Destination entity type;
NOTE
l The SoftX3000 interworks with the SG7000 in non-peer-to-peer mode. Therefore, set Local
entity type to Application server on the SoftX3000 and Destination entity type to Signaling
gateway on the SG7000.
l The exchange of SS7 signaling between the SoftX3000 and the SCP is achieved through the
SG7000. Therefore, set Destination entity type to Signaling point on the SCP.
l On the signaling network, the SG7000 transfers signaling. Therefore, set STP flag to YES.
Otherwise, errors may occur when you add an M3UA route by running ADD M3RT.
ADD M3LKS: LSX=Linkset index, ADX=Adjacent destination entity index, WM=Work
mode;
NOTE
M3UA signaling links in the associated signaling mode exist between the SoftX3000 and the SG7000.
Therefore, set Adjacent entity index to the destination entity index of the SG7000. In the given
example, Adjacent entity index is set to 10.
5. Add an M3UA route to the PSTN switch.

1. Add the office direction to the PSTN switch.

type, DOL=Peer office level, DPC1=Destination point code 1;
NOTE
This office direction has SS7 trunk circuits. Therefore, you must specify DPC. Otherwise, errors
occur when you add an SS7 trunk group by running ADD N7TG.
2. Add a subroute.
subroute;
3. Add a route.
ADD RT: R=Route number, SR1=1st sub-route;
4. Add route analysis data for the route to the PSTN switch.
prior;
NOTE
Set Caller category, Service attribute, Caller access, Transmission capability, and Called
number plan identity to All categories, unless specified otherwise.

1. Add an SS7 trunk group.
ADD N7TG: TG=Trunk group number, EID=Equipment ID, G=Group direction,
SRC=Sub-route number, CT=Circuit type, RCHS=Charging source code,
OTCS=Outgoing trunk charging source code, PRTFLG=National Variant, NOAA=NOA
attribute, ISM=ISUP mask, EA=Enhanced attribute;
NOTE
l If destination code charging is used for trunk groups, set Charging source code or Outgoing
trunk charging source code to the value of Caller charging source code in the ADD
CHGIDX command.
office side, define the charging source code and outgoing trunk charging source code for both
2. Add an SS7 trunk circuit.
number, EC=End circuit number, SCIC=Start CIC, TID=Start circuit terminator ID;
Step 5 Add a number analysis record.

NOTE
----End

Example
Task Description
l Two E1 circuits are set up for interworking between the SoftX3000 and the PSTN switch
l Two M3UA links are established between the SoftX3000 and the SG7000. Both links carry
SS7 signaling in load-sharing mode.
l Subscriber served by the SoftX3000 and subscribers served by the PSTN switch can make
calls to each other.
l Destination code charging is used for calls made by a subscriber served by the SoftX3000
to a subscriber served by the PSTN switch.
l Destination code charging is used for trunks from the SoftX3000 to the PSTN switch (for
settlement between carriers).
Scripts
//Add a UMG8900 with the equipment ID being 211.169.150.43:2944.
ADD MGW: EID="211.169.150.43:2944", GWTP=UMGW, MGWDESC="ShenZhen-
UMG8900-04",
HAIRPIN=S,
CODETYPE=ASN, ET=NO, OWDYNA=TRUE;
//Add an M3UA local entity. The index of the local entity is 0. The originating point code is
001122. The routing context is 12345.
//Add two M3UA destination entities. The destination entity index 10 stands for the SG7000
connected to SoftX3000 in the associated signaling mode, and 20 stands for the PSTN switch.
ADD M3DE: DEX=10, LEX=0, DENAME="SG7000", DPC="001177", STPF=YES, DET=SG;
ADD M3DE: DEX=20, LEX=0, DENAME="PSTN Switch", DPC="1100cc", DET=SP;
//Add an M3UA linkset. The index of the linkset is 0. The index of the adjacent entity is 10.
ADD M3LKS: LSX=0, LSNAME="To SG7000", ADX=10, TM=LOADSHARE, WM=ASP;
//Add two M3UA links. Set the SoftX3000 as the client, the local SCTP port number of link 0
of module 136 to 2905, the local SCTP port number of link 0 of module 137 to 2911, and the
peer SCTP port number to 2905 (default value).
LOCIP1="191.169.150.30", LOCPORT=2905, PEERIP1="211.169.150.70",
PEERPORT=2905, CS=C, LSX=0;
//Add an M3UA route to the PSTN switch, whose destination entity index is 20. Add an M3UA
route to the SG7000, whose destination entity index is 10.
ADD M3RT: RTNAME="To F_office", DEX=20, LSX=0;
ADD M3RT: RTNAME="To SG7000", DEX=10, LSX=0;
//Add an office direction numbered 50 to the PSTN switch. The DPC is 1100cc.

ADD OFC: O=50, ON="F_office", DOT=CMPX, DOL=HIGH, DPC1="1100cc";
//Add a sub-route numbered 50.

ADD SRT: SRC=50, O=50, SRN="To F_office", RENT=URT;
//Add a route numbered 50.

ADD RT: R=50, RN="To F_office", IDTP=UNKNOWN, NAMECFG=NO, SNCM=SRT,
SRST=SEQ, SR1=50,
//Add analysis data for the route to the PSTN switch. The route selection code is 85.
TMX=0, NCAI=ALL, CST=ALL, CNPI=ALL, R=50, ISUP=NOCHG;
ADD N7TG: TG=50, EID="211.169.150.43:2944", G=OUT, SRC=50, SOPC="001122",
//Add SS7 trunk circuits. The start CICs are 0 and 32 respectively.
//Add the call prefix 0850.

MAXL=24, CHSC=0, EA=NO;
Related Tasks
Commissioning the Interworking with Other Networks (No.7)
Related Concepts
l For details about the relations between M3UA data tables, see 12.6.2 Relations Between
l For details about the relations between MTP signaling data tables, see 12.6.5 Relations
Between MTP Signaling Data Tables.
l For details about the relations between route data tables, see 12.7 Relations Between Route
Data Tables.
l For details about the relations between SS7 trunk circuit tables. see 12.8.1 Relations
Between N0.7 Trunk Circuit Data Tables.
8.3 Configuring Data to Interwork with H.323 Network

8.3.1 Configuring Data to Interwork with H.323 Network (GK - GW)
8.3.2 Configuring Data to Interwork with H.323 Network (GK - Upper-Level GK)
8.3.3 Configuring Data to Interwork with H.323 Network (GW - Outer GK)

8.3.1 Configuring Data to Interwork with H.323 Network (GK - GW)

Scenarios
When interworking with a traditional H.323 network, the SoftX3000 can act either as a
GateKeeper (GK) or a GateWay (GW). When the SoftX3000 acts as a GK (only supporting
routing calls) and the peer device acts as a GW (such as the A8010 Expert) in the same H.323
network, a typical networking model is as shown in Figure 8-6.
Figure 8-6 Typical networking model for the SoftX3000 to interwork with an H.323 network
(GK - GW)
SoftX3000 (GK)
H.323 H.323
trunk trunk
PSTN PSTN
A8010 Expert A8010 Expert
Switch in Switch in
(GW) (GW)
city A city B
As shown in Figure 8-6, the coverage of the SoftX3000 is called an "area". In the area, the
SoftX3000 performs functions such as subscriber address resolution and authentication,
provision of routing information for the controlled gateways, and call connection and release.
Prerequisites
Conditions
Data
You need to configure the data for interworking between the SoftX3000 and the H.323 gateways.

Table 8-10 Data for interworking between the SoftX3000 and the A8010 Expert
Catego Parameter Name Example Value How to Obtain Description
ry
H.323 System name SoftX3000 The value is The value is

protoco (SYSNM) obtained through determined
l data the LST during H.323
H323SYS protocol data
command. planning.
Configure the
H.323 protocol
data.
Call local Call local The value is The value is

minimum port minimum port obtained through determined
value value: 6000 the LST during H.323
and Call local H323APP protocol data
Call local maximum port command. planning.
maximum port value : 10000 Configure the
value H.323 protocol
data.
Routing Office direction Office A: 71 The value is -

data number Office B: 72 determined by
the carrier.
Peer office type Toll,urban&rural The value must -

call office be negotiated
with the PSTN.

of the same level,
set one office to a
lower level. For
example, if the
local office acts
as a GK and
offices A and B
are end offices,
set Peer office
level to Inferior
for offices A and
B.
Toll call Call prefix Office A: 0711 The value is -

prefix Office B: 0722 determined by
data the carrier.
Service attribute Service attribute The value is -

(CSA) determined by
the carrier.

Catego Parameter Name Example Value How to Obtain Description

ry
H.323 Maximum caller HCIC: 200 The value is -

trunk number restriction LCIC: 180 determined by
data and the carrier.
Stop call restriction
H323 trunk type H323 GW trunk The value must The SoftX3000
be negotiated interworks with
with the PSTN. H.323 gateways.
Therefore, set
H323 trunk
type to H323
GW trunk.
FCCU module 23 The value is The value is

number obtained through determined
the LST BRD during
command. hardware data
planning.
Gateway alias Office A: office_a The value must -

Office B: office_b be negotiated
with the PSTN.
Documents
Huawei.
Workflow
The procedure for configuring data to interwork with H.323 network is as follows:
1. Configure the H.323 protocol data.
3. Add an H.323 trunk group.
4. Add a call prefix.
Procedure
Step 1 Configure the H.323 protocol data.
NOTE
The H.323 protocol data is public data. Therefore, you need not configure the data here if the data is already
configured in other operations.
1. Add H.323 system information.
2. Add H.323 application information.


NOTE

1. Add an office direction.
ADD OFC: O=Office direction number, DOT=Peer office type, DOL=Peer office level;
2. Add a subroute.
subroute;
3. Add a route.
ADD RT: R=Route number, IDTP=UNKNOWN, NAMECFG=NO, SNCM=SRT,
SRST=SEQ, SR1=1st sub-route, STTP=INVALID, REM=NO;
4. Add routing analysis data.
prior;
NOTE
l Set Caller category, Service attribute, Caller access, Transmission capability, and Called
number Plan identity to All categories, unless specified otherwise.
l The local office and the peer office use H.323 for signaling interworking. Therefore, set Signaling
as prior to Must select H323.
Step 3 Add an H.323 trunk group.

ADD H323TG: TRUNKNO=Trunk group number, CSC=Call source code, SRT=Sub-route
number, GD=Group direction, TRNKTYPE=H323 trunk type, CCMID=FCCU module number,
EID=Gateway alias, RCHSRC=Charging source code, OTCHSRC=Outgoing trunk charging
source code, HCIC=Maximum caller number restriction, LCIC=Stop call restriction,
EA=Enhanced Attribute;
NOTE
If destination code charging is used for incoming trunk groups, set Charging source code or Outgoing
trunk charging source code to the value of Caller charging source code in the ADD CHGIDX command.
Step 4 Add a call prefix.

NOTE
----End

Example
Task Description
l Subscribers served office A and subscribers served by office B can make calls to each other.
l Destination code charging is used for calls made from office A to office B. That is,
destination code charging is used for the incoming trunk from office A to the SoftX3000.
l Destination code charging is used for calls made from office B to office A. That is,
destination code charging is used for the incoming trunk from office B to the SoftX3000.
Scripts
//Add the system configuration of the H.323 protocol.

//Add application layer data of the H.323 protocol.
CALLMAXPRT=10000;
//Add two office directions.
ADD OFC: O=71, ON="A_office", DOT=CMPX, DOL=LOW;
ADD OFC: O=72, ON="B_office", DOT=CMPX, DOL=LOW;
//Add two subroutes.
ADD SRT: SRC=71, O=71, SRN="To A_office", RENT=URT;
ADD SRT: SRC=72, O=72, SRN="To B_office", RENT=URT;
//Add two routes.
ADD RT: R=71, RN="To A_office", IDTP=UNKNOWN, NAMECFG=NO, SNCM=SRT,
SRST=SEQ, SR1=71,
ADD RT: R=72, RN="To B_office", IDTP=UNKNOWN, NAMECFG=NO, SNCM=SRT,
SRST=SEQ, SR1=72,
//Add routing analysis data.
TMX=0, R=71,
ISUP=H323_M, NCAI=ALL, CST=ALL, CNPI=ALL;
TMX=0, R=72,
//Add two H.323 trunk group.
ADD H323TG: TRUNKNO=71, CSC=0, SRT=71, GD=TINOUT, TGNM="To A_office",
TRNKTYPE=GW, CCMID=23,
EID="office_a", RCHSRC=88, OTCHSRC=65535, HCIC=200, LCIC=180, EA=YES,
E2833F=NSUPPORT, VIDEOS=SUPPORT;
ADD H323TG: TRUNKNO=72, CSC=0, SRT=72, GD=TINOUT, TGNM="To B_office",
TRNKTYPE=GW, CCMID=23,
EID="office_b", RCHSRC=88, OTCHSRC=65535, HCIC=200, LCIC=180, EA=YES,
E2833F=NSUPPORT, VIDEOS=SUPPORT;
//Add call prefixes.
Related Tasks

Related Concepts
12.4 Relations Between Number Analysis Data Tables
12.7 Relations Between Route Data Tables
8.3.2 Configuring Data to Interwork with H.323 Network (GK -

Upper-Level GK)
Scenarios
When interworking with a traditional H.323 network, the SoftX3000 can act either as a GK or
a GW. Figure 8-7 shows a typical networking model where the SoftX3000 acts as a level-1 GK
in a two-level network and the peer device is a top GK in the same H.323 network (or a GK in
a different H.323 network).
(GK - upper-level GK)
SoftX3000 (GK) Top GK Level-1 GK
H.323 trunk H.323 trunk
IP packet IP packet IP packet

network network network
H.323 H.323
network in network in
area A area B
H.323 GW H.323 GW H.323 terminal H.323 GW
As shown in Figure 8-7, the top GK implements address resolution, call setup, and call release
between the SoftX3000 and another level-1 GK.
Prerequisites
Conditions

Data
You need to configure the data for interworking between the SoftX3000 and the upper-level
GK. Assume that the data configuration planned is as shown in Table 8-11.

Table 8-11 Data for interworking between the SoftX3000 and the A8010 Expert
Name Value Obtain
H.323 protocol System name SoftX3000 The value is The value is

data obtained determined
through the LST during H.323
command. planning.
Configure the
H.323 protocol
data.

minimum port minimum port obtained determined
value value: 6000 through the LST during H.323
data.
Routing data Office direction 73 The value is -

number determined by
the carrier.

with the GK.

with the GK. between offices
of the same
level, set one
office to a
higher level. For
example, if the
local office is an
end office and
the peer office is
a toll office, set
Peer office
level to
Superior.
Call prefix data National toll 073, 074 The value is -

area code of area determined by
B the carrier.
H.323 trunk Trunk group 73 and 74 The value is -

data number determined by
the carrier.


Name Value Obtain

incoming trunk
H323 trunk type H323 GW trunk The value must The SoftX3000
be negotiated acts as a level-1
with the GK. GK and a top
GK interworks
with the
SoftX3000.
Therefore, set
H.323 trunk
type to H.323
GK trunk.
Trunk IP 211.169.150.1 The value must -

address be negotiated
with the GK.
RAS trunk port 1719 The value must -

with the GK.
Maximum HCIC: 200 The value is -

caller number LCIC: 180 determined by
restriction the carrier.
and
Stop call
restriction
Send tech- Trunk group 73: The value must -

prefix flag 12345 be negotiated
Trunk group 74: with the GK.
54321
Virtual trunk H323 trunk type H323 virtual The value must Set H323 trunk
data trunk be negotiated type to H323
with the GK. virtual trunk.


Name Value Obtain

with the GK. between offices
of the same
level, set one
office to a
higher level. For
example, if the
local office is an
end office and
the peer office is
a toll office, set
Peer office
level to
Superior.
Send tech- Trunk groups The value must -

prefix flag 73: 12345# be negotiated
Trunk group 74: with the GK.
54321#
IP address 211.169.150.1 The value must -

be negotiated
with the GK.
Mask 255.255.255.12 The value must -

8 be negotiated
with the GK.
Documents
Huawei.
Workflow
5. Configure H.323 virtual trunk group data.
Procedure
Step 1 Configure the H.323 protocol data. For details, see Configure the H.323 protocol data.


2. Add a subroute.
subroute;
3. Add a route.
prior;
NOTE
Step 3 Add the H.323 trunk group from the local office to the upper-level GK.
number, GD=Group direction, TRNKTYPE=H323 trunk type, TRNKIP=Trunk IP address,
RASTRNKPORT=RAS trunk port number, SNDTECH=Send tech-prefix flag, TECH=Tech-
prefix, RCHSRC=Charging source code, OTCHSRC=Outgoing trunk charging source code,
HCIC=Maximum caller number restriction, LCIC=Stop call restriction;
NOTE
If destination code charging is used for the trunk group, set Charging source code or Outgoing trunk
charging source code to the value of Caller charging source code in the ADD CHGIDX command.

NOTE
Step 5 Configure optional data.
In actual networking, if a GK in area B does not support Q.931 and the peer GK starts an incoming
call, the GK in area B exchanges RAS messages with the SoftX3000 and then instructs the GW
under its control to interact Q.931 messages with the SoftX3000 directly. In this case, the
SoftX3000 cannot match the call source code and the charging source code for this incoming
call. As a result, the charging and authentication in the local office fails. To solve this problem,
configure a virtual H.323 trunk from this GW to the SoftX3000.

NOTE
When an office direction contains H.323 trunks, you can define only one H.323 trunk group for this office
direction. In this case, define different office directions and sub-routes for different H.323 trunks.
2. Add a subroute.
subroute;
3. Add an virtual IP address.
ADD IPLIST: IPLISTNO=IP list number, IP=IP address, MSK=Mask;
4. Add an H.323 incoming trunk group from the H.323 GW to the local GK
ADD H323TG: TTRUNKNO=Trunk group number, CSC=Call source code, SRT=Sub-
route number, GD=Group direction, TRNKTYPE=H323 trunk type, IPLISTNO=IP list
number, RCHSRC=Charging source code, OTCHSRC=Outgoing trunk charging source
code, HCIC=Maximum caller number restriction, LCIC=Stop call restriction;
----End
Example
Task Description
l Subscribers in area A and subscribers in area B can make calls to each other.
l Destination code charging is used for calls made from area A to area B. That is, destination
code charging is used for the outgoing trunk from the SoftX3000 to the upper-level GK.
l Destination code charging is used for calls made from area B to area A. That is, destination
code charging is used for the incoming trunk from the upper-level GK to the SoftX3000.
Scripts

CALLMAXPRT=10000;
//Add an office direction to area B.

ADD OFC: O=73, ON="B_area", DOT=CMPX, DOL=HIGH;
//Add a subroute.
ADD SRT: SRC=73, O=73, SRN="To B_area", RENT=URT;
//Add a route.
ADD RT: R=73, RN="To B_area", IDTP=UNKNOWN, NAMECFG=NO, SNCM=SRT,
SRST=SEQ, SR1=73,
//Add route analysis data for the route to area B.


TMX=0, R=73,
//Add the H.323 trunk group from the local office to the upper-level GK.
ADD H323TG: TRUNKNO=73, CSC=0, SRT=73, GD=TOUT, TGNM="To B_area",
TRNKTYPE=GK, TRNKIP="211.169.150.1",
RASTRNKPORT=1719, SNDTECH=SEND, TECH="12345#", OTCHSRC=99, HCIC=200,
LCIC=180;
ADD H323TG: TRUNKNO=74, CSC=0, SRT=73, GD=TIN, TGNM="To B_area",
TRNKTYPE=GK, TRNKIP="211.169.150.1",
RASTRNKPORT=1719, SNDTECH=SEND, TECH="54321#", RCHSRC=88, OTCHSRC=65535,
HCIC=200, LCIC=180;
ADD CNACLD: LP=0, PFX=K'073, CSTP=BASE, CSA=NTT, RSC=73, MINL=4, MAXL=24,
CHSC=0, EA=NO;
CHSC=0, EA=NO;
//Add an office direction to area B.

ADD OFC: O=75, ON="B_area", DOT=CMPX, DOL=HIGH;
//Add a subroute.
ADD SRT: SRC=75, O=75, SRN="To B_area", RENT=URT;
//Add a virtual IP address.

ADD IPLIST: IPLISTNO=0, IP="211.169.150.1", MSK="255.255.255.128";
//Add an H.323 incoming trunk group from the H.323 GW in area B to the local GK.
ADD H323TG: TRUNKNO=75, CSC=0, SRT=75, GD=TIN, TGNM="To B_area",
TRNKTYPE=VT, IPLISTNO=0,
RCHSRC=88, HCIC=200, LCIC=180;
Related Tasks
Related Concepts
8.3.3 Configuring Data to Interwork with H.323 Network (GW -

Outer GK)
Scenarios
When interworking with a traditional H.323 network, the SoftX3000 can act either as a GK or
a GW. When the SoftX3000 acts as a GW in an H.323 network and the peer device is an outer
GK, a typical networking model is shown in Figure 8-8.

(GW - outer GK)
SoftX3000 (GW) Outer GK
H.323 trunk
H.323 trunk
A8010 Expert
IP (GW)
IP MAN in
backbone
city A
network
PSTN switch in
city B
As shown in Figure 8-8, the SoftX3000 acts as an H.323 GW logically. That is, the SoftX3000,
together with all the media gateway devices and terminal devices controlled by the SoftX3000,
is regarded as a logical H.323 gateway.
Prerequisites
Conditions

Data
You need to configure the data for interworking between the SoftX3000 and the outer GK.
Table 8-12 Data for interworking between the SoftX3000 and the outer GK

Name Value Obtain
H.323 protocol System name SoftX3000 The value is The value is

data obtained determined
through the LST during H.323
command. planning.
Configure the
H.323 protocol
data.


Name Value Obtain

minimum port minimum port obtained determined
value value: 6000 through the LST during H.323
data.
Routing data Office direction 60 The value is -

the carrier.

with the PSTN.

of the same
level, set one
office to a lower
level. For
example, if the
local office is a
toll office and
the peer office is
an end office, set
Peer office
level to
Inferior.
H.323 trunk Maximum HCIC: 200 The value is -

data caller number LCIC: 180 determined by
restriction the carrier.
and
Stop call
restriction
Trunk IP 211.169.150.2 The value must -

address be negotiated
with the GK.
RAS trunk port 1719 The value must -

with the GK.
Group direction Bi-directional The value is -

trunk determined by
the carrier.


Name Value Obtain
H323 trunk type H323 outer GK The value must The SoftX3000
trunk be negotiated acts as an H.323
with the GK. gateway and
interworks with
an outer GK.
Therefore, set
H323 trunk
type to H323
outer GK
trunk.
Gateway alias SoftX3000 The value must -

be negotiated
with the GK.
Entity name H323GK The value is -

determined by
the carrier.
Entity type Primary GK The value must -

be negotiated
with the GK.
Gatekeeper ID outGK The value must -

be negotiated
with the GK.
Toll call prefix Service attribute National toll The value is -

data determined by
the carrier.
Call prefix 0860 The value is -

determined by
the carrier.
Documents
Huawei.
Workflow

Procedure
Step 1 Configure the H.323 protocol data. For details, see Configure the H.323 protocol data.

2. Add a subroute.
subroute;
3. Add a route.
capability, TMX=Time index, R=Route number, ISUP=Signaling as prior;
NOTE
Step 3 Add an H.323 trunk group.

number, GD=Group direction, TRNKTYPE=H323 trunk type, TRNKIP=Trunk IP address,
RASTRNKPORT=RAS trunk port number, EN=Entity name, ET=Entity type,
GKID=GateKeeper ID, OTCHSRC=Outgoing trunk charging source code, HCIC=Maximum
caller number restriction, LCIC=Stop call restriction;
NOTE
If destination code charging is used for the trunk group, set Charging source code or Outgoing trunk
charging source code to the value of Caller charging source code in the ADD CHGIDX command.

NOTE
----End
Example
Task Description

l Subscribers served by office A and subscribers served by office B can make calls to each
other.
l Destination code charging is used for calls made from office A to office B.
l Destination code charging is used for the trunk from office A to office B for settlement
between carriers.
Scripts

CALLMAXPRT=10000;
//Add an office direction to office B.

ADD OFC: O=60, ON="B_office", DOT=CMPX, DOL=LOW;
//Add a subroute.
//Add a route.
SRST=SEQ, SR1=60,
//Add route analysis data for the route to office B.

ADD RTANA: RSC=86, RSSC=0, RUT=ALL, SAI=ALL, CLR=ALL, TP=ALL, TMX=0, R=60,
ISUP=H323_M,
NCAI=ALL, CST=ALL, CNPI=ALL;
//Add an H.323 trunk group.

ADD H323TG: TRUNKNO=60, CSC=0, SRT=60, GD=TINOUT, TGNM="To B_office",
TRNKTYPE=OGK,
TRNKIP="211.169.150.2", RASTRNKPORT=1719, EN="H323GK", ET=PRGK,
GKID="outGK", OTCHSRC=99, HCIC=200, LCIC=180;
//Add a call prefix.

ADD CNACLD: PFX=K'0860, CSTP=BASE, CSA=NTT, RSC=86, MINL=4, MAXL=24,
CHSC=0, EA=NO;
Related Tasks
Related Concepts

8.4 Configuring Data to Interwork with HFC Network

Scenarios
The SoftX3000 can interwork with an HFC network through the Common Open Policy Service
Protocol (COPS). COPS, which is a simple query and response protocol, is defined by the
RFC2748. COPS is used for exchange of dynamic policy rule information between a policy
decision point (PDP) and a policy enforcement point (PEP). Figure 8-9 shows a typical
networking where the SoftX3000 interworks with an HFC network. In the networking
architecture, the CMS interworks with the CMTS through COPS.
Figure 8-9 Typical networking model for the SoftX3000 to interwork with the HFC
SoftX3000
CMS
E200
COPS
NCS
CMTS
EMTA TV
HFC network
Prerequisites
Conditions
Data
You need to configure the data for interworking between the SoftX3000 and the SMTS (through
COPS) and that for interworking between the SoftX3000 and the EMTA (through NCS). Assume
that the data configuration planned is as shown in Table 8-13 and Table 8-14.

Table 8-13 Data for interworking between the SoftX3000 and the CMTS
C Parameter Name Example Value How to Obtain Description
at
e
g
or
y
D Element ID 0 The value must be -

at negotiated with the
a CMTS.
fo
r CMTS Identify cmts The value is -
in determined by the
te carrier.
r CMTS IP address 191.150.1.33 The value must be -
w negotiated with the
or CMTS.
ki
ng CMTS Port number 2126 The value must be -
be negotiated with the
tw CMTS.
ee
n MSG Module 135 The value is The value is
th Number obtained through determined
e the LST BRD during hardware
S command. data planning.
of
IFM Module Number 132 The value is The value is
tX
obtained through determined
30
the LST BRD during hardware
00
command. data planning.
an
d Local Port 3000 The value is -
th determined by the
e carrier.
C
M
T
S

Table 8-14 Data for interworking between the SoftX3000 and the EMTA
C Parameter Name Example Value How to Obtain Description

at
e
g
or
y
D Equipment ID emta.com The value must be -

at negotiated with the
a EMTA.
fo
r Gateway type MTA The value must be -
in negotiated with the
te EMTA.
r FCCU/AGCU/UACU 22 The value is The value is
w module number obtained through determined
or the LST BRD during hardware
ki command. data planning.
ng
be Protocol type MGCP The value must be -
tw negotiated with the
ee EMTA.
n
th Local IP address 191.169.150.30 The value is The value is
e obtained through determined
S the LST FECFG during hardware
of command. data planning.
tX
Support dynamic IP Supported The value must be -
30
address negotiated with the
00
EMTA.
an
d RTP Type RTP-S The value must be -
th negotiated with the
e EMTA.
E
M
T
A
Documents
Huawei.
Workflow
The procedure for configuring data to interwork with HFC network is as follows:
1. Configure the data for interworking between the SoftX3000 and the CMTS.

2. Configure routing data. Configure the data for interworking between the SoftX3000 and
the EMTA.
3. Modify the internal timer and related software parameters.
Procedure
Step 1 Configure the data for interworking between the SoftX3000 and the CMTS.
1. Set COPS configuration.
SET COPSCFG: ElEMENTID=Element ID;
2. Add a CMTS device.
ADD CMTS: CMTSI=CMTS Index, CMTSID=CMTS Identify, IP=CMTS IP address,
PORT=CMTS Port number;
3. Add a COPS link.
ADD COPSLNK: COPSLINKNO=COPSLink Index, MSGMNO=MSG Module
Number, CMTSI=CMTS Index, IFMMNO=IFM Module Number, LOCALPORT=Local
Port;
Step 2 Configure the data for interworking between the SoftX3000 and the EMTA.
UACU module number, PTYPE=Protocol type, LA=Local IP address, DYNIP=Support
dynamic IP address, ET=Encryption type, CMTSIDX=CMTS Index, RTPTYPE=RTP Type;
NOTE
The value of CMTS index must be referenced from CMTS index defined in ADD CMTS.
Step 3 Modify the internal timer and related software parameters.

1. Modify the internal timer.
MOD ITIMER: PID=PID, YWLX=timer group, SEQ=Timer sequence, NVL=New value/
second;
2. Change the setting of bit 8 of P75 to 0.
The value 0 indicates that the SoftX3000 can transparently transmit SDP.
3. Change the setting of bit 13 of P375 to 0.
The value 0 indicates that the SoftX3000 supports the RTP security encryption function.
----End
Example
Task Description
l The SoftX3000 can send and receive COPS messages through firewall E200.
l The CMS can use COPS messages to allocate GATE resources to or release GATE
resources used by HFC subscribers at any time.
l The SoftX3000 can use NCS messages to establish, connect, and release calls for HFC
subscribers.
l HFC subscribers can use the basic voice services provided by the SoftX3000.
Scripts
//Set COPS configuration.

SET COPSCFG: ElEMENTID=0;
//Add a CMTS device.

ADD CMTS: CMTSI=0, CMTSID="cmts", IP="191.150.1.33";
//Add a COPS link.

ADD COPSLNK: COPSLINKNO=0, MSGMNO=135, CMTSI=0, IFMMNO=132,
LOCALPORT=3000;
//Add a media gateway.

ADD MGW: EID="emta.com", GWTP=MTA, MGCMODULENO=22, PTYPE=MGCP,
LA="191.169.150.30",
DYNIP=S, ET=NO, CMTSIDX=0, RTPTYPE=RTPS;
//Modify the internal timer.

MOD ITIMER: PID=120, YWLX=0, SEQ=6, NVL=10;
//Modify the setting of bit 8 of P75 to 0.

//Modify the setting of bit 13 of P375 to 0.

Related Tasks
Related Concepts
For details about the relations between COPS signaling data tables, see 12.6.9 Relations
Between COPS Signaling Data Tables.
8.5 Configuring Data to Interwork with Other Softswitches

8.5.1 Configuring Data to Interwork with Other Softswitches (Through SIP Trunk)
8.5.2 Configuring Data to Interwork with Other Softswitches (Through H.323 Trunk)
8.5.3 Configuring Data to Interwork with Other Softswitches (Through Russia CAS)
8.5.1 Configuring Data to Interwork with Other Softswitches

(Through SIP Trunk)
Scenarios
As shown in Figure 8-10, the SoftX3000 interworks with another softswitch through the SIP
trunk. The interworking data is transmitted over IP.

Figure 8-10 Typical networking model for the SoftX3000 to interwork with other softswitch
(through SIP trunk)
SoftX3000 Softswitch
(Office A) (Office B )
SIP trunk IP backbone SIP trunk

MAN in city A MAN in city B
network
Subscriber access layer

AMG AMG
Prerequisites
Conditions
Data
Before making the configuration, collect the data listed in Table 8-15.
Table 8-15 Data for interworking between the SoftX3000 and other softswitches (through SIP
trunk)
Name Value Obtain
SIP trunk data Local IP address 191.169.150.30/ The value is The value is
255.255.0.0 determined by determined
the carrier. during the
hardware data
planning.
Well-known 5060 The value is -

port number of determined by
the local end the carrier.


Name Value Obtain
Peer IP address 211.169.150.33/ The value is -

255.255.0.0 determined by
the carrier.

the peer end the carrier.
Documents
Workflow
The procedure for configuring the data between the SoftX3000 and the other softswitch is as
follows:
1. SIP protocol data

2. SIP route data
3. SIP trunk data
4. Number analysis data
Procedure
Step 1 Configure the SIP protocol data.
1. Set SIP global configuration.
SET SIPCFG: UST=Use call heartbeat;

2. Configure the SIP local port and protocol dispatching ability.
NOTE
The first SIP message sent from the peer softswitch to the SoftX3000 carries the SIP well-known
port number 5060. After receiving the SIP message, the IFMI sends the message in load sharing mode
to the MSGI. Then, the IFMI of the SoftX3000 sends a SIP message that carries the local port number
5061 configured for the MSGI. The peer softswitch receives the returned SIP message and sends
number is 5061.
Step 2 Configure SIP route data.

1. Configure the data of the SIP office direction.
type, DOL=Peer office level;

NOTE
l To avoid alternate routing between offices of the same level, set one office to a higher level. For
example, if the local office is a transit office and the peer office is a toll office, set Peer office
level to Superior.
l This office direction does not contain SS7 trunk circuits. Therefore, you need not specify DPC.
l Office names must be specified as required. Do not use the default name provided by the system.
2. Configure SIP subroute data.
ADD SRT: SRC=Sub-route number, O=Office direction number, SRN=Sub-route name,
RENT=Unrent;
3. Configure SIP route data.
ADD RT: R=Route number, RN=Route name, IDTP=UNKNOWN,
NAMECFG=Configure with number, SNCM=Configure with sub-route,
SRST=Sequential selection, SR1=1st sub-route, STTP=Invalid Value, REM=False;
4. Configure SIP routing analysis data.
capability, TM=Time index mode, TMX=Time index, NCAI=Nature of callee address
indicator, CST=Customized caller type, CNPI=Called number Plan identity, R=Route
number, ISUP=Signaling as prior;
NOTE
l Set Caller category, Service attribute, Caller access, Transmission capability, and Nature
of callee address indicator to ALL, unless specified otherwise.
l The local office and the peer office use SIP for signaling interworking. Therefore, set Signaling
as prior to Must select SIP.
Step 3 Configure SIP trunk data.

1. Configure SIP trunk group data.
ADD SIPTG: TG=Trunk group number, SRT=Sub-route number, TGN=Trunk group
name, RCHS=Charging source code, OTCS=Outgoing trunk charging source code,
HCIC=Maximum call number restriction, LCIC=Stop call restriction, NOAA=False,
EA=True, UHB=Heartbeat Mode, VIDEOS=Video supported, CHBF=NO, E2833F=2833
encryption flag, E2833K=2833 encryption key, SELMODE=Distribute;
NOTE
l Destination code charging is used for both incoming and outgoing trunk groups. Therefore, do
not set Charging source code and Outgoing trunk charging source code to 255.
l Heartbeat Mode must be set correctly. If the peer softswitch cannot identify heartbeat signals,
Heartbeat Mode must be set to No heart beat. Otherwise, the SIP trunk is faulty all the time.
2. Configure SIP trunk IP pair.
ADD SIPIPPAIR: TG=Trunk group number, IMN=IFMI module number, OSU=Remote
URI 1, DH=False;
Step 4 Configure number analysis data.
number length, CHSC=Charging selection code, EA=False;
----End

Example
Task Description
l The national toll area code of office B is 0810. The encryption key of RFC2833 protocol
is shenzhen.
other.
l Destination code charging is used for trunk occupied by calls from office A to office B.
Scripts
//Configure SIP protocol data.

SET SIPCFG: UST=SessionTimer;
//Configure SIP route data.

ADD OFC: O=10, ON="B_office", DOT=NATT, DOL=HIGH;
SRST=SEQ, SR1=10, STTP=INVALID, REM=NO;
TMX=0, NCAI=ALL, CST=ALL, CNPI=ALL, R=10, ISUP=SIP_M;
//Configure SIP trunk data.

ADD SIPTG: TG=10, SRT=10, TGN="To B_office", RCHS=88, OTCS=99, HCIC=2000,
LCIC=1800, NOAA=NO, EA=YES, UHB=NO, VIDEOS=NSUPPORT, CHBF=NO,
E2833F=SUPPORT, E2833K="shenzhen", SELMODE=DIST;
ADD SIPIPPAIR: TG=10, IMN=132, OSU="221.169.150.33:5060", DH=No;
//Configure called number analysis data.

Related Tasks
Related Concepts
None.

(Through H.323 Trunk)
Scenarios
As shown in Figure 8-11, the SoftX3000 interworks with another softswitch through the H.323
trunk. The interworking data is transmitted over IP.

Figure 8-11 Typical networking model for the SoftX3000 to interwork with other softswitch
(through H.323 trunk)
SoftX3000 Softswitch
(Office A) (Office C )
H.323 trunk IP backbone H.323 trunk

MAN in city A MAN in city C
network

AMG AMG
Prerequisites
Conditions
Data
Table 8-16 Data for interworking between the SoftX3000 and other softswitches (through H.
323 trunk)
Name Value Obtain
H.323 trunk Local IP address 191.169.150.30/ The value is The value is

data 255.255.0.0 determined by determined
hardware data
planning.
CALL port 1720 The value is -

number of the determined by
local end the carrier.


Name Value Obtain

the carrier.
CALL port 1720 The value is -

peer end the carrier.
Documents
Workflow
follows:
1. H.323 protocol data
2. H.323 route data
3. H.323 trunk data
Procedure
Step 1 Configure the H.323 protocol data.
1. Configure H323 system information.
NOTE
System name is the other name of the SoftX3000 used in the H.323 network. Set System name
correctly; otherwise, the SoftX3000 cannot interwork with the Gatekeeper (GK), Gateway (GW) or
Multipoint Control Unit (MCU) in the H.323 network.
2. Add application layer data of the H.323 protocol
NOTE
Step 2 Configure H.323 route data.

1. Configure the data of the H.323 office direction.

NOTE
l To avoid alternate routing between offices of the same level, set one office to a higher level. For
example, if the local office is a transit office and the peer office is a toll office, set Peer office
level to Superior.
2. Configure H.323 subroute data.

RENT=Unrent;
3. Configure H.323 route data.

4. Configure H.323 routing analysis data.

NOTE
Step 3 Configure H.323 trunk data.

number, GD=Group direction, TGN=Trunk group name, TRNKTYPE=H323 trunk type,
TRNKIP=Trunk IP address, SELMODE=Distribute, RCHSRC=Charging source code,
OTCHSRC=Outgoing trunk charging source code, HCIC=Maximum caller number restriction,
LCIC=Stop call restriction, EA=True, E2833F=22833 encryption flag, E2833K=2833
encryption key;
NOTE
l Destination code charging is used for both incoming and outgoing trunk groups. Therefore, do not set
Charging source code and Outgoing trunk charging source code to 255.
l The SoftX3000 interworks with a softswitch that is in the same network position. Therefore, set H323
trunk type to H323 peer trunk.
Step 4 Configure called number analysis data.

----End

Example
Task Description
l The national toll area code of office Cis 0820. The encryption key of RFC2833 protocol is
0123456789abcdef.
l Subscribers served by office A and subscribers served by office C can make calls to each
other.
l Destination code charging is used for the trunk occupied by calls from office A to office
C.
Scripts
//Configure H.323 protocol data.
CALLMAXPRT=10000;
//Configure H.323 route data.

ADD OFC: O=20, ON="C_office", DOT=NATT, DOL=HIGH;
ADD SRT: SRC=20, O=20, SRN="To C_office", RENT=URT;
ADD RT: R=20, RN="To C_office", IDTP=UNKNOWN, NAMECFG=NO, SNCM=SRT,
TMX=0, NCAI=ALL, CST=ALL, CNPI=ALL, R=20, ISUP=H323_M;
//Configure H.323 trunk data.

ADD H323TG: TRUNKNO=20, CSC=0, SRT=20, GD=TINOUT, TGN="To C_office",
TRNKTYPE=TRNK, TRNKIP="211.168.150.36", SELMODE=DIST, RCHSRC=88,
OTCHSRC=99, HCIC=2000, LCIC=1800, EA=YES, E2833F=SUPPORT,
E2833K="0123456789abcdef";
//Configure number analysis data.

Related Tasks
Related Concepts
None.

(Through Russia CAS)
Scenarios
As shown in Figure 8-12, the SoftX3000 interworks with another softswitch through Russia
CAS.

The Russia CAS is called the R15 signaling. The Russia CAS is similar to the R2 signaling
defined by ITU-T and also consists of the line signaling and the register signaling. Different
combinations of the line signaling and the register signaling provide different service features,
including the ANI feature, dual-stage dialing tone, toll call ringing, operator break-in, MFS-DP
mode, and release control mode
Figure 8-12 Typical networking model for the SoftX3000 to interwork with another softswitch
(through Russia CAS)
SoftX3000 SoftX3000
(Office A) (Office B)
MAN in H.248 E1 (R15 trunk circuits) H.248 MAN in

city A city B
UMG UMG

AMG AMG
Prerequisites
Conditions
Data

Table 8-17 Data for interworking between the SoftX3000 and other softswitches (through Russia
CAS)
Name Value Obtain
Data about the Equipment ID 211.169.150.7:2 The value is The value is

outgoing office 944 determined by determined
direction of the carrier. during
office A configuring
data to
interwork with
UMG.
Gateway type Universal media The value is The value is

gateway determined by determined
the carrier. during
configuring
data to
interwork with
UMG.

determined by determined
the carrier. during
configuring
data to
interwork with
UMG.
Peer IP address 211.169.150.7 The value is The value is

the carrier. during
configuring
data to
interwork with
UMG.
Peer port 2944 The value is The value is

number determined by determined
the carrier. during
configuring
data to
interwork with
UMG.
Office direction 15 The value must -

number of office be negotiated
A with the peer
softswitch.
outgoing route 17 The value must -

A with the peer
softswitch.


Name Value Obtain
Outgoing 17 The value must -

subroute be negotiated
number of office with the peer
A softswitch.
Data about the Equipment ID 211.169.150.7:2 The value is The value is

incoming office 945 determined by determined
direction of the carrier. during
office B configuring
data to
interwork with
UMG.
Gateway type Universal media The value is The value is

gateway determined by determined
the carrier. during
configuring
data to
interwork with
UMG.

the carrier. during
configuring
data to
interwork with
UMG.
Peer IP address 211.169.150.9 The value is The value is

the carrier. during
configuring
data to
interwork with
UMG.
Peer port 2945 The value is The value is

number determined by determined
the carrier. during
configuring
data to
interwork with
UMG.
Office direction 17 The value must -

B with the peer
softswitch.


Name Value Obtain
outgoing route 15 The value must -

B with the peer
softswitch.
Outgoing 15 The value must -

subroute be negotiated
number of office with the peer
B softswitch.
Documents
Workflow
follows:
1. Media gateway data
2. Outgoing route data of office A
3. Outgoing trunk data of office A
4. Outgoing number analysis data of office A
5. Incoming trunk data of office B
Procedure
Step 1 Configure the media gateway data.
MRSCAP=Not supported, CODETYPE=Code type, ET=Not supported, SUPROOTPKG=Not
Supported;
Step 2 Configure the outgoing routing data for office A.
1. Configure the outgoing office direction data of office A.
NOTE
In Russia, when the SoftX3000 is used as an end office, a transit office, a national toll office, or an
international toll office, select the signaling standard based on the actual office level. The OCL
signaling standard is adopted when the SoftX3000 is an end office and the peer office is a toll office.
The TCL signaling standard is adopted when the SoftX3000 is a toll office and the peer office is an
end office. In actual networking, select the correct signaling type based on the status of the local
office and that of the peer office in the network.

2. Configure the outgoing subroute data for office A.

RENT=Unrent;
3. Configure the outgoing route data for office A.

SRST=Sequential selection, SR1=1st sub-route, TRIPFLAG=False, STTP=Invalid Value,
REM=False;
4. Configure the outgoing routing analysis data for office A.

Step 3 Configure the outgoing trunk data for office A.

1. Configure the outgoing CAS signaling data for office A.
ADD CASCFG: SN=CAS signaling name, SAT=Signaling type, LS=Line signal,

RS=Register signal;
2. Configure outgoing trunk data for office A.
ADD N1TG: TG=Trunk group number, TGN=Trunk group name, EID=Equipment ID,
G=Group direction, SRC=Sub-route number, SN=CAS signal name, CSM=Circuit
selection mode, ECATTR=False, TIATTR=False, ENATTR=False;
3. Configure the outgoing trunk circuit data for office A.
number, EC=End circuit number, TID=Start circuit termination ID;
Step 4 Configure the outgoing number analysis data for office A.

1. Configure the outgoing call prefix data for office A.
ADD CNACLD: LP=Local DN set, PFX=Call prefix, CSTP=Service category,

CSA=Service attribute, RSC=Route selection code, MINL=Minimum number length,
MAXL=Maximum number length, CHSC=Charging selection code, EA=False;
NOTE
The MFS register signalings are adopted in outgoing trunk configuration. Therefore, the minimum
length and maximum number length of the outgoing prefix are the same.
2. Configure the outgoing number change data for office A.
ADD DNC: DCX=Number change index, DCT=Number change type, DCL=Change

length;
3. Configure outgoing call prefix processing data for office A.
ADD PFXPRO: CSC=Call source code, LP=Local DN set, PFX=Call prefix, CCF=Called
number change flag, SENDTONE=Not send tone, DDCX=Called number change index,
ISREANA=False, TT=Record 0;
Step 5 Configure incoming trunk data for office B.

1. Configure incoming gateway data for office B.

description, MGCMODULENO=FCCU/AGCU/UACU module number, LA=Local IP
address, RA1=Remote IP address 1, RP=Remote port, MRSCAP=Not supported,
CODETYPE=Code type, ET=Not supported, SUPROOTPKG=Not Supported;
2. Configure incoming office direction data for office B.
NOTE
Configure the office direction in office B for office A. Set Office direction number to 15. Office B is a
toll, urban and rural call office. Therefore, the level of office A is lower.
3. Configure incoming subroute data for office B.
RENT=Unrent;
4. Configure incoming route data for office B.
SRST=Sequential selection, SR1=1st sub-route, TRIPFLAG=False, STTP=Invalid Value,
REM=False;
5. Configure incoming routing analysis data for office B.
6. Configure incoming CAS signaling data for office B.
ADD CASCFG: SN=CAS signaling name, SAT=Signaling type, LS=Line signal,
RS=Register signal;
7. Configure incoming trunk data for office B.
G=Group direction, SRC=Sub-route number, SN=CAS signal name, CSM=Circuit
selection mode, ECATTR=False, TIATTR=False, ENATTR=False;
NOTE
Configure an R2 outgoing trunk group in office B. Set Trunk group number to 15 and Group
direction to Incoming trunk. This indicates that office B processes only incoming calls.
8. Configure incoming trunk circuit data for office B.
----End
Example
Task Description

l The MFS register signaling is used.

other.
l Destination code charging is used for the trunk occupied by calls from office A to office
B.
Scripts
//Configure media gateway data.

ADD MGW: EID="211.169.150.7:2944", GWTP=UMGW, MGCMODULENO=22,
LA="191.169.150.30", RA1="211.169.150.7", RP=2944, MRSCAP=NS,
CODETYPE=ASN, ET=NO, SUPROOTPKG=NS;
//Configure outgoing route data for office A.

ADD OFC: O=17, ON="CAS2_OUT", DOT=CMPX, DOL=HIGH;
ADD SRT: SRC=17, O=17, SRN="CAS2_OUT", RENT=URT;
ADD RT: R=17, RN="CAS2_OUT", IDTP=UNKNOWN, NAMECFG=NO, SNCM=SRT,
SRST=SEQ, SR1=17, TRIPFLAG=NO, STTP=INVALID, REM=NO;
//Configure outgoing trunk data for office A.

ADD CASCFG: SN="OCL_CAS2_MFS", SAT=R15, LS=OCL_CAS2, RS=MFS;
ADD N1TG: TG=17, TGN="CAS2_OUT", EID="211.169.150.7:2944", G=OUT, SRC=17,
SN="OCL_CAS2_MFS", CSM=MIN, ECATTR=NO, TIATTR=NO, ENATTR=NO;
ADD N1TKC: MN=22, TG=17, SC=608, EC=639, TID="608";
//Configure outgoing number analysis data for office A.

ADD CNACLD: LP=0, PFX=K'017, CSTP=BASE, CSA=LC, RSC=17, MINL=10, MAXL=10,
CHSC=0, EA=NO;
ADD DNC: DCX=1, DCT=DEL, DCL=3;
ADD PFXPRO: CSC=0, LP=0, PFX=K'017, CCF=YES, SENDTONE=NST, DDCX=1,
ISREANA=NO, TT=REC0;
//Configure incoming trunk data for office B

ADD MGW: EID="211.169.150.7:2945", GWTP=UMGW, MGWDESC="UMG22",
MRSCAP=NS, CODETYPE=ASN, ET=NO, SUPROOTPKG=NS;
ADD OFC: O=15, ON="CAS2_IN", DOT=CC, DOL= LOW;
ADD SRT: SRC=15, O=15, SRN="CAS2_IN", RENT=URT;
ADD RT: R=15, RN="CAS2-IN", IDTP=UNKNOWN, NAMECFG=NO, SNCM=SRT, SRST=SEQ,
SR1=15, TRIPFLAG=NO, STTP=INVALID, REM=NO;
ADD CASCFG: SN="OCL_CAS2_MFSB", SAT=R15, LS=OCL_CAS2, RS=MFS;
ADD N1TG: TG=15, TGN="CAS2_IN", EID="192.168.15.100:2946", G=IN, SRC=15,
SN="OCL_CAS2_MFS", CSM=MIN, ECATTR=NO, TIATTR=NO, ENATTR=NO;
Related Tasks
Commissioning the Interworking with Other Networks (R2)

Related Concepts
None.
8.6 Configuring Data to Interwork with IP SMS GW

(Through SIP)
Scenarios
As shown in Figure 8-13, the SoftX3000 interworks with the IP short message service gateway
(SMS GW) by using the SIP signaling as the control signaling.

Figure 8-13 Typical networking model for the SoftX3000 to interwork with the IP SMS GW
(through SIP)
SMSC
SMS GW
SIP
SoftX3000
UMG8900 UMG8900
RAC6610 RAC6610
BTS3606 BTS3606
Mobile Mobile Mobile Mobile

subscriber A subscriber B subscriber C subscriber D

Prerequisites
Conditions

Data
Table 8-18 Data for interworking between the SoftX3000 and the IP SMS GW (through SIP)

Name Value Obtain
SIP trunk data Local IP address 191.169.150.30/ The value is The value is
255.255.0.0 determined by determined
hardware data
planning.

the SIP protocol the carrier.
at the local end

the carrier.

the SIP protocol the carrier.
at the peer end
Documents
Workflow
The procedure for configuring the data between the SoftX3000 and the IP SMS GW is as follows:
2. Local office data
3. SIP route data
4. SIP trunk data

Procedure
Step 1 Configure SIP protocol data.
1. Set SIP global configuration.
2. Configure the SIP local port and protocol dispatching ability.
NOTE
The first SIP message sent from the peer device to the local SoftX3000 carries the SIP well-known
5061 configured for the MSGI. The peer device receives the returned SIP message and sends
number is 5061.
Step 2 Configure local office data.

SET OFI: OFN=Local office name, TMZ=Time zone index, SMSNUM=Short message center
number, SGCR=False;
Step 3 Configure SIP route data.
1. Configure SIP office direction data.
NOTE
l Office names must be specified as required. Do not use the default name provided by the system.
2. Configure SIP subroute data.
RENT=Unrent;
3. Configure SIP route data.
4. Configure SIP routing analysis data.
NOTE

Step 4 Configure SIP trunk data.

1. Configure SIP trunk group data.

HCIC=Maximum call number restriction, LCIC=Stop call restriction, ST=Server type,
NOAA=False, EA=False;
2. Configure SIP trunk IP pair.

URI 1, DH=False;

----End
Example
Task Description
l Normal SIP signaling channels are established between the SoftX3000 and the IP SMS
GW.
l The number of SMC is 13107550511.
Scripts
//Configure SIP protocol data.

//Configure local office data.

SET OFI: OFN="SMSC", TMZ=21, SMSNUM=K'13107550511, SGCR=NO;
//Configure SIP route data.

ADD OFC: O=82, ON="SMS Center", DOT=CMPX, DOL=SAME;
ADD SRT: SRC=82, O=82, SRN="To SMS Center", RENT=URT;
ADD RT: R=82, RN="To SMS Center", IDTP=UNKNOWN, NAMECFG=NO, SNCM=SRT,
//Configure SIP trunk data.

ADD SIPTG: TG=82, SRT=82, TGN="To SMS Center", RCHS=88, OTCS=99,
HCIC=65535, LCIC=65535, ST=NGNN, NOAA=NO, EA=NO;
//Configure number analysis data.

ADD CNACLD: LP=0, PFX=K'13107550511, CSTP=BASE, CSA=LC, RSC=82, MINL=11,

Related Tasks
Related Concepts
None.

Initial Configuration 9 Configuring Data to Interwork with Other Service Devices
9 Configuring Data to Interwork with Other

Service Devices
About This Chapter
9.1 Configuring Data to Interwork with PBX

9.2 Configuring Data to Interwork with IP U-Path
9.3 Configuring Data to Interwork with ISDN U-Path
9.4 Configuring Data to Interwork with the AS (Through SIP)
9.5 Configuring Data to Interwork with the SHLR

9 Configuring Data to Interwork with Other Service Devices Initial Configuration
9.1 Configuring Data to Interwork with PBX

9.1.1 Configuring Data to Interwork with the PBX (Through the PRA Trunk)
9.1.2 Configuring Data to Interwork with the PBX (Through the R2 Trunk)
9.1.3 Configuring Data to Interwork with PBX (Through the AT0 Trunk)
9.1.4 Configuring Data to Interwork with the PBX (Through the Loop Trunk)
9.1.5 Configuring Data to Interwork with the PBX (Through the SIP Trunk)
9.1.1 Configuring Data to Interwork with the PBX (Through the

PRA Trunk)
Scenarios
When the SoftX3000 interworks with the Private Branch Exchange (PBX) or Network Access
Server (NAS) in a PSTN, Digital Subscriber Signaling No. 1 (DSS1) can be used as the inter-
office signaling. For the PBX, Primary Rate Adaptation (PRA) links carry DSS1 signaling. For
the SoftX3000, IUA links carry DSS1 signaling. Figure 9-1 shows a typical networking model.
Figure 9-1 Typical networking model for the SoftX3000 to interwork with the PBX (through
PRA)
SoftX3000
IUA
links UMG8900 / TMG8010 PBX
IP
MAN
PRA links/
PRA trunk circuits

AMG
As shown in Figure 9-1, the SoftX3000 provides IUA links for connection with the UMG8900.
The SoftX3000 interworks with the PBX using DSS1 through the UMG8900 (with embedded
SG functions). For voice channels, the SoftX3000 interworks with the PBX by controlling the
UMG8900. To achieve interworking between the SoftX3000 and the PBX, configure the
following interworking data on the SoftX3000 side:

l Data for interworking between the SoftX3000 and the UMG8900 (with embedded SG
functions).
l Data for interworking between the SoftX3000 and the PBX.
Prerequisites
Conditions

Data
l Table 9-1 shows the data to be planned for interworking between the SoftX3000 and the
UMG8900.

Name Value Obtain
H.248 protocol Protocol used H.248 The value must The value is
for be negotiated determined
interworking with the during
between the UMG8900. configuring
SoftX3000 and data to
the UMG8900 interwork
with UMG.
H.248 code ASN.1 (binary The value must The value is

type mode) be negotiated determined
with the during
UMG8900. configuring
data to
interwork
with UMG.
Data on the IP address of 191.169.150.3 The value must The value is

SoftX3000 the IFMI of the 0/255.255.0.0 be negotiated determined
side SoftX3000 with the during
data to
interwork
with UMG.
Local UDP 2944 The value must The value is

port number of be negotiated determined
H.248 on the with the during
SoftX3000 UMG8900. configuring
side data to
interwork
with UMG.


Name Value Obtain
E1 number of 6-7 The value must The value is

the PRA trunk be negotiated determined
group on the with the during
data to
interwork
with UMG.
Local SCTP IUA link 0: The value must The value is

port number of 9900 be negotiated determined
IUA links on IUA link 1: with the during
the SoftX3000 9901 UMG8900. configuring
side (client) data to
interwork
with UMG.
Data on the H.248 IP 211.169.150.7/ The value must The value is

UMG8900 side address of the 255.255.0.0 be negotiated determined
UMG8900 with the during
data to
interwork
with UMG.
SIGTRAN IP 211.169.150.8/ The value must The value is

address of the 255.255.0.0 be negotiated determined
data to
interwork
with UMG.

UMG8900 side UMG8900. configuring
data to
interwork
with UMG.
Speech codecs G.711A, G. The value must The value is

supported by 711μ, G.723.1, be negotiated determined
the UMG8900 G.729 with the during
data to
interwork
with UMG.


Name Value Obtain
Whether the Yes The value must The value is

UMG8900 be negotiated determined
supports with the during
hairpin UMG8900. configuring
connection data to
interwork
with UMG.

supports the with the during
EC function UMG8900. configuring
data to
interwork
with UMG.

supports the T. with the during
38 protocol UMG8900. configuring
data to
interwork
with UMG.
E1 numbering Starting from 0 The value must The value is

plan on the be negotiated determined
data to
interwork
with UMG.
Numbering Starting from 0 The value must The value is

plan of be negotiated determined
termination ID with the during
(E1 timeslot) UMG8900. configuring
of the data to
UMG8900 interwork
with UMG.
E1 IDs 0-1 The value must The value is

corresponding be negotiated determined
to the PRA with the during
trunk group on UMG8900. configuring
the UMG8900 data to
side interwork
with UMG.


Name Value Obtain
Local SCTP 9900 The value must The value is

IUA links on with the during
the UMG8900 UMG8900. configuring
side (server) data to
interwork
with UMG.
IUA data Traffic mode of Load-sharing The value must -

the IUA linkset mode be negotiated
with the
UMG8900.
PRA data Interface ID 12345 The value must -

(integer) of be negotiated
PRA link 0 with the
UMG8900.
Interface ID 54321 The value must -

(integer) of be negotiated
PRA link 1 with the
UMG8900.
PBX.
Table 9-2 Data for interworking between the SoftX3000 and the PBX
Name Value Obtain
DSS1 DSS1 Network side The value is -

signaling data signaling type determined
on the based on actual
SoftX3000 situation.
side (the
UMG8900 side
must be
consistent with
the SoftX3000
side)
PRA data DSS1 Subscriber side The value must -

signaling type be negotiated
on the PBX with the PBX.
side


Name Value Obtain
PRA link Link 0: 208 The value must -

circuit number Link 1: 240 be negotiated
(on the with the PBX.
SoftX3000
side)
Termination Link 0: 16 The value must -

ID of the PRA Link 1: 48 be negotiated
link circuit with the PBX.
number (on the
UMG8900
side)
Selection mode Cyclic The value must -

for PRA trunk selection be negotiated
circuits with the PBX.
Prefix for PBX 2225 The value must -

subscribers be negotiated
with the PBX.
Documents
Workflow
The procedure for configuring the data between the SoftX3000 and the PBX is as follows:
1. MGW data
2. IUA link data
3. PRA link data
4. PRA route data
5. PRA trunk data
Procedure
Step 1 Configure MGW data.
MGCMODULENO=FCCU/AGCU/UACU module number, LA=Local IP address,
RA1=Remote IP address 1, RP=Remote port, LISTOFCODEC=Codec list, MRSCAP=Not
supported, HAIRPIN=Hairpin connection, CODETYPE=Code type, ET=False,
SUPROOTPKG=Not supported;

NOTE
ID must be IP address:port number, and Gateway Type must be set to UMGW.
211.169.150.7.
l The H.248 protocol of the UMG8900 adopts the binary format. Therefore, Code type must be set to
ASN.1.
l The UMG8900 in the given example supports hairpin connection. Therefore, Hairpin connection must
be set to Supported. If the UMG8900 does not support hairpin connection, set Hairpin connection
to Not supported.
Step 2 Configure IUA link data.

1. Configure signaling gateway data.
NOTE
In the given example, the embedded SG in the UMG8900 is used to process the IUA protocol.
Therefore, SG type must be set to Embedded SG, and Equipment ID must be set to the equipment
ID of the UMG8900.
2. Configure IUA linkset data.
ADD IUALKS: LSX=Linkset index, LSNAME=Linkset name, DT=Device type,
NOTE

the IUA links of the linkset works normally.
3. Configure IAU link data.
LOCPORT=Local port number, LOCIP1=Local IP address1, PEERPORT=Peer port
number, PEERIP1=Peer IP address1;
NOTE
l You must set Peer IP address 1 to the IP address of the UMG8900 used for SIGTRAN.
l If the system is configured with two BSGI modules, allocate the two IUA links to each of them.
This guarantees reliability of the IUA links.
Step 3 Configure PRA link data.

ADD PRALNK: PLN=Link number, SCN=Signal circuit number, MN=FCCU module number,
LKS=IUA linkset index, BinIfId=Integer interface ID, NCF=Caller number check mode;

NOTE
l The signal circuit number of the PRA link is a logical circuit number assigned inside the SoftX3000.
The specific value is calculated based on Start circuit number defined by running ADD PRATKC.
A PRA link can occupy only timeslot 16 of an E1. Therefore, the mapping calculation formula is: signal
circuit number of a PRA link = start circuit number of the mapping PRA trunk group + 16.
l If the PRA link is based on IUA, you need to specify its interface ID. The interface IDs (integer) of
different PRA links cannot be the same.
l Consider the SoftX3000 and the UMG8900 as a unit. Set the same signaling type (DSS1 network side
or DSS1 subscriber side) for the SoftX3000 and the UMG8900.
l Calls made by PBX subscribers through PRA incoming trunks are charged on the subscriber number
2250000. Therefore, set Caller number check mode to Use default number.
Step 4 Configure PRA route data.

1. Configure PRA office direction data.
NOTE
l To avoid alternate routing between offices of the same level, set Peer office level to Inferior
when the peer office is a PBX.
l This office direction does not contain SS7 trunk circuits. Therefore, you need not set DPC.
2. Configure PRA subroute data.
RENT=Unrent;
3. Configure PRA route data.
NAMECFG=Configure with name, SNCM=Configure with sub-route, SRST=Sequential
selection, SR1=1st sub-route, STTP=Invalid Value, REM=False;
4. Configure PRA routing analysis data.
capability, TM=TMM, TMX=Time index, NCAI=Nature of callee address indicator,
CST=Customized caller type, CNPI=Called number Plan identity, R=Route number,
ISUP=Signaling as prior;
NOTE
Set Caller category, Service attribute, Caller access, Transmission capability, and Nature of
callee address indicator to ALL, unless specified otherwise.
Step 5 Configure PRA trunk data.

1. Configure PRA trunk group data.
ADD PRATG: TG=Trunk group number, TGN=Trunk group name, MGW=Equipment
ID, SRC=Sub-route number, LINK=Signaling link number, CDEF=Default caller number,
IPM=Caller number provision mode, RCHS=Charging source code;
NOTE
By default, a PRA signaling link controls only one PCM system. Therefore, if there are N E1 circuits
enabled between the SoftX3000 and the PBX, configure PRA trunk groups.
2. Configure PRA trunk circuit data.

ADD PRATKC: MN=FCCU module number, TG=Trunk group number, SC=Start circuit,
EC=End circuit, TID=Start circuit termination ID;
NOTE
l Start circuit number and End circuit number are the universal logical numbers of E1 trunk
circuits, such as SS7, PRA, R2, and V5, in an FCCU module. The physical numbers of the E1
trunk circuits on the UMG8900 side are defined by Start circuit termination ID.
l Start circuit termination ID is a parameter used for interworking with a trunk MGW. Start
circuit termination ID identifies the start circuit timeslot of a specified batch of trunk circuits
in the resident trunk MGW. For example, if Start circuit termination ID is set to 32, it indicates
that the trunk circuits belong to E1 1 on the UMG8900 side.
l The absolute value of the difference between the start circuit number and the start circuit
termination ID must be a multiple of 32, such as 0, 32, 64, and 96.
3. Configure the application mode of the PRA trunk.
l Configure the PRA trunk to be in trunk mode.
NOTE
l When "Trunk mode" is used by the PRA trunk between the SoftX3000 and the PBX, you
only need to set the call attribute of the corresponding call prefix to outgoing call (for example,
local call). Do not add PRA subscribers by running ADD PRA.
l "Trunk mode" means that when there is a call on the PRA trunk group, the SoftX3000
manages the authority control, charging analysis, and call barring analysis of the call
according to the call attribute and charging attribute of the PRA trunk group. In this case, the
system generates only trunk bills for an incoming trunk call. No subscriber bills are generated.
l Configure the PRA trunk to be in subscriber mode.
NOTE
l When "Subscriber mode" is used by the PRA trunk between the SoftX3000 and the PBX,
you only need to set the call attribute of the corresponding call prefix to intra-office call. You
must also add a PRA subscriber by running ADD PRA.
l "Subscriber mode" means that when there is a call on the PRA trunk group, the SoftX3000
manages the authority control, charging analysis and call barring analysis of the call
according to the call attribute and charging attribute of the PRA subscriber. In this case, the
system generates only subscriber bills for an incoming trunk call. No trunk bills are generated.
4. Configure ISDN data.
ADD ISDNDAT: ISDN=Index, BCHN=Maximum B channel;
NOTE
Maximum B channel must be set to 30 for PRA subscribers.

5. Add PRA subscribers in one batch.
ADB PRA: LP=Local DN set, SD=Start subscriber number, ED=End subscriber number,
ISDN=ISDN index, LOCM=Trunk group, TRUNKGP=PRA trunk group, CSC=Call
source code, RCHS=Charging source code, NS=Supplementary service, CUGU=False,
CTX=entrex attribute, EHC=Hidden;

NOTE
l The system allows you to add a PRA subscriber only when the call source code to which the PRA
subscriber belongs is the same as the call source code to which the PRA trunk group belongs.
l Set the PRA trunk group to bidirectional to enable the PRA subscriber to call in and call out
through the PRA trunk group.
l When multiple E1 circuits are enabled between the SoftX3000 and the PBX, distribute PRA
subscribers evenly to PRA trunk groups mapping the E1s. This helps to implement the load
sharing of traffic between the E1s and that of signaling between PRA links.
----End
Example
Task Description
l Two E1 circuits are set up between the SoftX3000 and the PBX through the UMG8900.
l Two IUA links are established between the SoftX3000 and the UMG8900, The DSS1
signaling are transmitted over these two links in load-sharing mode.
l Local subscribers and subscribers served by the PBX can make calls to each other.
l Trunk mode is used by the PRA trunk.
Scripts
//Configure MGW data.
RP=2944, LISTOFCODEC=PCMA-1&PCMU-1&G7231-1&G729-1&T38-1, MRSCAP=NS,
HAIRPIN=S, CODETYPE=ASN, ET=NO, SUPROOTPKG=NS;
//Configure IUA link data.

ADD IUALKS: LSX=2, LSNAME="IUA LinkSet 2", DT=PRA, SGID=3;
PEERPORT=9900, PEERIP1="211.169.150.8";
PEERPORT=9901, PEERIP1="211.169.150.8";
//Configure PRA link data.

ADD PRALNK: PLN=0, SCN=208, MN=22, LKS=2, BinIfId=12345, NCF=
Default_CLI;
ADD PRALNK: PLN=1, SCN=240, MN=22, LKS=2, BinIfId=54321, NCF= Default_CLI;
//Configure PRA route data.

ADD OFC: O=91, ON="H_office", DOT=PBX, DOL=LOW;
ADD SRT: SRC=91, O=91, SRN="To H_office", RENT=URT;
ADD RT: R=91, RN="To H_office", IDTP=UNKNOWN, NAMECFG=NO, SNCM=SRT,
//Configure PRA trunk data

ADD PRATG: TG=91, TGN="To H_office", MGW="211.169.150.7:2944", SRC=91,
LINK=0, CDEF=K'8888888, IPM=TRK, RCHS=88;

ADD PRATG: TG=92, TGN="To H_office", MGW="211.169.150.7:2944", SRC=91,

LINK=1, CDEF=K'8888888, IPM=TRK, RCHS=88;
ADD PRATKC: MN=22, TG=91, SC=192, EC=223, TID="0";
ADD CNACLD: LP=0, PFX=K'2225, CSTP=BASE, CSA=LC, RSC=91, MAXL=7, CHSC=0,
EA=NO;
ADD ISDNDAT: ISDN=2, BCHN=30;
CSC=0, RCHS=22, NS=CLIP-1, CUGU=NO, CTX=FALSE, EHC=FALSE;
CSC=0, RCHS=22, NS=CLIP-1, CUGU=NO, CTX=FALSE, EHC=FALSE;
Related Tasks
Commissioning the Interworking with Other Networks (PRA)
Related Concepts
For details about the relation between PRA trunk circuit tables, see 12.8.3 Relations Between
PRA Trunk Circuit Data Tables.
9.1.2 Configuring Data to Interwork with the PBX (Through the R2

Trunk)
Scenarios
Figure 9-2 shows the typical networking model where the SoftX3000 interworks with the PBX
using R2 through the UMG8900 (or TMG8010) of Huawei.
the R2 trunk)
SoftX3000
UMG8900 / TMG8010 PBX
IP
MAN
R2 trunk circuits

AMG

The R2 signaling is the channel associated signaling (CAS). The UMG8900 shown in Figure
9-2 supports the R2 signaling conversion function, that is, the SoftX3000 interworks with the
PBX using R2 through the UMG8900. For voice channels, the SoftX3000 interworks with the
PBX by controlling the UMG8900. To achieve interworking between the SoftX3000 and the
PBX, configure the following interworking data on the SoftX3000 side:
l Data for interworking between the SoftX3000 and the UMG8900.
l Data for interworking between the SoftX3000 and the PBX.
Prerequisites
Conditions
Data
UMG8900.
Name Value Obtain
with UMG.

with the during
data to
interwork
with UMG.

SoftX3000 with the during
data to
interwork
with UMG.


Name Value Obtain

side data to
interwork
with UMG.
E1 number of 8-9 The value must The value is

the R2 trunk be negotiated determined
group on the with the during
data to
interwork
with UMG.

UMG8900 address of the 255.255.0.0 be negotiated determined
data to
interwork
with UMG.

UMG8900 UMG8900. configuring
data to
interwork
with UMG.

data to
interwork
with UMG.

connection data to
interwork
with UMG.


Name Value Obtain

supports the with the during
EC function UMG8900. configuring
data to
interwork
with UMG.

data to
interwork
with UMG.
E1 numbering Starting from 0 The value must The value is

plan on the be negotiated determined
UMG8900 side with the during
data to
interwork
with UMG.

termination ID with the during
(E1 timeslot) UMG8900. configuring
of the data to
UMG8900 interwork
with UMG.
E1 IDs 0-1 The value must The value is

corresponding be negotiated determined
to the R2 trunk with the during
group on the UMG8900. configuring
UMG8900 side data to
interwork
with UMG.
PBX.


Name Value Obtain
CAS data Channel R2 The value is -

associated planned as
signaling required.
R2 trunk data Selection mode Cyclic The value must -

for R2 trunk selection be negotiated
circuits with the PBX.

with the PBX.
Documents
Workflow
1. MGW data
2. R2 route data
3. R2 trunk data
Procedure

RA1=Remote IP address 1, RP=Remote port, LISTOFCODEC=Codec list, MRSCAP=NS,
HAIRPIN=Hairpin connection, CODETYPE=Code type, ET=Not supported,
NOTE
ASN.1.
to Not supported.
Step 2 Configure the routing data.

1. Configure the R2 office direction data.

NOTE
2. Configure the R2 sub-route data.

RENT=Unrent;
3. Configure the R2 route data.

NAMECFG=Configure with name, SNCM=Configure with sub-route, SRST=Sequential
selection, SR1=1st sub-route, STTP=Invalid Value, REM=False;
4. Configure the R2 routing analysis data.

Step 3 Configure the R2 trunk data.

1. Configure the CAS data for R2.
ADD CASCFG: SN=CAS signaling name, SAT=Signaling type;

2. Configure the R2 trunk data.
G=Group direction, SRC=Sub-route number, SN=CAS signal name, OTCS=Outgoing
trunk charging source code, ECATTR=NO, TIATTR=NO, ENATTR=NO;
G=Group direction, SRC=Sub-route number, SN=CAS signal name, RCHS=Charging
source code, ECATTR=NO, TIATTR=NO, ENATTR=NO;
NOTE
l Destination code charging is used in the local office for outgoing and incoming calls from PBX
subscribers. For the outgoing trunk group, set Outgoing trunk charging source code to 99
instead of 65535. For the incoming trunk group, set Charging source code to 88 instead of 65535.
l If the local office is required to charge each PBX subscriber separately, set CAMA of the
incoming trunk group to YES. Perform caller number discrimination on the incoming trunk group
at the same time to prevent the PBX from sending incorrect caller numbers.
office side, define Charging source code and Outgoing trunk charging source code for both
3. Configure the R2 trunk circuit data.

NOTE
l Start circuit number and End circuit number are the universal logical numbers of E1 trunk
circuits, such as SS7, PRA, R2, and V5 in an FCCU module. The physical numbers of the E1
trunk circuits on the UMG8900 side are defined by Start circuit termination ID.
l Start circuit termination ID is a parameter used for interworking with a trunk MGW. Start
circuit termination ID identifies the start circuit timeslot of a specified batch of trunk circuits
in the resident trunk MGW.
l The absolute value of the difference between the start circuit number and the start circuit
termination ID must be a multiple of 32, such as 0, 32, 64, and 96.

NOTE
l For the outgoing call prefix, Route selection code cannot be set to 65535.
l Destination code charging is used for the outgoing call prefix. Therefore, Charging selection code
cannot be set to 65535.
----End
Example
Task Description
l Two E1 circuits are set up between the SoftX3000 and the PBX through the UMG8900.
l Subscribers in the local office and in the PBX can call each other.
l Destination code charging is adopted in the local office for incoming calls from the PBX
subscribers.
Scripts
//Configure the MGW data.
//Configure the R2 route data.

ADD OFC: O=93, ON="K_office", DOT=PBX, DOL=LOW;
ADD SRT: SRC=93, O=93, SRN="To K_office", RENT=URT;
ADD RT: R=93, RN="To K_office", IDTP=UNKNOWN, NAMECFG=NO, SNCM=SRT,
//Configure the R2 trunk data.

ADD CASCFG: SN="R2", SAT=R2;
ADD N1TG: TG=93, TGN="To K_office", EID="211.169.150.7:2944", G=OUT,
SRC=93, SN="R2", OTCS=99, ECATTR=NO, TIATTR=NO, ENATTR=NO;
ADD N1TG: TG=94, TGN="To K_office", EID="211.169.150.7:2944", G=IN,
SRC=93, SN="R2", RCHS=88, ECATTR=NO, TIATTR=NO, ENATTR=NO;


//Configure the number analysis data.

CHSC=0, EA=NO;
Related Tasks
Commissioning the Interworking with Other Networks (R2)
Related Concepts
For details about the relation between R2 trunk circuit tables, see 12.8.2 Relations Between R2
Trunk Circuit Data Tables.
9.1.3 Configuring Data to Interwork with PBX (Through the AT0

Trunk)
Scenarios
The AT0 trunk (a type of circuit trunk) is an analog subscriber line used to achieve the Direct
Dial In (DDI) function of the PBX. When AT0 trunks are used in networking, the SoftX3000
interworks with the PBX through common analog subscriber lines. Figure 9-3 shows a typical
networking model.
the AT0 trunk)
SoftX3000
UMG8900 (Inserted PBX (Inserted with analog

with CDI trunk boards) subscriber boards)
IP
MAN Analog subscriber line
(ATO trunk)

AMG
As shown in Figure 9-3, the PBX occupies number resources of the public network. AT0 trunks
support only uni-directional calls, that is, calls from the public network (SoftX3000) to the PBX.

Prerequisites
Conditions
Data
UMG8900.
Name Value Obtain
with UMG.

with the during
data to
interwork
with UMG.

side SoftX3000 with the during
data to
interwork
with UMG.

side data to
interwork
with UMG.


Name Value Obtain

UMG8900 side address of the 255.255.0.0 be negotiated determined
data to
interwork
with UMG.

UMG8900 side UMG8900. configuring
data to
interwork
with UMG.

data to
interwork
with UMG.

connection data to
interwork
with UMG.

data to
interwork
with UMG.
Termination 128-143 The value must The value is

ID range for the be negotiated determined
CDI of the with the during
UMG8900 UMG8900. configuring
data to
interwork
with UMG.
PBX.


Name Value Obtain
AT0 trunk data Selection mode Minimum line The value is -

planning for AT0 trunk selection mode planned as
circuits required.

with the PBX.
Documents
Workflow
1. MGW data
2. AT0 route data
3. AT0 trunk data
Procedure

RA1=Remote IP address 1, RP=Remote port, LISTOFCODEC=Codec list, MRSCAP=NS,
HAIRPIN=Hairpin connection, CODETYPE=Code type, ET=Not supported,
NOTE
ASN.1
to Not supported.
Step 2 Configure the AT0 route data.

1. Configure the AT0 office direction.

NOTE
2. Configure the AT0 sub-route data.
RENT=Unrent;
3. Configure the AT0 route data.
4. Configure the AT0 routing analysis data.
Step 3 Configure the AT0 trunk data.
1. Configure the AT0 trunk data.
ADD AT0TG: TG=Trunk group number, TGN=Trunk group name, G=Group direction,
EID=Equipment ID, SRN=Sub-route number, CSM=Circuit selection mode,
ENATTR=False;
NOTE
l Set Circuit selection mode to Minimum for the AT0 trunk group. If you select other modes,
the call connection fails.
l You must set DOD2 to False when the AT0 trunk group is used for DDI networking of the PBX.
l Set the duration of the timers to the default values. Do not modify them unless it is required.
2. Configure the AT0 trunk circuit data.
ADD AT0TKC: MN=FCCU module number, TG=Trunk group number, SC=Start circuit
NOTE
Start circuit termination ID specified is the termination ID of port 0 of the CDI on the UMG8900
side.

NOTE
l 3650 is an outgoing call prefix. Therefore, Route selection code cannot be set to 65535.
l Destination code charging is used for the prefix 3650. Therefore, Charging selection code cannot be
set to 65535.
----End

Example
Task Description
l The UMG8900 provides 16 AT0 trunks between the SoftX3000 and the PBX.
l Subscribers in the SoftX3000 office can call PBX subscribers directly (dual-stage dialing
is not required).
Scripts

//Configure the AT0 route data.

ADD OFC: O=95, ON="DDI_office", DOT=PBX, DOL=LOW;
ADD SRT: SRC=95, O=95, SRN="To DDI_office", RENT=URT;
ADD RT: R=95, RN="To DDI_office", IDTP=UNKNOWN, NAMECFG=NO, SNCM=SRT,
//Configure the AT0 trunk data.

ADD AT0TG: TG=95, TGN="To DDI_office", G=OUT, EID="211.169.150.7:2944",
SRN=95, CSM=MIN, ENATTR=NO;
ADD AT0TKC: MN=22, TG=95, SC=320, EC=335, TID="128";

CHSC=0, EA=NO;
Related Tasks
None.
Related Concepts
For details about the relation between AT0 trunk circuit tables, see 12.8.4 Relations Between
AT0 Trunk Circuit Data Tables.
9.1.4 Configuring Data to Interwork with the PBX (Through the

Loop Trunk)
Scenarios
The loop trunks are actually analog subscriber lines provided by the IAD or AMG, which is
controlled by the SoftX3000. When the SoftX3000 interworks with the PBX through the loop
trunk, the typical networking model is shown as Figure 9-4.

the loop trunk)
SoftX3000
IAD (Inserted with analog PBX (Inserted with

subscriber boards) loop trunk boards)
IP
MAN
Analog subscriber
line

AMG
Prerequisites
Conditions
Data
IAD.
Name Value Obtain
MGCP Protocol used MGCP The value must The value is

protocol for be negotiated determined
interworking with the IAD. during
between the configuring
the IAD interwork
with IAD.


Name Value Obtain
MGCP code ABNF (text The value must The value is

type format) be negotiated determined
with the IAD. during
configuring
data to
interwork
with IAD.

side SoftX3000 with the IAD. during
configuring
data to
interwork
with IAD.

MGCP on the with the IAD. during
SoftX3000 configuring
side data to
interwork
with IAD.
Data on the Domain name shenzhen- The value must The value is
IAD side of the IAD iad104-01.com be negotiated determined
configuring
data to
interwork
with IAD.
IP address of 211.169.150.1/ The value must The value is

the IAD 255.255.0.0 be negotiated determined
configuring
data to
interwork
with IAD.

MGCP on the with the IAD. during
IAD side configuring
data to
interwork
with IAD.


Name Value Obtain
Interface name aaln The value must The value is

of the IAD be negotiated determined
configuring
data to
interwork
with IAD.

termination ID with the IAD. during
(subscriber configuring
port) of the data to
IAD interwork
with IAD.

the IAD G.729 with the IAD. during
configuring
data to
interwork
with IAD.
Whether the No The value must The value is

IAD supports be negotiated determined
hairpin with the IAD. during
connection configuring
data to
interwork
with IAD.

the EC with the IAD. during
function configuring
data to
interwork
with IAD.

the detection of with the IAD. during
fax and modem configuring
signal tones data to
interwork
with IAD.


Name Value Obtain

the T.38 with the IAD. during
protocol configuring
data to
interwork
with IAD.
Phone numbers 6540100-6540 The value must The value is

assigned to 115 be negotiated determined
subscriber with the IAD. during
lines of the configuring
IAD data to
interwork
with IAD.
Termination 0-15 The value must The value is

IDs assigned to be negotiated determined
subscriber with the IAD. during
lines of the configuring
IAD data to
interwork
with IAD.
PBX.
Name Value Obtain
PBX service PBX pilot 6540101 The value must -

data number be negotiated
with the PBX.
Phone numbers 6540100-6540 The value must -

assigned to the 115 be negotiated
PBX with the PBX.
subscriber
group
Documents

Workflow
1. MGW data
2. Subscriber data
3. PBX service data
Procedure

IP address, RA1=Remote IP address 1, RP=Remote port, LISTOFCODEC=Codec list,
UCATT=Special attributes, ET=Not supported, SUPROOTPKG=Not supported;
NOTE
When the IAD adopts MGCP, the format of Equipment ID is domain name, and you are advised to set
the domain name in the office name-MGW type-number format, for example, shenzhen-
iad104-01.com.
DID=ESL, MN=FCCU module number, EID=Equipment ID, STID=Start MG termination ID,
CODEC=Codec prefer, RCHS=Charging source code, CSC=Call source code, UTP=Ordinary,
CNTRX=False, PBX=False, CHG=False, ENH=False;
Step 3 Configure the PBX service data.

1. Configure the PBX subscriber group data.
ADD PBX: GDN=PBX pilot number, LP=Local DN set, PNC=No Change;
NOTE
After you run this command, the PBX pilot number 6540101 has been defined as a PBX subscriber
occupying number resources.
2. Modify the voice subscriber data.
MOD VSBR: D=Subscriber number, LP=Local DN set, CNTRX=False, PBX=PBX

attribute, AUT=Additional status, GDN=PBX pilot number, CHG=False, ENH=False;
NOTE
6540101 is a PBX pilot number that occupies number resources. MOD VSBR can be used to define
only PBX non-pilot numbers that occupy number resources. Therefore, you cannot modify the
subscriber attributes of 6540101 by running MOD VSBR.
3. Modify the voice subscriber data in batches.
MOB VSBR: SD=Start subscriber number, ED=End subscriber number, LP=Local DN

set, CNTRX=False, PBX=PBX attribute, AUT=Additional status, GDN=PBX pilot
number, CHG=False, ENH=False;


MINL=Minimum number length, MAXL=Maximum number length, CHSC=Charging
selection code, EA=False, SDESCRIPTION=Description;
----End
Example
Task Description
l An IAD provides 16 loop trunks between SoftX3000 and the PBX.
l Subscribers in the SoftX3000 office can call PBX subscribers through a pilot number.
Scripts
ADD MGW: EID="shenzhen-iad104-01.com", GWTP=IAD, MGWDESC="shenzhen-
iad104-01", MGCMODULENO=22, PTYPE=MGCP, LA="191.169.150.30",
RA1="211.169.150.1", RP=2427,
LISTOFCODEC=PCMA-1&PCMU-1&G7231-1&G729-1&T38-1, UCATT=NOFX-0&NOM-0,
ET=NO, SUPROOTPKG=NS;
//Configure the subscriber data.

ADB VSBR: SD=K'6540100, ED=K'6540115, LP=0, DID=ESL, MN=22, EID="shenzhen-
iad104-01.com", STID="0", CODEC=PCMA, RCHS=65, CSC=0, UTP=NRM, CNTRX=NO,
PBX=NO, CHG=NO, ENH=NO;
//Configure the PBX service data.

ADD PBX: GDN=K'6540101, LP=0, PNC=NOCHG;
MOD VSBR: D=K'6540100, LP=0, CNTRX=NO, PBX=YES, AUT=PBXD, GDN=K'6540101,
CHG=NO, ENH=NO;
MOB VSBR: SD=K'6540102, ED=K'6540115, LP=0, CNTRX=NO, PBX=YES, AUT=PBXD,
GDN=K'6540101, CHG=NO, ENH=NO;

ADD CNACLD: LP=0, PFX=K'654, CSTP=BASE, MINL=7, MAXL=7, CHSC=0, EA=NO,
Related Tasks
Related Concepts
None.

9.1.5 Configuring Data to Interwork with the PBX (Through the SIP
Trunk)
Scenarios
The PBX, which adopts SIP trunks, interworks with the SoftX3000 through a session border
controller (SBC). Figure 9-5 shows a typical networking model.
the SIP trunk)
SoftX3000
IP MAN
SBC
SIP trunk
(IP network)
IP PBX IP PBX IP PBX

……
In Figure 9-5 the SBC is a boarder router that guarantees the VoIP security and provides
multimedia services. Through the SBC, the SoftX3000 and the PBX can interwork with each
other by using the SIP signaling.
Prerequisites
Conditions

Data

Table 9-9 shows the data to be planned for interworking between the SoftX3000 and the PBX.
Table 9-9 Data for interworking between the SoftX3000 and the PBX through the SIP trunk
Name Value Obtain
SIP trunk data SIP code type Text format The value must -
be negotiated
with the PBX.
SIP trunk data IP address of the 191.169.150.30/ The value is The value is
IFMI of the 255.255.0.0 determined by determined
SoftX3000 the carrier. during the
hardware data
planning.
SIP trunk data UDP port 5060 The value is -

number of SIP determined by
on the the carrier.
SoftX3000 side
SIP trunk data IP address of the 211.169.150.48/ The value is -

SBC used for 255.255.0.0 determined by
SIP the carrier.
SIP trunk data UDP port 5060 The value is -

number of SIP determined by
on the SBC side the carrier.
SIP trunk data unified identity Domain The value must -

of PBX trunks be negotiated
with the PBX.
Documents
Workflow
2. SIP route data
3. SIP trunk data
5. Carrier label data

Procedure
1. Configure the SIP global data.

2. Configure the local port number and the protocol dispatch ability of the SIP.
NOTE
The first SIP message sent from the peer device to the local SoftX3000 carries the SIP well-known
5061 configured for the MSGI. The peer SIP entity, based on the local port number, routes SIP
response messages to the local SoftX3000. After receiving the messages, the IFMI of the SoftX3000
directly sends the messages to the MSGI whose local port number is 5061.
Step 2 Configure the SIP route data.

1. Configure the SIP office direction data.
NOTE
l According to the principle that there should not be alternate routing between offices of the same
level, if you set the PBX as an office of the same level, the SoftX3000 and the PBX cannot transfer
traffic between each other. Therefore, if the SoftX3000 acts as a gateway office, set the gateway
offices and local toll offices that interwork with the SoftX3000 as superior offices, and set other
exchanges in the local network as inferior offices. In this command, set Peer office level to
Inferior.
2. Configure the SIP sub-route data.

RENT=URT;
3. Configure the SIP route data.
ADD RT: R=Route number, RN=Route name, IDTP=UNKNOWN, NAMECFG=NO,

SNCM=SRT, SRST=SEQ, SR1=1st sub-route, TRIPFLAG=TRIP flag, STTP=Invalid
Value, REM=False;
4. Configure the SIP routing analysis data.

Step 3 Configuring SIP trunk data.

1. Add multimedia data.
ADD MMTE: EID=Equipment ID, IMSFLAG=NO, MN=FCCU module number,

PT=SIP, IFMMN=IFMI module number, AT=Authorized by EID, PASS=Authorization
password;

NOTE
l The difference between the SIP trunk configuration described in this section and ordinary SIP
trunk configuration is that you should configure data by running ADD MMTE. The data
configured is referenced after you set ISSUPPORTREG to Yes for the SIP trunk group.
l The maximum length of Equipment ID is 32 characters.
2. Configure the SIP trunk group data.
ADD SIPTG: TG=Trunk group number, SRT=Sub-route number, HCIC=Maximum call
number restriction, LCIC=Stop call restriction, ST=Server type, NOAA=False, EA=True,
UHB=Heartbeat Mode, VIDEOS=Video supported, CHBF=No heart beat, E2833F=2833
encryption flag, SELMODE=Distribute, ISSUPPORTREG=Trunk Support Register;
NOTE
l ISSUPPORTREG is set to YES. This indicates that the SIP trunk group can register with the
SoftX3000. That is, the SoftX3000 can interwork with the PBX through SIP trunks. This
parameter is available when you set Enhanced attribute to Yes in ADD SIPTG.
l Heartbeat Mode must be set carefully. If the SBC is unable to identify heartbeat signals, set
Heartbeat Mode to No heart beat. This indicates that the SoftX3000 does not send heartbeat
signals to the peer end. Otherwise, SIP trunks are always in faulty state.
l It is recommended that you set Call heart beat flag to NO and adopt Session Timer heartbeat
signals in SET SIPCFG. You can set the heartbeat interval by setting Session interval(s) (whose
default value is 300 seconds) in ADD SIPTG.
3. Configure the IP address pair data of the SIP trunk group.
URI 1, DH=False;
NOTE
If you set ISSUPPORTREG to YES during the SIP trunk configuration, you must set Trunk
Domain Name for the corresponding SIP trunk. The value of Trunk Domain Name is the value of
Equipment ID in ADD MMTE. OSU indicates the peer resource flag. The format of the parameter
value is IP address of the SBC:SIP port number. That is, OSU is set to 211.169.150.48:5060.

Step 5 Configure the carrier label data.
SET CARLBL: PROTO=Protocol, DIGRLM=DigestRealm, DIGDOM=DigestDomain;
NOTE
This command is used to configure the label information to be carried in the messages issued by the
SoftX3000.
----End
Example
Task Description
l Multiple SIP trunk circuits are set up between the SoftX3000 and PBXs through the SBC.

l The SoftX3000 is able to authenticate the SIP trunks connected to the PBX.
Scripts
//Configure the SIP protocol data.

//Configure the SIP route data.

ADD OFC: O=96, ON="SIP-OFC", DOT=PBX, DOL=LOW;
ADD SRT: SRC=96, O=96, SRN="To SIP-OFC", RENT=URT;
ADD RT: R=96, RN="SIP-RT", IDTP=UNKNOWN, NAMECFG=NO, SNCM=SRT, SRST=SEQ,
SR1=96, TRIPFLAG=NO, STTP=INVALID, REM=NO;
//Configure the SIP trunk data.

ADD MMTE: EID="PBX1.Embratel.com", IMSFLAG=NO, MN=22, PT=SIP, IFMMN=132,
AT=ABE, PASS="00000";
ADD SIPTG: TG=96, SRT=96, HCIC=10000, LCIC=9000, ST=NGNN, NOAA=NO,
EA=YES, UHB=NO, VIDEOS=SUPPORT, CHBF=NO, E2833F=NSUPPORT, SELMODE=DIST,
ISSUPPORTREG=YES;
ADD SIPIPPAIR: TG=10, IMN=132, OSU="221.169.150.48:5060", DH=No,
DOMAINNAME="PBX1.Embratel.com";

CHSC=0, EA=NO;
//Configure the carrier label data.

SET CARLBL: PROTO=SIP, DIGRLM="Embratel.com", DIGDOM="Embratel.com";
Related Tasks
Related Concepts
None.
9.2 Configuring Data to Interwork with IP U-Path

Scenarios
The IP U-Path can be directly connected to the SoftX3000 through an IP MAN. The IP U-Path
provides enterprise subscribers (Centrex subscribers) with operator operation functions, such as
call transfer, extension authority management, and extension charging management. Figure
9-6 shows the typical networking model where the IP U-Path interworks with the SoftX3000.

Figure 9-6 Typical networking model for the IP U-Path interworking with the SoftX3000
SoftX3000
Internal
protocol
IP U-Path
AMG
Centrex subscribers
As shown in Figure 9-6, Centrex subscribers can be of any type, including ESL, V5, SIP and
H.323 subscribers. ESL subscribers are used as an example here.
Prerequisites
Conditions

Data
IP U-Path.
Table 9-10 Data for interworking between the SoftX3000 and the IP U-Path

Name Value Obtain
Data on the IP address of 191.169.150.3 The value is The value is

SoftX3000 the IFMI of the 0/255.255.0.0 determined by determined
side SoftX3000 the carrier. during the
hardware
data planning.


Name Value Obtain
Data on the IP IP address of 211.169.150.1 The value is -

U-Path side the IP U-Path 1/255.255.0.0 determined by
the carrier.
Number of the 1 The value must -

IP U-Path be negotiated
with the IP U-
Path.
Registered upath The value must -

subscriber be negotiated
name of the IP with the IP U-
U-Path Path.
Registered ngnsx The value must -

password of be negotiated
the IP U-Path with the IP U-
Path.
Phone number 6540099 (short The value must -

of the IP U- number: 2099) be negotiated
Path with the IP U-
Path.
AMG.
Table 9-11 Data for interworking between the SoftX3000 and the AMG
Name Value Obtain
MGCP Protocol used MGCP The value must The value is

protocol for be negotiated determined
interworking with the AMG. during
between the configuring
the AMG interwork
with AMG.
MGCP code ABNF The value is The value is

type determined by determined
the carrier. during
configuring
data to
interwork
with AMG.


Name Value Obtain
Data on the IP address of 191.169.150.3 The value is The value is

SoftX3000 the IFMI of the 0/255.255.0.0 determined by determined
side SoftX3000 the carrier. during the
hardware
data planning.
Local UDP 2727 The value is -

MGCP on the the carrier.
SoftX3000
side
Data on the IP address of 211.169.150.5/ The value is The value is

AMG side the AMG 255.255.0.0 determined by determined
the carrier. during
configuring
data to
interwork
with AMG.
Local UDP 2944 The value is The value is

port number of determined by determined
MGCP on the the carrier. during
AMG side configuring
data to
interwork
with AMG.
Domain name shenzhen- The value must The value is

of the AMG amg5160-01.c be negotiated determined
om with the AMG. during
configuring
data to
interwork
with AMG.
Interface name aaln The value must The value is

of the AMG be negotiated determined
with the AMG. during
configuring
data to
interwork
with AMG.

termination ID with the AMG. during
(subscriber configuring
port) of the data to
AMG interwork
with AMG.


Name Value Obtain

the AMG G.729 with the AMG. during
configuring
data to
interwork
with AMG.

AMG supports be negotiated determined
hairpin with the AMG. during
connection configuring
data to
interwork
with AMG.

AMG supports be negotiated determined
the EC with the AMG. during
function configuring
data to
interwork
with AMG.
Subscriber data Phone number 6540090 (short The value must -

of subscriber A number: 2090) be negotiated
(whose with the AMG.
termination ID
is 0)

of subscriber B number: 2091) be negotiated
termination ID
is 1)

of subscriber C number: 2092) be negotiated
termination ID
is 2)

of subscriber D number: 2093) be negotiated
termination ID
is 3)
Documents

Workflow
The procedure for configuring the data between the SoftX3000 and the IP U-Path is as follows:
1. Centrex data
2. MGW data
3. Subscriber data
Procedure
Step 1 Configure the Centrex data.
1. Configure the Centrex group data.
ADD CXGRP: CGN=Centrex group name, CXG=Centrex group number,
UCPC=Capacity, WACF=False, BIF=False, CCF=False;
2. Configure the Centrex sub-group data.
ADD CXSUBGRP: CXG=Centrex group number, CXSG=Centrex subgroup number,
CXSGN=Centrex subgroup name;
3. Configure the Centrex intra-group charging data.
ADD CHGCX: CXG=Centrex group number, CHSC=Charging selection code,
RCHS=Caller charging source code, CHA=Charging case;
4. Configure the Centrex intra-group prefix data.
ADD ICXPFX: CXG=Centrex group number, CLRLP=Caller local DN set, PFX=Centrex
call prefix, CSA=Service attribute, MINL=Minimum number length, MAXL=Maximum
number length, CHSC=Charging selection code;
NOTE
The prefix 2 is used for calls between intra-group subscribers. Therefore, Service attribute must be
set to Intra-Centrex .
5. Configure the local IP address for controlling the console.
SET CONADDR: CONLAIP=Local IP address;
6. Configure the STUN protocol dispatch data.
ADD STUNDISP: FMN=IFMI module number, MMN=MSGI module number;
NOTE
l When the IP address of the IP U-Path is in the private network segment, the local port of the
STUN protocol must be added on the SoftX3000 side. This guarantees that the SoftX3000 and
the IP U-Path interwork correctly.
l By default, all MSGI modules are able to dispatch the STUN protocol. If the default configuration
has been modified, run SET DPA to reset it.
7. Configure the Centrex console data.
ADD CXCON: D=Subscriber number, MN=FCCU module number, CONNO=Console
number, IP=Console IP address, CODEC=Codec list, ACNT=Account name,

PWD=Password, CXG=Centrex group number, CXSG=Centrex subgroup number,

CXD=Centrex short number, RCHS=Charging source code, CSC=Call source code,
OCR=Call-out authority, CON=False, PBX=False, CHARGE=False, ENH=False;
NOTE
l To use a public dynamic IP address for the IP U-Path, set Console IP address to
255.255.255.255. In this case, the SoftX3000 does not authenticate the IP address.
l To use a public static IP address for the IP U-Path, set Console IP address to a valid IP address
(such as 191.169.150.99), or 255.255.255.255. When Console IP address is set to a valid IP
address, the SoftX3000 authenticates the IP address.
l To use a private IP address for the IP U-Path, set Console IP address to 255.255.255.255.
Otherwise, the IP U-Path cannot register. When Console IP address is set to 255.255.255.255,
the SoftX3000 does not authenticate the IP address.

IP address, RA1=Remote IP address 1, RP=Remote port, LISTOFCODEC=Codec list,
HAIRPIN=Hairpin connection, UCATT=Special attributes, ET=Not supported,
SUPROOTPKG=Not Supported;
NOTE
l When the AMG adopts MGCP, the format of Equipment ID is domain name, and you are advised
to set the domain name in the office name-MGW type-number format, for example, shenzhen-
amg5160-01.com.
l The AMG in the given example does not support hairpin connection. Therefore, Hairpin
connection must be set to Not supported. Otherwise, the configuration may result in abnormal internal
communication of the AMG.
DID=ESL, MN=FCCU module number, EID=Equipment ID, STID=Start MG termination ID,
CODEC=Codec prefer, RCHS=Charging source code, CSC=Call source code, UTP=NRM,
NS=Supplementary service, CNTRX=Centrex attribute, CGF=Centrex flag, CXG=Centrex
group number, SCXD=Start Centrex short number, COR=Console call-out authority,
PBX=False, CHG=False, ENH=False;
NOTE
l It is required that Centrex subscribers listen to the dual-stage dial tone after dialing the out-group prefix.
Therefore, Call source code is set to 1. That is, the number of pre-received digits is 1.
service.
l To manage the call-in, call-out and supplementary service authority of Centrex intra-group subscribers
through the IP U-Path, select SELECT ALL from the parameters Call-in authority, Call-out
authority, and Supplementary service

selection code, EA=False, SDESCRIPTION=Description;

NOTE
l Configure a valid Charging selection code (it is 0 in the given example) for each call prefix to guarantee
reliable charging.
mode; therefore, in the given example, the SoftX3000 selects the intra-office group charging mode
when an intra-office subscriber dials the prefix 654.
----End
Example
Task Description
l A, B, C and D are Centrex subscribers. They can call each another by dialing short numbers.
l The IP U-Path can transfer various calls, such as those from external subscribers to intra-
group subscribers, and those from intra-group subscribers to the toll exchange.
l You can manage the call-in authority, call-out authority and supplementary service
authority of Centrex intra-group subscribers on the IP U-Path.
Scripts
//Configure the Centrex data.

ADD CXGRP: CGN="Huawei", CXG=1, UCPC=100, WACF=NO, BIF=NO, CCF=NO;
ADD CXSUBGRP: CXG=1, CXSG=2, CXSGN="subgroup";
ADD CHGCX: CXG=1, CHSC=2, RCHS=65, CHA=0;
ADD ICXPFX: CXG=1, CLRLP=0, PFX=K'2, CSA=CIG, MINL=4, MAXL=4, CHSC=2;
SET CONADDR: CONLAIP="191.169.150.30";
ADD CXCON: D=K'6540099, MN=22, CONNO=1, IP="211.169.150.11",
CODEC=G711_A-1&G711_U-1&G729-1&G723_1-1, ACNT="upath", PWD="ngnsx",
CXG=1, CXSG=2, CXD=K'2099, RCHS=65, CSC=1, OCR=NTT-1&ITT-1&INTT-1&IITT-1,
CON=NO, PBX=NO, CHARGE=NO, ENH=NO;

ADD MGW: EID="shenzhen-amg5160-01.com", GWTP=AG, MGWDESC="shenzhen-
amg5160-01", MGCMODULENO=22, PTYPE=MGCP, LA="191.169.150.30",
RA1="211.169.150.5", RP=2944,
LISTOFCODEC=PCMA-1&PCMU-1&G7231-1&G729-1&T38-1, HAIRPIN=NS,
UCATT=NOFX-0&NOM-0&V3FX-1, ET=NO, SUPROOTPKG=NS;

ADB VSBR: SD=K'6540090, ED=K'6540093, LP=0, DID=ESL, MN=22, EID="shenzhen-
amg5160-01.com", STID=0, CODEC=PCMA, RCHS=65, CSC=1, UTP=NRM, NS=CLIP-1,
CNTRX=YES, CGF=YES, CXG=1, SCXD=K'2090, COR=ITT-1&IITT-1, PBX=NO, CHG=NO,
ENH=NO;;

ADD CNACLD: LP=0, PFX=K'654, CSTP=BASE, MINL=7, MAXL=7, CHSC=0, EA=NO,
Related Tasks

Centrex Data Commissioning
Related Concepts
None.
9.3 Configuring Data to Interwork with ISDN U-Path

Scenarios
The ISDN U-Path can be directly connected to the SoftX3000 through the AMG (or the
UMG8900). The ISDN U-Path provides enterprise subscribers (Centrex subscribers) with
operator operation functions, such as call transfer, extension authority management, and
extension charging management. Figure 9-7 shows the typical networking model where the
ISDN U-Path interworks with the SoftX3000.
Figure 9-7 Typical networking model for the ISDN U-Path interworking with the SoftX3000
SoftX3000
AMG
ISDN U-Path Subscriber A Subscriber B
Centrex subscribers
As shown in Figure 9-7, Centrex subscribers can be of any type, including ESL, V5, SIP, H.
323, ISDN U-Path, and IP U-Path. The following description is based on the assumption that
subscribers A and B are both ESL subscribers.
Prerequisites
Conditions
l You have the administrator rights.


Data
Table 9-12 shows the data to be planned for interworking between the SoftX3000 and the AMG.
Table 9-12 Data for interworking between the SoftX3000 and the ISDN U-Path
Name Value Obtain
Data on the IP address of the 191.169.150.30 The value is The value is

SoftX3000 IFMI of the /255.255.0.0 determined by determined
hardware data
planning.
Local UDP port 2944 The value is -

number of H. determined by
248 on the the carrier.
SoftX3000
Local port 9901 The value is -

IUA link on the the carrier.
SoftX3000
Data on the IP address of the 211.169.150.6/2 The value is The value is

AMG AMG 55.255.0.0 determined by determined
the carrier. during the data
planning for
interworking
with the AMG.
Local UDP port 2944 The value is The value is

number of H. determined by determined
248 on the AMG the carrier. during the data
planning for
interworking
with the AMG.
Domain name of 211.169.150.6:2 The value must The value is

the AMG 944 be negotiated determined
with the AMG. during the data
planning for
interworking
with the AMG.
Interface name aaln The value must -

of the AMG be negotiated
with the AMG.


Name Value Obtain
Numbering plan Starting from 0 The value must The value is

of termination be negotiated determined
ID (subscriber with the AMG. during the data
port) of the planning for
AMG interworking
with the AMG.
Speech codecs G.711, G.711μ, The value must The value is

supported by the G.723.1, G.729 be negotiated determined
AMG with the AMG. during the data
planning for
interworking
with the AMG.
IUA linkset data 8+OVERRIDE The value must -

(linkset index + be negotiated
traffic mode) on with the AMG.
the AMG
IUA link data 8+9900 The value is -

(link number + determined by
local port) on the carrier.
the AMG
Interface ID on 2 The value must -

the AMG be negotiated
with the AMG.
Data on the ISDN data index 8 The value is -

ISDN U-Path (The maximum determined by
number of B the carrier.
channels is 2.)

of the ISDN U- number: 60000) be negotiated
Path (The with the AMG.
terminal ID is 2
and the interface
ID is 2.)
Subscriber data Phone number 6540090 (short The value must -

of subscriber A number: 60090) be negotiated
(The terminal with the AMG.
ID is 0.)

of subscriber B number: 60091) be negotiated
(The terminal with the AMG.
ID is 1.)
Documents

Workflow
The procedure for configuring the data between the SoftX3000 and the ISDN U-Path is as
follows:
1. Configure the Centrex data.
2. Configure the MGW and IUA link data.
3. Configure the ISDN U-Path data.
Procedure
Step 1 Configure the Centrex data.
1. Configure the Centrex group data.
ADD CXGRP: CGN=Centrex group name, CXG=Centrex group number,
UCPC=Capacity, WACF=False, BIF=False, CCF=False;
2. Configure the Centrex subgroup data.
ADD CXSUBGRP: CXG=Centrex group number, CXSG=Centrex subgroup number,
CXSGN=Centrex subgroup name;
3. Configure the Centrex intra-group charging data.
ADD CHGCX: CXG=Centrex group number, CHSC=Charging selection code,
RCHS=Caller charging source code, CHA=Charging case;
4. Configure the Centrex intra-group prefix data.
ADD ICXPFX: CXG=Centrex group number, CLRLP=Caller local DN set, PFX=Centrex
call prefix, CSA=Service attribute, MINL=Minimum number length, MAXL=Maximum
number length, CHSC=Charging selection code;
5. Configure the Centrex out-group prefix data.
ADD OCXPFX: CXG=Centrex group number, OGP=Out-group prefix;
Step 2 Configure the MGW and IUA link data.
description, MGCMODULENO=FCCU/AGCU/UACU module number,
PTYPE=Protocol type, LA=Local IP address, RA1=Remote IP address 1, RP=Remote port,
LISTOFCODEC=Codec list, ET=Not supported, SUPROOTPKG=Not Supported;
2. Configure the signaling gateway data.
NOTE
SG type must be set to Embedded SG.

3. Configure the IUA linkset data.

ADD IUALKS: LSX=Linkset index, LSNAME=Linkset name, TM=Traffic mode,

DT=Device type, MN=FCCU module number, SGID=Signaling gateway ID;
NOTE
Linkset index and Traffic mode must be set in compliance with the configuration on the AMG.
4. Configure the IUA link data.
LOCPORT=Local port number, LOCIP1=Local IP address1, PEERPORT=Peer port
number, PEERIP1=Peer IP address1;
NOTE
Link number, Peer port number, and Peer IP address1 must be set in compliance with the
configuration on the AMG.
Step 3 Configure the ISDN U-Path data.

1. Configure the ISDN data.
ADD ISDNDAT: ISDN=Index, BCHN=Maximum B channel;
NOTE
Maximum B channel must be set to 2.

2. Configure the ISDN U-Path data.
ADD ISDNCON: D=Subscriber number, LP=Local DN set, EID=Equipment ID,
TID=Termination ID, LKS=IUA linkset index, IID=Interface ID, ISDN=ISDN index,
CXG=Centrex group number, CXSG=Centrex subgroup number, CXD=Centrex short
number, RCHS=Charging source code, CSC=Call source code, CON=NO, PBX=False,
CHARGE=False, ENH=False;
NOTE
Termination ID and Interface ID must be set in compliance with the configuration on the AMG.
DID=Port type, MN=FCCU module number, EID=Equipment ID, STID=Start MG termination
ID, RCHS=Charging source code, CSC=Call source code, UTP=Ordinary, CNTRX=Centrex
attribute, CGF=Centrex flag, CXG=Centrex group number, CXSG=Centrex subgroup number,
SCXD=Start Centrex short number, PBX=False, CHG=False, ENH=False;
NOTE
To manage the call-in, call-out and supplementary service authority of Centrex intra-group subscribers
through the ISDN U-Path, choose SELECT ALL for parameters Call-in authority, Call-out authority,
and Supplementary service.

selection code, EA=False, SDESCRIPTION=Destination;
NOTE
Configure a valid Charging selection code (it is 0 in the given example) for each call prefix to guarantee
reliable charging.
----End

Example
Task Description
l A and B are Centrex subscribers. They can call each other by dialing short numbers.
l The ISDN U-Path can transfer various calls, such as calls from external subscribers to intra-
group subscribers, and calls from intra-group subscribers to the toll exchange.
l You can manage the call-in authority, call-out authority and supplementary service
authority of Centrex intra-group subscribers on the ISDN U-Path.
Scripts
//Configure the Centrex data.

ADD CXGRP: CGN="Centrex", CXG=0, UCPC=60, WACF=NO, BIF=NO, CCF=NO;
ADD CXSUBGRP: CXG=0, CXSG=0, CXSGN="Sub-Centrex";
ADD OCXPFX: CXG=0, OGP=K'0;
//Configure the MGW and IUA link data.

ADD MGW: EID="211.169.150.6:2944", GWTP=AG, MGWDESC="AMG",
MGCMODULENO=22, PTYPE=H248, LA="191.169.150.30", RA1="211.169.150.6",
RP=2944, LISTOFCODEC=PCMA-1&PCMU-1&G7231-1&G729-1&G726-1, ET=NO,
SUPROOTPKG=NS;
ADD SG: SGID=8, SGNAME="SG-Gateway", SGTYPE=emb,
EID="211.169.150.6:2944";
ADD IUALKS: LSX=8, LSNAME="IUA-LKS", TM=OVERRIDE, DT=BRA, MN=22, SGID=8;
PEERPORT=9900, PEERIP1="211.169.150.6";
//Configure the ISDN U-Path data.

ADD ISDNDAT: ISDN=8, BCHN=2;
ADD ISDNCON: D=K'6540000, LP=0, EID="211.169.150.6:2944", TID="2", LKS=8,
IID=2, ISDN=8, CXG=0, CXSG=0, CXD=K'60000, RCHS=10, CSC=0, CON=NO,
PBX=NO, CHARGE=NO, ENH=NO;

EID="211.169.150.6:2944", STID="0", RCHS=10, CSC=0, UTP=NRM, CNTRX=YES,
CGF=YES, CXG=0, CXSG=0, SCXD=K'60090, PBX=NO, CHG=NO, ENH=NO;

ADD CNACLD: LP=0, PFX=K'654, CSTP=BASE, MINL=7, MAXL=7, CHSC=0, EA=NO;
Related Tasks
Centrex Data Commissioning
Related Concepts
None.

9.4 Configuring Data to Interwork with the AS (Through

SIP)
Scenarios
When the SoftX3000 interworks with the AS in the NGN and provides NGN value-added
services such as SIP-PPS, ONLY, and CRBT, SIP is used as the control signaling. Figure 9-8
shows a typical networking model.
Figure 9-8 Typical networking model for the SoftX3000 to interwork with the AS (through SIP)
SoftX3000 SMS
IP SIP
MAN
AS
AS MRS
Huawei U-NICA system
SIP Phone AMG TMG H.323 Phone
Prerequisites
Conditions
Data
Table 9-13 shows the data to be planned for interworking between the SoftX3000 and the AS
through SIP.

Table 9-13 Data for interworking between the SoftX3000 and the AS through SIP

Name Value Obtain
SIP protocol Signaling SIP The value must -

between the be negotiated
SoftX3000 and with the AS.
the AS
SIP trunk data IP address of the 191.169.150.30/ The value is The value is
hardware data
planning.

SIP on the the carrier.
SoftX3000 side
IP address of the 211.169.150.38/ The value is -

AS 255.255.0.0 determined by
the carrier.

SIP on the peer the carrier.
softswitch side
Sending mode Sent by the The value must -

of call heartbeat SoftX3000 and be negotiated
detected by the with the AS.
AS
Period of call Six minutes (by The value must -

heartbeat default) be negotiated
with the AS.
Documents
Workflow
The procedure for configuring the data between the SoftX3000 and the AS is as follows:
2. SIP route data
3. SIP trunk data

Procedure
1. Configure the SIP global data.
2. Configure the local port and protocol dispatch ability of the SIP.
NOTE
The first SIP message sent from the peer softswitch to the SoftX3000 carries the SIP well-known
5061 configured for the MSGI. The peer softswitch receives the returned SIP message and sends
messages that contain the local port number 5061 of the MSGI. After receiving the messages, the
IFMI of the SoftX3000 directly sends the messages to the MSGI whose local port number is 5061.
Step 2 Configure the SIP route data.

1. Configure the SIP office direction data.
NOTE
l Office names must be specified as required. Do not use the default name offered by the system.
2. Configure the SIP sub-route data.
RENT=Unrent;
3. Configure the SIP route data.
4. Configure the SIP routing analysis data.
NOTE
Step 3 Configure the SIP trunk data.

1. Configure the SIP trunk group data.

HCIC=Maximum call number restriction, LCIC=Stop call restriction, NOAA=NO,

EA=YES, UHB=Heartbeat Mode, VIDEOS=Video supported, CHBF=No heart beat,
E2833F=2833 encryption flag, SELMODE=Distribute;
NOTE
l Heartbeat Mode must be set correctly. If the peer AS cannot identify heartbeat signals,
Heartbeat Mode must be set to No heart beat. Otherwise, the SIP trunk is faulty all the time.
l If you set Call heart beat flag to Local heart beat, the SoftX3000 periodically sends an Option
message to the AS for heartbeat test when there is a call on the SIP trunk group. After receiving
an Option message, the AS returns a 200 response to the SoftX3000, indicating that the call status
on the two sides is consistent. If the AS returns a 481 response to the SoftX3000 or does not
respond, it indicates that the AS has released the call or an error occurs in the call. In this case,
the SoftX3000 immediately releases the call.
2. Configure the IP address pair data of the SIP trunk group.
URI 1, DH=False;
NOTE
Set Remote URI to a value in the format of peer IP address:SIP port number, for example,
211.169.150.38:5060.

attribute, RSC=oute selection code, MINL=Minimum number length, MAXL=Maximum
NOTE
NGN value-added services, such as SIP-PPS and ONLY, are different from ordinary IN services because
NGN value-added services are triggered by the AS that controls their service logics. You only need to
configure the access code on the SoftX3000 side and route the service to the mapping SIP trunk.
----End
Example
Task Description
l The access code for the SIP-PPS service is set to 205. The access code for the ONLY service
is set to 202.
l SIP connection must be set up between the SoftX3000 and AS through data configuration
on the SoftX3000 side.
Scripts
//Configure the SIP protocol data.
//Configure the SIP route data.

ADD OFC: O=80, ON="APP Server", DOT=CMPX, DOL=LOW;
ADD SRT: SRC=80, O=80, SRN="To APP Server", RENT=URT;
ADD RT: R=80, RN="To APP Server", IDTP=UNKNOWN, NAMECFG=NO, SNCM=SRT,


//Configure the SIP trunk data.

ADD SIPTG: TG=80, SRT=80, TGN="To APP Server", RCHS=88, OTCS=99, HCIC=200,
LCIC=180, NOAA=NO, EA=YES, UHB=NO, VIDEOS=NSUPPORT, CHBF=LOCTEST,
E2833F=NSUPPORT, SELMODE=DIST;

CHSC=0, EA=NO;
CHSC=0, EA=NO;
Related Tasks
Related Concepts
None.
9.5 Configuring Data to Interwork with the SHLR

Scenarios
Before configuring NP service data or smart network service data in SHLR mode, configure
signaling data for interworking between the SoftX3000 and the SHLR. Otherwise, the NP service
or smart network service cannot be deployed. Figure 9-9 shows a typical networking model
where M3UA links carry MAP signaling (that is, MAP/TCAP/SCCP/M3UA) on both the
SoftX3000 side and the SHLR side.
Figure 9-9 Typical networking model for the SoftX3000 to interwork with the SHLR
SoftX3000
SHLR
IP M3UA links
MAN
SIP Phone AMG TMG H.323 Phone

Prerequisites
Conditions

Data
Table 9-14 shows the data to be planned for interworking between the SoftX3000 and the SHLR.
Table 9-14 Data for interworking between the SoftX3000 and the SHLR

Name Value Obtain
M3UA data IP address of the 191.169.150.30/ The value is The value is

hardware data
planning.
IP address of the 211.169.150.36/ The value is -

SHLR 255.255.0.0 determined by
the carrier.
SPC of the 001122 The value is The value is

SoftX3000 (national determined by determined
network) the carrier. during the
hardware data
planning.
SPC of the 1100ee The value is -

SHLR (national determined by
network) the carrier.
Local SCTP M3UA link 2: The value is -

port number of 2905 M3UA determined by
M3UA links on link 3: 2911 the carrier.
the SoftX3000
side (client)
Local SCTP 2905 The value is -

M3UA links on the carrier.
the SHLR side
(server)
Routing context 12345 The value is -

determined by
the carrier.


Name Value Obtain
Traffic mode of Load sharing The value is -

the M3UA mode determined by
linkset the carrier.
Work mode of IPSP The value is -

the SoftX3000 determined by
in the M3UA the carrier.
linkset
Work mode of IPSP The value is -

the SG7000 in determined by
the M3UA the carrier.
linkset
SCCP data Subsystem MSC, HLR The value is -

between the the carrier.
SoftX3000 and
the SHLR
SHLR data SHLR address 0 The value is It uniquely

index determined by defines an
the carrier. SHLR group
number within
the SoftX3000.
SHLR group 0 The value is -

the carrier.
Documents
Workflow
The procedure for configuring the data between the SoftX3000 and the SHLR is as follows:
1. M3UA data
2. SCCP data
3. SHLR data
Procedure
1. Configure the M3UA local entity data.

ADD M3LE: LEX=Local entity index, LENAME=Local entity name, OPC=Signaling

point code of local entity, LET=Local entity type, RC=Route context;
NOTE
The routing context can be a decimal number or null (not set). It must be consistent with that on the
SHLR side.
2. Configure the M3UA destination entity data.
ADD M3DE: DEX=Destination entity index, LEX=Local entity index,

DENAME=Destination entity name, DPC=Signaling point code of destination entity,
DET=Destination entity type;
NOTE
The SoftX3000 interworks with the SHLR in peer-to-peer mode and the entity type of the SoftX3000
is AS. Therefore, set the destination entity type of the SHLR to AS.
3. Configure the M3UA linkset data.
ADD M3LKS: LSX=Linkset index, LSNAME=Linkset name, ADX=Adjacent destination

entity index, TM=Traffic mode, WM=Work mode;
NOTE
l M3UA signaling links in the associated signaling mode exist between the SoftX3000 and the
SHLR. Therefore, set Adjacent entity index in the command to the destination entity index of
the SHLR.
l The SoftX3000 and the SHLR interwork with each other in peer-to-peer mode and the SoftX3000
acts as an AS. Therefore, set Work mode in the command to IPSP.
l The traffic mode of the linkset must be consistent with that on the SG7000 side. Otherwise, none
of the M3UA links of the linkset can work normally. Set Traffic mode to Load-sharing for a
linkset, unless specified otherwise.
4. Configure the M3UA link data.
ADD M3LNK: MN=BSGI module number, LNKN=Link number, LNKNAME=Link

name, LOCIP1=Local IP address1, LOCPORT=Local port number, PEERIP1=Peer IP
address1, PEERPORT=Peer port number, CS=Client/Server mode, LSX=Linkset index;
NOTE
If the system is configured with two BSGI modules, allocate the two M3UA links to each of them.
This guarantees reliability of the M3UA links.
5. Configure the M3UA route data.
ADD M3RT: RTNAME=Route name, DEX=Destination entity index, LSX=Linkset

index;

1. Configure the SCCP DSP data.
ADD SCCPDSP: DPX=DSP index, NI=Network indicator, DPC=DPC, OPC=OPC,

DPNAME=DSP name, SHAREFLAG=NONE;
NOTE
l DSP index defined by running ADD SCCPDSP, DSP index defined by running ADD
N7DSP, and Destination entity index defined by running ADD M3DE are different parameters.
There is no referencing or referenced relationship among them.
l When the local office uses multiple SPCs, set OPC according to the actual signaling networking.

2. Configure the SCCP subsystem data.

number, SPC=SPC, OPC=OPC, SSNNAME=SSN name;
NOTE
l For smart network services, set two SSNs: MSC and HLR.
l SPC in the command is the DPC of the mapping subsystem, that is, the receiver of local SCCP
messages. For each subsystem, you must define two DSPs, namely, SCCP remote SP and local
SP.
Step 3 Configure the SHLR data.

1. Configure the SHLR local address data.
ADD SHLRLA: SHLRAddrIndex=SHLR address index, SHLRDESC=SHLR
description, RT=DPC, OPC=OPC, SSN=SCCP sub-system number;
NOTE
SCCP sub-system number must be set to MSC 0x08.

2. Configure the SHLR remote address data.
ADD SHLRRA: SHLRAddrIndex=SHLR address index, RT=DPC, DPC=DPC,
SSN=SCCP sub-system number;
NOTE
l SCCP sub-system number must be set to HLR 0x06.

l SHLR address index must be the same as SHLR address index in ADD SHLRLA.
3. Configure the SHLR group data.
ADD SHLRGRP: SHLRGrpNumber=SHLR group number, SelectMode=STB,
SHLRIDX1=SHLR index 1;
NOTE
SHLR index 1 must be defined by SHLR address index in ADD SHLRRA before being referenced
here.
----End
Example
Task Description
l Two M3UA links are configured between the SoftX3000 and the SHLR for carrying the
SS7 signaling services in load sharing mode.
l SCCP connection can be set up between the SoftX3000 and the SHLR.
Scripts
//Configure the M3UA data.
ADD M3DE: DEX=60, LEX=0, DENAME="SHLR", DPC="1100ee", DET=AS;
ADD M3LKS: LSX=2, LSNAME="To SHLR", ADX=60, TM=LOADSHARE, WM=IPSP;
ADD M3LNK: MN=136, LNKN=2, LNKNAME="To SHLR #0", LOCIP1="191.169.150.30",
LOCPORT=2905, PEERIP1="211.169.150.36", PEERPORT=2905, CS=C, LSX=2;

ADD M3LNK: MN=137, LNKN=2, LNKNAME="To SHLR #1", LOCIP1="191.169.150.30",

LOCPORT=2911, PEERIP1="211.169.150.36", PEERPORT=2905, CS=C, LSX=2;
ADD M3RT: RTNAME="To SHLR", DEX=60, LSX=2;
//Configure the SCCP data.

ADD SCCPDSP: DPX=3, NI=NAT, DPC="1100ee", OPC="001122", DPNAME="SHLR",
SHAREFLAG=NONE;
ADD SCCPSSN: SSNX=6, NI=NAT, SSN=MSC, SPC="001122", OPC="001122",
SSNNAME="MSC to MSC";
ADD SCCPSSN: SSNX=7, NI=NAT, SSN=HLR, SPC="001122", OPC="001122",
ADD SCCPSSN: SSNX=8, NI=NAT, SSN=MSC, SPC="1100ee", OPC="001122",
SSNNAME="MSC to SHLR";
ADD SCCPSSN: SSNX=9, NI=NAT, SSN=HLR, SPC="1100ee", OPC="001122",
SSNNAME="MSC to SHLR";
//Configure the SHLR data.

ADD SHLRLA: SHLRAddrIndex=0, SHLRDESC="SHLR", RT=DPC, OPC="001122",
SSN=MSC;
ADD SHLRRA: SHLRAddrIndex=0, RT=DPC, DPC="1100ee", SSN=HLR;
ADD SHLRGRP: SHLRGrpNumber=0, SelectMode=STB, SHLRIDX1=0;
Related Tasks
Related Concepts
For details about the relation between SIP signaling data tables, see 12.6.2 Relations Between

Initial Configuration 10 Typical Networking Configuration Examples
10 Typical Networking Configuration

Examples
About This Chapter
10.1 Configuring Dual Homing Data (Active/Standby Mode)

10.2 Configuring Dual Homing Data (Load-Sharing Mode)
10.3 Configuring Smart Network Data
10.4 Configuring Smart Network Data (with the SCPs Working in the Active/Standby Mode)
10.5 Configuring Multi-SPC Network Data
10.6 Configuring Multi-Area-Code Data
10.7 Configuring MOIP Networking Data
10.8 Configuring Data for Blended Application of Public and Private Networks

10 Typical Networking Configuration Examples Initial Configuration
10.1 Configuring Dual Homing Data (Active/Standby

Mode)
Scenarios
Dual homing is a disaster tolerance mechanism that prevents the softswitch from breaking down
in the case of a disaster. According to the Huawei U-SYS solution, the networking model for
the SoftX3000 that adopts the dynamic dual homing solution in active/standby mode is as shown
in Figure 10-1.
Figure 10-1 Networking diagram of the dynamic dual homing solution in active/standby mode
Actice Standby
SoftX3000 SoftX3000
UMG_A
IP packet network PSTN
UMG_B
Legend:
Heartbeat link
IAD AMG UMG Packet
Primary signaling channel
teminal Secondary signaling
Access layer of local network channel
Consider the networking shown in Figure 10-1 as an example. You must configure data on the
two SoftX3000s to meet the following requirements:
l The two SoftX3000s work in mutual aid mode and adopt the automatic switchover mode.
l Normally, the active SoftX3000 controls and manages MGWs in the whole network and
provides services for subscribers.
l After dual homing switchover, the standby SoftX3000 controls and manages the MGWs
in the whole network and provides services for subscribers.
Prerequisites
Conditions

Data
The active and standby SoftX3000s in the dual homing network share the same configurations
of hardware, software, and public data. The only difference is that the IP addresses of the
SoftX3000s are different. Table 10-1 lists the data needs to be planned for active and standby
SoftX3000s in the dual homing network.
Table 10-1 Dual homing data to be planned
Item Active Standby Remarks

SoftX3000 SoftX3000
IP 191.169.150. 191.169.150. The active and standby SoftX3000s must be

address 30 31 configured with different external IP addresses.
of the
IFMI
board
SPC 001122 001122 The active and standby SoftX3000s can share the
(national (national same SPC.
network) network)
Dual Automatic Automatic None

homing switchover switchover
work
mode
Documents
Before configuring the dual homing data, you must plan the related data based on the
Workflow
The procedure for configuring the dual homing data is as follows:
1. Configuring data on the active SoftX3000

(1) Add FE port configuration.
(2) Configure local office information.
(3) Configure dual homing work mode data.
(4) Configure other data.
2. Configure data on the standby SoftX3000.
(1) Get offline.
(2) Copy configuration database file of active SoftX3000.
(3) Restore BAM database of standby SoftX3000 by using SQL server 2000.
(4) Change certain settings by using the Dual Homing Change tool.

(5) Configure dual homing work mode data.

(6) Convert data format and getting online.
(7) Load data to the host.
(8) Check data consistency.
Procedure
Step 1 Configure data on the active SoftX3000.
1. Add FE port configuration.
DGW="191.169.150.1", EA=FH;
NOTE
l Set the IP address of the default router (gateway) of the FE port correctly. Otherwise, the
SoftX3000 fails to communicate with other network elements through IP.
l Set Ethernet attribute of the FE port to Full-duplex, 100Mbit/s. In addition, set the LAN Switch
port that is connected to the FE port of the SoftX3000, to Full-duplex, 100Mbit/s.
l Ensure that the active SoftX3000 and the standby SoftX3000 use different external IP addresses.
2. Configure local office information.
SET OFI: OFN="SZSX_M", LOT=CMPX, NN=YES, SN1=NAT, SN2=NAT, SN3=NAT,
SN4=NAT, NPC="001122", NNS=SP24, SPF=YES, TMZ=21;
NOTE
The active SoftX3000 and the standby SoftX3000 can use the same local SPC.
3. Configure dual homing work mode data.
NOTE
To set Switch mode of the local SoftX3000 to Automatic, perform the following steps:
l Run SET DHWM to set Work mode of the local SoftX3000 to Assistant, and Switch mode to
Manual.
l Run ADD DHHCFG to add a dual homing heartbeat link.
l Run SET DHWM to set Work mode of the local SoftX3000 to Assistant, and Switch mode to
Automatic.
SET DHWM: WM=ASSIST, SM=MANUAL, FS=DEACTIVE;
SET DHWM: WM=ASSIST, SM=AUTO, TM=MODE1-1&MODE2-1, HT=30;
ADD DHHCFG: MN=132, IP="191.169.150.31", KEY="123456";
The preceding command means that the work mode of the local SoftX3000 is Assistant,
the switchover mode is Automatic, the takeover mode is SELECT ALL, and the
handshake time is 30 x 5 = 150 seconds. The dual homing work mode is usually configured
as follows: The work mode of the local SoftX3000 is set to Assistant, the switchover mode
is set to Automatic, and the takeover mode is set to Deactivated enable.
4. Configure other data.
l Configure other basic data, interworking data, and service data according to the ordinary
deployment flow. Select Master (default value) for Master/Slave type of all category
1 data.
l The commands related to category 1 data include ADD MGW, ADD MMTE, ADD
M2LNK, ADD M3LNK, ADD V5UALNK, ADD IUALNK, and ADD N7LNK.
Step 2 Configure data on the standby SoftX3000.
1. Get offline.

LOF:;
SET FMT: STS=OFF;
2. Copy configuration database file of active SoftX3000.
After configuring and commissioning the data of the active SoftX3000, copy all the files
in F:\SoftX3000 on the BAM of the active SoftX3000 to F:\SoftX3000 on the BAM of the
standby SoftX3000.
3. Restore BAM database of standby SoftX3000 by using SQL server 2000.
l For details, refer to restoring the BAM database
l After restoring the BAM database of the standby SoftX3000, do not format the BAM
database. That is, do not load the data to the host.
4. Change the settings of the following items according to the Dual Homing Change tool:
l IP address
l Signaling point
l Dual homing data
5. Configure dual homing work mode data.
MOD DHHCFG: MN=132, IP="191.169.150.30", KEY="123456";
NOTE
l After converting the data flag for the BAM database of the standby SoftX3000, run MOD
DHHCFG to modify the dual homing heartbeat link data. Otherwise, the dual homing heartbeat
link of the standby SoftX3000 fails to work.
l The preceding command means that the work mode of the local SoftX3000 is Assistant, the
switchover mode is Automatic, the takeover mode is SELECT ALL, and the handshake time
is 30 x 5 = 150 seconds. The dual homing work mode is usually configured as follows: The work
mode of the local SoftX3000 is set to Assistant, the switchover mode is set to Automatic, and
the takeover mode is set to Deactivated enable.
6. Convert data format and getting online.
SET FMT: STS=ON;
FMT:;
LON:;
7. Load data to the host.
Power off the frames of the standby SoftX3000, and then power them on to reload the data
from the BAM to the host.
8. Check Data Consistency
Run STR CRC to check the consistency of the foreground data and background data of all
the modules.
l If the data is consistent in all modules, the recovery of the BAM data is complete.
l If foreground data and background data of a module is inconsistent, proceed as follows,
according to the actual conditions:
– Run SND SPD to resend the inconsistent data table in the module to the host.
– If the problem persists, reset the host of the standby SoftX3000 to reload all the data
from the BAM. Obtain tickets before resetting the host so that the tickets are not
lost.
----End

Related tasks
Commissioning the Dual-Homing Networking Data
Related concepts
None.
10.2 Configuring Dual Homing Data (Load-Sharing Mode)
Scenarios
According to the Huawei U-SYS solution, the networking model for the SoftX3000 that adopts
the dynamic dual homing solution in load sharing mode is as shown in Figure 10-2.
Figure 10-2 Networking diagram of the dynamic dual homing solution in load sharing mode
SoftX3000 SoftX3000 Legend:

in office A in office B
Heartbeat link
Primary signaling channel
Secondary signaling channel
UMG_A
UMG_B
Packet Packet
IAD AMG UMG IAD AMG UMG
Terminal Terminal
Accessed by office A Accessed by office B
Consider the networking shown in Figure 10-2 as an example. Assume that office A provides
subscriber numbers 654xxxx and office B provides subscriber numbers 878xxxx. You must
configure data on the two SoftX3000s to meet the following requirements:
l The two SoftX3000s work in mutual aid mode and adopt the automatic switchover mode.
l The access devices in office A and TMG_A are primarily controlled by the SoftX3000 in
office A and secondarily controlled by the SoftX3000 in office B.
l The access devices in office B and TMG_B are primarily controlled by the SoftX3000 in
office B and secondarily controlled by the SoftX3000 in office A.
l After the dual homing switchover, the following items of each subscriber in each office do
not change:

– Telephone number
– Subscriber attributes
– Dialing mode
– Routing mode
– Charging mode
Prerequisites
Conditions
Data
The key principle for configuring dual homing data is to ensure that the mutual aid data is
consistent and coordinate between the two SoftX3000s in mutual aid. That is, data configured
on the primary SoftX3000 must be consistent with that configured on the secondary SoftX3000,
such as:
l GW registry information
l Signaling interworking information
l Trunk interworking information
l Routing plan
l Dialing plan
l Charging plan
l Number allocation plan
l Subscriber attributes
One SoftX3000 can take over a part of or all the services of the other SoftX3000 after the dual
homing switchover, only when data is consistent.

CAUTION
l When the system adopts the dual homing mode, the number of gateways or the number of
subscribers under the control of a single SoftX3000 cannot be greater than 50 percent of the
maximum capacity of the SoftX3000.
l The number of subscribers connected to one FCCU should be set to 50% of the total number
of subscribers that a local office or a mutual aid office can carry.
l The number of GWs and SIGTRAN links controlled by one BSGI should be set to 50% of
the total number of GWs and SIGTRAN links that a local office or a mutual aid office can
control.
l When SoftX3000s in offices A and B interwork with the SoftX3000 in office C through SIP-
T trunks, and if the dual homing switchover is carried out due to a fault in the SoftX3000 in
office A (the local office), you must configure the alternate route data in office C to route a
call from office C to the subscriber of original office A, who is now under the control of
office B (mutual aid office). That is, set the route from office C to office A as a direct route,
and the route from office C to office B as an alternate route.
l When SoftX3000s in offices A and B interwork with the same STP through MTP links
directly, and if the dual homing switchover is carried out due to a fault in the SoftX3000 in
office A (the local office), you must configure the alternate signaling route data in the STP
to route a signaling message from the STP to the SPC of the original office A, which is now
under the control of office B (mutual aid office). That is, set the route from the STP to office
A as a normal route, and the route from the STP to office B as an alternate route. In office
B, you also need to set the SPC of office B as the mutual aid node of the office A's SPC.
To ensure data consistency, comply with the principles listed in Table 10-2.
Table 10-2 Principles for configuring the dual homing data

Category Sub-Category Configuration Principle
Hardware data - Configure it based on the actual condition.
Local office SPC Configure it based on the actual condition.

data
Local DN set Configure a unique range of the local DN set for
each SoftX3000. For example, set the local DN set
of office A to range from 0 to 9, and that of office B
to range from 10 to 19.
Call source code Configure a unique range of call source codes for
each SoftX3000. For example, set the call source
codes of office A to range from 0 to 49, and those
of office B to range from 50 to 99.
Route selection Configure a unique range of route selection source

source code codes for each SoftX3000. For example, set the
route selection source codes of office A to range
from 0 to 9, and those of office B to range from 10
to 19.

Local office Failure source code Configure a unique range of failure source codes for
data each SoftX3000. For example, set the failure source
codes of office A to range from 0 to 9, and those of
office B to range from 10 to 19.
Charging data - To simplify data configuration, you are advised to

configure the same charging data for the two
SoftX3000s, including the date type, week type,
charging case, charging mode, charging source
code, outgoing trunk charging source code,
charging selection code, and callee charging source
code.
MGW data - Configure it based on the actual condition.
MRS data - Configure it based on the actual condition.
Protocol data - Configure it based on the actual condition.
Signaling data MTP DSP index Configure a unique range of MTP DSP indexes for
each SoftX3000. For example, set the MTP DSP
indexes of office A to range from 0 to 127, and those
M3UA destination Configure a unique range of M3UA destination

entity index entity indexes for each SoftX3000. For example, set
the M3UA destination entity indexes of office A to
range from 0 to 127, and those of office B to range
from 128 to 255.
SCCP DSP index Configure a unique range of SCCP DSP indexes for
each SoftX3000. For example, set the SCCP DSP
indexes of office A to range from 0 to 127, and those
SCCP subsystem Configure a unique range of SCCP subsystem

index indexes for each SoftX3000. For example, set the
SCCP subsystem indexes of office A to range from
0 to 127, and those of office B to range from 128 to
255.
ISDN index To simplify data configuration, you are advised to

configure the same ISDN index for the two
SoftX3000s.
(Built-in) SG ID Configure a unique range of SG IDs for each

SoftX3000. For example, set the SG IDs of office A
to range from 0 to 127, and those of office B to range
from 128 to 255.

Linkset number Configure a unique range of MTP, M3UA, V5UA,

and IUA Linkset numbers for each SoftX3000. For
example, set the MTP Linkset numbers of office A
from 128 to 255.
Link number Configure a unique range of MTP, M2UA, M3UA,

V5UA, and IUA link numbers for each SoftX3000.
For example, set the MTP link numbers of office A
from 16 to 31.
Routing data Office direction Configure the same office direction number for the
number two SoftX3000s. That is, the two SoftX3000s have
the same office direction number for the same
destination, but have different office direction
numbers for different destinations.
Sub-route number Configure a unique range of subroute numbers for

each SoftX3000. For example, set the subroute
numbers of office A to range from 0 to 127, and
those of office B to range from 128 to 255.
Route number Configure a unique range of route numbers for each

SoftX3000. For example, set the route numbers of
office A to range from 0 to 127, and those of office
B to range from 128 to 255.
Route selection code Configure a unique range of route selection codes

for each SoftX3000. For example, set the route
selection codes of office A to range from 0 to 127,
and those of office B to range from 128 to 255.
Subscriber - Configure it based on the actual condition.

data
Trunk data Trunk group number Configure a unique range of trunk group numbers
for each SoftX3000. For example, set the trunk
group numbers of office A to range from 0 to 99,
Number Number change To simplify data configuration, you are advised to

analysis data index configure the same number change index for the two
SoftX3000s.
Call prefix The local DN sets have been configured globally.

Therefore, configure call prefixes based on the
actual condition.
Centrex data Centrex group Configure a unique range of Centrex group numbers
number for each SoftX3000. For example, set the Centrex
group numbers of office A to range from 0 to 999,

IP console number Configure a unique range of IP console numbers for

each SoftX3000. For example, set the IP console
numbers of office A to range from 0 to 4999, and
those of office B to range from 5000 to 9999.
Call barring Caller discrimination Configure a unique range of caller discrimination

data group number group numbers for each SoftX3000. For example,
set the caller discrimination group numbers of office
A to range from 0 to 127, and those of office B to
range from 128 to 255.
Call barring group Configure a unique range of call barring group

number numbers for each SoftX3000. For example, set the
call barring group numbers of office A to range from
0 to 127, and those of office B to range from 128 to
255.
IN service IN charging data To simplify data configuration, you are advised to

data configure the same IN charging data for the two
SoftX3000s, including the charging discount and
charging category.
IN announcement To simplify data configuration, you are advised to

data configure the same IN announcement data for the
two SoftX3000s, including the language bit,
language kind, and currency.
SCP number Configure it based on the actual condition.
Other data - Configure it based on the actual condition.
Documents
Before configuring the dual homing data, you must plan the related data based on the
Workflow
The procedure for configuring the dual homing data is as follows:
1. Configure data for office A.
(1) Configure hardware data for office A.
(2) Configure hardware data (office A).
(3) Configure dual homing data (office A).
(4) Configure charging data (office A).
(5) Configure data for interworking with IAD (office A).
(6) Configure data for interworking with AMG (office A).
(7) Configure data for interworking with UMG (office A).

(8) Configure multimedia subscriber data (office A).

(9) Configure data for interworking with PSTN (office A).
(10) Configure routing data for interworking with mutual aid office B (office A).
2. Configure data for office B.
(1) Configure hardware data for office B.
(2) Configure hardware data (office B).
(3) Configure dual homing data (office B).
(4) Configure charging data (office B).
(5) Configure data for interworking with IAD (office B).
(6) Configure data for interworking with AMG (office B).
(7) Configure data for interworking with UMG (office B).
(8) Configure multimedia subscriber data (office B).
(9) Configure data for interworking with PSTN (office B).
(10) Configure routing data for interworking with mutual aid office B (office B).
Procedure
Step 1 Configure hardware data (office A).
//Add two shelves numbered 0 and 1 respectively.
ADD SHF: SHN=0, LT="SoftX3000", ZN=0, RN=0, CN=0;
//Add two basic frames numbered 0 and 5 respectively.

NOTE
l To ensure the reliability of dual homing heartbeat links, configure two basic frames and a pair of IFMI
boards in each frame.
l If the SoftX3000 is equipped with only one pair of IFMIs, you still need to configure two pairs of IFMIs
when you configure data. In this way, the dual homing solution in load sharing mode can be carried
out.
//Add two pairs of IFMIs. One pair is located in basic frame 0 and the other pair in basic frame
5.
ADD BRD: FN=0, SN=0, LOC=FRONT, BT=IFMI, MN=132, ASS=1;
//Add FE port configurations.

DGW="191.169.150.60", EA=FH;
DGW="191.169.150.60", EA=FH;
Step 2 Configure dual homing data (office A).

//Set the dual homing work mode. Set Work mode to Assistant and Switch mode to Manual
for the local SoftX3000.

NOTE
To set Switch mode to Automatic for the SoftX3000 in office A, perform the following steps:
l Run SET DHWM to set Work mode to Assistant and Switch mode to Manual for the SoftX3000
in office A.
l Run SET DHWM to set Work mode to Assistant and Switch mode to Automatic for the SoftX3000
in office A.
//Add two dual homing heartbeat links. The IP addresses of the two IFMIs in the mutual aid
office B are 191.169.150.40 and 191.169.150.41 respectively.
NOTE
The automatic switchover mode is adopted between the SoftX3000 in office A and the SoftX3000 in the
mutual aid office B. Therefore, when both SoftX3000s are equipped with two pairs of IFMIs, configure
two heartbeat links between the two SoftX3000s to ensure the reliability of heartbeat signals.
//Set the dual homing work mode.

NOTE
The preceding command means that the work mode of the SoftX3000 in office A is Assistant, the
switchover mode is Automatic, the takeover mode is SELECT ALL, and the handshake time is 30 x 5 =
150 seconds.The dual homing work mode is usually configured as follows: The work mode of the local
SoftX3000 is set to Assistant, the switchover mode is set to Automatic, and the takeover mode is set to
Deactivated enable.
Step 3 Configure local office data (office A).

//Set the SPC of the local office A to 001122 (national network).
SET OFI: OFN="SoftX3000_A", LOT=CMPX, NN=YES, SN1=NAT, SN2=NAT, SN3=NAT,
//Add the SPC of the mutual aid office B, with the OPC index being 1 and OPC being 001133
(national network).
ADD OFI: IDX=1, OPC="001133", MSF=SLAVER;
NOTE
l To achieve mutual aid between MTP links and M3UA links, run ADD OFI to add the SPC of the
mutual aid office in the local office.
l Master/Slave flag in ADD OFI must be set to SLAVE.
//Modify information about office A. Set the two original SPCs as mutual assistant nodes.
MOD OFI: ID=0, PA1=NN, PAC1="001133";
NOTE
l The setting of the signaling network where the assistant node resides must be consistent with that of
the signaling network where the served node resides. Otherwise, this piece of data is regarded as invalid.
l In the preceding commands, the assistance is unidirectional. If both the original SPCs are set as mutual
assistant nodes, run MOD OFI to configure two pieces of data.
//Add two local DN sets. Set the DN set of the local office A to 0 and that of the mutual aid
office B to 10.

ADD LDNSET: LP=0, NC=K'86, AC=K'755, LDN="ShenZhen", DGMAPIDX=0,

MDGMAPIDX=0;
ADD LDNSET: LP=10, NC=K'86, AC=K'756, LDN="ZHUHAI", DGMAPIDX=0,
MDGMAPIDX=0, MSTYPE=SLAVE;
//Add call sources. Set the call source code of office A to 0 and that of the mutual aid office B
to 10.
ADD CALLSRC: CSC=0, CSCNAME="Office_A", PRDN=3, LP=0, RSSC=0, FSC=0;
ADD CALLSRC: CSC=10, CSCNAME="Office_B", PRDN=3, LP=10, RSSC=10, FSC=10;
NOTE
According to the principle for configuring the local office data, the call source code, route selection source
code and failure source code of office A must be different from those of the mutual aid office B.
Step 4 Configure charging data (office A).

//Add charging cases 0, 10 and 20. Charging case 0 adopts the detailed ticket and is used for
destination code charging. Charging cases 10 and 20 adopt the meter table and are used for intra-
office group charging.
ADD CHGANA: CHA=0, CRM=TNSO;
ADD CHGANA: CHA=10, CHGT=PLSACC, CRM=TNSO;
ADD CHGANA: CHA=20, CHGT=PLSACC, MID=METER2, CRM=TNSO;
//Modify charging modes.

PB1=1, AGIO1=60, TS2=07&00, TA2="6", PA2=1, TB2="6", PB2=1, AGIO2=60,
TS3=21&00, TA3="6", PA3=1, TB3="6", PB3=1, AGIO3=100;
MOD CHGMODE: CHA=0, DAT=DTYPE1, TS1=00&00, TA1="6", PA1=1, TB1="6",
TS3=21&00, TA3="6", PA3=1, TB3="6", PB3=1, AGIO3=100;
PB1=1, AGIO1=60, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
//Add intra-office group charging data.

ADD CHGGRP: RCHS=65, DCHS=65, LOAD=ALL, CODEC=ALL, CHA=10;
//Add destination code charging data. Both the caller charging source codes 65 and 87 are used
for destination code charging.
ADD CHGIDX: CHSC=0, RCHS=65, LOAD=ALL, CODEC=ALL, CHA=0;
//Add destination code charging data. The caller charging source code 88 is used for the
destination code charging of incoming trunk groups, and the caller charging source code 99 is
used for the destination code charging of outgoing trunk groups.


Step 5 Configure data for interworking with IAD (office A).

//Add two IADs using MGCP, with the equipment ID of the IAD in office A being shenzhen-
iad104-2.com and that in the mutual aid office B being zhuhai-iad104-2.com.
RA1="211.169.150.21", RP=2427, LISTOFCODEC=PCMA-1&PCMU-1&G7231-1&G729-1,
UCATT=NOFX-0&NOM-0, ET=NO;
ADD MGW: EID="zhuhai-iad104-2.com", GWTP=IAD, MGWDESC="zhuhai-iad104-20",
MSTYPE=SLAVE, ET=NO;
NOTE
l In the preceding commands, Local IP address must be set to the IP address of the IFMI of the local
office, whereas Remote IP address must be set based on the actual condition.
l You must set Master/slave type correctly.
//Add eight ESL subscribers. 6540001-6540004 are subscribers in office A, and

8780001-8780004 are subscribers in the mutual aid office B.
ADB VSBR: SD=K'6540001, ED=K'6540004, LP=0, MN=22, DID=ESL, EID="shenzhen-
iad104-2.com", STID=1, CODEC=PCMA, RCHS=65, CSC=0, NS=CLIP-1, CNTRX=NO,
ADB VSBR: SD=K'8780001, ED=K'8780004, LP=10, MN=22, DID=ESL, EID="zhuhai-
NOTE
l In the preceding commands, parameters such as Local DN set, Call source code, Charging source
code and parameters related to subscriber attributes must be set correctly.
l When configuring subscriber data, specify Equipment ID of the corresponding MGW for the
subscriber. This MGW data is marked with Master/Slave type. Therefore, the corresponding
subscriber data also contains Master/Slave type.
//Add an intra-office call prefix for office A. Set Local DN set to 0, Call prefix to 654 and
Service attribute to Intra-office.
ADD CNACLD: PFX=K'654, CSTP=BASE, MINL=7, MAXL=7, CHSC=65535,
SDESCRIPTION="Office_654", EA=NO;
//Add an intra-office call prefix for the mutual aid office B. Set Local DN set to 10, Call
prefix to 878 and Service attribute to Intra-office.
ADD CNACLD: LP=10, PFX=K'878, CSTP=BASE, MINL=7, MAXL=7, CHSC=65535,
Step 6 Configure data for interworking with AMG (office A).

//Add two AMGs using MGCP, with the equipment ID of the AMG in office A being shenzhen-
amg5000-2.com and that in the mutual aid office B being zhuhai-amg5000-2.com.
RA1="211.169.150.51", RP=2427,
UCATT=NOFX-0&NOM-0&V3FX-1, ET=NO;
ADD MGW: EID="zhuhai-amg5000-2.com", GWTP=AG, MGWDESC="zhuhai-amg5000-2",


RP=2427, LISTOFCODEC=PCMA-1&PCMU-1&G7231-1&G729-1&T38-1, HAIRPIN=NS,
UCATT=NOFX-0&NOM-0&V3FX-1, MSTYPE=SLAVE, ET=NO;
//Add 64 ESL subscribers. 6540100-6540131 are subscribers in office A, and 8780100-8780131

are subscribers in the mutual aid office B.
amg5000-2.com", STID=0, CODEC=PCMA, RCHS=65, CSC=0, NS=CLIP-1, CNTRX=NO,
amg5000-2.com", STID=0, CODEC=PCMA, RCHS=87, CSC=10, NS=CLIP-1, CNTRX=NO,
Step 7 Configure data for interworking with UMG (Office A).
//Add two UMG8900s. Set the equipment ID of the UMG8900 in office A to

211.169.150.89:2944, and that of the UMG8900 in the mutual aid office B to
221.169.150.99:2944.
ADD MGW: EID="221.169.150.99:2944", GWTP=UMGW, MGWDESC="zhuhai-
CODETYPE=ASN, MSTYPE=SLAVE, ET=NO;
//Add 64 ESL subscribers. 6540200-6540231 are subscribers in office A, and 8780200-8780231

ADB VSBR: SD=K'6540200, ED=K'6540231, LP=0, MN=22, DID=ESL,
EID="211.169.150.89:2944", STID=0, CODEC=PCMA, RCHS=65, CSC=0, NS=CLIP-1,
CNTRX=NO, PBX=NO, CHG=NO, ENH=NO;
EID="221.169.150.99:2944", STID=0, CODEC=PCMA, RCHS=87, CSC=10,
NS=CLIP-1, CNTRX=NO, PBX=NO, CHG=NO, ENH=NO;
//Add two SGs (built in the UMG8900), with the SG ID of office A being 0 and that of the mutual
aid office B being 128.
ADD SG: SGID=128, SGNAME="IUA SG", SGTYPE=emb, EID="221.169.150.99:2944",
MSTYPE=SLAVE;
NOTE
According to the principle for configuring signaling data, the built-in-SG ID of the local office must be
different from that of the mutual aid office.
//Add two IUA Linksets. Set the Linkset index of office A to 0 and that of the mutual aid office
B to 128.
ADD IUALKS: LSX=0, LSNAME="IUA LinkSet 0", DT=BRA, MN=22, SGID=0;
NOTE
According to the principle for configuring signaling data, the IUA Linkset index of the local office must
be different from that of the mutual aid office.
//Add four IUA links. Set the IUA links of office A to link 0 of BSGI 136 and link 0 of BSGI
137. Set the IUA links of the mutual aid office B to link 8 of BSGI 136 and link 8 of BSGI 137.


PEERIP1="211.169.150.17";
PEERIP1="211.169.150.17";
ADD IUALNK: MN=136, LNKN=8, LSX=128, LOCPORT=9900,
LOCIP1="191.169.150.30", PEERIP1="221.169.150.27", ASF=STANDBY;
NOTE
l According to the principle for configuring signaling data, the IUA link numbers of the local office must
be different from those of the mutual aid office.
office, whereas Peer IP address must be set based on the actual condition. In this example, Peer IP
address is the IP address of the UMG8900 used in the SIGTRAN protocol.
//Add ISDN data. Set Index to 1 and Maximum B channel to 2.

ADD ISDNDAT: ISDNX=1, BCHN=2;
//Add 64 BRA subscribers. 6540300-6540331 are subscribers in office A, and 8780300-8780331

ADB BRA: LP=0, SD=K'6540300, ED=K'6540331, DID=BRA,
EID="211.169.150.89:2944", STID="32", LKS=0, SIID=10000, ISDN=1,
ISA=MSN-1, CSC=0, RCHS=65, NS=CLIP-1, CUGU=NO, CTX=YES, PBX=YES, CHR=YES;
NOTE
Step 8 Configure multimedia subscriber data (Office A).

//Add two multimedia devices using SIP, with the equipment ID of the device in office A being
6540401 and that in the mutual aid office B being 8780401.
ADD MMTE: EID="6540401", MN=22, IMSFLAG=NO, IFMMN=132, AT=ABE, PT=SIP,
PASS="112233";
PASS="223344", MSTYPE=SLAVE;
//Add two SIP subscribers. 6540401 is a SIP subscriber in office A, and 8780401 is a SIP
subscriber in the mutual aid office B.
Step 9 Configure data for interworking with PSTN (Office A).

//Add two TMG8010s. Set the equipment ID of the TMG8010 in office A to
211.169.150.81:2944, that of the TMG8010 in the mutual aid office B to 221.169.150.91:2944,
and the FCCU module number to 23.
ADD MGW: EID="211.169.150.81:2944", GWTP=TG, MGWDESC="Shenzhen-
TMG8010-2", MGCMODULENO=23, LA="191.169.150.30", RA1="191.169.150.81",


ET=NO;
ADD MGW: EID="221.169.150.91:2944", GWTP=TG, MGWDESC="Zhuhai-TMG8010-2",
LISTOFCODEC=PCMA-1&PCMU-1&G7321-1&G729-1&T38-1, HAIRPIN=S, MSTYPE=SLAVE,
ET=NO;
//Add two SGs (built in the TMG8010), with the SG ID of office A being 1 and that of the mutual
aid office B being 129.
ADD SG: SGID=1, SGNAME="M2UA SG", SGTYPE=emb, EID="211.169.150.81:2944";
ADD SG: SGID=129, SGNAME="M2UA SG", SGTYPE=emb,
EID="221.169.150.91:2944", MSTYPE=SLAVE;
NOTE
//Add four M2UA Linksets. Set M2UA Linkset indexes to 0, 1, 129, and 130. Set Interface ID
type to Integer.
ADD M2LKS: M2LSX=0, LSNAME="M2UA LinkSet 0", SGID=1;
//Add four M2UA links. Set the M2UA links of office A to link 0 of BSGI 136 and link 0 of
BSGI 137. Set the M2UA links of the mutual aid office B to link 8 of BSGI 136 and link 8 of
BSGI 137.
LOCIP1="191.169.150.30", PEERIP1="211.169.150.81";
LOCIP1="191.169.150.30", PEERIP1="211.169.150.81";
NOTE
l According to the principle for configuring signaling data, the M2UA link numbers of the local office
must be different from those of the mutual aid office.
office, whereas Peer IP address must be set based on the actual condition.
//Add two MTP DSPs. The DPC is 1100bb. The OPC mapping DSP index 0 is 001122 (SPC of
office A). The OPC mapping DSP index 128 is 001133 (SPC of the mutual aid office B).
ADD N7DSP: DPX=0, DPC="1100bb", OPC="001122", DPNAME="A to PSTN";
ADD N7DSP: DPX=128, DPC="1100bb", OPC="001133", DPNAME="B to PSTN";
NOTE
According to the principle for configuring signaling data, the DSP indexes of the local office must be
different from those of the mutual aid office.
//Add two MTP Linksets. Set Linkset index to 0 and Adjacent DSP index to 0 for office A.
Set Linkset index to 128 and Adjacent DSP index to 128 for the mutual aid office B.
ADD N7LKS: LSX=0, ASPX=0, LSNAME="A to PSTN";
ADD N7LKS: LSX=128, ASPX=128, LSNAME="B to PSTN";

NOTE
According to the principle for configuring signaling data, the MTP Linkset indexes of the local office must
//Add four MTP links. Set the MTP links of office A to link 0 of BSGI 136 and link 0 of BSGI
137. Set the MTP links of the mutual aid office B to link 8 of BSGI 136 and link 8 of BSGI 137.
ADD N7LNK: MN=136, LNKN=0, LNKNAME="A to PSTN", LNKTYPE=M64K, M2LSX=0,
ADD N7LNK: MN=136, LNKN=8, LNKNAME="B to PSTN", LNKTYPE=M64K, M2LSX=129,
NOTE
l According to the principle for configuring signaling data, the MTP link numbers of the local office
l In the preceding example, Master/Slave type of the MTP links must be set to the same value as that
of the corresponding M2UA links.
//Add MTP routes destined for the PSTN switch. For the MTP links from office A to the PSTN
switch, set Linkset index to 0 and DSP index to 0. For the MTP links from the mutual aid office
B to the PSTN switch, set Linkset index to 128 and DSP index to 128.
ADD N7RT: LSX=0, DPX=0, RTNAME="A to PSTN";
ADD N7RT: LSX=128, DPX=128, RTNAME="B to PSTN";
//Add an office direction destined for the PSTN switch, with the office direction number being
0 and DPC being 1100bb.
ADD OFC: O=0, ON="To PSTN", DOT=CMPX, DOL=LOW, DPC1="1100bb";
NOTE
According to the principle for configuring routing data, you need to add only one office direction. This is
because the PSTN switch is the destination for both the local office and the mutual aid office.
//Add two subroutes. Set the number of the subroute from office A to the PSTN switch to 0 and
that of the subroute from the mutual aid office B to the PSTN switch to 128.
ADD SRT: SRC=0, O=0, SRN="A to PSTN", RENT=URT;
ADD SRT: SRC=128, O=0, SRN="B to PSTN", RENT=URT;
//Add two routes. Set the number of the route from office A to the PSTN switch to 0 and that of
the route from the mutual aid office B to the PSTN switch to 128.
ADD RT: R=0, RN="A to PSTN ", SRST=SEQ, SR1=0, SR2=128;
ADD RT: R=128, RN="B to PSTN ", SRST=SEQ, SR1=128, SR2=0;
NOTE
In the preceding commands, the direct and alternate subroutes from office A to the PSTN switch are
numbered 0 and 128; those from the mutual aid office B to the PSTN switch are numbered 128 and 0.
//Add analysis data of the route destined for the PSTN switch. For the route from office A to the
PSTN switch, set the route selection code to 22 and the route number to 0. For the route from
the mutual aid office B to the PSTN switch, set the route selection code to 33 and the route
number to 128.
ISUP=NOCHG, NCAI=ALL, CST=ALL, CNPI=ALL;

ADD RTANA: RSC=33, RSSC=0, RUT=ALL, SAI=ALL, CLR=ALL, TP=ALL, TMX=0,

R=128, ISUP=NOCHG, NCAI=ALL, CST=ALL, CNPI=ALL;
//Add SS7 trunk groups, with the trunk groups from office A to the PSTN switch numbered 0
and 1, and the trunk groups from the mutual aid office B to the PSTN switch numbered 100 and
101.
TGN="A to PSTN", CSC=0, RCHS=88, OTCS=99, PRTFLG=CN, NOAA=FALSE,
ISM=FALSE, EA=FALSE;
SOPC="001122", TGN="B to PSTN", CSC=10, RCHS=88, OTCS=99, PRTFLG=CN,
NOAA=FALSE, ISM=FALSE, EA=TRUE, CCT=DEC, CCV=32;
ADD N7TG: TG=101, EID="221.169.150.91:2944", G=IN, SRC=128,
NOTE
l According to the principle for configuring trunk data, the trunk group numbers of the local office must
l To enable the SS7 trunk groups to use the correct number analysis data table for incoming calls, set
Call source code correctly. In the example, the call source codes of trunk groups 0 and 1 are set to 0,
and the call source codes of trunk groups 100 and 101 are set to 10.
l In the example, if it is required to perform CIC conversion on trunk groups 100 and 101, set CIC
change type to Decrease and CIC change value to 32. CIC change type and CIC change value are
used for the self-loop test of the two SS7 trunk groups (outgoing trunk E1 and incoming trunk E1)
between the local office and the same office direction.

ADD N7TKC: MN=23, TG=0, SC=0, EC=31, SCIC=0, SCF=FALSE, TID="0";
NOTE
l If the SS7 trunk circuits of both the local office and the mutual aid office are connected to the same
FCCU, the circuit number range and the CIC code of each trunk group must be set globally.
l For the circuit number range, set Start circuit termination ID correctly by running ADD N7TKC.
This enables the SoftX3000 to interwork with the PSTN switch.
l For the CIC code, you may need to change the CIC code of the corresponding SS7 trunk group by
running MOD N7TG. This enables the SoftX3000 to interwork with the PSTN switch.
//Add a toll prefix for toll calls from the local office to the PSTN switch. Set Local DN set to
0, Call prefix to 0, Service attribute to National toll, and Route selection code to 22.
CHSC=0, SDESCRIPTION="Toll call", EA=NO;
//Add a toll prefix for toll calls from the mutual aid office B to the PSTN switch. Set Local DN
set to 10, Call prefix to 0, Service attribute to National toll, and Route selection code to 33.
Step 10 Configure routing data for interworking with mutual-aid office B (office A).

NOTE
l In a network, if a standby SoftX3000 is configured for office A and office B respectively, perform the
data configuration according to the routing method 1.
l In a network, if no standby SoftX3000 is configured for office A and office B, perform the data
configuration according to the routing method 2.
Configuring routing data for interworking with mutual-aid office B (mode one)
//Add three office directions numbered 101, 11 and 12 respectively.
ADD OFC: O=101, ON="B_Signal_office", DOT=NATT, DOL=SAME;
ADD OFC: O=11, ON="B_Dual_office", DOT=NATT, DOL=SAME;
ADD OFC: O=12, ON="A_Dual_office", DOT=NATT, DOL=SAME;
NOTE
According to the principle for configuring routing data, configure three office directions for the
interworking between the local office and the mutual aid office:
l The office direction numbered 101 is the mutual aid office before the dual homing switchover, that is,
the mutual aid office B in normal conditions.
l The office direction numbered 11 is the mutual aid office after the dual homing switchover, that is, the
virtual mutual aid office B in office A.
l The office direction numbered 12 is the mutual aid office after the dual homing switchover, that is,
office A in the virtual mutual aid office B.
//Add three subroutes numbered 10, 11 and 12 respectively.

ADD SRT: SRC=10, O=101, SRN="A to B_0", RENT=URT;
ADD SRT: SRC=12, O=12, SRN="B to A", RENT=URT;
NOTE
The subroutes correspond to the three preceding office directions:

l The subroute numbered 10 is the subroute from office A to the mutual aid office B before the dual
homing switchover.
l The subroute numbered 11 is the subroute from office A to the virtual mutual aid office B after the
dual homing switchover. Set the SIP trunk group contained in this subroute as the self-loop trunk group
of office A.
l The subroute numbered 12 is the subroute from the virtual mutual aid office B to office A after the
of office A.
//Add two routes numbered 10 and 12 respectively.

ADD RT: R=10, RN="To B_office", SRST=SEQ, SR1=10, SR2=11;
ADD RT: R=12, RN="To A_office", SRST=SEQ, SR1=12;
NOTE
l Route 10 is the route from office A to the mutual aid office B. You must configure two subroutes for
it: subroute 10 is the direct subroute, and subroute 11 is the alternate subroute.
l Route 12 is the route from the virtual mutual aid office to the office A. You need to configure only one
subroute for it.
//Add route analysis data. For the route from office A to the mutual aid office B, set the route
selection code to 87 and the route number to 10. For the route from the virtual mutual aid office
B to office A, set the route selection code to 65 and the route number to 12.
ISUP=SIP_M, NCAI=ALL, CST=ALL, CNPI=ALL;
R=12, ISUP=SIP_M, NCAI=ALL, CST=ALL, CNPI=ALL;

//Add three SIP trunk groups.

ADD SIPTG: TG=101, CSC=0, SRT=10, TGN=" A to B_0", RCHS=88, OTCS=99,
HCIC=2000, LCIC=1800, NOAA=NO, EA=YES, UHB=NORMAL, VIDEOS=SUPPORT,
CHBF=NO, E2833F=NSUPPORT, SELMODE=DIST;
ADD SIPTG: TG=11, CSC=0, SRT=11, TGN=" A to B ", RCHS=88, OTCS=99,
ADD SIPTG: TG=12, CSC=10, SRT=12, TGN="B to A_1", RCHS=88, OTCS=99,
//Add IP address pair data of the SIP trunk.

NOTE
l To enable the SoftX3000 to detect the working state of SIP trunks correctly, set Use Heartbeat to
Yes. Otherwise, the SoftX3000 cannot use the alternate subroute.
l To enable the SIP trunk groups to use the correct number analysis data table for incoming calls, set
Call source code correctly. In the example, the call source codes of trunk groups 101 and 11 are set
to 0, and the call source code of trunk group 12 is set to 10.
l SIP trunk groups 11 and 12 must be configured as the self-loop trunk groups of the office A. Therefore,
their source and destination IP addresses must be the IP addresses of the IFMIs in office A and the
addresses must be crossly set. As shown in the given example, the source IP address of trunk group 11
is 191.169.150.30 (the module number of the IFMI is 132), and its destination IP address is
191.169.150.31. The source IP address of trunk group 12 is 191.169.150.31 (the module number of the
IFMI is 133), and its destination IP address is 191.169.150.30.
//Add an outgoing prefix for the calls from office A to the mutual aid office B. Set Local DN
set to 0, Call prefix to 878, Service attribute to Local, and Route selection code to 87.
CHSC=65535, SDESCRIPTION="Office_878", EA=NO;
NOTE
From the previous routing data configuring, it can be inferred that:

l Before the dual homing switchover, when an office A subscriber dials the prefix 878, the system selects
the normal subroute from office A to the mutual aid office B.
l After the dual homing switchover, when an office A subscriber dials the prefix 878, the system selects
the subroute from office A to the virtual mutual aid office B (that is, the self-loop subroute of office
A).
Thus, the call attribute and charging attribute of the office A prefix 878 are not changed before and after
the dual homing switchover.
//Add an outgoing prefix for the calls from the mutual aid office B to office A. Set Local DN
NOTE
After the dual homing switchover, when a subscriber in the mutual aid office B dials the prefix 654, the
system selects the subroute from the virtual mutual aid office B to office A (that is, the self-loop subroute
of office A). Thus, the call attribute and charging attribute of the prefix 654 in the virtual mutual aid office
B and the mutual aid office B are not changed before and after the dual homing switchover.
Configuring routing data for interworking with mutual-aid office B (mode two)

When routing data for interworking between office A and the mutual aid office B is configured
in mode one, three office directions and three SIP trunk groups must be configured in office A.
The first trunk group is that from office A to B before dual-homing switchover. The second trunk
group is the self-loop trunk group from office A to B after dual-homing switchover. The third
trunk group is the self-loop trunk group from office B to A after dual-homing switchover. The
first and second trunk groups have the same call attributes. You must, however, configure two
office directions and two subroutes. The service data configured for one trunk group must also
be configured for the other. As a result, maintenance is difficult. In mode two, however, only
one self-loop trunk group is configured.
//Add an office direction. Set Office direction number to 101.
ADD OFC: O=101, ON="B_Signal_office", DOT=NATT, DOL=SAME;
NOTE
101 is the office direction number of office B before and after dual-homing switchover.
//Add a subroute. Set Sub-route number to 10.

NOTE
10 is the number of the subroute from office A to office B before and after dual-homing switchover.
//Add a route. Set Route number to 10.

ADD RT: R=10, RN="To B_office", SRST=SEQ, SR1=10, TRIPFLAG=NO;
NOTE
10 is the number of the route from office A to office B before and after dual-homing switchover.
//Add route analysis data. Set Route selection code to 87 and Route number to 10 for the route
from office A to the mutual aid office B.
ISUP=SIP_F, NCAI=ALL, CST=ALL, CNPI=ALL;
//Add an outgoing prefix for the calls from office A to office B. Set Local DN set to 0, Call
prefix to 878, Service attribute to Local, and Route selection code to 87.
ADD CNACLD: LP=0, PFX=K'878, CSA=LC, RSC=87, MINL=7, MAXL=7, CHSC=65535,
//Add the trunk group from office A to office B.

ADD SIPTG: TG=101, CSC=0, SRT=10, TGN=" A to B_0", RCHS=88, OTCS=99,
//Add the trunk group IP address pair.

ADD SIPIPPAIR: TG=101, IMN=132, LSRVP=5060, OSU="191.169.150.40:5060",
DH=Yes, DHOSU="191.169.150.30:5060"
NOTE
When configuring the IP address pair for the trunk group from office A to office B, set Trunk group
number to 101, Remote URI 1 to the IP address and port number of office B, that is,
191.169.150.40:5060, and DH Remote URI to the IP address and port number of office A, that is,
191.169.150.30:5060.
Step 11 Configure hardware data (office A).

//Add two shelves numbered 0 and 1 respectively.


//Add two basic frames numbered 0 and 5 respectively.

NOTE
l To ensure the reliability of dual homing heartbeat links, configure two basic frames and a pair of IFMI
boards in each frame.
l If the SoftX3000 is equipped with only one pair of IFMIs, you still need to configure two pairs of IFMIs
when you configure data. In this way, the dual homing solution in load sharing mode can be carried
out.
//Add two pairs of IFMIs. One pair is located in basic frame 0 and the other pair in basic frame
5.
//Add FE port configurations.

DGW="191.169.150.60", EA=FH;
DGW="191.169.150.60", EA=FH;
Step 12 Configure dual homing data (office B).
//Set the dual homing work mode. Set Work mode to Assistant and Switch mode to Manual
for the SoftX3000 in office B.
NOTE
To set Switch mode to Automatic for the SoftX3000 in office B, perform the following steps:
l Run SET DHWM to set Work mode to Assistant and Switch mode to Manual for the SoftX3000
in office A.
l Run SET DHWM to set Work mode to Assistant and Switch mode to Automatic for the SoftX3000
in office B.
//Add two dual homing heartbeat links. The IP addresses of the two IFMIs in the mutual aid
office A are 191.169.150.30 and 191.169.150.31 respectively.
NOTE
The automatic switchover mode is adopted between the SoftX3000 in office B and the SoftX3000 in the
mutual aid office A. Therefore, when both SoftX3000s are equipped with two pairs of IFMIs, configure
two heartbeat links between the two SoftX3000s to ensure the reliability of heartbeat signals.
//Set the dual homing work mode.


NOTE
The preceding command means that the work mode of the SoftX3000 in office B is Assistant, the
switchover mode is Automatic, the takeover mode is SELECT ALL, and the handshake time is 30 x 5 =
150 seconds.
Step 13 Configure local office data (office B).
//Set the SPC of the local office B to 001133 (national network).

SET OFI: OFN="SoftX3000_B", LOT=CMPX, NN=YES, SN1=NAT, SN2=NAT, SN3=NAT,
//Add the SPC of the mutual aid office A, with the OPC index being 1 and OPC being 001122
(national network).
ADD OFI: IDX=1, OPC="001122", MSF=SLAVER;
NOTE
l To achieve mutual aid between MTP links and M3UA links, run ADD OFI to add the SPC of the
mutual aid office in the local office.
l Master/Slave flag in ADD OFI must be set to SLAVE.
//Modify information about office B. Set the two original SPCs as mutual assistant nodes.
//Modify information about office B. Set the two original SPCs as mutual assistant nodes.
NOTE
//Add two local DN sets. Set the DN set of the local office B to 10 and that of the mutual aid
office A to 0.
ADD LDNSET: LP=10, NC=K'86, AC=K'756, LDN="ZHUHAI", DGMAPIDX=0,
MDGMAPIDX=0;
ADD LDNSET: LP=0, NC=K'86, AC=K'755, LDN="SHENZHEN", DGMAPIDX=0,
MDGMAPIDX=0, MSTYPE=SLAVE;
//Add call sources. Set the call source code of office B to 10 and that of the mutual aid office A
to 0.
ADD CALLSRC: CSC=10, CSCNAME="Office_B", PRDN=3, LP=10, RSSC=10, FSC=10;
ADD CALLSRC: CSC=0, CSCNAME="Office_A", PRDN=3;
NOTE
According to the principle for configuring the local office data, the call source code, route selection source
code and failure source code of office B must be different from those of the mutual aid office A.
Step 14 Configure charging data (office B).
//Add charging cases 0, 10 and 20. Charging case 0 adopts the detailed ticket and is used for
destination code charging. Charging cases 10 and 20 adopt the meter table and are used for intra-
office group charging.

ADD CHGANA: CHA=0, CRM=TNSO;


TS3=21&00, TA3="6", PA3=1, TB3="6", PB3=1, AGIO3=100;
TS3=21&00, TA3="6", PA3=1, TB3="6", PB3=1, AGIO3=100;
PB1=1, AGIO1=60, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;MOD CHGMODE: CHA=20, DAT=DTYPE2, TS1=00&00,
TA1="60", PA1=1, TB1="60", PB1=1, AGIO1=100, TS2=00&00;
//Add intra-office group charging data.

//Add destination code charging data. Both the caller charging source codes 65 and 87 are used
for destination code charging.
//Add destination code charging data. The caller charging source code 88 is used for the
destination code charging of incoming trunk groups, and the caller charging source code 99 is
used for the destination code charging of outgoing trunk groups.
Step 15 Configure data for interworking with IAD (office B).

//Add two IADs using MGCP, with the equipment ID of the IAD in office B being zhuhai-
iad104-2.com and that in the mutual aid office A being shenzhen-iad104-2.com.
ADD MGW: EID="zhuhai-iad104-2.com", GWTP=IAD, MGWDESC="zhuhai-iad104-20",
ET=NO;
RA1="211.169.150.21", RP=2427, LISTOFCODEC=PCMA-1&PCMU-1&G7231-1&G729-1,
UCATT=NOFX-0&NOM-0, MSTYPE=SLAVE, ET=NO;

NOTE
office, whereas Remote IP address must be set based on the actual condition.
//Add eight ESL subscribers. 8780001-8780004 are subscribers in office B, and

6540001-6540004 are subscribers in the mutual aid office A.
NOTE
//Add an intra-office call prefix for office B. Set Local DN set to 10, Call prefix to 878 and
Service attribute to Intra-office.
ADD CNACLD: LP=10, PFX=K'878, CSA=LCO, MINL=7, MAXL=7, CHSC=65535,
//Add an intra-office call prefix for the mutual aid office A. Set Local DN set to 0, Call
prefix to 654 and Service attribute to Intra-office.
Step 16 Configure data for interworking with AMG (office B).

//Add two AMGs using MGCP, with the equipment ID of the AMG in office B being zhuhai-
amg5000-2.com and that in the mutual aid office A being shenzhen-amg5000-2.com.
ADD MGW: EID="zhuhai-amg5000-2.com", GWTP=AG, MGWDESC="zhuhai-amg5000-2",
RP=2427, LISTOFCODEC=PCMA-1&PCMU-1&G7231-1&G729-1&T38-1, HAIRPIN=NS,
UCATT=NOFX-0&NOM-0&V3FX-1, ET=NO;
RA1="211.169.150.51", RP=2427,
UCATT=NOFX-0&NOM-0&V3FX-1, MSTYPE=SLAVE, ET=NO;
//Add 64 ESL subscribers. 8780100-8780131 are subscribers in office B, and 6540100-6540131

are subscribers in the mutual aid office A.
amg5000-2.com", STID=0, CODEC=PCMA, RCHS=87, CSC=10, NS=CLIP-1;
amg5000-2.com", STID=0, CODEC=PCMA, RCHS=65, CSC=0, NS=CLIP-1;
Step 17 Configure data for interworking with UMG (office B).

//Add two UMG8900s. Set the equipment ID of the UMG8900 in office B to
221.169.150.99:2944, and that of the UMG8900 in the mutual aid office A to
211.169.150.89:2944.

ADD MGW: EID="221.169.150.99:2944", GWTP=UMGW, MGWDESC="zhuhai-

CODETYPE=ASN, MSTYPE=SLAVE, ET=NO;
//Add 64 ESL subscribers. 8780200-8780231 are subscribers in office B, and 6540200-6540231

EID="221.169.150.99:2944", STID=0, CODEC=PCMA, RCHS=87, CSC=10,
EID="211.169.150.89:2944", STID=0, CODEC=PCMA, RCHS=65, CSC=0, NS=CLIP-1,
//Add two SGs (built in the UMG8900), with the SG ID of office B being 128 and that of the
mutual aid office A being 0.
ADD SG: SGID=0, SGNAME="IUA SG", SGTYPE=emb, EID="211.169.150.89:2944",
MSTYPE=SLAVE;
NOTE
//Add two IUA Linksets. Set the Linkset index of office B to 128 and that of the mutual aid
office A to 0.
NOTE
According to the principle for configuring signaling data, the IUA Linkset index of the local office must
be different from that of the mutual aid office.
//Add four IUA links. Set the IUA links of office B to link 8 of BSGI 136 and link 8 of BSGI
137. Set the IUA links of the mutual aid office A to link 0 of BSGI 136 and link 0 of BSGI 137.
LOCIP1="191.169.150.40", PEERIP1="221.169.150.27";
LOCIP1="191.169.150.40", PEERIP1="221.169.150.27";
PEERIP1="211.169.150.17", ASF=STANDBY;
PEERIP1="211.169.150.17", ASF=STANDBY;
NOTE
l According to the principle for configuring signaling data, the IUA link numbers of the local office must
office, whereas Peer IP address must be set based on the actual condition. In this example, Peer IP
address is the IP address of the UMG8900 used in the SIGTRAN protocol.


//Add 64 BRA subscribers. 8780300-8780331 are subscribers in office B, and 6540300-6540331

ISA=MSN-1, CSC=10, RCHS=87, NS=CLIP-1, CUGU=NO, CTX=YES, PBX=YES,
CHR=YES;
NOTE
Step 18 Configure multimedia subscriber data (office B).

//Add two multimedia devices using SIP, with the equipment ID of the device in office B being
8780401 and that in the mutual aid office A being 6540401.
PASS="223344", MSTYPE=SLAVE;
PASS="112233";
//Add two SIP subscribers. 8780401 is a SIP subscriber in office B, and 6540401 is a SIP
subscriber in the mutual aid office A.
Step 19 Configure data for interworking with PSTN (office B).

//Add two TMG8010s. Set the equipment ID of the TMG8010 in office B to
221.169.150.91:2944, that of the TMG8010 in the mutual aid office A to 211.169.150.81:2944,
and the FCCU module number to 23.
ADD MGW: EID="221.169.150.91:2944", GWTP=TG, MGWDESC="Zhuhai-TMG8010-2",
LISTOFCODEC=PCMA-1&PCMU-1&G7231-1&G729-1&T38-1, HAIRPIN=S, ET=NO;
TMG8010-2", MGCMODULENO=23, LA="191.169.150.30", RA1="191.169.150.81",
MSTYPE=SLAVE, ET=NO;
//Add two SGs (built in the TMG8010), with the SG ID of office B being 129 and that of the
mutual aid office A being 1.
ADD SG: SGID=129, SGNAME="M2UA SG", SGTYPE=emb,
EID="221.169.150.91:2944";
ADD SG: SGID=1, SGNAME="M2UA SG", SGTYPE=emb, EID="211.169.150.81:2944",
MSTYPE=SLAVE;
NOTE
type to Integer.

type to Integer.
//Add four M2UA links. Set the M2UA links of office B to link 8 of BSGI 136 and link 8 of
BSGI 137. Set the M2UA links of the mutual aid office A to link 0 of BSGI 136 and link 0 of
BSGI 137.
LOCIP1="191.169.150.40", PEERIP1="211.169.150.91";
LOCIP1="191.169.150.40", PEERIP1="211.169.150.91";
NOTE
l According to the principle for configuring signaling data, the M2UA link numbers of the local office
office, whereas Peer IP address must be set based on the actual condition.
//Add two MTP DSPs. The DPC is 1100bb. The OPC mapping DSP index 128 is 001133 (SPC
of office B). The OPC mapping DSP index 0 is 001122 (SPC of the mutual aid office A).
ADD N7DSP: DPX=128, DPC="1100bb", OPC="001133", DPNAME="B to PSTN";
ADD N7DSP: DPX=0, DPC="1100bb", OPC="001122", DPNAME="A to PSTN";
NOTE
According to the principle for configuring signaling data, the DSP indexes of the local office must be
different from those of the mutual aid office.
//Add two MTP Linksets. Set Linkset index to 128 and Adjacent DSP index to 128 for office
B. Set Linkset index to 0 and Adjacent DSP index to 0 for the mutual aid office A.
ADD N7LKS: LSX=128, ASPX=128, LSNAME="B to PSTN";
ADD N7LKS: LSX=0, ASPX=0, LSNAME="A to PSTN";
NOTE
According to the principle for configuring signaling data, the MTP Linkset indexes of the local office must
//Add four MTP links. Set the MTP links of office B to link 8 of BSGI 136 and link 8 of BSGI
137. Set the MTP links of the mutual aid office A to link 0 of BSGI 136 and link 0 of BSGI 137.
BINIFID=101, LSX=0, SLC=0, SLCS=0, MSF=SLAVER, TID=0;
BINIFID=102, LSX=0, SLC=1, SLCS=1, MSF=SLAVER, TID=0;

NOTE
l According to the principle for configuring signaling data, the MTP link numbers of the local office
l In the preceding example, Master/Slave type of the MTP links must be set to the same value as that
of the corresponding M2UA links.
//Add MTP routes destined for the PSTN switch. For the MTP links from office B to the PSTN
switch, set Linkset index to 128 and DSP index to 128. For the MTP links from the mutual aid
office A to the PSTN switch, set Linkset index to 0 and DSP index to 0.
ADD N7RT: LSX=128, DPX=128, RTNAME="B to PSTN";
ADD N7RT: LSX=0, DPX=0, RTNAME="A to PSTN";
//Add an office direction destined for the PSTN switch, with the office direction number being
0 and DPC being 1100bb.
ADD OFC: O=0, ON="To PSTN", DOT=CMPX, DOL=LOW, DPC1="1100bb";
NOTE
According to the principle for configuring routing data, you need to add only one office direction. This is
because the PSTN switch is the destination for both the local office and the mutual aid office.
//Add two subroutes. Set the number of the subroute from office B to the PSTN switch to 128
and that of the subroute from the mutual aid office A to the PSTN switch to 0.
ADD SRT: SRC=128, O=0, SRN="B to PSTN", RENT=URT;
ADD SRT: SRC=0, O=0, SRN="A to PSTN", RENT=URT;
//Add two routes. Set the number of the route from office B to the PSTN switch to 128 and that
of the route from the mutual aid office A to the PSTN switch to 0.
ADD RT: R=128, RN="B to PSTN ", SRST=SEQ, SR1=128, SR2=0;
ADD RT: R=0, RN="A to PSTN ", SRST=SEQ, SR1=0, SR2=128;
NOTE
In the preceding commands, the direct and alternate subroutes from office B to the PSTN switch are
numbered 128 and 0; those from the mutual aid office A to the PSTN switch are numbered 0 and 128.
//Add analysis data of the route destined for the PSTN switch. For the route from office B to the
PSTN switch, set the route selection code to 33 and the route number to 128. For the route from
the mutual aid office A to the PSTN switch, set the route selection code to 22 and the route
number to 0.
//Add SS7 trunk groups, with the trunk groups from office B to the PSTN switch numbered 100
and 101, and the trunk groups from the mutual aid office A to the PSTN switch numbered 0 and
1.


NOTE
l According to the principle for configuring trunk data, the trunk group numbers of the local office must
l To enable the SS7 trunk groups to use the correct number analysis data table for incoming calls, set
Call source code correctly. In the example, the call source codes of trunk groups 0 and 1 are set to 0,
and the call source codes of trunk groups 100 and 101 are set to 10.
l In the example, if it is required to perform CIC conversion on trunk groups 100 and 101, set CIC
change type to Decrease and CIC change value to 32. CIC change type and CIC change value are
used for the self-loop test of the two SS7 trunk groups (outgoing trunk E1 and incoming trunk E1)
between the local office and the same office direction.

NOTE
l If the SS7 trunk circuits of both the local office and the mutual aid office are connected to the same
FCCU, the circuit number range and the CIC code of each trunk group must be set globally.
l For the circuit number range, set Start circuit termination ID correctly by running ADD N7TKC.
This enables the SoftX3000 to interwork with the PSTN switch.
l For the CIC code, you may need to change the CIC code of the corresponding SS7 trunk group by
running MOD N7TG. This enables the SoftX3000 to interwork with the PSTN switch.
//Add a toll prefix for toll calls from the local office to the PSTN switch. Set Local DN set to
10, Call prefix to 0, Service attribute to National toll, and Route selection code to 33.
//Add a toll prefix for toll calls from the mutual aid office A to the PSTN switch. Set Local DN
set to 0, Call prefix to 0, Service attribute to National toll, and Route selection code to 22.
Step 20 Configure routing data for interworking with office A (office B).
NOTE
l In a network, if a standby SoftX3000 is configured for office A and office B respectively, perform the
data configuration according to the routing method 1.
l In a network, if no standby SOFTX3000 is configured for office A and office B, perform the data
configuration according to the routing method 2.
Configuring routing data for interworking with office A (mode one)

ADD OFC: O=102, ON="A_Signal_office", DOT=NATT, DOL=SAME;
ADD OFC: O=11, ON="B_Dual_office", DOT=NATT, DOL=SAME;
ADD OFC: O=12, ON="A_Dual_office", DOT=NATT, DOL=SAME;

NOTE
According to the principle for configuring routing data, configure three office directions for the
interworking between the local office and the mutual aid office:
l The office direction numbered 102 is the mutual aid office before the dual homing switchover, that is,
the mutual aid office A in normal conditions.
l The office direction numbered 11 is the mutual aid office after the dual homing switchover, that is,
office B in the virtual mutual aid office A.
l The office direction numbered 12 is the mutual aid office after the dual homing switchover, that is, the
virtual mutual aid office A in office B.

ADD SRT: SRC=102, O=102, SRN="B to A_0", RENT=URT;
ADD SRT: SRC=11, O=11, SRN="A to B", RENT=URT;
NOTE
The subroutes correspond to the three preceding office directions:

l The subroute numbered 102 is the subroute from office B to the mutual aid office A before the dual
homing switchover.
l The subroute numbered 11 is the subroute from the virtual mutual aid office A to office B after the
of office B.
l The subroute numbered 12 is the subroute from office B to the virtual mutual aid office A after the
of office B.

ADD RT: R=10, RN="To A_office", SRST=SEQ, SR1=102, SR2=12;
ADD RT: R=12, RN="To B_office", SRST=SEQ, SR1=11;
NOTE
l Route 10 is the route from office B to the mutual aid office A. You must configure two subroutes for
it: subroute 102 is the direct subroute, and subroute 12 is the alternate subroute.
l Route 12 is the route from the virtual mutual aid office A to office B. You need to configure only one
subroute for it.
//Add route analysis data. For the route from office B to the mutual aid office A, set the route
selection code to 65 and the route number to 10; for the route from the virtual mutual aid office
A to office B, set the route selection code to 87 and the route number to 12.
R=10, ISUP=SIP_M, NCAI=ALL, CST=ALL, CNPI=ALL;
ISUP=SIP_M, NCAI=ALL, CST=ALL, CNPI=ALL;
//Add three SIP trunk groups.

ADD SIPTG: TG=102, CSC=10, SRT=102, TGN=" B to A_0", RCHS=88, OTCS=99,
ADD SIPTG: TG=11, CSC=0, SRT=11, TGN=" A to B", RCHS=88, OTCS=99,
ADD SIPTG: TG=12, CSC=10, SRT=12, TGN="B To A_1", RCHS=88, OTCS=99,
//Add IP address pair data of the SIP trunk.


NOTE
l To enable the SoftX3000 to detect the working state of SIP trunks correctly, set Use Heartbeat to
Yes. Otherwise, the SoftX3000 cannot use the alternate subroute.
l To enable the SIP trunk groups to use the correct number analysis data table for incoming calls, set
Call source code correctly. In the example, the call source codes of trunk groups 102 and 12 are set
to 10, and the call source code of trunk group 11 is set to 0.
l SIP trunk groups 11 and 12 must be configured as the self-loop trunk groups of office B. Therefore,
their source and destination IP addresses must be the IP addresses of the IFMIs in office A and the
addresses must be crossly set. As shown in the given example, the source IP address of trunk group 11
is 191.169.150.40 (the module number of the IFMI is 132), and its destination IP address is
191.169.150.41. The source IP address of trunk group 12 is 191.169.150.41 (the module number of the
IFMI is 133), and its destination IP address is 191.169.150.40.
//Add an outgoing prefix for the calls from office B to the mutual aid office A. Set Local DN
NOTE
From the previous routing data configuring, it can be inferred that:

l Before the dual homing switchover, when a subscriber in office B dials the prefix 654, the system
selects the normal subroute from office B to the mutual aid office A.
l After the dual homing switchover, when a subscriber in office B dials the prefix 654, the system selects
the subroute from office B to the virtual mutual aid office A (that is, the self-loop subroute of office
B).
Thus, the call attribute and charging attribute of the office B prefix 654 are not changed before and after
the dual homing switchover.
//Add an outgoing prefix for the calls from office A to the mutual aid office B. Set Local DN
NOTE
After the dual homing switchover, when a subscriber in the mutual aid office A dials the prefix 878, the
system selects the subroute from the virtual mutual aid office A to office B (that is, the self-loop subroute
of office B). Thus, the call attribute and charging attribute of the prefix 878 in the virtual mutual aid office
A and the mutual aid office A are not changed before and after the dual homing switchover.
Configuring routing data for interworking with office A (mode two)

//Add an office direction. Set Office direction number to 102.
ADD OFC: O=102, ON="A_Signal_office", DOT=NATT, DOL=SAME;
//Add a subroute. Set Sub-route number to 102.

//Add a route. Set Route number to 10.

ADD RT: R=10, RN="To A_office", SRST=SEQ, SR1=102
//Add route analysis data. Set Route selection code to 65 and Route number to 10 for the route
from office B to office A.


R=10, ISUP=SIP_F, NCAI=ALL, CST=ALL, CNPI=ALL;
//Add an outgoing prefix for the calls from office B to office A. Set Local DN set to 10, Call
prefix to 654, Service attribute to Local, and Route selection code to 65.
//Add the trunk group from office B to office A.

ADD SIPTG: TG=102, CSC=10, SRT=102, TGN=" B to A_0", RCHS=88, OTCS=99,
//Add the trunk group IP address pair.

DH=Yes, DHOSU="191.169.150.40:5060";
----End
Related tasks
Commissioning the Dual-Homing Networking Data
Related concepts
None.
10.3 Configuring Smart Network Data
Scenarios
Smart network is a complete solution used to reconstruct the existing PSTN by separating
services from call control. Most end offices in the existing PSTN do not support the SSP function.
Therefore, three centers are set up in the smart network to shield end offices and enable value-
added services rapidly. The three centers are as follows:
l Service switching center
l Subscriber data center
l IN service center
Figure 10-3 shows the typical networking model.

Figure 10-3 Networking for the smart network solution
IN service center
AIP AS SCP MRS
Subscriber data center
SHLR
Service switch center

SoftX3000
UMG8900 UMG8900
End office End office End office End office
End office of local network
requirements:
l The signaling networking between the SoftX3000 and the SCP adopts the "M3UA-M3UA"
peer-to-peer network mode. The SoftX3000 and the SCP together can provide services such
as the intelligent card number service.
l The signaling networking between the SoftX3000 and the SHLR adopts the "M3UA-
M3UA" peer-to-peer network mode. The SoftX3000 and the SHLR together can provide
services such as NP, CUG, and MON.
l The SoftX3000, SCP, and SHLR together can provide services such as the one number link
you (ONLY) service and the ring back tone (RBT) service in callee IN subscription mode.
Prerequisites
Conditions

Data
consistent between the SoftX3000 and the SCP, and the parameters in Table 10-4 are consistent
between the SoftX3000 and the SHLR.
Table 10-3 Data for interworking between the SoftX3000 and the SCP
Serial Interworking Parameters Value

No.
1 IP address of the IFMI of the SoftX3000 191.169.150.30/255.255.0.0
2 IP address of the SCP 191.169.150.12/255.255.0.0
3 SPC of the SoftX3000 001122 (national network)
4 SPC of the SCP 115566 (national network)
5 Local SCTP port number of the M3UA link on the M3UA link 2: 2905
SoftX3000 (client) side M3UA link 3: 2911
6 Local SCTP port number of the M3UA link on the 2905

SCP (server) side
7 Number of the subsystem between the SoftX3000 SCMG and INAP

and the SCP
8 Access code of the ONLY service 274
9 DP number of the ONLY service 3
10 Service key of the ONLY service 274
11 Access code of the RBT service 275
12 DP number of the RBT service 3
13 Service key of the RBT service 275
14 Access code of the ACC service 201
15 DP number of the ACC service 3
16 Service key of the ACC service 201
Table 10-4 Data for interworking between the SoftX3000 and the SHLR
Serial Parameter Value

No.
2 IP address of the active SHLR 191.169.150.13/255.255.0.0


No.
3 IP address of the standby SHLR 191.169.150.15/255.255.0.0
5 SPC of the active SHLR 115588 (national network)
6 SPC of the standby SHLR 115599 (national network)
7 Local SCTP port number of the M3UA link on the M3UA link 2: 2905
SoftX3000 (client) side M3UA link 3: 2911
8 Local SCTP port number of the M3UA link on the 2905

SG7000 (server) side
9 Number of the subsystem between the SoftX3000 MSC and HLR

and the SHLR
10 Type of number sent from the SoftX3000 to the Original number

SHLR
11 Service flow between the SoftX3000 and the SHLR Extended flow
12 Overlap service indicator 100
13 Service access code of the CUG service 200
14 Triggering access code of the MON service 300
15 Release access code of the MON service 400
Documents
Workflow
The procedure for configuring the smart network data is as follows:
1. Configure M3UA Data.
2. Configure SCCP signaling data for interworking with SHLR.
3. Configure service data for interworking with SHLR.
4. Configure SCCP signaling Data for interworking with SCP.
5. Configure IN service data for interworking with SCP.
Procedure
Step 1 Configure M3UA data.

//Add an M3UA local entity. Set Local entity index to 0, Local entity point code to
001122, and Routing context to 12345.
NOTE
Route context can be a decimal number or null (the value is not set). Route context should be
consistent with that configured on the SCP and SHLR when the SoftX3000 interworks with the SCP
and SHLR.
//Add three M3UA destination entities. Destination entity index 51 stands for the SCP,
destination entity index 52 for the active SHLR, and destination entity index 53 for the
standby SHLR.
ADD M3DE: DEX=51, LEX=0, DENAME="SCP", DPC="115566", DET=AS;
ADD M3DE: DEX=52, LEX=0, DENAME="M_SHLR", DPC="115588", DET=AS;
ADD M3DE: DEX=53, LEX=0, DENAME="S_SHLR", DPC="115599", DET=AS;
NOTE
The peer-to-peer network mode is used for the M3UA signaling networking among the SCP, the
SHLR, and the SoftX3000; the entity type of the SoftX3000 is application server. Therefore, set
Destination entity type of the SCP and the SHLR to AS.
2. Add three M3UA Linksets.
//Add three M3UA Linksets. For Linkset index 1, set Linkset index to 1 and Adjacent
entity index to 51. For Linkset index 2, set Linkset index to 2 and Adjacent entity
index to 52. For Linkset index 3, set Linkset index to 3 and Adjacent entity index to
53.
ADD M3LKS: LSX=1, LSNAME="To SCP", ADX=51, WM=IPSP;
ADD M3LKS: LSX=2, LSNAME="To M_SHLR ", ADX=52, WM=IPSP;
ADD M3LKS: LSX=3, LSNAME="To S_SHLR ", ADX=53, WM=IPSP;
NOTE
l The peer-to-peer network mode is used for the M3UA signaling networking among the SCP, the
SHLR, and the SoftX3000; the entity type of the SoftX3000 is application server. Therefore, set
Work mode to IPSP.
l The traffic mode of the Linkset must be consistent with that on the SG side. Otherwise, the M3UA
links in the Linkset fail to work. In normal cases, set Traffic mode of the Linkset to
LOADSHARE.
//Add six M3UA links. Configure two links for each M3UA Linkset connecting the
SoftX3000 and the SCP, the SoftX3000 and the active SHLR, and the SoftX3000 and the
standby SHLR. The M3UA links belong to M3UA Linksets 1, 2, and 3 respectively.
ADD M3LNK: MN=136, LNKN=1, LNKNAME="To SCP #0",
ADD M3LNK: MN=137, LNKN=1, LNKNAME="To SCP #1",
ADD M3LNK: MN=136, LNKN=2, LNKNAME="To M_SHLR #0",
ADD M3LNK: MN=137, LNKN=2, LNKNAME="To M_SHLR #1",
ADD M3LNK: MN=136, LNKN=3, LNKNAME="To S_SHLR #0",
ADD M3LNK: MN=137, LNKN=3, LNKNAME="To S_SHLR #1",


NOTE
To ensure the reliability of the M3UA links, if two BSGIs are equipped in the SoftX3000, allocate
the two M3UA links to different BSGIs.
3. Add M3UA routes destined for the SCP, the active SHLR, and the standby SHLR.
ADD M3RT: RTNAME="To SCP", DEX=51, LSX=1;
ADD M3RT: RTNAME="To M_SHLR", DEX=52, LSX=2;
ADD M3RT: RTNAME="To S_SHLR", DEX=53, LSX=3;
Step 2 Configure SCCP signaling data for interworking with SHLR.

1. Add two SCCP destination signaling points (DSPs)
//Add two SCCP destination signaling points (DSPs). For one SCCP DSP, set DSP
index to 52 and DPC to 115588. For the other SCCP DSP, set DSP index to 53 and
DPC to 115599.
ADD SCCPDSP: DPX=52, NI=NAT, DPC="115588", OPC="001122",
DPNAME="M_SHLR", SHAREFLAG=NONE;
DPNAME="S_SHLR", SHAREFLAG=NONE;
NOTE
When the local office uses multiple signaling points, set OPC based on the actual signaling
networking.
2. Add SCCP subsystems.
SSNNAME="MSC to M_SHLR";
SSNNAME="MSC to S_SHLR";
SSNNAME="MSC to M_SHLR";
SSNNAME="MSC to S_SHLR";
NOTE
l Configure two SSN names for the smart network service: MSC and HLR.
l SPC is the destination signaling point code of the corresponding subsystem (receiver of the local
SCCP messages). For each subsystem, configure two DSPs: SCCP remote signaling point and
local signaling point.
Step 3 Configure service data for interworking with SHLR.

1. Modify the call source code.
//Modify the call source code. Set Call source code to 0 and SHLR selection source
code to 0.
MOD CALLSRC: CSC=0, SHLRSSC=0;
2. Modify called number analysis data.
//Modify called number analysis data. Set NP/SHLR Select Code to 0.
MOD CNACLD: LP=0, PFX=K'654, EA=YES, SHLRSLC=0;
MOD CNACLD: LP=0, PFX=K'878, EA=YES, SHLRSLC=0;

//Modify called number analysis data. Change the SHLR selection code of the call prefix
whose service attribute is Intra-office national toll or Intra-office international toll from
65535 to 0, and SHLR MON route prefix to Yes.
MOD CNACLD: LP=0, PFX=K'0755, EA=YES, SHLRFLAG=YES, SHLRSLC=0;
NOTE
When the SoftX3000 adopts multiple area codes or country codes to interwork with other offices,
and cooperates with the SHLR to enable the MON service, set SHLR MON route prefix to Yes for
the call prefix whose service attribute is Intra-office national toll or Intra-office international
toll. In such a case, the SoftX3000 adds the route number returned from the SHLR to the called
number, and then performs analysis again.
3. Add two SHLR local addresses.
//Add two SHLR remote addresses. The SHLR address index 0 represents the active SHLR,
and the SSN is HLR; the SHLR address index 1 represents the standby SHLR, and the SSN
is HLR.
ADD SHLRRA: SHLRAddrIndex=0, RT=DPC, DPC="115588", SSN=HLR;
ADD SHLRRA: SHLRAddrIndex=1, RT=DPC, DPC="115599", SSN=HLR;
NOTE
l To add SHLR local addresses, set SSN to MSC 0x08.

l DPC is the SPC of the local office. It must be defined by running SET OFI and configured by
running ADD SCCPDSP (configuring OPC) before being referenced here.
4. Add two SHLR remote addresses.
//Add two SHLR local addresses. The SHLR address index 0 represents the active SHLR,
and the SSN is MSC; the SHLR address index 1 represents the standby SHLR, and the SSN
is MSC.
ADD SHLRLA: SHLRAddrIndex=0, SHLRDESC="M_SHLR", RT=DPC, OPC="001122",
SSN=MSC;
ADD SHLRLA: SHLRAddrIndex=1, SHLRDESC="S_SHLR", RT=DPC, OPC="001122",
SSN=MSC;
NOTE
l To add SHLR remote addresses, set SSN to HLR 0x06.

l DPC is the SPC of the SHLR. It must be defined by running ADD M3DE and configured by
running ADD SCCPDSP (configuring DPC) before being referenced here.
5. Add an SHLR group.
//Add an SHLR group. Set SHLR group number to 0, Select mode to Active/Standby
mode, SHLR index 1 to 0, and SHLR index 2 to 1.
ADD SHLRGRP: SHLRGrpNumber=0, SelectMode=STB, SHLRIDX1=0, SHLRIDX2=1;
6. Add SHLR configuration.
//Add SHLR configuration. Set SHLR selection code to 0, Query SHLR type to
Extend, Overlap flag to True, and Overlap service indicator to 100.
ADD SHLRCFG: SHLRSLC=0, SHLRSSC=0, CLTP=ALLTYPE, SHLRCFGIDX=0,
QTYPE=EXT, HOOKTRGFLG=NO, OVRPFLGEXT=OVRAIND, SHLRGRPNOEXT=0;
7. Set the SHLR server.
//Set the SHLR server. The standard ITU-T MAP is used for interworking between the
SoftX3000 and the SHLR. The SHLR group number is 0.

SET NPDB: NT=MAP, SGI=0;

8. Add SHLR service configuration.
//Add SHLR service configuration. Set Service type to Caller NP/IN, Callee NP/IN,
CUG, and MON respectively. Set SHLR group number to 0.
ADD SHLRSRVC: SHLRCFGIDX=0, SRVTP=CLRNPIN, SHLRGRPNO=0;
ADD SHLRSRVC: SHLRCFGIDX=0, SRVTP=CLDNPIN, SHLRGRPNO=0;
ADD SHLRSRVC: SHLRCFGIDX=0, SRVTP=CUG, SRVACCODE="200", SHLRGRPNO=0;
ADD SHLRSRVC: SHLRCFGIDX=0, SRVTP=MON, SRVACCODE="300",
MONRLCODE="400", SHLRGRPNO=0;
9. Modify the setting of the corresponding software parameter.
//Modify software parameter P166.

NOTE
When a MON subscriber starts a call, and if the SHLR determines that the virtual number of the
caller exists in the same local network as the called number, the SHLR returns the virtual number of
the caller. By default, the caller number displayed on the callee's phone is the default caller number
configured by running ADD SHLRSRVC instead of the virtual number returned by the SHLR. The
caller number displayed on the callee's phone is the virtual number returned by the SHLR only after
you run MOD FSFP to set bit 8 of the call internal parameter 13 (P166) to 0.
Step 4 Configure SCCP signaling data for interworking with SCP.

1. Add an SCCP DSP.
//Add an SCCP DSP. Set DSP index to 50 and DPC to 115566.

DPNAME="SCP", SHAREFLAG=NONE;
NOTE
networking.
//Add SCCP subsystems.

NOTE
l For fixed IN services, configure two SSNs: SCMG 0x01 and INAP 0x0C.
Step 5 Configure IN service data for interworking with SCP.

1. Add IN call prefixes.
//Add IN call prefixes. Set call prefixes to 201, 274, and 275 respectively.

ADD CNACLD: PFX=K'201, CSTP=IN, CSA=INSVR, MINL=3, MAXL=3, CHSC=0,

SDESCRIPTION="ACC Service", EA=NO;
SDESCRIPTION="ONLY Service", EA=NO;
SDESCRIPTION="RBT Service", EA=NO;
NOTE
l For the ACC service, ONLY service, and RBT service, set Service category of the corresponding
call prefix to IN.
l Configure the IN call prefix and access code only when the DP number is 3.
2. Add the access code description.
//Add the access code description. The access codes are 201, 274 and 275.
ADD ACCODE: CODE=K'201, POS=255, DBLEN=255;
NOTE
It is not required to obtain the database number from the called number in the ACC service, ONLY
service, and RBT service. Therefore, Database start position and Database field length are set to
255.
3. Add the TDP configuration.
//Add the TDP configuration. Set Service key to 201, 274, and 275 respectively. Set Call
source code to 65534 (wildcard).
ADD TDPCFG: DPNO=DP3, DPCNO=ACODE, CODE=K'201, SKEY=201,
CALLSRC=65534;
CALLSRC=65534;
CALLSRC=65534;
NOTE
l For IN services of card number type, the SSP employs the information analysis call model. That
is, the DP number is 3.
l In this example, the SoftX3000 provides the ONLY service and RBT service in callee IN
subscription mode. Set DP number to DP3 indicating that the information analysis call model
is used on the SSP side for triggering the RBT service.
4. Add the SCP physical address description.
//Add the SCP physical address description. Set SCP number to 1, DPC to 115566, and
SCP connect type to Connect SAU.
ADD SCPADDR: SCP=1, DPC="115566", SCT=SAU;
5. Add the SSP physical address description.
//Add the SSP physical address description. The SCP number is 1. The OPC of the SSP
(SoftX3000) is 001122.
ADD SSPADDR: SCP=1, OPC="001122";
6. Add the SCP configuration.
//Add the SCP configuration. SCP1 processes INAP messages of the ACC service (with
service key as 201), ONLY service (with service key as 274), and RBT service (with service
key as 275). The SCP selection source code is 65534.

ADD SCPCFG: SKEY=201, DB=65535, SNAME=ACC, SCP=SCP0-0&SCP1-1,

RCODE=65534;
RCODE=65534;
RCODE=65534;
NOTE
It is not required to obtain the database number from the called number in the preceding IN services.
Therefore, Database number is set to 65535.
----End
Related tasks
IN Service Data Commissioning
Related concepts
None.
10.4 Configuring Smart Network Data (with the SCPs

Working in the Active/Standby Mode)
Scenarios
To improve the reliability of the network and avoid system breakdown, carriers deploy networks
in the way shown in Figure 10-4. On such a network, if the communication between the
SoftX3000 and an SCP is interrupted, the SoftX3000 automatically switches services to the other
SCP, which prevents service interruption.

Figure 10-4 Networking for the smart network solution
AIP AS Active SCP StandbySCP MRS

Subscriber data IN service center
center
SHLR
Service switching
SoftX3000 center
UMG8900 UMG8900
End office End office End office End office

End office of local network
requirements:
l The signaling networking between the SoftX3000 and the SCP adopts the "M3UA-M3UA"
peer-to-peer network mode. The SoftX3000 and the SCP together can provide services such
as the intelligent card number service.
l The SoftX3000 and SCP together can provide services such as the one number link you
(ONLY) service and the ring back tone (RBT) service in callee IN subscription mode.
Prerequisites
Conditions
Data
consistent between the SoftX3000 and the SCP.

Table 10-5 Data for interworking between the SoftX3000 and the SCP
Serial No. Interworking Parameters Value
1 IP address of the IFMI of the 191.169.150.30/255.255.0.0

SoftX3000
2 IP address of the SCP l Active: 191.169.150.12/255.255.0.0

l Standby: 191.169.150.13/255.255.0.0
4 SPC of the SCP l Active: 115566 (national network)

l Standby: 115577 (national network)
5 Local SCTP port number of the l M3UA link 2: 2905

M3UA link on the SoftX3000 l M3UA link 3: 2911
(client) side
6 Local SCTP port number of the l Active: 2905

M3UA link on the SCP l Standby: 2911
(server) side
7 Number of the subsystem SCMG and INAP

between the SoftX3000 and
the SCP
8 Access code of the ONLY 274

service
9 DP number of the ONLY 3

service
10 Service key of the ONLY 274

service
11 Access code of the RBT 275

service
12 DP number of the RBT service 3
13 Service key of the RBT service 275
14 Access code of the ACC 201

service
15 DP number of the ACC service 3
16 Service key of the ACC service 201
Documents

Workflow
The procedure for configuring the smart network data is as follows:
1. Configure M3UA data.

2. Configure SCCP signaling Data for interworking with SCP.
3. Configure IN service data for interworking with SCP.
Procedure
//Add an M3UA local entity. Set Local entity index to 0, Local entity point code to
001122, and Routing context to 12345.
NOTE
Route context can be a decimal number or null (the value is not set). Route context should be
consistent with that configured on the SCP when the SoftX3000 interworks with the SCP.
//Add two M3UA destination entities. Destination entity index 51 stands for the active SCP,
and destination entity index 54 for the standby SCP.
ADD M3DE: DEX=51, LEX=0, DENAME="M_SCP", DPC="115566", DET=AS;
ADD M3DE: DEX=54, LEX=0, DENAME="S_SCP", DPC="115577", DET=AS;
NOTE
The peer-to-peer network mode is used for the M3UA signaling networking among the SCP and the
SoftX3000; the entity type of the SoftX3000 is application server. Therefore, set Destination entity
type of the SCP to AS.
2. Add three M3UA Linksets.
//Add two M3UA Linksets. For Linkset index 1, set Linkset index to 1 and Adjacent entity
index to 51. For Linkset index 4, set Linkset index to 4 and Adjacent entity index to
54.
ADD M3LKS: LSX=1, LSNAME="To M_SCP ", ADX=51, TM=LOADSHARE, WM=IPSP;
ADD M3LKS: LSX=4, LSNAME="To S_SCP ", ADX=54, TM=LOADSHARE, WM=IPSP;
NOTE
l The peer-to-peer network mode is used for the M3UA signaling networking among the SCP and
the SoftX3000; the entity type of the SoftX3000 is application server. Therefore, set Work
mode to IPSP.
l The traffic mode of the Linkset must be consistent with that on the SG side. Otherwise, the M3UA
links in the Linkset fail to work.
l In normal cases, set Traffic mode of the Linkset to LOADSHARE.
//Add two M3UA links. The M3UA links belong to M3UA Linksets 1 and 4 respectively.
ADD M3LNK: MN=136, LNKN=1, LNKNAME="To M_SCP",
ADD M3LNK: MN=136, LNKN=4, LNKNAME="To S_SCP",

3. Add M3UA routes destined for the active SCP and the standby SCP.
ADD M3RT: RTNAME="To M_SCP", DEX=51, LSX=1;
ADD M3RT: RTNAME="To S_SCP", DEX=54, LSX=4;
Step 2 Configure SCCP signaling data for interworking with SCP.

1. Add two SCCP destination signaling points (DSPs)
//Add two SCCP destination signaling points (DSPs). For one SCCP DSP, set DSP
index to 51 and DPC to 115566. For the other SCCP DSP, set DSP index to 54 and
DPC to 115577.
DPNAME="M_SCP", SHAREFLAG=NONE;
DPNAME="S_SCP", SHAREFLAG=NONE;
NOTE
networking.
SSNNAME="SSP to S_SCP";
SSNNAME="SSP to S_SCP";
SSNNAME="SSP to M_SCP", BAKINDEX=12;
SSNNAME="SSP to M_SCP", BAKINDEX=13;
NOTE
l Configure two SSN names for the smart network service: SCMG and INAP.
Step 3 Configure IN service data for interworking with SCP.

1. Add IN call prefixes.
//Add IN call prefixes. Set call prefixes to 201, 274, and 275 respectively.
SDESCRIPTION="ACC Service", EA=NO;
SDESCRIPTION="ONLY Service", EA=NO;
SDESCRIPTION="RBT Service", EA=NO;
NOTE
l For the ACC service, ONLY service, and RBT service, set Service category of the corresponding
call prefix to IN.
l Configure the IN call prefix and access code only when the DP number is 3.
2. Add the access code description.
//Add the access code description. The access codes are 201, 274 and 275.


NOTE
It is not required to obtain the database number from the called number in the ACC service, ONLY
service, and RBT service. Therefore, Database start position and Database field length are set to
255.
3. Add the TDP configuration.
//Add the TDP configuration. Set Service key to 201, 274, and 275 respectively. Set Call
source code to 65534 (wildcard).
CALLSRC=65534;
CALLSRC=65534;
CALLSRC=65534;
NOTE
l For IN services of card number type, the SSP employs the information analysis call model. That
is, the DP number is 3.
l In this example, the SoftX3000 provides the ONLY service and RBT service in callee IN
subscription mode. Set DP number to DP3 indicating that the information analysis call model
is used on the SSP side for triggering the RBT service.
4. Add the SCP physical address description.
//Add the SCP physical address description. Set SCP number to 1, DPC to 115566; Set
SCP number to 2, DPC to 115577; Set SCP connect type to Connect SAU.
5. Add the SSP physical address description.
//Add the SSP physical address description. The SCP number is 1 and 2. The OPC of the
SSP (SoftX3000) is 001122.
6. Add the SCP configuration.
//Add the SCP configuration. SCP1 processes INAP messages of the ACC service (with
service key as 201), ONLY service (with service key as 274), and RBT service (with service
key as 275). The SCP selection source code is 65534.
ADD SCPCFG: SKEY=201, DB=65535, SNAME=ACC, SCP=SCP1-1, RCODE=65534;
NOTE
It is not required to obtain the database number from the called number in the preceding IN services.
Therefore, Database number is set to 65535.
----End
Related tasks

IN Service Data Commissioning
Related concepts
None.
10.5 Configuring Multi-SPC Network Data
Scenarios
As restricted by the digits (12 digits) of SS7 circuit identification code (CIC), when two offices
adopt the single originating point code (OPC) mode, a maximum of 4096 SS7 trunk circuits can
be deployed between them. This, however, does not meet the requirement for a large number of
trunks, for example, in the networking of the gateway office. To break the restriction, the
SoftX3000 provides the multi-OPC function, through which you can configure up to 256 OPCs
for the SoftX3000. Thus, even if the peer office adopts the single OPC mode, 256 x 4096 =
1048576 SS7 trunk circuits can be deployed between them.
For example, the SoftX3000 acts as the gateway office of carrier A. Through the UMG8900,
6000 SS7 trunk circuits (200 E1s) are deployed between the SoftX3000 and the PSTN switch
of carrier B. Figure 10-5 shows the networking.
Figure 10-5 Networking in which the SoftX3000 acts as the gateway office
SoftX3000
M2UA link UMG8900 PSTN switch
MTP link
NO.7 trunk ciruit
Gataway office Gataway office of
of carrier A carrier B
requirements:
l The SoftX3000 uses two OPCs. Each OPC deploys 3000 SS7 trunk circuits (100 E1s).
l Two M2UA links are provided between the SoftX3000 and the UMG8900. Through the
UMG8900, four 64-kbit/s MTP links are provided for the PSTN switch. Each M2UA link
carries the SS7 signaling traffic on two MTP links.
l On the SoftX3000 side, the two OPCs are mutual assistant nodes.
Prerequisites
Conditions


Data
Only the basic data required for the configuration is listed in Table 10-6.
Table 10-6 Basic data of the multi-SPC function

No.
1 SPC of the SoftX3000 001122, 001133
2 SPC of the PSTN switch 110088
3 MTP link code Link 0: 0

Link 1: 1
Link 2: 2
Link 3: 3
4 Type of signaling used by SS7 ISUP

trunks
5 CIC of SS7 trunk circuits For each pair of OPC and DPC, the CIC
ranges 0-3199.
6 Selection type for SS7 trunk Circuits are selected in a cyclic manner. The
circuits local office controls the circuits with odd
numbers, and the peer office controls the
circuits with even numbers.
Documents
Before configuring the multi-SPC network data, you must plan the related data based on the
Workflow
The procedure for configuring the multi-SPC network data is as follows:
1. Configure local office data.

2. Configure MGW data.
4. Configure MTP data.

Procedure
//Configure local office information. The SPC (OPC index is 0) of the local office is 001122
(national network).
SET OFI: OFN="SoftX3000", LOT=CMPX, NN=YES, SN1=NAT, SN2=NAT, SN3=NAT,
//Add the SPC (OPC index is 1) 001133 (national network).

ADD OFI: IDX=1, NI=NN, OPC="001133", MSTYPE=MASTER;
//Modify local office assistant node data. Set the two original SPCs as mutual assistant nodes.
MOD OFI: IDX=0, PA1=NN, PAC1="001133";
MOD OFI: IDX=1, PA1=NN, PAC1="001122";
NOTE
assistance nodes, run MOD OFI to configure two pieces of data.
l If the local office starts the multi-SP mutual aid function, the peer office must adapt accordingly when
configuring data of signaling routes destined for the local office. Assume that the original SP A and B
of the local office are mutual nodes, the peer office must set its DSP A and B to be of STP attribute.
Two more alternate signaling routes must also be added: one from A to B, and the other from B to A.

//Add a UMG8900. Set Equipment ID to 211.169.150.95:2944.
CODETYPE=ASN;
NOTE
l Regardless of whether the UMG8900 acts as an AG or a TG, the format of Equipment ID must be "IP
address:port number", and Gateway type must be UMGW.
l Remote address must be set to the IP address of the UMG8900 used for the H.248 protocol, that is,
211.169.150.95.
l In general, the UMG8900 interworks with the SoftX3000 using the H.248 protocol; therefore, set Code
type to ASN.1.
l The UMG8900 supports the hairpin connection function. Therefore, Hairpin connection must be set
to Supported.

//Add an embedded SG (built in the UMG8900) with the ID 9.
ADD SG: SGID=9, SGNAME="M2UA SG", SGTYPE=EMB, EID="211.169.150.95:2944";
NOTE
The SG is embedded in the UMG8900. Therefore, Equipment ID must be set to the equipment ID of the
UMG8900. In this example, Equipment ID is set to 211.169.150.95:2944.
// Add two M2UA Linksets.

ADD M2LKS: M2LSX=2, SGID=9;
ADD M2LKS: M2LSX=3, SGID=9;

//Add two M2UA links, with the SoftX3000 serving as the client and the UMG8900 serving as
the server.
LOCIP1="191.169.150.30", PEERIP1="211.169.150.15";
LOCIP1="191.169.150.30", PEERIP1="211.169.150.15";
NOTE
Peer IP address must be set to the IP address of the UMG8900 used for the SIGTRAN protocol. In this
example, Peer IP address is set to 211.169.150.15.
Step 4 Configure MTP data.
//Add the MTP Destination Point Code (DPC) 110088.

ADD N7DSP: DPX=80, DPC="110088", OPC="001122", DPNAME="P_office #0";
ADD N7DSP: DPX=81, DPC="110088", OPC="001133", DPNAME="P_office #1";
NOTE
The local office uses two OPCs. Therefore, define the corresponding MTP DPCs for different OPCs.
//Add two MTP Linksets, with the indexes 2 and 3 respectively.

ADD N7LKS: LSX=2, ASPX=80, LSNAME="To P_office #0";
ADD N7LKS: LSX=3, ASPX=81, LSNAME="To P_office #1";
NOTE
l The local office uses two OPCs. Therefore, define the corresponding MTP Linksets for different OPCs.
l The SoftX3000 and the PSTN switch interwork with each other in the associated signaling mode of
SS7. Therefore, set Adjacent DSP index as the SP indexes of the PSTN switch. In this example,
Adjacent DSP index is set to 80 and 81 respectively.
//Add four MTP links. The SS7 signaling traffic on the first two MTP links is carried by No. 2
M2UA link, and the signaling traffic on the last two MTP links is carried by No. 3 M2UA link.
ADD N7LNK: MN=136, LNKN=2, LNKNAME="To P_office #0", LNKTYPE=M64K,
M2LSX=2, BINIFID=21234, LSX=2, SLC=0, SLCS=0, TID=0;
NOTE
l The SoftX3000 uses M2UA to carry SS7 signaling traffic on MTP links. Therefore, Link type must
be set to M2UA 64K LINK.
l Module number can be set only to the module number of the corresponding BSGI. In this example,
Module number is set to 136.
l For an MTP link with M2UA to carry SS7 signaling traffic (logical link on the SoftX3000 side), the
interface ID of the MTP link must be defined. Different MTP links have different (integer) interface
IDs.
//Add MTP routes destined for the PSTN switch.

ADD N7RT: LSX=2, DPX=80, RTNAME="To P_office #0";
ADD N7RT: LSX=3, DPX=81, RTNAME="To P_office #1";

NOTE
There are two MTP Linksets between the local office and the PSTN switch. Therefore, two MTP routes
must be set from the local office to the PSTN switch.
//Add an office direction destined for the PSTN switch. Set Office direction number to 88 and
Destination point code 1 to 110088.
ADD OFC: O=88, ON="P_office", DOT=CMPX, DOL=SAME, DPC1="110088";
NOTE
This office direction has SS7 trunk circuits. Therefore, you must set DPC. Otherwise, errors occur when
you add an SS7 trunk group by running ADD N7TG.
//Add two sub-routes numbered 80 and 81.

ADD SRT: SRC=80, O=88, SRN="To P_office #0", RENT=URT;
ADD SRT: SRC=81, O=88, SRN="To P_office #1", RENT=URT;
NOTE
The local office adopts two OPCs. Therefore, set two sub-routes between the local office and the PSTN
switch. This improves flexibility in route selection.

ADD RT: R=88, RN="To P_office", SRST=PERC, SR1=80, SR2=81;
SET SRTATTR: R=88, SR=81, PSR=50;
NOTE
Two sub-routes exist between the local office and the PSTN switch. Therefore, Sub-route selection
mode is set to Select by percentage, and the percentage of sub-route 80 and sub-route 81 is 50%.
//Add analysis data of the route destined for the PSTN switch. Set Route selection code to 88.
//Add SS7 trunk groups. Trunk groups 80 and 82 belong to sub-route 80; trunk groups 81 and
83 belong to sub-route 81.
SDPC="110088", TGN="To P_office", PRTFLG=CN, NOAA=FALSE, ISM=FALSE,
EA=FALSE;
EA=FALSE;
EA=FALSE;
EA=FALSE;
NOTE
For trunk groups 80 and 82 that belong to sub-route 80, the OPC and DPC used are 001122 and 110088
respectively. For trunk groups 81 and 83 that belong to sub-route 81, the OPC and DPC used are 001133
and 110088 respectively.

//Add SS7 trunk circuits, with the trunk group number being 80 (OPC is 001122, and DPC is
110088), circuit number ranging from 1024-2623, and CIC ranging from 0-1599.
ADD N7TKC: MN=23, TG=80, SC=1344, EC=1663, SCIC=320, SCF=FALSE,
TID="320";
TID="640";
TID="960";
TID="1280";
NOTE
l Start circuit number and End circuit number are logical numbers universally assigned among SS7,
PRA, and R2 trunk circuits inside the SoftX3000. The corresponding physical number on the TMG8010
side is specified by Start circuit termination ID.
l The start circuit number must be a multiple of 32, such as 0, 32, 64, and 96. "End circuit number - start
circuit number + 1" must also be a multiple of 32.
l A maximum of 320 circuits can be added each time.
l On the TMG8010 side, each E1 has 32 timeslots. Therefore, the termination ID of No. 0 timeslot is
always a multiple of 32. When configuring data on the SoftX3000 side, ensure that Start media
gateway termination ID is a multiple of 32, to avoid any errors.
TID="1600";
TID="1920";
TID="2240";
TID="2560";
TID="2880";
TID="3520";
TID="3840";
TID="4160";
TID="4480";
TID="4800";
TID="5120";
TID="5440";

TID="5760";
TID="6080";
----End
Related tasks
Commissioning the Multi-signaling Point Networking Data
Related concepts
None.
10.6 Configuring Multi-Area-Code Data
Scenarios
The SoftX3000 supports the multi-area-code function (or multi-country-code) in the same
switch, which can fully meet a carrier 's requirements for inter-area and inter-nation networking.
For example, a carrier needs to provide local call access services in cities A, B, and C. Figure
10-6 shows the application networking.
Figure 10-6 Networking for multi-area-code application of the SoftX3000
SoftX3000
TMG8010 PSTN Switch
AMG AMG AMG
POTS POTS POTS POTS POTS POTS

Local network Local network Local network
in city A in city B in city C
requirements:
l Calls between internal subscribers in each local network are local calls, which are charged
according to the charging rate of the local network.

l Calls between the local networks are toll calls, which are charged according to the charging
rate of the toll call.
Prerequisites
Conditions

Data
Table 10-7 Basic data of the multi-area-code function
Serial No. Parameter Value
1 Area code of the local network in city A 0755
2 DN set used by the local network in city A 0
3 Subscriber numbers used by the local network 6540000-6540999

in city A 8780000-8780999
4 Two call sources planned for the local network Call source codes 0 and 1
in city A
5 Area code of the local network in city B 0756
6 DN set used by the local network in city B 10

in city B
8 Call source planned for the local network in Call source code 10
city B
9 Area code of the local network in city C 0752
10 DN set used by the local network in city C 20

in city C 3990000-3990999
12 Two call sources planned for the local network Call source codes 20 and 21
in city C
Documents
Before configuring the multi-country-code data, you must plan the related data based on the

Workflow
The procedure for configuring the multi-area-code network data is as follows:
3. Configure subscriber data.
4. Configure number analysis data.
Procedure
//Add local DN sets. Set the area code of the local network in city A to 755 and the local DN set
to 0. Set the area code of the local network in city B to 756 and the local DN set to 10. Set the
area code of the local network in city C to 752 and the local DN set to 20.
ADD LDNSET: LP=0, NC=K'86, AC=K'755, LDN="City A", DGMAPIDX=0,
MDGMAPIDX=0;
ADD LDNSET: LP=10, NC=K'86, AC=K'756, LDN="City B", DGMAPIDX=0,
MDGMAPIDX=0;
ADD LDNSET: LP=20, NC=K'86, AC=K'752, LDN="City C", DGMAPIDX=0,
MDGMAPIDX=0;
//Add call sources. Call sources 0 and 1 belong to the local DN set 0. Call source 10 belongs to
the local DN set 10. Call sources 20 and 21 belong to the local DN set 20.
ADD CALLSRC: CSC=0, CSCNAME="City A", PRDN=3, LP=0;
ADD CALLSRC: CSC=1, CSCNAME="City A", PRDN=3, LP=0;
ADD CALLSRC: CSC=10, CSCNAME="City B", PRDN=3, LP=10;
ADD CALLSRC: CSC=20, CSCNAME="City C", PRDN=3, LP=20;
ADD CALLSRC: CSC=21, CSCNAME="City C", PRDN=3, LP=20;

For details on how to configure the MGW data, see 4.2 Configuring Data to Interwork with
AMG (Through MGCP/H.248).
Step 3 Configure subscriber data.
//Add subscriber data of the local network in city A. Pay attention to the definitions of the local
DN set and the call source code.
EID="amg6540.com", STID=0, CODEC=PCMA, RCHS=65, CSC=0, NS=CLIP-1,
EID="amg8780.com", STID=0, CODEC=PCMA, RCHS=87, CSC=1, NS=CLIP-1,
NOTE
The call source code of 654000-6540159 is 0 (belongs to the local network in city A). The call source code
of 878000-8780159 is 1 (belongs to the local network in city A).
//Add subscriber data of the local network in city B. Pay attention to the definitions of the local
EID="amg3550.com", STID="0", CODEC=PCMA, RCHS=35, CSC=10, NS=CLIP-1,

NOTE
The call source code of 355000-3550159 is 10 (belongs to the local network in city B).
//Add subscriber data of the local network in city C. Pay attention to the definitions of the local
NOTE
The call source code of 282000-2820159 is 20 (belongs to the local network in city C).The call source code
of 399000-3990159 is 21 (belongs to the local network in city C).

//Add the prefixes of the local network in city A. Set the local DN set to 0.
SDESCRIPTION="City A_654", EA=NO;
SDESCRIPTION="City A_878", EA=NO;
ADD CNACLD: LP=0, PFX=K'0756355, CSTP=BASE, CSA=INTT, MINL=11, MAXL=11,
CHSC=0, SDESCRIPTION="To City B", EA=NO;
CHSC=0, SDESCRIPTION="To City C ", EA=NO;
CHSC=0, SDESCRIPTION="To City C", EA=NO;
NOTE
l For the called prefixes 654 and 878, Service attribute must be set to Intra-office, and Route selection
code must be set to 65535.
l For the called prefixes 0756 and 0752, Service attribute must be set to Intra-office national toll, and
Route selection code must be set to 65535.
//Add the prefixes of the local network in city B. Set the local DN set to 10.
SDESCRIPTION="City B_355", EA=NO;
CHSC=0, SDESCRIPTION="To City A", EA=NO;
NOTE
l For the called prefix 355, Service attribute must be set to Intra-office, and Route selection code must
be set to 65535.
//Add the prefixes of the local network in city C. Set the local DN set to 20.
SDESCRIPTION="City C_282", EA=NO;

SDESCRIPTION="City C_399", EA=NO;

CHSC=0, SDESCRIPTION="To City B", EA=NO;
NOTE
l For the called prefixes 282 and 399, Service attribute must be set to Intra-office, and Route selection
code must be set to 65535.
----End
Related tasks
None.
Related concepts
Figure 10-7 shows the relation among the call source, local DN set, and global DN set.
Figure 10-7 Relation among the call source, local DN set and global DN set
Call
source 0
Local DN set 0
Call
source 1
Call Global DN
Local DN set 10
source 10 set 0
Call
source 20
Local DN set 20
Call
source 21
10.7 Configuring MOIP Networking Data
Scenarios
The Multimedia of IP (MOIP) networking mode supports the access of multimedia terminals
without changing the original PSTN. The MOIP networking mode provides services such as
multimedia services, color ring back tone services, and call barring services. Figure 10-8 shows
the typical MOIP networking model.

Figure 10-8 MOIP networking model
MRS6100
MGCP
SHLR
CMT Platform (AIP)
IN service center
SoftX3000
MTP link
No.7 trunk circuit
UMG8900
SIP SIP
SIP SIP
WIFI terminal
hard terminal hard terminal
requirements:
l Multimedia subscribers can call each other.

l The UMG8900 provides two E1 circuits between the SoftX3000 and the PSTN switch.
l Two M2UA links are provided between the SoftX3000 and the UMG8900. The UMG8900
offers two 64-kbit/s MTP links to the PSTN switch. Each M2UA link carries SS7 signaling
traffic on one MTP link.
l Subscribers in the SoftX3000 office and in the PSTN switch office can call each other.
l The SoftX3000 interworks with the MRS6100 through the MGCP protocol. The SoftX3000
supports the playing of announcement for basic services, supplementary services, and IN
services, and supports digit collection of IN services.
l The phone lock service is enabled.
l The call barring service is enabled.
l The color ringback tone service and data service of the SoftX3000 mode are enabled.
Prerequisites
Conditions

Data
Before configuring the different types of service data, configure the following basic data:

l Equipment data
l Local office data
l Charging data
Equipment Data
l Equipment configuration
In this example, the SoftX3000 is configured with two basic frames. They are located at
frames 2 and 3 in the integrated configuration cabinet. Figure 10-9 shows the equipment
configuration of basic frame 2.
Figure 10-9 SoftX3000 equipment configuration (basic frame)
B B S H S H U U
Back F F I S I S P P
boards I I U C U C W W
I I I I I I R R
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
I I F F S S C C B B M M A U U
Front F F C C M M D D S S S S L P P
boards M M C C U U B B G G G G U W W
I I U U I I I I I I I I I R R
l Board information
Table 10-8 Basic information of major boards
Frame No./ Position Board Active/ Module No.

Slot No. Standby
0/0 Front IFMI Active 132
0/1 Front IFMI Standby 132
0/2 Front FCCU Active 22
0/3 Front FCCU Standby 22
0/12 Front BSGI Work 136

independently
0/13 Front BSGI Work 137

independently
0/14 Front MSGI Active 211
0/15 Front MSGI Standby 211
0/10 Front CDBI Active 102
0/11 Front CDBI Standby 102

Local Office Data

l SPC of the local office: national network SPC 001915
l Related information of local DN set 0 in global DN set 0: country code 65; no national area
code
l Related information of local DN set 1 in global DN set 1: country code 65; no national area
code
Charging Data
l Charging case 210: The calling party pays for the call. Different charging modes are defined
for different days.
For example, during normal workdays, when meter table 1 is used, from 18:00 to 8:00, the
meter counts one time for the first 30 seconds, and then counts one time every 60 seconds;
from 8:00 to 18:00, the meter counts one time for the first 60 seconds, and then counts one
time every 90 seconds.
l Charging case 10: The called party pays for the call. Different charging modes are defined
for different days.
For example, during normal workdays, when meter table 1 is used, from 18:00 to 8:00, the
meter counts one time for the first 30 seconds, and then counts one time every 60 seconds;
from 8:00 to 18:00, the meter counts one time for the first 60 seconds, and then counts one
time every 90 seconds.
Interworking data
consistent between the SoftX3000 and the PSTN switch.

No.
1 Protocol used for interworking between the H.248

SoftX3000 and the UMG8900
2 H.248 code type ASN.1 (binary mode)

4
4 H.248 IP address of the UMG8900 10.161.128.45/255.255.255.22

4
5 SIGTRAN IP address of the UMG8900 10.161.128.45/255.255.255.22

4
6 Local UDP port number of H.248 on the 2944

SoftX3000 side
7 Local UDP port number of H.248 on the 2944

UMG8900 side


No.
8 Speech codecs supported by the UMG8900 G.711A, G.711μ, G.723.1, G.

729, G726, T38, AMR, H261,
H263, MPEG4
9 Whether the UMG8900 supports hairpin Yes

connection
10 Whether the UMG8900 supports the EC Yes

function
11 Whether the UMG8900 supports the detection Yes

of fax and modem signal tones
12 Whether the UMG8900 supports the T.38 Yes

protocol
13 E1 numbering plan on the UMG8900 side Starting from 0
14 Numbering plan of termination ID (E1 timeslot) Starting from 0

of the UMG8900
15 E1 numbers of the SS7 trunk group on the 2-3

SoftX3000 side
16 E1 IDs corresponding to the SS7 trunk group on 0-1

the UMG8900 side
17 Local SCTP port number of M2UA links on the Link 0: 2907

SoftX3000 side (client) Link 1: 2905
18 Local SCTP port number of M2UA links on the Link 0: 2907

UMG8900 side (server) Link 1: 2905
19 Interface ID (integer) of MTP link 0 0
20 Interface ID (integer) of MTP link 1 1
No.
2 SPC of the PSTN switch 000500 (national network)
3 Type of signaling used for SS7 trunks ISUP
4 Circuit identification code for SS7 trunk circuits 0-63

consistent between the SoftX3000 and the MRS6100.
Table 10-11 Data for interworking between the SoftX3000 and the MRS6100
No.
1 Protocol used for interworking between the MGCP

SoftX3000 and the MRS6100
3 Domain name of the external MRS6100 MRS6100.huawei.com

24
4 IP address of the MCCU of the MRS6100 10.161.128.40/255.255.255.2

24
5 Local UDP port number on the SoftX3000 side 2427
6 Speech codecs supported by the MRS6100 G771A, G771u, G723.1
Color Ringback Tone Service data
Table 10-12 Data for interworking between the SoftX3000 and the CRBT server
No.
1 IP address of the IFMI of the SoftX3000 10.161.128.36/

255.255.255.224
2 IP address of the SG that the SoftX3000 10.161.128.40/

interworks with 255.255.255.224
3 Module number of the BSGI of the SoftX3000 136, 137
4 SPC of the SoftX3000 (local office) 001915
5 SPC of the SHLR (destination) 00191C
6 Number of the subsystem between the SoftX3000 MSC, HLR

and the SHLR
7 SCTP port number on the SoftX3000 side Link 0: 2905

Link 1: 2906
8 Application mode of the SoftX3000 in SCTP Client

association
9 Routing context 0
Documents

Before configuring the MOIP networking data, you must plan the related data based on the
Workflow
The procedure for configuring the MOIP networking data is as follows:
1. Get offline.
2. Configure equipment data.
4. Configure charging data.
5. Convert data format and getting online.
6. Configure SIP data.
10. Configure MTP data.
13. Configure number analysis data.
14. Configure data for interworking with MRS6100.
15. Configure phone lock service.
16. Configure color ringback tone service in softswitch mode.
Procedure
Step 1 Get offline.
//Get offline.
LOF:;
//Set the format conversion switch to OFF.

SET FMT: STS=OFF;
Step 2 Configure equipment data.

//Add a rack with the rack number 0.
ADD SHF: SHN=0, LT=" SingTel-MIO", ZN=0, RN=0, CN=0;
//Add the frame numbered 0 to position 2.

//Add boards with their auxiliary boards in the adjacent slots.

ADD BRD: FN=0, SLN=0, LOC=FRONT, FRBT=IFMI, MN=132, ASS=1;
ADD BRD: FN=0, SLN=12, LOC=FRONT, FRBT=BSGI, MN=136, ASS=255;
ADD BRD: FN=0, SLN=10, LOC=FRONT, FRBT=CDBI, MN=102, ASS=11;

NOTE
l Module numbers of the SMUI boards: 2-21 in ascending order is recommended.

l Module numbers of the FCCU boards: 22-101 in ascending order is recommended.
l Module numbers of the CDBI boards: 102-131 in ascending order is recommended.
l Module numbers of the IFMI boards: 132-135 in ascending order is recommended.
l Module numbers of the BSGI boards: 136-211 in ascending order is recommended.
l Module numbers of the MSGI boards: 211-136 in descending order is recommended.
l Module numbers of the MRCA boards: 212-247 in ascending order is recommended.
l Typically, the BSGIs work in load sharing mode. That is, one module number is configured for one
board. Therefore, set Assistant slot number to 255.
//Add an expansion frame for connecting more subscribers or for distinguishing subscribers of
various attributes.
//Add an IFMI FE port, with the default gateway address being the IP address of the router.
ADD FECFG:MN=132, IP="10.161.128.36", MSK="255.255.255.224",
DGW="10.161.128.33";
NOTE
Set the IP address of the default router (gateway) of the FE port correctly. Otherwise, the SoftX3000 fails
to communicate with other network elements through IP.
//Add the central database function. Set CDBI module number to 102.
ADD CDBFUNC:CDPM=102,
FCF=LOC-1&TK-1&MGWR-1&BWLIST-1&IPN-0&DISP-1&SPDNC-1&RACF-0&PRESEL-1&UC-0&
KS-0;
NOTE
If the system is equipped with two pairs of CDBIs, allocate the database functions to the two groups of
CDBIs according to the load sharing principle. The configuration of the two pairs of CDBIs must be the
same. If the system is equipped with only one pair of CDBIs, allocate all the database functions to it.
//Configure local office information. The SPC of the local office is 001915 (national network).
SET OFI: OFN=" SingTel-MIO", LOT=CMPX, NN=YES, SN1=NAT, SN2=NAT, SN3=NAT,
SN4=NAT, NPC="001915", INS=SP14, IN2S=SP24, NNS=SP14, NN2S=SP14, SPF=YES,
STP=YES, TMZ=21;
//Add a toll prefix, with the country code 65, national call prefix 0, and international call prefix
00.
ADD PFXTOL: NC=K'65, NTP=K'0, ITP=K'00;
//Add a national area code, with the global DN set 0, country code 65, national area code E (E
indicates that there is no national area code), city name Singapore, and district code 0.
ADD ACODE: NC=K'65, AC=K'E, AN="Singapore", DC=0;
//Add a country code or region code. Add a country code with global DN set 1.

ADD NCODE: P=1, NC=K'65, NN="Singapore";

ADD PFXTOL: P=1, NC=K'65, NTP=K'0, ITP=K'00;
ADD ACODE: P=1, NC=K'65, AC=K'E, AN="Singapore", DC=0;
//Add digitmap data for local DN set 0 that belongs to global DN set 0.
ADD DMAP: PROTYPE=H248, DMAPIDX=0, PARTIDX=0, DMAP="[689]xxxxxxx|
00xxxxxxxxx|1800xxxxxxxx|99x|E|F|x.F|[0-9].L";
ADD DMAP: PROTYPE=MGCP, DMAPIDX=0, PARTIDX=0, DMAP="[689]xxxxxxx|
1800xxxxxxxx|00xxxxxxxxx|99x|*|#|x.#|[0-9*#].T";
ADD LDNSET: LP=0, NC=K'65, AC=K'E, LDN="SingTel-MIO-0", DGMAPIDX=0,
MDGMAPIDX=0, CN="SG";
//Add digitmap data for local DN set 1 that belongs to global DN set 1.
ADD DMAP: PROTYPE=H248, DMAPIDX=1, PARTIDX=0, DMAP="[3689]xxxxxxx|7xxxxxx|
1xx|0xxxxxxx|99x|E|F|x.F|[0-9].L";
ADD DMAP: PROTYPE=MGCP, DMAPIDX=1, PARTIDX=0, DMAP="[3689]xxxxxxx|7xxxxxx|
1xx|0xxxxxxx|99x|*|#|x.#|[0-9*#].T";
ADD LDNSET: LP=1, P=1, NC=K'65, AC=K'E, LDN="SingTel-MIO-1", DGMAPIDX=1,
MDGMAPIDX=1, CN="SG";
//Add call sources.

ADD CALLSRC: CSC=0, CSCNAME="SingTel-MIO-2", PRDN=3;
ADD CALLSRC: CSC=210, CSCNAME=" SingTel-MIO-1";
ADD CALLSRC: CSC=104, CSCNAME=" SingTel-MIO-0";
Step 4 Configure charging data.

//Add date categories. Set August 9, 2006 to category 2 and December 25, 2006 to category 2.
ADD DCAT: YEAR=2006, MON=AUG, DAY=9, DAT=DTYPE2;
ADD DCAT: YEAR=2007, MON=DEC, DAY=25, DAT=DTYPE2;
NOTE
l The date category is configured to define national and religious holidays as special days, during which
the subscribers can enjoy charging discount.
l The system defines six types of dates: normal workday, and categories 1 to 5. The date category is
obtained from the date category table and week category table. If the date category is different in the
two tables, the one with higher priority is used. The priority from highest to lowest is category 5,
category 4, category 3, category 2, category 1, and normal workday.
l By default, the date category is null and the week category is predefined. Monday, Tuesday,
Wednesday, and Thursday belong to Normal workday; Friday belongs to Category 1; Saturday and
Sunday belong to Category 2.
l To modify the date category, run ADD DCAT.
//Modify the week category. Set Date category of Friday to Normal workday.
MOD WCAT: WD=FRI, DAT=NORMAL;
NOTE
l By default, the week category is predefined. Monday to Thursday are normal workdays; Friday is
category 1; Saturday and Sunday are category 2.
l To modify the default value of the week category, run MOD WCAT. For example, for an office which
adopts the offline charging, the date category of all days must be set to Normal workday. In such a
case, run MOD WCAT to change Date category of Friday, Saturday, and Sunday to Normal
workday.
Two charging methods are configured in the given example below:

l Caller charging

//Add charging case 210. Set Payer to Calling party.

ADD CHGANA: CHA=210, CHGT=ALL;
PB1=1, TS2=18&00, TA2="60", PA2=1, TB2="90", PB2=1;
MOD CHGMODE: CHA=210, DAT=DTYPE2, TA1="60", PA1=1, TB1="60", PB1=1;
//Add charging case index data.
ADD CHGIDX: CHSC=104, RCHS=210, LOAD=ALL, BT=ALLBT, CODEC=ALL,
CHA=210;
ADD CHGIDX: CHSC=106, RCHS=210, LOAD=ALL, BT=ALLBT, CODEC=ALL,
CHA=210;
l Callee charging
//Add charging case 10. Set Payer to Called party.
ADD CHGANA: CHA=10, PAY=CALLED, CHGT=ALL;
//Modify the charging mode.
PB1=1, TS2=18&00, TA2="60", PA2=1, TB2="90", PB2=1;
MOD CHGMODE: CHA=10, DAT=DTYPE2, TA1="60", PA1=1, TB1="60", PB1=1;
//Add callee group charging data.
ADD CHGCLD: DCHS=10, LOAD=ALL, CODEC=ALL, CHA=10;
Step 5 Convert data format and getting online.
//Set the format conversion switch to ON.

SET FMT: STS=ON;
//Convert the data format.

FMT:;
//Get online.
LON:;
Step 6 Configure SIP data.
//Add SIP local port number, with the MSGI module number 210 and port number 5062.
//Add the protocol dispatch function. Set the MSGI module number to 210, and protocol dispatch
ability to STUN.
SET DPA: MN=210, DA=STUN-1;
//Add another SIP local port number, with the MSGI module number 211 and port number 5061.
//Add the protocol dispatch function. Set the MSGI module number to 211, and protocol dispatch
ability to STUN.
SET DPA: MN=211, DA=STUN-1;
//Add STUN protocol dispatch information. Set the IFMI module number to 132.

//Set SIP global configuration. Start the heartbeat timer, with the maximum registration expiry
duration being 10 minutes.
SET SIPCFG: UST=YES, MRX=10;
NOTE
l Each MSGI board is configured with a unique local port number. For the first SIP message sent from
the local office, the system specifies a port number to receive the response from the peer, and the
outgoing SIP message packet carries that port number. The port number specified is the local port
number of the MSGI. On receiving the returned SIP message packet, the IFMI dispatches it to the
MSGI according to the port number carried in the message packet.
l For the first SIP message from other offices, usually, the well-known port number, 5060, is carried.
The IFMI dispatches the first SIP message packet to one of the MSGIs according to the load sharing
principle. The MSGI receives the first SIP message packet, processes it, and returns an outgoing SIP
message packet, which carries a port number to receive responses from the peer. For the subsequent
SIP message packets in the same call procedure, that local port number is used for communication.
l When you run ADD BRD to add boards, the protocol dispatch ability for the BSGI and MSGI has
automatically been set by the system. The default values are:
l BSGI: MGCP, H.248 and SCTP
l MSGI: TRIP, STUN, MIDCOM, Original call, iDo, SMC
Generally, you can use the default settings directly. To enable a module to dispatch one or several
protocols, run SET DPA. For example, in normal cases, the MSGI can dispatch TRIP, STUN,
MIDCOM, Original call, iDo and SMC simultaneously. You can enable an MSGI to dispatch one
protocol such as STUN by running SET DPA.

//Add a batch of multimedia devices.
ADB MMTE: SEID=K'62370000, EEID=K'62370099, MN=22, IMSFLAG=NO, IFMMN=132,
PT=SIP, AT=ABE, PASS="12345678";
ADB MMTE: SEID=K'62370100, EEID=K'62370199, MN=22, IMSFLAG=NO, IFMMN=132,
PT=SIP, AT=ABE, PASS="12345678";
//Add a batch of multimedia subscribers.

RCHS=210, CSC=104, NS=CLIP-1, CTXA=NO, PBXA=NO, CA=NO, EA=NO;
RCHS=210, CSC=104, NS=CLIP-1, CTXA=NO, PBXA=NO, CA=NO, EA=NO;

//Add a UMG that adopts H.248. Set Equipment ID to 10.161.128.45:2944.
ADD MGW: EID="10.161.128.45:2944", GWTP=UMGW, MGWDESC="UMG-MOIP-OC",
MGCMODULENO=22, LA="10.161.128.36", RA1="10.161.128.45",
RP=2944,LISTOFCODEC=PCMA-1&PCMU-1&G729-1&G7231-1&G726-1&T38-0&AMR-1&H261-
1&H263-1&MPEG4-1, HAIRPIN=S, CODETYPE=ASN;

NOTE
l Set Remote address to the IP address of the UMG8900 used for the H.248 protocol, that is,
10.161.128.45.
l The UMG8900 adopts the H.248 protocol that supports only the binary code. Therefore, set Code
type to ASN.1.
l The UMG8900 supports the hairpin connection function. Therefore, Hairpin connection must be set
to Supported.
l The UMG8900 supports EC, fax, and modem functions. Therefore, use the default values of the options
EC, No Fax and No Modem in the parameter Special attributes and set EC to the default value.

//Add an embedded SG. Set SG ID to 0, SG name to UMG-MOIP-OC, SG type to emb, and
Equipment ID to 10.161.128.45:2944.
ADD SG: SGID=0, SGNAME="UMG-MOIP-OC", SGTYPE=emb,
EID="10.161.128.45:2944";
NOTE
In this example, the embedded SG in the UMG8900 is used to process the M2UA protocol. Therefore, SG
type must be set to Embedded SG, and Equipment ID must be set to the equipment ID of the UMG8900.
In this example, Equipment ID is set to 10.161.128.45:2944.
//Add two M2UA Linksets. Set M2UA linkset index to 0 and 1 respectively. Set SG ID to 0.
ADD M2LKS: M2LSX=0, LSNAME="SX-UMG01-01", SGID=0;
ADD M2LKS: M2LSX=1, LSNAME="SX-UMG01-02", SGID=0;
//Add two M2UA links. The SoftX3000 is the client. The local SCTP port number of link 0 of
module 136 is 2907 and that of link 1 of module 137 is 2905.
ADD M2LNK: MN=136, LNKN=0, M2LSX=0, LOCPORT=2907, LOCIP1="10.161.128.36",
PEERPORT=2907, PEERIP1="10.161.128.45";
ADD M2LNK: MN=137, LNKN=1, M2LSX=1, LOCPORT=2905, LOCIP1="10.161.128.36",
PEERPORT=2905, PEERIP1="10.161.128.45";
NOTE
l Set Peer IP address to the IP address of the UMG8900 used for the SIGTRAN protocol, that is,
10.161.128.45.
l To ensure the reliability of M2UA links, allocate M2UA links destined for the same embedded SG to
different BSGI modules.
Step 10 Configure MTP data.

//Add an MTP DSP. Set DSP index to 20, representing a PSTN switch.
ADD N7DSP: DPX=20, DPC="000500",OPC="001915", DPNAME="UMG01-NTY",
STPF=YES;
//Add an MTP Linkset.

ADD N7LKS: LSX=0, ASPX=20, LSNAME="UMG01-NTY";
//Add two MTP links. For MTP link 0, the SS7 signaling traffic is carried on M2UA link 0 of
module 136; the interface ID is 0; the signaling link code is 0; the start circuit termination ID is
144. For MTP link 1, the SS7 signaling traffic is carried on M2UA link 0 of module 137; the
interface ID is 1; the signaling link code is 0; the start circuit termination ID is 1296.
ADD N7LNK: MN=136, LNKN=0, LNKNAME="UMG01-NTY", LNKTYPE=M64K, M2LSX=0,

ADD N7LNK: MN=137, LNKN=1, LNKNAME=" UMG01-NTY ", LNKTYPE=M64K, M2LSX=1,

//Add an MTP route.

ADD N7RT: LSX=0, DPX=20, RTNAME="UMG01-NTY";

//Add an office direction destined for the PSTN switch. Set Office direction number to 0 and
Destination point code 1 to 000500.
ADD OFC: O=0, ON="UMG01-PLYF", DOT=CMPX, DOL=SAME, DPC1="000500";
NOTE
l To avoid alternate routing between offices of the same level, set one office to a lower level. For example,
if the local office is a tandem office and the peer office is an end office, set Peer office level to
LOW.
l This office direction has SS7 trunk circuits. Therefore, you must specify DPC. Otherwise, errors occur
when you add an SS7 trunk group by running ADD N7TG.
//Add a subroute.
ADD SRT: SRC=0, O=0, SRN="UG1-PLYF", RENT=URT;
//Add a route.
ADD RT: R=0, RN=" UG1-PLYF ", SR1=0, TRIPFLAG=NO;
//Add analysis data of the route destined for the PSTN switch. Set Route selection code to 0.
NOTE
Set Caller category, Nature of callee address indicator, Caller access, and Transmission capability to
All, unless specified otherwise.

//Add an SS7 trunk group. Trunk group 0 is bidirectional. Singapore specifications are adopted.
ADD N7TG: TG=0, EID="10.161.128.45:2944", G=INOUT, SRC=0, SOPC="001915",
SDPC="000500", TGN="PLYF", PRTFLG=SG, NOAA=FALSE, ISM=FALSE, EA=FALSE;

ADD N7TKC: MN=22, TG=0, SC=1, EC=15, SCIC=1, TID="1";
ADD N7TKC: MN=22, TG=0, SC=17, EC=31, SCIC=17, TID="17";

CHSC=104, SDESCRIPTION="Mobile Service-IG", EA=YES, CALLCODEC=G7231-0,
ASF=NO, QCDN=NO, VPNF=NOVC;
CHSC=104, SDESCRIPTION="Mobile Service-IG", EA=YES, CALLCODEC=G7231-0,
ASF=NO, QCDN=NO, VPNF=NOVC;
//Modify a call source code. Set Failure source code to 1.

MOD CALLSRC: CSC=104, LP=0, FSC=1;

//Add number change data.

ADD DNC: DCX=1, DCT=INS, ND=K'A;
//Add call failure processing data.

ADD CFPRO: LP=0, PFX=K'63726, FCC=DPF, FSC=1, FPT=CPA, DCX=1;
ADD CFPRO: LP=0, PFX=K'63729, FCC=DPF, FSC=1, FPT=CPA, DCX=1;
//Add special called number change data.

ADD SPDNC: LP=0, PFX=K'63726, DCT=MOD, DCL=5, ND=K'62178888;
ADD SPDNC: LP=0, PFX=K'63729, DCT=MOD, DCL=5, ND=K'92000345;
Step 14 Configure data for interworking with MRS6100.

//Add a voice media gateway. Set Equipment ID to MRS6100.huawei.com.
ADD MGW: EID="MRS6100.huawei.com", GWTP=MRS, MGWDESC="MRS6100",
MGCMODULENO=22, PTYPE=MGCP, LA="10.161.128.36",RA1="10.161.128.40",
RP=2427, MRSLISTOFCODEC=G729-1;
MOD MGW: EID=" MRS6100.huawei.com ", LISTOFCODEC=PCMA-1&PCMU-1&G7231-1;
NOTE
l The SoftX3000 regards the MRS as a voice media gateway. Therefore, adding an MRS gateway means
adding a voice media gateway. When running ADD MGW to add an MRS gateway, pay attention to
the following points: Equipment ID must be consistent with the domain name of the external MRS.
Gateway type must be MRS. Protocol type must be MGCP. Local IP address is the external IP
address of the corresponding IFMI (defined by running ADD FECFG).
l The MRS6100, as a whole, functions as an independent MRS. Therefore, if the external MRS is the
MRS6100, Remote IP address 1 is the IP address of the MCCU board in the MRS6100.
l Remote port is the local UDP port number on the SoftX3000 side. The configuration principles for
the parameter are as follows: If the media gateway adopts MGCP, the remote port number is 2427 by
default; if the media gateway adopts H.248, the remote port number is 2944 by default.
Step 15 Configure phone lock service.

Assume that a subscriber number is 62370001. Through the phone lock service configuration,
the subscriber with this number should not be able to make calls to intra-office subscriber B or
international toll subscriber C
ADD CNACLD: PFX=K'63071, CSA=LCO, RSC=74,MINL=8, MAXL=8, CHSC=104, EA=NO;
ADD CNACLD: PFX=K'1501, CSA=ITT, RSC= 16, MINL=4, MAXL=21, CHSC=0, EA=NO;
//Configure the call-out authority of the call prefixes.

SET PFXOCR: K=K11, OCR=LCO-1&LC-1&LCT-1&NTT-1&ITT-1;
SET PFXOCR: K=K12, OCR=LCT-1&NTT-1&ITT-1;
//Modify multimedia subscriber data. Set Subscriber number to 62370001 and Local DN set
to 0.
MOD MSBR: D=K'6237001, LP=0, RCHS=210, CSC=104,
ICR=LCO-1&LC-1&LCT-1&NTT-1&ITT-1, OCR=LCO-1&LC-1&LCT-1&NTT-1&ITT-1,
NS=CLIP-1&PWCB-1, CTXA=NO, PBXA=NO, CA=NO, EA=YES, CUGU=NO, K=K11;
NOTE
In the preceding example, if K value is set to K11, the subscriber whose number is 62370001 cannot call
subscribers whose numbers are 63071xx or 1501xxx.
Step 16 Configure call barring service (implemented through configuring call barring group data).

Through the configuration of call barring groups, it is required that the following call barring
services in the MOIP networking are implemented for subscribers A, B, C, and D:
l A cannot call C, but A can call D.
l B cannot call C or D.
//Configure inter-group call barring indication data. Set Source call barring group number to
9, Destination call barring group number to 106, and Call indication to Barring call.
SET GRPAC: SRG=9, DRG=106, CI=CDIS, SIG=NO;
//Configure inter-group call barring indication data. Set Source call barring group number to
3, Destination call barring group number to 110, and Call indication to Barring call.
//Modify multimedia subscriber data.

ICR=LCO-1&LC-1&LCT-1&NTT-1&ITT-1,OCR=LCO-1&LC-1&LCT-1&NTT-1&ITT-1,
NS=CLIP-1, CTXA=NO, PBXA=NO, CA=NO, EA=YES, LMTGRP=9, CUGU=NO;
ICR=LCO-1&LC-1&LCT-1&NTT-1&ITT-1, OCR=LCO-1&LC-1&LCT-1&NTT-1&ITT-1,
NS=CLIP-1, CTXA=NO, PBXA=NO, CA=NO, EA=YES, LMTGRP=3, CUGU=NO;
//Add called number barring group data. Set Group category to Ordinary group, and Called
barring group number to 106 and 110 respectively.
ADD CLDGRP: CLD=K'66917, GRPT=OG, GRP=106, NAME="PAYPHONE";
ADD CLDGRP: CLD=K'012, GRPT=OG, GRP=110, NAME="IDD";
NOTE
Through the preceding configuration, the following can be achieved:

l Subscriber whose number is 62370110 cannot call subscribers whose numbers are 66917XXX, but can
call subscribers whose numbers are 012XXX.
l Subscriber whose number is 62370111 cannot call subscribers whose numbers are 66917XXX or
012XXX.
Step 17 Configure color ringback tone service in softswitch mode.

//Add M3UA local entity data. Set Local entity point code to 001915.
ADD M3LE:LEX=0, LENAME="SX_TB_SHLR_OC", OPC="001915", LET=AS, RC=0;
//Add M3UA destination entity data.
ADD M3DE: DEX=0, LEX=0, DENAME="SX_TB_SHLR_OC", DPC="00191C", DET=AS;
//Add an M3UA Linkset. Set Adjacent entity index to 0 and Word mode to ASP.
ADD M3LKS: LSX=0, LSNAME="SX_TB_SHLR_OC", ADX=0, TM=LOADSHARE, WM=ASP;
//Add two M3UA links. Set Module number to 136 and 137 respectively.
ADD M3LNK: MN=136, LNKN=0, LNKNAME="SX_TB_SHLR_OC_05",
LOCIP1="10.161.128.36", LOCPORT=2905, PEERIP1="10.161.128.40", CS=C,
LSX=0, ASF=STD;
ADD M3LNK: MN=137, LNKN=1, LNKNAME="SX_TB_SHLR_OC_06",
LOCIP1="10.161.128.36", LOCPORT=2906, PEERIP1="10.161.128.40", CS=C,
LSX=0, ASF=STD;
//Add M3UA route data. Set Destination entity index to 0 and Linkset index to 0.
ADD M3RT: RTNAME="SX_TB_SHLR_OC", DEX=0, LSX=0;

2. Configure SCCP signaling data to interwork with the SHLR.

//Add SCCP DSP data.
ADD SCCPDSP: DPX=0, NI=NAT, DPC="00191C", OPC="001915",
DPNAME="SX_TB_SHLR_OC", SHAREFLAG=NONE;
//Add SCCP subsystem numbers.
ADD SCCPSSN: SSNX=0, NI=NAT, SSN=MSC, SPC="001915", OPC="001915";
ADD SCCPSSN: SSNX=1, NI=NAT, SSN=MSC, SPC="00191C", OPC="001915";
ADD SCCPSSN: SSNX=2, NI=NAT, SSN=HLR, SPC="001915", OPC="001915";
ADD SCCPSSN: SSNX=3, NI=NAT, SSN=HLR, SPC="00191C", OPC="001915";
3. Configure service data to interwork with the SHLR.
//Add SHLR local address data.
ADD SHLRLA: SHLRAddrIndex=0, SHLRDESC="SX_TB_SHLR_OC", RT=DPC,
OPC="001915", SSN=MSC;
//Add SHLR remote address data.
ADD SHLRRA: SHLRAddrIndex=0, RT=DPC, DPC="00191C", SSN=HLR;
//Add SHLR group data.
ADD SHLRGRP: SHLRGrpNumber=0, SelectMode=STB, SHLRIDX1=0;
//Modify the call source code. Set Call source code to 104 and SHLR selection source
code to 0.
MOD CALLSRC: CSC=104, SHLRSSC=0;
//Add an IN call prefix. Set Call prefix to 64145200 and Service attribute to Local.
ADD CNACLD: PFX=K'64145200, CSTP=BASE, CSA=LC, RSC=1, MINL=16,
MAXL=16, CHSC=0, SDESCRIPTION="SMT", EA=YES, SHLRSLC=0,
SSCRBT=CALLEDSSCRBT, ASF=NO, QCDN=NO, VPNF=NOVC;
//Add SHLR configuration data.
ADD SHLRCFG: SHLRSLC=0, SHLRSSC=0, CLTP=ALLTYPE, SHLRCFGIDX=0,
QTYPE=STD, OVRPFLGSTD=NO, SHLRGRPNOSTD=0;
----End
Related tasks
None
Related concepts
None
10.8 Configuring Data for Blended Application of Public

and Private Networks
Scenarios
Using the relevant software, the SoftX3000 can support the blended application mode of public
and private networks in the same office. That is, one office can be logically divided into the
public network application and the private network application to meet a carrier's requirement
for inter-network networking. Figure 10-10 shows the networking for this application.

Figure 10-10 Networking for the blended application of public and private networks in the
SoftX3000
SoftX3000 U-Path
Exchange in Exchange in
TMG8010 TMG8010 private network
public network
AMG AMG
POTS POTS POTS POTS

Subsciber accessed Subsciber accessed
in public network in private network
requirements:
l The subscribers in the public network of the local office are numbered according to the
numbering plan of the public network. The numbers consist of seven digits. The subscribers
in the private network of the local office are numbered according to the numbering plan of
the private network. The numbers consist of five digits. Certain subscribers in the private
network may also use the number resources of the public network.
l When calling other public network subscribers in the local office or in other offices, the
public network subscriber in the local office adopts the dialing mode stipulated in the public
network. When calling other private network subscribers in the local office or in other
offices, the private network subscriber in the local office adopts the dialing mode stipulated
in the private network.
l When calling the public network subscribers, the private network subscriber in the local
office must dial 10 before dialing the called number.
l In all cases, all the subscribers in the local office can dial emergency numbers such as 110,
119, 120, and 122.
l When a private network subscriber in the local office who uses public network number
resources calls a public network subscriber, the local office sends the caller's public network
number to the public network. If the private network subscriber does not use public network
number resources, the local office sends the calling number 2589999 to the public network.
l When a public network subscriber in the local office or another office calls a private network
subscriber in the local office who does not use public network number resources, the caller
should first dial the access code 2589999 of the computer console (U-Path). After the call
is connected, the U-Path prompts the caller to dial the number again to call the callee.

Prerequisites
Conditions

Data
Table 10-13 Data need to be planned for the blended application of public and private networks

No.
1 Global DN set used by the local office on the public 0

network side
2 SPC of the local office in the public network 001122 (national network)
3 Area code of the local office in the public network 0755
4 Public network number resources (with seven- 2580000-2589999

digit length) used by the local subscribers 2590000-2599999
5 Global DN set used by the local office on the 1

private network side
6 SPC of the local office in the private network 001234 (national reserved
network)
7 Area code of the local office in the private network 052
8 Private network number resources (with five-digit 20000-29999

length) used by the local subscribers 30000-39999
9 Private network subscribers who use both private Private network:

and public network number resources 20000-29999
Public network:
2580000-2589999
10 Local DN set used by the public network 0

subscribers in the local office
11 Local DN set used by the private network 10

subscribers in the local office
12 Telephone number of the U-Path Short number: 90000

Long number: 2589999
In this example, assume that the U-Path is used to transfer all the incoming traffic from the public
network to the private network subscribers.

l The U-Path must be located in the Centrex group, but the private network subscribers of
the local office are not in the Centrex group. Therefore, to enable the U-Path to call the
subscribers outside the Centrex, run ADD ICXPFX to set the service attributes of the intra-
Centrex group prefixes 2 and 3 to Emergency outgoing prefix.
l The short numbers of the Centrex group where the U-Path is located cannot begin with 2
or 3. Assume the short numbers begin with 9.
Documents
Before configuring the blended application of public and private networking data, you must plan
the related data based on the requirements in the Specifications for Data Configuration provided
by the Global Technical Service Department of Huawei.
Workflow
The procedure for configuring the blended application of public and private networking data is
as follows:
3. Configure Centrex data (Including U-Path).
4. Configure number analysis data (intra-Network call).
5. Configure number analysis data (calls from public network to private network).
6. Configure number analysis data (calls From private network to public network).
7. Configure number analysis data (calling number analysis when the private network
subscriber calls the public network subscriber).
Procedure
//Configure local office information. The SPCs of the local office are 001122 (national network)
and 001234 (national reserved network).
SET OFI: OFN="SoftX3000", LOT=CMPX, NN=YES, NN2=YES, SN1=NAT, SN2=NAT2,
NPC="001122", NP2C="001234", NNS=SP24, NN2S=SP24, SPF=YES, TMZ=21;
NOTE
The local office is located in the two signaling networks: the public and private networks. Therefore, the
related information in the local office information table must be defined correctly.
//Add the country/region code, with the global DN set being 1 (used for the private network)
and the country code being 86.
ADD NCODE: P=1, NC=K'86, NN="China";
NOTE
The system automatically configures global DN set 0 during the initialization. Therefore, it is not required
to configure the global DN set 0 again.
//Add the description of the toll call prefix.

//Add national area codes, with the global DN set being 1.

ADD ACODE: P=1, NC=K'86, AC=K'51, AN="City A", DC=0;

ADD ACODE: P=1, NC=K'86, AC=K'52, AN="City B", DC=0;
ADD ACODE: P=1, NC=K'86, AC=K'53, AN="City C", DC=0;
ADD ACODE: P=1, NC=K'86, AC=K'54, AN="City D", DC=0;
ADD ACODE: P=1, NC=K'86, AC=K'55, AN="City E", DC=0;
NOTE
l During initialization, the system presets the national area code table for the global DN set 0. This table is
usually used for the public network and need not be configured again.
l All the national area codes must be configured for the global DN set 1 according to the national area code
planning table of the private network. For the convenience of description, the configuration here is only an
example.
//Add the digitmap configurations of the local DN sets 0 and 10.

ADD DMAP: PROTYPE=MGCP, DMAPIDX=0, PartIDX=0, DMAP="[2-8]xxxxxx|
13xxxxxxxxx|013xxxxxxxxx|00xxxxxxxxx|010xxxxxxxx|02xxxxxxxxx|0[3-9]
xxxxxxxxx|9xxxx|1[0124-9]x|E|F|x.F|x.L";
ADD DMAP: PROTYPE=H248, DMAPIDX=0, PartIDX=0, DMAP="[2-8]xxxxxx|
xxxxxxxxx|9xxxx|1[0124-9]x|*|#|x.#|x.T";
ADD DMAP: PROTYPE=H248, DMAPIDX=1, PartIDX=0, DMAP="[2-8]xxxx|0xxxxx|
10xxx|1[124-9]x|E|F|x.F|x.L";
ADD DMAP: PROTYPE=MGCP, DMAPIDX=1, PartIDX=0, DMAP="[2-8]xxxx|0xxxxx|
10xxx|1[124-9]x|*|#|x.#|x.T";
NOTE
In the example, the digitmap of local DN set 10 (private network subscriber) is briefly defined. In the
deployment of an office, it should be configured according to the carrier's dialing plan.
//Add local DN sets. The local DN set 0 belongs to the global DN set 0, and the local DN set 10
belongs to the global DN set 1.
ADD LDNSET: LP=0, P=0, NC=K'86, AC=K'755, LDN="For PSTN", DGMAPIDX=0,
MDGMAPIDX=0;
ADD LDNSET: LP=10, P=1, NC=K'86, AC=K'52, LDN="For PSTN", DGMAPIDX=1,
MDGMAPIDX=1;
NOTE
Parameters DN set, Local DN set, Country/Region code, and National area code must be correctly
defined.
//Add call sources. Call source 0 belongs to the local DN set 0, and call source 10 belongs to the
local DN set 10.
ADD CALLSRC: CSC=0, CSCNAME="For PSTN", PRDN=3, LP=0;
ADD CALLSRC: CSC=10, CSCNAME="For Special", PRDN=2, LP=10;
NOTE
l Call source code 0 is used for the public network subscribers in the local office and the trunks connecting
the local office to the public network. The number of the pre-collected digits is 3.
l Call source code 10 is used for the private network subscribers in the local office and the trunks
connecting the local office to the private network. The number of the pre-collected digits is 2.

//Add subscriber data for the public network. Pay attention to the definitions of the local DN set
and call source code.


//Add subscriber data for the private network. Pay attention to the definitions of the local DN
set and call source code.
NOTE
The call-in and call-out authority of the private network subscribers should be defined based on the actual
conditions.
Step 3 Configure Centrex data (including U-Path).

//Add a Centrex group, with the Centrex group number being 100, outgoing prefix being 10, and
subscriber capacity being 10.
ADD CXGRP: CGN="For U-Path", CXG=100, UCPC=10, WACF=NO, BIF=NO;
//Add a Centrex subgroup. Set Centrex subgroup number to 5.

ADD CXSUBGRP: CXG=100, CXSG=5, CXSGN="U-Path subgroup";
//Add a Centrex out-group prefix. Set Out-group prefix to 0.

ADD OCXPFX: CXG=100, OGP=K'10, DOD2=YES;
//Add an intra-Centrex group prefix (short number), with the prefix being 9 and the maximum
and minimum number lengths being 5.
ADD ICXPFX: CXG=100, PFX=K'9, CSA=CIG, MINL=5, MAXL=5, CLRLP=0, CHSC=0;
NOTE
To avoid a conflict with the emergency outgoing prefixes 2 and 3, define the prefix used in intra-Centrex
group calls as 9. That means the short numbers of the Centrex group begin with 9.
//Add intra-Centrex group prefixes (emergency outgoing prefixes), with the maximum and
minimum number lengths being 5.
ADD ICXPFX: CXG=100, PFX=K'2, CSA=EMCOUT, MINL=5, MAXL=5, CLRLP=0,
CHSC=0;
ADD ICXPFX: CXG=100, PFX=K'3, CSA=EMCOUT, MINL=5, MAXL=5, CLRLP=0, CHSC=0;
NOTE
Prefixes 2 and 3 are used to call the subscribers outside the Centrex group directly. Therefore, Service
attribute must be set to Emergency outgoing.
//Set the local IP address that controls the IP console. The IP address is that of the FE port on
the IFMI board.
SET CONADDR: CONLAIP="191.169.150.30";
//Add an IP console (U-Path), with the number being 20, registered user name being group,
registration password being abc123, short number being 9000, and call source code being 0.
ADD CXCON: D=K'2589999, MN=22, CONNO=20, IP="191.169.150.20",
CODEC=G711_A-1&G711_U-1&G729-1&G723_1-1, ACNT="group", PWD="******",
CXG=100, CXSG=5, CXD=K'90000, RCHS=25, CSC=0,

OCR=LCO-0&LC-0&LCT-0&NTT-0&ICTX-1&OCTX-1&INTT-0&IITT-0, CON=NO, PBX=NO,

CHARGE=NO, ENH=NO;
NOTE
This U-Path is only used to transfer calls.
Step 4 Configure number analysis data (intra-network call).

//Add ordinary prefixes used in the public network. The local DN set is 0.
SDESCRIPTION="For 259", EA=NO;
CHSC=0, SDESCRIPTION="PSTN national toll", EA=NO;
ADD CNACLD: LP=0, PFX=K'00, CSTP=BASE, CSA=ITT, RSC=0, MINL=3, MAXL=24,
CHSC=0, SDESCRIPTION="PSTN international toll", EA=NO;
NOTE
For the outgoing call prefixes 0 and 00 of the public network, parameters such as Local DN set, Route
selection code, and Charging selection code must be configured correctly.
//Add emergency call prefixes of the public network. Set the local DN set to 0.
ADD CNACLD: PFX=K'110, CSTP=BASE, CSA=LC, RSC=0, MINL=3, MAXL=3,
CHSC=110, RCM=CLDC, ECOS=YES, SDESCRIPTION="For 110", EA=NO;
NOTE
l When a local subscriber dials numbers such as 110, 119, 120, and 122, the calls are all outgoing calls.
Therefore, Route selection code cannot be set to 65535. Assume that Route selection code is set to 0
here.
l According to the stipulations, the system does not charge the calls to numbers such as 110, 119, 120,
and 122, but records the detailed information. Therefore, the charging case corresponding to the
charging selection code 110 must be correctly defined (the charging side cannot be free).
l In normal cases, calls to 110, 119, 120, and 122 are released under the control of the called party.
Therefore, Release mode must be set to Called control.
l Emergency call observation flag is used to observe only emergency call prefixes. When a subscriber
dials an emergency call prefix, the system generates an alarm event of emergency call on the alarm
console.
//Add the supplementary signaling. Set Emergency call override flag of prefixes such as 110
and 119 to Yes.
ADD AUSSIG: LP=0, PFX=K'110, CSC=0, ERF=YES;
NOTE
Set Emergency call override flag to Yes so that subscribers can dial prefixes such as 110, 119, 120, and
122 in any condition. Thus, even if the maintenance staff performs operations such as parking owing
subscribers or restricting the call authority, the ordinary subscribers can call numbers such as 110.
//Add ordinary prefixes used in the private network. The local DN set is 10.
SDESCRIPTION="For 2XXXX", EA=NO;


SDESCRIPTION="For 3XXXX", EA=NO;
CHSC=10, SDESCRIPTION="DN national toll", EA=NO;
NOTE
For the outgoing call prefix 0 of the private network, parameters such as Local DN set, Route selection
code, and Charging selection code must be configured correctly.
Step 5 Configure number analysis data (calls from public network to private network).
//Add an ordinary call prefix for calls from the public network to the private network. Set Local
DN set to 0 and Call prefix to 258.
SDESCRIPTION="For 258", EA=NO;
NOTE
The prefix 258 must be sent to the number analysis table of global DN set 1 for analysis. Therefore, Service
attribute must be set to Local. When Service attribute is set to Local, Intra-office national toll, or
Intra-office international toll, Minimum number length must be the same as Maximum number
length.
//Add number change data. Set Number change index to 51.

ADD DNC: DCX=51, DCT=MOD, DCP=0, DCL=3, ND=K'2;
NOTE
The preceding command changes the first 3 digits of the original caller number to 2.
//Add prefix processing data. Set Call source code to 0, Local DN set to 0, and New DN set to
1.
ADD PFXPRO: CSC=0, LP=0, PFX=K'258, CCF=YES, SENDTONE=NST, NP=1, DDCX=51,
ISREANA=YES;
NOTE
l To perform the called number change function for the prefix 258 of the local DN set 0, Called number
change flag must be set to YES, and Called number change index must be set to 51.
l For the prefix 258 of the local DN set 0, parameters such as Maximum number length, Minimum
number length, Service type and Service attribute cannot be used in the calls made by public network
subscribers to private network subscribers. Therefore, Reanalysis must be set to YES, and New DN
set must be set to 1.
Step 6 Configure number analysis data (calls from private network to public network).
//Add an ordinary call prefix for calls from the private network to the public network. Set Local
SDESCRIPTION="To PSTN", EA=NO;
NOTE
The prefix 10 must be sent to the number analysis table of global DN set 0 for analysis. Therefore, Service
attribute must be set to Local. When Service attribute is set to Local, Intra-office national toll, or
Intra-office international toll, Minimum number length must be the same as Maximum number
length.
//Add emergency call prefixes for the calls from the private network to the public network. Set
the local DN set to 10.
RCM=CLDC, ECOS=YES, SDESCRIPTION="For 110", EA=NO;


NOTE
The prefixes 110, 119, 120, and 122 must be sent to the number analysis table of global DN set 0 for
analysis. Therefore, Service attribute must be set to Local.
//Add the supplementary signaling. Set Emergency call override flag of prefixes such as 110
and 119 to Yes.

ADD DNC: DCX=52, DCT=DEL, DCP=0, DCL=2;
NOTE
The command deletes the first 2 digits of the original called number.
//Add prefix processing data. Set Call source code to 10, Local DN set to 10, and New DN
set to 0.
ADD PFXPRO: CSC=10, LP=10, PFX=K'10, CCF=YES, SENDTONE=NST, NP=0,
DDCX=52, ISREANA=YES;
ADD PFXPRO: CSC=10, LP=10, PFX=K'110, SENDTONE=NST, NP=0, ISREANA=YES;
NOTE
l To perform the called number change function for the prefix 10 of the local DN set 10, Called number
change flag must be set to YES, and Called number change index must be set to 52.
l For the prefixes 10, 110, 119, 120, and 122 of the local DN set 10, parameters such as Minimum
number length, Maximum number length, Service type, Service attribute, Route selection code,
and Charging selection code cannot be used for the calls made by subscribers in the private network
to subscribers in the public network. Therefore, set Reanalysis to Yes and New DN set to 0.
Step 7 Configure number analysis data (calling number analysis when the private network subscriber
calls the public network subscriber).
//Add number change data. Set number change indexes to 61 and 62 respectively.
NOTE
l The first command means that the system changes the first digit of the original number to 258. The
change is applicable to calls made by private network subscribers using public network number
resources to public network subscribers.
l The second command means that the system changes the first five digits of the original number to
2589999. The change is applicable to calls made by private network subscribers who do not use public
network number resources to public network subscribers.
//Add caller analysis data with the call source code being 10.

ADD CNACLR: CSC=10, CID=K'2, LP=10, PFX=K'10, FUNC=MCA, RDCX=61;

NOTE
l The function of the preceding commands can be described as follows: When a specific caller dials a
specific prefix, the system performs the specified number change.
l According to the number analysis sequence, the SoftX3000 first performs the call prefix processing,
and then the number analysis.
----End
Related tasks
None
Related concepts
None

Initial Configuration 11 Typical Data Configuration Example
11 Typical Data Configuration Example
About This Chapter

11.2 Configuration Example of Number Analysis Data
11.3 Configuration Example of Route Data
11.4 Trunk Configuration Examples
11.5 Configuration Example of Call Barring Data
11.6 Configuration Example of Network Management Data
11.7 Configuration Example of Equal Access Data
11.8 Configuration Example of Remote Network Access Data

11 Typical Data Configuration Example Initial Configuration
11.1.1 Configuring Centralized Charging Data

11.1.2 Configuring Distinctive Charging Data
11.1.3 Configuring Multi-Time-Zone Charging Data
11.1.4 Configuring Called Group Charging Data
11.1.5 Configuring Third Party Charging Data
11.1.6 Configuring Centrex Charging Data
11.1.7 Configuring Supplementary Service Charging Data
11.1.8 Configuring Instant Charging Data (Charging Rate)
11.1.9 Configuring Instant Charging Data (KC16 Public Telephone)
11.1.10 Configuring Instant Charging Data (Polarity Reversal Public Telephone)
11.1.11 Configuring Instant Charging Data (Trunk Charging Pulse)
11.1.12 Configuring CRG Charging Data
11.1.13 Configuring IN Service Charging Data
11.1.1 Configuring Centralized Charging Data
Example 1 (Local Office Acting as an End Office)

Introduction
Requirement: The toll office charges all toll calls of the local office.
Scripts
//Add the charging case 100.

ADD CHGANA: CHA=100, PAY=NOCHG, CRM=TNSO;
NOTE
The local office does not charge toll calls; however, if toll call prefixes do not have a charging case, the
SoftX3000 may generate a large number of charging alarms. To avoid this problem, add a charging case
for the toll call prefixes and set Payer to No charge.

PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;

//Add charging case indexes. Set Charging selection code to 100, Charging case to 100, and
Caller charging source code to 22, 33, 65 and 87 respectively (all used for destination code
charging of the subscribers who reside in the local office).
ADD CHGIDX: CHSC=100, RCHS=22, LOAD=ALL, BT=ALLBT, CODEC=ALL, CHA=100;
NOTE
Payer of the charging case 100 is No charge. Therefore, the local office neither generates bills nor generates
charging alarms when its subscribers dial the toll call prefixes.
//Add ESL subscribers (applying charging source codes to subscribers).

EID="amg5320_22.com", STID="0", CODEC=PCMA, RCHS=22, CSC=0, NS=CLIP-1,
//Add a call prefix (applying the charging selection code to the toll call prefix). Set Call
prefix to 0 and Charging selection code to 100.
CHSC=100, EA=NO;
Example 2 (Local Office Acting as a Toll Office)

Introduction
Requirement: The local office charges the toll calls of all its end offices.
Scripts

ADD CHGANA: CHA=101, CHO=CENACC, CHGT=DETAIL;
NOTE
The local office charges toll calls of lower-level offices. Therefore, set Charging office to Centralized
charging and Charging method to Detailed ticket.

TS3=21&00, TA3="6", PA3=1, TB3="6", PB3=1, AGIO3=100;
TS3=21&00, TA3="6", PA3=1, TB3="6", PB3=1, AGIO3=100;
PB1=1,, AGIO1=60, TS2="00&00";

//Add charging case indexes. Set Charging selection code to 101, Charging case to 101, and
Caller charging source code to 60 (used for destination code charging of incoming trunk groups
of lower-level offices).
NOTE
You are advised to adopt the destination code charging mode when the toll office charges lower-level
offices. Thus, you can adopt different charging policies for different call prefixes.
//Modify the attributes of an incoming trunk group. Take an SS7 trunk group as an example.
Apply the charging source code to the incoming trunk group.
MOD N7TG: TG=31, SOPC="001122", RCHS=60, NOAA=FALSE, ISM=FALSE, EA=TURE,
CAMA=YES;
NOTE
The local office charges the toll calls of lower-level offices. Therefore, set CAMA to Yes and Charging
source code to the caller charging source code defined for the trunk group (it is 60 in the given example).
//Add a call prefix (applying the charging selection code to the toll call prefix). Set Call
prefix to 0 and Charging selection code to 101.
CHSC=101, EA=NO;
NOTE
When a subscriber who resides in an end office makes a toll call through the trunk group 31, the local office
performs the following operations:
l The local office checks whether the call signaling from the end office contains the caller number. If
yes, the local office connects the call. If not, the local office requests the caller number from the end
office through signaling.
l After the call ends, the local office generates two bills: one trunk bill and one ordinary bill. The trunk
bill, sorted based on the trunk group number in the billing center, is used for call charge settlement
between offices. The ordinary bill, sorted based on the caller number in the billing center, is used for
charging the caller.
l The maintenance staff of the end office determines whether the end office charges the toll calls made
by subscribers of the local office.
Related tasks
Related concepts
None
11.1.2 Configuring Distinctive Charging Data
Example 1 (Charging Audio and Video Services Distinctively According to Bearer

Capability)
Introduction
Requirements: An IP multimedia end office connects both voice subscribers and IP multimedia
subscribers. It is required to distinctively charge the audio services and video services of IP

multimedia subscribers. For calls within the local network, charge IP audio calls at 10 cents per
minute and IP video calls at 20 cents per minute.
Scripts
//Add two charging cases. The charging case 150 is used for charging audio calls and the charging
meter 1 is used. The charging case 151 is used for charging video calls and the charging meter
11 is used.

PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
//Modify rates of the meters. Change the rate of the meter 1 to 10 cents per pulse and that of the
meter 11 to 20 cents per pulse.
MOD MTRR: MID=METER1, RAT=10;
//Add intro-office group charging data. The charging case 150 is used for charging IP audio calls
and the charging case 151 is used for charging IP video calls.
ADD CHGGRP: RCHS=30, DCHS=254, LOAD=IPAUDIO, CODEC=ALL, CHA=150;
ADD CHGGRP: RCHS=30, DCHS=254, LOAD=IPVEDIO, CODEC=ALL, CHA=151;
NOTE
l For charging on IP audio calls, set Bearer capability to IP audio and use the charging case 150.
l For charging on IP video calls, set Bearer capability to IP video and use the charging case 151.
//Add multimedia subscribers. Set Charging source code to 30 (defined by running ADD
CHGGRP).
ADD MSBR: D=K'8780011, LP=0, EID="8780011", RCHS=30, CSC=0, NS=CLIP-1,
CTXA=NO, PBXA=NO, CA=NO, EA=NO;
ADD MSBR: D=K'8780012, LP=0, EID="8780012", RCHS=30, CSC=0, NS=CLIP-1,
CTXA=NO, PBXA=NO, CA=NO, EA=NO;
Example 2 (Charging Calls Distinctively According to Codec Mode)

Introduction
Requirements: For subscribers who reside in an access media gateway (AMG), their call quality
is closely related to the codec modes, thus requiring distinctive charging. Take toll calls as an
example. When the codec is set to G.711A or G.711μ, the rate is 7 cents per 6 seconds; when
the codec is set to G.723 or G.729, the rate is 30 cents per minute.
Scripts

//Add two charging cases. The charging case 155 is used when the codec is set to G.711A or G.
711μ and the rate is 7 cents per pulse. The charging case 156 is used when the codec is set to G.
723 or G.729 and the rate is 30 cents per pulse.
ADD CHGANA: CHA=155, RAT=7, CRM=TNSO;

PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
//Add charging case indexes. Set Charging selection code to 100 and Caller charging source
code to 50.
ADD CHGIDX: CHSC=100, RCHS=50, LOAD=ALL, BT=ALLBT, CODEC=G71164A,
CHA=155;
ADD CHGIDX: CHSC=100, RCHS=50, LOAD=ALL, BT=ALLBT, CODEC=G71164U,
CHA=155;
ADD CHGIDX: CHSC=100, RCHS=50, LOAD=ALL, BT=ALLBT, CODEC=G71156A,
CHA=155;
ADD CHGIDX: CHSC=100, RCHS=50, LOAD=ALL, BT=ALLBT, CODEC=G71156K,
CHA=155;
ADD CHGIDX: CHSC=100, RCHS=50, LOAD=ALL, BT=ALLBT, CODEC=G7231, CHA=156;
ADD CHGIDX: CHSC=100, RCHS=50, LOAD=ALL, BT=ALLBT, CODEC=G7231A, CHA=156;
ADD CHGIDX: CHSC=100, RCHS=50, LOAD=ALL, BT=ALLBT, CODEC=G729, CHA=156;
ADD CHGIDX: CHSC=100, RCHS=50, LOAD=ALL, BT=ALLBT, CODEC=G729B, CHA=156;
ADD CHGIDX: CHSC=100, RCHS=50, LOAD=ALL, BT=ALLBT, CODEC=G729AB, CHA=156;
NOTE
l When the voice coding is G.711A or G.711μ, set Codec to G.711_A_LAW or G.711_U_LAW and
use the charging case 155.
l When the voice coding is G.723 or G.729, set Codec to G.723 or G.729 and use the charging case 156.
//Add voice subscribers. Set Charging source code to 50 (defined by running ADD
CHGIDX).
ADD VSBR: D=K'6540001, LP=0, MN=22, DID=ESL, EID="iad0021.com", TID=1,
CODEC=PCMA, RCHS=50, CSC=0, NS=CLIP-1, CNTRX=NO, PBX=NO, CHG=NO, ENH=NO;
ADD VSBR: D=K'6540002, LP=0, MN=22, DID=ESL, EID="iad0021.com", TID=2,
NOTE
Codec prefer specifies the preferred codec of ESL subscribers. The default value is PCMA (G.711A).
Related tasks
Related concepts

The SoftX3000 supports distinctive charging on NGN services according to the bearer capability
and codec. This enhances the charging flexibility.
l Bearer capability is used for distinctive charging on different services or bearer capabilities.
For example, for multimedia subscribers A and B:
– If the bearer capability is set to IP audio, the SoftX3000 charges only the IP audio.
– If the bearer capability is set to IP video, the SoftX3000 charges only the IP video.
– If the bearer capability is set to Unrestricted 384K, the SoftX3000 charges only the
audio and video services that use the 384-kbit/s circuit switching network.
NOTE
Other cases can be deduced in the same manner.

l The codec mode is used for distinctive charging on different media streams. For example,
calls between subscribers A and B can be connected through either the circuit switching
network (the codec is G.711) or the IP packet network (the codec is G.723).
– If the codec is set to G.711, the SoftX3000 charges only the calls that pass through the
circuit switching network.
– If the codec is set to G.723, the SoftX3000 charges only the calls that pass through the
IP packet network.
NOTE
Other cases can be deduced in the same manner.
11.1.3 Configuring Multi-Time-Zone Charging Data
Example
Introduction
When the SoftX3000 subscribers belong to different time zones, the time for the call between
subscribers in different time zones is considered to be the same by the SoftX3000. When
subscribers in different time zones talk with each other; however, the time when they talk is
actually different. Therefore, subscribers must be charged based on the actual time of the
conversation (according to the time zone to which the subscribers belong).
Requirement: The SoftX3000 subscribers belong to different time zones.
Scripts
//Add customized time zone indexes 27 and 28. Set Time zone index to 27 and Time offset to
30; set Time zone index to 28 and Time offset to 50.
ADD TMZCFG: TZ=27, BCTZ=TZ22, TOFFSET=30;
ADD TMZCFG: TZ=28, BCTZ=TZ22, TOFFSET=50;
//Set Time zone index to 21 for the system; set Time zone index to 27 for call source code 1;
set Time zone index to 28 for call source code 2.
SET OFI: OFN="local", TMZ=21;
ADD CALLSRC: CSC=1, TZ=27;
ADD CALLSRC: CSC=2, TZ=28;
//Modify subscriber data. Set Call source code to 1 for subscriber number 6680001; set Call
source code to 2 for subscriber number 6680002.

MOD VSBR: D=K'6680001, CSC=1;

MOD VSBR: D=K'6680002, CSC=2;
//Add charging case analysis data. Set Charging case to 110, Payer to Called party, Charging
method to Detailed ticket, and Detailed ticket rate to 5.
ADD CHGANA: CHA=110, PAY=CALLED, RAT=5, CRM=TNSO;
//Modify charging mode.

PB1=1, AGIO1=100, TS2=00&00;
//Add called group charging data. Set Called charging source code to 200 and Charging
case to 110.
//Modify subscribers' charging attributes (add called charging mode for subscribers). Set Callee
charging source code to 200.
MOD VSBR: D=K'6680001, LP=0, DCHS=200;
MOD MSBR: D=K'6680002, LP=0, DCHS=200;
Related tasks
Related concepts
None
11.1.4 Configuring Called Group Charging Data
Example
Introduction
The called group charging mode charges the called parties. This charging mode is parallel to the
charging mode for calling parties. In general, the SoftX3000 charges only the calling parties. If
a subscriber adopts the called group charging mode at the same time, the SoftX3000 performs
bi-directional charging for the subscriber.
Requirement: Charge the new batch of Personal Handy phone System (PHS) subscribers in the
local network when they answer calls, at the rate of 5 cents per minute.
Scripts
//Add charging case analysis data. Set Charging case to 110, Payer to Called party, Charging
method to Detailed ticket, and Detailed ticket rate to 5.
ADD CHGANA: CHA=110, PAY=CALLED, RAT=5, CRM=TNSO;
NOTE
l For the called group charging, Payer must be set to Called party. To facilitate bill querying, set
Charging method to Detailed ticket.
l If the local office adopts the offline billing mode, you need not specify Detailed ticket rate.


PB1=1, AGIO1=100, TS2=00&00;
MOD CHGMODE: CHA=110, DAT= DTYPE1, TS1=00&00, TA1="60", PA1=1, TB1="60",
PB1=1, AGIO1=100, TS2=00&00;
MOD CHGMODE: CHA=110, DAT= DTYPE2, TS1=00&00, TA1="60", PA1=1, TB1="60",
PB1=1, AGIO1=100, TS2=00&00;
//Add called group charging data. Set Called charging source code to 200 and Charging
case to 110.
NOTE
l Called charging source cannot be set to 254. Otherwise, the called group charging mode is applied
to all subscribers of the local office.
l For the referenced charging case, Payer must be set to Called party.
//Modify subscribers' charging attributes (add the called charging mode for the specified
subscribers). Set Callee charging source code to 200.
NOTE
The called group charging mode has certain limitations because the mode is not related to the position of
the caller. Pay attention to this when you use the called group charging mode.
//Modify the charging attributes of specified subscribers (remove the called charging mode for
specified subscribers).
NOTE
To remove the called charging mode for a subscriber, you only need to change Callee charging source
code to 255.
Related tasks
Related concepts
None
11.1.5 Configuring Third Party Charging Data
Example 1 (Recording Call Charge of Incoming Trunks to a Number)

Introduction
Requirements: A Private Branch Exchange (PBX) is connected through R2 trunks to the

SoftX3000 in the local network of city A. Configure charging data on the SoftX3000 side. Charge
the subscriber number 3630000 for all toll calls of PBX subscribers originated through R2

incoming trunks and charge the subscriber number 3630001 for calls originated within the local
network.
Scripts
//Add two charging cases. The charging case 120 is used for charging toll calls and the charging
number is 3630000. The charging case 121 is used for charging calls within the local network
and the charging number is 3630001.
ADD CHGANA: CHA=120, PAY=THIRD, BDN=K'3630000, CRM=TNSO;
ADD CHGANA: CHA=121, PAY=THIRD, CHGT=PLSACC, MID=METER20, BDN=K'3630001,
CRM=TNSO;
NOTE
For the third party charging, Payer must be set to Third party.

TS3=21&00, TA3="6", PA3=1, TB3="6", PB3=1, AGIO3=100;
TS3=21&00, TA3="6", PA3=1, TB3="6", PB3=1, AGIO3=100;
PB1=1, AGIO1=60, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
//Add a charging case index. Set Caller charging source code to 20 and Charging case to
120.
//Add intra-office group charging data. Set Caller charging source code to 20, Callee charging
source code to 254 (wildcard), and Charging case to 121.
//Add an R2 trunk group. Set Charging source code to 20.

ADD N1TG: TG=16, EID="211.169.150.41:2944", G=IN, SRC=16, SN="N1",
RCHS=20, ECATTR=NO, TIATTR=NO, ENATTR=NO;
NOTE
After you run the preceding commands, the charging number is 3630000 in the toll call bills generated for
calls made by PBX subscribers through R2 incoming trunks and the charging number is 3630001 in the
bills generated for calls within the local network.
Example 2 (Recording Charge of All Calls Made by a Customer Service Center to

a Bank Account)
Introduction
Requirements: The customer service center of a company has 16 operator positions. Charge a
bank account for all calls made by the customer service center.
Scripts

//Add two charging cases. The charging case 122 is used for charging toll calls. Set Charging
number type to a bank account and Charging number to 123456789. The charging case 123
is used for charging calls within the local network. Set Charging number type to a bank account
and Charging number to 123456789.
ADD CHGANA: CHA=122, PAY=THIRD, BNT=BANK3, BDN=K'123456789, CRM=TNSO;
ADD CHGANA: CHA=123, PAY=THIRD, CHGT=PLSACC, BNT=BANK3, BDN=K'123456789,
CRM=TNSO;
NOTE
For the third party charging, Payer must be set to Third party.

TS3=21&00, TA3="6", PA3=1, TB3="6", PB3=1, AGIO3=100;MOD CHGMODE:
CHA=122, DAT=DTYPE1, TS1=00&00, TA1="6", PA1=1, TB1="6", PB1=1, AGIO1=60,
TS2=07&00, TA2="6", PA2=1, TB2="6", PB2=1, AGIO2=60, TS3=21&00, TA3="6",
PA3=1, TB3="6", PB3=1, AGIO3=100;
PB1=1, AGIO1=60, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;MOD CHGMODE: CHA=123, DAT=DTYPE2, TS1=00&00,
TA1="60", PA1=1, TB1="60", PB1=1, AGIO1=100, TS2=00&00;
//Add a charging case index. Set Caller charging source code to 21 and Charging case to
122.
//Add intra-office group charging data. Set Caller charging source code to 21, Callee charging
source code to 254 (wildcard), and Charging case to 123.
//Add voice subscribers. Set Charging source code to 21.

ADD VSBR: D=K'6540001, LP=0, MN=22, DID=ESL, EID="iad0021.com", TID="1",
ADD VSBR: D=K'6540002, LP=0, MN=22, DID=ESL, EID="iad0021.com", TID="2",
NOTE
After you run the preceding commands, the charging number is the bank account 123456789 in the bills
generated for all calls of the customer service center.
Example 3 (Multiple Subscriber Numbers Use a Charging Number)

Introduction
Requirements: A subscriber has installed two phones in his home. The phone numbers are
6540001 and 6540002. Charge all calls of the two phones to the number 6540001.
Scripts
//Modify the charging number of a subscriber. Set Original charging subscriber number to
6540002 and New charging subscriber number to 6540001.
MOD CHGNUM: DN=K'6540002, JFDN=K'6540001;

NOTE
After you run the preceding commands, the SoftX3000 charges the number 6540001 for all calls made by
the number 6540002.
Related tasks
Related concepts
In the third party charging mode, neither the caller nor the callee pays for the call; instead, a
third party pays for the call. In actual applications, a third party may be one of the following
types:
l Subscriber number
l National valid number
l International valid number
l Centrex group number
l Account card
l Bank account
The account card charging and bank account charging are achieved through offline billing.
To achieve the third party charging, you can perform one of the following operations:
l Define a third party number in a charging case, which applies to group subscribers.
l Modify the charging number, which applies to individual subscribers.
11.1.6 Configuring Centrex Charging Data
Example 1 (Charging Internal Calls of a Centrex Group)

Introduction
Requirement: Charge the outgoing calls of a Centrex group as ordinary calls and charge internal
calls at the rate of 5 cents per minute.
Scripts
//Add a Centrex group. Set Centrex group number to 8.
ADD CXGRP: CGN="Huawei", CXG=8, UCPC=100, WACF=NO, BIF=NO;

ADD CXSUBGRP: CXG=8, CXSG=5, CXSGN="Huawei subgroup";

//Add a Centrex call prefix. Set Centrex call prefix to 2, and Minimum number length and
Maximum number length to 4.

NOTE
The prefix 2 is used for intra-group calls between Centrex subscribers. Therefore, Service attribute must
be set to Intra-Centrex.
//Add a charging case. Set Charging case to 130 (used for charging internal calls of a Centrex
group).
NOTE
For charging internal calls of a Centrex group, set Charging method to Meter table.

PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
//Modify the rate of a meter. Set Meter table to Meter table 10 and Tariff to 5.
MOD MTRR: MID=METER10, RAT="5";
//Add Centrex intra-group charging data. Set Charging case to 130.

//Add a batch of ESL subscribers. Set Charging source code to 65 (used for ordinary intra-
office group charging and destination code charging) and Centrex group number to 8 (used
for charging internal calls of a Centrex group).
EID="amg5000.com", STID="0", CODEC=PCMA, RCHS=65, CSC=1, UTP=NRM,
NS=CLIP-1, CNTRX=YES, CGF=YES, CXG=8, CXSG=5, PBX=NO, CHG=NO, ENH=NO;
NOTE
l Centrex intra-group charging takes precedence over intra-office group charging and destination code
charging. Therefore, when a Centrex subscriber makes an internal call, the SoftX3000 charges the call
according to the charging case defined by Centrex intra-group charging.
l Centrex intra-group charging does not differentiate the bearer capability and codec mode. To perform
distinctive charging on internal calls of a Centrex group, apply the intra-office group charging or
destination code charging.
Example 2 (SoftX3000 Sending Ordinary Bills to a Console)

Introduction
Requirements: The SoftX3000 acts as an end office in a local network. All the toll calls are
charged by the toll office. A U-Path console in a Centrex group needs to provide the bill querying
function and therefore requires the SoftX3000 to send ordinary bills to it.
Scripts
//Add a charging case. Set Charging case to 140 and Charging method to Meter table.
ADD CHGANA: CHA=140, PAY=CALLER, CHGT=PLSACC, CRM=TNSO;

NOTE
l The local office does not charge toll calls; however, if toll call prefixes do not have a charging case,
the SoftX3000 may generate a lot of charging alarms. To avoid this problem and enable the SoftX3000
to send bills of toll calls to the U-Path, add a charge case for toll call prefixes and set Payer to Calling
party instead of No charge.
l Charging data is configured on the U-Path and the U-Path has a lower requirement for bills. Bills must
contain only the basic charging information (such as calling number, called number, answer time and
conversation end time). Therefore, to reduce the load on the SoftX3000, set Charging method to
Meter table.

PB1=0, AGIO1=100, TS2=00&00;
PB1=0, AGIO1=100, TS2=00&00;
PB1=0, AGIO1=100, TS2=00&00;
NOTE
To prevent the SoftX3000 from charging toll calls, set Start pulse 1 and Continued pulse 1 to 0.

//Add a Centrex subgroup. Set Centrex subgroup number to 5 to enable the SoftX3000 to send
bills to the U-Path.
ADD CXSUBGRP: CXG=8, CXSG=5, CXSGN="Huawei subgroup", BSCF=DTM;

//Add a Centrex console.

ADD CXCON: D=K'8880000, MN=22, CONNO=0, ACNT="ss", PWD="*****", CXG=8,
CXSG=5, RCHS=1, CSC=0, CON=NO, PBX=NO, CHARGE=NO, ENH=NO;
//Modify the console function reduction parameters.

MOD CONFUNC: D=K'8880000, LP=0, FBIL=GETBILL-1, SGRP1=5;
NOTE
l To enable the SoftX3000 to send ordinary bills of Centrex subscribers to the U-Path, set Send ticket
to console to Detailed ticket and meter table.
l In the regular bill fetching mode, the U-Path sends the request of Request bill sending to the SoftX3000
at the preset intervals. On receipt of the request, the SoftX3000 reads bills from the host bill pool or
bill server and sends them to the U-Path through the dedicated communication links.
Example 3 (SoftX3000 Sending Immediate Bills to a Console)

Introduction
Requirements: The SoftX3000 acts as an end office in a local network. All the toll calls are
charged by the toll office. Telecom operators provide the IP supermarket service through the U-
Path and therefore, require the SoftX3000 to send immediate bills to the U-Path. In this way,
the U-Path can print bills for Centrex subscribers on a real-time basis.
Scripts

Configuration steps for this example are basically the same as the steps for the preceding example
(SoftX3000 sending ordinary bills to a console). The difference is that the following step is added
to the end of the preceding example.
//Modify the charging attributes of a Centrex subscriber. Change Charging category to

Immediately sending to printer.
MOD VSBR: D=K'8780200, LP=0, CHG=YES, CHT=IMP;
NOTE
l Charging category of Centrex subscribers must be set to Immediately sending to printer so that call
bills can be queried and printed on the U-Path immediately after Centrex subscribers end calls.
l On the U-Path side, the Receiving immediate bill option on the bill management menu must be
selected. This enables the U-Path to receive the immediate bills from the SoftX3000.
l To facilitate the management of immediate bills, grant only one U-Path in a Centrex group the authority
to receive immediate bills. If the authority is granted to multiple U-Paths, the SoftX3000 sends
immediate bills only to the last logged-in U-Path.
Example 4 (Charging Centrex Subscribers When They Originate Toll Calls

Through a Console)
Introduction
Requirement: In general, the SoftX3000 charges the console that forwards toll calls for Centrex
subscribers who have no authority to make toll calls. This example requires the SoftX3000 to
charge the subscribers, instead of the console.
Scripts

//Modify the attributes of the Centrex group. Set Forward charge not record in console to
Yes.
MOD CXGRP: CXG=8, TBNC=YES;
NOTE
To charge Centrex subscribers when they originate toll calls through a console, set Forward charge not
record in console to Yes.

ADD CXSUBGRP: CXG=8, CXSG=5, CXSGN="Huawei subgroup";

Related tasks
Related concepts
None.

11.1.7 Configuring Supplementary Service Charging Data
Example
Introduction
Requirement: Configure charging data on the SoftX3000 side to charge subscribers who use
supplementary services. Assume that all supplementary services use two meters. Table 11-1
lists the charging strategies.
Table 11-1 Charging strategies for supplementary services

Supplementary Meter Number of Pulse Rate (Cent/Pulse)
Service
Abbreviated dialing Meter 15 1 10
Hotline Meter 15 1 10
Do not disturb Meter 15 1 10
Wakeup Meter 15 1 10
Call back on busy Meter 15 1 10
Call forwarding no Meter 16 1 5

reply
Call forwarding Meter 16 1 5

unconditional
Call forwarding busy Meter 16 1 5
Call waiting Meter 16 1 5
Absent subscriber Meter 16 1 5
Scripts
//Modify rates of the meters. Change the rate of the meter 15 to 10 cents per pulse and that of
the meter 16 to 5 cents per pulse.
//Add supplementary service charging data.

ADD CHGSS: NS=ADU, RCHS=254, CHGMOD=MOD1, MID=METER15, PLSN=1;
ADD CHGSS: NS=HLU, RCHS=254, CHGMOD=MOD1, MID=METER15, PLSN=1;
ADD CHGSS: NS=DDU, RCHS=254, CHGMOD=MOD1, MID=METER15, PLSN=1;
ADD CHGSS: NS=ACU, RCHS=254, CHGMOD=MOD1, MID=METER15, PLSN=1;
ADD CHGSS: NS=CBU, RCHS=254, CHGMOD=MOD1, MID=METER15, PLSN=1;
ADD CHGSS: NS=CFNRU, RCHS=254, CHGMOD=MOD1, MID=METER16, PLSN=1;
ADD CHGSS: NS=CFUU, RCHS=254, CHGMOD=MOD1, MID=METER16, PLSN=1;
ADD CHGSS: NS=CFBU, RCHS=254, CHGMOD=MOD1, MID=METER16, PLSN=1;
ADD CHGSS: NS=CWU, RCHS=254, CHGMOD=MOD1, MID=METER16, PLSN=1;
ADD CHGSS: NS=ASU, RCHS=254, CHGMOD=MOD1, MID=METER16, PLSN=1;

NOTE
l The charging source code 254 is a wildcard. It represents all charging source codes (applies to all
subscribers).
l The example defines only how the SoftX3000 charges subscribers when they use supplementary
services. In actual applications, the SoftX3000 can also define how to charge subscribers when they
register or cancel certain supplementary services.
l The example defines the charging cases for call forwarding services. Therefore, the SoftX3000
generates two bills for a subscriber who uses these services. One is used for charging the use of the
service and the other is used for charging the call to the destination number.
Related tasks
Related concepts
The SoftX3000 mainly uses meters to charge supplementary services. That is, the SoftX3000
charges subscribers based on the number of times they register or use the supplementary services.
For call forwarding services, the SoftX3000 can also charge the subscribers based on the
destination numbers. That is, the SoftX3000 uses the intra-office group charging or destination
code charging mode.
In actual applications, you can apply different charging strategies to charge supplementary
services. For example, you can adopt the "monthly rental" mode to charge the Calling Line
Identity Presentation (CLIP) service.
11.1.8 Configuring Instant Charging Data (Charging Rate)
Example
Introduction
To immediately charge subscribers who make calls through pay phones or Internet Personal
Numbers (IPNs), and to display the charges immediately, define complete and precise rates for
the mapping charging cases.
Configure charging rates on the SoftX3000 side to achieve precise charging of calls made
through pay phones or IPNs and to display the charges immediately. Charging data of
supplementary services must be defined separately. For details, see section 11.1.7 Configuring
Supplementary Service Charging Data lists the charging requirements Table 11-2 charging
requirement.

Table 11-2 Charging requirements

Charging Charging Object Rate Meanings
Case Method (Cent/
Pulse)
1 Detailed Ordinary 80 The SoftX3000 takes six seconds as

ticket international a charging pulse. The SoftX3000
toll calls provides a discount of 40 percent for
calls on Saturdays, Sundays,
national holidays, and during
00:00-07:00 and 21:00-24:00 on
weekdays.
2 Detailed Ordinary 7 The SoftX3000 takes six seconds as

ticket national toll a charging pulse. The SoftX3000
calls provides a discount of 40 percent for
calls on Saturdays, Sundays,
national holidays, and during
00:00-07:00 and 21:00-24:00 on
weekdays.
3 Detailed IP 250 The SoftX3000 takes 60 seconds as

ticket international a charging pulse and does not
toll calls provide a discount.
4 Detailed IP national 30 The SoftX3000 takes 60 seconds as

ticket toll calls a charging pulse and does not
provide a discount.
11 Meter 1 Calls within 10 The SoftX3000 adds 2 to the meter

the business counts for the first 180 seconds and
area then adds 1 every 60 seconds. It does
not provide a discount during
00:00-07:00 and 21:00-24:00 on
weekdays.
12 Meter 2 Calls 20 The SoftX3000 adds 1 to the meter

between counts for the first 60 seconds and
business then adds 1 every 60 seconds. It does
areas not provide a discount during
00:00-07:00 and 21:00-24:00 on
weekdays.
13 Meter 3 Calls to 30 The SoftX3000 adds 1 to the meter

"13X" counts for the first 60 seconds and
then adds 1 every 60 seconds. It does
00:00-07:00 and 21:00-24:00 on
weekdays.

Charging Charging Object Rate Meanings

Case Method (Cent/
Pulse)
14 Meter 4 Calls to 25 The SoftX3000 adds 1 to the meter

"9XX" counts for the first 60 seconds and
then adds 1 every 60 seconds. It does
00:00-07:00 and 21:00-24:00 on
weekdays.
Scripts
//Add charging cases.
NOTE
The ADD CHGANA command directly defines the detailed ticket rate.
//Modify rates of meters.

NOTE
By default, the rate of each meter is 10 cents per pulse. To change the rate, run MOD MTRR.
//Add date categories.

ADD DCAT: YEAR=2003, MON=JAN, DAY=1, DAT=DTYPE2;
ADD DCAT: YEAR=2003, MON=FEB, DAY=1, DAT=DTYPE2;
ADD DCAT: YEAR=2003, MON=MAY, DAY=1, DAT=DTYPE2;
ADD DCAT: YEAR=2003, MON=OCT, DAY=1, DAT=DTYPE2;
NOTE
The example defines Jan. 1, Feb. 1, Feb. 2, Feb. 3, May 1, May 2, May 3, Oct. 1, Oct. 2 and Oct. 3 as
Category 2 to provide discounts for toll calls made on these days.
//Modify charging modes (for toll calls).

TS3=21&00, TA3="6", PA3=1, TB3="6", PB3=1, AGIO3=100;


TS3=21&00, TA3="6", PA3=1, TB3="6", PB3=1, AGIO3=100;
PB1=1, AGIO1=60, TS2=00&00;
TS3=21&00, TA3="6", PA3=1, TB3="6", PB3=1, AGIO3=100;MOD CHGMODE: CHA=2,
DAT=DTYPE1, TS1=00&00, TA1="6", PA1=1, TB1="6", PB1=1, AGIO1=60,
TS2=07&00, TA2="6", PA2=1, TB2="6", PB2=1, AGIO2=60, TS3=21&00, TA3="6",
PA3=1, TB3="6", PB3=1, AGIO3=100;
PB1=1, AGIO1=60, TS2=00&00;
PB1=1, TS2=00&00;
PB1=1, TS2=00&00;
PB1=1, TS2=00&00;
PB1=1, TS2=00&00;
PB1=1, TS2=00&00;
PB1=1, TS2=00&00;
NOTE
l By default, Monday to Thursday are defined as normal workdays, Friday as Category 1, and Saturday
and Sunday as Category 2.
l Jan. 1, Feb. 1, Feb. 2, Feb. 3, May 1, May 2, May 3, Oct. 1, Oct. 2 and Oct. 3, are defined as Category
2.
//Modify charging modes (for non-toll calls).

PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
Related tasks


Related concepts
None.
11.1.9 Configuring Instant Charging Data (KC16 Public Telephone)
Example
Introduction
It is required to implement instant charging on IC public phones (adopting the KC16 mode)
numbered from 6540001 to 6540004 of the local office, by configuring data on the SoftX3000
side.
Scripts
//Modify the meter rate to 5 cent for one KC16 pulse string.
MOD MTRR: MID=KC16, RAT=5;
NOTE
l The rate of a single KC16 pulse string should be set according to the charging policy of the carrier.
l The SoftX3000 calculates the number of pulse strings to be sent to the IC public phones according to
the preset charging rate, actual conversation duration and the rate of a single KC16 pulse string.
//Modify the charging attribute of voice subscribers.

MOD VSBR: D=K'6540001, LP=0, CHG=YES, TFPT=T_16K, CHT=IMU;
NOTE
l To enable the SoftX3000 to perform instant charging on IC public phones, set Charging attribute to
Yes, and change Charging category to Immediate subscriber table and Tariff pulse type to
16KC.
l If instant charging is adopted for subscribers, you cannot set Charging category to Free. Otherwise,
the SoftX3000 fails to send the polarity reversal signal, KC16 pulse or the trunk charging pulse to IC
public phones.
l The IAD or AMG connected to IC public phones is required to support the KC16 function.
l In the charging mode used for the Thailand TOT public coin phones, you can determine whether to
charge a call which is shorter than the charging duration, by setting bit 0 of P182. When bit 0 is set to
0, it indicates that the call is not charged. When bit 0 is set to 1, it indicates that the call is charged. The
default value of bit 0 is 0 for Thailand. The default value is 1 for other countries.
Related tasks
Related concepts
KC16 public telephones refer to phones such as IC public phones, magcard phones and coin-
boxes, which are charged based on the KC16 charging pulse received from the switching system.
The basic working principle is as follows:

The KC16 public phone can work in two modes: Karlson and Handson.
l In Karlson mode, pulse strings are sent only when the conversation fee reaches a preset
value instead of being sent regularly. Assume that the rate of one pulse string is 5 cents,
0.05 dollar is charged for one minute of local call, and 0.5 dollar is charged for one minute
of toll call. If a subscriber makes a local call on a public phone, the SoftX3000 first sends
one pulse string the moment the call is connected, and then sends one pulse string every
one minute. If a subscriber makes a toll call on a public phone, the SoftX3000 first sends
one pulse string the moment the call is connected, and then sends one pulse string every
six seconds.
l In Handson mode, pulse strings are sent regularly. For example, if a subscriber makes a
local call on a public phone, the SoftX3000 first sends one pulse string the moment the call
is connected, and then sends one pulse string every one minute. If a subscriber makes a toll
call on a public phone, the SoftX3000 first sends ten pulse strings the moment the call is
connected, and then sends ten pulse strings every one minute.
By default, the SoftX3000 supports the Karlson mode. If you need to use the Handson mode,
modify the mapping system software parameter.
11.1.10 Configuring Instant Charging Data (Polarity Reversal

Public Telephone)
Example
Introduction
It is required to implement instant charging on magcard public phones (adopting the polarity
reversal mode) numbered from 6540011 to 6540014 of the local office, by configuring data on
the SoftX3000 side.
Scripts
//Modify the charging attribute of voice subscribers.
MOD VSBR: D=K'6540011, LP=0, CHG=YES, TFPT=T_PORE, CHT=IMU;
NOTE
l To enable the SoftX3000 to perform instant charging on magcard public phones, set Charging
attribute to Yes, Tariff pulse type to Polarity reversal, and Charging category to Immediate
subscriber table.
l If instant charging is adopted for subscribers, you cannot set Charging category to Free. Otherwise,
the SoftX3000 fails to send the polarity reversal signal, KC16 pulse or trunk charging pulse to magcard
public phones.
l The IAD or AMG connected to magcard public phones is required to support the polarity reversal
function.
Related tasks
Related concepts

Polarity reversal public telephones refer to public phones such as magcard phones and coin-
boxes, which are charged based on the voltage polarity of the subscriber lines. The basic working
principle is as follows: The SoftX3000 controls the IAD or AMG to reverse the voltage polarity
of the subscriber lines based on the on-hook or off-hook of both the caller and callee. On receipt
of the polarity reversal information, the public phone performs the mapping operation.
The polarity reversal public phone can work in two modes:

l Polarity reversal mode: Charging data is configured on the public phone that has the
charging function. The phone requires only the start time and the end time of the
conversation, which can be indicated by the SoftX3000 through reversing the voltage
polarity of the subscriber line.
l Polarity reversal pulse mode: It is applied to the public phone that does not have the charging
function. The working principle is as follows: After a subscriber inserts coins and dials a
number on a public phone, the SoftX3000 indicates the "callee off-hook" event by reversing
the voltage polarity of the subscriber line, and then starts the time monitor based on the
supported conversation duration (set by the SoftX3000). When the duration times out, the
SoftX3000 recovers the voltage polarity of the subscriber line within 300 ms. At this time,
if the subscriber inserts coins again, the public phone reverses the voltage polarity again to
extend the duration; if not, the public phone releases the call.
By default, the SoftX3000 supports the polarity reversal mode. If the polarity reversal pulse
mode is required, modify the mapping system software parameter.
11.1.11 Configuring Instant Charging Data (Trunk Charging Pulse)
Example
Introduction
requirements:
l For the outgoing SS7 trunks, the local office can receive charging pulses through signaling
messages sent from the peer office.
l For the incoming SS7 trunks, the local office can send charging pulses through signaling
messages to the peer office.
Script (Applicable to Outgoing SS7 Trunk)
//Modify the charging attribute of the outgoing SS7 trunk group.

MOD N7TG: TG=30, SOPC="001122", NOAA=FALSE, ISM=FALSE, EA=TRUE, UPF=YES;
NOTE
If a call is made through a public phone of the local office, to enable the SoftX3000 to receive charging
pulses in the signaling messages returned by the peer office, set Use opposite pulse to Yes.
Script (Applicable to Incoming SS7 Trunk)
//Modify the meter rate to 30 cents for one trunk charging pulse.
MOD MTRR: MID=TKCHGPLS, RAT=30;

NOTE
l The rate of a single trunk charging pulse should be set based on to the charging policy of the carrier.
l The SoftX3000 calculates the number of charging pulses to be sent to the peer office according to the
preset charging rate, actual conversation duration and the rate of a single trunk charging pulse.
//Modify the charging attribute of the incoming SS7 trunk group.

MOD N7TG: TG=31, SOPC="001122", NOAA=FALSE, ISM=FALSE, EA=TRUE, UPF=YES;
NOTE
If a call is made on a public phone of the peer office, to enable the SoftX3000 to send charging pulses to
the peer office, set Use opposite pulse to Yes.
Related tasks
Related concepts
A trunk charging pulse is sent from a higher-level office with the toll charging function (such
as a tandem office or a toll office) to the end office without the toll charging function. On receipt
of the trunk charging pulse, the end office transfers the pulse to the public phone. For an office,
the charging pulse set for outgoing trunk calls and that set for incoming trunk calls have different
meanings.
l Outgoing trunk: For outgoing calls from the trunk group of the local office, the local office
receives the charging pulse or charging message (CRG or MPM) from the peer office.
l Incoming trunk: For incoming calls to the trunk group of the local office, the local office
sends the charging pulse or charging message (CRG or MPM) to the peer office.
11.1.12 Configuring CRG Charging Data

Introduction
The charging information message (CRG) charging is a charging process implemented based
on charging signaling messages. The CRG charging can be carried out in different signaling
procedures. Data configuration is similar for all the signaling procedures. The charging office,
tandem office, and charging-determining office must work with each other. The charging-
determining office determines the charging signaling procedure to be applied. The following
part takes the third charging procedure (CRG_BAND charging) as an example.
Figure 11-1 shows the network of the CRG charging.

Figure 11-1 Network of the CRG charging

Charging
Charging Office Tandem Office
Controlling Office
IAM IAM
CPG CPG
Example 1 (When the Local Office Serves as the Charging Office)

Task Description
The local office is required to generate a CDR for an outgoing call based on the charging message
sent from the charging-determining office.
Scripts
//Configure the ISUP signaling adaptation data. Set Trunk group number to 0, ISUP transmit
mask number to 21, and ISUP receive mask number to 20.
MOD N7TG: TG=0, NOAA=FALSE, ISM=TRUE, STM=21, SRM=20, EA=FALSE;
MOD IMSGMSK: SM=20, MSG=CHBI, MV=YES;
MOD IMSGMSK: SM=20, MSG=CHAI, MV=YES;
MOD IMSGMSK: SM=20, MSG=TACI, MV=YES;
MOD IMSGMSK: SM=20, MSG=CHGI, MV=YES;
MOD IMSGMSK: SM=20, MSG=CRG, MV=YES;
MOD IMSGMSK: SM=20, MSG=CHUI, MV=YES;
MOD IMSGMSK: SM=20, MSG=CHPI, MV=YES;
//Modify the associated software parameter.

//Add the changing band data. Set Charging band number to 13.
ADD CHGBAND: CHB=13, DAT=normal, TA1="180", PA1=5, TB1="60", PB1=1;
NOTE
If a charging office can provide detailed charging information but must be notified by the charging-
determining office through the CRG or CHB message of starting charging, you must set charging band
data in both the charging office and the charging-determining office. The Charging band number
parameter must be numbered globally on the network. The value of this parameter must be consistent with
that set in the charging office or tandem office.
//Add the charging case analysis data. Set Charging manner to Send CRG band number.

ADD CHGANA: CHA=10, CHGM=SCBN, CHGB=13;

NOTE
Before you configure the charging case data associated with the CRG charging, ensure the consistency of
charging manners between offices. That is, the charging manners must match the charging messages
transmitted between them.
//Add the charging case index data.

NOTE
The CRG charging can use only the destination code charging mode.
//Configure the call prefix and trunk charging data. Set Charging selection code of the call
prefix to 10 and set Outgoing trunk charging source code or Incoming trunk charging source
code to 11.
MOD CNACLD: LP=3, PFX=K'666, CHSC=10, EA=NO;
Example 2 (When the Local Office Serves as the Tandem Office)

Task Description
During a transit call, the local office transparently transmits the charging messages from the
charging-determining office to the charging office.
Scripts

NOTE

//Add the charging case analysis data. Set Charging manner to Transfer CRG band
number.
ADD CHGANA: CHA=10, CHGM= PCBN, CHGB=13;
NOTE

NOTE
code to 11.
Example 3 (When the Local Office Serves as the Charging-Determining Office)

Task Description
The local office sends charging messages to the charging office, instructing the charging office
to generate a CDR for an incoming call.
Scripts


NOTE
//Add the charging case analysis data. Set Charging manner to Send CRG band number
and .Charging band number to 13.
ADD CHGANA: CHA=10, CHGM= SCBN, CHGB=13;
NOTE

NOTE
code to 11.
MOD N7TG: TG=0, RCHS=11, OTCS=11, NOAA=FALSE, ISM=FALSE, EA=FALSE;
Related Tasks
Related Concepts
Charging Modes
11.1.13 Configuring IN Service Charging Data

Example
Introduction
In this example, you must configure data so that the SoftX3000 provides an IN service (such as
the ACC service) for subscribers.

NOTE
l Charging class, a key parameter for the interworking between the SSP and the SCP, must be negotiated
between the SSP and the SCP.
l In this example, all the IN service charging is performed on the SSP side. Therefore, detailed and
complete charging class information must be defined on the SoftX3000. (The charging classes defined
in the preceding commands are only for example.) Otherwise, the SSP fails to charge calls and the fee
loss occurs.
l Whether to implement a tariff discount policy and for which type of calls a tariff discount policy is
implemented are determined by carriers based on the actual situation.
Table 11-3 lists the data to be planned before configuring the IN service.
Table 11-3 Data to be planned before configuring the IN service

Value Obtain
IN charging Charging 1 Obtain from l 1: charging class for

data class carriers. ordinary international
toll calls
2 Obtain from
l 2: charging class for
carriers.
ordinary national toll
3 Obtain from calls
carriers. l 3: charging class for IP
international toll calls
4 Obtain from
carriers. l 4: charging class for IP
national toll calls
11 Obtain from l 11: charging class for
carriers. calls within the same
service area
12 Obtain from
carriers. l 12: charging class for
calls between service
13 Obtain from areas
carriers. l 13: charging class for
14 Obtain from calls addressed to the
carriers. numbers prefixed with
13x in the local network
15 Obtain from l 14: charging class for
carriers. calls addressed to the
numbers prefixed with
16x in the local network
l 15: charging class for
calls addressed to the
numbers prefixed with
9xx in the local network
Scripts
//Add the tariff discount data for holidays, with Discount index set to 300 and Additional
charging discount style set to Discount by percentage. (The New Year's Day, the Chinese

New Year's Day, the International Labor Day, and the national day of China in 2003 are taken
for example.)
ADD HLDDIS: IDX=300, YEAR=2003, MON=JAN, DAY=1, STM="00&00&00",
ETM="23&59&59", DIS0=60, SRS=PERCENT;
ADD HLDDIS: IDX=300, YEAR=2003, MON=FEB, DAY=1, STM="00&00&00",
ADD HLDDIS: IDX=300, YEAR=2003, MON=MAY, DAY=1, STM="00&00&00",
ADD HLDDIS: IDX=300, YEAR=2003, MON=OCT, DAY=1, STM="00&00&00",
//Add the tariff discount data for the days of the week, with Additional charging discount
style set to Discount by percentage and Basic charging discount0 set to 60. (Saturday and
Sunday are taken for example.)
ADD WEKDIS: IDX=300, WEK=SUN, STM="00&00&00", ETM="23&59&59", DIS0=60,
SRS=PERCENT;
ADD WEKDIS: IDX=300, WEK=SAT, STM="00&00&00", ETM="23&59&59", DIS0=60,
SRS=PERCENT;
//Add the tariff discount data for the specified time segments of a day, with Additional charging
discount style set to Discount by percentage and Basic charging discount by percentage set
to 60. (Tariff discount is performed during 00:00-08:00 and 21:00-24:00 every day.)
ADD NRMDIS: IDX=300, STM="00&00&00", ETM="08&00&00", RS=PERCENT, DIS0=60,
SRS=PERCENT;
ADD NRMDIS: IDX=300, STM="21&00&00", ETM="23&59&59", RS=PERCENT, DIS0=60,
SRS=PERCENT;
//Add the charging class data.

ADD CHGCLS: CLS=1, RAT="80", PRAT="80", TA=600, PA=1, TB=600, PB=1,
IDX=300;
ADD CHGCLS: CLS=2, RAT="7", PRAT="7", TA=600, PA=1, TB=600, PB=1,
IDX=300;
ADD CHGCLS: CLS=3, RAT="240", PRAT="240", TA=6000, PA=1, TB=6000, PB=1;
NOTE
l You can configure multiple pieces of tariff discount data for the same discount index. That is, when
you run ADD HLDDIS, ADD WEKDIS, and ADD NRMDIS to add tariff discount data for IN
charging, you can configure multiple pieces of data by using the same discount index.
l In ADD CHGCLS, the metering time interval is expressed in units of 10 milliseconds.

Related Tasks
Commissioning IN Services
Related Concepts
Configuring IN Services
11.2 Configuration Example of Number Analysis Data
11.2.1 Configuring Digitmap Data

11.2.2 Configuring Release Mode Data
11.2.3 Configuring Caller Number Change Data
11.2.4 Configuring Called Number Change Data
11.2.5 Configuring PBX Pilot Number Change Data
11.2.6 Configuring Special Called Number Change Data
11.2.7 Configuring Caller Number Analysis Data
11.2.8 Prefix Processing Data
11.2.9 Configuring Failure Processing Data
11.2.10 Configuring Trunk Group Bearer Data
11.2.1 Configuring Digitmap Data
Example
Introduction
It is required to modify the Digitmap defined by MGCP and H.248 on the SoftX3000 side in a
local network, so that the digitmaps conform to the dialing requirements specified in Table
11-4.
Table 11-4 Digitmap configuration requirements
Serial Function MGCP Code H.248 Code Remarks

No. of
Digitmap
1 Calling local [2-8]xxxxxx [2-8]xxxxxx The phone numbers of

fixed the local fixed
subscribers subscribers consist of 7
digits and are prefixed
with a digit between 2
and 8.


No. of
Digitmap
2 Calling local 13xxxxxxxxx 13xxxxxxxxx The numbers of local

mobile mobile subscribers
subscribers consist of 11 digits and
are prefixed with 13.
3 Calling non- 013xxxxxxxxx 013xxxxxxxxx When a local subscriber

local mobile calls a non-local mobile
subscribers subscriber, the local
subscriber must dial 0
before the called
number. The numbers of
non-local mobile
subscribers consist of 11
digits and are prefixed
with 13.
4 Dialing an 00xxxxxxxxx 00xxxxxxxxx When a local subscriber

international makes an international
toll prefix toll call, the local
subscriber must dial 00
before the called
number.
l If the international
called number
consists of more than
9 digits, the digits
following the ninth
digit are sent one by
one by matching x.T
or x.L.
l If the international
called number
consists of less than
9 digits, the caller
can end the dialing
by matching x.# or
x.F (pressing #), or
by matching x.T or
x.L (timeout).
5 Dialing the 010xxxxxxxx 010xxxxxxxx When a local subscriber

area code of makes a national toll
Beijing call, the local subscriber
must dial 0 before the
called number. The area
code of Beijing is 10.
The phone number of a
local subscriber consists
of 8 digits.


No. of
Digitmap
6 Dialing area 02xxxxxxxxx 02xxxxxxxxx When a local subscriber

codes of makes a national toll
provincial call, the local subscriber
capitals must dial 0 before the
called number. In
China, the area codes of
provincial capitals are
02x, and the phone
numbers of local
subscribers in each city
consist of 8 digits.
7 Dialing area 0[3-9]xxxxxxxxx 0[3-9]xxxxxxxxx When a local subscriber

codes of makes a national toll
other cities call, the local subscriber
must dial 0 before the
called number.
l If the national called
number consists of
more than 10 digits,
the digits following
the tenth digit are
sent one by one by
matching x.T or x.L.
l If the national called
number consists of
less than 10 digits,
the caller can end the
dialing by matching
x.# or x.F (pressing
#), or by matching
x.T or x.L (timeout).
8 Dialing 9xxxx 9xxxx Typically, the special

special service numbers
service prefixed with 9x consist
numbers of 5 digits.
prefixed
with 9x


No. of
Digitmap
9 Dialing 1[0124-9]x 1[0124-9]x Currently, the special

special service numbers
service prefixed with 1x can
numbers consist of 3 to 5 digits. If
prefixed a special service number
with 1x consists of more than 3
(excluding digits, the digits
13) following the third digit
are sent one by one by
matching x.T or x.L.
10 Allowing * E When a subscriber uses

dialing * as supplementary services
the first digit on a DTMF phone, the
prefix is usually * or #.
After * is dialed, * is
reported immediately,
and the subsequent
digits are sent one by
one by matching *, #,
and x.T (or E, F, and
x.L).
11 Allowing # F When a subscriber uses

dialing # as supplementary services
the first digit on a DTMF phone, the
prefix is usually * or #.
After # is dialed, # is
reported immediately,
and the subsequent
digits are sent one by
one by matching *, #,
and x.T (or E, F, and
x.L).
12 Allowing x.# x.F If # is dialed after any

dialing # at digit (0-9) in the
the end of numbering plan, it
any number indicates that the dialing
to end dialup is completed, and the
MGW will send the
received digits
(including #)
immediately.


No. of
Digitmap
13 Allowing x.T x.L If a dialed number

sending a matches a dialing plan
number digit completely, the MGW
by digit or sends the received digits
after timeout immediately. If there are
subsequent digits, they
are sent one by one. If a
dialed number matches
a dialing plan partially
and the subscriber stops
dialing the subsequent
digits, the MGW sends
the received digits after
timeout.
When configuring digitmap data, note the following:

l The SoftX3000 supports a digitmap with a maximum of 1024 characters. The maximum
length of the digitmap in the actual data configuration, however, cannot exceed the length
supported by the IAD or AMG.
l Some IADs also have limitations on the number of delimiters supported. For example, if
an IAD does not support more than 10 delimiters, you must simplify the configuration of
the digitmap.
l If Centrex subscribers are connected to an MGW, the SoftX3000 generates a digitmap for
the Centrex subscribers based on the out-group call prefix and intra-group call prefix of the
Centrex group.
Scripts
//Modify the digitmap of the local DN set.
MOD DMAP: PROTYPE=H248, DMAPIDX=0, PARTIDX=0, DMAP="[2-8]xxxxxx|
MOD DMAP: PROTYPE=MGCP, DMAPIDX=0, PARTIDX=0, DMAP="[2-8]xxxxxx|
MOD LDNSET: LP=0, DGMAPIDX=0, MDGMAPIDX=0;
NOTE
l Some GWs may be case-sensitive to the characters in a digitmap. Therefore, during the configuration,
ensure that all characters, except the letter x, are in the upper case.
l The digitmap syntax rule defined by MGCP is not the same as that defined by H.248. For example, in
H.248, E stands for * and F stands for #.
Related tasks
None

Related concepts
Digitmap
11.2.2 Configuring Release Mode Data
Example 1 (For All Service Attributes or Signaling Modes)

Introduction
It is required to set the release mode of special service calls such as police calls and fire calls to
Called party release in all cases.
Scripts

ADD CNACLD: PFX=K'110, CSTP=BASE, MINL=3, MAXL=3, RDT=3, CHSC=0,
NOTE
l If the release mode of a call prefix need not differ in the service attribute or signaling mode, run ADD
CNACLD to set it.
l As required in this example, set Release mode to Called party release.
Example 2 (For a Specific Service Attribute or Signaling Mode)

Introduction
It is required to set the release mode of national toll calls and international toll calls to Calling
party release when ISUP signaling is permanently used.
Scripts

ADD CNACLD: PFX=K'0, CSTP=BASE, CSA=NTT, RSC=0, MINL=3, MAXL=24, CHSC=0,
SDESCRIPTION="National toll", EA=NO;
ADD CNACLD: PFX=K'00, CSTP=BASE, CSA=ITT, RSC=0, MINL=3, MAXL=24, CHSC=0,
SDESCRIPTION="International toll", EA=NO;
NOTE
When you add a call prefix by running ADD CNACLD and using the default value, the release mode of
the prefix is First party release by default.
//Configure the release modes.

SET RLSMOD: PFX=K'0, CSA=NTT, ST=IS, RCM=CLRC;
SET RLSMOD: PFX=K'00, CSA=ITT, ST=IS, RCM=CLRC;
NOTE
l If the release mode of a call prefix is required to differ in the service attribute or signaling mode, run
SET RLSMOD to set the release mode.
l As required in this example, set Service attribute and Signaling mode correctly, and set Release
mode to Calling party release.

Related tasks
None.
Related concepts
Call Prefix
11.2.3 Configuring Caller Number Change Data
Introduction
The SoftX3000 supports caller number change by using the following methods:
l Discrimination of the caller address attribute of a call source (ADD CALLSRC)

A call source can be used not only to define the attribute of callers, but also to convert the
address attribute of caller numbers through discrimination of the caller address attribute of
a call source.
l Discrimination of caller numbers (ADD CLRDSN)
Caller number discrimination functions can be used to bar incoming trunk calls and convert
the call source attribute and charging attribute of incoming trunk calls initiated by specific
subscribers. That is, you can define different call source codes and charging source codes
for callers on the SoftX3000. After the number change, the call source codes and charging
source codes of these callers are no longer the default ones for the incoming trunk calls.
l Caller analysis (ADD CNACLR)
Caller analysis can help to achieve both caller number change and called number change.
It is used to convert caller numbers based on different call prefixes or call sources. Unlike
prefix processing, caller analysis not only changes the caller numbers, but also changes
caller number attributes such as route selection source code, failure source code, charging
source code, and subscriber type.
l Prefix processing (ADD PFXPRO)
Prefix processing can help to achieve both caller number change and called number change.
It is used to convert caller numbers based on the call prefixes and call sources. This method
can change the caller numbers. That is, during charging, the caller numbers in the bills are
the converted numbers.
l Trunk bearing (ADD TGLD)
Trunk bearing functions can achieve both caller number change and called number change.
Caller number change is performed after called number analysis. This method can change
the numbers of the callers as well as their address attributes. It does not affect charging.
That is, the caller number in a bill is the original number.
Example 1 (Change of Caller Address Attribute Through Discrimination of Caller

Address of a Call Source)
Introduction
requirements:

l The SoftX3000 acts as an end office and interworks with the local call tandem office in the
local network through SS7 trunks.
l When the local call tandem office transfers a national toll call through an incoming trunk
to the SoftX3000, the SoftX3000 converts the caller number to an international toll number
with a prefix.
Scripts
//Add the call source code 30 (used for SS7 trunks between the SoftX3000 and the local call
tandem office).
ADD CALLSRC: CSC=30, CSCNAME="For No7 trunk", PRDN=1, ISADRDSG=TNNWZ;
NOTE
To change a caller number in the incoming trunk (belongs to the call source 30) to a valid national number
headed with 0, set Caller address discrimination to Change to international toll number with prefix
mode.
//Add two SS7 trunk groups. Trunk group 0 is an outgoing trunk group, trunk group 1 is an
incoming trunk group, and their call source code is 30.
TGN="To tandem office", CSC=30, PRTFLG=CN, NOAA=FALSE, ISM=FALSE,
EA=FALSE;
EA=FALSE;
NOTE
l In the preceding example, you only need to set Call source code to 30 for the incoming trunk group
between the SoftX3000 and the local call tandem office.
l Unless otherwise specified, set Call source code of the outgoing trunk group and incoming trunk group
to the same value.
Example 2 (Change of Caller Number Through Caller Analysis)

Introduction
requirements:
l The SoftX3000 acts as an end office and interworks with the local call tandem office in the
local network through SS7 trunks.
l When the local call tandem office transfers a call to the SoftX3000 from another end office
in the local network through an incoming trunk, and the caller number is 3331XXX and
the called prefix is 6661, the SoftX3000 converts the caller number to 3XXX, that is,
changes 3331 in the caller number to 3.
Scripts

ADD DNC: DCX=21, DCT=MOD, DCL=4, ND=K'3;
NOTE
The preceding command changes the first four digits of the original caller number to one digit, that is, 3.
//Add the local call prefix 6661.


//Add caller analysis data, with the call source being 0, caller number being 3331, call prefix
being 6661, and caller number index being 21.
ADD CNACLR: CSC=0, CID=K'3331, PFX=K'6661, FUNC=MCA, RDCX=21;
NOTE
l Call source code in the preceding command must be set to the call source code to which the incoming
trunk group belongs.
l In the preceding command, Calling party number changing index is set to 21. It indicates that the
SoftX3000 converts the caller numbers based on the preset conditions through caller analysis.
//Add two SS7 trunk groups. Trunk group 0 is an outgoing trunk group, trunk group 1 is an
incoming trunk group, and their call source code is 0.
EA=FALSE;
EA=FALSE;
NOTE
In this example, the application requirements can also be met through trunk group bearing. This method,
however, is not as flexible as caller analysis, because it can implement number change only for a single
trunk group.
Example 3 (Change of Caller Number Through Prefix Processing)

Introduction
requirements: When any subscriber in the local office makes an IN card call by dialing the card
service prefix 201, a carrier wishes to replace the first three digits of the original caller number
with 201.
Scripts

NOTE
//Add the IN call prefix 201.

SDESCRIPTION="ACC Service";
//Add prefix processing data. Set Call source code to 65534 (wildcard) and Call prefix to
201.
ADD PFXPRO: CSC=65534, PFX=K'201, PROCSTART=YES, RDCX=22;

NOTE
l The call source code 65534 is a wildcard. It represents all call source codes (applicable to all
subscribers).
l In this example, Caller change flag must be set to Yes and Caller party number change index to
22.
Related tasks
None.
Related concepts
Number Change
11.2.4 Configuring Called Number Change Data
Introduction
The SoftX3000 supports called number change by using the following methods:
l Number preparation of call source (ADD CALLSRC)

A call source is used to define the attribute of callers, and also to convert the called numbers
through number preparation. This method is applied in cases where prefixes are different
based on the network that an office exists in. This method takes precedence over other
methods and is performed before called number analysis. In terms of charging, the called
number in the bill is the changed called number.
l Caller analysis (ADD CNACLR)
Caller analysis helps to achieve both caller number change and called number change. It
is used to convert called numbers based on different call prefixes or call sources. In terms
of charging, the called number in the bill is the changed called number.
l Prefix processing (ADD PFXPRO)
Prefix processing helps to achieve both caller number change and called number change.
It is used to convert called numbers based on different call prefixes or call sources. In terms
of charging, the called number in the bill is the changed called number.
l Trunk bearing (ADD TGLD)
Trunk bearing can achieve both caller number change and called number change. Called
number change is performed after number analysis, without affecting other attributes such
as charging, emergency calling and release mode. In terms of charging, the called number
in the bill is the original number.
Example 1 (Change of Called Number Through Number Preparation of Call

Source)
Introduction
requirements:

l Simplify the one-stage dialing procedure for Advanced Prepaid Service (APS) subscribers
and make the procedure as simple as the dialing mode of ordinary subscribers.
l When acting as a service switching point (SSP), the SoftX3000 is required to insert the
APS access code (213 for example) before the called number, so that the APS can be
triggered.
Scripts

ADD DNC: DCX=31, DCT=INS, ND=K'213;
NOTE
The preceding command inserts the number 213 before the original called number.
//Add a call source. The call source code is 9. The number of pre-receive digits is 1. The number
change index is 31.
ADD CALLSRC: CSC=9, CSCNAME="APS User", PRDN=1, DCX=31, DCF=YES;
NOTE
The new call source code is added for APS subscribers. That is, the SoftX3000 inserts the APS prefix 213
to the numbers dialed by the APS subscribers of this call source. For example, if an APS subscriber dials
07556540001, the SoftX3000 converts this number to 21307556540001 before sending it to the SSP.
//Modify subscriber attributes. Change the call source code to 9 for the subscriber numbers from
6540001 to 6540004.
MOD VSBR: D=K'6540001, LP=0, CSC=9;
Example 2 (Change of Called Number Through Caller Analysis)

Introduction
requirements:
The SoftX3000 acts as a local call tandem office, and its lower-level office A is configured with
two subscriber groups: 666XXXX and 668XXXX.
To facilitate management of fault complaint calls (special service number 112), the carrier
requires the following:
l Connect fault complaint calls made by callers whose numbers are prefixed with 666 to the
local number 6540112.
l Connect fault complaint calls made by callers whose numbers are prefixed with 668 to the
local number 6541112.
Scripts

NOTE
l The first command changes the first 3 digits of the original called number to 6540112.
l The second command changes the first 3 digits of the original called number to 6541112.
//Add call prefixes 112 and 654.

SDESCRIPTION="Special call", EA=NO;
SDESCRIPTION="Special call", EA=NO;
NOTE
l To enable call prefix discrimination that is required in caller analysis, separately define the call prefix
112, which is to be discriminated.
l If a subscriber of the end office dials 112, the called number sent to the local office is still 112 because
the end office does not change this called number. In this example, the minimum number length should
be set to 3 in order to enable the local office to receive digits from the incoming trunks.
ADD CNACLR: CSC=0, CID=K'666, PFX=K'112, FUNC=MCA, DDCX=35;
ADD CNACLR: CSC=0, CID=K'668, PFX=K'112, FUNC=MCA, DDCX=36;
NOTE
l If a subscriber whose number is prefixed with 666 dials 112, the SoftX3000 starts the caller analysis
program to convert the called number to 6540112 (which corresponds to the called number change
index 35). Then, the SoftX3000 performs the subsequent number analysis procedure based on the
service attribute defined for the call prefix 654.
l If a subscriber whose number is prefixed with 668 dials 112, the SoftX3000 starts the caller analysis
program to convert the called number to 6541112 (which corresponds to the called number change
index 36). Then, the SoftX3000 performs the subsequent number analysis procedure based on the
service attribute defined for the call prefix 654.
Example 3 (Change of Called Number Through Prefix Processing)

Introduction
It can be inferred from Example 1 that the SoftX3000 first inserts the APS access code 213
before any number dialed by APS subscribers. Then, the SSP triggers the IN service. If a
subscriber makes a special service call such as a police call, fire call or ambulance call, however,
the carrier requires that the SoftX3000 connect these calls through the common service flow
instead of inserting the APS access code before such special service numbers.
Scripts
NOTE
//Add call prefixes 110, 119, 120, and 122 for special services.


//Add prefix processing data. Set Call source code to 9.

ADD PFXPRO: CSC=9, PFX=K'213110, CCF=YES, DDCX=32, SENDTONE=NST,
ISREANA=YES;
ISREANA=YES;
ISREANA=YES;
ISREANA=YES;
NOTE
l In this example, Called number change flag must be set to YES and Called number change index
must be set to 32.
l Irrespective of whether the APS is triggered in the local office or another office, the service type and
service attribute of its access code 213 (as a call prefix) are inconsistent with those of the special service
prefixes. Therefore, the SoftX3000 must reanalyze the called number after deleting the prefix 213.
Thus, set Reanalysis to Yes.
Example 4 (Change of Called Number Through Prefix Processing)

Introduction
requirements:
l During rearrangement of the local number resources, a carrier has changed the numbers
296XXXX to 836XXXX.
l Subscribers are allowed to dial the original numbers prefixed with 296 during a specified
period.
Scripts

NOTE


NOTE
To enable the coexistence of both the old and the new numbers during a specific period, you must define
the call prefix for the new number, and at the same time reserve the call prefix of the old number. If you
do not reserve the old one, the SoftX3000 plays an announcement indicating an error when a subscriber
dials the old number.
//Add prefix processing data. Set Call source code to 0 and Call prefix to 296.
ADD PFXPRO: CSC=0, PFX=K'296, CCF=YES, DDCX=33, SENDTONE=NST, ISREANA=YES;
NOTE
l The number 296XXXX is deleted. Therefore, you must define the prefix processing data (or failure
processing data) for the prefix 296. Otherwise, the SoftX3000 plays an announcement indicating a
number error.
must be set to 33.
l To avoid charging errors, set Reanalysis to Yes when you define the prefix processing table for the
call prefix 296.
Related tasks
None
Related concepts
Number Change
11.2.5 Configuring PBX Pilot Number Change Data
Example
Introduction
Requirement: After a PBX group is configured by SingTel, the caller number displayed on the
callee's phone is the PBX pilot number when a subscriber in the PBX group makes a call. After
an NP number is configured for the PBX pilot number, the caller number displayed on the callee's
phone is the NP number, instead of the PBX pilot number.
CAUTION
This feature is used only in Singapore and is applicable to the PBX group, the pilot number of
which has an NP number.
Scripts
//Add an ordinary subscriber who has an NP number.

ADD VSBR: D=K'6680000, LP=0, DID=ESL, MN=22, EID="huawei.com", TID="0",
RCHS=0, CSC=0, UTP=NRM, CNTRX=NO, PBX=NO, CHG=NO, ENH=YES,
NPDN=K'6660000, CUGU=NO;

NOTE
In the database, the NP number cannot be occupied. That is, the NP number cannot be allocated to another
subscriber.
//Set the number of the subscriber as a PBX pilot number.

ADD PBX: GDN=K'6680000, LP=0, PAC=YES, PNC=NOCHG;
NOTE
Set Use pilot number as caller number to Yes.
//Add other subscribers to the PBX group.

MOD VSBR: D=K'6680001, LP=0, PBX=YES, AUT=PBXD, GDN=K'6680000;
NOTE
Set PBX attribute to Yes. PBX pilot number is the pilot number configured by running ADD PBX.
//Configure the CLIP service authority for the callee.

MOD SS: D=K'6690002, LP=0, NS=CLIP-1;
NOTE
Set Supplementary service to CLIP.
The subscriber whose number is 6680000 or 6680001 calls the subscriber whose number is
6690002. The number displayed on the callee's phone is the NP number 6660000.
Related tasks
None.
Related concepts
PBX pilot number change means that if the pilot number of a PBX group has an NP number,
the NP number, instead of the PBX pilot number, is displayed to the callee when a subscriber
in the PBX group makes a call.
11.2.6 Configuring Special Called Number Change Data

Special called number change meets the requirement of functions such as remote network access
and Wide Area Centrex (WAC) for changing large volume of irregular called numbers. The
SoftX3000 supports the changing of 1,000,000 called numbers. The call processing software re-
analyzes the new called number after changing the called prefix. In terms of charging, the called
number in the bill is the changed called number.
Example
Introduction
The office is a pure tandem office with 6000 prefixes. The office provides only tandem services.
It is required that the call to the office is processed with a different codec if a subscriber dials
1234 before the prefix so that the charging is cheaper. Other attributes, such as the minimum
number length, maximum number length, and route selection code, remain the same. The
prefixes 881, 882, 883, and 884 have the same attributes except the codec list and charging
selection code.

Scripts
//Add call prefix data. Set Special called number change to Yes.
ADD CNACLD: PFX=K`8888, CSTP=BASE, MINL=12, MAXL=12, CHSC=0, EA=YES,
SPCHG=SPCHG, ASF=NO, QCDN=NO, VPNF=NOVC;
NOTE
Add the call prefix 8888. The codec list and charging selection code are the same as those of the prefix
1234. Other attributes are the same as those of the prefixes 881, 882, 883, and 884.
//Add special called number change data.

ADD SPDNC: PFX=K'1234, DCT=MOD, DCL=4, ND=K'8888;
//Add number change data. Set Number change index to 1, Number change type to Delete
number, and Change length to 4.
//Add call prefix processing data. Set Call prefix to 8888 and Called number change index to
1.
ADD PFXPRO: CSC=0, PFX=K"8888, CCF=YES, SENDTONE=NST, DDCX=1, ISREANA=NO;
NOTE
When adding call prefix processing data, configure the number not to be re-analyzed after deleting the
prefix 8888. Thus, the call can be connected based on the previous prefix 881, 882, 883, or 884.
Related tasks
None.
Related concepts
Number Change
11.2.7 Configuring Caller Number Analysis Data

To modify a call source code means to modify the related attributes of all callers. In some cases,
however, you need to define different call source attributes for a specific type of callers in the
call source, including:
l Route selection mode
l Failure processing mode
l Charging mode
To achieve this, run ADD CNACLR to redefine them.
Example 1 (Changing Route Selection Source Code of Caller)

Introduction
The SoftX3000 acts as a toll office in the local network. It has two subroutes to the upper-level
toll office. They are subroute 0 (the direct subroute) and subroute 1 (the alternative subroute).
Normally, the SoftX3000 occupies subroute 0 when it transits outgoing toll calls from the local
network. The number of channels in subroute 1 is limited. Therefore, if subroute 0 is unreachable

or congested, the SoftX3000 permits only certain special subscribers (whose prefix is 32310XX
or 36921XX) to occupy subroute 1 when they dial toll prefixes such as 010 and 020.
Scripts
//Add a call source. Set Call source code to 35, Route selection source code to 0 (default value),
and Failure source code to 0 (default value).
ADD CALLSRC: CSC=35, CSCNAME="For No7 trunk";
NOTE
The call source is used for the SS7 incoming trunk between the local office and the urban call tandem
office.
//Add an SS7 trunk group. Set Trunk group number to 0 and Call source code to 35.
EA=FALSE;
NOTE
This command sets the call source code of the SS7 trunk group to 35. This indicates that the SoftX3000
uses the default route selection source code 0 of the incoming trunk (belonging to call source 35) when
performing route analysis for all the incoming trunk group calls.
//Add call prefixes 0, 010 and 020.

CHSC=0, SDESCRIPTION="For 010", EA=NO;
NOTE
l To discriminate call prefixes in the caller number analysis, you must define the call prefixes 010 and
020.
l Normally, the SoftX3000 selects subroute 1 for outgoing toll calls. Therefore, you can assign the same
value to Route selection code of the call prefixes 0, 010 and 020. In this example, the value is 81.
ADD CNACLR: CSC=35, CID=K'32310, PFX=K'010, FUNC=MCA, RSSC=10;
NOTE
The first command means that when a subscriber in the local network requests the SoftX3000 to connect
a toll call, the SoftX3000 changes the route selection source code of the incoming trunk (belonging to call
source 35) to 10, if the caller prefix is 32310 and the call prefix is 010 in the call.
//Add subroutes from the local office to the upper-level toll office. (subroute 0 is the direct
subroute and subroute 1 is the alternative subroute.)
ADD SRT: SRC=0, O=0, SRN="Direct route", RENT=URT;
ADD SRT: SRC=1, O=0, SRN="Bypass route", RENT=URT;
//Add routes from the local office to the upper-level toll office. Route 0 contains only subroute
0 and route 1 contains subroute 0 and subroute 1.
ADD RT: R=0, RN="Normal route", SRST=SEQ, SR1=0, IDTP=UNKNOWN;
ADD RT: R=1, RN="Special route", SRST=PERC, SR1=0, SR2=1, IDTP=UNKNOWN;


NOTE
Sub-route selection mode of route 1 is Select by percentage. The first subroute is subroute 0 and its
percentage is 100. The second subroute is subroute 1 and its percentage is 100. Thus, the system first selects
subroute 0 according to the mode configured for route 1. If subroute 0 is unreachable or congested, the
system selects subroute 1.
//Add analysis data of the routes between the local office and the upper-level toll office, with all
the route selection codes being 81.
NOTE
The first command means that when the route selection source is 0, route 0 is selected. The second command
means that when the route selection source is 10, route 1 is selected.
Example 2 (Changing Failure Source Code of Caller)

Introduction
The SoftX3000 acts as an end office and interworks with the urban call tandem office in the
local network through the SS7 trunk. When the urban call tandem office transfers an incoming
call to the local office through the incoming trunk, the local office processes the call according
to the call prefix of the caller if the local subscriber is busy (the prefixes of local subscribers are
660XXXX or 661XXXX).
l If the caller of the peer office is a fixed subscriber, the local office sends Subscriber
Busy to the peer office and releases the call.
l If the caller of the peer office is a mobile subscriber (the prefix is 13XXXXXXXXX), the
local office sends the Address Complete message to the peer office and sends the "line
busy" tone to the caller of the peer office.
Scripts
//Add an SS7 trunk group. Set Trunk group number to 2 and Call source code to 36.
EA=FALSE;
NOTE
This command sets the call source code of the SS7 trunk group to 36. This indicates that the SoftX3000
uses the default failure source code 0 of the incoming trunk (belonging to call source 36) when performing
failure processing for all calls of the incoming trunk group.
//Add call prefixes 660 and 661 (both are used for local calls).
//Add failure processing data with all the failure source codes being 10.
ADD CFPRO: PFX=K'660, FCC=DLBS, FSC=10, FPT=SIG, TT=CONG;
ADD CFPRO: PFX=K'660, FCC=DTBS, FSC=10, FPT=SIG, TT=CONG;

ADD CFPRO: PFX=K'661, FCC=DLBS, FSC=10, FPT=SIG, TT=CONG;

ADD CFPRO: PFX=K'661, FCC=DTBS, FSC=10, FPT=SIG, TT=CONG;
ADD CNACLR: CSC=36, CID=K'13, PFX=K'660, FUNC=MCA, FSC=10;
ADD CNACLR: CSC=36, CID=K'13, PFX=K'661, FUNC=MCA, FSC=10;
NOTE
The first command means that when the urban call tandem office transfers incoming calls from another
exchange, the SoftX3000 changes the failure source code of the incoming trunk (belonging to call source
36) to 10, if the caller number prefix is 13 and the call prefix is 660 in the call.
The preceding commands define the failure processing mode when the caller, whose failure source code
is 10, calls the callee with prefix 660 or 661, but the callee is busy. Here the processing mode is to send
the "line busy" tone to the caller in the peer office.
Example 3 (Changing Charging Source Code of Caller)

Introduction
There is a large amount of toll call traffic between the headquarters of a company in city A and
its branch in city B. The operator decides to give the company a 40% discount for toll calls made
between city A and city B. In city A, it is required to perform separate billing on the toll office
side (SoftX3000) for the toll calls made by the company (subscriber number is 369XXXX) to
city B (toll call prefix is 021).
Scripts
//Add destination code charging. Set Charging selection code to 0, Caller charging source
code to 0, and Charging case to 0 (assume that the charging case 0 already exists).
//Add an SS7 trunk group. Set Trunk group number to 4 and Charging source code to 0.
TGN="To tandem office", RCHS=0, PRTFLG=CN, NOAA=FALSE, ISM=FALSE,
EA=FALSE;
NOTE
This command sets the charging source code of the SS7 trunk group to 0. This indicates that the SoftX3000
uses the default charging source code 0 of the incoming trunk when performing incoming trunk charging
for all calls of the incoming trunk group.
//Add call prefixes 0 and 021. Set Charging selection code to 0.

NOTE
To enable call prefix discrimination that is required in caller analysis, separately define the call prefix 021,
which is to be discriminated.
//Add caller number analysis. Set Caller number to 369, Call prefix to 021, and Charging
source code to 10.
ADD CNACLR: CSC=0, CID=K'369, PFX=K'021, FUNC=MCA, CSCH=10;

NOTE
The command means that when the urban call tandem office transfers the incoming toll calls from another
exchange, the SoftX3000 changes the charging source code of the incoming trunk to 10, if the caller number
prefix is 369 and the call prefix is 021 in the call.
code to 10, and Charging case to 1 (assume that the charging case 1 already exists).
NOTE
The command means that the caller with charging source code 10 is charged in the charging mode specified
in charging case 1 when the caller calls the subscriber with the prefix 021 (charging selection code is 0).
Example 4 (Changing Subscriber Category of Caller)

Introduction
The SoftX3000 acts as an end office and subscribers 23510XX are special subscribers in the
local office. The SoftX3000 changes Caller category of these special subscribers to Priority
when they dial subscriber numbers with prefix 010, to ensure that they have a higher priority to
select routes when they dial 010.
Scripts
//Add call prefixes 0 and 010.

NOTE
To enable call prefix discrimination that is required in caller analysis, separately define the call prefix 010,
which is to be discriminated.
//Add caller number analysis. Set Caller number to 2351, Call prefix to 010, and Caller
category to Priority.
ADD CNACLR: CSC=0, CID=K'2351, PFX=K'010, FUNC=MCA, CAT=PRI;
NOTE
After the command is executed, the SoftX3000 temporarily changes Caller category of subscribers
23510XX to Priority when they dial 010.
Related tasks
None
Related concepts
Sequence of Number Analysis
11.2.8 Prefix Processing Data

Introduction
Normally, the caller number and the dialed number can be used directly for number analysis and
call connection. In some cases, however, you must run ADD PFXPRO to perform prefix
processing for the caller numbers or called numbers with specific call prefixes. Then, the system
can continue number analysis or call connection. Such cases include:
l For specific call prefixes, it is required to change the caller number to mask the real number
of the caller. For details, see the examples in section 11.2.3 Configuring Caller Number
Change Data.
l The call prefix is only an access code, and it is required to perform mapping number change
on the called number before call connection.
l The call prefix is used only for playing tones in the local office, for example, time report
tone and number change notice tone.
l For specific call prefixes, it is required to set them manually into failure processing. For
details, see the examples in section 11.2.9 Configuring Failure Processing Data.
l After calls to certain prefixes are routed successfully, tones are sent to the calling
subscribers to indicate the successful routing, and then the calls are routed out. The function
is applicable only to ISUP, SIP-I, and PRA trunks.
Note that if you define multiple prefix processing modes at the same time, the system selects
only one of them based on the following sequence:
l Number change
l Send tone/Inter-digit send tone
l Fail processing
l Reanalysis
Number change can be used together with Inter-digit send tone and Reanalysis.
Example 1 (Changing Called Number Without Reanalysis)

Introduction
The SoftX3000 acts as a toll office in the local network. The SoftX3000 is connected to the
Public Switched Telephone Network (PSTN) through SS7 trunks or the IP telephone network
through packet trunks. If a subscriber directly dials the toll call prefix 0, the SoftX3000 connects
the call through the PSTN. If a subscriber dials the IP access code 17311 before the toll call
prefix 0, the local office connects the call through the IP telephone network. This example
requires the SoftX3000 to delete the prefix 17311 so that the called number sent from the local
office to the IP telephone network does not include the IP access code 17311.
Scripts
NOTE

SDESCRIPTION="PSTN toll", EA=NO;
CHSC=0, SDESCRIPTION="IP toll", EA=NO;

NOTE
l The first command defines an ordinary toll call prefix whose route selection code is 0 (assume that the
PSTN is selected for routing).
l The second command defines an IP toll call prefix whose route selection code is 1 (assume that the IP
telephone network is selected for routing).
NOTE
l The called number sent from the local office to the peer office cannot contain the access code 17311.
Therefore, define prefix processing data for the prefix 173110. Otherwise, when a subscriber dials the
prefix 17311, the peer office cannot connect the call.
must be set to 51.
l For the call prefix 173110, the minimum number length, maximum number length, service attribute,
route selection code and charging selection code differ much from those of the call prefix 0. Therefore,
you cannot select the called number reanalysis when defining the prefix processing table. Otherwise,
the system connects the call through a PSTN route when a subscriber dials 173110.
Example 2 (Changing Called Number with Reanalysis)

Introduction
The SoftX3000 acts as an office applied in both the public network and private network.
l In the public network, its global DN set is 0 and local DN set is 0.
l In the private network, its global DN set is 1 and local DN set is 10.
To unify the dial-up mode, the carrier requires that the access code 10 be added before the called
number when a subscriber in the private network of the local office calls the subscribers in the
public network of the local office, or calls other subscribers in the public network through the
trunk.
Scripts
ADD DNC: DCX=52, DCT=DEL, DCP=0, DCL=2;
NOTE
//Add a call prefix for the calls made from the private network to the public network. Set Local
SDESCRIPTION="To PSTN", EA=NO;
NOTE
The call prefix must be re-analyzed according to the number analysis data table of the global DN set 0.
Therefore, Service attribute must be set to Local.
//Add prefix processing data. Set Call source code to 10 (assume that it belongs to private
network subscribers), Local DN set to 10, Call prefix to 10, and New DN set to 0.
ADD PFXPRO: CSC=10, LP=10, PFX=K'10, CCF=YES, NP=0, DDCX=52,
SENDTONE=NST, ISREANA=YES;

NOTE
l For details of the data configuration flow when the SoftX3000 acts as an office applied in both the
public network and private network, see section 10.8 Configuring Data for Blended Application of
Public and Private Networks.
l To perform the called number change function, you must set Called number change flag to Yes and
Called number change index to 52.
l For the call prefix 10 of the local DN set 10, the minimum number length, maximum number length,
service attribute, route selection code and charging selection code cannot be used for the calls made
by subscribers in the private network to subscribers in the public network. Therefore, set Reanalysis
to Yes and New DN set to 0.
Example 3 (Sending Tone, For Example, Time Report Tone)

Introduction
The SoftX3000 acts as an end office and is configured with an embedded Media Resource Server
(MRS). The carrier requires that the local office report the current time to the caller in voice
when a subscriber dials the prefix 117.
Scripts
//Add the call prefix 117. Set Service category to Basic service and Service attribute to
Local.
ADD CNACLD: PFX=K'117, CSTP=BASE, MINL=3, MAXL=3, CHSC=0, EA=NO;
NOTE
For this type of call prefix, if the time report tone resources are provided by the MRS controlled by the
local office, set Service attribute to Local.
//Add prefix processing data. Set Call prefix to 117, Method of sending tone to Send tone and
Tone type to Timer announcement.
ADD PFXPRO: CSC=0, PFX=K'117, SENDTONE=SDT, TT=CLK117, SENDTONE=NST,
ISREANA=YES;
NOTE
l To enable the SoftX3000 to play the time report tone to the callers, configure number analysis data and
MRS resource data correctly and upload the correct voice files to the MRS.
l Note that during the tone playing in prefix processing mode, the local office returns the answer signaling
when a caller or incoming trunk dials the call prefix.
Example 4 (Sending Inter-Digit Tone, For Example, Special Dial Tone)

Introduction
The SoftX3000 acts as an end office and provides the PSTN toll call service and the IP toll call
service in the local network. To differentiate the IP toll call service, the carrier should define the
dial-up method for the service: Dial the special access prefix 17308 (this prefix is not used for
call setup), and then dial 0 followed by the called number after hearing the special dial tone.
Scripts
NOTE


CHSC=0, SDESCRIPTION="IP toll", EA=NO;
NOTE
l The preceding command defines an IP toll call prefix whose route selection code is 1 (assume that the
IP telephone network is selected for routing.)
l Assume that a subscriber dials 17308-0XXPQRABCD, the system performs validity check on the
minimum number length and maximum number length of the result number after changing the called
number. The result number does not contain 17308 because the local office is required to delete the
prefix 17308.
ADD PFXPRO: CSC=0, PFX=K'17308, CCF=YES, SENDTONE=DSDT, DDCX=53,
ISREANA=YES;
NOTE
l To enable the SoftX3000 to send the special dial tone to the caller when a subscriber dials 17308, you
must set Method of sending tone to Inter-digits send tone.
l The called number sent from the local office to the peer office cannot contain the access code 17308.
Therefore, Called number change flag must be set to Yes and Called number change index to 53.
l The SoftX3000 cannot support tone sending and number reanalysis for a call prefix at the same time.
Therefore, set Reanalysis to No. Otherwise, the system cannot perform the Send tone prefix processing
mode.
Example 5 (Sending Different Tones in Different Time Segments to Indicate

Successful Routing)
Introduction
The SoftX3000 acts as a tandem office, as shown in Figure 11-2. Subscriber A of SoftX3000 1
originates a call to subscriber C of SoftX3000 2. The SoftX3000 routes the call. After routing
the call successfully, the SoftX3000 sends a tone to notify subscriber A that this is an
international call. The SoftX3000 is required to send different tones in different time segments,
for example, sending "Good Morning, this is ..." in the morning.
Figure 11-2 Networking of the application scenario
SoftX3000_1 SoftX3000 SoftX3000_2

Scripts
//Add a time index.
ADD TMIDX: TMX=1, TYPE=PFXPRO, IDXTP=WIDX, WD=MON, TM=11;
ADD TMIDX: TMX=2, TYPE=PFXPRO, IDXTP=WIDX, WD=MON, TM=24;
NOTE
1. This time index is used when the call prefix is processed. Therefore, Service type must be set to Call
prefix processing.
2. Monday is divided into two time intervals, the interval from 0 to 11 o'clock is assigned with the time
index value of 1, and the interval from 11 to 24 o'clock is assigned with the time index value of 2.

NOTE
This command deletes the first 4 digits of the original called number.
//Add call prefix processing data. Set Call source code to 0, Local DN set to 0, and Call
prefix to 0310.
ADD PFXPRO: CSC=0, LP=0, PFX=K'0310, TMX=1, CCF=YES, SENDTONE=SDPT,
DDCX=54, ISREANA=NO, TT=PTN223;
ADD PFXPRO: CSC=0, LP=0, PFX=K'0310, TMX=2, CCF=YES, SENDTONE=SDPT,
DDCX=54, ISREANA=NO, TT=PTN221;
NOTE
1. To enable the SoftX3000 to play tones to callers, configure number analysis data and MRS resource
data correctly and upload the correct voice files to the MRS.
2. To enable the SoftX3000 to send routing successful tone to the callers who dial 0310, set Method of
sending tone to Send prompt tone.
3. The SoftX3000 cannot send tone and re-analyze number at the same time. Therefore, set Reanalysis
to No. Otherwise, the system cannot process the Send tone prefix.
4. After being configured with the preceding data, the SoftX3000 sends tone 96 (PTN223) during 0:00
to 11:00 a.m. of Monday and sends tone 94 (PTN221) during 11:00 a.m. to 24:00 of Monday.
Related tasks
None.
Related concepts
Number Change
11.2.9 Configuring Failure Processing Data
Introduction
In a dial-up call setup process, the call may fail due to certain reasons. If the system does not
perform any processing on the failed call, the caller can only hear the busy tone but cannot learn
the actual cause of the call failure. In such cases, when the dialed number is an unallocated
number or a wrong number, the subscriber may attempt to dial the number many times after the
call failure, thus reducing the call completion rate.

When a call or call connection fails, if the system notifies the subscriber of the failure cause or
prompts the subscriber to perform the next operation instead of sending the busy tone, it greatly
reduces the attempts of calls and increases the call completion rate of the system. For this
purpose, run ADD CFPRO to add the failure processing mode.
Note the following:
l The failure processing mode defined by running ADD CFPRO for a call prefix must
precisely match the failure cause code. That is, the system generates a call failure cause
code (which can be obtained by the User Status tracing task) if a call fails after the subscriber
dials the prefix. If the failure cause code is the same as a failure cause code defined in the
failure processing data table (that is, the failure cause code is precisely matched), the system
performs the failure processing defined in the failure processing data table. Run the ADD
CFPRO command to define the failure processing method. The SoftX3000 records the
corresponding tone ID in the CDR.
l You can run ADD PFXPRO to define a failure processing mode for a call prefix, but the
mode is unconditional. That is, the system regards the call to be failed whenever a subscriber
dials the call prefix. In this case, the system can either send the busy tone or specify the
failure cause code and then search for the failure processing mode of precise match in the
failure processing data table according to the failure cause code.
l You can run SET GRPAC to define a failure processing mode for black and white list call
barring. After the black and white list call barring is performed, the system can play the
subscriber defined tone, if the command is configured.
Example 1 (Unconditional Failure Processing, Used for Playing Number Change

Notice Tone)
Introduction
A carrier changes numbers 296XXXX into numbers 836XXXX. After a period of time, the
carrier requires the system to guide the callers who call numbers 296XXXX. That is, when a
subscriber dials the prefix 296, the system neither connects the call to the callee nor charges the
call prefix. Instead, the system plays a notification. For example, "The first three digits of the
number you dialed has changed to 836, please hang up and dial again."
Scripts
ADD CHGANA: CHA=200, PAY=NOCHG, CRM=TNSO;
NOTE
The local office does not charge the call prefix 296; however, if the call prefix 296 does not have a charging
case, the SoftX3000 may generate a large number of charging alarms. To avoid this problem, add a charging
case for the call prefix 296 and set Payer to No charge.

PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
PB1=1, AGIO1=100, TS2=00&00;
code to 254 (wildcard), and Charging case to 200.


NOTE
Payer of the charging case 200 is No charge. Therefore, the local office neither generates bills nor generates
charging alarms when a local subscriber (or incoming trunk) dials the prefix 296.
//Add the call prefix 296. Set Service category to Basic service, Service attribute to Local,
and Charging selection code to 296.
NOTE
The prefix 296 is used to play the number change notification tone. Therefore, set Minimum number
length and Maximum number length to 3.
//Add prefix processing data. Set Call prefix to 296, Failure process flag to Yes and Failure
cause code to CV_Number_Changed.
ADD PFXPRO: CSC=0, PFX=K'296, FPF=YES, FCC=DNC, SENDTONE=NST, ISREANA=YES;
NOTE
l For the tone playing implemented in prefix processing mode, when a caller or an incoming trunk dials
the mapping call prefix, the local office returns the answer signaling. As a result, the local office or the
peer office charges the caller incorrectly. To avoid this problem, select failure processing mode in the
prefix processing table.
l You can customize Failure cause code. The failure cause code that you select in the failure processing
data table, however, must be the same as the one you customized. In this example, the value is
CV_Number_Changed.
//Add failure processing data. Set Failure cause code to CV_Number_Changed, Failure
source code to 0, Processing type to Send signal tone, and Signal tone type to Number
changed notice tone.
ADD CFPRO: FCC=DNC, FSC=0, FPT=SIG, TT=CHGDIAL;
NOTE
When a subscriber or an incoming trunk dials the call prefix, the local office does not send an answer to
the caller or the peer office. This is to prevent the local office or the peer office from charging the caller
incorrectly. In such a case, Send answer signal is set to No.
Example 2 (Conditional Failure Processing, Used for Playing Unallocated Number

Tone and Wrong Number Tone)
Introduction
The SoftX3000 acts as an end office. The local office occupies the number resources
87XXXXXX, and the available number is 878XXXXX. To improve the call completion rate,
the carrier determines to implement the following measure: When a subscriber calls a subscriber
who belongs to the local office, the system plays the following announcements:
l "The subscriber you dialed is busy" if the callee is busy.
l "The subscriber you dialed cannot be connected temporarily" if the callee does not reply.
l "The number you dialed does not exist" or "The number you dialed is wrong."
Scripts

//Add failure processing data. Set Call prefix to 87 and Send answer signal to No.
ADD CFPRO: PFX=K'87, FCC=BUSY, FSC=0, FPT=SIG, TT=TSTE;
ADD CFPRO: PFX=K'87, FCC=NUA, FSC=0, FPT=SIG, TT=SPS;
ADD CFPRO: PFX=K'87, FCC=IDF, FSC=0, FPT=SIG, TT=NODN;
ADD CFPRO: PFX=K'87, FCC=NADN, FSC=0, FPT=SIG, TT=ERDN;
NOTE
Failure cause code must be defined correctly. If you are not sure about which failure cause code is used,
simulate a failed call and use the User Status tracing task on the maintenance console to obtain the related
failure cause code.
Example 3 (Conditional Failure Processing, Used for Reselecting Route)

Introduction
The SoftX3000 acts as a toll office in the local network. It has two subroutes to the peer toll
office: subroutes 0 and 1 are both direct subroutes. The subroutes on the SoftX3000 side are
selected based on percentage; the percentage of each subroute is 50%. To improve the call
completion rate, the carrier requires that the system select the next subroute when the SoftX3000
selects a subroute but fails to occupy the trunk (for example, the remote device is congested or
the trunk is occupied bi-directionally).
Scripts
//Add a call source. Set Call source code to 51 and Failure source code to 51.
ADD CALLSRC: CSC=51, CSCNAME="To toll", PRDN=1, FSC=51;
NOTE
The call source is used for the SS7 trunk between the local office and the peer toll office.
//Add failure processing data. Set Failure source code to 51 (mapping the trunk between local
office and peer toll office) and Processing type to Re-select route.
ADD CFPRO: FCC=FSCW, FSC=51, CSA=NTT, FPT=RSRT;
ADD CFPRO: FCC=FSCW, FSC=51, CSA=ITT, FPT=RSRT;
ADD CFPRO: FCC=TDUSD, FSC=51, CSA=NTT, FPT=RSRT;
ADD CFPRO: FCC=TDUSD, FSC=51, CSA=ITT, FPT=RSRT;
NOTE
l For easy description, this example provides only two kinds of failure cause codes, that is, remote device
congestion and bi-directional occupancy. In actual application, if you are not sure about which failure
cause code is used, simulate a failed call and use the User Status tracing task on the maintenance console
to obtain the related failure cause code.
l The local office acts as a toll office. Therefore, the command defines the service attribute for starting
the failure processing. That is, the system starts the failure processing when a call is a national toll call
or an international toll call.
//Add subroutes from the local office to the peer toll office.
ADD SRT: SRC=0, O=0, SRN="Direct route", RENT=URT;
ADD SRT: SRC=1, O=0, SRN="Bypass route", RENT=URT;
//Add routes from the local office to the peer toll office.
ADD RT: R=0, RN="To toll", SRST=PERC, SR1=0, SR2=1;

NOTE
In this example, sub-route selection mode is Select by percentage. The first subroute is subroute 0 and
its percentage is 50. The second subroute is subroute 1 and its percentage is 50. In such a case, the system
selects subroute 0 and subroute 1 according to the load sharing mode.
Example 4 (Conditional Failure Processing, Used for Reanalyzing Changed

Number)
Introduction
The SoftX3000 acts as an end office in the local network. The subscriber number has seven
digits and the office occupies the number 85XXXXX. The carrier performs number digit
expansion for the local network, and the number length is changed from seven digits to eight
digits. That is, the offices in the local network do not have a number with seven digits. The
number digit expansion principle is as follows:
l Add 8 before the original numbers with first prefixes as 2-5.
l Add 2 before the original numbers with first prefixes as 6-8.
In such a case, the new number that belongs to the local office is 285XXXXX. To reduce the
inconvenience caused due to digit expansion, the carrier requires that the callers be able to use
both the original number and new number to call a subscriber during the transition period.
However, the original numbers 58XXXXX (of other end offices) in the local network have
changed to 858XXXXX. This changed number may conflict with the original numbers
858XXXX of the local office. In such a case, when a subscriber in the local office dials the prefix
858, there are two options:
l If the dialed number consists of eight digits, the local office connects the call to 58XXXXX
through the trunk.
l If the dialed number consists of seven digits, the local office must perform the called number
change to process the call as an intra-office call.
Scripts
//Modify the digitmap of the local DN set.
MOD DMAP: PROTYPE=H248, DMAPIDX=0, PARTIDX=0, DMAP="[2-8]xxxxxx|
MOD DMAP: PROTYPE=MGCP, DMAPIDX=0, PARTIDX=0, DMAP="[2-8]xxxxxx|
MOD LDNSET: LP=0, DGMAPIDX=0, MDGMAPIDX=0;
NOTE
l In the transition period, to decrease the waiting time when a caller dials the original 7-digit number,
you are advised to define the length of the dial-up scheme in the digitmap used for the local network
call setup to the number length before digit expansion (that is, seven): [2-8]xxxxxx.
l If the number length is defined as eight, when a subscriber dials a 7-digit number, the integrated access
device (IAD) or the AMG does not send the dialed number to the SoftX3000 until the digitmap timer
times out. In such a case, the SoftX3000 is required to wait until the digitmap timer times out before
starting the triggering delay timer. This in turn causes the caller to wait for a long time after dialing a
number.
//Add call prefixes. Set 285 as an intra-office call prefix and 858 as a local call prefix (for
outgoing calls).
SDESCRIPTION="285_office", EA=NO;


CHSC=16, EA=YES, DP=7, DT=3, ASF=NO, QCDN=NO, VPNF=NOVC;
NOTE
l The call prefix 858 is used for outgoing calls. Therefore, you must correctly define parameters such as
Service attribute, Route selection code, and Charging selection code.
l For the call prefix 858, Minimum number length must be set to 8. If it is set to 7, after a subscriber
dials a 7-digit number, the system starts the number analysis program immediately according to the
service attribute defined by the call prefix 858. Thus, the triggering delay timer cannot be started.
l For the call prefix 858, Time delay trigger point and Triggering delay must be correctly defined. In
this example, Time delay trigger point must be set to 7 and Triggering delay is set to 3-5 seconds.

NOTE
The command inserts 2 before the original numbers.
//Add failure processing data. Set Failure cause code to Delay for insert number after increase
number length.
ADD CFPRO: PFX=K'858, FCC=CNF, FSC=0, CSA=LC, FPT=CPA, DCX=55;
NOTE
l Failure cause code must be correctly defined. In this example, Failure cause code is set to Delay for
insert number after increase number length.
l Processing type must be set to Re-analysis after number change and Number change index to
55.
l Service attribute of the call prefix 858 is Local. Therefore, Service attribute must be set to Local
for the normal start of the failure processing.
l After the preceding commands are executed, when a subscriber dials the call prefix 858 and the dialed
number is a 7-digit number, the system first inserts 2 before the original called number through failure
processing. Then, the system re-analyzes the number based on the number analysis table of local DN
set 0. At this time, the system starts the number analysis program according to the related attributes
defined by the call prefix 285. That is, the call is an intra-office call with the prefix 285 instead of a
local call with the prefix 858.
Example 5 (Black and White List Call Barring, Used for Reselecting Routes to the
Specified Carrier or Trunk Group)
Introduction
When a call is barred by black and white list, reselecting routes to the specified carrier or trunk
group.
Scripts
1. Configure black list call barring data for a trunk group.

(1) //Set inter-group call barring indication.
(2) //Add a caller number discrimination group. Set Function code to Modify caller
attribute and Barring group number to 222. Set other parameters based on the actual
requirement.
ADD CLRDSN: DSP=22, CLI=K'88810005, DSTYPE=NORT, DAI=ALL,
FUNC=ATT, GRP=222, CMN=NO;

NOTE
Barring group number must be defined by Source call barring group number in SET
GRPAC before being referenced here.
(3) //Add a called number barring group. Set Group category to Ordinary group and
Called barring group number to 333. Set other parameters based on the actual
requirement.
ADD CLDGRP: LP=0, CLD=K'88810006, GRPT=OG, GRP=333;
NOTE
Called barring group number must be defined by Destination call barring group
number in SET GRPAC before being referenced here.
(4) //Add a trunk discrimination group. Set Discrimination group number to 22. Set
other parameters based on the actual requirement.
ADD TGDSG: TGN="T_SX1_ISUP_SX2_6", DSG=22;
NOTE
Discrimination group number must be defined by Discrimination group number in ADD

CLRDSN before being referenced here.
2. //Add a call prefix 456 in local DN set 1, which should be different from the local DN set
of the incoming trunk. Set Local DN set to 1, Call prefix to 456, Route selection code to
20, Minimum number length to 3, Maximum number length to 24, and Charging
selection code to 0. Set other parameters based on the actual requirement.
NOTE
Route selection code must be defined in ADD RTANA before being referenced here, and the route
analysis data must allow the selection of routes to another trunk group for an outgoing call.
3. //Add the number change data. Set Number change type to Delete number. Set other
parameters based on the actual requirement.
4. //Add call prefix processing data. Set Call prefix to 456, Called number change flag to
YES, Called number change index to 3 (that is, delete the new call prefix 456 in local
DN set 1), and Reanalysis to NO. Set other parameters based on the actual requirement.
5. //Add the number change data. Set Number change type to Insert number. Set other
6. //Add call failure processing. Set Failure cause code to Black and white list
restriction, Processing type to Re-analysis after number change, Number change
index to 8 (that is, prefix the called number with the call prefix 456 configured in 2), and
New Local DNSet to 1 (this is the local DN set to which the call prefix 456 configured in
2 belongs). Set other parameters based on the actual requirement.
ADD CFPRO: LP=0, PFX=K'018, SEC=ENUMERATE, FCC=BWLBA, FSC=0, CSA=NTT,
FPT=CPA, DCX=8, NLP=1;
Example 6 (Black and White List Call Barring, Used for Playing Subscriber Defined
Tones)
Introduction

For the black and white list barring service, you can run SET GRPAC to set inter-group call
barring indication to instruct the system to play subscriber defined tones.
Scripts
//To set inter-group call barring indication, set Call indication to CDIS(Barring call). Set other
SET GRPAC: SRG=1, DRG=2, CI=CDIS, SIG=YES, TT=Other, EXTID=1000, SAS=NO;
NOTE
l You can also run the following command to instruct the system to play the subscriber defined tone
after the black and white list call barring.
SET GRPAC: SRG=1, DRG=2, CI=CDIS, SIG=YES, TT=Other, TN="hw001",
SAS=NO;
l EXTID and TN must be defined in ADD TONE before being referenced here.
Either EXTID or TN must be specified at least. If both of them are specified, EXTID and TN must
match.
Example 7 (Black and White List Call Barring, Used for Releasing a Call Due to
Special Reasons)
Introduction
When a call destined for a number listed in the black and white list is originated, the SoftX3000
releases the call with the internal cause value 77 or the external cause value 21 if the processing
modes described in examples 5 and 6 are not configured.
Scripts
None.
Example 8 (Conditional Failure Processing, Used for Skipping Subroute Group and
Rerouting)
Introduction
When the routing of an outgoing call fails, the SoftX3000 implements automatic rerouting
according to the failure processing data configuration.
Application background:

Figure 11-3 Typical networking where SoftX3000 A functions as a tandem office

SoftX3000 E
SoftX3000 C
User B
Subroute
SRT A/
SRT C
Subroute
SRT B/SRT D
SoftX3000 A
SoftX3000 D
User A
The carrier uses SoftX3000 A as a tandem office. Figure 11-3 shows the typical networking. If
A served by SoftX3000 A calls B served by SoftX3000 E, the call can be routed in the following
directions:
1. SoftX3000 A→SoftX3000 C→SoftX3000 E
2. SoftX3000 A→SoftX3000 D→SoftX3000 E
Subroutes SRT A and SRT C from SoftX3000 A to SoftX3000 C are configured.
Subroutes SRT B and SRT D from SoftX3000 A to SoftX3000 D are configured.
The carrier plans ROUTE A from SoftX3000 A to SoftX3000 E as shown in Figure 11-4.
Figure 11-4 Structure of the route tree

ROUTE 50% 50% SRTG 50%
SRTG A SRT A
A AA
Select by Select by Select by

percentage percentage percentage
SRT B
50%
SRTG
SRT C
50% AB
SRTG B SRT D
50%
NOTE
l ROUTE A is classified into the following two subroute groups based on carriers: SRTG A and SRTG
B. The subroute groups are selected by percentage.
l Subroute group SRTG A is classified into the following two subroute groups based on trunks: SRTG
AA and SRTG AB. The subroute groups are selected by percentage.

Application requirement:
To improve the call completion rate, the skipping subroute group and rerouting for failure
processing function is configured.
When SoftX3000 A successfully selects a subroute for routing a trunk call but receives a device
congestion message from the peer office, SoftX3000 A regards that the subroute group to which
the selected subroute belongs does not have the physical links available to the destination. In
such a case, SoftX3000 A skips the subroute group can select subroute from the next subroute
group.
That is, when A served by SoftX3000 A calls B served by SoftX3000 E, if SoftX3000 A first
selects SRT A for routing the call but receives a device congestion message from the peer office,
SoftX3000 A skips SRTG AA and selects the subroute SRT C in the subgroup SRTG AB for
routing the call to B.
NOTE
The skipped subroute group is the subroute group that contains the selected subroute directly.
Scripts
//Add a call source code with Call source code set to 0 and Failure source code to 10.
ADD CALLSRC: CSC=0, CSCNAME="TO TOLL", FSC=10;
//Add call failure processing with Failure source code to 10 (corresponding to the trunk between
the local office and the peer toll office) and Processing type to RSSRG.
ADD CFPRO: FCC=DCONG, FSC=10, CSA=ALL, TP=ALL, FPT=RSSRG;
NOTE
This example assumes that the failure cause code is device congestion. In the actual operation, if you are
not sure about which failure cause code is used, simulate a failed call and use the User Status tracing task
on the maintenance console to obtain the related failure cause code.
//Add office direction data.

ADD OFC: O=0, ON="C", DOT=INTT, DOL=LOW, DPC1="001100";
ADD OFC: O=1, ON="D", DOT=INTT, DOL=LOW, DPC1="110011";
//Add subroute data and use name to index the subroute.

ADD SRT: O=0, SRN="SRT A", RENT=URT;
ADD SRT: O=1, SRN="SRT B", RENT=URT;
ADD SRT: O=0, SRN="SRT C", RENT=URT;
ADD SRT: O=1, SRN="SRT D", RENT=URT;
//Add subroute group data and use name to index the subroute group.
ADD SRTG: SRTGN="SRTG AA", NAMECFG=YES, SNCM=SRT, SNSM=PERC, SRN1="SRT
A", SRN2="SRT B",
PERC1=50, PERC2=50;
ADD SRTG: SRTGN="SRTG AB", NAMECFG=YES, SNCM=SRT, SNSM=SEQ, SRN1="SRT C";
ADD SRTG: SRTGN="SRTG A", NAMECFG=YES, SNCM=SRTG, SNSM=PERC, SRN1="SRTG
AA", SRN2="SRTG AB",
PERC1=50, PERC2=50;
ADD SRTG: SRTGN="SRTG B", NAMECFG=YES, SNCM=SRT, SNSM=SEQ, SRN1="SRT D";
//Add local route data.

ADD RT: R=10, RN="ROUTE A", IDTP=UNKNOWN, NAMECFG=YES, SNCM=SRTG,

SRST=PERC, PERCCFG=YES,
SRN1="SRTG A", SRN2="SRTG B", PERC1=50, PERC2=50, REM=NO;
Related tasks
None.
Related concepts
Number Change
11.2.10 Configuring Trunk Group Bearer Data
Example 1 (Changing Contents and Address Nature of Caller Number)

Introduction
The SoftX3000 acts as a toll office in the local network and interworks with the upper-level toll
office through SS7 trunks. The carrier requires that when the end offices in the local network
originate toll calls, the caller information sent from the end offices to the toll office be subscriber
numbers. When the toll office transits outgoing toll calls in the local network, the toll office
changes the numbers into valid national numbers or valid international numbers according to
the call prefix and modifies the address nature of the callers correspondingly.
Scripts
ADD DNC: DCX=60, DCT=INS, DAI=NDN, ND=K'755;
ADD DNC: DCX=61, DCT=INS, DAI=IDN, ND=K'86755;
NOTE
l The first command means that the system inserts 755 (national toll area code) before the original
numbers, and changes Nature of address indicator of the numbers to National number.
l The second command means that the system inserts 86755 (country code + national toll area code)
before the original numbers, and changes Nature of address indicator of the numbers to International
number.
//Add SS7 trunk groups from the local office to the upper-level toll office. Trunk group 40 is an
outgoing trunk group and trunk group 41 is an incoming trunk group.
TGN="To toll office", PRTFLG=CN, NOAA=FALSE, ISM=FALSE, EA=FALSE;
TGN="To toll office", PRTFLG=CN, NOAA=FALSE, ISM=FALSE, EA=FALSE;
//Add trunk group bearer data. Bearer index 0 is used for national toll calls and bearer index 1
is used for international toll calls.
ADD TGLD: CLI=0, TOP=3, RI=60, EI=0;

NOTE
l In this example, bearer index 0 is used for national toll calls. The trunk seizure point is 3, the caller
number sending change index is 60, and the callee number sending change index is 0 (indicating no
change).
l In this example, bearer index 1 is used for international toll calls. The trunk seizure point is 5, the caller
number sending change index is 61, and the callee number sending change index is 0 (indicating no
change).
l In this example, the requirements can also be met through prefix processing, but the method affects
charging (modifying caller numbers in bills). Therefore, in actual application, use the appropriate
method depending on the specific requirements of the carrier.
//Add trunk group bearer index data (only for outgoing trunk groups).
ADD TGLDIDX: TG=40, CSC=0, LP=0, PFX=K'0, CLI=0;
NOTE
For outgoing trunk groups, define the trunk group bearer index, and define the national toll call prefix and
internal toll call prefix separately.
Example 2 (Changing Contents of Called Number)

Introduction
The SoftX3000 acts as a gateway office on the fixed carrier side of a city. The SoftX3000
interworks with the gateway office on the mobile carrier side of the city through SS7 trunks.
The two gateway offices bear all mobile call traffic of the local fixed subscribers. When a fixed
subscriber calls a local mobile subscriber, the subscriber can directly dial the number of the
mobile subscriber, such as 13X0123XXXX. When a fixed subscriber calls a mobile subscriber
in another network, the subscriber must dial 0 followed by the number of the mobile subscriber,
such as, 013XXXXXXXXX. In this example, when a PSTN subscriber dials 0 to call a non-
local mobile subscriber, 0 is deleted through trunk bearer before it is routed to the outgoing
trunk.
Scripts

NOTE
//Add SS7 trunk groups from the local office to the peer gateway office. Trunk group 50 is an
outgoing trunk group and trunk group 51 is an incoming trunk group.
TGN="To mobile office", PRTFLG=CN, NOAA=FALSE, ISM=FALSE, EA=FALSE;
TGN="To mobile office", PRTFLG=CN, NOAA=FALSE, ISM=FALSE, EA=FALSE;
//Add trunk group bearer data. Set Bearer index to 2.


NOTE
l In this example, the trunk seizure point is 3, the caller number sending change index is 0 (indicating
no change), and the callee number sending change index is 62.
l If trunk group bearer data is not configured, the trunk seizure point is determined by the greater of the
minimum number length in the callee number analysis table or the number of pre-received digits in the
call source table.
//Add trunk group bearer index data (only for an outgoing trunk group).
NOTE
In this example, Call Source code is used to indicate the calling subscribers to which the bearer index is
applicable.
Related tasks
None.
Related concepts
Number Change
11.3 Configuration Example of Route Data
11.3.1 Configuring Load-Sharing Routing Data

11.3.2 Configuring Alternative Routing Data
11.3.3 Configuring Dynamic Routing Data
11.3.4 Configuring Route Tree Data
11.3.5 Configuring Special Routing Data
11.3.6 Configuring M3UA Signaling Route Data
11.3.7 Dual Homing Data of Signaling Link in Priority Routing Mode
11.3.8 Super Trunk Routing Data
11.3.1 Configuring Load-Sharing Routing Data
Example
Introduction
In actual networking, if the outgoing traffic from an office to another office can be transmitted
through several routes, the traffic load is allocated to each route based on its specific bearer
capability.
Assume that there are two toll offices in a city for transiting all toll calls in the local network.
See Figure 11-5 for the networking model.

Figure 11-5 Networking model of a local network (1)

Toll Toll
office C office D
The first The second

route route
Tandem Tandem
office A office B
The SoftX3000 acts as tandem office A in the local network. It is required to achieve load sharing
of all outgoing toll traffic between routes from tandem office A to toll office C and toll office
D, by configuring routing data on the SoftX3000 side.
//Add two office directions. The office direction from the local office to toll office C is numbered
201, and that from the local office to toll office D is numbered 202.
ADD OFC: O=201, ON="To Office_C", DOT=CMPX, DOL=HIGH, DPC1="110033";
ADD OFC: O=202, ON="To Office_D", DOT=CMPX, DOL=HIGH, DPC1="110055";
//Add two sub-routes numbered 201 and 202 respectively.

ADD SRT: SRC=201, O=201, SRN="To Office_C", RENT=URT;
ADD SRT: SRC=202, O=202, SRN="To Office_D", RENT=URT;

ADD RT: R=201, RN="To Toll Office", SRST=PERC, SR1=201, SR2=202;
NOTE
l You can implement load-sharing routing in the SoftX3000 by running ADD RT.
l To achieve load-sharing routing correctly, set Sub-route selection mode to Select by percentage by
running ADD RT. In this example, set 1st sub-route to 201 and 2nd sub-route to 202 by running
ADD RT. Set Percentage of sub-route1 to 50 and Percentage of sub-route2 to 50 by running SET
SRTATTR.
l Sub-routes are grouped based on percentage. Therefore, regardless of the percentage configured for
each sub-route, the total percentage must be an integral multiple of 100. Otherwise, the system fails to
work.
//Add analysis data for the route destined for the toll office.

Related tasks
None.
Related concepts
Office Direction and Routes
11.3.2 Configuring Alternative Routing Data
Example 1 (Adopting Sequential Selection Mode)

Introduction
See Figure 11-6 for the networking model of a local network.
Figure 11-6 Networking model of a local network (2)

Tandem Tandem
office C office D
The
second The first
attemative attemative
route route
Direct route
End End
office A office B
Assume that the SoftX3000 acts as end office A in the local network. It is required to achieve
the following routing principles by configuring routing data on the SoftX3000 side:
l In normal cases, the SoftX3000 chooses the direct route first, that is, the route from end
office A to end office B.
l When the direct route is unavailable (due to fault or overflow), the SoftX3000 chooses the
first alternative route, that is, the route from end office A to tandem office D, and finally
to end office B.
l When both the direct route and the first alternative route are unavailable, the SoftX3000
chooses the second alternative route, that is, the route from end office A to tandem office
C, then to tandem office D, and finally to end office B.
Scripts
//Add three office directions. The office direction from the local office to end office B is
numbered 211, that from the local office to tandem office D is numbered 212, and that from the
local office to tandem office C is numbered 213.

ADD OFC: O=211, ON="To Office_B", DOT=CC, DOL=SAME, DPC1="112233";

//Add three subroutes that are numbered 211, 212 and 213. 211 is a direct subroute, 212 is the
first alternative subroute, and 213 is the second alternative subroute.
ADD SRT: SRC=211, O=211, SRN="To Office_B", RENT=URT;

ADD RT: R=211, IDTP="To Office_B", NAMECFG=NO, SNCM=SRT, SRST=SEQ,
SR1=211, SR2=212, SR3=213, STTP=INVALID, REM=NO;
NOTE
l You can implement alternative routing in the SoftX3000 by running ADD RT.
l If the sequential selection mode is adopted for the alternative route selection, set Sub-route selection
mode to Sequential selection. In addition, set 1st sub-route to 211, 2nd sub-route to 212, and 3rd
sub-route to 213.
//Add analysis data for the route destined for end office B.
R=211, ISUP=NOCHG, NCAI=ALL;
Example 2 (Adopting Selection by Percentage Mode)

Introduction
See Figure 11-6 for the networking model of a local network. Assume that the SoftX3000 acts
as end office A in the local network. It is required to achieve the following routing principles
by configuring routing data on the SoftX3000 side:
l In normal cases, the SoftX3000 chooses the direct route first, that is, the route from end
office A to end office B.
l When the direct route is unavailable, the SoftX3000 chooses the first or second alternative
route, and the two alternative routes share the load in the ratio of 60% : 40%.
Scripts
numbered 211, that from the local office to tandem office D is numbered 212, and that from the
local office to tandem office C is numbered 213.
ADD OFC: O=211, ON="To Office_B", DOT=CC, DOL=SAME, DPC1="112233";
//Add three subroutes that are numbered 211, 212 and 213. 211 is a direct subroute, 212 is the
first alternative subroute, and 213 is the second alternative subroute.

ADD RT: R=211, IDTP="To Office_B", NAMECFG=NO, SNCM=SRT, SRST=PERC,
SR1=211, SR2=212, SR3=213, STTP=INVALID, REM=NO;


NOTE
l You can implement alternative routing in the SoftX3000 by running ADD RT.
l To achieve the selection of alternative subroutes by percentage, set Sub-route selection mode to Select
by percentage. In addition, set 1st sub-route to 211, 2nd sub-route to 212, and 3rd sub-route to
213. Set Percentage of sub-route1 to 100, Percentage of sub-route2 to 60, and Percentage of sub-
route2 to 40 by running SET SRTATTR.
l Subroutes (five in total) are grouped based on percentage, that is, the subroute(s) whose total percentage
equals 100% are in one group. Each subroute in a group shares the traffic load based on its percentage,
and different groups are selected by sequence.
//Add analysis data for the route destined for end office B.
R=211, ISUP=NOCHG, NCAI=ALL;
Related tasks
None.
Related concepts
Direct route is the route selected for the first time during routing; alternative route is the route
selected for the second time or later during routing.
To improve networking reliability, two or more outgoing routes are planned for an office and
one of the routes is an alternative route. Thus, when the direct route is unavailable, the alternative
route can be used.
11.3.3 Configuring Dynamic Routing Data
Example 1 (Using Time Index)

Introduction
The SoftX3000 acts as end office A in a local network, and there are three routes between the
SoftX3000 and end office B in the same network. See Figure 11-7.

Figure 11-7 Networking model of a local network

Tandem
office C
End End
office A Tandem office B
office D
Tandem office C and tandem office D have different busy hours. To improve the circuit usage
between end office A and end office B, it is required to use different alternative routes during
busy and idle hours, by configuring routing data on the SoftX3000 side. See Table 11-5.
Table 11-5 Plan for selecting routes from end office A to end office B
Time Segment Routing Plan
00:00-07:59 Direct route: from end office A to end office B

21:00-23:59 Alternative route: from end office A to tandem
office C, and finally to end office B
08:00-20:59 Direct route: from end office A to end office B

Alternative route: from end office A to tandem
office D, and finally to end office B
Scripts
numbered 231, that from the local office to tandem office C is numbered 232, and that from the
local office to tandem office D is numbered 233.
ADD OFC: O=231, ON="To Office_B", DOT=CC, DOL=SAME, DPC1="1122aa";
ADD OFC: O=232, ON="To Office_C", DOT=CMPX, DOL=HIGH, DPC1="1122bb";
ADD OFC: O=233, ON="To Office_D", DOT=CMPX, DOL=HIGH, DPC1="1122cc";
//Add three subroutes that are numbered 231, 232 and 233. 231 is a subroute from office A to
office B, 232 is a subroute from office A to office C, and 233 is a subroute from office A to
office D.


//Add two routes numbered 232 and 233. 232 is a route selected during idle hours, and 233 is a
route selected during busy hours.
ADD RT: R=232, RN="A to C to B", SRST=SEQ, SR1=231, SR2=232;
ADD RT: R=233, RN="A to D to B", SRST=SEQ, SR1=231, SR2=233;
//Add two time indexes. Time index 1 ranges 00:00-07:59, and time index 2 ranges 08:00-20:59.
ADD TMIDX: TMX=1, TYPE=RT, IDXTP=WIDX, WD=SUN, TM=8;
ADD TMIDX: TMX=1, TYPE=RT, IDXTP=WIDX, WD=MON, TM=8;
ADD TMIDX: TMX=1, TYPE=RT, IDXTP=WIDX, WD=TUE, TM=8;
ADD TMIDX: TMX=1, TYPE=RT, IDXTP=WIDX, WD=WED, TM=8;
ADD TMIDX: TMX=1, TYPE=RT, IDXTP=WIDX, WD=THU, TM=8;
ADD TMIDX: TMX=1, TYPE=RT, IDXTP=WIDX, WD=FRI, TM=8;
ADD TMIDX: TMX=1, TYPE=RT, IDXTP=WIDX, WD=SAT, TM=8;
ADD TMIDX: TMX=2, TYPE=RT, IDXTP=WIDX, WD=SUN, TM=21;
ADD TMIDX: TMX=2, TYPE=RT, IDXTP=WIDX, WD=MON, TM=21;
ADD TMIDX: TMX=2, TYPE=RT, IDXTP=WIDX, WD=TUE, TM=21;
ADD TMIDX: TMX=2, TYPE=RT, IDXTP=WIDX, WD=WED, TM=21;
ADD TMIDX: TMX=2, TYPE=RT, IDXTP=WIDX, WD=THU, TM=21;
ADD TMIDX: TMX=2, TYPE=RT, IDXTP=WIDX, WD=FRI, TM=21;
ADD TMIDX: TMX=2, TYPE=RT, IDXTP=WIDX, WD=SAT, TM=21;
NOTE
l The SoftX3000 has preset the time index 0 during initialization. The time index table adopts the 24-
hour indication, by default. If you do not add any time index, time index 0 corresponds to 00:00-23:59.
l After you run the preceding commands, time index 1 corresponds to 00:00-07:59, time index 2
corresponds to 08:00-20:59, and time index 0 corresponds to 21:00-23:59.
l During routing, the SoftX3000 first matches the current time with the time and week in the time index
table. If they do not match, the routing fails. Therefore, exercise caution when configuring the time
index table.
//Add route analysis data. Set Route selection code to 231, Time index to 0, 1, and 2
respectively, and Route number to 232, 232, and 233 respectively.
TMX=0, R=232, ISUP=NOCHG, NCAI=ALL, CST=ALL, CNPI=ALL;
NOTE
l You can implement dynamic routing in the SoftX3000 by running ADD RTANA.
l If you divide a day into three time segments and set the same route selection code for them, you must
set a piece of route analysis data for each time index. Otherwise, the SoftX3000 fails in routing within
a specific time segment.
Example 2 (Using Time Segment Index)

Introduction
The SoftX3000 acts as end office A in a local network, and there are two routes between the
SoftX3000 and end office B in the same network. See Figure 11-8.

Figure 11-8 Networking model of a local network

Tandem
office C
End End
office A Tandem office B
office D
Tandem office C and tandem office D have different busy hours. To improve the circuit usage
between end office A and end office B, it is required to use different alternative routes during
busy and idle hours, by configuring routing data on the SoftX3000 side. See Table 11-6.
Table 11-6 Plan for selecting routes from end office A to end office B
Idle Time Period Routing Plan
00:00-12:00 From end office A to tandem office C and finally to

end office B
11:00-24:00 From end office A to tandem office D and finally to

end office B
Scripts
//Add two subroutes numbered 232 and 233 respectively. 232 is a subroute from office A to
office C and 233 is a subroute from office A to office D.

ADD RT: R=232, RN="A to C to B", IDTP=UNKNOWN, NAMECFG=NO, SNCM=SRT,

SRST=SEQ, PERCCFG=NO,
SR1=232, REM=NO;
ADD RT: R=233, RN="A to D to B", IDTP=UNKNOWN, NAMECFG=NO, SNCM=SRT,
SRST=SEQ, PERCCFG=NO,
SR1=233, REM=NO;
//Enable the time segment-based routing function.

//Add two time indexes. Time index 1 ranges 00:00-12:00, and time index 2 ranges 11:00:00
AM-24:00.
ADD TMSIDX: TMSX=1, IDXTP=WIDX, WD=EVERY, STM="00&00", ETM="12&00";
ADD TMSIDX: TMSX=2, IDXTP=WIDX, WD=EVERY, STM="11&00", ETM="24&00";
//Add route analysis data. Set Route selection code to 231, Time mode to Time segment mode,
Time index to 1 and 2 respectively, and Route number to 232 and 233 respectively.
ADD RTANA: RSC=231, RSSC=0, RUT=ALL, SAI=ALL, CLR=ALL, TP=ALL, TM=TMX,
TMSX=1, R=232, ISUP=NOCHG, NCAI=ALL, CST=ALL, CNPI=ALL;
ADD RTANA: RSC=231, RSSC=0, RUT=ALL, SAI=ALL, CLR=ALL, TP=ALL, TM=TMX,
TMSX=2, R=233, ISUP=NOCHG, NCAI=ALL, CST=ALL, CNPI=ALL;
NOTE
If the values of the other parameters except for Time segment index are the same, the time segments
referenced by the route analysis data records can overlap.
Related tasks
None.
Related concepts
Dynamic routing means that the exchange can update the routing data based on time, network
status, and event. The updated routing mode can be periodic, non-periodic, predefined, or can
change with the network status.
The SoftX3000 supports dynamic routing by time. The SoftX3000 allows route update within
a day or a week based on the preset time segment. That is, the SoftX3000 can select routes in
different time segments.
Routes can be selected dynamically based on the settings of Time index and Time segment
index.
If routes are selected based on the setting of Time segment index, the SoftX3000 finds all the
available routes based on the information about the caller and callee when selecting a route to
route out the call. Then, the SoftX3000 checks the time segment defined in Time segment
index. If the current time is within the time segment defined in Time segment index, the
SoftX3000 selects the route of the time segment to route out the call. If the current time is not
within the time segment defined in Time segment index, the SoftX3000 drops the call.
NOTE
To address different time division requirements, the time segments defined in time segment indexes can
overlap. The time defined in different time indexes, however, cannot be the same.
The Time index and Time segment index cannot be used at the same time. Bit 13 of p825
determines whether Time index or Time segment index is used. Bit 13 of p825 is set to 1 by

default, indicating that Time index is used in route analysis. When bit 13 of p825 is set to 0,
Time segment index is used in route analysis.
11.3.4 Configuring Route Tree Data
Example
Introduction
In the actual networking, a carrier can group the subroutes in terms of attributes for centralized
management and maintenance. This facilitates the daily data maintenance of the carrier. The
subscribers can also enjoy quality service.
The carrier uses SoftX3000 A as a tandem office. Figure 11-9 shows the typical networking.
ROUTE A from SoftX3000 A to SoftX3000 E has the following directions:
1. SoftX3000 A→SoftX3000 C→SoftX3000 E
2. SoftX3000 A→SoftX3000 D→SoftX3000 E
SIP trunks and ISUP trunks are used between SoftX3000 A and SoftX3000 C, and the subroutes
are SRT aaa, SRT aba, SRT ba, and SRT ca.
H.323 trunks, TUP trunks, and ISUP trunks are used between SoftX3000 A and SoftX3000 C,
and the subroutes are SRT aab, SRT abb, and SRT bb.
Figure 11-9 Route tree planning

SoftX3000 A SoftX3000 C
Subroute SRT aaa/SRT aba/
SRT ba/SRT ca
SIP/ISUP trunk
Subroute H323/ 1
SRT aab/ TUP/
SRT abb/ ISUP
SRT bb trunk
2
Voice
Channel
SoftX3000 D SoftX3000 E
The communications equipment of the carrier is provided by three manufacturers. The carrier
determines to group the subroutes on SoftX3000 A in terms of manufactures, as shown in Figure
11-10. Table 11-7 describes the route planning.

Figure 11-10 Route tree planning

1st layer of 2nd layer of 3rd layer of 4th layer of
route tree route tree route tree route tree
ROUTE A SRTG A SRTG AA SRT aaa

50% 60%
Select by percentage
Select by Sequential
percentage selection SRT aab
40%
SRTG AB SRT aba

70%
SRT abb
30%
SRTG B SRT ba
50% 50%
Sequential
selection SRT bb
50%
SRTG C
SRT ca
100%
Table 11-7 Description of route tree planning
1st 2nd Layer 3rd 3rd Layer 4th 4th Layer

Laye (In Terms of Layer Description Layer Description
r Manufactur
er)
ROU Subroute Subroute The subroutes are Subro Office direction:

TE A group SRTG group grouped in terms of ute SoftX3000 A→
A SRTG trunk type. This SRT SoftX3000 C, using
AA group contains the aaa SIP trunks
IP domain
subroutes in SRTG Subro Office direction:
A. ute SoftX3000 A→
SRT SoftX3000 D, using H.
aab 323 trunks
Subroute The subroutes are Subro Office direction:

group grouped in terms of ute SoftX3000 A→
SRTG trunk type. This SRT SoftX3000 C, using
AB group contains the aba ISUP trunks
circuit domain

1st 2nd Layer 3rd 3rd Layer 4th 4th Layer

Laye (In Terms of Layer Description Layer Description
r Manufactur
er)
subroutes in SRTG Subro Office direction:

A. ute SoftX3000 A→
SRT SoftX3000 D, using
abb TUP trunks
Subroute Subroute Office direction: - -

group SRTG SRT ba SoftX3000 A→
B SoftX3000 C,
using ISUP trunks
Subroute Office direction: - -

SRT bb SoftX3000 A→
SoftX3000 D,
using ISUP trunks
Subroute Subroute Office direction: - -

group SRTG SRT ca SoftX3000 A→
C SoftX3000 C,
using ISUP trunks
Scripts
The configuration scripts are as follows:
1. //Add office direction data.
//To configure SoftX3000 C and SoftX3000 D to the lower level offices of SoftX3000 A,
set Peer office level (DOL) to LOW.
ADD OFC: O=0, ON="C", DOT=INTT, DOL=LOW, DPC1="001100";
ADD OFC: O=1, ON="D", DOT=INTT, DOL=LOW, DPC1="110011";
2. //Add subroute data.
ADD SRT: O=0, SRN="SRT aaa", RENT=URT;
ADD SRT: O=1, SRN="SRT aab", RENT=URT;
ADD SRT: O=0, SRN="SRT aba", RENT=URT;
ADD SRT: O=1, SRN="SRT abb", RENT=URT;
ADD SRT: O=0, SRN="SRT ba", RENT=URT;
ADD SRT: O=1, SRN="SRT bb", RENT=URT;
ADD SRT: O=0, SRN="SRT ca", RENT=URT;
3. //Add outgoing trunk data.
//To add an H.323 trunk, set Trunk type to TRNK when both the local office and the peer
office use softswitches.
ADD SIPTG: TGN="aaa", SRN="SRT aaa", NOAA=NO, EA=NO;
ADD H323TG: TRUNKNAME="aab", CSC=0, SRN="SRT aab", TRNKTYPE=TRNK,
TRNKIP="160.11.12.20", EA=NO;
ADD N7TG: TGN="aba", EID="160.11.12.10:2944", G=OUT, SRN="SRT aba",
NOAA=FALSE, ISM=FALSE, EA=FALSE;
ADD N7TG: TGN="abb", EID="160.11.12.10:2944", G=OUT, SRN="SRT abb",
ADD N7TG: TGN="ba", EID="160.11.12.10:2944", G=OUT, SRN="SRT ba",

ADD N7TG: TGN="bb", EID="160.11.12.10:2944", G=OUT, SRN="SRT bb",

ADD N7TG: TGN="ca", EID="160.11.12.10:2944", G=OUT, SRN="SRT ca",
4. //Add outgoing subroute group data.
//Subroute group SRTG AA and subroute group SRTG AB are subnodes of subroute group
SRTG A. Before configuration the data of SRTG A, configure the data of SRTG AA and
SRTG AB. Then, they can be referenced by SRTG A.
ADD SRTG: SRTGN="SRTG AA", NAMECFG=YES, SNCM=SRT, SNSM=PERC,
SRN1="SRT aaa", SRN2="SRT aab", PERC1=60,
PERC2=40;
ADD SRTG: SRTGN="SRTG AB", NAMECFG=YES, SNCM=SRT, SNSM=PERC,
SRN1="SRT aba", SRN2="SRT abb", PERC1=70,
PERC2=30;
ADD SRTG: SRTGN="SRTG A", NAMECFG=YES, SNCM=SRTG, SNSM=SEQ,
SRN1="SRTG AA", SRN2="SRTG AB";
ADD SRTG: SRTGN="SRTG B", NAMECFG=YES, SNCM=SRT, SNSM=PERC, SRN1="SRT
aa", SRN2="SRT bb", PERC1=50,
PERC2=50;
ADD SRTG: SRTGN="SRTG C", NAMECFG=YES, SNCM=SRT, SRN1="SRT ca";
5. //Add outgoing route data.
ADD RT: RN="ROUTE A", IDTP=UNKNOWN, NAMECFG=YES, SNCM=SRTG,
SRST=PERC, PERCCFG=YES, SRN1="SRTG A",
SRN2="SRTG B", SRN3="SRTG C", PERC1=50, PERC2=50, PERC3=100, REM=NO;
Related tasks
None.
Related concepts
Office Direction and Routes
11.3.5 Configuring Special Routing Data

The SoftX3000 provides a flexible route authentication function. The SoftX3000 determines
whether an outgoing call has the right to use a route and which route is selected, based on
conditions such as:
l Route selection source code
l Caller type
l Address indicator
l Transmission capability
l Time
This function meets the requirements for the routing policy in various special applications.
Example 1 (Routing Based on Route Selection Source Code)

Introduction
The SoftX3000 acts as end office A in a local network and has direct routes to end office B, and
tandem offices C and D. See Figure 11-11.

Figure 11-11 Routes for outgoing toll calls originated from end office A
Tandem Tandem
office C office D
The first The second

route route
Alternative
End route End
office A office B
According to the planning, all outgoing toll calls originated from end office A must be transferred
by tandem office C or D. Therefore, there are three outgoing routes for end office A:
l The first route (A→C)
l The second route (A→D)
l The alternative route (A→B→D)
The alternative route for toll calls has limited bearer capability. Therefore, it is required to divide
the local subscribers into two groups to avoid overload on the alternative route when both the
first and the second routes are faulty. Some subscribers (whose call source code is 0) can use all
routes and the other subscribers (whose call source code is 1) are prohibited from using the
alternative route.
Scripts
//Add two call sources. Set Call source code to 0 and 1 respectively, Route selection source
code of call source 0 to 0, and Route selection source code of call source 1 to 1.
ADD CALLSRC: CSC=0, CSCNAME="Group_0", PRDN=1, RSSC=0;
ADD CALLSRC: CSC=1, CSCNAME="Group_1", PRDN=1, RSSC=1;
//Add 32 ESL subscribers. Set Call source code of subscribers 6540000-6540015 to 0, and that
of subscribers 8780000-8780015 to 1.
EID="191.169.150.89:2944", STID="0", CODEC=PCMA, RCHS=65, CSC=0,
EID="191.169.150.90:2944", STID="0", CODEC=PCMA, RCHS=87, CSC=1,

//Add three subroutes that are numbered 231, 232 and 233. 231 is a subroute from office A to
office B, 232 is a subroute from office A to office C, and 233 is a subroute from office A to
office D.
//Add two routes numbered 232 and 233 respectively. All subroutes of route 232 can be used
for outgoing calls. The alternative subroute of route 233 is prohibited from being used for
outgoing calls.
ADD RT: R=232, RN="For all SRT", SRST=PERC, SR1=232, SR2=233, SR3=231;
SET SRTATTR: R=232, SR=233, PSR=50;ADD RT: R=233, RN="Except alt-SRT",
SRST=PERC, SR1=232, SR2=233;
NOTE
For route 232, selection of alternative subroutes based on percentage is adopted.
//Add two pieces of route analysis data. Set Route selection code to 231 for both data. Set Route
selection source code to 0 and Route number to 232 for the first piece of data. Set Route
selection source code to 1 and Route number to 233 for the second piece of data.
NOTE
The route selection source code is an attribute of the call source. Therefore, you can define different route
analysis data for the route selection source codes (call sources).
Example 2 (Routing Based on Caller Type)

Introduction
The SoftX3000 acts as a toll office in a city and has three routes to the upper-level toll office.
According to the planning, the SoftX3000 allows subscribers with the highest priority to use all
routes (routes 1, 2 and 3) when transiting outgoing toll calls started locally, and allows the other
subscribers to use only the specified two routes (routes 1 and 2).
Scripts
//Modify the attribute of 16 ESL subscribers. Change Subscriber type of subscribers

6540000-6540015 to Prior.
MOB VSBR: SD=K'6540000, ED=K'6540015, LP=0, UTP=PRI;

ADD OFC: O=1, ON="To Office_A", DOT=CMPX, DOL=HIGH, DPC1="1122aa";
ADD OFC: O=2, ON="To Office_B", DOT=CMPX, DOL=HIGH, DPC1="1122bb";
ADD OFC: O=3, ON="To Office_C", DOT=CMPX, DOL=HIGH, DPC1="1122cc";

ADD SRT: SRC=1, O=1, SRN="To Office_A", RENT=URT;

//Add two routes numbered 1 and 2 respectively. All subroutes of route 1 can be used for outgoing
calls. Only subroutes 1 and 2 of route 2 can be used for outgoing calls.
ADD RT: R=1, RN="For all SRT", SRST=PERC, SR1=1, SR2=2, SR3=3;
ADD RT: R=2, RN="Except SRT_3", SRST=PERC, SR1=1, SR2=2;
//Add two pieces of route analysis data. Set Route selection code to 0 for both data. Set Caller
category to Priority and Route number to 1 for the first piece of data. Set Caller category to
All categories and Route number to 2 for the second piece of data.
ADD RTANA: RSC=0, RSSC=0, RUT=PRI, SAI=ALL, CLR=ALL, TP=ALL, TMX=0, R=1,
NOTE
When the call processing software performs route analysis, if Caller category in several pieces of route
analysis data matches the current call, the parameter value All categories takes the lowest priority for
analysis.
Example 3 (Routing Based on Address Indicator)

Introduction
There are two toll offices in a city for transiting all toll calls in the local network. See Figure
11-12 for the networking model.
Figure 11-12 Route for toll calls from toll office C to end office A
Toll Toll
office C office D
The first
alternative route
The second
alternative route
Direct
route
End End
office A office B

Assume that the SoftX3000 acts as toll office C and has direct routes to end offices A and B and
toll office D in the local network. According to the planning, the SoftX3000 routes toll calls to
end office A in the following manner:
l National toll calls: The SoftX3000 selects the direct route (C→A) first, and then the first
alternative route (C→D→A).
l International toll calls: The SoftX3000 selects the direct route (C→A) first, and then the
first alternative route (C→D→A), and finally the second alternative route (C→B→A).
Scripts
//Add three office directions. The office direction from the local office to end office A is
numbered 231, that from the local office to end office B is numbered 232, and that from the local
office to toll office D is numbered 233.
ADD OFC: O=231, ON="To Office_A", DOT=CC, DOL=LOW, DPC1="1122aa",;
ADD OFC: O=232, ON="To Office_B", DOT=CC, DOL=LOW, DPC1="1122bb";
ADD OFC: O=233, ON="To Office_D", DOT=CMPX, DOL=SAME, DPC1="1122cc";
//Add three subroutes numbered 231, 232 and 233 respectively. 231 is a subroute from office C
to office A, 232 is a subroute from office C to office B, and 233 is a subroute from office C to
office D.
ADD SRT: SRC=231, O=231, SRN="To Office_A", RENT=URT;
//Add two routes numbered 232 and 233 respectively. All subroutes of route 232 can be used
for outgoing calls. The second alternative subroute of route 233 cannot be used for outgoing
calls.
ADD RT: R=232, RN="For all SRT", SRST=SEQ, SR1=231, SR2=233, SR3=232;
ADD RT: R=232, RN="Except alt-SRT", SRST=SEQ, SR1=231, SR2=233;
//Add two pieces of route analysis data. Set Route selection code to 231 for both data. Set
Service attribute to International toll and Route number to 232 for the first piece of data. Set
Service attribute to All categories and Route number to 233 for the second piece of data.
ADD RTANA: RSC=231, RSSC=0, RUT=ALL, SAI=INTT, CLR=ALL, TP=ALL, TMX=0,
NOTE
When the call processing software performs route analysis, if Service attribute in several pieces of route
analysis data matches the current call, the parameter value All categories takes the lowest priority for
analysis.
Related tasks
None
Related concepts
None
11.3.6 Configuring M3UA Signaling Route Data

Example 1 (Configuring M3UA Signaling Route in Load Sharing Mode)

Introduction
Assume that the SoftX3000 acts as an ASP in a local network and interworks with a PSTN switch
(an SP in the signaling network), as shown in Figure 11-13.
Figure 11-13 Signaling networking model of a local network (1)
Normal SG 1 STP 1
route
ASP SP
Normal
route SG 2 STP 2
It is required to achieve load sharing of signaling traffic between two normal routes from the
ASP to the SP by configuring signaling route data on the SoftX3000 side.
Scripts
//Add two M3UA Linksets. Set Adjacent entity index of Linkset 1 to 10 and that of Linkset 2
to 20.
NOTE
Route context can be a decimal number or null (the value is not set). Route context should be consistent
with that on the SG7000 side when the SoftX3000 interworks with the SG7000.
//Add three M3UA destination entities. The DSP index 10 represents SG1 that is connected with
the SoftX3000 directly. The DSP index 20 represents SG2 that is connected with the SoftX3000
directly. The destination entity index 30 represents the SP.
ADD M3DE: DEX=10, LEX=0, DENAME="SG1", DPC="001171", STPF=TRUE, DET=SG;
ADD M3DE: DEX=30, LEX=0, DENAME="SP", DPC="1100cc", DET=SP;
NOTE
l Set STP flag and Adjacent flag correctly based on the actual networking conditions. Otherwise, you
may fail to add the M3UA route when you run ADD M3RT.
l For the SP with the destination entity index 30, to achieve load sharing of signaling traffic between
two normal routes from the ASP to the SP, set Linkset select mask to the default value B1111.
to 20.

NOTE
l In the M3UA protocol, one M3UA Linkset stands for a signaling route. In this example, two M3UA
Linksets must be configured.
l The traffic mode of a Linkset determines only the work mode of all M3UA links in this Linkset. The
traffic mode of a Linkset is not related to the signaling route selection. Unless otherwise specified, set
Traffic mode of a Linkset to Load-share mode, which must be the same as that set on the SG side.
//Add two M3UA links. Link 0 that resides in BSGI 136 belongs to Linkset 1; link 0 that resides
in BSGI 137 belongs to Linkset 2.
ADD M3LNK: MN=136, LNKN=0, LNKNAME="To SG1", LOCIP1="191.169.150.30",
PEERIP1="191.169.150.70", CS=C, LSX=1;
PEERIP1="191.169.150.71", CS=C, LSX=2;
NOTE
To ensure the reliability of the M3UA links, if two BSGIs are equipped in the SoftX3000, allocate the two
M3UA links to different BSGIs.
//Add two M3UA routes destined for the SP, with the destination entity index being 30 and the
route priority being 0.
ADD M3RT: RTNAME="To SP_1", DEX=30, LSX=1, PRI=0;
NOTE
The signaling routes from the ASP to the SP through SG1 and SG2 are normal routes. Therefore, they must
enjoy the same priority. Otherwise, load sharing cannot be achieved.
Example 2 (Configuring M3UA Signaling Route in Active/Standby Mode)

Introduction
Assume that the SoftX3000 acts as an ASP in a local network and interworks with a PSTN switch
(an SP in the signaling network), as shown in Figure 11-14.
Figure 11-14 Signaling networking model of a local network (2)

Normal SG 1 STP 1
route
ASP SP
Alternative
route SG 2 STP 2
Configure signaling route data on the SoftX3000 side to meet the following requirements:
l In normal cases, the SoftX3000 chooses the normal route from the ASP to the SP.
l If the normal route is unavailable, the SoftX3000 uses the alternative route.
Scripts
//Add an M3UA local entity. Set Local entity index to 0 and Local entity point code to
001122.


NOTE
Route context can be a decimal number or null (the value is not set). Route context should be consistent
with that on the SG7000 side when the SoftX3000 interworks with the SG7000.
//Add three M3UA destination entities. The DSP index 10 represents SG1 that is connected with
the SoftX3000 directly. The DSP index 20 represents SG2 that is connected with the SoftX3000
directly. The destination entity index 30 represents the SP.
ADD M3DE: DEX=30, LEX=0, DENAME="SP", DPC="1100cc", DET=SP;
NOTE
Set STP flag and Adjacent flag correctly based on the actual networking conditions. Otherwise, you may
fail to add the M3UA route when you run ADD M3RT.
to 20.
NOTE
l In the M3UA protocol, one M3UA Linkset stands for a signaling route. In this example, two M3UA
Linksets must be configured.
l The traffic mode of a Linkset determines only the work mode of all M3UA links in this Linkset. The
traffic mode of a Linkset is not related to the signaling route selection. Unless otherwise specified, set
Traffic mode of a Linkset to Load-share mode, which must be the same as that set on the SG side.
//Add two M3UA links. Link 0 that resides in BSGI 136 belongs to Linkset 1; link 0 that resides
in BSGI 137 belongs to Linkset 2.
PEERIP1="191.169.150.70", CS=C, LSX=1;
PEERIP1="191.169.150.71", CS=C, LSX=2;
NOTE
To ensure the reliability of the M3UA links, if two BSGIs are equipped in the SoftX3000, allocate the two
M3UA links to different BSGIs.
//Add two M3UA routes destined for the SP. Set Destination entity index to 30, Priority of
Linkset 1 to 0, and Priority of Linkset 2 to 1.
NOTE
l The normal route from the ASP to the SP through SG1 takes the highest priority. Therefore, Priority
of the normal route is set to 0.
l The alternative route from the ASP to the SP through SG2 takes a lower priority than the normal route.
Therefore, Priority of the alternative route must be set to 1. Otherwise, the ASP cannot choose the
normal route preferentially.
Related tasks
None.

Related concepts
A signaling route is a predefined path for signaling messages to be sent from a signaling point
(SP) to a destination. Depending on the specific features and functions, signaling routes are
classified into the following types:
l Normal route
It refers to the route for transmitting signaling traffic in normal conditions. When an SP
has several signaling routes in a signaling network:
– If one of the signaling routes is a direct route (adopting the direct connection mode),
the direct route is the normal route.
– If all signaling routes of the SP are transferred by the signaling transfer point (STP)
(adopting the quasi-associated mode), the shortest one is the normal route.
– If two signaling routes in the quasi-associated mode share the load, they are both normal
routes.
l Alternative route
It refers to the route for transmitting signaling traffic when the normal route is unavailable
due to the fault in the signaling link or route. It is a quasi-associated route transferred by
STP(s). It can be one or multiple routes. If there are multiple alternative routes, they should
be labeled as the first alternative route, the second alternative route and so on in ascending
order based on the number of times that the routes pass through the STP.
l Choose the normal route first. Choose the alternative route only when the normal route is
unavailable due to a fault in the route.
l If there are multiple alternative routes, choose the first alternative route that takes a higher
priority. If the first alternative route is unavailable, choose the second one. Other cases can
be deduced in the same manner.
Among normal or alternative routes, if there are two routes with the same priority, the load
should be shared between the two routes. That is, each route should carry 50% of the whole
signaling traffic.
11.3.7 Dual Homing Data of Signaling Link in Priority Routing

Mode
Example
Introduction
When the signaling links between the SoftX3000 and M3UA signaling gateways (SGWs) (such
as the SG7000 of Huawei) work in dual homing mode, the priority routing mode is
recommended. See Figure 11-15.

Figure 11-15 Networking model of the priority routing mode
A B
SoftX3000 M3UA link SoftX3000
C D
SG7000 SG7000
MTP link
E
Exchange
As shown in Figure 11-15, assume that the SGW is SG7000, and the SoftX3000 adopts the
M3UA protocol to interwork with the SG7000. It is required to implement dual homing of the
signaling links in priority routing mode, by configuring M3UA signaling data on SoftX3000 A
and SoftX3000 B.
l On SoftX3000 A, set the SP of SoftX3000 B as the mutual assistant SP. On SoftX3000 B,
set the SP of SoftX3000 A as the mutual assistant SP too.
l Configure two M3UA Linksets on SG7000 C. Linkset 0 stands for the M3UA route from
SG7000 C to SoftX3000 A, and Linkset 1 stands for the M3UA route from SG7000 C to
SoftX3000 B.
l Configure two M3UA routes on SG7000 C. SoftX3000 A is the destination entity for both
routes. The first M3UA route, with the highest priority, uses Linkset 0 and stands for the
direct signaling route from SG7000 C to SoftX3000 A, that is, C->A. The second M3UA
route, with the lowest priority, uses Linkset 1 and stands for the alternative signaling route
from SG7000 C to SoftX3000 A, that is, C->B->A.
l In normal cases, the signaling route C->A takes the highest priority. Therefore, SG7000 C
sends signaling messages to SoftX3000 A directly. When SoftX3000 A is faulty,
SoftX3000 B acts as the mutual assistant to take over all the services of SoftX3000 A. All
the signaling messages are then transferred through SoftX3000 B. On SoftX3000 B, the
SP of SoftX3000 A is set as the mutual assistant SP. Therefore, SoftX3000 B can directly
process the signaling messages whose DSP is SoftX3000 A.
Script (SoftX3000 A)
//Configure local office information. The signaling point code (SPC) of the local office
(SoftX3000 A) is 001122.
SET OFI: OFN="SZSX A", LOT=CMPX, NN=YES, SN1=NAT, SN2=NAT, SN3=NAT,
//Add SPC data. Set OPC index to 1, OPC of SoftX3000 B to 001133, and Master/Slave
type to Slave (this indicates that in normal cases, the mutual assistance function of the SP is
activated).
ADD OFI: IDX=1, OPC="001133", MSTYPE=SLAVE;


NOTE
l When the SP mutual assistance is started in the local office, data of the signaling routing to the local
office, configured on the SG7000 side, must be consistent with data configured in the local office.
Assume that the original SPs A and B in the local office are mutual assistant nodes, then the DSPs A
and B on the SG7000 side must be set as STPs. In addition, two alternative routes should be added,
one from A to B, and the other from B to A.
//Add two M3UA local entities. The OPC of local entity index 0 is 001122 and the OPC of local
entity index 1 is 001133.
ADD M3LE: LEX=0, LENAME="A office", OPC="001122", LET=AS, RC=12345;
ADD M3LE: LEX=1, LENAME="B office", OPC="001133", LET=AS, RC=54321;
//Add two M3UA destination entities. The destination entity index 10 stands for SG7000 C and
destination entity index 11 stands for SG7000 D.
ADD M3DE: DEX=10, LEX=0, DENAME="SG C", DPC="001177", STPF=TRUE, DET=SG;
ADD M3DE: DEX=11, LEX=0, DENAME="SG D", DPC="001188", STPF=TRUE, DET=SG;
//Add two M3UA destination entities. The destination entity index 20 stands for exchange E
using local entity index 0 and destination entity index 30 stands for exchange E using local entity
index 1.
ADD M3DE: DEX=20, LEX=0, DENAME="E office", DPC="1100cc", DET=SP;
//Add two M3UA Linksets. Linkset index 0 corresponds to adjacent entity index 10 and Linkset
index 1 corresponds to adjacent entity index 11.
ADD M3LKS: LSX=0, LSNAME="To SG C", ADX=10, WM=ASP;
ADD M3LKS: LSX=1, LSNAME="To SG D", ADX=11, WM=ASP;
//Add four M3UA links. The first two links belong to Linkset 0 and the other two links belong
to Linkset 1.
ADD M3LNK: MN=136, LNKN=0, LNKNAME="To SG C #0", LOCIP1="191.169.150.30",
PEERIP1="211.169.150.70", CS=C, LSX=0;
LOCPORT=2911, PEERIP1="211.169.150.70", CS=C, LSX=0;
ADD M3LNK: MN=136, LNKN=1, LNKNAME="To SG D #0", LOCIP1="191.169.150.30",
PEERIP1="211.169.150.71", CS=C, LSX=1;
NOTE
To ensure the reliability of M3UA links, allocate M3UA links destined for the same DSP to different BSGI
modules.
//Add two M3UA routes destined for exchange E. Set Destination entity index to 20,
Priority of Linkset 0 to 0, and Priority of Linkset 1 to 1.
ADD M3RT: RTNAME="To E office", DEX=20, LSX=0, PRI=0;


Script (SoftX3000 B)
//Configure local office information. The SPC of the local office (SoftX3000 B) is 001133.
SET OFI: OFN="SZSX B", LOT=CMPX, NN=YES, SN1=NAT, SN2=NAT, SN3=NAT,
//Add SPC data. Set OPC index to 1, OPC of SoftX3000 A to 001122, and Master/Slave
type to Slave (this indicates that in normal cases, the mutual assistance function of the SP is
activated).
ADD OFI: IDX=1, OPC="001122", MSTYPE=SLAVE;
NOTE
l When the SP mutual assistance is started in the local office, data of the signaling routing to the local
office, configured on the SG7000 side, must be consistent with data configured in the local office.
Assume that the original SPs A and B in the local office are mutual assistant nodes, then the DSPs A
and B on the SG7000 side must be set as STPs. In addition, two alternative routes should be added,
one from A to B, and the other from B to A.
//Add two M3UA local entities. The OPC of local entity index 0 is 001133 and the OPC of local
entity index 1 is 001122.
ADD M3LE: LEX=0, LENAME="A office", OPC="001133", LET=AS, RC=12345;
ADD M3LE: LEX=1, LENAME="B office", OPC="001122", LET=AS, RC=54321;
//Add two M3UA destination entities. The destination entity index 10 stands for SG7000 D and
destination entity index 11 stands for SG7000 C.
ADD M3DE: DEX=10, LEX=0, DENAME="SG D", DPC="001188", STPF=TRUE, DET=SG;
ADD M3DE: DEX=11, LEX=0, DENAME="SG C", DPC="001177", STPF=TRUE, DET=SG;
//Add two M3UA destination entities. The destination entity index 20 stands for exchange E
using local entity index 0 and destination entity index 30 stands for exchange E using local entity
index 1.
//Add two M3UA Linksets. Linkset index 0 corresponds to adjacent entity index 10 and Linkset
index 1 corresponds to adjacent entity index 11.
ADD M3LKS: LSX=0, LSNAME="To SG D", ADX=10, WM=ASP;
ADD M3LKS: LSX=1, LSNAME="To SG C", ADX=11, WM=ASP;
//Add four M3UA links. The first two links belong to Linkset 0 and the other two links belong
to Linkset 1.
PEERIP1="211.169.150.71", CS=C, LSX=0;


PEERIP1="211.169.150.70", CS=C, LSX=1;
NOTE
To ensure the reliability of M3UA links, allocate M3UA links destined for the same DSP to different BSGI
modules.
Related tasks
None
Related concepts
None
11.3.8 Super Trunk Routing Data
Example
Introduction
A carrier uses the SoftX3000 A and switch H6 as gateway offices. The super trunk is used
between the two gateway offices. Figure 11-16 shows the typical networking.
requirements:
l SoftX3000 A and switch H6 use the uniform routing policy. The sequence for selecting
routes from SoftX3000 A to SoftX3000 B is the same as that from switch H6 to SoftX3000
B. The sequence is as follows:
sub-route A > sub-route B > sub-route C > sub-route D > sub-route E > sub-route F
l SoftX3000 A is connected to switch H6 through the super trunk trunk group. super
trunk is configured in indirect sub-route S.
l When routing out a call to SoftX3000 B, SoftX3000 A selects sub-route C if sub-routes A
and B are unavailable. SoftX3000 A routes out the call to switch H6 through the super trunk
in indirect sub-route S. Then, switch H6 routes out the call to the callee served by
SoftX3000 B through its sub-route C.

Figure 11-16 Networking when the super trunk is used
SoftX3000 A Switch H6
Super trunk
Indirect sub-route S
Sub- Sub- Sub- Sub- Sub-route Sub-

route A route B route D route C E route F
Communication Communication
Network Network
SoftX3000 B
Table 11-8 lists the data planning.

NOTE
This data planning is for your reference only. In the actual situation, plan the data based on the deployment
data of the field office.
Table 11-8 Data planning

Category Parameter Name Example How to Obtain
Subroute data Office direction SoftX3000 A- It is planned by

name (O) >SoftX3000 B: 1 carriers.
SoftX3000 A-
>Switch H6: 0
Sub-route selection Select by cost It is negotiated with

mode (SRST) the switch H6 side.
Sub-route name A, B, C, D, E, F It is negotiated with

(SRN) the switch H6 side.
Percentage of sub- A: 50 It is negotiated with

route (PSR) B: 25 the switch H6 side.
C: 25
D: 50
E: 25
F: 25

Category Parameter Name Example How to Obtain
Cost of sub-route A: 1 It is negotiated with

(CST) B: 1 the switch H6 side.
C: 1
D: 2
E: 2
F: 2
Number change data Number change C: 2 It is planned by

index (DCX) E: 6 carriers.
F: 8
Number conversion Insert number (INS) It is planned by

type (DCT) carriers.
Change location 0 It is planned by

(DCP) carriers.
New number (ND) 2: 222 It is negotiated with

6: 666 the switch H6 side.
8: 888
Indirect subroute Indirect sub-route S It is planned by

data name (ISNAME) carriers.
Charge with number Callee number It is planned by

changed (CNC) (CLD) carriers.
Scripts
The script for configuring data on SoftX3000 A is as follows:
//Configure the route to the destination office SoftX3000 B as route 1. Route 1 contains sub-
routes A, B, C, D, E, and F. The subroutes of route 1 are selected based on cost.
ADD RT RN="Route1", IDTP=UNKNOWN, NAMECFG=YES, SNCM=SRT, SRST=COST,
SRN1="A", SRN2="B", SRN3="C", SRN4="D", SRN5="E", SRN6="F", STTP=INVALID,
REM=NO;
//Configure the cost and percentage information about sub-routes A, B, C, D, E, and F.

SET SRTATTR: RN="Route1", SRN="A", PSR=50, CST=1;
SET SRTATTR: RN="Route1", SRN="B", PSR=25, CST=1;
SET SRTATTR: RN="Route1", SRN="C", PSR=25, CST=1;
SET SRTATTR: RN="Route1", SRN="D", PSR=50, CST=2;
SET SRTATTR: RN="Route1", SRN="E", PSR=25, CST=2;
SET SRTATTR: RN="Route1", SRN="F", PSR=25, CST=2;
//Configure the number change principle to allow the system to prefix number change indexes
2, 6, and 8 with 222, 666, and 888, respectively.
ADD DNC: DCX=2, DCT=INS, DCP=0, ND=K'222;

//Configure the indirect subroute for sub-routes C, E, and F as S. Callee sending change
index of sub-routes C, E, and F references Number change index defined by ADD DNC. Select
Charge with number changed to enable the system to display the number after change in the
CDR.
ADD SRT: O=0, SRN="S", RENT=URT;
MOD SRT: O=1, SRN="C", RENT=URT, ISNAME="S", EI=2, CNC=CLD-1;
MOD SRT: O=1, SRN="E", RENT=URT, ISNAME="S", EI=6, CNC=CLD-1;
MOD SRT: O=1, SRN="F", RENT=URT, ISNAME="S", EI=8, CNC=CLD-1;
Related tasks
None.
Related concepts
l Uniform routing policy: The same routing selection policy is configured on several
softswitches or switches. This configuration can enable the system to select the subroutes
that are to the same destination but belong to different switches based on the same policy.
l Super trunk: It is a trunk group that connects two switches. It is used for transferring a call
traffic when the uniform routing policy is used.
l Indirect subroute: During a subroute selection procedure, the indirect subroute is used to
correlate an ordinary subroute with the super trunk. That is, the super trunk is configured
in the indirect subroute. When an ordinary subroute is selected, the system routes out a call
through the super trunk in the indirect subroute that is configured for the ordinary subroute.
At this time, the ordinary subroute is used as a virtual subroute.
11.4 Trunk Configuration Examples
11.4.1 Configuring Single PCM Port to Bear Multiple Trunk Groups (Same Office Direction)
11.4.2 Configuring Single PCM Port to Bear Multiple Trunk Groups (Multiple Office
Directions)
11.4.3 Configuring Multiple SIP Trunks Between Two IP Addresses
11.4.4 Configuring Trunk-Specified Dialing Test Data
11.4.1 Configuring Single PCM Port to Bear Multiple Trunk Groups

(Same Office Direction)
Introduction
If only a few E1 trunk circuits are set up between two switches, you need to set the trunk circuits
of the same office direction to outgoing and incoming trunk groups based on the timeslots. For
a single PCM port, configure certain timeslots as outgoing trunk groups and other timeslots as
incoming trunk groups.

Example 1 (ISUP Trunk)

Introduction
Assume that two E1 trunk circuits are enabled between the SoftX3000 of the local office and a
PSTN switch, and ISUP signaling is used between the two offices. See Figure 11-17 for the
system networking.
Figure 11-17 Typical networking when a single PCM port bears multiple trunk groups (same
office direction)
SoftX3000 Time slots 0 to 15 of 0#PCM port are

outgoing trunks
UMG8900
Time slots 16 to 31 of 0#PCM port
IP are incoming trunks
PSTN
MAN switch
are outgoing trunks
are incoming trunks
AMG
requirements:
l Configure time slots 0 to 15 of the physical port of the 0#PCM of the UMG8900 and those
of the 1#PCM as outgoing trunks.
of the 1#PCM as incoming trunks.
Scripts
RP=2944, LISTOFCODEC=PCMA-1&PCMU-1&G7231-1&G729-1&t38-1, HAIRPIN=S,
CODETYPE=ASN;
//Add an MTP DSP. Set DSP index to 201, representing a PSTN switch.
ADD N7DSP: DPX=201, DPC="110033", DPNAME="E_office";
//Add an office direction destined for the PSTN switch. Set Office direction number to 201
and Destination point code 1 to 110033.
ADD OFC: O=201, ON="E_office", DOT=CMPX, DOL=LOW, DPC1="110033";
//Add a subroute numbered 201.


ADD RT: R=201, RN="To E_office", SR1=201;
//Add analysis data of the route destined for the PSTN switch. Set Route selection code to
201.
//Add an SS7 trunk group. Trunk group 201 is an outgoing trunk group. Trunk group 202 is an
incoming trunk group.
SOPC="001122", TGN="To E_office", OTCS=99, PRTFLG=CN, NOAA=FALSE,
SOPC="001122", TGN="To E_office", RCHS=88, OTCS=255, PRTFLG=CN,
NOTE
l For outgoing trunk groups, Charging source code is set to 255 and Outgoing trunk charging source
code cannot be set to 255 (it is set to 99 in the given example).
l For incoming trunk groups, Charging source code cannot be set to 255 (it is set to 88 in the given
example), and Outgoing trunk charging source code is set to 255.
//Add SS7 trunk circuits. The physical port is the port of 0# PCM. Circuits No. 64 to No. 79 are
outgoing trunk circuits. Set Start CIC to 0, Start circuit termination ID to 0, and Trunk group
number to 201 for circuits No. 64 to No. 79. Circuits No. 112 to No. 127 are incoming trunk
circuits. Set start CIC to 16, Start circuit termination ID to 16, and Trunk group number
to 202 for circuits No. 112 to No. 127.
//Add SS7 trunk circuits. The physical port is the port of 1# PCM. Circuits No. 128 to No. 143
are outgoing trunk circuits. Set Start CIC to 32, Start circuit termination ID to 32, and Trunk
group number to 201 for circuits No. 128 to No. 143. Circuits No. 176 to No. 191 are incoming
trunk circuits. Set start CIC to 48, Start circuit termination ID to 48, and Trunk group
number to 202 for circuits No. 176 to No. 191.

NOTE
l When an SS7 trunk circuit is added, the system allocates the circuit number resources in the FCCU
module based on E1 by default. Regardless of the values of the start and end circuit numbers, the circuit
number resources from [n x 32] to [m x 32 - 1] are used. N = INT (Start circuit number / 32), and m =
INT (End circuit number / 32) + 1. If you have configured the data of n trunk groups for a PCM physical
port, the circuit number resources of n logical PCM ports on the SoftX3000 are used. A part of the
circuit number resources is wasted.
l Start CIC is a parameter used for interworking between the SoftX3000 and the PSTN switch. Start
circuit termination ID is a parameter used for interworking between the SoftX3000 and the
UMG8900. Set the two parameters based on the actual conditions. The absolute value of the difference
between the start circuit number and the start circuit termination ID must be an integral multiple of 32,
for example, 0, 32, 64, and 96.
l According to the preceding configuration principles, the key point for configuring a single PCM port
to bear multiple trunk groups is to define Start circuit number and End circuit number correctly. In
this example, the data of the two trunk groups is configured for the port of 0# PCM. The first 16 time
slots of the port of 0#PCM use the first 16 circuits (from No. 64 to No. 79) of the logical 2#PCM port
on the SoftX3000. The last 16 time slots of the port of 0#PCM use the last 16 circuits (from No. 112
to No. 127) of the logical 3#PCM port instead of the first 16 circuits (from No. 96 to No. 111) of the
logical 3#PCM port. Other cases can be deduced in the same manner.
Example 2 (R2 Trunk)

Introduction
PSTN switch, and R2 signaling is used between the two offices. See Figure 11-17 for the system
networking.
requirements:
Scripts

RP=2944, LISTOFCODEC=PCMA-1&PCMU-1&G7231-1&G729-1&t38-1, HAIRPIN=S,
CODETYPE=ASN;
//Add an office direction destined for the PSTN switch. Set Office direction number to 201.
ADD OFC: O=201, ON="E_office", DOT=CMPX, DOL=LOW;


201.


//Add an R2 trunk group. Trunk group 201 is an outgoing trunk group. Trunk group 202 is an
incoming trunk group.
ADD N1TG: TG=201, EID="211.169.150.95:2944", G=OUT, SRC=201, SN="N1",
TGN="To E_office", RCHS=255, OTCS=99, ECATTR=NO, TIATTR=NO, ENATTR=NO;
ADD N1TG: TG=202, EID="211.169.150.95:2944", G=IN, SRC=201, SN="N1",
TGN="To E_office", RCHS=88, ECATTR=NO, TIATTR=NO, ENATTR=NO;
NOTE
l For outgoing trunk groups, Charging source code is set to 255 and Outgoing trunk charging source
code cannot be set to 255 (it is set to 99 in the given example).
l For incoming trunk groups, Charging source code cannot be set to 255 (it is set to 88 in the given
example), and Outgoing trunk charging source code is set to 255.
//Add R2 trunk circuits. The physical port is the port of 0# PCM. Circuits No. 64 to No. 79 are
outgoing trunk circuits. Set Start circuit termination ID to 0 and Trunk Group Number to
201 for circuits No. 64 to No. 79. Circuits No. 80 to No. 95 are incoming trunk circuits. Set
Start circuit termination ID to 16 and Trunk group number to 202 for circuits No. 80 to No.
95.
ADD N1TKC: MN=22, TG=201, SC=64, EC=79, TID=0;
//Add R2 trunk circuits. The physical port is the port of 1# PCM. Circuits No. 96 to No. 111 are
outgoing trunk circuits. Set Start circuit termination ID to 32 and Trunk Group Number to
201 for circuits No. 96 to No. 111. Circuits No. 112 to No. 127 are incoming trunk circuits. Set
Start circuit termination ID to 48 and Trunk group number to 202 for circuits No. 112 to
No. 127.
NOTE
When an R2 trunk circuit is added, the system allocates the circuit number resources in the FCCU module
based on time slots. Therefore, there is no special requirement for the preceding configuration.
Example 3 (PRA Trunk)

Introduction
PSTN switch, and DSS1 signaling is used between the two offices. See Figure 11-17 for the
system networking.
requirements:
Scripts

RP=2944, LISTOFCODEC=PCMA-1&PCMU-1&G7231-1&G729A-1&t38-1, HAIRPIN=S,

CODETYPE=ASN;
//Add an office direction destined for the PSTN switch. Set Office direction number to 201.
ADD OFC: O=201, ON="E_office", DOT=CMPX, DOL=LOW;


201.

//Add a PRA subscriber. Set Route selection code to 201 and ISDN index to 2.
ADD PRA: LP=0, D=K'8780000, ISDN=2, LOCM=TG, TRUNKGP=201, CSC=0, RCHS=22,
CUGU=NO;
//Add PRA trunk groups. Trunk groups 201 and 203 are outgoing trunk groups that use PRA
link No. 10. Trunk groups 202 and 204 are incoming trunk groups that use PRA link No. 11.
ADD PRATG: TG=201, MGW="211.169.150.95:2944", SRC=201, LINK=10,
CDEF=K'8780000, TGN="To E_office", GD=OUT;
CDEF=K'8780000, TGN="To E_office", GD=IN;
CDEF=K'8780000, TGN="To E_office", GD=OUT;
CDEF=K'8780000, TGN="To E_office", GD=IN;
NOTE
l The difference between adding a PRA trunk group and adding an SS7 or R2 trunk group is as follows:
When you add a PRA trunk group, you must specify the link number of the PRA signaling link that
bears the DSS1 signaling messages of the PRA trunk group. Therefore, you cannot configure only two
PRA trunk groups. You must configure four PRA trunk groups in the given example.
l The outgoing PRA trunk group and incoming PRA trunk group that are borne by a PCM physical port
must use the same PRA signaling link. In addition, the time slot used by the PRA signaling link must
be within the PCM physical port.
//Add PRA trunk circuits. The physical port is the port of 0# PCM. Circuits No. 64 to No. 79
are outgoing trunk circuits. Set Start circuit termination ID to 0 and Trunk Group
Number to 201 for circuits No. 64 to No. 79. Circuits No. 80 to No. 95 are incoming trunk
circuits. Set Start circuit termination ID to 16 and Trunk group number to 202 for circuits
No. 80 to No. 95.
//Add PRA trunk circuits. The physical port is the port of 1# PCM. Circuits No. 96 to No. 111
are outgoing trunk circuits. Set Start circuit termination ID to 32 and Trunk Group
Number to 203 for circuits No. 96 to No. 111. Circuits No. 112 to No. 127 are incoming trunk

circuits. Set Start circuit termination ID to 48 and Trunk group number to 204 for circuits
No. 112 to No. 127.
NOTE
When adding a PRA trunk circuit, pay attention to the number of the PRA trunk group to which the trunk
circuit belongs.
Related tasks
None.
Related concepts
None.
11.4.2 Configuring Single PCM Port to Bear Multiple Trunk Groups

(Multiple Office Directions)
Introduction
When the SoftX3000 interworks with multiple switches, the SS7 trunk circuits between the
SoftX3000 and a switch may be fewer than the number of the timeslots on a single PCM port.
For example, only 15 trunk circuits are set up. In this case, the carrier may use cross-connect
equipment to combine the trunk circuits into a PCM port, and then interconnect the SoftX3000
through transmission links. This helps to save the inter-office PCM circuit resources. For a single
PCM port, set certain timeslots to trunk groups of one office direction and set the remaining
timeslots to trunk groups of another office direction.
Example
Introduction
Assume that the SoftX3000 in the local office interworks with switches A and B through an E1
trunk circuit. The ISUP signaling is used. See Figure 11-18 for the system networking.

Figure 11-18 Typical networking when configuring a single PCM port to bear multiple trunk
groups (multiple office directions)
SoftX 3000 Switch A

Time slots 0 to 15 of
Transmission 2# PCM port are used
UMG 8900 equipment
IP Cross - connection
MAN Transimission through equipment
a single PCM port
Time slots 16 to 31 of
2 # PCM port are used
AMG
Switch B
requirements:
l Sixteen trunk circuits are enabled between the SoftX3000 and switch A. The circuits use
time slots 0 to 15 of the physical port of 2#PCM of the UMG8900.
l Sixteen trunk circuits are enabled between the SoftX3000 and switch B. The circuits use
time slots 16 to 31 of the physical port of 2#PCM of the UMG8900.
NOTE
You can configure data of multiple trunk groups under multiple office directions for the PCM port only
when a single PCM port bears all the SS7 trunk groups.
Scripts

RP=2944, LISTOFCODEC=PCMA-1&PCMU-1&G7231-1&G729A-1&T38-1, HAIRPIN=S,
CODETYPE=ASN;
//Add two MTP DSPs. Set one DSP index to 202, representing switch A. Set the other DSP index
to 203, representing switch B.
ADD N7DSP: DPX=202, DPC="110055", DPNAME="F_office", STPF=FALSE,
ADJF=TRUE;
ADD N7DSP: DPX=203, DPC="110066", DPNAME="G_office", STPF=FALSE,
ADJF=TRUE;
//Add two office directions. Set one office direction number to 202, representing the office
direction from the local office to switch A. Set the other office direction number to 203, indicating
the office direction from the local office to switch B.

ADD OFC: O=202, ON="F_office", DOT=CMPX, DOL=LOW, DPC1="110055";

ADD OFC: O=203, ON="G_office", DOT=CMPX, DOL=LOW, DPC1="110066";
//Add two subroutes numbered 202 and 203 respectively.

ADD SRT: SRC=202, O=202, SRN="To F_office", RENT=URT;
ADD SRT: SRC=203, O=203, SRN="To G_office", RENT=URT;

ADD RT: R=202, RN="To F_office", SR1=202;
ADD RT: R=203, RN="To G_office", SR1=203;
//Add analysis data of the routes destined for PSTN switches. Set Route selection code to 202
and 203 respectively.
//Add SS7 trunk groups. Trunk group 202 is a bi-directional trunk from the local office to switch
A. Trunk group 202 belongs to subroute 202. Trunk group 203 is a bi-directional trunk from the
local office to switch B. Trunk group 203 belongs to subroute 203.
ADD N7TG: TG=202, EID="211.169.150.95:2944", G=INOUT, SRC=202,
SOPC="001122", TGN="To F_office", RCHS=88, OTCS=99, PRTFLG=CN,
ADD N7TG: TG=203, EID="211.169.150.95:2944", G=INOUT, SRC=203,
SOPC="001122", TGN="To G_office", RCHS=88, OTCS=99, PRTFLG=CN,
//Add SS7 trunk circuits. The physical port is the port of 2# PCM. Circuits No. 64 to No. 79
belong to trunk group 202. Set Start CIC to 0 and Start circuit termination ID to 64 for circuits
No. 64 to No. 79. Circuits No. 112 to No. 127 belong to trunk group 203. Set Start CIC to 0
and Start circuit termination ID to 80 for circuits No. 112 to No. 127.
NOTE
l By default, the system allocates the circuit number resources in the FCCU module based on E1.
Regardless of the values of the start and end circuit numbers, the circuit number resources from [n x
32] to [m x 32 - 1] are used. N = INT (Start circuit number / 32), and m = INT (End circuit number /
32) + 1. If you have configured the data of n trunk groups for a PCM physical port, the circuit number
resources of n logical PCM ports on the SoftX3000 are used. A part of the circuit number resources is
wasted.
l Start CIC is a parameter used for interworking between the SoftX3000 and the PSTN switch. Start
circuit termination ID is a parameter used for interworking between the SoftX3000 and the
UMG8900. Set the two parameters based on the actual conditions. The absolute value of the difference
between the start circuit number and the start circuit termination ID must be an integral multiple of 32,
for example, 0, 32, 64, and 96.
l According to the preceding configuration principles, the key point for configuring a single PCM port
to bear multiple trunk groups is to define Start circuit number and End circuit number correctly. In
this example, the data of two trunk groups is configured for the port of 2#PCM. The first 16 time slots
of the port of 2#PCM use the first 16 circuits (from No. 64 to No. 79) of the logical 2#PCM port on
the SoftX3000. The last 16 time slots of the port of 2#PCM use the last 16 circuits (from No. 112 to
No. 127) of the logical 3#PCM port instead of the first 16 circuits (from No. 96 to No. 111) of the
logical 3#PCM port.

Related tasks
None.
Related concepts
None.
11.4.3 Configuring Multiple SIP Trunks Between Two IP Addresses
Example
Introduction
CAUTION
This configuration has great impacts on system performance. Therefore, do not make this
configuration unless required.
Figure 11-19 shows a typical network on which SoftX3000 A and SoftX3000 B interconnect
with SoftX3000 C in load-balancing and dual-homing modes. SoftX3000 A and SoftX3000 B
are configured with only one IFMI board each. This task enables the carrier to configure multiple
SIP trunks between two IP addresses without adding IFMI boards. In other words, this task
enables the carrier to implement the following operations:
l Setting up multiple SIP trunks between SoftX3000 A and SoftX3000 C.
l Setting up multiple SIP trunks between SoftX3000 B and SoftX3000 C.
Figure 11-19 Network on which multiple SIP trunks are configured between two IP addresses
SoftX3000 C
Heartbeat
SoftX3000 A SoftX3000 B
To implement this task, you need to configure the SoftX3000 against the following requirements:

NE Name IP Address Trunk Group Port Number

Name
SoftX3000 A 191.169.150.30 AC-TG- 5060

MASTER
BC-TG- 5061
SLAVE
SoftX3000 B 191.169.150.40 BC-TG- 5061

MASTER
AC-TG- 5060
SLAVE
SoftX3000 C 211.169.150.50 CA-TG-A 5060
CB-TG-A 5061
CA-TG-B 5060
CB-TG-B 5061
Scripts
//Change the setting of public parameter 63 so that the maximum number of ports that a SIP
trunk group can serve is no less than the number of trunk groups required to be configured for
one IP address.
NOTE
Make this configuration on SoftX3000 A, SoftX3000 B, and SoftX3000 C.
MOD PUBPRM: ID=P63, VAL=2;
//Configure the local ports and server ports. Set ports 5062 to 5188 as local ports. Set ports 5060
to 5061 as server ports.
NOTE
SET SIPCFG: UST=SessionTimer, MNP=5062, MXP=5188, MNSVP=5060, MXSVP=5061;
//Configure the local port number. Set the MSG module number to 136 and the local port number
to 5062.
NOTE
//Add office directions. Add an office direction from SoftX3000 A to SoftX3000 C and set the
number of this office direction to 1. Add an office direction from SoftX3000 B to SoftX3000 C
and set the number of this office direction to 128.
ADD OFC: O=1, ON="AC-SIP-MASTER", DOT=CMPX, DOL=SAME;
ADD OFC: O=128, ON="BC-SIP-SLAVE", DOT=CMPX, DOL=SAME;
//Add two sub-routes. Add a subroute from SoftX3000 A to SoftX3000 C and set the number
of this subroute to 1. Add a subroute from SoftX3000 B to SoftX3000 C and set the number of
this subroute to 128.

ADD SRT: SRC=1, O=1, SRN="AC-SIP-MASTER", RENT=URT;

ADD SRT: SRC=128, O=128, SRN="BC-SIP-SLAVE", RENT=URT;
//Add two routes. Add a route from SoftX3000 A to SoftX3000 C and set the number of this
route to 1. Add a route from SoftX3000 B to SoftX3000 C and set the number of this route to
128.
ADD RT: R=1, RN="AC-SIP-MASTER", IDTP=UNKNOWN, NAMECFG=NO, SNCM=SRT,
ADD RT: R=128, RN="BC-SIP-SLAVE", IDTP=UNKNOWN, NAMECFG=NO, SNCM=SRT,
//Add two route analysis records. Add a route analysis record for the route from SoftX3000 A
to SoftX3000 C. In this record, the route selection source code is set to 0 and the route selection
code is set to 1. Add another route analysis record for the route from SoftX3000 B to SoftX3000
C. In this record, the route selection code is set to 10 and the route selection code is set to 128.
ADD RTANA: RAN="AC-SIP-MASTER", RSC=1, RSSC=0, TM=TMM, R=1;
ADD RTANA: RAN="BC-SIP-SLAVE", RSC=128, RSSC=10, TM=TMM, R=128;
//Add SIP trunks. Set Software parameter of signalling control to Support Multi-SIP-trunk
between two IP. In the record for the trunk from SoftX3000 A to SoftX3000 C, the trunk group
number is set to 1 and the call source code is set to 0. In the record for the trunk from SoftX3000
B to SoftX3000 C, the trunk group number is set to 128 and the call source code is set to 10.
ADD SIPTG: TG=1, CSC=0, SRT=1, TGN="AC-SIP-MASTER", RCHS=0, OTCS=0,
HCIC=100, LCIC=100, ST=NGNN, NOAA=NO, EA=YES,
ICR=LCO-1&LC-1&LCT-1&NTT-1&ITT-1&INTT-1&IITT-1&IOLT-1,
OCR=LCO-1LC-1LCT-1&NTT-1&ITT-1&INTT-1&IITT-1&IOLT-1, UHB=NO,
SGCTRL=SVR10-1, VIDEOS=SUPPORT, CHBF=NO, E2833F=NSUPPORT, SELMODE=DIST;
ADD SIPTG: TG=2, CSC=0, SRT=2, TGN="BC-SIP-SLAVE", RCHS=0, OTCS=0,
HCIC=100, LCIC=100, ST=NGNN, NOAA=NO, EA=YES,
ICR=LCO-1LCT-1&NTT-1&ITT-1&INTT-1&IITT-1&IOLT-1,
OCR=LCO-1LCT-1&NTT-1&ITT-1&INTT-1&IITT-1&IOLT-1, UHB=NO, SGCTRL=SVR10-1,
VIDEOS=SUPPORT, CHBF=NO, E2833F=NSUPPORT, SELMODE=DIST;
//Add SIP trunk group IP pair data. Set the IFMI module number to 132 and the local server port
to port 5060 and port 5062 respectively. The number of the trunk group from SoftX3000 A to
SoftX3000 C is 1. The number of the trunk group from SoftX3000 B to SoftX3000 C is 128.
DH=No;
DH=No;
Make the following configurations on SoftX3000 C.

//Add office directions. Add an office direction from SoftX3000 C to SoftX3000 A and set the
number of this office direction to 1. Add an office direction from SoftX3000 C to SoftX3000 B
and set the number of this office direction to 3.
ADD OFC: O=1, ON="CA-SIP", DOT=CMPX, DOL=SAME;
ADD OFC: O=3, ON="CB-SIP", DOT=CMPX, DOL=SAME;
//Add sub-routes. Add a subroute from SoftX3000 C to SoftX3000 A and set the number of this
subroute to 1. Add a secondary subroute from SoftX3000 C to SoftX3000 B and set the number
of this secondary subroute to 2. Add a subroute from SoftX3000 C to SoftX3000 B and set the
number of this subroute to 3. Add a secondary subroute from SoftX3000 C to SoftX3000 A and
set the number of this secondary subroute to 4.
ADD SRT: SRC=1, O=1, SRN="CA-SIP-A", RENT=URT;
ADD SRT: SRC=2, O=2, SRN="CB-SIP-A", RENT=URT;

ADD SRT: SRC=3, O=3, SRN="CB-SIP-B", RENT=URT;

ADD SRT: SRC=4, O=4, SRN="CA-SIP-B", RENT=URT;
//Add routes. Add a route from SoftX3000 C to SoftX3000 A and set the number of this route
to 1. Set the first subroute of route 1 to subroute 1 and the second subroute to subroute 2. Add
a route from SoftX3000 C to SoftX3000 B and set the number of this route to 3. Set the first
subroute of route 3 to subroute 3 and the second subroute to subroute 4.
ADD RT: R=1, RN="CA-SIP", IDTP=UNKNOWN, NAMECFG=NO, SNCM=SRT, SRST=SEQ,
SR1=1, SR2=2, STTP=INVALID, REM=NO;
ADD RT: R=3, RN="CB-SIP", IDTP=UNKNOWN, NAMECFG=NO, SNCM=SRT, SRST=SEQ,
SR1=3, SR2=4, STTP=INVALID, REM=NO;
//Add route analysis data. Add a route analysis record for the route from SoftX3000 C to
SoftX3000 A. In this record, the route selection source code is set to 0 and route selection code
is set to 1. Add another route analysis record for the route from SoftX3000 C to SoftX3000 B.
In this record, the route selection code is set to 0 and route selection code is set to 3.
ADD RTANA: RAN="CA-SIP", RSC=1, RSSC=0, TM=TMM, R=128;
ADD RTANA: RAN="CB-SIP", RSC=3, RSSC=0, TM=TMM, R=1;
//Add SIP trunks from SoftX3000 C to SoftX3000 A and SoftX3000 B. Set Software parameter
of signalling control to Support Multi-SIP-trunk between two IP. In the data about the SIP
trunks from SoftX3000 C to SoftX3000 A, the primary trunk group is set to trunk group 1, the
secondary trunk group to trunk group 4, and the call source code of both trunk groups to 0. In
the data about the SIP trunk from SoftX3000 C to SoftX3000 B, the primary trunk group is set
to trunk group 3, the secondary trunk group to trunk group 2, and the call source code to 0.
ADD SIPTG: TG=1, CSC=0, SRT=1, TGN="CA-SIP-A", RCHS=0, OTCS=0, HCIC=100,
LCIC=100, ST=NGNN, NOAA=NO, EA=YES,
OCR=LCO-1LCT-1&NTT-1&ITT-1&INTT-1&IITT-1&IOLT-1,, UHB=NO,
ADD SIPTG: TG=2, CSC=0, SRT=2, TGN="CB-SIP-A", RCHS=0, OTCS=0, HCIC=100,
OCR=LCO-1LCT-1&NTT-1&ITT-1&INTT-1&IITT-1&IOLT-1,, UHB=NO,
ADD SIPTG: TG=3, CSC=0, SRT=3, TGN="CB-SIP-B", RCHS=0, OTCS=0, HCIC=100,
ADD SIPTG: TG=4, CSC=0, SRT=4, TGN="CA-SIP-B", RCHS=0, OTCS=0, HCIC=100,
ICR=LCO-1LCT-1&NTT-1&ITT-1&INTT-1&IITT-1&IOLT-1,,
//Add SIP trunk group IP pair data. Set the IFMI module number to 132 and local server port to
5060 and 5061 respectively. Add IP pair records for trunk group 1 (primary SIP trunk group
from SoftX3000 C to SoftX3000 A), trunk group 2 (secondary SIP trunk group from SoftX3000
C to SoftX3000 B), trunk group 3 (primary SIP trunk group from SoftX3000 C to SoftX3000
B), and trunk group 4 (secondary SIP trunk group from SoftX3000 C to SoftX3000 A).
MSTYPE=MASTER, DH=No;


Related Tasks
None.
Related Concepts
None.
11.4.4 Configuring Trunk-Specified Dialing Test Data

Introduction
The trunk dialing test refers to the dialing test performed on the trunk circuits or trunk groups
by using the phones or running MML commands on the LMT. During the trunk dialing test, you
need not block trunk circuits. The trunk-specified dialing test is a common test method used in
deployment and maintenance. The main implementation modes are as follows:
1. Trunk-specified dialing test through phones (also called dedicated line calling)
Test Type Operations Description
Trunk circuit dial test Dial *66*module It is used to test whether the
number*0*circuit specified trunk circuit is
number*callee number# available.
on a phone. The number 0 The caller must be
dialed represents the trunk configured as the operator
circuit dialing test. or test subscriber and must
not be a Centrex subscriber;
otherwise, the caller does
not have the rights to make
a trunk test call.
Trunk group dial test Dial *67*trunk group It is used to test whether the
number*callee number# specified office direction is
or *67*trunk group available.
number*callee The caller must be
number*transmission configured as the operator
capability# on a phone. or test subscriber and the
test subscriber cannot be a
Centrex subscriber;
otherwise, the caller does
not have the rights to make
a trunk test call.

Trunk CIC dial test Dial *68*trunk group l It is used to test whether
number*CIC*callee the specified ISUP or
number# on a phone. TUP trunk is available.
l It is applicable to POTS
and SIP terminals.
l Before performing the
dialing test, you need to
run ADD CNACLD
with Call prefix set to
*68* (configurable),
Service category set to
NEW(Supplementary
service), and Service
attribute set to Special
trunk CIC line call.
l The dialing test is
applicable to callers of
any subscriber type
(defined by Subscriber
type in ADD VSBR).
NOTE
l The trunk group number, circuit number, and CIC number must contain five digits, and the
module number must contain three digits. If the number length is not five digits or three digits,
the number is left-padded with zeros.
l The transmission capability can be 01 (voice), 02 (unrestricted digital service), 04 (restricted
digital service), and 08 (3.1 kHz audio service).
l The terminal-triggered dialing tests are applicable to different types of trunks. The details are as
follows:
l Trunk circuit dial test: ISUP, TUP, PRA, R2, and No5 trunks
l Trunk group dial test: ISUP, TUP, PRA, R2, No5, SIP, and H.323 trunks
l Trunk CIC dial test: ISUP and TUP turnks
2. Trunk-specified dialing test through MML commands (applicable to the office that has a
large number of trunks) You can perform a function test or a call test by setting the
parameters of STR SPLC.

Trunk circuit dial test Specify the parameters If the circuit to be tested is
such as Local DN set of the already occupied, the
caller, Caller number, dialing test fails. To avoid
Local DN set of the this problem, before
callee, Callee number, performing a trunk-
Module number of the specified dialing test, run
called trunk circuit, and MOD N7TKC to change
Circuit number of the the value of Circuit state to
called trunk, and then run Reserved for the circuit to
the command to perform a be tested. Thus, when you
function test. perform a dialing test on the
circuit, outgoing calls and
incoming calls cannot seize
this circuit. After the
dialing test is completed,
change the value of Circuit
state to Available for the
circuit.
Trunk group dial test Specify the parameters -

such as Local DN set of the
caller, Caller number,
Local DN set of the
callee, Callee number, and
Called TrunkGroup
number, and then run the
command to perform a call
test.
Trunk CIC dial test Specify the parameters -

such as Local DN set of the
caller, Caller number,
Local DN set of the
callee, Callee number,
Called TrunkGroup
number, and Called trunk
CIC, and then run the
command to perform call
tests on the ISUP and TUP
trunks.

NOTE
l Before performing dialing tests by using this command, you need to configure a virtual PBX subscriber.
l Set Start equipment number and End equipment number to idle equipment numbers. To check
whether the specified equipment numbers are idle, run LST VPSN.
l To delete the virtual PBX subscriber, run RMV VSBRor RVB VSBR with the corresponding
module number or equipment number specified.
l Rules for querying a virtual PBX group are as follows:
l The system first selects a virtual PBX group with the local DN set to the value of Local DN
set of the callee in the called trunk circuit module.
l If the preceding selection fails, the system selects a virtual PBX group configured in the called
trunk circuit module.
l If the preceding selections fail, the system selects a virtual PBX group configured in the local
DN set of the callee.
l If the query fails, the system prompts that no virtual PBX subscriber is configured, and you
cannot run the command.
l The caller can be a local subscriber or a subscriber from another office that interworks with the local
office through trunks. The callee must be served by another office.
l The command-triggered dialing tests are applicable to different types of trunks. The details are as
follows:
l Trunk circuit dial test: ISUP, TUP, PRA, R2, and No5 trunks
l Trunk group dial test: ISUP, TUP, R2, and No5 trunks
l Trunk CIC dial test: ISUP and TUP turnks
Example 1 (Trunk Circuit Dialing Test on Calls in Which the Caller Resides in the
Local Office)
Requirements
The caller with the phone number 26540808 resides in the local office. Subscriber A resides in
another office that interworks with the local office through ISUP circuits. The ISUP outgoing
prefix is 020. The phone number of A is 12340001, the trunk module number of A is 22, and
the trunk circuit number of A is 20.
Scripts
1. MML mode
//Configure a virtual PBX pilot number.
ADD PBX: GDN=K'999000, LP=0, VF=YES;
//Configure a virtual PBX subscriber.
//Configure the trunk-specified dialing test.
STR SPLC: TTYPE=TKC, CRLP=0, CRD=K'26540808, CELP=0,
CED=K'02012340001, CEMN=22, CETKC=20;

NOTE
l Before running STR SPLC, ensure that the trunk-specified call prefix is already configured. By
default, the prefix is *66*. In special cases, you can configure different trunk-specified call
prefixes for different local DN sets. The length of a prefix must be less than 12 characters.
l Caller number and Callee number consist of 0-E (BCD code). Callee number cannot be a
number configured in the local office. If Module number of the calling trunk circuit and
Circuit number of the calling trunk are specified, Caller number cannot be a number
configured in the local office either.
l You are required to specify both Module number of the calling trunk circuit and Circuit
number of the calling trunk, or specify none of the two parameters. You cannot specify only
one of the two parameters.
l If Module number of the calling trunk circuit and Circuit number of the calling trunk are
not specified, the callee number in the call made to the caller side is Caller number specified in
STR SPLC. The outgoing circuit is determined by the CDB routing.
2. Subscriber dialing mode
//Add the caller as the test subscriber.
ADD VSBR: D=K'26540808, LP=0, MN=22, DID=ESL, EID="iad1.com",
ID="10", RCHS=0, CSC=0, UTP=TEST, CNTRX=NO, PBX=NO, CHG=NO, ENH=NO;
//The caller initiates the dialing test with the trunk group and CIC specified through the
phone.
*66*022*0*00020*02012340001#
Example 2 (Trunk Circuit Dialing Test on Calls in Which the Caller Resides in
Another Office)
Requirements
Subscribers A and B reside in an office that interworks with the local office through TUP circuits.
The TUP outgoing prefix is 010. The phone number of A is 22220000, the trunk module number
of A is 22, and the trunk circuit number of A is 10. The phone number of B is 88880000, the
trunk module number of B is 23, and the trunk circuit number of B is 20.
Scripts
1. MML mode
STR SPLC: TTYPE=TKC, CRLP=0, CRD=K'01022220000, CRMN=22, CRTKC=10,
CELP=0, CED=K'01088880000, CEMN=23, CETKC=20;
NOTE
If Module number of the calling trunk circuit and Circuit number of the calling trunk are
specified, the callee number must be generated based on the number format of the trunk-specified
call when a call is made to the PBX subscriber. If the system, by default, sets the prefix of the trunk-
specified call to *66* (configurable), the actual callee number is *66*MMM*0*TTTTT*Caller
number specified in STR SPLC#.
ID="10", RCHS=0, CSC=0, UTP=TEST, CNTRX=NO, PBX=NO, CHG=NO, ENH=NO;

//The caller initiates the dialing test with the trunk group and CIC specified through the
phone.
*66*022*0*00020*01088880000#
Example 3 (Trunk-Group-Specified Dialing Test)

Requirements
When a carrier adds a trunk group (trunk group number: 10) in an end office, the carrier can use
the trunk dialing test service to test the functions of the new trunk group. Assume that in the end
office, the test number is 16051001. In the peer office, the test number is 16051000. The outgoing
prefix is 010. The carrier can use two methods to perform the trunk group dialing test and verify
the functions of the trunk group.
Scripts
1. MML mode
//Add a PBX group.
//Add a virtual PBX group. Set PBX pilot number to 8880001.
STR SPLC: TTYPE=TG, CRLP=0, CRD=K'16051001, CELP=0,
CED=K'01016051000, CETG=10, TP=VOICE;
TID="10", RCHS=0, CSC=0, UTP=TEST, CNTRX=NO, PBX=NO, CHG=NO, ENH=NO;
//The caller initiates the trunk group dialing test through the phone.
*67*00010*01016051000#
Example 4 (Trunk CIC dialing test)

Requirements
When a carrier adds a trunk group (trunk group number: 10; start CIC: 0) in an end office, the
quality of the calls over certain circuits of the trunk group are poor. In this case, the carrier can
use the trunk CIC dialing test service to identify the faulty circuits. Assume that in the end office,
the test number (the number of an operator) is 16051001. In the peer office, the test number (the
number of an ordinary subscriber) is 16051000. The outgoing prefix is 010. The carrier can use
two methods to perform the trunk CIC dialing test and verify the functions of the trunk group.
Scripts
1. MML mode
//Add a PBX group.
//Add a virtual PBX group. Set PBX pilot number to 8880001.
STR SPLC: TTYPE=TCIC, CRLP=0, CRD=K'16051001, CELP=0,
CED=K'01016051000, CETG=10, CECIC=0;

NOTE
The CIC of the called trunk (CECIC) ranges from 0 to 31. Test the circuit of the trunk group one by
one to identify the faulty circuits based on the call connection condition.
//Add prefix analysis data.
ADD CNACLD: LP=0, PFX=K'*68*, CSTP=NEW, CSA=SPTKCIC, MINL=2, MAXL=32,
CHSC=0, EA=NO;
//Add the caller as the operator.
TID="10", RCHS=0, CSC=0, UTP=OPR, CNTRX=NO, PBX=NO, CHG=NO, ENH=NO;
//The caller initiates the dialing test with the trunk group specified through the phone.
*68*00010*00000*01016051000#
Related Tasks
None.
Related Concepts
The following table describes the implementation mode of each trunk-specified dialing test.
Test Type Implementation
Trunk circuit In STR SPLC, specify parameters such as Caller number, Callee
dial test number, Module number of the called trunk circuit, and Circuit number
of the called trunk. Then, a virtual PBX subscriber makes two calls. The
format of the called number in the first call is *66*MMM*0*TTTTT*caller
number#. MMM represents the module number corresponding to the circuit
number of the calling trunk, and TTTTT represents the circuit number of the
calling trunk. If the module number and circuit number of the calling trunk
are not specified, the callee number of the first call is the caller number. The
format of the called number in the second call is
*66*MMM*0*TTTTT*callee number%. MMM represents the module
number corresponding to the circuit number of the called trunk, and TTTTT
represents the circuit number of the called trunk. After the call between the
caller and the callee is connected and the caller talks with the callee, it
indicates that the trunk-specified dialing test is successful.
Trunk group In STR SPLC, specify the parameters such as Caller number, Callee
dial test number, Called TrunkGroup number, and transfers ability. After
receiving the command, the SoftX3000 selects an idle virtual PBX
subscriber to originate a call to the caller. The caller hooks off and hears the
ringback tone. The SoftX3000 originates a call through a specified trunk.
The callee is alerted. After the callee hooks off, the caller talks with the
callee. It indicates that the trunk-specified dialing test is successful.

Test Type Implementation
Trunk CIC In STR SPLC, specify the parameters such as Caller number, Callee
dial test number, Called TrunkGroup number, and CIC of the called trunk. After
receiving the command, the SoftX3000 selects an idle virtual PBX
subscriber to originate a call to the caller. The caller hooks off and hears the
ringback tone. The SoftX3000 originates a call through a specified trunk
group and CIC. The callee is alerted. After the callee hooks off, the caller
talks with the callee. It indicates that the trunk CIC dial test is successful.
11.5 Configuration Example of Call Barring Data
11.5.1 Configuring Caller Number Discrimination Data

11.5.2 Configuring Inter-Group Call Barring Data
11.5.3 Configuring Black/White List Data
11.5.4 Configuring Called Number Barring Group Data
11.5.5 Configuring Time-based Call Barring Data
11.5.6 Configuring Nested Dialing Data
11.5.7 Configuring IGC Call Barring Data
11.5.8 Configuring Barring on a Certain Proportion of Calls Destined to a Specified Prefix over
the Designated Trunk
11.5.9 Configuring Call Congestion Barring Data
11.5.1 Configuring Caller Number Discrimination Data

Example 1 (Implementing Incoming Call Barring)
Introduction
The SoftX3000 acts as the gateway office on the fixed carrier side. The SoftX3000 interworks
with the gateway office on the mobile carrier side through SS7 trunks. The prefix of the mobile
subscriber numbers is 13X. Therefore, the SoftX3000 is required to reject the incoming calls
from the subscriber numbers with prefixes as 2-9 when the SoftX3000 transits the calls from the
mobile gateway office through the incoming trunk.
Scripts
//Add caller number discrimination groups. Set Discrimination group number to 10.
ADD CLRDSN: DSP=10, CLI=K'2, DAI=UDN, FUNC=NIN;

NOTE
The same discrimination group number can be configured with multiple caller numbers. That is, you can
use the same discrimination group number when you run ADD CLRDSN multiple times to add caller
number discrimination groups.
//Add trunk group discrimination groups from the local office to the mobile gateway office.
Trunk group 50 is an outgoing trunk group, trunk group 51 is an incoming trunk group, and
caller discrimination group numbers are 10.
ADD TGDSG: TG=50, DSG=10;
NOTE
To prevent the peer office from originating incoming calls through the outgoing trunk of the local office,
you are advised to define discrimination group numbers for both the incoming trunk and outgoing trunk
Example 2 (Implementing Caller Number Discrimination)

Introduction
The SoftX3000 acts as the gateway office on the fixed carrier side. The SoftX3000 interworks
with the gateway office on the mobile carrier side through SS7 trunks. The prefixes of the mobile
subscriber numbers are 13X and the number length is 11 digits. Therefore, the SoftX3000 is
required to set the number length limit to 11 for the mobile subscriber numbers when the
SoftX3000 transits the calls from the mobile gateway office through the incoming trunk.
Scripts
//Add a caller number discrimination group. Set Discrimination group number to 10.
ADD CLRDSN: DSP=10, CLI=K'13, DAI=UDN, FUNC=DSG, MIN=11, MAX=11;
//Add trunk group discrimination groups from the local office to the mobile gateway office.
Trunk group 50 is an outgoing trunk group, trunk group 51 is an incoming trunk group, and
caller discrimination group numbers are 10.
Example 3 (Changing Caller's Call Source Code)

Introduction
The SoftX3000 acts as the gateway office on the side of carrier A. The SoftX3000 interworks
with the gateway office on the side of carrier B through SS7 trunks. When the SoftX3000 transits
the calls from the peer gateway office through the incoming trunk, the callers who belong to
carrier B should be defined as different call sources. For example:
l For local fixed callers, assume that their numbers are 63XXXXX.
l For local mobile callers, assume that their numbers are 1330123XXXX.
Scripts
//Add call sources. Call source code 10 is used for the local fixed callers of carrier B, and 11 is
used for the local mobile callers of carrier B.
ADD CALLSRC: CSC=10, CSCNAME="For PSTN", PRDN=1, RSSC=10, FSC=10;
ADD CALLSRC: CSC=11, CSCNAME="For Mobile", PRDN=1, RSSC=20, FSC=20;

NOTE
In the preceding command, the call source codes 10 and 11 have different route selection source codes and
failure source codes. Based on these source codes, you can configure different route selection policies,
failure processing policies and call barring policies for the fixed callers and mobile callers of carrier B.
//Add caller number discrimination groups. Set Discrimination group number to 20.
ADD CLRDSN: DSP=20, CLI=K'63, DAI=UDN, FUNC=ATT, CSRC=10;
ADD CLRDSN: DSP=20, CLI=K'1330123, DAI=UDN, FUNC=ATT, CSRC=11;
//Add trunk group discrimination groups from the local office to the peer gateway office. Trunk
group 60 is an outgoing trunk group, trunk group 61 is an incoming trunk group, and caller
discrimination group numbers are 20.
NOTE
To prevent the peer office from originating incoming calls through the outgoing trunk of the local office,
you are advised to define discrimination group numbers for both the incoming trunk and outgoing trunk
Example 4 (Changing Caller's Charging Source Code)

Introduction
The SoftX3000 acts as the toll office and its toll calls to the lower-level end offices are charged
in the local office. The carrier requires that the toll calls made by local subscribers with numbers
36331XX not be charged.
Scripts
//Add charging cases. Charging case 160 is used for the normal charging of incoming trunks,
and charging case 161 is used for the charging (free) of local subscribers whose numbers are
36331XX.
ADD CHGANA: CHA=160, CHO=CENACC, CRM=TNSO;
ADD CHGANA: CHA=161, CHO=CENACC, PAY=FREE, CRM=TNSO;

TS3=21&00, TA3="6", PA3=1, TB3="6", PB3=1, AGIO3=100;
TS3=21&00, TA3="6", PA3=1, TB3="6", PB3=1, AGIO3=100;
PB1=1, AGIO1=60, TS2=00&00;
PB1=0, AGIO1=100, TS2=00&00;
PB1=0, AGIO1=100, TS2=00&00;
PB1=0, AGIO1=100, TS2=00&00;
//Add destination code charging. Caller charging source code 60 is used for the normal charging
of incoming trunk groups of lower-level offices; caller charging source code 61 is used for the
charging (free) of local subscribers whose numbers are 36331XX.

//Add a caller number discrimination group numbered 30. The caller number is 36331 and
charging source code is 61.
ADD CLRDSN: DSP=30, CLI=K'36331, DAI=UDN, FUNC=ATT, CHG=61;
//Add a trunk group discrimination group. The trunk group number is 31, (the charging source
code is 60 by default), and the discrimination group number is 30.
NOTE
After the preceding commands are executed, the default charging source code of the SS7 trunk group (group
number 31) is 60. If callers are in the number 36331XX, their charging source code is changed to 61 after
the system performs caller number discrimination analysis.
Example 5 (Changing Caller's Call Barring Group Number)

Introduction
The SoftX3000 acts as the gateway office on the side of carrier A. The SoftX3000 interworks
with the gateway office on the side of carrier B through SS7 trunks. When the SoftX3000 transits
the calls from the peer gateway office through the incoming trunk, it is required to define the
subscribers in the following ways:
l Define the callers in number segment 63XXXXX into the normal call barring group.
l Define the subscribers in numbers 63011XX, 63012XX and 63013XX as subscribers in
the white list.
Scripts
//Modify attributes of an incoming trunk group (take an SS7 trunk group for example). Set Call
barring group number to 65534 (ordinary call barring group).
MOD N7TG: TG=61, SOPC="001122", NOAA=FALSE, ISM=FALSE, EA=TURE,
LMTGRP=65534;
NOTE
After the preceding command is executed, 65534 is the default call barring group number of the callers
who make calls through incoming trunk group 61. That is, the callers are in the normal call barring group.
//Add caller number discrimination group numbered 40. Set Call barring group number to
60002 (white list).
ADD CLRDSN: DSP=40, CLI=K'63011, DAI=UDN, FUNC=ATT, GRP=60002;
Related tasks
None.
Related concepts
Call Barring Analysis Data

11.5.2 Configuring Inter-Group Call Barring Data
Example 1 (Implementing Call Barring in the Local Office)

Introduction
The SoftX3000 acts as an end office. The subscribers in the number 53210XX are special
subscribers and others are ordinary subscribers. This example requires that the call barring group
number of the special subscribers be set to 101, and that of the ordinary subscribers be set to
65534. Table 11-9 shows the inter-group barring relationship.
Table 11-9 Inter-group barring relationship
Caller Barring Group Called Barring Group Call Indication

Number Number
101 101 Call allowed
65534 101 Barring call
Scripts
//Set inter-group call barring indication data.

SET GRPAC: SRG=101, DRG=101, CI=CENA;
NOTE
Configure the data according to the inter-group barring relationship as shown in Table 11-9.
//Modify attributes of subscribers, that is, set different call barring group numbers for subscribers
according to the requirements.
MOB VSBR: SD=K'5320000, ED=K'5329999, LP=0, CNTRX=NO, PBX=NO, CHG=NO,
ENH=YES, LMTGRP=65534;
MOB VSBR: SD=K'5321000, ED=K'5321099, LP=0, CNTRX=NO, PBX=NO, CHG=NO,
ENH=YES, LMTGRP=101;
Example 2 (Implementing Call Barring in the Gateway Office)

Introduction
The SoftX3000 acts as a gateway office. Figure 11-20 shows the networking model of the
SoftX3000 that interworks with exchanges of the same local carrier and gateway offices of other
carriers.

Figure 11-20 Networking model when the SoftX3000 acts as a gateway office
Gateway office Gateway office Gateway office
of carrier A of carrier B of carrier C
Trunk group
Trunk group 20 Trunk group
10 30
SoftX3000
Gatrway office
Trunk group Trunk group
50 60
Toll office of Tandem office
local carrier of local carrier
Normally, the local office can transfer the incoming calls from the gateway offices of other
carriers to the toll office or the tandem office of the local carrier instead of the gateway offices
of other carriers. Otherwise, it may hinder the inter-network charging. In this example, you must
configure call barring data on the SoftX3000 side to prohibit call transfer among trunk groups
10, 20, and 30.
Scripts
//Set inter-group call barring indication data. Call barring group number 10 is used for the trunk
groups between the local office and the gateway office of carrier A.
groups between the local office and the gateway office of carrier B.
groups between the local office and the gateway office of carrier C.
groups between the local office and the toll office of the local carrier.

groups between the local office and the tandem office of the local carrier.
//Modify attributes of trunk groups. (Assume that all the groups are SS7 trunk groups). That is,
define the call barring group numbers of trunk groups according to the plan of inter-group call
barring.
MOD N7TG: TG=10, SOPC="001122", NOAA=FALSE, ISM=FALSE, EA=TRUE,
LMTGRP=10;
LMTGRP=10;
LMTGRP=20;
LMTGRP=20;
LMTGRP=30;
LMTGRP=30;
LMTGRP=50;
LMTGRP=50;
LMTGRP=60;
LMTGRP=60;
NOTE
l Define call barring group numbers for both the incoming trunk groups and the outgoing trunk groups
in the same sub-route. Otherwise, the inter-trunk-group call barring cannot be implemented.
l In this example, trunk group 10 is an outgoing trunk group, and trunk group 11 is an incoming trunk
group. Other trunk groups follow this principle.
Related tasks
None.
Related concepts
11.5.3 Configuring Black/White List Data

Example
Introduction
The black/white list represents a special inter-group call barring relationship. The system has
set the call barring group numbers 60001 for the black list and 60002 for the white list during
initialization. In addition, the system has set an ordinary call barring group numbered 65534
(wildcard).

The SoftX3000 acts as an end office in the army network. The local subscribers are divided into
category-A, category-B and category-C subscribers. This example implements call barring
among subscribers based on the black and white lists:
l Category-A subscribers can call all the subscribers.
l Category-B subscribers can call category-A and category-B subscribers but cannot call
category-C subscribers.
l Category-C subscribers can only call category-A subscribers.
Table 11-10 shows the inter-group call barring relationship.
Table 11-10 Inter-group barring relationship

Caller Barring Group Called Barring Group Call Indication
Category-A subscribers Category-A subscribers Call allowed
Category-A subscribers Category-B subscribers Call allowed
Category-A subscribers Category-C subscribers Call allowed
Category-B subscribers Category-A subscribers Call allowed
Category-B subscribers Category-B subscribers Call allowed
Category-B subscribers Category-C subscribers Barring call
Category-C subscribers Category-A subscribers Call allowed
Category-C subscribers Category-B subscribers Barring call
Category-C subscribers Category-C subscribers Barring call
As shown in Table 11-10, category-A subscribers adopt the white list (60002), category-B
subscribers adopts the ordinary call barring group (65534) and category-C subscribers adopt the
black list (60001).
Scripts
See 11.5.2 Configuring Inter-Group Call Barring Data.
Related tasks
None.
Related concepts
11.5.4 Configuring Called Number Barring Group Data

Example 1 (Implementing Call Barring by Black/White List)
Introduction

The SoftX3000 acts as an ordinary end office in the local network and occupies the number
368XXXX. The subscribers in the number segment 3685XXX are special subscribers and the
other subscribers are ordinary subscribers. Office S is an army network end office in the local
network and occupies the number 281XXXX. The subscribers in the number 2810XXX are the
category-A subscribers of office S and the other subscribers are category-B subscribers. This
example requires that the local ordinary subscribers be able to call only category-B subscribers
of office S instead of category-A subscribers in office S, and that the special subscribers in the
local office be able to call all subscribers (including category-A subscribers) in office S.
Scripts
//Add call prefix 281 from the local office to office S. Set Service attribute to Local.
ADD CNACLD: PFX=K'281, CSTP=BASE, CSA=LC, RSC=0, MINL=7, MAXL=7, CHSC=0,
EA=NO;
NOTE
By default, when you add a call prefix by running ADD CNACLD, the system defines the callees with the
call prefix as ordinary call barring group (65534) subscribers. In this example, the callees 281XXXX have
been defined as the ordinary call barring group subscribers.
//Add a called number barring group to define the called numbers 2810XXX (category-A
subscribers in office S) as the black list.
ADD CLDGRP: CLD=K'2810, GRPT=BG;
NOTE
After the preceding command is executed, for the call prefix 281, the callees except those in the number
segment 2810XXX are in the ordinary call barring group.
//Modify attributes of subscribers, that is, set different call barring group numbers for subscribers
according to the requirements.
MOB VSBR: SD=K'3685000, ED=K'3685299, LP=0, LMTGRP=60002;
MOB VSBR: SD=K'3680000, ED=K'3680299, LP=0, LMTGRP=65534;
NOTE
According to the call barring principle of the black and white lists, the call barring group number of the
special subscribers 3685XXX needs to be defined as 60002 (white list), and ordinary subscribers in the
local office defined into the ordinary call barring group (65534).
Example 2 (Implementing Call Barring by Inter-Group Barring Mode)

Introduction
The SoftX3000 acts as an end office. The subscribers in the number 532XXXX in the local office
are 201 card subscribers. The card numbers within this range are used to implement campus card
services in colleges belonging to the local office. To facilitate charging management, the carrier
needs to perform call barring for all 201 card numbers in the local office. That is, the 201 card
subscribers can dial only prefixes such as 200, 201, 300, 110, 119, 120 and 122.
Scripts
//Add called number barring groups to define call prefixes such as 200, 201, 300, 110, 119, 120
and 122 into ordinary call barring group 100.
ADD CLDGRP: CLD=K'200, GRPT=OG, GRP=100;


//Set inter-group call barring indication data. Source call barring group 201 is used for 201 card
subscribers.
NOTE
After the preceding commands are executed, the subscribers in the call barring group 201 can dial only
prefixes such as 200, 201, 300, 110, 119, 120 and 122.
//Modify attributes of subscribers. Set the call barring group number of 201 card subscribers to
201.
MOB VSBR: SD=K'5320000, ED=K'5320319, LP=0, ENH=YES, LMTGRP=201;
Related tasks
None.
Related concepts
11.5.5 Configuring Time-based Call Barring Data

Example
Introduction
To control the call charge, a Centrex group requires the carrier to perform a time-based call
barring policy for the intra-group ordinary subscribers.
Scripts
//Add date categories.
ADD DCAT: YEAR=2008, MON=JAN, DAY=1, DAT=DTYPE2;
NOTE
This example takes Year 2008 and defines the date category of holidays to be the same as that of Saturday
and Sunday.

ADD CXGRP: CGN="ABC", CXG=8, UCPC=100, WACF=NO, BIF=NO;

ADD CXSUBGRP: CXG=8, CXSG=5, CXSGN="ABC subgroup";
NOTE
l The call barring group number can be configured with multiple date categories. That is, you can use
the same call barring group number when you run ADD LCGRP multiple times to add time-based
call barring groups.
l By default, the date category of Friday is Category 1 instead of Normal Workday. Therefore, when
you run ADD LCGRP, note that Friday is not Normal Workday.
//Modify time-based call barring group data. Set Centrex group number to 8 and Call barring
group number to 10.
ADD LCGRP: CXG=8, LCG=10, DT=NORMAL, CT=COUT,
SCO=NTT-1&ITT-1&INTT-1&IITT-1, ST1="00&00", ED1="07&59", ST2="18&00",
ED2="23&59";
ADD LCGRP: CXG=8, LCG=10, DT=DTYPE1, CT=COUT,
SCO=NTT-1&ITT-1&INTT-1&IITT-1, ST1="00&00", ED1="07&59", ST2="18&00",
ED2="23&59";
ADD LCGRP: CXG=8, LCG=10, DT=DTYPE2, CT=COUT,
SCO=NTT-1&ITT-1&INTT-1&IITT-1, ST1="00&00", ED1="23&59";
//Add ESL subscribers (Centrex subscribers).

CNTRX=YES, CGF=YES, CXG=8, CXSG=5, SCXD=K'2001, COR=ITT-1&IITT-1,
CNTRX=YES, CGF=YES, CXG=8, CXSG=5, SCXD=K'2001, COR=ITT-1IITT-1, ENH=YES,
LMTGRP=10, CNTRX=NO, PBX=NO, CHG=NO, ENH=NO;
NOTE
l The call barring relationship is not designed for the subscriber numbers ranging from 3331001 to
3331020. Therefore, do not define a call barring group number for them.
l Call barring relationship is designed for the subscriber numbers ranging from 3331021 to 3331099.
Therefore, define a call barring group number for them. In this example, it is 10.
Related tasks
None.
Related concepts
Call Barring Methods
11.5.6 Configuring Nested Dialing Data
Example
Task Description
Figure 11-21 shows the networking when the SoftX3000 serves as the gateway office. To ensure
optimal use of the circuits, nested dialing between two peer offices is prohibited, and only the
specified trunk nested dialing is allowed.

Figure 11-21 Typical networking of the SoftX3000 trunk nested dialing feature
SoftX3000 1 SoftX3000 2
A B C D
The application requirements are as follows:
The nested dialing is prohibited between the peer offices, that is, SoftX3000_1 and SoftX3000_2;
only the trunk nested dialing with trunk group number 10 is allowed.
Scripts
//Configure an office of the same level as the peer office.

ADD OFC: O=11, DOT=INTT, DOL=SAME;
//Configure the p223 software parameter with bit 0 set to 0; that is, the nested dialing between
peer offices is prohibited.
//Add a trunk that supports the nested dialing.

ADD TGAP: TG=10, CDFP=NO, CNCM=ALLOW, CCICF=NO, CNISUP=NO, HPR=YES;
Related Tasks
None.
Related Concepts
None.
11.5.7 Configuring IGC Call Barring Data
Example
Task Description
Figure 11-22 shows the networking when multiple SoftX3000s serve as the international
gateway offices.

Figure 11-22 Typical networking of the SoftX3000 call barring feature

SoftX3000 1 SoftX3000 SoftX3000 2
A B C D
SoftX3000_1, SoftX3000, and SoftX3000_2 are peer offices. When A calls C, the SoftX3000
checks whether the IGC type of the outgoing trunk group is the same as that of the incoming
trunk group. If the IGC type is the same, the SoftX3000 selects the next sub-route.
Scripts
//Add the office direction: SoftX3000_1 to SoftX3000 and SoftX3000 to SoftX3000_2.

ADD OFC: O=1, DOT=IGCINT, DOL=SAME;
ADD OFC: O=2, DOT=IGCINT, DOL=SAME;
Related Tasks
None.
Related Concepts
None.
11.5.8 Configuring Barring on a Certain Proportion of Calls

Destined to a Specified Prefix over the Designated Trunk
Example
Task Description
Figure 11-23 shows the networking when the SoftX3000 serves as the tandem office. Trunks
are configured between the SoftX3000 and SoftX3000_1 and between the SoftX3000 and
SoftX3000_2. Subscribers of SoftX3000_1 and SoftX3000_2 can call each other through
SoftX3000, SoftX3000_1, and SoftX3000_2. When a call from SoftX3000_1 arrives, the tandem
office SoftX3000 judges the call barring proportion during this period of time.

Figure 11-23 Typical networking of barring on a certain proportion of calls destined to a

specified prefix over the designated trunk on the SoftX3000
SoftX3000 1 SoftX3000 SoftX3000 2
A B C D
Restrict the calls addressed to the number 0106666 through trunk group 2 between 12:00 to
13:00 every day; the barring proportion is 60%. The incoming trunk network management source
code of trunk group 2 is 3.
Scripts
//Configure barring on a certain proportion of calls destined to a specified prefix over the
designated trunk.
ADD NMIDEST: P=0, CDC=K'0106666, PERC=60, MED=TIMER, ACT=ACT,
TYPE=INCOMING, INTRK=3, ST1="12&00", ET1="13&00";
Related Tasks
None.
Related Concepts
Call Barring Methods
11.5.9 Configuring Call Congestion Barring Data
Example
Task Description
In the case of heavy traffic when the SoftX3000 serves as the end office and tandem office,
carriers need to restrict calls based on call priorities of subscribers, CPU overload levels, and
customized barring percentage. If the CPU usage exceeds 95%, all the calls except emergency
calls are restricted.

l The priority of calls with the call prefix 0755 is level 3.

l The CPU overload threshold and resume threshold are (75-70), (80-75), (85-80), and
(90-85) respectively.
l There are four CPU overload levels. The barring percentage for level-1 CPU overload is
25%, for level-2 CPU overload 50%, for level-3 overload 75%, and for level-4 CPU
overload 95%.
Scripts
//Configure call priorities.
ADD CALLTHD: CSC=1, LP=0, PFX=K'0755, RUT=NRM, CLP=LV3;
//Configure CPU overload levels.

SET CPUTHD: MN=2, LV1=75, LV2=80, LV3=85, LV4=90, LR1=70, LR2=75, LR3=80,
LR4=85;
//Configure barring percentages.

SET CALLCFG: CLV=LV4, CLP1=25, CLP2=50, CLP3=75, CLP4=95;
Related Tasks
None.
Related Concepts
Whether call barring is performed and what is the barring percentage is determined based on
CPU overload levels and call priorities, as shown in Table 11-11.
Table 11-11 Call barring based on CPU overload levels and call priorities
CPU Priority 1 Priority 2 Priority 3 Priority 4 Priority 5
Overload
Level/Call
Priority
Level-1 Percentage Not barring Not barring Not barring Not barring
overload call barring
Level-2 Percentage Percentage Not barring Not barring Not barring

overload call barring call barring
Level-3 Percentage Percentage Percentage Not barring Not barring

overload call barring call barring call barring
Level-4 Percentage Percentage Percentage Percentage Not barring

overload call barring call barring call barring call barring
CPU > 95% Barring Barring Barring Barring Barring
11.6 Configuration Example of Network Management Data

11.6.1 Configuring Network Management Instruction Data

11.6.2 Configuring Low Level Call Gapping Control
11.6.3 Configuring NTP Client Data
11.6.1 Configuring Network Management Instruction Data

To implement the network management function, all the nodes in the telecommunications
network must receive and implement the instructions sent by the network management center.
These instructions are "network management instructions".
The SoftX3000 can provide the following network management instructions and MML
commands:
l Command for adding originating source codes: (ADD NMIDEST)
l Command for adding outgoing source codes: (ADD NMODEST)
l Command for adding call interval control: (ADD NMGAP)
l Command for adding circuit orient control: (ADD NMCICD)
l Command for adding circuit reject control: (ADD NMCICR)
l Command for adding direct route control: (ADD NMDRT)
l Command for alternative route cancellation control: (ADD NMCRT)
l Command for temporary alternative route control: (ADD NMTMP)
l Command for adding skip sub-route control: (ADD NMSRT)
l Command for adding special record notification control: (ADD NMTONE)
l Command for adding trunk reserved control: (ADD NMRES)
l Command for adding sub-route (group) barring control: (ADD NMDCRT)
l Command for modifying bearer quality check control: (SET QOSPARA)
l Commands for activating, deactivating, and deleting network management control: (ACT
NM/DEA NM/RMV NM)
Example
Task Description
The following takes the operation of adding direct route control as an example.
The application requirements are as follows: Restrict direct services on the direct sub-route 12
of ordinary subscribers in the local office with the barring percentage of 10%, and transfer the
overflow traffic to other sub-routes.
Scripts
//Configure direct route control data.
ADD NMDRT: SUB=12, PERC=10, CTRL=CancelTo, TYPE=ORIGINE, CAT=NRM;
Related Tasks
None.

Related Concepts
None.
11.6.2 Configuring Low Level Call Gapping Control

Example
Introduction
This section describes how to configure the data by taking PRA calls for example. To perform
call gapping on the SETUP ACK messages in PRA calls, set Gapping mode to Auto mode,
Level 1 overload gapping rate to 20, Level 2 overload gapping rate to 30, Level 3 overload
gapping rate to 40, Level 4 overload gapping rate to 50, and Active state to Active. The
command is as follows:
Scripts
//Enable the call gapping software parameter.
MOD FSFP: ID=240, ModType=P0, Value="1";
//Configure the call gapping strategy.

ADD LGAPSTR: GGNAME="PRAWC", SITYPE=PRAWC, PTYPE=SETUPACK0xD,
GMODE=AMODE, L1RATE=20, L2RATE=30, L3RATE=40, L4RATE=50, ASTATE=ACT;
l Gapping mode
– If you set Gapping mode to Auto mode, you need to set Level 1 overload gapping
rate, Level 2 overload gapping rate, Level 3 overload gapping rate, and Level 4
overload gapping rate.
– If you set Gapping mode to Fix mode, you need to set Fix Mode Gapping Rate.
The CPU overload thresholds are configured by running SET CPUTHD. You are advised
to use the default values. If you need to change the values, confirm with Huawei engineers.
l Signalling interface type
– If you set Signalling interface type to protocol wildcard (such as TUP wildcard), you
need not set gapping group.
– If you set Signalling interface type to non-protocol wildcard (such as TUP), you need
to configure a call gapping group by running ADD LGAPGRP.
Related tasks
After the preceding data is configured:
l When the CPU is not overloaded, the SoftX3000 is able to process SETUP ACK messages
in PRA calls normally.
l When level 1 CPU overload occurs on the BSGI board, the SoftX3000 discards 20% of
SETUP ACK messages in subsequent PRA calls.

Related concepts
None.
11.6.3 Configuring NTP Client Data
Example
Task Description
(NTP client data needs to be configured only when the SoftX3000 is required to interwork with
the NTP sever.)
l The IP address of the NTP sever, which is 129.9.10.123, has been configured on the
SoftX3000.
l The synchronization period is six minutes.
l The BAM unconditionally synchronizes time from the NTP sever. The BAM does not
perform synchronization and sends an alarm when the time offset reaches 8 seconds.
Scripts
//Add an NTP sever.

ADD NTPSVR: NSL="129.9.10.123";
//Configure NTP sever data.

SET NTPCFG: NSP=6, FORCESYN=NO, TMWARNTHD=8;
NOTE
New configuration takes effect on the next synchronization task.
Related Task
None.
Related Concept
NTP Client
11.7 Configuration Example of Equal Access Data

Introduction
With the equal access service, subscribers can choose different carriers for toll calls. Figure
11-24 shows the network of the equal access service.

Figure 11-24 Network of the equal access service
Originating Office Gateway office A Gateway office B Terminating Office
ISUP ISUP ISUP
Caller A Carrier A Carrier B Callee B
Example
Task Description
The toll call line can be selected between the gateway office A and gateway office B based on
calling subscribers.
Scripts
1. Configure the data of the preselection service in originating office mode.
//Configure the local office data. Set Local office ONID to 990.
SET OFI: TMZ=14, ONINM="990", SGCR=NO;
//Add a toll call prefix from the local office to the gateway office. Set Call prefix to 091
and Service attribute to National toll.
MAXL=24, CHSC=0, EA=YES, ASF=NO, QCDN=NO, OBDTMFFLAG=NO, VPNF=NOVC;
//Add a preselection access code. Set Access code to 091 and Carrier selection code to
AB2C91.
ADD PRECODE: IDX=91, ACD=K'091, CN="B Carrier", CSC=K'AB2C91;
//Add the preselection data.
ADD PRESEL: PREPOLCODE=1, PRESELCODE=2, FUNCCODE=PRE, PRESELINDX=91,
REANAFLAG=ARE;
//Add a toll call prefix from the local office to the gateway office. Set Call prefix to 0,
Service attribute to National toll, and Preselect select code to 2.
CHSC=0, EA=YES, ASF=NO, PRESELCODE=2, QCDN=NO, OBDTMFFLAG=NO,
VPNF=NOVC;
//Change Preselect policy code of subscriber A to 1.
MOD VSBR: D=K'66600001, LP=0, CNTRX=NO, PBX=NO, CHG=NO, ENH=YES,
PPCD=1;
//Add the trunk group appendant data. Set Carrier selection flag to True.
ADD TGAP: TG=40, CSF=YES, CDFP=NO, CNCM=ALLOW, CCICF=NO, CNISUP=NO;
2. Configure the data of the preselection service in terminating office mode.
//Modify the software parameter data. Change bit 7 of P155 to 0.
MOD FSFP: ID=P155, ModType=P1, Bit=7, BitVal=0;

//Add an originating network ID. Set Originating network ID to 990, which is the ONID
of the originating office.
ADD ONID: ONI=K'990;
3. Configure the data of the preselection service in incoming gateway mode.
//Configure the local office data. Set Local office CAC number to AB2C91.
SET OFI: TMZ=14, CACNM="AB2C91";
//Add a carrier access code. Set CAC source code to By CAC IE and CAC
discrimination to Discriminate.
ADD CAC: TG=41, CACSC=CACIE, CACDM=DCM;
//Remove the first three digits of the number.
//Add the call prefix processing data to enable the SoftX3000 to remove the call prefix 091
and reanalyze the data.
ADD PFXPRO: LP=0, PFX=K'091, CCF=YES, SENDTONE=NST, DDCX=3,
ISREANA=YES, TT=REC0;
Related Tasks
Related Concepts
None
11.8 Configuration Example of Remote Network Access

Data
Introduction
Assume that a local subscriber makes a call to a subscriber of another network B in a different
area. In normal conditions, the call is transferred to the local network B and then transferred
from the local network B to network B in the destined area. With the remote network access
service, the call is transferred from the existing local network to the local network in the destined
area and then to network B in the destined area. Consequently, the toll call traffic of the local
network increases. The remote network access service can be implemented in special number
change mode and IN mode. For details on the special number change mode, see 11.2.6
Configuring Special Called Number Change Data.
NOTE
In IN mode, if a local subscriber makes a call to a subscriber of a different network in another area, the
SCP is triggered to insert a toll area code before the called number. Based on the inserted toll area code,
the SoftX3000 transfers the call to the local network in the destined area.
Example
Task Description
As shown in Figure 11-25, a fixed-network subscriber in Shenzhen dials 01301025647 to make
a call to a mobile subscriber in Beijing. Configure data on the SoftX3000 in Shenzhen to enable

the remote network access service in IN mode and ensure that the call is connected through the
fixed toll network.
Figure 11-25 Network of remote network access service in IN mode
SCP
Callee Callee Beijing

Local Exchange 13901025647 01013901025647 SoftX3000
Shenzhen
SoftX3000
Call Beijing
013901025647 MSOFTX3000
075587642112 13901025647
Scripts
//Add a call prefix 0139 for triggering the remote network access service.
ADD CNACLD: LP=0, PFX=K'0139, CSTP=IN, MINL=12, MAXL=12, CHSC=0, EA=NO;
//Add an IN service access code 0139.

ADD ACCODE: CODE=K'0139;
//Add the TDP data.

ADD TDPCFG: DPNO=DP3, CODE=K'0139, SKEY=139, CALLSRC=65534;
//Add the SCP physical address description data.

//Add the SSP physical address description data.

//Add the SCP data.

//Add a toll call prefix.

ADD CNACLD: LP=0, PFX=K'010, CSTP=BASE, CSA=LCT, RSC=1, MINL=3, MAXL=32,

CHSC=0, EA=NO;
Related Tasks
Related Concepts
None

Initial Configuration 12 Relations Between Database Tables
12 Relations Between Database Tables
About This Chapter
12.1 Relations Between Hardware Data Tables

12.2 Relations Between Local Office Data Tables
12.3 Relations Between Subscriber Data Tables
12.5 Relations Between Billing Data Tables
12.6 Relations Between Signaling Data Tables
12.8 Relations Between Trunk Circuit Data Tables

12 Relations Between Database Tables Initial Configuration
12.1 Relations Between Hardware Data Tables

Figure 12-1 shows the relations between hardware data tables.
Figure 12-1 Relations between hardware data tables

ADD SHF ADD FECFG
Shelf number IFMI module number
(SHN) (MN)
Zone number IP address
(RN) (IP)
Row number Subnet mask
(CN) (MSK)
ADD FRM
Frame number ADD CDBFUNC
(FN) CDBI module number
Shelf number (CDPM)
(SHN) Function configuration
Position number (FCF)
(PN)
ADD BRD
Frame number SET DPA
(FN) BSGI/MSGI module number
Slot number (MN)
(SLN) Protocol Dispatch ability
Module number (DA)
(MN)
12.2 Relations Between Local Office Data Tables

Figure 12-2 shows the relations between local office data tables.

Figure 12-2 Relations between local office data tables

ADD NCODE
DN set
(P)
Country/Region code
(NC)
Country/Region name
(NN)
ADD PFXTOL
DN set ADD CALLSRC
(P) Local DN set
Country/Region code (LP)
(NC) Call source code
National toll prefix (CSC)
(NTP)
ADD ACODE
DN set
(P)
Country/Region code
(NC)
National area code
(AC)
ADD LDNSET
Local DN set
(LP)
DN set
(P)
Country/Region code
(NC)
National area code
(AC)
12.3 Relations Between Subscriber Data Tables

Figure 12-3 shows the relations between subscriber data tables.

Figure 12-3 Relations between subscriber data tables

ADD LDNSET
ADD LDNSET Local DN set(LP)
ADB MSBR
Local DN set(LP) ADD CHGGRP
Local DN set(LP)
ADB VSBR ADD CHGGRP Charging source Charging source
Local DN set(LP) Caller charging source code(RCHS) code(RCHS)
code(RCHS)
Charging source Call source
ADD CALLSRC
code(RCHS) code(CSC)
ADD CALLSRC Call source code(CSC)
Call source
code(CSC) Call source code(CSC)
Equipment ID(EID) ADD LDNSET
ADD MGW ADB WACSBR Local DN set(LP)
Equipment ID(EID)
Local DN set(LP)
Centrex group
number(CXG) ADD CXGRP
Centrex subgroup Centrex group
number(CXSG) number(CXG)
ADD LDNSET
Local DN set(LP)
ADD LDNSET
ADD CHGGRP Local DN set(LP)
ADB PRA Caller charging source
ADD CHGGRP
code(RCHS)
Local DN set(LP) Charging source
ADB BRA code(RCHS)
Charging source ADD CALLSRC
code(RCHS) Call source code(CSC) Local DN set(LP)
ADD CALLSRC
Call source Charging source
code(RCHS) Call source code(CSC)
code(CSC)
Equipment ID(EID) ADD MGW Call source
Equipment ID(EID) code(CSC) ADD MGW
PRA trunk group
(TRUNLGP) Equipment ID(EID) Equipment ID(EID)
ADD PRATG IUA link set
ISDN index(ISDN) Trunk group number(TG) index(LKS) ADD IUALKS
ISDN index(ISDN) Linkset index(LSX)
ADD ISDNDAT
Index(ISDN) ADD ISDNDAT
Index(ISDN)

Figure 12-4 shows the relations between number analysis data tables.

Figure 12-4 Relations between number analysis data tables

ADD LDNSET ADD DNC
Local DN set(LP) Number change index(DCX)
DN set(P)
ADD PFXPRO
Country/Region code(NC)
Local DN set(LP)
Call source code(CSC)
ADD CALLSRC Call prefix(PFX)

Called number change index
Local DN set(LP) (DDCX)
Caller number change index
Call source code(CSC) (RDCX)
Route selection source code Failure cause code(FCC)
(RSSC)
ADD CNACLR
Local DN set(LP)

ADD CNACLD
Call prefix(PFX)
Local DN set(LP)
Call prefix(PFX) (DDCX)
Caller number change index
(RDCX)
Failure cause code(FCC)
ADD SPCNACLD
ADD CFPRO
Local DN set(LP)
Local DN set(LP)
Call prefix(PFX)
Call prefix(PFX)
(DDCX)
Failure cause code(FCC)
SET RLSMOD
Failure source code(FSC)
Local DN set(LP)
ADD AUSSIG
Call prefix(PFX)
Local DN set(LP)
Call prefix(PFX)
12.5 Relations Between Billing Data Tables

Figure 12-5 shows the relations between billing data tables.

Figure 12-5 Relations between billing data tables

ADD CHGANA ADD CHGIDX
Charging case Charging selection code
(CHA) (CHSC)
Charging manner Caller charging source code
(CHGM) (RCHS)
Payer Charging case
(PAY) (CHA)
ADD CHGGRP
MOD CHGMODE Caller charging source code
Charging case (RCHS)
(CHA) Charging case
Date category (CHA)
(DAT)
Time zone1 switch point ADD CHGCLD
(TS1) Callee charging source code
(DCHS)
Charging case
MOD PLUSMOD (CHA)
Charging case
(CHA) ADD CHGCX
Date category Centrex group number
(DAT) (CXG)
Time zone1 switch point Charging case
(TS1) (CHA)
12.6 Relations Between Signaling Data Tables

12.6.1 Relations Between M2UA Signaling Data Tables
12.6.3 Relations Between V5UA Signaling Data Tables
12.6.4 Relations Between IUA Signaling Data Tables
12.6.6 Relations Between SCCP Signaling Data Tables
12.6.7 Relations Between V5 Signaling Data Tables
12.6.8 Relations Between PRA Signaling Data Tables
12.6.9 Relations Between COPS Signaling Data Tables

Figure 12-6 shows the relations between M2UA signaling data tables.

Figure 12-6 Relations between M2UA signaling data tables

ADD SG
SG ID
(SGID)
SG type
(SGTYPE)
Equipment ID
(EID)
ADD M2LKS
M2UA linkset
index(M2LSX)
SG ID
(SGID)
ADD M2LNK
BSGI module
number(MN)
Link number
(LNKN)
M2UA linkset
index(M2LSX)
Local port number
(LOCPORT)
Local IP address1
(LOCIP1)
Peer IP address1
(PEERIP1)

Figure 12-7 shows the relations between M3UA signaling data tables.

Figure 12-7 Relations between M3UA signaling data tables
ADD M3LE
Local entity index(LEX)

Signaling point code of
local entity(OPC)
Local entity type(LET)
ADD M3DE
Destination entity
index(DEX)
Local entity index(LEX)
Signaling point code of
destination entity(DPC)
Destination entity
type(DET)
ADD M3DS
Additional service
index(DSX)
Destination entity
index(DEX)
ADD M3LKS
Linkset index(LSX)
Adjacent destination entity
index(ADX)
Work mode(WM)
ADD M3LNK
BSGI module number(MN)
Link number(LNKN)
Local IP address1(LOCIP1)
Peer IP
address1(PEERIP1)
Client/Server(CS)
Linkset index(LSX)
ADD M3RT
Route name(RTNAME)
Destination entity
index(DEX)
Linkset index(LSX)
12.6.3 Relations Between V5UA Signaling Data Tables

Figure 12-8 shows the relations between V5UA signaling data tables.

Figure 12-8 Relations between V5UA signaling data tables

ADD SG
SG ID
(SGID)
SG type
(SGTYPE)
Equipment ID
(EID)
ADD V5UALKS
Linkset index
(LSX)
Signaling gateway
ID(SGID)
ADD V5UALNK
BSGI module
number(MN)
Link number
(LNKN)
Linkset index(LSX)
Local port number

(LOCPORT)
Local IP address
1(LOCIP1)
Peer IP address
1(PEERIP1)
12.6.4 Relations Between IUA Signaling Data Tables

Figure 12-9 shows the relations between IUA signaling data tables.

Figure 12-9 Relations between IUA signaling data tables

ADD SG
SG ID
(SGID)
SG type
(SGTYPE)
Equipment
(EID)
ADD IUALKS
Linkset index
(LSX)
FCCU module
number(LSX)
Signaling gateway
ID(SGID)
ADD IUALNK
BSGI module
number(MN)
Linkset
number(LNKN)
Linkset index(LSX)
Local port number

(LOCPORT)
Local IP address
1(LOCIP1)
Peer IP address
1(PEERIP1)

Figure 12-10 shows the relations between MTP signaling data tables.

Figure 12-10 Relations between MTP signaling data tables

ADD N7DSP ADD M2LKS
M2UA linkset
DSP index(DPX)
index(M2LSX)
OPC Signaling gateway
(OPC) ID(SGID)
DPC
(DPC)
ADD N7LKS
Linkset index
(LSX)
Adjacent DSP
Iindex(ASPX)
ADD N7LNK
BSGI module
number(MN)
Link number
(LNKN)
Link type
(LNKTYPE)
M2UA linkset
index(M2LSX)
Integer interface
ID(BINFID)
Signaling link
code(SLC)
Linkset index
(LSX)
Start circuit
terminator ID(TID)
ADD N7RT
Linkset
index(LSX)
DSP index
(DPX)
12.6.6 Relations Between SCCP Signaling Data Tables

Figure 12-11 shows the relations between SCCP signaling data tables.

Figure 12-11 Relations between SCCP signaling data tables
ADD N7DSP ADD SCCPDSP

DSP index DSP index
(DPX) (DPX)
OPC OPC
(OPC) (OPC)
DPC DPC
(DPC) (DPC)
Network indicator
ADD M3DE (NI)
Destination entity
OR
index(DEX) ADD SCCPSSN
Network indicator
Local enitity index(LEX)
(NI)
Signaling point code of SCCP sub-system
destination entity(DPC) number(SSN)
Destination entity SPC
type(DET) (SPC)
OPC
(OPC)
ADD SCCPNGT
New GT index(NGTX)
Handle mode
(HANDMODE)
GT address
information(ADDR)
ADD SCCPGT
GT index
(GTX)
SCCP sub-system
number(SSN)
SPC
(SPC)
New GT index(NGTX)
GT address
information(ADDR)
12.6.7 Relations Between V5 Signaling Data Tables

Figure 12-12 shows the relations between V5 data tables.

Figure 12-12 Relations between V5 signaling data tables

ADD V5TG
Trunk group
number(TGID)
Equipment ID
(EID)
ADD V5I
V5 interface
ID(V5IID)
Trunk group
number(TGID)
Primary link logical
C-channel ID(MID)
Primary link circuit
number(PNUM)
Secondary link circuit
number(SNUM)
V5 variant
number(IVC)
ADD V5VAR
V5 interface
ID(V5IID)
V5 variant
number(IVC)
New V5 interface
ID(NIFID)
12.6.8 Relations Between PRA Signaling Data Tables

Figure 12-13 shows the relations between PRA data tables.

Figure 12-13 Relations between PRA signaling data tables
ADD IUALKS
Linkset index(LSX)
FCCU module
number(MN)
Signaling gateway
ID(SGID)
ADD PRALNK
Link number
(PLN)
FCCU module
number(MN)
IUA linkset
index(LKS)
Signal circuit
number(SCN)
12.6.9 Relations Between COPS Signaling Data Tables

Figure 12-14 shows the relations between COPS data tables.

Figure 12-14 Relations between COPS signaling data tables

ADD CMTS
CMTS index
(CMTSI)
CMTS Identify
(CMTSID)
CMTS IP
address(IP)
CMTS Port
number(PORT)
ADD COPSLNK
COPS Link Index
(COPSLNKNO)
MSG Module
Number(MSGMNO)
CMTS Index
(CMTSI)
IFMI Module
Number(IFMMNO)
Local Port
(LOCALPORT)

Figure 12-15 shows the relations between route data tables.

Figure 12-15 Relations between route data tables
ADD OFC
Office direction
number (O)
Peer office
type(DOT)
Peer office
level(DOL)
ADD SRT
Sub-route
number(SRT)
Office direction
number(O)
ADD RT
Route number(R)
1st sub-route
n sub-route
ADD TMIDX
Week(WD)
Hour(TM) ADD CALLSRC
Route selection
Time index(TMX)
source code(RSSC)
ADD CNACLD
ADD RTANA Route selection
Route analysis codeRSC)
name(RAN)
Time index(TMX)
Route number(R)
Route selection
code(RSC)
Route selection
source code(RSSC)
12.8 Relations Between Trunk Circuit Data Tables

12.8.1 Relations Between N0.7 Trunk Circuit Data Tables

12.8.2 Relations Between R2 Trunk Circuit Data Tables

12.8.3 Relations Between PRA Trunk Circuit Data Tables
12.8.4 Relations Between AT0 Trunk Circuit Data Tables
12.8.5 Relations Between V5 Trunk Circuit Data Tables
12.8.1 Relations Between N0.7 Trunk Circuit Data Tables

Figure 12-16 shows the relations between N0.7 trunk circuit data tables.
Figure 12-16 Relations between N0.7 trunk circuit data tables

ADD N7TG
Trunk group number
(TG)
Equipment ID
(EID)
Group direction
(G)
ADD N7TKC
FCCU module number
(MN)
Trunk group number
(TG)
Start circuit number
(SC)
12.8.2 Relations Between R2 Trunk Circuit Data Tables

Figure 12-17 shows the relations between R2 trunk circuit data tables.

Figure 12-17 Relations between R2 trunk circuit data tables

ADD N1TG
Trunk group number
(TG)
Equipment ID
(EID)
Group direction
(G)
ADD N1TKC
FCCU module number
(MN)
Trunk group number
(TG)
(SC)
ADD N1TDM
Incoming trunk group number
(IGN)
Outgoing trunk group number
(OGN)
Tandem mode
(TM)
12.8.3 Relations Between PRA Trunk Circuit Data Tables

Figure 12-18 shows the relations between PRA trunk circuit data tables.
Figure 12-18 Relations between PRA trunk circuit data tables

ADD PRATG
Trunk group number
(TG)
Equipment ID
(MGW)
Sub-route number
(SRC)
ADD PRATKC
FCCU module number
(MN)
Trunk group number
(TG)
Start circuit
(SC)

12.8.4 Relations Between AT0 Trunk Circuit Data Tables

Figure 12-19 shows the relations between AT0 trunk circuit data tables.
Figure 12-19 Relations between AT0 trunk circuit data tables

ADD AT0TG
Trunk group number
(TG)
Group direction
(G)
Equipment ID
(EID)
ADD AT0TKC
FCCU module number
(MN)
Trunk group number
(TG)
(SC)
12.8.5 Relations Between V5 Trunk Circuit Data Tables

Figure 12-20 shows the relations between V5 trunk circuit data tables.
Figure 12-20 Relations between V5 trunk circuit data tables

ADD V5TG
Trunk group number
(TGID)
Equipment ID
(MGEID)
ADD V5TKC
FCCU module number
(MN)
Start E1 number
(SEN)
End E1 number
(EEN)
Trunk group number
(TGID)


UMG8900 CONFIGURACIÓN 307315391-01-Initial-Configuration-V300R010C03-02 PDF

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

UMG8900 CONFIGURACIÓN 307315391-01-Initial-Configuration-V300R010C03-02 PDF

Uploaded by

Copyright:

Available Formats

U-SYS SoftX3000 SoftSwitch System

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 02 (2010-09-14) Huawei Proprietary and Confidential i

About This Document

Product Name Version

U-SYS SoftX3000 V300R010C03

Changes in Issue 01 (2010-03-25)

Changes in Issue 02 (2010-09-14)

Issue 02 (2010-09-14) Huawei Proprietary and Confidential iii

About This Document...................................................................................................................iii

3 Configuring Basic Data............................................................................................................. 3-1

4 Configuring Data for Subscriber Access Networking........................................................ 4-1

Issue 02 (2010-09-14) Huawei Proprietary and Confidential v

5 Configuring Data to Interwork with MRS............................................................................5-1

6 Configuring Data to Interwork with Subscriber Terminal...............................................6-1

7 Configuring Subscriber Data...................................................................................................7-1

9 Configuring Data to Interwork with Other Service Devices.............................................9-1

vi Huawei Proprietary and Confidential Issue 02 (2010-09-14)

9.5 Configuring Data to Interwork with the SHLR.............................................................................................9-53

10 Typical Networking Configuration Examples.................................................................10-1

11 Typical Data Configuration Example.................................................................................11-1

Issue 02 (2010-09-14) Huawei Proprietary and Confidential vii

11.3.6 Configuring M3UA Signaling Route Data.......................................................................................11-83

12 Relations Between Database Tables...................................................................................12-1

viii Huawei Proprietary and Confidential Issue 02 (2010-09-14)

12.8 Relations Between Trunk Circuit Data Tables..........................................................................................12-16

Issue 02 (2010-09-14) Huawei Proprietary and Confidential ix

Figure 1-1 Data configuration procedure.............................................................................................................1-1

Issue 02 (2010-09-14) Huawei Proprietary and Confidential xi

xii Huawei Proprietary and Confidential Issue 02 (2010-09-14)

Figure 11-10 Route tree planning.....................................................................................................................11-77

Issue 02 (2010-09-14) Huawei Proprietary and Confidential xiii

Issue 02 (2010-09-14) Huawei Proprietary and Confidential xv

xvi Huawei Proprietary and Confidential Issue 02 (2010-09-14)

Issue 02 (2010-09-14) Huawei Proprietary and Confidential xvii

1 Data Configuration Procedure

Figure 1-1 Data configuration procedure

Plan the IP Configure data for

Plan hardware Configure local Configure data for

Plan local Configure Configure data for

Configure data for

Configure data for

Issue 02 (2010-09-14) Huawei Proprietary and Confidential 1-1

1-2 Huawei Proprietary and Confidential Issue 02 (2010-09-14)

About This Chapter

2.1 Planning the Bearer Network IP Address

Issue 02 (2010-09-14) Huawei Proprietary and Confidential 2-1

2.1 Planning the Bearer Network IP Address

l Local end device

IP Address Planning Principle for the Local End Device

Device Planning Principle

SoftX3000 A pair of IFMIs working in active/standby mode require an IP address.

TMG8010 A TMG8010 requires an IP address.

AMG5000 An AMG5000 requires an IP address.

2-2 Huawei Proprietary and Confidential Issue 02 (2010-09-14)

Device Planning Principle

MRS6100 l For signaling: A pair of MCCUs working in active/standby mode

SG7000 A pair of SBPIs working in active/standby mode require an IP address.

SBC A Eudemon2000 SBC requires an IP address on each interface. Note

RM9000 A RM9000 requires an IP address. The BNI of the NPB provides an FE

UC The number of IP addresses occupied by the UC is related to the