01_initial configuration-(v300r010c03_02).pdf

8/18/2019 01_Initial Configuration-(V300R010C03_02).pdf

1/570

U-SYS SoftX3000 SoftSwitch System

V300R010C03

Initial Configuration

Issue 02

Date 2010-09-14

HUAWEI TECHNOLOGIES CO., LTD.


2/570


3/570

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: [email protected]

Issue 02 (2010-09-14) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com/


4/570


5/570

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.


Initial Configuration About This Document



iii


6/570


7/570

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


Initial Configuration Contents



v


8/570

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-18 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 Conf iguring 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-458.3.1 Configuring Data to Interwork with H.323 Network (GK - GW)........................................................8-46

8.3.2 Conf iguring 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 Conf iguring 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

Contents



vi Huawei Proprietary and Confidential


Issue 02 (2010-09-14)


9/570

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-610.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-211.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-4511.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





vii


10/570

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 Configur ation Example of Equal Access Data........................................................................................11-131

11.8 Configur ation 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-612.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

Contents



viii Huawei Proprietary and Confidential


Issue 02 (2010-09-14)


11/570

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





ix


12/570


13/570

Figures

Figure 1-1 Data configuration procedure.............................................................................................................1-1

Figure 3-1 Board configuration in the basic subrack........................................................................................... 3-3

Figure 3-2 Ty pical 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 Ty pical networking model for the SoftX3000 to interwork with the MRS6100................................5-9

Figure 5-3 Ty pical networking model for the SoftX3000 to interwork with the MRFP6600................... ........5-14

Figure 6-1 Ty pical networking model for SIP terminals interworking with the SoftX3000............................... 6-2Figure 6-2 Ty pical networking model for H.323 terminals interworking with the SoftX3000......................... ..6-6

Figure 6-3 Ty pical 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 O peration panel of the ViewPoint 8220.................................................................................. .......6-23

Figure 6-11 Network interface...........................................................................................................................6-23

Figure 6-12 User interface..................................................................................................................................6-24

Figure 8-1 Ty pical networking model for the SoftX3000 to interwork with the SCP (M3UA - MTP) ............. 8-2

Figure 8-2 Ty pical networking model for the SoftX3000 to interwork with the SCP (M3UA - M3UA) .......... 8-8

Figure 8-3 Ty pical 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


Initial Configuration Figures



xi


14/570

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-63Figure 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 Ty pical networking model for the SoftX3000 to interwork with the PBX (through PRA) ..... ..... ....9-2

Figure 9-2 Ty pical networking model for the SoftX3000 to interwork with the PBX (through the R2 trunk)

.............................................................................................................................................................................9-12

Figure 9-3 Ty pical networking model for the SoftX3000 to interwork with the PBX (through the AT0 trunk)

.............................................................................................................................................................................9-19

Figure 9-4 Ty pical networking model for the SoftX3000 to interwork with the PBX (through the loop trunk)

.............................................................................................................................................................................9-25

Figure 9-5 Ty pical networking model for the SoftX3000 to interwork with the PBX (through the SIP trunk)

.............................................................................................................................................................................9-31

Figure 9-6 Ty pical 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 Ty pical 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 R elation 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-62Figure 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 R oute tree planning.......................................................................................................................11-76

Figures



xii Huawei Proprietary and Confidential


Issue 02 (2010-09-14)


15/570

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 R elations between hardware data tables ........................................................................................12-2

Figure 12-2 R elations between local office data tables......................................................................................12-3

Figure 12-3 R elations between subscriber data tables.......................................................................................12-4

Figure 12-4 R elations between number analysis data tables..............................................................................12-5

Figure 12-5 R elations between billing data tables.............................................................................................12-6

Figure 12-6 R elations between M2UA signaling data tables.............................................................................12-7

Figure 12-7 R elations between M3UA signaling data tables.............................................................................12-8

Figure 12-8 R elations between V5UA signaling data tables..............................................................................12-9

Figure 12-9 R elations 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-15Figure 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


Initial Configuration Figures



xiii


16/570


17/570

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-30Table 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


Initial Configuration Tables



xv


18/570

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-37Table 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

Tables



xvi Huawei Proprietary and Confidential


Issue 02 (2010-09-14)


19/570

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-72Table 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


Initial Configuration Tables



xvii


20/570


21/570

1 Data Configuration ProcedureContext

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

Start Plan dataConfigure

basic data

Configure

interworking data

Plan hardware

data

Plan local

office data

Plan the IPaddress of thebearer subnet

Configure local

office data

Configure

charging data

Configure

hardware data

Configure data forinterworking with

the MRS


the terminal


the accessequipment

Configure data forinterworking withother networks


other service

devices

Configure

subscriber data

End


Initial Configuration 1 Data Configuration Procedure



1-1


22/570

1 Data Configuration Procedure



1-2 Huawei Proprietary and Confidential


Issue 02 (2010-09-14)


23/570

2 Planning DataAbout This Chapter

2.1 Planning the Bearer Network IP Address

2.2 Planning the Equipment Data

2.3 Planning the Local Office Data


Initial Configuration 2 Planning Data



2-1


24/570

2.1 Planning the Bearer Network IP Address

In the deployment process, you should have an overall understanding of the data of the NGNoffices. 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.

NOTEOn 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.

2 Planning Data





Issue 02 (2010-09-14)


25/570


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.





2-3


26/570


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

system

Only the FG1O is configured on the large-capacity UMG8900.

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-capacityUMG8900 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.

2 Planning Data





Issue 02 (2010-09-14)


27/570

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

system

You can perform central forwarding by using the FMPU/FMPB in the

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

Host NameVirtual IPAddress

Intra-Group IPAddress Planning Principle

media1 media1_web Media1_web_test

0

Seven IP addresses are required.

media2 media2_web Media1_web_test

1





2-5


28/570

Host NameVirtual IPAddress

Intra-Group IPAddress Planning Principle

Media2_web_test

0

NOTE Note that the IP addresses must be public

network IP addresses in the samenetwork segment. The MediaX3600

provides the web access through the

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).

Media2_web_test

1

media1 media1_sip Media1_sip_test0 Seven IP addresses are required.

NOTE Note that the IP addresses must be in thesame network segment of the original

NGN signaling network. The

MediaX3000 interworks SIP signaling

with the SoftX3000 through the

ipmp_sip address.

Media1_sip_test1

media2 media2_sip Media2_sip_test0

Media2_sip_test1

media1 media1_alarm Media1_alarm_te

st0

Seven IP addresses are required.

NOTE Note that the IP addresses must be in the

same network segment of the original

NGN NM network. The MediaX3000

communicates with the NM platform

through the ipmp_alarm address.

Media1_alarm_te

st1

media2 media2_alarm Media2_alarm_test0

Media2_alarm_te

st1

media1 media1_igwb Media1_igwb_tes

t0

Because there is only one iGWB

server, one IP address of charging

network segment is required.

NOTE Note that seven private network IP

addresses in the same user-defined

network segment can be used as the

communication addresses between the

MediaX server and the iGWB. To

standardize data setting, it is

recommended that you can apply for the

charging network segment address of the

original NGN.

media2 media2_igwb Media1_igwb_tes

t1

Media2_igwb_tes

t0

Media2_igwb_tes

t1

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.

2 Planning Data





Issue 02 (2010-09-14)


29/570

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.

NOTEIf 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.

NOTEThere 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-7


30/570

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.

Racks of the same SoftX3000

observe the same numberingscheme. A maximum of 10

racks, ranging from 0 to 9,

can be configured for a

SoftX3000.

ADD SHF

Row number It specifies the position of the

rack in the telecommunica-

tions room.

ADD SHF

Column number

PDB location It specifies the location

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. PDBlocation is set to 2 for the

integrated configuration

cabinet and value 0 for the

service processing cabinet.

ADD SHF

2 Planning Data





Issue 02 (2010-09-14)


31/570


PDB type It specifies whether the -48 V

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.

NOTEWhen the SoftX3000 is used in

Russia and former AIS

countries, it is set to -60V

according to the requirement.

ADD SHF

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

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 expansionsubracks.

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.

ADD FRM





2-9


32/570


Location number The location number

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 subracksin 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.

ADD FRM

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 orOptional

FullConfiguration(Pairs)

Remarks

FCCU Front Mandatory 40 -

IFMI Front Mandatory 4 -

SMUI Front Mandatory - Configured

according to the

default

configuration in

each subrack.

2 Planning Data





Issue 02 (2010-09-14)


33/570

Type Position Mandatory orOptional

FullConfiguration(Pairs)

Remarks

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 - Configuredaccording 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.





2-11


34/570

Board data planning principle

lThe 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

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 evenslots 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.

ADD BRD

2 Planning Data





Issue 02 (2010-09-14)


35/570


Assistant slot number For the boards working in

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 boardsare 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 boardsworking 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.

ADD BRD

2.2.4 Planning the Module Number

Module number planning principle





2-13


36/570

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

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 135l BSGI: 136 to 211

l MSGI: 211 to 136

l MRCA: 212 to 247

ADD BRD

2.3 Planning the Local Office Data

The required data is as follows:

l Switch IDl Local office DN set

l Local DN set

l Country code

l Area code

l National area code

01_initial configuration-(v300r010c03_02).pdf

Documents