SoftX3000 Operation Manual-Configuration Guide

Chapter 1 Overview of Configuration Guide .................................................
1-1
1.1 General Configuration Procedure ...........................................................

1.1.1 Overview of General Configuration Procedure ..............................
1.1.2 Configuring Base Data ...................................................................
1.1.3 Configuring Interconnection Data ..................................................
1.1.4 Configuring Service or Application Service ....................................
1.2 Database Operations .............................................................................
1.2.1 Introduction to Database Operations .............................................
1.2.2 Format Conversion ........................................................................
1.2.3 Online Setting ................................................................................
1.2.4 CRC Check ....................................................................................
1.2.5 Data Transmission .........................................................................
1.2.6 Database Backup...........................................................................
1.2.7 Script Configuration .......................................................................
1.2.8 Batch File Execution ......................................................................
1.2.9 BAM Database Browse ..................................................................
1.3 Notes on Data Configuration ..................................................................
1.3.1 Rules for Setting MML Command Parameters ..............................
1.3.2 Effect of Maximum Number of Tuples on Data Configuration ........
1.3.3 Effect of Software Parameters on Data Configuration ...................
1-1
1-1
1-2
1-3
1-3
1-4
1-4
1-6
1-7
1-8
1-10
1-12
1-14
1-17
1-18
1-19
1-19
1-20
1-21
Chapter 2 Configuring Equipment Information ............................................
2-1
2.1 Related Concepts ...................................................................................

2.1.1 Device Numbering .........................................................................
2.1.2 Module Numbering .........................................................................
2.1.3 Central Database Function ............................................................
2.1.4 Protocol Dispatch Ability ................................................................
2.2 Configuring Equipment Data ..................................................................
2.2.1 Overview ........................................................................................
2.2.2 Adding Shelf ...................................................................................
2.2.3 Adding Frame ................................................................................
2.2.4 Adding Board .................................................................................
2.2.5 Adding FE Port Configuration ........................................................
2.2.6 Adding CDB Function ....................................................................
2.2.7 Setting Dispatch Ability (Optional) .................................................
2.3 Configuring E1 Port and Clock Data ......................................................
2.3.1 Overview ........................................................................................
2.3.2 Adding EPII and CKII Board Data ..................................................
2.3.3 Adding EPII E1 configuration .........................................................
2.3.4 Adding Board Clock Reference Source (Optional) ........................
2-1
2-1
2-4
2-4
2-5
2-6
2-6
2-9
2-10
2-10
2-12
2-13
2-15
2-16
2-16
2-17
2-17
2-18
2.3.5 Setting CKII Clock Configuration ...................................................

2.3.6 Setting Clock Reference Source of EPII (Optional) .......................
2-19
2-20
Chapter 3 Configuring Office Data .................................................................
3-1

3.1.1 Local Office Information .................................................................
3.1.2 Call Source and DN Set .................................................................
3.2 Configuring Office Data ..........................................................................
3.2.1 Overview ........................................................................................
3.2.2 Setting Local Office Information .....................................................
3.2.3 Adding Local Office Signaling Point Code (Optional) ....................
3.2.4 Modifying Local Office Assistant Code (Optional) ..........................
3.2.5 Adding Country or Region Code (Optional) ...................................
3.2.6 Adding National Area Code (Optional) ...........................................
3.2.7 Adding Toll Prefix Description (Optional) .......................................
3.2.8 Adding Local DN Set ......................................................................
3.2.9 Adding Call Source Code...............................................................
3.2.10 Adding Subscriber Number Segment ..........................................
3.2.11 Setting Daylight Saving Time (Optional) ......................................
3-1
3-1
3-1
3-3
3-3
3-6
3-11
3-12
3-14
3-14
3-15
3-16
3-17
3-22
3-23
Chapter 4 Configuring Charging Data ...........................................................
4-1

4.1.1 Charging Concepts ........................................................................
4.1.2 Charging Case and Charging Source Code ..................................
4.1.3 Charging Method ...........................................................................
4.1.4 Trunk Charging ..............................................................................
4.2 Configuring Basic Charging Data ...........................................................
4.2.1 Overview ........................................................................................
4.2.2 Adding Date Category (Optional) ...................................................
4.2.3 Modifying Week Category (Optional) .............................................
4.2.4 Adding Charging Case Analysis ....................................................
4.2.5 Modifying Charging Mode ..............................................................
4.2.6 Adding Intra-office Group Charging ...............................................
4.2.7 Adding Charging Case Index .........................................................
4.2.8 Adding Called Group Charging ......................................................
4.2.9 Adding Supplementary Service Charging ......................................
4.3 Configuring Addition Fee Data ...............................................................
4.3.1 Overview ........................................................................................
4.3.2 Adding Additional Fee Charging Mode (Optional) .........................
4.3.3 Modifying Additional Fee Charging Mode ......................................
4.4 Configuring CRG Charging Data ............................................................
4-1
4-1
4-5
4-6
4-9
4-9
4-9
4-12
4-13
4-14
4-18
4-20
4-21
4-23
4-24
4-25
4-25
4-26
4-27
4-29
4.4.1 Overview ........................................................................................

4.4.2 Configuring Related ISUP Adaptation Data ...................................
4.4.3 Modifying Fixed Software Parameter .............................................
4.4.4 Adding Tariff Indicator (Optional) ...................................................
4.4.5 Adding Time Indicator (Optional) ...................................................
4.4.6 Adding Charging Band ...................................................................
4.4.7 Adding Charging Case Analysis ....................................................
4.4.8 Adding Charging Case Index .........................................................
4.5 Other Charging-related Configurations ..................................................
4.5.1 Modifying Charging Number ..........................................................
4.5.2 Modifying Meter Tariff Rate............................................................
4.5.3 Checking Charging Configuration (Charging Emulation) ...............
4.5.4 Adding Conversation Duration Control ..........................................
4.5.5 Adding Charging Pulse Control......................................................
4.5.6 Adding Charging Case Change .....................................................
4.5.7 Adding charging band number change ..........................................
4.5.8 Adding Caller Charge Failure Processing ......................................
4.5.9 Adding Callee Charge Failure Processing .....................................
4-29
4-30
4-30
4-31
4-32
4-34
4-36
4-36
4-36
4-36
4-37
4-37
4-38
4-40
4-42
4-43
4-45
4-47
Chapter 5 Configuring MG Data .....................................................................
5-1

5.1.1 Types of Media Gateways .............................................................
5.1.2 Media Stream Codec Mode ...........................................................
5.1.3 Gateway Registration Mode ...........................................................
5.2 Configuring Gateway Data .....................................................................
5.2.1 Overview ........................................................................................
5.2.2 Setting MGCP Protocol Parameter (Optional) ...............................
5.2.3 Setting Diffie-Hellman Authentication P Parameter (Optional) ......
5.2.4 Adding Termination ID Layer Configuration (Optional) ..................
5.2.5 Adding Media Gateway ..................................................................
5.2.6 Adding a Multimedia Device ..........................................................
5.2.7 Adding a Batch of Multimedia Devices ..........................................
5.3 Configuring VIG Data .............................................................................
5.3.1 Overview ........................................................................................
5.3.2 Adding VIG .....................................................................................
5.3.3 Adding VIG H.245 Link ..................................................................
5.3.4 Adding VIG Gateway Capabilities ..................................................
5-1
5-1
5-2
5-4
5-5
5-5
5-8
5-9
5-10
5-12
5-22
5-24
5-25
5-25
5-27
5-28
5-30
Chapter 6 Configuring MRS Data ...................................................................
6-1

6.1.1 MRS ...............................................................................................
6-1
6-1
6.1.2 MRS Networking Mode ..................................................................

6.1.3 MRS Voice Categories ...................................................................
6.1.4 Voice File Description ....................................................................
6.2 Configuring Embedded MRS Data .........................................................
6.2.1 Overview ........................................................................................
6.2.2 Adding MRCA Board ......................................................................
6.2.3 Adding MRC Configuration ............................................................
6.2.4 Adding MRP Configuration ............................................................
6.2.5 Adding MRC Voice File ..................................................................
6.2.6 Adding Mapping Relation between Tone ID and Voice File
(Optional) ................................................................................................
6.2.7 Adding Language Zone (Optional) .................................................
6.2.8 Adding Tone ID Configuration (Optional) .......................................
6.2.9 Adding Mapping Relation between Release Cause Value and
Tone ID (Optional) ..................................................................................
6.3 Configuring External MRS Data .............................................................
6.3.1 Overview ........................................................................................
6.3.2 Adding MRS Gateway ....................................................................
6.3.3 Adding MRS Route (Only for MRS6000) .......................................
6.3.4 Adding Mapping between Tone ID and Tone File (Optional) .........
6.3.5 Adding Language Zone (Optional) .................................................
6.3.6 Adding Tone ID Configuration (Optional) .......................................
6.3.7 Adding Mapping between Cause Value and Tone ID (Optional) ...
6-2
6-4
6-5
6-7
6-7
6-10
6-11
6-12
6-15
Chapter 7 Configuring Protocol Data ............................................................
7-1

7.1.1 SIP .................................................................................................
7.1.2 H.323 .............................................................................................
7.2 Configuring SIP Data..............................................................................
7.2.1 Overview ........................................................................................
7.2.2 Setting SIP Global Configuration ...................................................
7.2.3 Setting SIP Local Port ....................................................................
7.3 Configuring H.323 Data ..........................................................................
7.3.1 Overview ........................................................................................
7.3.2 Adding H.323 System Information .................................................
7.3.3 Adding H.323 Application Information ............................................
7.4 Configuring STUN Data ..........................................................................
7.4.1 Overview ........................................................................................
7.4.2 Adding STUN Protocol Dispatch ....................................................
7.4.3 Setting Dispatch Ability ..................................................................
7-1
7-1
7-2
7-4
7-4
7-5
7-7
7-8
7-8
7-9
7-10
7-11
7-11
7-12
7-12
Chapter 8 Configuring Signaling Data ...........................................................
8-1
6-16
6-17
6-18
6-20
6-22
6-22
6-24
6-25
6-25
6-26
6-27
6-29

8.1.1 SIGTRAN .......................................................................................
8.1.2 SS7 ................................................................................................
8.1.3 V5 Interface Protocol .....................................................................
8.1.4 DSS1 ..............................................................................................
8.1.5 Mask ..............................................................................................
8.2 Configuring M2UA Data .........................................................................
8.2.1 Overview ........................................................................................
8.2.2 Adding Embedded Signaling Gateway ..........................................
8.2.3 Adding M2UA Linkset ....................................................................
8.2.4 Adding M2UA Link .........................................................................
8.3 Configuring M3UA Data .........................................................................
8.3.1 Overview ........................................................................................
8.3.2 Adding M3UA Local Entity .............................................................
8.3.3 Adding M3UA Destination Entity ....................................................
8.3.4 Adding M3UA Additional Destination Service (Optional) ...............
8.3.5 Adding M3UA Link Set ...................................................................
8.3.6 Adding M3UA Link .........................................................................
8.3.7 Adding M3UA Route ......................................................................
8.4 Configuring V5UA Data ..........................................................................
8.4.1 Overview ........................................................................................
8.4.3 Adding V5UA Link Set ...................................................................
8.4.4 Adding V5UA Link ..........................................................................
8.5 Configuring IUA Data .............................................................................
8.5.1 Overview ........................................................................................
8.5.3 Adding IUA Link Set .......................................................................
8.5.4 Adding IUA Link .............................................................................
8.6 Configuring MTP Data ............................................................................
8.6.1 Overview ........................................................................................
8.6.2 Adding MTP Destination Signaling Point .......................................
8.6.3 Adding MTP Link Set .....................................................................
8.6.4 Adding MTP Link ............................................................................
8.6.5 Adding MTP Route .........................................................................
8.7 Configuring SCCP Data .........................................................................
8.7.1 Overview ........................................................................................
8.7.2 Adding SCCP Destination Signaling Point .....................................
8.7.3 Adding SCCP Subsystem ..............................................................
8.7.4 Adding SCCP New Global Title (Optional) .....................................
8.7.5 Adding SCCP Global Title (Optional) .............................................
8-2
8-2
8-4
8-7
8-9
8-9
8-11
8-11
8-13
8-14
8-15
8-18
8-18
8-20
8-22
8-25
8-26
8-28
8-31
8-32
8-32
8-34
8-35
8-36
8-39
8-39
8-41
8-42
8-43
8-46
8-46
8-48
8-50
8-52
8-56
8-57
8-57
8-59
8-61
8-63
8-64
8.8 Configuring V5 Interface Data ................................................................

8.8.1 Overview ........................................................................................
8.8.2 Adding V5 Interface .......................................................................
8.8.3 Adding V5 Variant (Optional) .........................................................
8.9 Configuring PRA Link Data ....................................................................
8.9.1 Overview ........................................................................................
8.9.2 Adding PRA Link ............................................................................
8-66
8-66
8-69
8-72
8-74
8-74
8-76
Chapter 9 Configuring Routing Data .............................................................
9-1

9.1.1 Office Direction, Sub-route and Route ...........................................
9.1.2 Route Selection Source Code and Route Selection Code .............
9.1.3 Route Analysis Process .................................................................
9.1.4 Hierarchical Route Networking in NGN..........................................
9.2 Configuring Routing Data .......................................................................
9.2.1 Overview ........................................................................................
9.2.2 Adding Office Direction ..................................................................
9.2.3 Adding Sub-Route ..........................................................................
9.2.4 Adding Route .................................................................................
9.2.5 Adding Time Index (Optional) ........................................................
9.2.6 Adding Route Analysis ...................................................................
9.3 Configuring Location Server Data ..........................................................
9.3.1 Overview ........................................................................................
9.3.2 Adding Location Server..................................................................
9.3.3 Setting Location Server Agent .......................................................
9.3.4 Activating Location Server Link......................................................
9-1
9-1
9-2
9-2
9-4
9-6
9-6
9-9
9-13
9-14
9-17
9-19
9-21
9-21
9-22
9-23
9-25
Chapter 10 Configuring Trunk Data ...............................................................
10-1
10.1 Related Concepts .................................................................................

10.1.1 SIP Trunk .....................................................................................
10.1.2 H.323 Trunk .................................................................................
10.1.3 No. 7 Trunk ..................................................................................
10.1.4 R2 Trunk ......................................................................................
10.1.5 PRA Trunk ...................................................................................
10.1.6 AT0 Trunk ....................................................................................
10.1.7 V5 Trunk ......................................................................................
10.2 Configuring SIP Trunk Data .................................................................
10.2.1 Overview ......................................................................................
10.2.2 Adding SIP Trunk Group ..............................................................
10.3 Configuring H.323 Trunk Data ..............................................................
10.3.1 Overview ......................................................................................
10-2
10-2
10-3
10-6
10-6
10-10
10-10
10-11
10-12
10-12
10-13
10-19
10-19
10.3.2 Adding Virtual IP List (Optional) ................................................... 10-21

10.3.3 Adding H.323 Trunk Group .......................................................... 10-22
10.4 Configuring No. 7 Trunk Data............................................................... 10-27
10.4.1 Overview ...................................................................................... 10-27
10.4.2 Add Carrier Access Code (optional) ............................................ 10-29
10.4.3 Adding Carrier Selection Code (optional) .................................... 10-30
10.4.4 Add Originating Network ID (optional) ......................................... 10-31
10.4.5 Adding No. 7 Trunk Group ........................................................... 10-32
10.4.6 Adding No. 7 Trunk Circuit ........................................................... 10-49
10.4.7 Adding PCM Port (Optional) ........................................................ 10-51
10.5 Configuring R2 Trunk Data ................................................................... 10-52
10.5.1 Overview ...................................................................................... 10-52
10.5.2 Adding R2 Incoming Caller Category Conversion (Optional) ....... 10-55
10.5.3 Adding R2 Outgoing Caller Category Conversion (Optional) ....... 10-56
10.5.4 Adding CAS Signaling Configuration ........................................... 10-57
10.5.5 Adding R2 Trunk Group ............................................................... 10-58
10.5.6 Adding R2 Trunk Circuit ............................................................... 10-73
10.5.7 Adding R2 Trunk Group Tandem (Optional) ................................ 10-76
10.5.8 Adding R2 Trunk Group Caller Number Segment (Optional) ....... 10-78
10.6 Configuring PRA Trunk Data ................................................................ 10-79
10.6.1 Overview ...................................................................................... 10-79
10.6.2 Adding PRA Trunk Group ............................................................ 10-81
10.6.3 Adding PCM Port (Optional) ........................................................ 10-86
10.6.4 Adding PRA Trunk Circuit ............................................................ 10-87
10.7 Configuring AT0 Trunk Data ................................................................. 10-89
10.7.1 Overview ...................................................................................... 10-89
10.7.2 Adding AT0 Trunk Group ............................................................. 10-90
10.7.3 Adding AT0 Trunk Circuit ............................................................. 10-94
10.8 Configuring V5 Trunk Data ................................................................... 10-95
10.8.1 Overview ...................................................................................... 10-95
10.8.2 Adding V5 Trunk Group ............................................................... 10-97
10.8.3 Adding V5 Trunk Circuit ............................................................... 10-98
10.9 Configuring Trunk Group Bearer Data ................................................. 10-100
10.9.1 Overview ...................................................................................... 10-100
10.9.2 Adding TOS Changing Index (Optional) ...................................... 10-101
10.9.3 Adding Trunk Group Bearer ......................................................... 10-102
10.9.4 Adding Trunk Group Bearer Index ............................................... 10-105
10.10 Other Commands ............................................................................... 10-106
10.10.1 Adding Trunk Group Append Configuration ............................... 10-106
10.10.2 Adding Caller Category Transform Index ................................... 10-109
10.10.3 Adding Internal Caller Category Transform ............................... 10-110
Chapter 11 Configuring Number Analysis Data ............................................
11-1

11.1.1 Call Prefix .....................................................................................
11.1.2 Digit Map ......................................................................................
11.1.3 Number Change...........................................................................
11.1.4 Sequence of Number Analysis .....................................................
11.2 Configuring Number Analysis Data ......................................................
11.2.1 Overview ......................................................................................
11.2.2 Modifying Local DN Set (Optional) ...............................................
11.2.3 Adding Called Number Analysis ..................................................
11.3 Other Commands .................................................................................
11.3.1 Setting Prefix Priority (Optional)...................................................
11.3.2 Setting Release Control Mode .....................................................
11.3.3 Adding Cause Code Conversion (Optional) .................................
11.3.4 Adding Preselection Access Code Index (Optional) ....................
11.3.5 Adding Number Change (Optional) ..............................................
11.3.6 Adding Special Called Number Change (Optional) ......................
11.3.7 Adding Caller Number Analysis (Optional) ..................................
11.3.8 Adding Call Prefix Processing (Optional) .....................................
11.3.9 Adding Call Failure Processing (Optional) ...................................
11.3.10 Adding Auxiliary Signaling (Optional) .........................................
11-1
11-1
11-2
11-4
11-7
11-7
11-7
11-11
11-12
11-21
11-21
11-22
11-24
11-25
11-27
11-29
11-31
11-34
11-37
11-40
Chapter 12 Configuring Subscriber Data ......................................................
12-1

12.1.1 Subscriber Terminal Category .....................................................
12.1.2 Identification of Subscriber Line Physical Port .............................
12.1.3 ISDN Subscriber-Network Interface .............................................
12.2 Configuring Ordinary Subscriber Data .................................................
12.2.1 Overview ......................................................................................
12.2.2 Adding a Voice Subscriber ...........................................................
12.2.3 Adding a Batch of Voice Subscribers ...........................................
12.2.4 Adding a Multimedia Subscriber ..................................................
12.2.5 Adding a Batch of Multimedia Subscribers ..................................
12.2.6 Adding a Wide Area Centrex Subscriber .....................................
12.2.7 Adding a Batch of Wide Area Centrex Subscribers .....................
12.3 Configuring ISDN Subscriber Data .......................................................
12.3.1 Overview ......................................................................................
12.3.2 Adding ISDN Data........................................................................
12.3.3 Adding a BRA Subscriber ............................................................
12.3.4 Adding a Batch of BRA Subscribers ............................................
12-1
12-1
12-2
12-4
12-6
12-6
12-9
12-20
12-22
12-24
12-26
12-27
12-28
12-28
12-32
12-33
12-37
12.3.5 Adding a PRA Subscriber ............................................................

12.4 Configuring Other Subscriber Data ......................................................
12.4.1 Adding Multi-Subscriber Number .................................................
12.4.2 Setting String of Anonymous Card Flag.......................................
12-40
12-44
12-44
12-46
Chapter 13 Configuring Centrex Data............................................................
13-1

13.1.1 Centrex Prefix and Centrex Out-Group Prefix .............................
13.1.2 IP Console and IP Supermarket ..................................................
13.2 Configuring Centrex Data .....................................................................
13.2.1 Overview ......................................................................................
13.2.2 Adding Centrex Group .................................................................
13.2.3 Adding Centrex Intra-Group Prefix ...............................................
13.2.4 Adding Centrex Out-Group Prefix (Optional) ...............................
13.2.5 Adding Centrex Prefix Special Processing (Optional)..................
13.2.6 Adding Centrex Intra-Group Charging (Optional) ........................
13.2.7 Adding Centrex Out-Group Authority (Optional) ..........................
13.2.8 Adding Centrex Group Abbreviated Dialing (Optional) ................
13.2.9 Adding Centrex Subscriber Status Subscribing (Optional) ..........
13.2.10 Setting Local IP Address for Controlling Console ......................
13.2.11 Adding IP Console .....................................................................
13.2.12 Adding ISDN Centrex console ...................................................
13.2.13 Modifying Centrex Group (Optional) ..........................................
13-1
13-1
13-2
13-2
13-2
13-6
13-10
13-14
13-15
13-19
13-20
13-21
13-22
13-23
13-24
13-29
13-32
Chapter 14 Configuring Call Barring Data .....................................................
14-1

14.1.1 Caller Number Discrimination ......................................................
14.1.2 Inter-Group Call Barring and Black and White Lists ....................
14.1.3 Time-Based Call Restriction ........................................................
14.1.4 Other Call Restriction Methods ....................................................
14.1.5 Analysis of Number Restriction ....................................................
14.1.6 Applications of Call Barring Data .................................................
14.2 Configuring Call Barring Data...............................................................
14.2.1 Overview ......................................................................................
14.2.2 Modifying Call Source Code ........................................................
14.2.3 Adding Caller Number Discrimination Group ...............................
14.2.4 Adding Trunk Discrimination Group .............................................
14.2.5 Setting Inter-Group Call Barring Indication ..................................
14.2.6 Adding Called Number Barring Group .........................................
14.2.7 Adding Call Timingly Restriction Group .......................................
14-1
14-1
14-2
14-4
14-5
14-5
14-8
14-9
14-9
14-11
14-13
14-18
14-19
14-20
14-22
Chapter 15 Configuring IN Service Data ........................................................
15-1

15.1.1 Architecture of Standard IN ..........................................................
15.1.2 Architecture of Local IN ................................................................
15.1.3 IN Charging Principles .................................................................
15.1.4 Recorded Announcement Message ID ........................................
15.1.5 Naming Conventions for Intelligent Voice Files ...........................
15.2 Configuring IN Charging Data ..............................................................
15.2.1 Overview ......................................................................................
15.2.2 Adding Holiday Tariff Discount (Optional) ....................................
15.2.3 Adding Weekday Tariff Discount (Optional) .................................
15.2.4 Adding Normal Tariff Discount (Optional) ....................................
15.2.5 Adding Conversation Duration Discount (Optional) .....................
15.2.6 Adding Charging Class ................................................................
15.2.7 Adding Charging Property (Optional) ...........................................
15.2.8 Adding Charging Rounding (Optional) .........................................
15.3 Configuring DP Data ............................................................................
15.3.1 Overview ......................................................................................
15.3.2 Setting INAP Protocol Type (Optional) ........................................
15.3.4 Adding Access Code ....................................................................
15.3.5 Adding TDP Configuration ...........................................................
15.3.6 Set DP Trigger Configuration (Optional) ......................................
15.3.7 Add Mapping Between Service Key and Event Code
(Optional) ................................................................................................
15.3.8 Adding IN Service Restriction (Optional) .....................................
15.4 Configuring SCP and SSP Data ...........................................................
15.4.1 Overview ......................................................................................
15.4.2 Adding SCP Physical Address Description ..................................
15.4.3 Adding SSP Physical Address Description ..................................
15.4.4 Adding SCP Configuration ...........................................................
15.4.5 Adding SSP Service Specialized Resource Capability
(Optional) ................................................................................................
15.4.6 Adding SCP Number Mapping (Optional) ....................................
15.5 Configuring SHLR Data ........................................................................
15.5.1 Overview ......................................................................................
15.5.2 Adding SHLR Local Address .......................................................
15.5.3 Adding SHLR Remote Address ...................................................
15.5.4 Adding SHLR Group ....................................................................
15.5.5 Adding SHLR Configuration .........................................................
15.5.6 Adding SHLR Service Configuration (Optional) ...........................
15.6 Configuring SSAP Data ........................................................................
15-2
15-2
15-4
15-6
15-7
15-10
15-12
15-12
15-13
15-16
15-17
15-18
15-19
15-20
15-22
15-23
15-23
15-25
15-26
15-28
15-29
15-33
15-34
15-35
15-37
15-37
15-39
15-41
15-44
15-45
15-45
15-47
15-47
15-48
15-50
15-51
15-52
15-56
15-59
15.6.1 Overview ......................................................................................

15.6.2 Adding INAP over IP ....................................................................
15.6.3 Adding Module Dialog Number ....................................................
15.7 Configuring IN Announcement Data .....................................................
15.7.1 Overview ......................................................................................
15.7.2 Loading IN Voice Files to MRS ....................................................
15.7.3 Adding Language Kind (Optional) ................................................
15.7.4 Adding Language Kind Index .......................................................
15.7.5 Adding Money Category (Optional) ..............................................
15.7.6 Adding Record Announcement Message ID Conversion
(Optional) ................................................................................................
15.7.7 Adding Mapping between Message ID and Tone ID (Optional)...
15.8 Special Configuration Commands ........................................................
15.8.1 Adding IN Service Special Signaling ............................................
15.8.2 Adding Caller Description of Local IN Call ...................................
15.8.3 Adding Network Access Code .....................................................
15-59
15-60
15-61
15-62
15-62
15-64
15-64
15-66
15-67
Chapter 16 Configuring UC Service Data ......................................................
16-1

16.1.1 Architecture of UC System ...........................................................
16.1.2 UC Intelligent Calling Routing ......................................................
16.2 Configuring UC Service Data ...............................................................
16.2.1 Overview ......................................................................................
16.2.2 Adding UC Agent Server ..............................................................
16.2.3 Adding UC Application Server .....................................................
16.2.4 Adding UC Subscriber .................................................................
16.2.5 Adding Workstation ......................................................................
16.2.6 Adding UC Caller Group (Optional) .............................................
16.2.7 Adding UC Date Information (Optional) .......................................
16.2.8 Adding UC Presence Status Data (Optional) ...............................
16.2.9 Setting UC Presence Status Data (Optional) ...............................
16.2.10 Adding UC Profile (Optional)......................................................
16.2.11 Setting UC Profile (Optional)......................................................
16.2.12 Adding UC Intelligent Calling Routing (Optional) .......................
16-1
16-1
16-3
16-4
16-4
16-7
16-9
16-9
16-12
16-12
16-14
16-15
16-16
16-17
16-18
16-18
Chapter 17 Configuring Network Management Data ....................................
17-1
17.1 Background Knowledge .......................................................................

17.1.1 Overview to Network Management Instructions ..........................
17.1.2 Purposes of Network Management Instructions ..........................
17.2 Configuring NM Instructions .................................................................
17.2.1 Adding Originating Destination Code Control ..............................
17.2.2 Adding Outgoing Destination Code Control .................................
17-1
17-1
17-1
17-6
17-6
17-8
15-68
15-69
15-70
15-70
15-71
15-72
17.2.3 Adding Call Gap Control ..............................................................

17.2.4 Adding Circuit Orient Control .......................................................
17.2.5 Adding Circuit Reject Control .......................................................
17.2.6 Adding Direct Route Control ........................................................
17.2.7 Adding Alternative Route Cancellation Control ............................
17.2.8 Adding Temporary Alternative Route Control ..............................
17.2.9 Adding Skip Sub-Route Control ...................................................
17.2.10 Adding Special Record Notification Control ...............................
17.2.11 Adding Trunk Reserved Control .................................................
17.3 HTR Control Instructions ......................................................................
17.3.1 Adding HTR Description ..............................................................
17.3.2 Setting HTR Switch ......................................................................
17.3.3 Removing HTR Control Table Content ........................................
17-9
17-11
17-12
17-13
17-14
17-15
17-17
17-18
17-20
17-21
17-21
17-24
17-24
Chapter 18 Configuring Other Data ...............................................................
18-1

18.1.1 Dual-homing.................................................................................
18.1.2 PBX Service .................................................................................
18.1.3 Videoconferencing Service ..........................................................
18.1.4 NP Service (Hong Kong) ..............................................................
18.2 Configuring Dual-homing Data .............................................................
18.2.1 Overview ......................................................................................
18.2.2 Setting Dual-homing Work Mode .................................................
18.2.3 Adding Dual-homing Heartbeat Configuration .............................
18.3 Configuring PBX Service Data .............................................................
18.3.1 Overview ......................................................................................
18.3.2 Adding PBX Group .......................................................................
18.3.3 Adding PBX Subscriber ...............................................................
18.3.4 Adding PBX Virtual Subscribers ..................................................
18.4 Configuring Videoconferencing Service Data.......................................
18.4.1 Overview ......................................................................................
18.4.2 Adding MCU Configuration ..........................................................
18.4.3 Adding iDo and SMC ...................................................................
18.5 Configuring NP Service Data (Hong Kong) ..........................................
18.5.1 Overview ......................................................................................
18.5.2 Adding NP Server ........................................................................
18.5.3 Adding Connection to NP Server .................................................
18.5.4 Adding Mapping between Network Number and Telephone
Number (Optional) ..................................................................................
18.6 Configuring RACF Card Number ..........................................................
18-1
18-1
18-4
18-5
18-7
18-8
18-8
18-10
18-12
18-13
18-13
18-15
18-17
18-18
18-20
18-20
18-21
18-23
18-24
18-25
18-25
18-27
18-28
18-29
18-30
18.6.1 Overview ......................................................................................

18.6.2 Configuring DP, SCP, and SSP Data ..........................................
18.6.3 Add CSP Service Configuration ...................................................
18.6.4 Adding CSP Service Logic File ....................................................
18.6.5 Activating CSP Service Logic File................................................
18.6.6 Adding CSP Service Module Configuration .................................
18.6.7 Adding RACF Number Segment ..................................................
18.6.8 Adding RACF Number .................................................................
18.7 Configuring Supplementary Service Data ............................................
18.7.1 Modifying Special Tone Configuration .........................................
18.7.2 Adding Service Processing Configuration....................................
18.7.3 Modifying Supplementary Service Analysis .................................
18.7.4 Modifying Supplementary Service Collision Configuration ..........
18.7.5 Modifying Supplementary Service Priority Configuration .............
18.7.6 Adding Call Forwarding Restriction ..............................................
18.7.7 Adding Call Forwarding Data .......................................................
18.7.8 Setting MWN Service Configuration ............................................
18-30
18-30
18-31
18-33
18-34
18-34
18-35
18-36
18-36
18-36
18-37
18-39
18-46
18-47
18-48
18-49
18-50
Appendix A Configuring SNTP Client ............................................................
A-1
A.1 Overview ................................................................................................

A.2 Guide to Data Configuration ..................................................................
A-1
A-3
Appendix B Basic Principles of CRG Charging ............................................
B-1
B.1 Overview ................................................................................................

B.1.1 Basic Concepts..............................................................................
B.1.2 Charging Mode and Charging Process .........................................
B.2 CRG Charging Process .........................................................................
B.2.1 Charging Process of the First Class (CHG/TAC) ..........................
B.2.2 Charging Process of the Second Class (CHB/CHP) .....................
B.2.3 Charging Process of the Third Class (CRG) .................................
B.2.4 Special Cases of the CHP/CRG Charging Modes .........................
B-1
B-1
B-2
B-3
B-3
B-6
B-9
B-10
Appendix C Tone ID .........................................................................................
C-1
Appendix D Acronyms and Abbreviations ....................................................
D-1
HUAWEI
U-SYS SoftX3000 SoftSwitch System

Operation Manual Configuration Guide
V300R003
Huawei Technologies Proprietary

Operation Manual
Volume
Configuration Guide
Manual Version
T2-011627-20050331-C-3.30
Product Version
V300R003
BOM
31161627
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support
and service. Please feel free to contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address: Administration Building, Huawei Technologies Co., Ltd.,
Bantian, Longgang District, Shenzhen, P. R. China
Postal Code: 518129
Website: http://www.huawei.com
Email: support@huawei.com
Copyright 2005 Huawei Technologies Co., Ltd.
All Rights Reserved

No part of this manual may be reproduced or transmitted in any form or by any
means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks
, HUAWEI, C&C08, EAST8000, HONET,
, ViewPoint, INtess, ETS, DMC,
TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium,

M900/M1800,
TELESIGHT, Quidview, Musa, Airbridge, Tellwin, Inmedia, VRP, DOPRA, iTELLIN,
HUAWEI OptiX, C&C08 iNET, NETENGINE, OptiX, iSite, U-SYS, iMUSE, OpenEye,
Lansway, SmartAX, infoX, and TopEng are trademarks of Huawei Technologies
Co., Ltd.
All other trademarks and trade names mentioned in this manual are the property of
their respective holders.
Notice
The information in this manual is subject to change without notice. Every effort has
been made in the preparation of this manual to ensure accuracy of the contents, but
all statements, information, and recommendations in this manual do not constitute
the warranty of any kind, express or implied.
About This Manual

Release Notes
This manual applies to U-SYS SoftX3000 SoftSwitch System V300R003 (hereinafter
referred to as SoftX3000).
Related Manuals
The related manuals are listed in the following table.
Manual
Content
U-SYS SoftX3000 SoftSwitch

System Technical
Manual-System Description
It provides an overall introduction to the

SoftX3000, including product features,
applications, and technical specifications.

System Technical
Manual-System Principle
It details on the hardware architecture,

component interworking mechanism, and
subsystems of alarm, billing, and clock in the
SoftX3000.

System Hardware Description
Manual
It details the features and technical

specifications of the hardware components of
the SoftX3000, including cabinets, frames,
boards, cables, and cabinet internal
components.

System Technical
ManualServices and Features
It covers various services and functions

supported by the SoftX3000, including voice
services, supplementary services, IP Centrex
services, multi-media services, value added
services, dual homing functions, charging
functions, IPTN functions, remote network
access functions, and so on.

System Hardware Installation
Manual
It details the installation procedure of the

SoftX3000 hardware components, and matters
needing attention during the installation
process.

System Software Installation
Manual
It covers the detailed procedure of installing the

SoftX3000 software, including BAM server,
emergency workstation, and client, focusing on
the key points that might cause installation
failure.

System Routine Maintenance
Guide
It guides the maintenance engineers to perform

daily maintenance, monthly maintenance, and
yearly maintenance tasks on the SoftX3000.
Manual
Content

System Emergency
Maintenance Manual
It guides the maintenance engineers to perform

recovery operations in the case of emergencies,
such as congestion of global service, AMG, and
TMG, and failure of host and BAM.

System Part Replacement Guide
It guides the maintenance engineers on how to

replace hardware components of the
SoftX3000, such as boards, fan frame, LAN
Switch, and hard disk.

System Operation
Manual-Configuration Guide
It guides the engineers how to configure various

data in the SoftX3000, including configuration
steps, preparations, database table referencing
relationships, and command parameters.

System Operation
Manual-Configuration Examples
It guides the engineers how to configure various

data in the SoftX3000, including networking
example, configuration script, key parameters
and debugging guidance.

System Operation
Manual-Performance
Measurement
It guides the engineers how to work on

performance measurement tasks and analyze
measurement results.

System Operation Manual-GUI
Guide
It guides the engineers how to use the GUI on

various clients of the SoftX3000, including
operations on menus and navigation tree. In
addition, it introduces the operations on
TableBrowse.

System BAM User Manual
It guides the engineers how to install and use

the software related to the BAM, including
remote maintenance software, anti-virus
software, system customized software, and so
on.
U-SYS iGateway Bill User

Manual
It elaborates on the functioning principle of the

iGateway Bill. Also, it teaches you on how to
install, maintain, and operate the product.
Organization
The manual explains how to configure various data in U-SYS SoftX3000 SoftSwitch
System.
z
Chapter 1 Overview of Configuration Guide is a brief introduction to the data

configuration in SoftX3000, such as general principles for the data configuration, a
general data configuration process, basic operations, and necessary attentions.
Chapter 2 Configuring Equipment Information provides steps for configuring

equipment information of SoftX3000 such as racks, frames, and boards.
Chapter 3 Configuring Office Data explains how to configure local office data
including signaling point code, country/region code, toll area code, local DN set,
global DN set, and call source.
Chapter 4 Configuring Charging Data teaches how to configure ordinary

charge-related data.
Chapter 5 Configuring MG Data introduces how to configure various media

gateways including integrated access device, access media gateway, trunk media
gateway, universal media gateway, and multimedia gateway.
Chapter 6 Configuring MRS Data provides detailed steps for configuring

resource data regarding an embedded media resource server or a physically
separate media resource server.
Chapter 7 Configuring Protocol Data details how to configure protocol related

data such as Session Initiation Protocol (SIP), H.323, and Simple Traversal of
UDP Through Network Address Translators (STUN).
Chapter 8 Configuring Signaling Data describes in detail how to configure

signaling-related data such as Message Transfer Part 2-User Adaptation Layer
(M2UA), Message Transfer Part 3-User Adaptation Layer (M3UA), V5.2-User
Adaptation Layer (V5UA), ISDN Q.921-User Adaptation Layer (IUA), Message
Transfer Part (MTP), Signaling Connection and Control Part (SCCP), V5 interface,
and Primary Rate Access (PRA).
Chapter 9 Configuring Routing Data provides detailed steps for configuring

static routing data.
Chapter 10 Configuring Trunk Data explains how to configure trunk-related data

such as No. 7 trunk, R2 trunk, SIP trunk, H.323 trunk, V5 trunk, and PRA trunk.
Chapter 11 Configuring Number Analysis Data teaches how to configure call

prefix, number change, release mode, number initial processing, and failure
processing.
Chapter 12 Configuring Subscriber Data covers configuration steps regarding

ordinary subscribers and ISDN subscribers.
Chapter 13 Configuring Centrex Data explains how to configure a Centrex

group, Centrex subscribers, and an IP console.
Chapter 14 Configuring Call Barring Data covers configuration steps regarding

number discrimination, black and white lists, inter-group call barring relationship,
and network management commands.
Chapter 15 Configuring IN Service Data details how to configure Intelligent

Network (IN) service data, such as IN charging data, Detection Point (DP) data,
Service Control Point (SCP) data, Service Switching Point (SSP) data, and
recorded announcements.
Chapter 16 Configuring UC Service Data presents steps for configuring the

Unified Communication (UC) service.
Chapter 17 Configuring Network Management Data details how to configure

NM instructions.
Chapter 18 Configuring Other Data provides configuration steps regarding
Private Branch Exchange (PBX) service, videoconferencing service and dual

homing data.
Appendix A Configuring SNTP Client presents how to configure Simple
Network Time Protocol (SNTP) client.

Appendix B Basic Principles of CRG Charging elaborates the basic principle
and processing of CRG charging.

Appendix C Tone ID introduces the parameter values and meanings of the signal
tone IDs and supplementary service tone IDs that are supported by SoftX3000.
Appendix D Acronyms and Abbreviations lists frequently used acronyms and
abbreviations as well as their full names in this manual..
Intended Audience
The manual is intended for the following readers:
z
NGN engineering specialist
NGN operation & maintenance personnel
NGN network planning experts
Conventions
The manual uses the following conventions:
I. General conventions
Convention
Description
Arial
Normal paragraphs are in Arial.
Boldface
Headings are in Boldface.
Courier New
Terminal Display is in Courier New.
II. Command conventions

Convention
Description
Boldface
The keywords of a command line are in Boldface.
italic
Command arguments are in italic.
[]
Items (keywords or arguments) in square brackets [ ] are

optional.
{ x | y | ... }
Alternative items are grouped in braces and separated by

vertical bars. One is selected.
Convention
Description
[ x | y | ... ]
Optional alternative items are grouped in square brackets

and separated by vertical bars. One or none is selected.
{ x | y | ... } *
Alternative items are grouped in braces and separated by

vertical bars. A minimum of one or a maximum of all can be
selected.
[ x | y | ... ] *
Optional alternative items are grouped in square brackets

and separated by vertical bars. Many or none can be
selected.
III. GUI conventions

Convention
Description
<>
Button names are inside angle brackets. For example, click

the <OK> button.
[]
Window names, menu items, data table and field names

are inside square brackets. For example, pop up the [New
User] window.
Multi-level menus are separated by forward slashes. For

example, [File/Create/Folder].
IV. Keyboard operation

Format
Description
<Key>
Press the key with the key name inside angle brackets. For
example, <Enter>, <Tab>, <Backspace>, or <A>.
<Key1+Key2>
Press the keys concurrently. For example, <Ctrl+Alt+A>

means the three keys should be pressed concurrently.
<Key1, Key2>
Press the keys in turn. For example, <Alt, A> means the
two keys should be pressed in turn.
V. Mouse operation
Action
Description
Click
Press the left button or right button quickly (left button by

default).
Double Click
Press the left button twice continuously and quickly.
Drag
Press and hold the left button and drag it to a certain

position.
VI. Symbols
Eye-catching symbols are also used in the manual to highlight the points worthy of
special attention during the operation. They are defined as follows:
Caution, Warning, Danger: Means reader be extremely careful during the

operation.
Note, Comment, Tip, Knowhow, Thought: Means a complementary description
Operation Manual - Configuration Guide

Table of Contents
Table of Contents
Chapter 1 Overview of Configuration Guide .............................................................................. 1-1
1.1 General Configuration Procedure ...................................................................................... 1-1
1.1.1 Overview of General Configuration Procedure ....................................................... 1-1
1.1.2 Configuring Base Data ............................................................................................ 1-2
1.1.3 Configuring Interconnection Data............................................................................ 1-3
1.1.4 Configuring Service or Application Service............................................................. 1-3
1.2 Database Operations......................................................................................................... 1-4
1.2.1 Introduction to Database Operations ...................................................................... 1-4
1.2.2 Format Conversion.................................................................................................. 1-6
1.2.3 Online Setting.......................................................................................................... 1-7
1.2.4 CRC Check ............................................................................................................. 1-8
1.2.5 Data Transmission ................................................................................................ 1-10
1.2.6 Database Backup .................................................................................................. 1-12
1.2.7 Script Configuration............................................................................................... 1-14
1.2.8 Batch File Execution ............................................................................................. 1-17
1.2.9 BAM Database Browse ......................................................................................... 1-18
1.3 Notes on Data Configuration ........................................................................................... 1-19
1.3.1 Rules for Setting MML Command Parameters ..................................................... 1-19
1.3.2 Effect of Maximum Number of Tuples on Data Configuration .............................. 1-20
1.3.3 Effect of Software Parameters on Data Configuration .......................................... 1-21
Chapter 2 Configuring Equipment Information.......................................................................... 2-1
2.1 Related Concepts .............................................................................................................. 2-1
2.1.1 Device Numbering................................................................................................... 2-1
2.1.2 Module Numbering.................................................................................................. 2-4
2.1.3 Central Database Function ..................................................................................... 2-4
2.1.4 Protocol Dispatch Ability ......................................................................................... 2-5
2.2 Configuring Equipment Data.............................................................................................. 2-6
2.2.1 Overview ................................................................................................................. 2-6
2.2.2 Adding Shelf ............................................................................................................ 2-9
2.2.3 Adding Frame........................................................................................................ 2-10
2.2.4 Adding Board......................................................................................................... 2-10
2.2.5 Adding FE Port Configuration ............................................................................... 2-12
2.2.6 Adding CDB Function............................................................................................ 2-13
2.2.7 Setting Dispatch Ability (Optional)......................................................................... 2-15
2.3 Configuring E1 Port and Clock Data................................................................................ 2-16
2.3.1 Overview ............................................................................................................... 2-16
2.3.2 Adding EPII and CKII Board Data ......................................................................... 2-17

i

Table of Contents
2.3.3 Adding EPII E1 configuration ................................................................................ 2-17

2.3.4 Adding Board Clock Reference Source (Optional) ............................................... 2-18
2.3.5 Setting CKII Clock Configuration........................................................................... 2-19
2.3.6 Setting Clock Reference Source of EPII (Optional) .............................................. 2-20
Chapter 3 Configuring Office Data .............................................................................................. 3-1
3.1.1 Local Office Information .......................................................................................... 3-1
3.1.2 Call Source and DN Set .......................................................................................... 3-1
3.2 Configuring Office Data ..................................................................................................... 3-3
3.2.1 Overview ................................................................................................................. 3-3
3.2.2 Setting Local Office Information .............................................................................. 3-6
3.2.3 Adding Local Office Signaling Point Code (Optional) ........................................... 3-11
3.2.4 Modifying Local Office Assistant Code (Optional)................................................. 3-12
3.2.5 Adding Country or Region Code (Optional) .......................................................... 3-14
3.2.6 Adding National Area Code (Optional).................................................................. 3-14
3.2.7 Adding Toll Prefix Description (Optional) .............................................................. 3-15
3.2.8 Adding Local DN Set............................................................................................. 3-16
3.2.9 Adding Call Source Code...................................................................................... 3-17
3.2.10 Adding Subscriber Number Segment ................................................................. 3-22
3.2.11 Setting Daylight Saving Time (Optional) ............................................................. 3-23
Chapter 4 Configuring Charging Data......................................................................................... 4-1
4.1.1 Charging Concepts ................................................................................................. 4-1
4.1.2 Charging Case and Charging Source Code ........................................................... 4-5
4.1.3 Charging Method..................................................................................................... 4-6
4.1.4 Trunk Charging........................................................................................................ 4-9
4.2 Configuring Basic Charging Data ...................................................................................... 4-9
4.2.1 Overview ................................................................................................................. 4-9
4.2.2 Adding Date Category (Optional) .......................................................................... 4-12
4.2.3 Modifying Week Category (Optional) .................................................................... 4-13
4.2.4 Adding Charging Case Analysis............................................................................ 4-14
4.2.5 Modifying Charging Mode ..................................................................................... 4-18
4.2.6 Adding Intra-office Group Charging ...................................................................... 4-20
4.2.7 Adding Charging Case Index ................................................................................ 4-21
4.2.8 Adding Called Group Charging ............................................................................. 4-23
4.2.9 Adding Supplementary Service Charging ............................................................. 4-24
4.3 Configuring Addition Fee Data......................................................................................... 4-25
4.3.1 Overview ............................................................................................................... 4-25
4.3.2 Adding Additional Fee Charging Mode (Optional) ................................................ 4-26
4.3.3 Modifying Additional Fee Charging Mode ............................................................. 4-27
4.4 Configuring CRG Charging Data ..................................................................................... 4-29
4.4.1 Overview ............................................................................................................... 4-29
ii

Table of Contents
4.4.2 Configuring Related ISUP Adaptation Data .......................................................... 4-30

4.4.3 Modifying Fixed Software Parameter .................................................................... 4-30
4.4.4 Adding Tariff Indicator (Optional) .......................................................................... 4-31
4.4.5 Adding Time Indicator (Optional) .......................................................................... 4-32
4.4.6 Adding Charging Band .......................................................................................... 4-34
4.4.7 Adding Charging Case Analysis............................................................................ 4-36
4.4.8 Adding Charging Case Index ................................................................................ 4-36
4.5 Other Charging-related Configurations............................................................................ 4-36
4.5.1 Modifying Charging Number ................................................................................. 4-36
4.5.2 Modifying Meter Tariff Rate................................................................................... 4-37
4.5.3 Checking Charging Configuration (Charging Emulation) ...................................... 4-37
4.5.4 Adding Conversation Duration Control ................................................................. 4-38
4.5.5 Adding Charging Pulse Control............................................................................. 4-40
4.5.6 Adding Charging Case Change ............................................................................ 4-42
4.5.7 Adding charging band number change ................................................................. 4-43
4.5.8 Adding Caller Charge Failure Processing............................................................. 4-45
4.5.9 Adding Callee Charge Failure Processing ............................................................ 4-47
Chapter 5 Configuring MG Data................................................................................................... 5-1
5.1.1 Types of Media Gateways....................................................................................... 5-1
5.1.2 Media Stream Codec Mode .................................................................................... 5-2
5.1.3 Gateway Registration Mode.................................................................................... 5-4
5.2 Configuring Gateway Data................................................................................................. 5-5
5.2.1 Overview ................................................................................................................. 5-5
5.2.2 Setting MGCP Protocol Parameter (Optional) ........................................................ 5-8
5.2.3 Setting Diffie-Hellman Authentication P Parameter (Optional) ............................... 5-9
5.2.4 Adding Termination ID Layer Configuration (Optional) ......................................... 5-10
5.2.5 Adding Media Gateway ......................................................................................... 5-12
5.2.6 Adding a Multimedia Device.................................................................................. 5-22
5.2.7 Adding a Batch of Multimedia Devices ................................................................. 5-24
5.3 Configuring VIG Data....................................................................................................... 5-25
5.3.1 Overview ............................................................................................................... 5-25
5.3.2 Adding VIG ............................................................................................................ 5-27
5.3.3 Adding VIG H.245 Link.......................................................................................... 5-28
5.3.4 Adding VIG Gateway Capabilities ......................................................................... 5-30
Chapter 6 Configuring MRS Data................................................................................................. 6-1
6.1.1 MRS ........................................................................................................................ 6-1
6.1.2 MRS Networking Mode ........................................................................................... 6-2
6.1.3 MRS Voice Categories............................................................................................ 6-4
6.1.4 Voice File Description ............................................................................................. 6-5
6.2 Configuring Embedded MRS Data .................................................................................... 6-7
iii

Table of Contents
6.2.1 Overview ................................................................................................................. 6-7

6.2.2 Adding MRCA Board............................................................................................. 6-10
6.2.3 Adding MRC Configuration ................................................................................... 6-11
6.2.4 Adding MRP Configuration.................................................................................... 6-12
6.2.5 Adding MRC Voice File ......................................................................................... 6-15
6.2.6 Adding Mapping Relation between Tone ID and Voice File (Optional)................. 6-16
6.2.7 Adding Language Zone (Optional) ........................................................................ 6-17
6.2.8 Adding Tone ID Configuration (Optional).............................................................. 6-18
6.2.9 Adding Mapping Relation between Release Cause Value and Tone ID (Optional)6-20
6.3 Configuring External MRS Data....................................................................................... 6-22
6.3.1 Overview ............................................................................................................... 6-22
6.3.2 Adding MRS Gateway........................................................................................... 6-24
6.3.3 Adding MRS Route (Only for MRS6000) .............................................................. 6-25
6.3.4 Adding Mapping between Tone ID and Tone File (Optional)................................ 6-25
6.3.5 Adding Language Zone (Optional) ........................................................................ 6-26
6.3.6 Adding Tone ID Configuration (Optional).............................................................. 6-27
6.3.7 Adding Mapping between Cause Value and Tone ID (Optional) .......................... 6-29
Chapter 7 Configuring Protocol Data .......................................................................................... 7-1
7.1.1 SIP........................................................................................................................... 7-1
7.1.2 H.323....................................................................................................................... 7-2
7.2 Configuring SIP Data ......................................................................................................... 7-4
7.2.1 Overview ................................................................................................................. 7-4
7.2.2 Setting SIP Global Configuration ............................................................................ 7-5
7.2.3 Setting SIP Local Port ............................................................................................. 7-7
7.3 Configuring H.323 Data ..................................................................................................... 7-8
7.3.1 Overview ................................................................................................................. 7-8
7.3.2 Adding H.323 System Information .......................................................................... 7-9
7.3.3 Adding H.323 Application Information................................................................... 7-10
7.4 Configuring STUN Data ................................................................................................... 7-11
7.4.1 Overview ............................................................................................................... 7-11
7.4.2 Adding STUN Protocol Dispatch ........................................................................... 7-12
7.4.3 Setting Dispatch Ability ......................................................................................... 7-12
Chapter 8 Configuring Signaling Data ........................................................................................ 8-1
8.1.1 SIGTRAN ................................................................................................................ 8-2
8.1.2 SS7.......................................................................................................................... 8-4
8.1.3 V5 Interface Protocol............................................................................................... 8-7
8.1.4 DSS1 ....................................................................................................................... 8-9
8.1.5 Mask........................................................................................................................ 8-9
8.2 Configuring M2UA Data................................................................................................... 8-11
8.2.1 Overview ............................................................................................................... 8-11
iv

Table of Contents
8.2.2 Adding Embedded Signaling Gateway ................................................................. 8-13

8.2.3 Adding M2UA Linkset............................................................................................ 8-14
8.2.4 Adding M2UA Link ................................................................................................ 8-15
8.3 Configuring M3UA Data................................................................................................... 8-18
8.3.1 Overview ............................................................................................................... 8-18
8.3.2 Adding M3UA Local Entity .................................................................................... 8-20
8.3.3 Adding M3UA Destination Entity ........................................................................... 8-22
8.3.4 Adding M3UA Additional Destination Service (Optional) ...................................... 8-25
8.3.5 Adding M3UA Link Set .......................................................................................... 8-26
8.3.6 Adding M3UA Link ................................................................................................ 8-28
8.3.7 Adding M3UA Route ............................................................................................. 8-31
8.4 Configuring V5UA Data ................................................................................................... 8-32
8.4.1 Overview ............................................................................................................... 8-32
8.4.3 Adding V5UA Link Set........................................................................................... 8-35
8.4.4 Adding V5UA Link ................................................................................................. 8-36
8.5 Configuring IUA Data....................................................................................................... 8-39
8.5.1 Overview ............................................................................................................... 8-39
8.5.3 Adding IUA Link Set .............................................................................................. 8-42
8.5.4 Adding IUA Link..................................................................................................... 8-43
8.6 Configuring MTP Data ..................................................................................................... 8-46
8.6.1 Overview ............................................................................................................... 8-46
8.6.2 Adding MTP Destination Signaling Point .............................................................. 8-48
8.6.3 Adding MTP Link Set ............................................................................................ 8-50
8.6.4 Adding MTP Link ................................................................................................... 8-52
8.6.5 Adding MTP Route................................................................................................ 8-56
8.7 Configuring SCCP Data................................................................................................... 8-57
8.7.1 Overview ............................................................................................................... 8-57
8.7.2 Adding SCCP Destination Signaling Point............................................................ 8-59
8.7.3 Adding SCCP Subsystem ..................................................................................... 8-61
8.7.4 Adding SCCP New Global Title (Optional)............................................................ 8-63
8.7.5 Adding SCCP Global Title (Optional) .................................................................... 8-64
8.8 Configuring V5 Interface Data ......................................................................................... 8-66
8.8.1 Overview ............................................................................................................... 8-66
8.8.2 Adding V5 Interface............................................................................................... 8-69
8.8.3 Adding V5 Variant (Optional) ................................................................................ 8-72
8.9 Configuring PRA Link Data.............................................................................................. 8-74
8.9.1 Overview ............................................................................................................... 8-74
8.9.2 Adding PRA Link ................................................................................................... 8-76
Chapter 9 Configuring Routing Data ........................................................................................... 9-1
v

Table of Contents
9.1.1 Office Direction, Sub-route and Route .................................................................... 9-1

9.1.2 Route Selection Source Code and Route Selection Code ..................................... 9-2
9.1.3 Route Analysis Process .......................................................................................... 9-2
9.1.4 Hierarchical Route Networking in NGN................................................................... 9-4
9.2 Configuring Routing Data .................................................................................................. 9-6
9.2.1 Overview ................................................................................................................. 9-6
9.2.2 Adding Office Direction ........................................................................................... 9-9
9.2.3 Adding Sub-Route................................................................................................. 9-13
9.2.4 Adding Route......................................................................................................... 9-14
9.2.5 Adding Time Index (Optional) ............................................................................... 9-17
9.2.6 Adding Route Analysis .......................................................................................... 9-19
9.3 Configuring Location Server Data.................................................................................... 9-21
9.3.1 Overview ............................................................................................................... 9-21
9.3.2 Adding Location Server......................................................................................... 9-22
9.3.3 Setting Location Server Agent .............................................................................. 9-23
9.3.4 Activating Location Server Link............................................................................. 9-25
Chapter 10 Configuring Trunk Data........................................................................................... 10-1
10.1 Related Concepts .......................................................................................................... 10-2
10.1.1 SIP Trunk ............................................................................................................ 10-2
10.1.2 H.323 Trunk......................................................................................................... 10-3
10.1.3 No. 7 Trunk.......................................................................................................... 10-6
10.1.4 R2 Trunk.............................................................................................................. 10-6
10.1.5 PRA Trunk......................................................................................................... 10-10
10.1.6 AT0 Trunk.......................................................................................................... 10-10
10.1.7 V5 Trunk............................................................................................................ 10-11
10.2 Configuring SIP Trunk Data......................................................................................... 10-12
10.2.1 Overview ........................................................................................................... 10-12
10.2.2 Adding SIP Trunk Group ................................................................................... 10-13
10.3 Configuring H.323 Trunk Data ..................................................................................... 10-20
10.3.1 Overview ........................................................................................................... 10-20
10.3.2 Adding H.323 Trunk Group ............................................................................... 10-21
10.4 Configuring No. 7 Trunk Data ...................................................................................... 10-26
10.4.1 Overview ........................................................................................................... 10-26
10.4.2 Adding Carrier Selection Code (optional) ......................................................... 10-28
10.4.3 Add Originating Network ID (optional) .............................................................. 10-29
10.4.4 Add Carrier Access Code (optional) ................................................................. 10-30
10.4.5 Adding No. 7 Trunk Group ................................................................................ 10-30
10.4.6 Adding No. 7 Trunk Group Append................................................................... 10-46
10.4.7 Adding No. 7 Trunk Circuit ................................................................................ 10-48
10.4.8 Adding PCM Port (Optional).............................................................................. 10-49
10.5 Configuring R2 Trunk Data .......................................................................................... 10-51
10.5.1 Overview ........................................................................................................... 10-51
vi

Table of Contents
10.5.2 Adding R2 Incoming Caller Category Conversion (Optional) ........................... 10-53

10.5.3 Adding R2 Outgoing Caller Category Conversion (Optional) ........................... 10-54
10.5.4 Adding CAS Signaling Configuration ................................................................ 10-55
10.5.5 Adding R2 Trunk Group .................................................................................... 10-57
10.5.6 Adding R2 Trunk Circuit .................................................................................... 10-72
10.5.7 Adding R2 Trunk Group Tandem (Optional) ..................................................... 10-74
10.6 Configuring PRA Trunk Data ....................................................................................... 10-76
10.6.1 Overview ........................................................................................................... 10-76
10.6.2 Adding PRA Trunk Group ................................................................................. 10-78
10.6.3 Adding PCM Port (Optional).............................................................................. 10-84
10.6.4 Adding PRA Trunk Circuit ................................................................................. 10-85
10.7 Configuring AT0 Trunk Data ........................................................................................ 10-86
10.7.1 Overview ........................................................................................................... 10-86
10.7.2 Adding AT0 Trunk Group .................................................................................. 10-88
10.7.3 Adding AT0 Trunk Circuit .................................................................................. 10-91
10.8 Configuring V5 Trunk Data .......................................................................................... 10-92
10.8.1 Overview ........................................................................................................... 10-92
10.8.2 Adding V5 Trunk Group .................................................................................... 10-94
10.8.3 Adding V5 Trunk Circuit .................................................................................... 10-95
10.9 Configuring Trunk Group Bearer Data......................................................................... 10-96
10.9.1 Overview ........................................................................................................... 10-96
10.9.2 Adding TOS Changing Index (Optional) ........................................................... 10-98
10.9.3 Adding Trunk Group Bearer .............................................................................. 10-99
10.9.4 Adding Trunk Group Bearer Index .................................................................. 10-102
10.10 Other Commands .................................................................................................... 10-103
10.10.1 Adding Charging Change.............................................................................. 10-103
10.10.2 Adding Trunk Group Caller Number Segment .............................................. 10-104
10.10.3 Adding Part Calling Line Identification .......................................................... 10-105
Chapter 11 Configuring Number Analysis Data ....................................................................... 11-1
11.1.1 Call Prefix ............................................................................................................ 11-1
11.1.2 Digit Map ............................................................................................................. 11-2
11.1.3 Number Change .................................................................................................. 11-4
11.1.4 Sequence of Number Analysis............................................................................ 11-7
11.2 Configuring Number Analysis Data................................................................................ 11-7
11.2.1 Overview ............................................................................................................. 11-7
11.2.2 Modifying Local DN Set (Optional).................................................................... 11-11
11.2.3 Adding Called Number Analysis........................................................................ 11-12
11.3 Other Commands ........................................................................................................ 11-23
11.3.1 Setting Prefix Priority (Optional)........................................................................ 11-23
11.3.2 Setting Release Control Mode .......................................................................... 11-24
vii

Table of Contents
11.3.3 Adding Cause Code Conversion (Optional)...................................................... 11-26

11.3.4 Adding Preselection Access Code Index (Optional) ......................................... 11-27
11.3.5 Adding Number Change (Optional)................................................................... 11-29
11.3.6 Adding Special Called Number Change (Optional)........................................... 11-30
11.3.7 Adding Caller Number Analysis (Optional) ....................................................... 11-32
11.3.8 Adding Call Prefix Processing (Optional).......................................................... 11-36
11.3.9 Adding Call Failure Processing (Optional) ........................................................ 11-39
11.3.10 Adding Auxiliary Signaling (Optional).............................................................. 11-42
11.3.11 Adding Caller Category Transform Index (Optional)....................................... 11-44
11.3.12 Adding Internal Caller Category Transform (Optional) ................................... 11-45
Chapter 12 Configuring Subscriber Data.................................................................................. 12-1
12.1.1 Subscriber Terminal Category ............................................................................ 12-1
12.1.2 Identification of Subscriber Line Physical Port.................................................... 12-2
12.1.3 ISDN Subscriber-Network Interface .................................................................... 12-4
12.2 Configuring Ordinary Subscriber Data........................................................................... 12-6
12.2.1 Overview ............................................................................................................. 12-6
12.2.2 Adding a Voice Subscriber.................................................................................. 12-9
12.2.3 Adding a Batch of Voice Subscribers................................................................ 12-19
12.2.4 Adding a Multimedia Subscriber ....................................................................... 12-21
12.2.5 Adding a Batch of Multimedia Subscribers ....................................................... 12-23
12.2.6 Adding a Wide Area Centrex Subscriber .......................................................... 12-25
12.2.7 Adding a Batch of Wide Area Centrex Subscribers .......................................... 12-27
12.3 Configuring ISDN Subscriber Data .............................................................................. 12-28
12.3.1 Overview ........................................................................................................... 12-28
12.3.2 Adding ISDN Data............................................................................................. 12-31
12.3.3 Adding a BRA Subscriber ................................................................................. 12-32
12.3.4 Adding a Batch of BRA Subscribers ................................................................. 12-36
12.3.5 Adding a PRA Subscriber ................................................................................. 12-39
12.4 Configuring Other Subscriber Data.............................................................................. 12-43
12.4.1 Adding Multi-Subscriber Number ...................................................................... 12-43
12.4.2 Setting String of Anonymous Card Flag............................................................ 12-44
Chapter 13 Configuring Centrex Data ....................................................................................... 13-1
13.1.1 Centrex Prefix and Centrex Out-Group Prefix .................................................... 13-1
13.1.2 IP Console and IP Supermarket.......................................................................... 13-2
13.2 Configuring Centrex Data .............................................................................................. 13-2
13.2.1 Overview ............................................................................................................. 13-2
13.2.2 Adding Centrex Group ........................................................................................ 13-6
13.2.3 Adding Centrex Intra-Group Prefix.................................................................... 13-10
13.2.4 Adding Centrex Out-Group Prefix (Optional) .................................................... 13-14
13.2.5 Adding Centrex Prefix Special Processing (Optional)....................................... 13-15
viii

Table of Contents
13.2.6 Adding Centrex Intra-Group Charging (Optional) ............................................. 13-19

13.2.7 Adding Centrex Out-Group Authority (Optional) ............................................... 13-20
13.2.8 Adding Centrex Group Abbreviated Dialing (Optional) ..................................... 13-21
13.2.9 Adding Centrex Subscriber Status Subscribing (Optional) ............................... 13-22
13.2.10 Setting Local IP Address for Controlling Console ........................................... 13-23
13.2.11 Adding IP Console .......................................................................................... 13-24
13.2.12 Adding ISDN Centrex console ........................................................................ 13-29
13.2.13 Modifying Centrex Group (Optional) ............................................................... 13-32
Chapter 14 Configuring Call Barring Data ................................................................................ 14-1
14.1.1 Caller Number Discrimination ............................................................................. 14-1
14.1.2 Inter-Group Call Barring and Black and White Lists ........................................... 14-2
14.1.3 Time-Based Call Restriction................................................................................ 14-4
14.1.4 Other Call Restriction Methods ........................................................................... 14-4
14.1.5 Analysis of Number Restriction ........................................................................... 14-5
14.1.6 Applications of Call Barring Data ........................................................................ 14-7
14.2 Configuring Call Barring Data ........................................................................................ 14-8
14.2.1 Overview ............................................................................................................. 14-8
14.2.2 Modifying Call Source Code.............................................................................. 14-10
14.2.3 Adding Caller Number Discrimination Group .................................................... 14-13
14.2.4 Adding Trunk Discrimination Group .................................................................. 14-16
14.2.5 Setting Inter-Group Call Barring Indication ....................................................... 14-18
14.2.6 Adding Called Number Barring Group .............................................................. 14-19
14.2.7 Adding Call Timingly Restriction Group ............................................................ 14-21
Chapter 15 Configuring IN Service Data ................................................................................... 15-1
15.1.1 Architecture of Standard IN................................................................................. 15-2
15.1.2 Architecture of Local IN....................................................................................... 15-4
15.1.3 IN Charging Principles ........................................................................................ 15-6
15.1.4 Recorded Announcement Message ID ............................................................... 15-7
15.1.5 Naming Conventions for Intelligent Voice Files ................................................ 15-10
15.2 Configuring IN Charging Data...................................................................................... 15-12
15.2.1 Overview ........................................................................................................... 15-12
15.2.2 Adding Holiday Tariff Discount (Optional)......................................................... 15-13
15.2.3 Adding Weekday Tariff Discount (Optional)...................................................... 15-16
15.2.4 Adding Normal Tariff Discount (Optional) ......................................................... 15-17
15.2.5 Adding Conversation Duration Discount (Optional) .......................................... 15-18
15.2.6 Adding Charging Class ..................................................................................... 15-19
15.2.7 Adding Charging Property (Optional)................................................................ 15-20
15.2.8 Adding Charging Rounding (Optional) .............................................................. 15-22
15.3 Configuring DP Data.................................................................................................... 15-23
15.3.1 Overview ........................................................................................................... 15-23
ix

Table of Contents
15.3.2 Setting INAP Protocol Type (Optional) ............................................................. 15-25

15.3.4 Adding Access Code......................................................................................... 15-28
15.3.5 Adding TDP Configuration ................................................................................ 15-29
15.3.6 Set DP Trigger Configuration (Optional) ........................................................... 15-33
15.3.7 Add Mapping Between Service Key and Event Code (Optional)...................... 15-34
15.3.8 Adding IN Service Restriction (Optional) .......................................................... 15-35
15.4 Configuring SCP and SSP Data .................................................................................. 15-37
15.4.1 Overview ........................................................................................................... 15-37
15.4.2 Adding SCP Physical Address Description....................................................... 15-39
15.4.3 Adding SSP Physical Address Description ....................................................... 15-41
15.4.4 Adding SCP Configuration ................................................................................ 15-44
15.4.5 Adding SSP Service Specialized Resource Capability (Optional) .................... 15-45
15.4.6 Adding SCP Number Mapping (Optional) ......................................................... 15-45
15.5 Configuring SHLR Data ............................................................................................... 15-47
15.5.1 Overview ........................................................................................................... 15-47
15.5.2 Adding SHLR Local Address............................................................................. 15-48
15.5.3 Adding SHLR Remote Address......................................................................... 15-50
15.5.4 Adding SHLR Group ......................................................................................... 15-51
15.5.5 Adding SHLR Configuration .............................................................................. 15-52
15.5.6 Adding SHLR Service Configuration (Optional) ................................................ 15-56
15.6 Configuring SSAP Data ............................................................................................... 15-58
15.6.1 Overview ........................................................................................................... 15-58
15.6.2 Adding INAP over IP ......................................................................................... 15-59
15.6.3 Adding Module Dialog Number ......................................................................... 15-61
15.7 Configuring IN Announcement Data ............................................................................ 15-62
15.7.1 Overview ........................................................................................................... 15-62
15.7.2 Loading IN Voice Files to MRS ......................................................................... 15-63
15.7.3 Adding Language Kind (Optional) ..................................................................... 15-64
15.7.4 Adding Language Kind Index ............................................................................ 15-65
15.7.5 Adding Money Category (Optional)................................................................... 15-67
15.7.6 Adding Record Announcement Message ID Conversion (Optional)................. 15-68
15.7.7 Adding Mapping between Message ID and Tone ID (Optional) ....................... 15-69
15.8 Special Configuration Commands ............................................................................... 15-70
15.8.1 Adding IN Service Special Signaling................................................................. 15-70
15.8.2 Adding Caller Description of Local IN Call ........................................................ 15-71
15.8.3 Adding Network Access Code........................................................................... 15-72
Chapter 16 Configuring UC Service Data ................................................................................. 16-1
16.1.1 Architecture of UC System.................................................................................. 16-1
16.1.2 UC Intelligent Calling Routing ............................................................................. 16-3
16.2 Configuring UC Service Data......................................................................................... 16-4
x

Table of Contents
16.2.1 Overview ............................................................................................................. 16-4

16.2.2 Adding UC Agent Server..................................................................................... 16-7
16.2.3 Adding UC Application Server............................................................................. 16-9
16.2.4 Adding UC Subscriber......................................................................................... 16-9
16.2.5 Adding Workstation ........................................................................................... 16-12
16.2.6 Adding UC Caller Group (Optional)................................................................... 16-12
16.2.7 Adding UC Date Information (Optional) ............................................................ 16-14
16.2.8 Adding UC Presence Status Data (Optional).................................................... 16-15
16.2.9 Setting UC Presence Status Data (Optional).................................................... 16-16
16.2.10 Adding UC Profile (Optional)........................................................................... 16-17
16.2.11 Setting UC Profile (Optional)........................................................................... 16-18
16.2.12 Adding UC Intelligent Calling Routing (Optional) ............................................ 16-18
Chapter 17 Configuring Network Management Data ............................................................... 17-1
17.1 Background Knowledge................................................................................................. 17-1
17.1.1 Overview to Network Management Instructions ................................................. 17-1
17.1.2 Purposes of Network Management Instructions ................................................. 17-1
17.2 Configuring NM Instructions .......................................................................................... 17-6
17.2.1 Adding Originating Destination Code Control ..................................................... 17-6
17.2.2 Adding Outgoing Destination Code Control ........................................................ 17-8
17.2.3 Adding Call Gap Control ..................................................................................... 17-9
17.2.4 Adding Circuit Orient Control ............................................................................ 17-11
17.2.5 Adding Circuit Reject Control ............................................................................ 17-12
17.2.6 Adding Direct Route Control ............................................................................. 17-13
17.2.7 Adding Alternative Route Cancellation Control................................................. 17-14
17.2.8 Adding Temporary Alternative Route Control ................................................... 17-15
17.2.9 Adding Skip Sub-Route Control ........................................................................ 17-17
17.2.10 Adding Special Record Notification Control .................................................... 17-18
17.2.11 Adding Trunk Reserved Control...................................................................... 17-20
17.3 HTR Control Instructions ............................................................................................. 17-21
17.3.1 Adding HTR Description.................................................................................... 17-21
17.3.2 Setting HTR Switch ........................................................................................... 17-24
17.3.3 Removing HTR Control Table Content ............................................................. 17-24
Chapter 18 Configuring Other Data ........................................................................................... 18-1
18.1.1 Dual-homing ........................................................................................................ 18-1
18.1.2 PBX Service ........................................................................................................ 18-4
18.1.3 Videoconferencing Service ................................................................................. 18-5
18.1.4 NP Service (Hong Kong)..................................................................................... 18-7
18.2 Configuring Dual-homing Data ...................................................................................... 18-8
18.2.1 Overview ............................................................................................................. 18-8
18.2.2 Setting Dual-homing Work Mode ...................................................................... 18-10
18.2.3 Adding Dual-homing Heartbeat Configuration .................................................. 18-12
xi

Table of Contents
18.3 Configuring PBX Service Data..................................................................................... 18-13

18.3.1 Overview ........................................................................................................... 18-13
18.3.2 Adding PBX Group............................................................................................ 18-15
18.3.3 Adding PBX Subscriber..................................................................................... 18-17
18.3.4 Adding PBX Virtual Subscribers........................................................................ 18-18
18.4 Configuring Videoconferencing Service Data.............................................................. 18-20
18.4.1 Overview ........................................................................................................... 18-20
18.4.2 Adding MCU Configuration ............................................................................... 18-21
18.4.3 Adding iDo and SMC......................................................................................... 18-23
18.5 Configuring NP Service Data (Hong Kong) ................................................................. 18-25
18.5.1 Overview ........................................................................................................... 18-25
18.5.2 Adding NP Server ............................................................................................. 18-27
18.5.3 Adding Connection to NP Server ...................................................................... 18-28
18.5.4 Adding Mapping between Network Number and Telephone Number (Optional)18-29
18.6 Configuring RACF Card Number ................................................................................. 18-30
18.6.1 Overview ........................................................................................................... 18-30
18.6.2 Configuring DP, SCP, and SSP Data ............................................................... 18-30
18.6.3 Add CSP Service Configuration ........................................................................ 18-31
18.6.4 Adding CSP Service Logic File ......................................................................... 18-33
18.6.5 Activating CSP Service Logic File..................................................................... 18-34
18.6.6 Adding CSP Service Module Configuration ...................................................... 18-34
18.6.7 Adding RACF Number Segment ....................................................................... 18-35
18.6.8 Adding RACF Number ...................................................................................... 18-36
18.7 Configuring Supplementary Service Data ................................................................... 18-36
18.7.1 Modifying Special Tone Configuration .............................................................. 18-36
18.7.2 Adding Service Processing Configuration......................................................... 18-37
18.7.3 Modifying Supplementary Service Analysis ...................................................... 18-39
18.7.4 Modifying Supplementary Service Collision Configuration ............................... 18-46
18.7.5 Modifying Supplementary Service Priority Configuration.................................. 18-47
18.7.6 Adding Call Forwarding Restriction................................................................... 18-48
18.7.7 Adding Call Forwarding Data ............................................................................ 18-49
18.7.8 Setting MWN Service Configuration.................................................................. 18-50
Appendix A Configuring SNTP Client .........................................................................................A-1
A.1 Overview............................................................................................................................A-1
A.2 Guide to Data Configuration..............................................................................................A-3
Appendix B Basic Principles of CRG Charging .........................................................................B-1
B.1 Overview............................................................................................................................B-1
B.1.1 Basic Concepts .......................................................................................................B-1
B.1.2 Charging Mode and Charging Process ..................................................................B-2
B.2 CRG Charging Process.....................................................................................................B-3
B.2.1 Charging Process of the First Class (CHG/TAC) ...................................................B-3
xii

Table of Contents
B.2.2 Charging Process of the Second Class (CHB/CHP) ..............................................B-6

B.2.3 Charging Process of the Third Class (CRG) ..........................................................B-9
B.2.4 Special Cases of the CHP/CRG Charging Modes................................................B-10
Appendix C Tone ID ......................................................................................................................C-1
Appendix D Acronyms and Abbreviations .................................................................................D-1

xiii

Chapter 1 Overview of Configuration Guide

1.1 General Configuration Procedure
1.1.1 Overview of General Configuration Procedure
U-SYS SoftX3000 SoftSwitch System (hereinafter referred to as the SoftX3000) is
designed with a referenceable database mechanism to manage the various data of the
system. The whole database mechanism is composed of a number of data tables that
are associated with each other. Each data table describes a particular combination of
data, and references or is referenced by other data tables through key fields.
Depending on the storing process of the database, the SoftX3000 provides a practical
data configuration procedure that is recommended to follow when you configure data in
the SoftX3000 to avoid generating useless data and to guarantee that key fields have
been defined before they are referenced in the subsequent data tables.
The general procedure for configuring data in the SoftX3000 is illustrated in Figure 1-1.

1-1

Start
Equipment data
Trunk data
Office data
Number analysis
Charging data
Subscriber data
MG data
Centrex data
MRS data
Call barring data
Protocol data
IN service data
Signaling data
Other service data
Routing data
Other application
data
End
Figure 1-1 General procedure for configuring data in the SoftX3000

Figure 1-1 illustrates the general data configuration procedure. In the actual office
deployment, you might make appropriate adjustments with regard to those
recommended configuration steps or items. However, the most essential principle,
base data, interconnection data, and then service or application data, must be
complied with.
1.1.2 Configuring Base Data

The base data includes equipment data, local office data, and charging data. Being the
grounds for configuring the database of the SoftX3000, the base data defines the
globally significant data such as equipment components, physical port parameters,
basic office information, and charging policies.
The key parameters defined when you configure the base data include module number
for a board, Internet Protocol (IP) address of an Fast Ethernet (FE) port, local Dial
Number (DN) set, call source code, charging source code, and charging selection code.
These key parameters will be frequently referenced in the subsequent data
configuration steps. Once the database is constructed by means of data configuration,

1-2

these key parameters cannot be modified or removed if not for a particular purpose,
which is limited by the storing process of the database.
An example of key parameter is the module number of a board. The module number is
referenced when you configure Media Gateway (MG) data, Media Resource Server
(MRS) data, protocol data, signaling data, trunk data, and subscriber data. If you want
to modify the module number of a board, first of all, you should remove all data tables
referencing that module number. This will be an absolutely complicated task. Moreover,
this action is not allowed when the equipment is operating to provide service for
subscribers.
Therefore, pay enough attention to the planning of the base data according to the data
configuration engineering specifications provided by Huawei Technologies Co., Ltd
(hereinafter referred to as Huawei). The purpose is to facilitate the management and
maintenance of the database as well as facilitating the extension of the database in a
system capacity expansion or software upgrade in future.
1.1.3 Configuring Interconnection Data

The interconnection data includes MG data, MRS data, protocol data, signaling data,
routing data, and trunk data. Being a significant part of the SoftX3000 database, the
interconnection data defines the data regarding signaling, protocol, and trunk when you
configure the SoftX3000 to interconnect with Integrated Access Device (IAD), Access
Media Gateway (AMG), Trunk Media Gateway (TMG), Media Resource Server (MRS),
Signaling Gateway (SG), Signaling Transfer Point (STP), Service Control Point (SCP),
Public Switched Telephone Network (PSTN) switch, SoftSwitch, and Private Branch
Exchange (PBX).
The configuration of the interconnection data is the necessary premise for the telecom
carrier to provide a variety of services on the SoftX3000. Due to the complexity of the
system networking, however, the interconnection data is configured in different
processes in different networking conditions. It is recommended to separate the
complex system networking into several relatively independent networking units
according to the networking functionality (or purposes) before you configure the
interconnection data. The purpose of the recommendation is to minimize the
complexity of data configuration and improve the efficiency of software debugging.
After the separation, refer to U-SYS SoftX3000 SoftSwitch System Operation
Manual-Configuration Example for suitable networking examples.
1.1.4 Configuring Service or Application Service

The service or application data includes number analysis data, subscriber data,
Centrex data, call barring data, Intelligent Network (IN) service data, Internet Personal
Number (IPN) service data, Unified Communication (UC) service data, and network
management data. Being the most flexible part of the SoftX3000 database, the service

1-3

or application data defines dialing plan, subscriber number allocation plan, call barring
plan, service integration information, and service rule.
The configuration of the service or application data achieves the deployment of the
variety of services and the implementation of the diversity of functions on the
SoftX3000. What you will operate in future routine maintenance is the service or
application data. It is not easy to configure this part of data due to its high flexibility. To
guarantee the normal operation of the equipment, it is recommended to carefully read
this manual and receive necessary training before you operate the equipment.
1.2 Database Operations

1.2.1 Introduction to Database Operations
I. Classification of databases
According to the storage position, the database mechanism of the SoftX3000 is divided
into host database and background database.
The host database is distributed in the memory of the boards installed in the host. The
host database stores the information closely related to the operation of the host, such
as media gateway (MGW) IP address, subscriber numbers, circuit numbers, dialing
plan, and routing plan. The host database stores information identified by the module
number of a board. Such boards include System Management Unit (SMUI), Central
Database Board (CDBI), IP Forward Module (IFMI), Broadband Signaling Gateway
(BSGI), Multimedia Signaling Gateway Unit (MSGI), Fixed Calling Control Unit (FCCU),
Fixed Calling Control and Signaling process Unit (FCSU), and Media Resource Control
Unit (MRCA).
The background database refers to a Structured Query Language (SQL) database that
is located in the hard disk of the Back Administration Module (BAM). The background
database stores the information supporting the operation of the host, including a BAM
database, an alarm database, a bill database, and a traffic measurement database.
The BAM database accommodates all information that is necessary to generate the
host database. No other database has a closer relationship than the BAM database to
the host database.
II. Relationship between the BAM database and the host database
What can be operated by you through Man Machine Language (MML) commands is
the BAM database due to the limitation of format. The Dataman process of the BAM
server provides a function to achieve the format conversion between the BAM
database and the host database. The maintenance, refreshment, and backup
mechanism of the BAM database are illustrated in Figure 1-2.

1-4


Supplementary services data
Scheduled backup/manual backup
Host database
SMUI
CDBI
IFMI
Data to be
BSGI
loaded to host
MSGI
db_2.dat
FCCU
db_3.dat
Loading data
FCSU
db_4.dat
MRCA
...
db_2($).dat
db_3($).dat
db_4($).dat
...
Online setting
Backup file
BamYYYYMMDD.dat
Automatic backup
Manual backup
BAM
database
Converting
format
Setting
background
data
Workstation
Supplementary services
data defined through
phone set
Figure 1-2 Maintenance, refreshment, and backup mechanism of the BAM database
When you add, modify or remove data through the operation & maintenance client in
the online (also known as in-service) way, the BAM conducts the following actions:
1)
The Dataman process of the BAM server refreshes the BAM database in real
time.
2)
The Dataman process of the BAM server converts the new settings to a suitable
format and refreshes the corresponding data files to be loaded to the host.
3)
The Exchange process of the BAM server transmits the new data to the host.
In addition, end users might set supplementary services, Internet personal number
(IPN) service, and remote activate call forwarding (RACF) service through a phone set.
The service data is automatically backed up to the BAM database at 2:30 a.m. every
day. The data files to be loaded to the host are automatically refreshed meanwhile.
To guarantee the security of the BAM database, the system automatically backs it up at
4:30 a.m. every day by default. A maximum of 11 database files can be backed up. The
backup files of the BAM database involve the following:
z
The default storage path is F:\SoftX3000.
The database files for the consecutive seven days except Sunday before the
current date are backed up separately. Six backup files are generated and named
in the format of BamYYYYMMDD.dat.
The database files for the four Sundays during the preceding twenty-eight days
are backed up separately. Four backup files are generated and named in the
format of BamYYYYMMDD.dat.
The BAM database file for the first day of each month is backed up. The backup
file is named BamMonthBak.dat.

1-5

Note:
z
The data files to be loaded to the host are stored on D:\Data in the hard disk of the
BAM. The files are named in the format of db_?.dat or db_?$.dat, in which ? stands
for a specific module number, and db_?$.dat is the compressed file corresponding
to db_?.dat.
What are sent by the BAM to the host through the internal Ethernet are the loading
data files named in the format of db_?$.dat. The purpose is to reduce the
communication traffic between the BAM and the host and thus improve the loading
speed.
III. Operations on database

The common operations on database include format conversion, online setting, CRC,
data transfer, database backup, script compilation, execution of batch commands, and
browse of BAM database.
1.2.2 Format Conversion

I. Setting the format conversion status: SET FMT
z
Functions
This command is used to control the format conversion switch of BAM database ->
host database. Whenever the BAM is restarted, the switch is ON by default. When
you set data in the online way, the Dataman process of the BAM server converts the
new settings to a suitable format in real time. When you use the FMT command to
format all the data, the Dataman process of the BAM server converts all the data to a
suitable format.
If the switch is set to OFF, the Dataman process of the BAM server does not
implement the format conversion function even though you are setting data in the
online way or you are using the FMT command to convert data. In this case, the
information stored in the BAM database no longer keeps consistent with the information
stored in the host database. That is, all the changes that you make on the BAM
database cannot be synchronized to the host database.
Therefore, this command is usually used in the office deployment or system capacity
expansion. After you have configured or modified data, remember to open the format
conversion switch, execute the FMT command to format all the data, and load the data
to the corresponding module of the host.
z
Parameters
[Status]

1-6

This parameter specifies the status of the format conversion switch. To open the format
conversion switch, set the parameter to ON. To close the format conversion switch,
set the parameter to OFF.
z
Examples
//Set the format conversion switch to be OFF.

SET FMT: STS=OFF;
//Set the format conversion switch to be ON.

SET FMT:STS=ON;
II. Formatting all data: FMT

z
Functions
This command is used to convert all the data stored in the BAM database to a suitable
format to generate the data files to be loaded to the host. The loading files,
distinguished by module numbers, are stored on D:\Data in the hard disk of the BAM
and named in the format of db_?.dat.
After you have set data in the offline way, remember to open the format conversion
switch, execute the FMT command to format all the data, and load the data to the
corresponding module of the host.
z
Parameters
None.
z
Examples
//Convert the data to a suitable format.

FMT:;
1.2.3 Online Setting

I. Entering the online mode: LON
z
Functions
This command is used to specify that data is set in the online way through the
SoftX3000 clients including normal workstations, the emergency workstation, and the
BAM. Whenever the BAM is restarted, the system enters the online mode by default for
data setting.
After this command is executed, the Dataman process of the BAM server
automatically formats the new settings as long as the BAM database is modified
through a client. Subsequently, the BAM sends the new settings to the host through the
Exchange" process. In this way, the information stored in the BAM database always
keeps consistent with the information stored in the host database. That is, all the
changes that you make on the BAM database can be synchronized to the host
database.
1-7

z
Parameters
None.
z
Examples
//Enter the online mode.

LON:;
II. Entering the offline mode: LOF

z
Functions
This command is used to specify that data is set in the offline way through the
SoftX3000 clients including normal workstations, the emergency workstation, and the
BAM.
After this command is executed, the BAM server formats the newly set data only
through the Dataman process when you modify the BAM database through a client.
The BAM cannot send the new settings to the host through the Exchange" process. In
this case, the information stored in the BAM database no longer keeps consistent with
the information stored in the host database. That is, all the changes that you make on
the BAM database cannot be synchronized to the host database.
Setting data in the offline way is usually applicable to the office deployment or system
capacity expansion for the purpose of saving data configuration time. It is not
recommended to set a large volume of data in the offline way because it might be
beyond the setting capability of the system. Once the system enters the online mode,
the changes that you make cannot be completely synchronized to the host database
and consequently the BAM database cannot keep consistent with the host database.
To solve this problem, the only approach is to LOAD data to the system.
z
Parameters
None.
z
Examples
//Enter the offline mode.

LOF:;
1.2.4 CRC Check

I. Starting the Cyclic Redundancy Check (CRC): STR CRC
z
Functions
This command is used to check whether the information stored in the BAM database
and in the host database keeps consistent. Data table errors can be found.
The BAM automatically performs a CRC check on all the data tables created in the
system at 3:30 a.m. every day, that is, the BAM executes STR CRC automatically.
When an inconsistency error is found, the system generates an alarm through the
1-8

alarm system. In this case, you can execute the CHK DATA command to locate the
data error precisely, and then the SND SPD command to send the inconsistent data
table to the host. If that inconsistency error is encountered again, unforeseeable errors
probably happen to the system. Contact Huawei immediately.
z
Parameters
[Module number]
This parameter specifies the module on which the CRC check is to be started. This
parameter must be set.
[Table ID]
This parameter specifies the data table on which the CRC check is to be started. This
parameter is optional. If this parameter is not set, the CRC check will be performed on
all the data tables of the module.
z
Examples
//Start the CRC check on all the data tables of the module numbered 22.
STR CRC: MN=22;
//Start the CRC check on the data table 0 of the module numbered 22.
STR CRC: MN=22, TID=TID0;
II. Starting the tuple-level CRC check: CHK DATA

z
Functions
This command is used to check whether the information stored in the BAM database
and in the host database keeps consistent. Tuple errors can be found.
The BAM automatically performs a CRC check on all the data tables created in the
system at 3:30 a.m. every day, that is, the BAM executes STR CRC automatically.
When an inconsistency error is found, the system generates an alarm through the
alarm system. In this case, you can execute the CHK DATA command to locate the
data error precisely, and then the SND SPD command to send the inconsistent data
table to the host. If that inconsistency error is encountered again, unforeseeable errors
probably happen to the system. Contact Huawei immediately.
z
Parameters
[Module number]
This parameter specifies the module on which the tuple-level CRC check is to be
started. This parameter must be set.
[Table ID]
This parameter specifies the data table on which the tuple-level CRC check is to be
started. This parameter is optional. If this parameter is not set, the tuple-level CRC
check will be performed on all the data tables of the module.
z
Examples
1-9

//Start the tuple-level CRC check on all the data tables of the module numbered 22.
CHK DATA: MN=22;
//Start the tuple-level CRC check on the data table 0 of the module numbered 22.
CHK DATA: MN=22, TID=TID0;
III. Stopping the CRC check: STP CRC

z
Functions
This command is used to manually stop the CRC check that the system is executing in
data table level. This command is the inverted command for STR CRC.
z
Parameters
None.
z
Examples
//Stop the CRC check that the system is executing.

STP CRC:;
1.2.5 Data Transmission

I. Sending specified data table: SND SPD
z
Functions
This command is used to send the inconsistent data table of the BAM database to the
host for the purpose of synchronizing the host database with the BAM database.
z
Parameters
[Module number]
This parameter specifies the module of the host to which the data table is to be sent.
This parameter must be set.
[Table ID]
This parameter specifies the data table that is to be sent to the host. This parameter
must be set.
[Record number]
This parameter specifies the data record in the data table that is to be sent to the host.
This parameter is optional. If this parameter is not set, all data records in the data table
will be sent to the host.
z
Examples
//Send all data records in the data table 10 to the module 22 of the host.
SND SPD: MN=22, TID=TID10;

1-10

//Send the data record 5 in the data table 10 to the module 22 of the host.
SND SPD: MN=22, TID=TID10, RID=5;
II. Listing the data to be re-sent for timeout: LST USD

z
Functions
This command is used to query whether there is data which is not synchronically set
from the BAM database to the host database yet. After you have set data in the offline
way, the BAM automatically sends all modified data tables to the host whenever you
execute the LON command. In this case, you can use the LST USD command to query
the automatic setting process of the BAM.
z
Parameters
[Module number]
This parameter specifies the module of the host to be queried. This parameter is
optional. If this parameter is not set, all modules of the host will be queried. That is, all
data that is not sent to the host yet will be listed.
z
Examples
//List all data that is not sent to the host yet.

LST USD:;
//List the data that is not sent to the module 22 of the host yet.
LST USD: MN=22;
III. Sending the data to be re-sent for timeout: SND USD

z
Functions
This command is used to send to the host the data of the BAM database that is not
synchronically set to the host database, for the purpose of synchronizing the host
database with the BAM database.
z
Parameters
[Module number]
This parameter specifies the module of the host to which the data is to be sent. This
parameter is optional. If this parameter is not set, the timeout data will be sent to all the
modules of the host.
z
Examples
//Send the timeout data to all the modules of the host.

SND USD:;
//Send the timeout data to the module 22 of the host.

SND USD: MN=22;

1-11

1.2.6 Database Backup

I. Backing up the supplementary service data: BKP SS
z
Functions
This command is used to manually back up the supplementary service data stored in
the host database.
The supplementary service data that is set by an end user through a phone set is stored
in the host database. According to the stored data in the host database, the system
synchronically refreshes the related information in the BAM database automatically at
scheduled time or by manual intervention for consistency purposes.
z
Parameters
[FCCU/FCSU Module number]

This parameter specifies the module of the host of which the supplementary service
data is to be backed up. This parameter is optional. If this parameter is not set, the
supplementary service data of all the modules of the host will be backed up.
[Supplementary service]
This parameter specifies the type of the supplementary service whose data is to be
backed up manually. By default, this parameter is set to all. That is, the data of all
types of supplementary services will be backed up.
[Mode]
This parameter specifies the mode of backing up the supplementary service data. By
default, this parameter is set to normal and accordingly only the added data will be
backed up. If this parameter is set to all, all data will be backed up.
z
Examples
//Back up the added supplementary service data of all the modules of the host.
BKP SS:;
//Back up all the supplementary service data of all the modules of the host.
BKP SS: MODE=ALL;
//Back up all the supplementary service data of the module 22 of the host.
BKP SS: MN=22;
//Back up the abbreviated dialing service data of the module 22 of the host.
BKP SS: MN=22, SS=ADI;
II. Backing up the IPN service data: BKP IPN

z
Functions

1-12

This command is used to manually back up the IPN service data stored in the host
database.
Such data of the IPN service as card number and selection rule that is set by an end
user through a phone set is stored in the host database. According to the stored data in
the host database, the system synchronically refreshes the related information in the
BAM database automatically at scheduled time or by manual intervention for
consistency purposes.
z
Parameters
[IPN service]
This parameter specifies the type of the IPN service whose data is to be backed up
manually. By default, this parameter is set to all. That is, all types of IPN service data
will be backed up.
[Mode]
This parameter specifies the mode of backing up the IPN service data. By default, this
parameter is set to normal and accordingly only the added data will be backed up. If
this parameter is set to all, all data will be backed up.
z
Examples
//Back up all types of added IPN service data.

BKP IPN: IPNS=ALL;
//Back up all types of all IPN service data.

BKP IPN: IPNS=ALL, MODE=ALL;
//Back up the IPN card data.

BKP IPN: IPNS=IPNC;
//Back up the IPN sequence rule data.

BKP IPN: IPNS=IPNSR;
III. Backing up the RACF service data: BKP RACF

z
Functions
This command is used to manually back up the RACF service data stored in the host
database.
Normally, such data of the RACF service as forwarded-to number set by an end user
through a phone set is stored in the host database. According to the stored data in the
host database, the system synchronically refreshes the related information in the BAM
database automatically at scheduled time or by manual intervention for consistency
purposes.
1-13

z
Parameters
[Mode]
This parameter specifies the mode for manually backing up the RACF service data. By
default, this parameter is set to normal and accordingly only the added data will be
backed up. If this parameter is set to all, all data will be backed up.
z
Examples
//Back up the added RACF service data.

BKP RACF: MODE=NORMAL;
//Back up all RACF service data.

BKP RACF: MODE=ALL;
IV. Backing up the BAM database and the registry: BKP DB

z
Functions
This command is used to manually back up the BAM database and the registry.
After you execute this command, the system generates on F:\SoftX3000 in the hard
disk of the BAM a BAM database file named in the format of BamYYYYMMDD.dat
and a BAM registry file named in the format of BamReg.bak. These files are reserved
to recover the BAM database from a fault.
z
Parameters
None.
z
Examples
//Back up the BAM database and the registry.

BKP DB:;
1.2.7 Script Configuration

Script configuration is used for data configuration operations (usually batch operations)
in the office deployment, system capacity expansion, software upgrade, and routine
maintenance. The purpose is to improve the efficiency of data configuration and
minimize the occurrence of data configuration errors.
I. Composition of a configuration script file

A configuration script file is actually a file in the format of text. For example, a script file
for configuring equipment data is as follows:
//Add a rack numbered 0.
ADD SHF: SN=0, LT="SoftX3000", PN=0, RN=0, CN=0, PL=2;
//Add a frame numbered 0. The position number in the rack is 2.

1-14

ADD FRM: FN=0, SN=0, PN=2;
//Add boards. The assist boards are in the respective adjacent slots
ADD BRD: FN=0, SN=0, LOC=FRONT, BT=IFMI, MN=132, ASS=1;
ADD BRD: FN=0, SN=2, LOC=FRONT, BT=FCCU, MN=22, ASS=3;
ADD BRD: FN=0, SN=4, LOC=FRONT, BT=FCSU, MN=23, ASS=5, LNKT=LINK_64K;
ADD BRD: FN=0, SN=10, LOC=FRONT, BT=BSGI, MN=136, ASS=11;
ADD BRD: FN=0, SN=12, LOC=FRONT, BT=MSGI, MN=137, ASS=13;
ADD BRD: FN=0, SN=14, LOC=FRONT, BT=CDBI, MN=102, ASS=15;
ADD BRD: FN=0, SN=4, LOC=BACK, BT=EPII;
ADD BRD: FN=0, SN=5, LOC=BACK, BT=EPII;
ADD BRD: FN=0, SN=13, LOC=BACK, BT=CKII;
ADD BRD: FN=0, SN=15, LOC=BACK, BT=CKII;
//Add FE port configuration. The default gateway address is the IP address of the
router.
ADD FECFG: MN=132,IP="191.169.150.30", MSK="255.255.0.0",
DGW="191.169.150.60", EA=AUTO;
//Add all central database functions.

ADD CDBFUNC: CDPM=102, FCF=All;
//Add E1 port configuration.

ADD EPICFG: FN=0, SN=4, E0=DF, E1=DF, E2=DF, E3=DF, E4=DF, E5=DF, E6=DF, E7=DF;
According to technical specifications of Huawei, a configuration script file is composed

of two parts. One is comments preceded by //, used to describe the purposes of the
following configuration command(s). The other is configuration command(s) started
with various MML commands, used to send data configuration operations to the BAM.
II. Creating a configuration script file

1)
2)
Create a text file named, for example, 20031201.txt.

The first line in the script file can neither be an empty line nor comments. That is, a
script file must be started with an executable MML command. Usually, it is LOF:;.
3)
On a workstation, start U-SYS SoftX3000 Client. Do not log on to the system. In

the [Operator login] window, click <Cancel> as shown in Figure 1-3.

1-15

Figure 1-3 [Operator login] window

4)
Enter the MML window. In the [Command Input] box, type a desired configuration
command. In the following parameter input area, set the parameters necessary for
the configuration. In the area above the command input area, you can find the
complete information of the configuration command appears. Select all the
characters of the configuration and press <Ctrl+C>. (Note: Do not omit any
characters.) See Figure 1-4.
Figure 1-4 MML command input interface

5)
In the configuration script file 20031201.txt, press <Ctrl+V> to copy the

configuration characters to the file. In this way, a configuration command is
created. Note that a configuration command is ended with a semicolon ;. The
character indicates the end of the input of the command. Do not remove it.
Otherwise, the command cannot be executed.
6)
Create other configuration commands in the same way and add comments
preceding the corresponding commands.

1-16

Note:
A lot of configuration script files are provided in U-SYS SoftX3000 SoftSwitch System
Operation Manual-Configuration Example for your reference.
1.2.8 Batch File Execution

To improve the efficiency of data configuration, the SoftX3000 provides a function to
execute a batch of configuration commands. With this function, you can create a script
and then execute it on any workstation. The operation steps are as follows:
1)
Create a script file named, for example, 20031201.txt.
2)
On a workstation, start the SoftX3000 Operation and Maintenance Client, log on to

the system, and then open the MML window.
3)
Press <Ctrl+E>, and the [Execute Batch File] window appears. In the window, click
<Browse> to select the storage path of the 20031201.txt. It is assumed that the
file is stored on D:\SoftX3000, as shown in Figure 1-5.
Figure 1-5 [Execute Batch File] window

4)
Click <OK> in Figure 1-5, and the system starts to check syntax errors in the
20031201.txt. If no syntax errors are found, an execution window appears. Drag

1-17

the horizontal scroll bar at the bottom of the window until <Go> is displayed on the
screen. Click <Go> to execute the script file, as shown in Figure 1-6.
Figure 1-6 Execution window

5)
The system executes the configuration commands written in the 20031201.txt one
by one. (Remarks start with // and are skipped during the execution.)
1.2.9 BAM Database Browse

After the BAM server software is installed on the BAM, the system automatically
provides a tool, TableBrowse.exe, on D:\SoftX3000\Tools\TableBrowser on the BAM
hard disk. With this tool, you can browse and view the data tables stored in the BAM
database quickly, graphically, and effectively. The tool does not provide modification
functions.
Usually the tool runs on the BAM or the emergency workstation. The operation steps
are as follows:
1)
On D:\SoftX3000\Tools\TableBrowser on the BAM hard disk, execute the

TableBrowse.exe. The [SQL Server Login] window appears. In the window, type
the IP address of the server (127.0.0.1 indicating the BAM itself), the login ID (sa),
and the correct login password, as shown in Figure 1-7. Click <OK>.
Figure 1-7 [SQL Server Login] window

2)
The [TableBrowse] window appears. Click a node on the TreeView, and you can
browse all the contents of the corresponding data table, as shown in Figure 1-8.

1-18

Figure 1-8 [TableBrowse] window
1.3 Notes on Data Configuration

1.3.1 Rules for Setting MML Command Parameters
When you configure data with MML commands, the SoftX3000 provides a graphical
user interface to help you set command parameters, as shown in Figure 1-9.
Figure 1-9 MML command input window

When configuring data, pay attention to the following:
z
Red parameters in a command are key parameters that you must set, for example,
[Shelf number], [Position number], [Row number], and [Column number] as shown

1-19

in Figure 1-9. If you do not set such red parameters, the command cannot be
executed.
z
Black parameters in a command are not key parameters. (Only few black
parameters are key parameters.) You can choose to set black parameters or
choose not to set them. Black parameters do not affect the execution of the
command. An example is [Location title] in Figure 1-9.
The system provides default values for some uncommonly modified parameters to
reduce your work. You can choose to modify such parameters according to the
actual situations. An example is [PDB location] in Figure 1-9.
If you want to know the default value or the value range of a parameter, you can
move the cursor to the input box of the parameter and the system displays the
default value or the value range of the parameter in a floating box, for example,
[Position number] in Figure 1-9.
1.3.2 Effect of Maximum Number of Tuples on Data Configuration

Limited by memory capacity, CPU processing capability, and other factors, the storage
requirements for board memory by host software, host database, and bill information
has to be taken into consideration during the allocation of board memory. Consequently,
the system does not allocate too large storage space for the host database which is
running on the memory of the boards in the host. In other words, the maximum number
of tuples of the various data tables in the host database must be defined.
For example, the module number of an FCCU module is 22. After you execute LST
MAXT: TP=FCCU, MN=22; on the SoftX3000 Client, the system displays the
maximum numbers of tuples stored in the various data tables of the host database in
the module 22.
CCU - Maxtuples for private tables
---------------------------------Table name
Table ID
FCCU/FCSU module number
Number
tbl_SMInstance
22
22
1500
tbl_Bcmgw
70
22
5000
tbl_Bcudpaddr
73
22
5000
tbl_Bcmgwauxinfo
76
22
5000
tbl_Bcmgwcapability
77
22
5000
tbl_CFData
115
22
64
tbl_PbxUserGrpDev
151
22
500
tbl_UserDataIdx
152
22
50000
tbl_ESLDev
154
22
40000
tbl_ESLUserData
155
22
40000
tbl_TkCircuit
304
22
5000
tbl_Bicccic
315
22

1-20

tbl_UcSubscriber
400
22
1024
tbl_UcCliGroup
401
22
10240
tbl_UcWeekType
402
22
1024
tbl_UcDateType
403
22
1024
tbl_UcTimeType
404
22
10240
tbl_UcIcr
405
22
4000
tbl_UcIcrIdx
406
22
10240
tbl_NMCallGap
456
22
100
tbl_SIPDev
650
22
5000
tbl_SIPUserData
651
22
5000
tbl_H323Dev
652
22
5000
tbl_H323UserData
653
22
5000
tbl_SIPH323DevRegInfo
654
22
10000
tbl_V5Var
680
22
100
tbl_PCMAttr
691
22
320
tbl_BRAUserData
879
22
1000
tbl_BRADev
880
22
2000
tbl_NPServerConnect
901
22
255
tbl_UserName
940
22
40000
(Result number = 31)
Judging from the preceding display, the maximum number of tuples stored in the
tbl_UserDataIdx data table is 50000. Accordingly, for the FCCU module, a maximum
of 50000 subscribers can be configured. When the 50001st subscriber is to be added,
the system prompts errors (data record overflow) and the operation fails. Other cases
can be deduced in the same way.
Do not modify the maximum number of tuples of the host database. Otherwise, the
storage capability of other key information (such as bill information) of the system will
be affected. In addition, the browse efficiency of the database will be reduced due to its
large volume and the reliability of the system will be degraded because the large
volume of the database exceeds the capabilities designed for the system.
If it is really required to modify the maximum number of tuples of the host database,
contact Huawei technical support engineers for help. Do not modify it by yourself.
1.3.3 Effect of Software Parameters on Data Configuration

It is a fact that different countries comply with different technical specifications and
industrial standards, different equipment providers have different understandings of the
same protocol or signaling, and different network devices employ different technologies.
Consequently it might be hard to interconnect the SoftX3000 with some network
devices.
To solve that problem, the SoftX3000 provides a software switch mechanism to control
some controversial and changeable software parameters. That is, you can modify the
1-21

corresponding software switch to interwork the local office with other network devices
or to provide some special functions.
For example, the SoftX3000 might be interconnected with a PSTN switch through ISUP
signaling. For the requirements for N % 64kbit/s data service, the opposite PSTN switch
requires the local office to transfer bearer capabilities through user terminal service
information; otherwise, the opposite PSTN switch refuses the connection when a local
office subscriber attempts to use the 2B + D video service through the corresponding
ISUP trunk circuit. In this case, you have to modify bit 13 of the parameter ISUP
operation reserved parameter 10 (P27) to 0 for the normal interconnection.
Generally speaking, software parameters are designed for some special issues. Each
bit of a software parameter has a unique meaning. Use the default values usually. If it is
really required to modify a software parameter, contact Huawei technical support
engineers for help. Do not modify it by yourself.

1-22

Chapter 2 Configuring Equipment Information

2.1 Related Concepts
2.1.1 Device Numbering
I. Rack numbering
Based on networking and capacity settings, a maximum of five racks can be configured
for the SoftX3000, numbering from 0 to 4. Number 0 is for the rack holding the
integrated configuration cabinet. All the other racks are numbered sequentially, as
shown in Figure 2-1.
Integrated configuration
cabinet
Service processing
cabinet
Service processing
cabinet
Service processing
cabinet
Service processing
cabinet
Power distribution frame Power distribution frame Power distribution frame Power distribution frame Power distribution frame
Expansion frame 01
Basic frame 05
Air deflector
Air deflector
Basic frame 00
Air deflector
Expansion frame 04
Air deflector
Expansion frame 03
Expansion frame 09
Air deflector
Expansion frame 08
Air deflector
Expansion frame 13
Air deflector
Expansion frame 12
Air deflector
Expansion frame 17
Air deflector
Expansion frame 16
Air deflector
Expansion frame 07
Expansion frame 11
Expansion frame 15
Air deflector
Air deflector
Air deflector
BAM / iGWB /
LAN Switch / others
Air deflector
Expansion frame 02
Expansion frame 06
Blank filler panel
Blank filler panel

Blank filler panel
Blank filler panel

Blank filler panel
Blank filler panel
Figure 2-1 Rack numbering (from left to right)

2-1
Expansion frame 10
Expansion frame 14
Blank filler panel

Blank filler panel
Blank filler panel

Blank filler panel

II. Frame numbering

The SoftX3000 can be configured with eighteen Huawei Open Standards Telecom
Architecture Platform (OSTA) frames at most, numbering from 0 to 17. The numbering
rule is as follows:
z
Numbering upward within a cabinet
Numbering between racks in ascending order of rack numbers
There are two basic frames at most, numbered 0 and 5. Refer to Figure 2-1 for the
numbering rule of frames.
Rack number is determined by the 8-bit Dial in-line Package Switch (DIP switch) S3 on
the System Interface Unit (SIUI) that is the back board of the System Management Unit
(SMUI). Refer to Table 2-1 for the setting of DIP switch.
Table 2-1 Setting of DIP switch S3
Switch
Frame No.
on
on
on
on
on
on
on
on
on
on
on
on
on
on
on
off
on
on
on
on
on
on
off
on
on
on
on
on
on
on
off
off
on
on
on
on
on
off
on
on
on
on
on
on
on
off
on
off
on
on
on
on
on
off
off
on
on
on
on
on
on
off
off
off
on
on
on
on
off
on
on
on
on
on
on
on
off
on
on
off
10
on
on
on
on
off
on
off
on
11
on
on
on
on
off
on
off
off
12
on
on
on
on
off
off
on
on
13
on
on
on
on
off
off
on
off
14
on
on
on
on
off
off
off
on
15
on
on
on
on
off
off
off
off
16
on
on
on
off
on
on
on
on
17
on
on
on
off
on
on
on
off

2-2

III. Slot numbering

In the OSTA frame used in the SoftX3000, all slots are compatible to all boards. There
are two types of boards: front board and back board. The former is inserted from the
front of the cabinet, and the latter is inserted from behind. The following boards are
used in the SoftX3000.
Table 2-2 Boards used in the SoftX3000
Board
Full name
FCCU
Fixed Calling Control Unit
FCSU
Fixed Calling Control and Signaling process Unit
UCSI
UC Service Unit
EPII
E1_Pool Interface Unit
IFMI
IP Forward Module
BFII
Back insert FE Interface Unit
SMUI
System Management Unit
SIUI
System Interface Unit
MRCA
Media Resource Control Unit
MRIA
Media Resource Interface Unit
BSGI
Broadband Signaling Gateway
MSGI
Multimedia Signaling Gateway Unit
CDBI
Central Database Board
ALUI
Alarm Unit
UPWR
Universal Power
HSCI
Hot-Swap and Control Unit
CKII
Clock Interface Unit
The front boards are FCCU, FCSU, UCSI, IFMI, CDBI, BSGI, MSGI, SMUI, MRCA, and
ALUI. The back boards are EPII, BFII, SIUI, HSCI, MRII, and CKII. UPWR can be a
front board as well as a back board.
The OSTA frame is designed with 21 standard slots, numbering from 0 to 20. The front
board slots are numbered from left to right, and the back board slots are numbered from
right to left so that the front and back boards are numbered consistently. Refer to Figure
2-2 for details.

2-3

M M S
R R I
I I U
A A I
B
F
Back boards I
I
B
F
I
I
E
P
I
I
E
P
I
I
I
I
F F
Front boards M M
I
I
F
C
S
U
F
C
S
U
M
R
C
A
M S
R M
C U
A I
H
S
C
I
S
I
U
I
H
S
C
I
S
M
U
I
C
K
I
I
10 11 12
B
S
G
I
13 14 15 16
B M M C
S S S D
G G G B
I
I
I I
U
P
W
R
U
P
W
R
17 18
19 20
U
P
W
R
U
P
W
R
C
K
I
I
C A
D L
B U
I I
Figure 2-2 Board positions in the OSTA frame
2.1.2 Module Numbering

The software in the SoftX3000 regards Back Administration Module (BAM), iGWB (a
billing gateway provided by Huawei), and front boards as modules for processing. They
are numbered from 0 to 255. The value 0 is always assigned to BAM and 1 is always
assigned to iGWB. The other numbers are assigned to the boards.
One active board and its standby are regarded as one unit, assigned with the same
module number. Each unit is assigned with a unique number. Here is the numbering
plan.
z
SMUI: 2 to 21 (automatically assigned by the system)
FCCU/FCSU/UCSI: 22 to 101
CDBI: 102 to 131
IFMI/BSGI/MSGI: 132 to 211
MRCA: 212 to 247
Caution:
z
Though the IFMI, BSGI, and MSGI vary in functions, they must be numbered within
the same number range.
Though the FCCU, FCSU, and UCSI vary in functions, they must be numbered
within the same number range.
2.1.3 Central Database Function

The host database of the SoftX3000 is divided into a central database and a database
of all modules. The database of all modules is stored in the memory of the board. It
2-4

contains all property data of the module, including subscriber number, and gateway and
trunk data that the module manages and controls. The central database is stored in the
memory of the CDBI. The central database stores the global data of the system,
including data concerning subscriber location, trunk hunting, MGW resource
management, black and white list, IPN card number, BSGI dispatching, special called
number change, RACF function, and preselection function.
Because the SoftX3000 can be configured with two pairs of CDBIs at most, you can
assign some or all the above-mentioned central database functions to the CDBIs.
1)
When the system is configured with one pair of CDBIs, you need to configure all
central database functions for them in normal cases.
2)
When two pairs of CDBIs are configured, you must assign different central
database functions to the two pairs based on the load-sharing principle. For
instance, set subscriber location, trunk hunting, MGW resource management,
BSGI dispatching, and black and white list functions on one pair, and set IPN card
number, special called number change, RACF function, and preselection function
on the other pair.
2.1.4 Protocol Dispatch Ability

In the SoftX3000, all IP-based protocols are processed by IFMI, BSGI and MSGI. There
is a clear classification of responsibilities among the three boards.
z
IFMI processes protocols of the Internet layer and the layers below, and
distributes the messages to BSGI or MSGI based on their protocol type, UDP port
number, TCP port number, or SCTP port number.
BSGI processes protocols of transport layer and higher layers including MGCP,
H.248, SCTP, M2UA, M3UA, V5UA, and IUA.
MSGI processes the protocols of the transport layer and higher layers, including
SIP, H.323, RADIUS, ENUM, STUN, MIDCOM, ORIGCALL, iDo, and SMC.
The functions of the BSGI and the MSGI do not overlap. The BSGI or MSGI cannot
deal with the protocols that are processed by the other.
The SIGTRAN protocols, such as M2UA, M3UA, V5UA and IUA, can only be
processed by the BSGI and cannot be configured. MGCP, H.248 and SCTP can only be
processed by the BSGI.
I. Scenario A: Load-sharing in protocol processing

To configure the protocol dispatch ability, one has to distribute protocols of different
stacks and layers to different BSGIs or MSGIs because each of these can process
multiple types of protocols.
For instance, following are three pairs of MSGI boards processing different protocols.
z
Pair A processes SIP only.
Pair B processes H.323 only.

2-5

z
Pair C processes all other protocols that can be processed by MSGI.
II. Scenario B: IFMI implementing the functions of MSGI

In small-scale applications such as PBX, the load of protocol processing is relatively
small. To minimize the cost, omit MSGI and configure the protocol dispatch ability to
IFMI so that IFMI can process multimedia protocols as SIP and H.323. In this way,
voice services and multimedia services are provided at a minimum cost.
2.2 Configuring Equipment Data

2.2.1 Overview
I. Relationship between configuration steps
The equipment data is the basis of all SoftX3000 data. It covers SoftX3000 hardware
information including physical port. The configuration of equipment data is the first step
in data configuration procedure, as shown in Figure 2-3.
Start
Equipment data
Trunk data
Office data
Number analysis
Charging data
Subscriber data
MG data
Centrex data
MRS data
Call barring data
Protocol data
IN service data
Signaling data
Other service data
Routing data
Other application
data
End
Figure 2-3 Data configuration procedure

During the process of SoftX3000 data configuration, some parameters defined during
the configuration of equipment data are referenced when you configure MG data, MRS
resource data, protocol data, signaling data, trunk data, and subscriber data. The

2-6

referencing relationship is presented as the broken lines in Figure 2-3. Refer to

Table 2-3 for details.
Table 2-3 Parameter referencing relationship between equipment data and other data
Input parameter
Name
Output parameter
Defined in
Name
Referenced in
Board
module
number
MG data, MRS data, protocol data, signaling

data, trunk data, and subscriber data
IP address
of FE port
MG data, MRS data, protocol data, and

signaling data
Slot
information
of E1 port
Signaling data
II. Preparations
Before configuring equipment data, make sure that all preparations are done as
specified in Table 2-4.
Table 2-4 Preparations
SN
Item
Remark
A detailed diagram of
panel configuration
It provides the type, location and number of

hardware components as racks, frames and
boards.
Board module number
It refers to the numbering of IFMI, FCCU, FCSU,

BSGI, MSGI and MRCA.
IP address of FE port
It is frequently referenced in later configuration

steps.
IP address of the router

that connects to the
SoftX3000
It is used to configure IP routing data.
E1 port working mode
It is to select 75 or 120 .
Clock
synchronization
networking plan
It is to decide the configuration of clock data.
III. Configuration steps

Table 2-5 lists the general steps for configuring equipment data.

2-7

Table 2-5 Configuration steps

Step
Description
Command
Add shelf
ADD SHF
Add frame
ADD FRM
Add board
ADD BRD
Add FE port configuration
ADD FECFG
Add Central Database (CDB) function
ADD CDBFUNC
Set dispatch ability (optional)
SET DPA
When the SoftX3000 has to provide MTP links for connecting the signaling equipment
in SS7, you need to set E1 port and clock data in the SoftX3000. For more information,
refer to Section 2.3 Configuring E1 Port and Clock Data, in this chapter.
IV. Parameter referencing relationship

Figure 2-4 illustrates the referencing relationship between key parameters used when
you configure equipment data.
ADD SHF
ADD FECFG
[Shelf number]
[IFM Module]
[Location title]
[IP address]
[Position number]
[Mask address]
[Row number]
[Default gateway]
ADD FRM
ADD CDBFUNC
[Frame number]
[Fun config]
[Shelf number]
[UCDP module number]
[Position number]
ADD BRD
SET DPA
[Frame number]
[Module number]
[Slot number]
[Dispatch ability]
[Location title]
[Module number]
Figure 2-4 Parameter referencing relationship

2-8

2.2.2 Adding Shelf

I. Related commands
Command
Function
ADD SHF
To add shelf
RMV SHF
To remove shelf
MOD SHF
To modify shelf
LST SHF
To query shelf
II. Parameter description

[Shelf number]
It is used to uniquely identify a rack. A maximum of five racks can be configured,
ranging from 0 to 4.
[Location name]
It is used to describe the location of the rack. The value type is character string.
[Position number]
It is the serial number of the equipment room in which the rack is located.
[Row number], [Column number]
They specify the position of the rack in the equipment room.
[PDB location]
It defines the location number of the frame, which contains the SMUI monitoring the
power distribution box (PDB), in the rack. The value range is 0 to 3, because a
maximum of four OSTA frames can be configured in a rack. The default value is 2.
Physically, the frame that manages the PDB is the one containing the SIUI, the board
that is connected by the monitor serial cable of PDB. The setting of the parameter must
be consistent with the cable connection; otherwise, the PDB state is not reported
correctly.
[PDB type]
It specifies whether the PDB in the rack is powered by 48V or 60V. By default, it is set
to 48V. When SoftX3000 is used in Russia and former AIS countries, it is set to
60V. The parameter indirectly defines the overvoltage and undervoltage alarm
threshold for the PDB.

2-9

2.2.3 Adding Frame

I. Related commands
Command
Function
ADD FRM
To add frame
RMV FRM
To remove frame
MOD FRM
To modify frame
LST FRM
To query frame

[Frame number]
It is used to uniquely identify a frame. A maximum of 18 frames can be configured,
ranging from 0 to 17. Numbers 0 and 5 are for basic frames and the other numbers are
for expansion frames.
The frame number is determined by the 8-bit DIP switch S3 on the SIUI. The configured
frame number must be consistent with that determined by the DIP switch; otherwise the
frame will not load the data correctly.
[Shelf number]
It specifies the number of the rack in which the frame is located. This parameter is
defined in the ADD SHF command and referenced here.
[Position number]
It specifies the position of the frame in the rack, ranging from 0 to 3 upward.
For integrated configuration cabinet in rack 0, BAM occupies frame 0, and iGWB
occupies frame 1. Therefore the position numbers available are 2 and 3. The frame
state is not displayed on BAM if the position numbers are incorrectly configured. There
is no limitation of position number in the service processing cabinets.
2.2.4 Adding Board

I. Related commands
Command
Function
ADD BRD
To add board
RMV BRD
To remove board
LST BRD
To query board
MOD CPCCFG
To modify the link configuration of the CPC
LST CPCCFG
To query the link configuration of the CPC

2-10

II. Notes of configuration

z
When you use the ADD FRM command to add the frame data, the system
automatically configures the SMUI, SIUI, HSCI, ALUI, and UPWR for the frame.
You only need to add the other boards with the ADD BRD command.
To modify the link configuration of the CPC on the FCSU, use the MOD CPCCFG
command.
III. Parameter description

[Frame number]
It specifies the number of the frame in which the board is located. This parameter is
defined in the ADD FRM command and referenced here.
[Slot number]
It specifies the number of the slot in which the board is located. 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 frame, numbering from 0 to 20
sequentially. Slots 6 through 9 and 16 through 20 are fixed for SMUI, SIUI, HSCI, ALUI
and UPWR boards.
You must comply with the following rules when adding back boards:
z
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 frame.
The CKII is only configured in slots 13 and 15 of the back half of the basic frame
(frame 0).
The EPII is added only after its front broad, FCSU, is added. The slot number of
the EPII must correspond to that of the FCSU. Otherwise, the EPII cannot be
added.
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 frame.
[Location]
It specifies the board as a front board or a back board.
[Board type]
It defines the specific type of the board. It includes types other than SMUI, SIUI, HSCI,
ALUI and UPWR.
[Module number]
It defines the module number of the board. The active and standby boards in a pair
share the same module number. The system allows accommodating a maximum of
four pairs of IFMIs and a maximum of 10 pairs of UCSIs.

2-11

Note:
The module numbering plan for boards:
z
SMUI: 2 to 21 (automatically assigned by the system when adding a frame)
FCCU/FCSU/UCSI: 22 to 101
CDBI: 102 to 131
IFMI/BSGI/MSGI: 132 to 211
MRCA: 212 to 247
[Assistant slot number]

It defines the slot number of an assistant board. When the boards are working in
active/standby mode, this parameter is used to specify the slot number of the standby
board. This parameter is valid only to boards in active/standby mode. If this parameter
is set to 255, it means that the board works in a non active/standby mode. That is, no
standby board is needed.
A pair of assistant boards working in the active/standby mode can be configured in
either adjacent slots or in nonadjacent slots, but the boards must be in the same frame.
[Link type]
It specifies the link type. When the added board is the FCSU, this parameter is used to
specify the link type of its CPC sub-board. There are two link types on the CPC
sub-board: one processes the 64 kbit/s MTP link, and the other processes the 2 Mbit/s
MTP link.
2.2.5 Adding FE Port Configuration

I. Related commands
Command
Function
ADD FECFG
To add the FE port configuration
RMV FECFG
To remove the FE port configuration
MOD FECFG
To modify the FE port configuration
LST FECFG
To list the FE port configuration

[IFMI module number]
It specifies the module number of the IFMI to which the FE port belongs. This
parameter is defined in the ADD BRD command and referenced here.
[IP address], [Mask]
2-12

They specify the IP address and sub-net mask of the FE port. Both the IP address and
mask are in dotted decimal format, for instance, 191.169.10.1 and 255.255.255.0.
[Default gateway]
It specifies the IP address of the router with which the FE port connects. This parameter
must be configured correctly; otherwise, the SoftX3000 cannot interwork with other IP
devices.
[Ethernet attribute]
It specifies the working mode of the FE port, which can be half-duplex 10 Mbit/s,
half-duplex 100 Mbit/s, full-duplex 10 Mbit/s, full-duplex 100 Mbit/s, or auto-negotiation.
By default, it is set to auto-negotiation.
[Stability option]
It specifies whether the SoftX3000 starts Address Resolution Protocol (ARP) detection
and IFMI flow detection. Here are the descriptions of the options:
z
ARP detect: It specifies if the SoftX3000 starts the ARP detection function. By
default, it is No. If you set it to Yes, the SoftX3000 will send an ARP detection
packet to the IP network through the FE port of the IFMI every 10 seconds. If the
response efficiency of the IP network is lower than 20% (that is, the packet loss
rate is greater than 80%), the SoftX3000 will switch over the IFMI automatically.
Flow check: It specifies if the SoftX3000 starts the flow detection of the IFMI board.
By default, it is set to Yes, and the IFMI board will periodically (every 60 seconds)
detect the data flow passing through it. During a continuous detection duration (5
minutes by default), SoftX3000 will automatically swap the IFMI boards based on
the following judgments:
z
The number of packets successfully forwarded through gateway from

internal network adaptor in uplink direction / the number of packets
successfully forwarded through gateway from external network adaptor in
uplink direction > 1 (it is unbalance threshold, and is 100 by default)
The number of packets successfully forwarded from internal network adaptor

in downlink direction / the number of packets successfully forwarded from
external network adaptor in downlink direction > 2 (it is unbalance threshold,
and is 100 by default)
2.2.6 Adding CDB Function

I. Related commands
Command
Function
ADD CDBFUNC
To add CDB function
RMV CDBFUNC
To remove CDB function

2-13


Because the SoftX3000 can be configured with two pairs of CDBIs at most, you can set
different central database functions for the CDBIs according to specific applications.
1)
When the system is configured with one pair of CDBIs, you need to configure all
central database functions for them in normal cases.
2)
When two pairs of CDBIs are configured, you must assign different central
database functions to the two pairs based on the load-sharing principle. For
instance, set subscriber location, trunk hunting, MGW resource management,
BSGI dispatching, and black and white list functions on one pair, and set IPN card
number, special called number change, RACF function, and preselection function
on the other pair.

[CDBI module number]
It specifies the module number of the CDBI that implements the database functions.
This parameter is defined in the ADD BRD command and referenced here.
[Function configuration]
It defines all central database functions of the CDBI. Following are the twelve options of
this parameter:
z
Select all: Configuring all the central database functions.
Clear all: Configuring no central database function.
Grayed all: Restoring the default configuration of the system, that is, configuring all
the central database functions.
Subscriber location: Implementing number location for the local subscribers and
PBX line hunting function.
Trunk hunting: Selecting trunks for outgoing calls.
MGW resource management: Managing and scheduling various resources on all

MRSs controlled by the local SoftX3000, including signal tone, service
announcement, conference bridge, and DTMF digit collector.
Black and white list: Storing all black list data and white list data of the local office
for authentication purposes.
IPN card number: Storing such IPN service data as IPN card number and
password.
BSGI
dispatching:
Controlling
the
CDBI
to
dispatch
call-independent
MGCP/H.248 messages between the BSGIs and FCCUs/FCSUs, such as

registration messages sent by MG and audit messages sent by MGC.
z
Special called number change: Storing all special called number change data in
the local office for remote network access.
RACF function: Storing card number and password of the RACF card service.
Preselection function: Storing the calling number analysis data related to the
preselection function in specific conditions. When the calling number analysis data
2-14

that is related to the preselection function and stored in the FCCU/FCSU reaches
a certain size, the system will dump all calling number analysis data in the
FCCU/FCSU to the CDBI to avoid overflow.
z
UC function: Storing subscriber numbers and intelligent routing data related to the
UC services in certain conditions. When the UC service data stored in an
FCCU/FCSU reaches a certain size, the system will dump all the data from the
FCCU/FCSU to the CDBI to avoid overflow.
Key system: Storing subscription data related to the Key System service, that is,
the mapping data between short numbers subscribed by all subscribers and
indicator numbers of phone sets.
2.2.7 Setting Dispatch Ability (Optional)

I. Related commands
Command
Function
SET DPA
To set dispatch ability
LST DPA
To list dispatch ability

This configuration step is optional. Read the following descriptions before using the
SET DPA and LST DPA commands.
When you use the ADD BRD command to configure board data, the system
automatically configures the default protocol dispatch ability for IFMI, BSGI and MSGI.
Following are the default values:
Board
Default dispatch ability
IFMI
None
BSGI
MGCP, H.248, SCTP
MSGI
TRIP, ENUM, STUN, MIDCOM, Original call, iDo, SMC, RADIUS
Generally, you can use the default settings directly. To enable a module to dispatch one
or several protocols, use SET DPA.
For example, the BSGI can dispatch MGCP, H.248, and SCTP simultaneously in
normal cases. However, you can enable a certain BSGI to dispatch one protocol
(MGCP, for instance) separately with the command SET DPA.

[Module number]

2-15

It specifies the module number of IFMI, BSGI, or MSGI whose protocol dispatch ability
is to be configured. This parameter is defined in the ADD BRD command and
referenced here.
[Dispatch ability]
It specifies the types of protocols that can be dispatched by a certain board. The
options are SIP, MGCP, H.248, SCTP, TRIP, ENUM, STUN, MIDCOM, and RADIUS.
When setting protocol dispatch ability for a board, note the following:
The BSGI dispatches SIGTRAN protocols, such as M2UA, M3UA, V5UA, and IUA
fixedly. You cannot set them.

z
Besides SIGTRAN, the BSGI can only dispatch MGCP, H.248, and SCTP.
The MSGI cannot dispatch MGCP, H.248, SCTP, or SIGTRAN. However, it can
dispatch any of the other protocols.
Huawei private protocols such as Original call, iDo, and SMC are dispatched by
the MSGI generally, and you cannot set them.

SIP is always dispatched by the MSGI. To enable an MSGI to process SIP, use
the command SET SIPLP.

H.323 is always dispatched by the MSGI. To enable an MSGI to process H.323,
use the command ADD H323APP.
2.3 Configuring E1 Port and Clock Data

2.3.1 Overview
This step is required only when the SoftX3000 needs to provide MTP links to
interconnect SPs, STPs, or SCPs in the SS7 network directly.
II. Configuration steps

Table 2-6 lists the general steps for configuring E1 port and clock data.
Step
Description
Command
Add EPII and CKII board data
ADD BRD
Add EPII E1 configuration
ADD EPICFG
Add board clock reference source
ADD BOSRC
Set CKII clock configuration
SET CKICFG
Set clock reference source of EPII (optional)
SET CLKSRC

2-16

2.3.2 Adding EPII and CKII Board Data

I. Related commands
Command
Function
ADD BRD
To add board data
RMV BRD
To remove board data
LST BRD
To list the board data

The EPII and the CKII are both back boards. When adding the EPII or the CKII, note the
following:
z
The CKII can only be configured in slot 13 and 15 of the rear half part of the basic
frame (frame 0).
The EPII can only be configured after the FCSU is added, and it must be inserted
in the corresponding slot as the FCSU; otherwise, you might fail to add it.

Refer to Section 2.2.4 Adding Board for details.
2.3.3 Adding EPII E1 configuration

I. Related commands
Command
Function
ADD EPICFG
To add EPII E1 configuration
RMV EPICFG
To remove EPII E1 configuration
MOD EPICFG
To modify EPII E1 configuration
LST EPICFG
To list EPII E1 configuration

[Frame number]
It specifies the number of the frame in which the EPII is located. This parameter is
defined in the ADD FRM command and referenced here.
[Slot number]
It specifies the number of the slot in which the EPII is located. By default, two EPIIs in
adjacent slots work as a pair of active/standby boards, for example, the EPIIs in the

2-17

slots 0 and 1 or in the slots 2 and 3. As for the active board, its slot number depends on
the setting here.
If you type, for example, 0, the system treats the EPII in slot 0 as the active board. In
this case, the E1 cable connector of this EPII pair can only be connected with the EPII
in slot 0. If you type, for example, 1, the system treats the EPII in the slot 1 as the active
board. In this case, the E1 cable connector of this EPII pair can only be connected with
the EPII in slot 1. It is recommended to assign the even slot number to the active EPII.
In addition, when you use the ADD EPICFG command to add an E1 port for the active
EPII, the SoftX3000 automatically adds the same E1 port for the standby EPII.
Therefore, you need add it again.
[E1_0 Configuration] to [E1_7 Configuration]
It specifies the frame format of the E1 port. E1_0 represents the E1 port numbered 0,
and E1_7 stands for the E1 port numbered 7. The options are
z
Double-frame format
CRC4 format
Not configured.
[Balance mode]
It defines the electrical features of the E1 port. The options are
z
Balance: It requires the connection to the 120-ohm twisted-pair cable.
Nonbalanced: It requires the connection to the 75-ohm coaxial cable. By default,

this mode is selected.
2.3.4 Adding Board Clock Reference Source (Optional)

I. Related commands
Command
Function
ADD BOSRC
To add board clock reference source
RMV BOSRC
To remove board clock reference source
LST BOSRC
To list board clock reference source

This configuration step is optional. Read the following descriptions before starting the
data configuration:
z
The SoftX3000 might lock the clock of the opposite office through E1 line. That is,
the synchronization networking of the SoftX3000 is Clock of opposite office E1
line EPII CKII. In this case, the ADD BOSRC command should be executed
to define the EPII, which provides input clock signals to the CKII, as the clock
source of the CKII.
2-18

z
The SoftX3000 might directly lock the Building Integrated Timing Supply System
(BITS) clock. That is, the synchronization style is BITS CKII. In this case,
addition of clock reference source is not required.

[Frame number]
It specifies the number of the frame in which the EPII providing clock signals for the
CKII is located. EPII provides the clock reference source. This parameter is defined in
the ADD FRM command and referenced here.
[Slot number]
It specifies the number of the slot in which the EPII is located. You can type the slot
number of the active EPII only. For a pair of active and standby EPIIs, the slot number
of the active one depends on the setting of E1 port in the ADD EPICFG command.
[E1 Number]
It defines the number of the E1 port through which the EPII obtains E1 clock reference
data from the peer end office.
2.3.5 Setting CKII Clock Configuration

I. Related commands
Command
Function
SET CKICFG
To set CKII clock configuration
LST CKICFG
To list CKII clock configuration

If the SoftX3000 is configured with the CKII, you need to set the clock parameters for
the CKII correctly according to the actual synchronization networking mode.

[Clock level]
It indicates that whether the clock of the local office is stratum-2 or stratum-3. If the local
office phase-locks the clock of the upper-level office, the clock level of the local office
should be lower than that of the upper-level office. Generally, it is set to statum-3.
[Work mode]
It specifies whether the external clock reference source of the CKII is to be adjusted
automatically or manually.
z
Automatic: The CKII selects the external clock reference source automatically
based on the preset priorities. Whenever the main clock reference source
2-19

becomes faulty, the CKII selects the spare clock reference source according to the
pre-defined reference source levels.
z
Manual: The CKII can phase-lock the specified external clock reference source
only.
[BITS1 priority], [BITS2 priority], [Line clock1 priority], [Line clock2 priority]
They are valid only when the work mode is automatic. They define the priorities of the
external clock reference sources that are connected to four clock signal input interfaces
on the CKII: Building Integrated Timing Supply System (BITS) 1, BITS2, LINE1, and
LINE2.
When the work mode of the clock is set to Automatic, the CKII automatically selects a
clock reference source with currently the highest priority according to the priority setting
pre-defined for the four inputs of reference signals. If the four reference sources are set
with the same priority, the CKII selects a clock reference source in the sequence from
reference 1 to reference 4.
[Main clock source]
When the work mode parameter is set to manual, this parameter is available to set
the external clock reference source that the CKII phase-locks. The meanings of the
parameter options are as follows:
z
BITS1: The CKII phase-locks the external clock reference source that is
connected to the BITS1 clock signal input interface.
BITS2: The CKII phase-locks the external clock reference source that is
connected to the BITS2 clock signal input interface.
Line clock 1: The CKII phase-locks the external clock reference source that is
connected to the LINE1 clock signal input interface.
Line clock 2: The CKII phase-locks the external clock reference source that is
connected to the LINE2 clock signal input interface.
No reference: The CKII works in the free-run mode.
[BITS1 clock source type], [BITS2 clock source type]

They define the type of allowed external reference signals received from the clock
signal input interfaces, BITS1 and BITS2, on the CKII.
z
2MHz: The type of allowed external reference signals is 2 MHz.
2Mbit/s: The type of allowed external reference signals is 2 Mbit/s.
2.3.6 Setting Clock Reference Source of EPII (Optional)

I. Related commands
Command
Function
SET CLKSRC
To set clock reference source of EPII
LST CLKSRC
To list clock reference source of EPII

2-20


data configuration.
Based on the clock synchronization plan of the SoftX3000, when the CKII is configured,
the EPII in basic frame will lock the clock on CKII directly through the sharing bus. Then,
CKII is the clock reference source of the basic frame.
The CKII provides clock reference for all expansion frames. The EPII of the expansion
frame, normally the EPII of slot 0 or 1, connects to CKII through the clock cable. The
EPII phase locks the CKII directly, and other EPIIs of the frame lock the clock through
the sharing bus. Then, the EPII that directly connects the CKII is regarded as the clock
reference source of the entire expansion frame.
By default,
z
The clock reference source of the EPII in the basic frame is the CKII in the slot 13
(active) and, if the active CKII fails, the CKII in the slot 15 (standby).
The clock reference source of the EPII in an expansion frame is the CKII in the slot
0 (active) and, if the active CKII fails, the CKII in the slot 1 (standby).
Generally, there is no need to configure the clock reference source of the EPII. When
the
actual
hardware
configuration
or
cable
connection
differs
from
the
above-mentioned rules, use the SET CLKSRC command to set the clock reference
source for the EPII.

[Frame number]
It defines the number of the frame that requires the configuration of clock reference
source.
[Slot number 1]
It defines the slot number of the board assigned as the master clock reference source.
[Slot number 2]
It defines the slot number of the board assigned as the slave clock reference source.

2-21

Chapter 3 Configuring Office Data

3.1.1 Local Office Information
The local office information defines the basic information of the SoftX3000 in the SS7
network, including the following:
z
Signaling Point Code (SPC)
SPC length
Signaling network to which the office belongs
Support for signaling transfer function by the office
Maximum delay permitted in long-distance transmission or satellite transmission
3.1.2 Call Source and DN Set

I. Call source code
Call source code refers to the subscriber or trunk that starts the call. The call source is
classified by caller attributes that include pre-received numbers, Dialed Number (DN)
set, route selection source code, failure source code, option to prepare the number,
and option to authenticate caller address.
II. DN set
DN set is the set of number prefixes. Number prefix is the prefix of the number dialed
by the call source. It defines all key factors that are service-related to the call. For
instance, subscriber A has the following authorities.
z
289XXXX: Local call (X stands for any digit from 0 to 9)
838XXXX: Local network call
0AXXX: National toll call (A stands for any digit from 1 to 9)
00AXX: International toll call
For subscriber A, 289, 838, 0 and 00 are prefixes, and they represent different
service attributes. The collection of prefixes is DN set.
III. Global DN set and local DN set

To meet the requirements for different networking models and applications, the DN
set is divided into global DN set and local DN set.
z
Global DN set
A globally significant DN set distinguishes different networks. For example, the

SoftX3000 supports the hybrid of public and private networks. An office can be
3-1

logically divided into public network and private network applications. To identify these
networks, global DN set is used to represent a public or private network.
Local DN set
A locally significant DN set distinguishes different local networks in the same network.
For example, the SoftX3000 supports the application of multiple area codes (or
multiple national codes). That is, the SoftX3000 supports to logically divide the
coverage of the same exchange to several local networks (or several national
networks). To identify these logical networks, the local DN set is used to represent a
local network (or a national network).
IV. Relationship between call source, local DN set and global DN set
Figure 3-1 illustrates the relationship between call source, local DN set and global DN
set.
Local DN
set 0
Call source 0
Global DN
set 0
Call source 1
Local DN
set 1
Call source 2
Call source 3
Local DN
set 2
Global DN
set 1
Call source 4
Figure 3-1 Relationship between call source, local DN set, and global DN set
z
A call source belongs to one local DN set only; one local DN set can be shared by
multiple call sources.
A local DN set belongs to one global DN set only; one global DN set can be
shared by multiple local DN sets.
DN set is classified by the analysis of called prefixes; call source is classified by

call attributes.
The range of DN set includes that of the call source. DN set refers to the
collection of all the valid prefixes open to subscribers. The subscribers can be
divided into different caller groups by call attributes such as different receiving
digits of prefix. Each subscriber group corresponds to a call source.
The DN set is necessary because the same prefix has different meanings to
different call sources. For instance, prefix 222 means local office calls to call
source 0, but means outgoing office calls to call source 3.

3-2

z
When the subscriber calls the prefix of non-global DN set, global DN set
conversion is required. For instance, the subscriber of public network calls the
subscriber of a private network.
3.2 Configuring Office Data

3.2.1 Overview
The office data is one of the basic data of the SoftX3000, used to define the office data
including Destination Point Code (DPC), global DN set, local DN set, country or region
code, national area code, call source code, and subscriber number segment. The
configuration of office data starts after the configuration of equipment data. Refer to
Figure 3-2 for details.
Start
Equipment data
Trunk data
Office data
Number analysis
Charging data
Subscriber data
MG data
Centrex data
MRS data
Call barring data
Protocol data
IN service data
Signaling data
Other service data
Routing data
Other application
data
End

During the process of the SoftX3000 data configuration, some parameters defined
during the configuration of charging data are referenced when you configure MG data,
MRS resource data, protocol data, signaling data, trunk data, and subscriber data.
The referencing relationship is presented as broken lines in Figure 3-2. Refer to

3-3

Table 3-1 Parameter referencing relationship between office data and other data
Input parameter
Output parameter
Name
Defined in
Name
Referenced in
Number
change
index
(optional)
Number
analysis
data (ADD
DNC)
Signaling Point
Code (SPC)
Signaling data, trunk data, IN

service data, and IPN service data
Local DN set
Trunk data, number analysis data,

subscriber data, Centrex data, call
barring data, and other service
data
Global DN set
Number analysis data and other

service data
Call source code
Trunk data, number analysis data,

subscriber data, Centrex data, call
barring data, and other service
data
Route selection
source code
Routing data
Failure
code
Number analysis data
source
Note:
If number preparation is required before adding the call source code with the ADD
CALLSRC command, execute the ADD DNC command to define the parameter
number change index before the parameter is referenced in other steps.
II. Preparations
Before configuring office data, make sure that all preparations are done as specified
in Table 3-2.
SN
Item
Remark
SPC
To configure MTP-related data
Planning Global DN set
To validate the multiple national/region code

supported
Planning local DN set
To validate the collection of prefixes that is

valid to the subscriber.
Planning call source code
To distinguish caller groups

3-4

SN
Item
Remark
Planning number segment
To validate number resources that the office

use
Preparing national toll zone

prefixes for all cities.
It is prepared during system initialization. This

step is necessary only when the SoftX3000 is
used outside China.

Table 3-3 lists the general steps for configuring office data.
Step
Description
Command
Set local office information
SET OFI
Add local office signaling point code (optional)
ADD OFI
Modify local office assistant code (optional)
MOD OFI
Add country or region code (optional)
ADD NCODE
Add national area code
ADD ACODE
Add toll prefix description
ADD PFXTOL
Add local DN set
ADD LDNSET
Add call source code
ADD CALLSRC
Add subscriber number segment
ADD DNSEG
10
Set daylight saving time (optional)
SET DST

you configure office data.

3-5

ADD NCODE
[DnSet]
[Nation/Region code]
[Nation/Region name]
ADD ACODE
[DnSet]
[National toll zone code]
ADD CALLSRC
ADD PFXTOL
[Call source]
[DnSet]
[Call source name]
[Local DnSet]
[National toll Prefix]

[International toll Prefix]
ADD
DNSEG
ADD LDNSET
[Local DnSet]
[Local DnSet]
[DnSet]
[Start number]
[End number]
[National toll zone code]
3.2.2 Setting Local Office Information

I. Related commands
Command
Function
SET OFI
To set local office information
LST OFI
To list local office information

[Local office name]
It identifies the local office in character string.
[Local office type]
It defines the office type as
z
PBX
Local/rural call office

3-6

z
Toll, urban & rural call office
National toll office
International toll office
Manual toll office
[International network valid], [International reserved network valid], [National network

valid], [National reserved network valid]
Select from the four parameters to determine the signaling network in which the local
office is valid.
z
International network valid: It means that the local office is an international

signaling network and occupies SPC resources of the international signaling
network. In this case, the local office interconnects with other offices in
quasi-associated mode.
International reserved network valid: It means that the local office is in an

international reserved signaling network but occupies no SPC resources of the
international signaling network. In this case, the local office interconnects with
other offices in associated mode.
National network valid: It means that the local office is in a national signaling
network and occupies SPC resources of the national signaling network. In this
case, the local office interconnects with other offices in quasi-associated mode.
National reserved network valid: It means that the local office is in a national
reserved signaling network but occupies no SPC resources of the international
signaling network. In this case, the local office interconnects with other offices in
quasi-associated mode.
An office can be valid in four signaling networks simultaneously, and their SPCs shall
conform to different rules for the different networks. Refer to descriptions of other
parameters in this section.
[First search network], [Second search network], [Third search network], [Fourth
search network]
These four parameters are valid when there are two or more signaling connections
between the local office and a certain Signaling Point (SP) in the signaling network.
They define the sequence when the office is searching the signaling network.
For instance, the local office and another office A are both in national network and
national reserved network. The two offices can exchange signaling in the two
networks. When the first search network is set to national network, and second search
network is set to national reserved network, the signal routing from local office to
office A will be national network; when national network is faulty or congested, the
national reserved network is selected.
[International network code], [International reserved network code], [National network
code], [National reserved network code]

3-7

These four parameters define the SPC of the local office in different signaling
networks. They are hexadecimal values, ranging from 0 to 999999.
[International network structure], [International reserved network structure], [National
network structure], [National reserved network structure]
These four parameters specify the SPC length, which varies in different nations. For
instance, the following specifications are applicable in China.
z
International network structure: specified in ITU-T Recommendations to 14
International reserved structure: 24 (recommended and can be customized)
National network structure: specified by Ministry of Information Industry to 24
International reserved structure: 14 (recommended and can be customized)
[Allowed transmission delay]

It defines the allowed transmission delay (in seconds) of MTP links in the signaling
network. By default, it is set to 0. Generally, it is applicable to MTP links in extra-long
distance transmission or satellite transmission.
[SP function]
It indicates whether this switch has signaling point function or not. This field is usually
set to YES.
[STP function]
It indicates whether this switch has signaling transfer point (STP) function. Usually, it
is set to NO. When local office is an STP, this field should be set to YES.
[Restart function]
It indicates whether this switch has restart function or not. This field is valid only when
the field STP function is set to YES.
Restart function is necessary as one of MTP signaling traffic management functions.
The core of the function is the exchange of network states between the restarted
signaling point and its adjacent signaling points. If a signaling point is isolated from the
signaling network so long that a particular threshold exceeds, when the transmission
of user traffic is restored, the signaling point cannot judge the validity of the previously
used routing data because potential routing errors might cause the loss of user traffic.
To avoid the loss, the signaling point must provide enough restart time to activate
enough signaling links and exchange enough routing data before the user traffic is
restored.
[Packet network access code]
Generally, this field is to indicate the packet access function provided by the local
switch.
[CFNR to voice mailbox], [CFB to voice mailbox], [CFU to voice mailbox]
When it is required to deploy Call Forwarding No Reply (CFNR) to voice mailbox, Call
Forwarding Busy (CFB) to voice mailbox, or Call Forwarding Unconditional (CFU) to

3-8

voice mailbox service for local office subscribers, these parameters specify the
respective access code to the voice mailbox service. Through the access code, the
SoftX3000 automatically routes to the voice mailbox based on number analysis table,
route analysis table, and trunk group table.
[Internal MGW media type]
It indicates the signaling bearer mode of the SoftX3000 when the SoftX3000
interconnects with external gateways. It can be IP, ATM, or TDM. By default, it is IP.
[Time zone]
It indicates the time zone where the local office is located. Its value range is 0 to 99.
By default, it is 0.
[Common language location identification]
As one of the parameters for the SoftX3000 to interwork with the switch applying ISUP
defined by ANSI, it identifies the location of the local office. The local office location is
allocated by the network uniformly.
It is valid only in ISUP defined by ANSI and indicates the location identification in the
CVR message set by the local office in the CVT/CVR procedure. It is composed of a
maximum of 11 characters. The default value is Anonymous.
[CPU rate for ACC level 1]
When the CUP rate of the local office reaches this threshold, the local office will send
an Automatic Congestion Control (ACC) message to all interconnected peer offices
through SS7 to notify them that ACC level 1 occurs in the local office. The value range
is 0100 in unit of %.
[CPU rate for ACC level 2]
When the CUP rate of the local office reaches this threshold, the local office will send
an Automatic Congestion Control (ACC) message to all interconnected peer offices
through SS7 to notify them that ACC level 2 occurs in the local office. The value range
is 0100 in unit of %.
[Active linkset percent for restart]
It specifies the minimal percent of MTP linksets that must be activated by the local
office to enable signaling transmission when the local SP is available and restarted.
When Active linkset percent for restart and Receive TRA percent for restart are
both satisfied, the local office starts signaling transmission. This parameter ranges
from 0 to 100 in unit of %. It is 100 by default.
[Receive TRA percent for restart]
It specifies the minimal percent of TRA messages that must be received by the local
office to enable signaling transmission when the local SP is available and restarted.
When Active linkset percent for restart and Receive TRA percent for restart are
both satisfied, the local office starts signaling transmission. This parameter ranges
from 0 to 100 in unit of %. It is 100 by default.
3-9

[Local office CAC]

It defines the carrier access code of the local office, ranging from 0 to 9 and A to E with
the maximum length of 6 characters. You cannot set it arbitrarily, but it is allocated
uniformly by the telecom department on nation-wide basis.
The carrier access code is used by the gateway office to authenticate a pre-selected
call. That is, you can set this parameter only when the local office serves as a gateway
office.
z
When the local office starts a call to the peer gateway office, and the ISUP
outgoing trunk group includes the carrier selection code (required by ADD
TGAP), the SoftX3000 shall include the Local office CAC parameter (from the
office information table, defined by SET OFI) in the IAM message in the ISUP
outgoing trunk direction.
When the local office receives a call from the peer gateway office, and its ISUP
trunk group has been configured with authentication information using ADD CAC,
the SoftX3000 shall start CAC authentication for the calls from the ISUP
incoming trunk. The basic authentication procedure is as follows:
1)
After receiving the IAM containing "carrier selection code" from the peer office,
the local office judges if the carrier selection code in the IAM is the same as the
"Local office CAC" in the local office information table (which can be configured
with the command SET OFI). If so, the authentication succeeds, and the local
office will delete the parameter "carrier selection code" in the IAM when
transferring the message to the lower-level office. If not, carry out the following
actions.
2)
The local office judges if the carrier selection code table (which can be
configured with the command ADD CSC) contains the "carrier selection code" in
the IAM. If so, the authentication succeeds, and the local office will transparently
transfer the IAM to the lower-level office. If not, the local office will reject the call.
[Local office ONID]

It defines the originating network identifier of the local office, ranging from 0 to 9 and A
to E with the maximum length of 6 characters. Currently, a length of only three
characters is supported in Germany. It is used by the peer office to authenticate a
pre-selected call. The basic authentication procedure is as follows:
z
When a local caller uses the pre-selection service, the local office (that is,
originating office) will send an IAM containing this parameter in the local office
information table (which can be set with the command SET OFI) through the
outgoing trunk. This parameter will be transmitted transparently to the
terminating office finally during the call connection process.
Upon receiving the IAM, the terminating office judges if the originating network
identifier table (which can be set with the command ADD ONID) contains this
parameter in the IAM. If so, the authentication succeeds, and the terminating

3-10

office will connect the call. If not, the terminating office will release the call (the
release cause value is 21).
By default, the SoftX3000 does not authenticate the ONID for calls of pre-selected
routes. When you set the bit7 of call internal parameter 8 (P122) to 0, the SoftX3000
shall authenticate the ONID of the calls from the ISUP incoming trunk.
3.2.3 Adding Local Office Signaling Point Code (Optional)

I. Related commands
Command
Function
ADD OFI
To add local office signaling point code
RMV OFI
To remove local office signaling point code
LST OFI
To list local office signaling point code

data configuration.
Restricted by the 12-bit length of CIC in SS7, when two offices use a single SPC only,
there can be a maximum of 4096 trunk circuits between them. It does not meet the
capacity requirement of trunk networking, for example, in gateway office. To exceed
the limitation, the SoftX3000 provides the multiple SPC function. A maximum of 254
SPCs can be configured for the local office, and theoretically one million No. 7 trunk
circuits can be deployed between the local office and the peer end office with a single
SPC.
Execute the ADD OFI command to add OPC before enabling multiple SPC service.

[OPC index]
It uniquely identifies an OPC in the SoftX3000. The value range is 1 to 253, indicating
that a maximum of 253 SPCs can be configured in ADD OFI. In SET OFI, the OPC
index is fixed at 0.
[International network code]
It defines the SPC of the SoftX3000 in international network. According to ITU-T
Recommendations, it should be 14 bits in length.
[International reserved network code]
It defines the SPC of the SoftX3000 in international reserved network. According to
ITU-T Recommendations, it can be 24 bits or 14 bits in length.
[National network code]
3-11

It defines the SPC of the SoftX3000 in national network. The coding can be
user-defined. For instance, in China it is 24 bits in length.
[National reserved network code]
It defines the SPC of the SoftX3000 in national reserved network. According to ITU-T
Recommendations, it can be 24 bits or 14 bits in length.
[Master/Slaver flag]
This parameter specifies whether the data record defined in the command belongs to
the local office or the assistant office. The meanings of the parameter options are as
follows:
z
Master: This record of data belongs to the local office and is always valid.
Slave: This record of data belongs to the assistant office and is valid only when
the local office is operating in the mutual assistance active state.
The default option of the parameter is master, indicating this record of data belongs
to the local office. When you want to configure dual homing data for the assistant
office, this parameter is set to slaver.
3.2.4 Modifying Local Office Assistant Code (Optional)

I. Related commands
Command
Function
MOD OFI
To modify local office assistant code
LST OFI
To list local office assistant code

data configuration.
Suppose the multi signaling point code service is deployed in the local office. The
local office has two originating point codes (A and B) and one destination point code
(C). Normally, signaling route from A to C is independent of the signaling route from B
to C. There is no backup relationship between the signaling routes to different
destinations. To further improve the reliability from the local office to the destination
office, the SoftX3000 provides mutual assistance function between the multiple
signaling point codes. Whenever the signaling route from A to C becomes faulty, the
signaling traffic from A to C is automatically taken over by the signaling route from B to
C. Likewise, whenever the signaling route from B to C becomes faulty, the signaling
traffic from B to C is automatically taken over by the signaling route from A to C.
To define an assistant node for an originating point code of the local office, execute
the MOD OFI command to modify the local office information.
3-12


[OPC index]
This parameter specifies the OPC index to the originating point code for which the
assistant node is to be added. This parameter should be defined first in the SET OFI
or ADD OFI command and then referenced here.
[Assistant node 1 network indication], [Assistant node 2 network indication]
Each of these parameters specifies the signaling network where the signaling point
code of the assistant node is resident. It might be an international network, an
international reserved network, a national network, or a national reserved network.
The setting of the signaling network the assistant node is resident must keep
consistent with that of the signaling network the served node is resident. Otherwise,
this piece of data is considered invalid.
[Assistant node 1 code], [Assistant node 2 code]
Each of these parameters specifies the signaling point code of the assistant node.
The configuration principles of this parameter are as follows:
z
There is no sequence difference between assistant node 1 and assistant node 2.

The numbers do not indicate the sequence in which the assistant nodes provide
assistance.
If an originating signaling point has two assistant nodes, signaling traffic are
shared between them.
If you want to set one assistant node for an originating signaling point, you can
set it either in Assistant node1 network indication and "Assistant node1 code"
or in Assistant node2 network indication and "Assistant node2 code". If you
want to set two assistant nodes for an originating signaling point, you must set
them in the same execution of the command. The settings in the second
execution of the command will replace those in the previous execution of the
command. The former settings will not be retained.
If you want to cancel the assistance relationship, execute this command too. If
you want to cancel all assistant nodes, set the Assistant node1 code parameter
to 0. If you want to cancel one of the assistant nodes, execute MOD OFI again
to define the retained node.
If you have defined an assistant node B for the originating signaling point A of the
local office, the assistance relationship is available to all offices that have a
signaling route to the originating signaling point A. In addition, the assistance
relationship is available to the four signaling networks (international network,
international reserved network, national network, and national reserved
network).
If you enable the mutual assistance function for the multiple originating point
codes in the local office, make sure that the opposite office are cooperating in
signaling and routing aspects. For example, the originating point codes A and B
3-13

of the local office are mutual assistant nodes. In the opposite office, accordingly,
the destination signaling points A and B must be set to have STP functions. In
addition, two alternative routes have to be added: one is destined to B through A
and the other is to A through B.
3.2.5 Adding Country or Region Code (Optional)

I. Related commands
Command
Function
ADD NCODE
To add country or region code
RMV NCODE
To remove country or region code
LST NCODE
To list country or region code

data configuration.
Generally, the country or region code data is set during system initialization and the
additional configuration is not required. If the multi-nation code/multi-region code
service is required, execute the ADD NCODE command to add new country or region
codes.

[ DN set]
It defines the global DN set to which the country or region code belongs. During
system initialization, a global DN set 0 is defined and is referenced directly during
subsequent data configurations. To add another global DN set, execute the ADD
NCODE command.
[Country/Region code]
It defines the country or region code that belongs to the global DN set.
[Country/Region name]
It is the country or region name that the code represents.
3.2.6 Adding National Area Code (Optional)

I. Related commands
Command
ADD ACODE
Function
To add national area code

3-14

Command
Function
RMV ACODE
To remove national area code
LST ACODE
To list national area code configuration

data configuration.
Generally, the national area code is set during system initialization and the additional
configuration is not required. To enable multi-national area code service, or use the
SoftX3000 outside China, execute the ADD ACODE command to add additional
domestic toll zone codes.

[DN set]
It defines the global DN set to which the national area code belongs. During system
initialization, a global DN set 0 is defined and is referenced directly during subsequent
data configurations. If the national area code belongs to another global DN set, the
parameter is defined in the ADD NCODE command and referenced here.
It defines the national area code that belongs to the global DN set. When the global
DN set is not 0, this parameter is defined in the ADD NCODE command and
referenced here.
[National area code]
It defines the national area code that corresponds to the global DN set and country or
region code.
[City name]
It is the name of the city owning the national area code.
[District code]
It identifies the administrative regions in the city. This field is user-defined.
3.2.7 Adding Toll Prefix Description (Optional)

I. Related commands
Command
Function
ADD PFXTOL
To add toll prefix description
RMV PFXTOL
To remove toll prefix description

3-15

Command
Function
LST PFXTOL
To list toll prefix description

data configuration.
Generally, the toll prefix is set during system initialization, and the additional
configuration is not required. To enable multi-national area code service, or use the
SoftX3000 outside China, execute the ADD PFXTOL command to configure
additional toll prefix descriptions.

[DN set]
It defines the global DN set to which the country or region code belongs in the
command. During system initialization, a global DN set 0 is defined and is referenced
directly during subsequent data configurations. To configure another toll prefix
description, the parameter is defined in the ADD NCODE command and referenced
here.
It defines the national area code that the toll prefix describes. When the global DN set
is not 0, this parameter is defined in the ADD NCODE command and referenced here.
[National toll prefix]
It specifies the prefix dialed by a local office user for making a national toll call.
Generally, it is set to 0.
[International toll prefix]
It specifies the prefix dialed by a local office user for making an international toll call.
Generally, it is set to 00.
3.2.8 Adding Local DN Set

I. Related commands
Command
Function
ADD LDNSET
To add local DN set
RMV LDNSET
To remove local DN set
LST LDNSET
To list local DN set configuration

3-16


[Local DN set]
It defines the local DN set used during called number analysis.
[DN set]
It refers to the global DN set to which the local DN belongs. During system
initialization, a global DN set 0 is defined and is referenced directly during subsequent
data configurations. If the local DN set belongs to another global DN set, the
parameter is defined in the ADD NCODE command and referenced here.
It specifies the country or region code to which the local DN set belongs. When the
global DN set is not 0, this parameter is defined in the ADD NCODE command and
referenced here.
[National area code]
It specifies the national area code to which the local DN set belongs. When the global
DN set is not 0, this parameter is defined in the ADD ACODE command and
referenced here.
[Local DN set name]
It describes the local DN set. The field type is character string.
[H248 digit map]
It defines the digit map of the H.248 protocol corresponding to the above local DN set.
For details about the meaning of the characters in the digit map, refer to chapter 11
Configuring Number Analysis Data of this manual.
[MGCP digit map]
It defines the digit map of the MGCP corresponding to the above local DN set. For
details about the meaning of the characters in the digit map, refer to chapter 11 of this
manual Configuring Number Analysis Data.
3.2.9 Adding Call Source Code

I. Related commands
Command
Function
ADD CALLSRC
To add call source code
RMV CALLSRC
To remove call source code
MOD CALLSRC
To modify call source code
LST CALLSRC
To list call source code

3-17


[Call source code]
It defines a call source uniquely in the SoftX3000. The value range is 0 to 65535.
Because a call source is a collection of callers with different attributes, you need to
define different call source codes if differences exist in number of pre-received digits,
local DN set, outgoing route selection, failure processing mode, and number
preparation mode.
[Call source name]
It identifies a call source with a string of characters.
[Pre-received digits]
It indicates the minimum number of digits received to activate number analysis in the
SoftX3000. That is, if the number of digits sent by a local subscriber or incoming trunk
is less than that of pre-received digits, the SoftX3000 does not start number analysis.
The parameter ranges from 0 to 7. By default, it is set to 1. Set this parameter by the
following principles:
z
For ordinary subscribers, it is generally set to 3. For instance, when you dial
28970001, as soon as the first three digits, 289, are dialed, the system starts
number analysis.
For Centrex subscribers, it is usually set to 1. When the outgoing prefix is dialed,
the second dialing tone will be heard. Therefore, an additional call source code is
set for Centrex subscribers.
[Local DN set]
It defines the local DN set to which the call source code belongs. This parameter is
defined in the ADD LDNSET command and referenced here.
[Time zone]
It identifies the time zone where the calling subscribers of a specific call source is
located, ranging from 0 to 99. It is 0 by default.
[Route selection source code]
It defines the category number of the routing policy for outgoing calls from the call
source. The route selection source of callers with different call attributes is different.
When the subscribers of two call sources dial the same outgoing prefix of one DNSet,
different route selection source codes can be allocated to the two call sources if the
routing policies are different. The parameter ranges from 0 to 65535. It will be
referenced in the command ADD RTANA.
[Failure source code]
It classifies call sources according to the failure processing method adopted. The
parameter ranges from 0 to 255. It will be referenced in the command ADD CFPRO.
[Number preparation]
3-18

It indicates whether the call processing software changes the called number before
number analysis. It is set to No by default. The parameter is used in some special
cases, for instance, when a universal access code is to be added to the numbers of all
pre-paid service subscribers.
Number preparation is a type of number change, but with higher priority. During billing
process, the called number is listed as the changed number in the bill.
[All number change index]
When number preparation is set to YES, this parameter is available to specify a
number change index for all called numbers. This parameter is defined in the ADD
NDC command and referenced here. The configuration principles of this parameter
are as follows:
z
When no number preparation is required, leave the field blank.
Among the several number change indexes referenced in this command, the all
number change index has the lowest priority and the system preferentially
attempts to match other number change indexes.
[International number change index]

number change index for called numbers that are international significant numbers.
This parameter is defined in the ADD NDC command and referenced here. The
configuration principles of this parameter are as follows:
z
Among the several number change indexes referenced in this command, the
international number change index is prior to the all number change index.
[National number change index]

number change index for called numbers that are national significant numbers. This
parameter is defined in the ADD NDC command and referenced here. The
configuration principles of this parameter are as follows:
z
national number change index is prior to the all number change index.
[Subscriber number change index]

number change index for called numbers that are subscriber numbers including
special service numbers. This parameter is defined in the ADD NDC command and
referenced here. The configuration principles of this parameter are as follows:
z
subscriber number change index is prior to the all number change index.
3-19

[Caller address discrimination]

It specifies how the system filters the calling number based on its attributes. The
choices are
z
Not identifying: Do not discriminate.
Reject call if not consistent: If the nature of address of the caller number sent by
the opposite office through an incoming office signaling message is not
consistent with the actual number length, the call will be refused. Two cases may
occur:
a) If the received caller number from the opposite office is shorter than or equal to the
maximum length defined for local numbers (which is determined by a software
parameter and is 8 digits by default), the nature of address of the caller number
must indicate a subscriber number; otherwise, the local office will reject the call.
b) If the received caller number from the opposite office is longer than the maximum
length defined for local numbers, the nature of address of the caller number must
indicate a national or international number; otherwise, the local office will reject
the call.
z
Modify address nature if not consistent: If the nature of address of the caller
number sent by the opposite office through an incoming office signaling
message is not consistent with the actual number length, the system will modify
the nature of address of the caller number before other call processing. Two
cases may occur:
maximum length defined for local numbers, the system will modify the nature of
address of the caller number to a subscriber number.
length defined for local numbers, the system will modify the nature of address of the
caller number to a national or international number.
z
Only allow national and international number: If the nature of address of the
caller number sent by the opposite office through an incoming office signaling
message does not indicate a national or international number, the local office will
reject the call.
Change to subscriber number: If the national toll area code in the caller number
sent by the opposite office through an incoming office signaling message is the
same as the national toll area code defined for local office subscribers, the caller
number will be changed to a subscriber number without area code. If they are the
same, no modification will be made.
Change to toll number without 0: If the nature of address of the caller number
sent by the opposite office through an incoming office signaling message
indicates a national number, the received caller number is changed to a national
number without 0.

3-20

z
Change to toll number with 0: If the nature of address of the caller number sent
by the opposite office through an incoming office signaling message indicates a
national number, the received caller number is changed to a national number
with 0.
Change international toll number without 0: If the nature of address of the caller
message indicates an international number, the received caller number is
changed to an international number without 00.
Change international toll number with 0: If the nature of address of the caller
message indicates an international number, the received caller number is
changed to an international number with 00.
[HongKong NP flag]
It indicates whether the call processing software starts Hong Kong NP service
analysis for specific calls originated by a call source. It is set to No by default. It is
applicable to the called NP service in NP server mode but not that in SHLR or SCP
mode. Set this parameter by the following principles:
z
If the Hong Kong NP service is not needed, set the Hong Kong NP analysis flags
of all call sources to No".
If the Hong Kong NP service is needed, set the Hong Kong NP analysis flags of
the call sources to which the local subscribers belong to "Yes.
If the Hong Kong NP service is needed, for some incoming trunk calls, if the
opposite office has implemented the Hong Kong NP service analysis procedure
for a call prefix, the local office need not implement this procedure any more. In
this case, you must set the Hong Kong NP analysis flags of the call sources to
which incoming trunks belong to No.
If the Hong Kong NP service is needed, for some incoming trunk calls, if the
opposite office dose not implement the NP service analysis procedure for a call
prefix, the local office needs to implement this procedure. In this case, you must
set the Hong Kong NP analysis flags of the call sources to which incoming trunks
belong to Yes.
The system starts the Hong Kong NP service analysis procedure for a call prefix
dialed by a call source only after you set the Hong Kong NP analysis flag of the call
source to Yes and set NP server query for the call prefix using ADD CNACLD.
[UC analysis flag]
It specifies if the call processing software starts the called UC service analysis
procedure for calls originated by a call source. It is No by default.
The system starts the called UC service analysis procedure for a call prefix dialed by a
call source only after you set the UC analysis flag of the call source to Yes and set
UC server query for the call prefix using ADD CNACLD.

3-21

[SHLR select source code]

It defines the category number of the SHLR selection policy made by the call source
(subscriber or incoming trunk). It ranges from 0 to 65535. By default, it is set to 65535,
meaning that the call source has no authority to select SHLR. This parameter are
referenced in ADD SHLRCFG and ADD SHLRSRVC.
3.2.10 Adding Subscriber Number Segment

I. Related commands
Command
Function
ADD DNSEG
To add subscriber number segment
RMV DNSEG
To remove subscriber number segment
LST DNSEG
To list subscriber number segment configuration

[Local DN set]
It defines the local DN set to which the subscriber number segment belongs. This
parameter is defined in the ADD LDNSET command and referenced here.
[Start number], [End number]
They define the start and end of the subscriber number segment.
[Start subsciber index]
It defines the index value of start number in the subscriber data index table. Index
numbers of other subscribers of the segment are counted up in ascending order. This
parameter does not require your input. It is specified by the system based on the
sequence of the multiple implementations of ADD DNSEG, and the segment range.
For instance, three number segments are configured in the following sequence:
ADD DNSEG: LP=0, SDN=K'26540000, EDN=K'26540199;
The start subscriber index for the first implementation is 0 always (defined by the
system). The start subscriber index for the second implementation is 200 (one plus
the index value assigned for the last subscriber in the first segment). The start
subscriber index for the third implementation is 1200 (one plus the index value
assigned for the last subscriber in the second segment).
[Master/Slaver type]

3-22

follows:
z
Slave: This record of data belongs to the assistant office and is valid only when
the local office is operating in the mutual assistance active state.
The default option of the parameter is master, indicating this record of data belongs
to the local office. When you want to configure dual homing data for the assistant
office, this parameter is set to slave.
3.2.11 Setting Daylight Saving Time (Optional)

I. Related commands
Command
Function
SET DST
To set daylight saving time
LST DST
To list daylight saving time

data configuration.
When the country or area where a carrier is located applies the daylight saving time,
use SET DST to set the parameters for adjusting the daylight saving time, such as
start date, start time, end date, end time, and offset hour.

[Start date], [Start time]
They specify the specific date and time when the daylight saving time starts. Specify
the start date in format of MM&DD, where MM stands for month and DD for day.
[End date], [End time]
They specify the specific date and time when the daylight saving time ends. Specify
the end date in format of MM&DD, where MM stands for month and DD for day.
[Offset hour]
It specifies the offset hour of the daylight saving time to the standard time. It is an
integer ranging from 6 to 6. Set this parameter by the following principles:
z
When the BAM time reaches the start date and start time of the daylight saving
time, the BAM will automatically adjust the current system time to start time +
offset hour.

3-23

z
When the BAM time reaches the end date and end time of the daylight saving
time, the BAM will automatically adjust the current system time to end time
offset hour.
[Usage flag]
It indicates whether the system supports the daylight saving time. It is Enable by
default. If it is set to Disable, the data configured with SET DST is invalid.
[Current time status]
It is available only when the BAM time is within the adjust time segment between the
daylight saving time and the standard time, indicating if the current BAM time is
daylight saving time or not.
For example, a carrier sets to start the daylight saving time from 8:00 on June 1, and
sets the offset hour to 1, that is, the BAM time will be changed to 7:00 when the start
time arrives. If you use SET DST to set the daylight saving time data between 7:00
and 8:00 on June 1, you must confirm whether the current BAM time has been
changed to the daylight saving time.
z
If "Stop is selected, it means that the current BAM time has not been changed
yet, and the BAM will automatically adjust the time to the daylight saving time at
8:00.
If Run is selected, it means that the current BAM time has been changed to the
daylight saving time, and no adjustment will be carried out at 8:00.

3-24

Chapter 4 Configuring Charging Data

4.1.1 Charging Concepts
I. Detailed ticket
The detailed ticket is one of the charging modes in the SoftX3000. It records charging
information of a call including the caller number, callee number, answer time, hang-up
time, conversation duration, and service attribute. It is used for toll call charging.
II. Charging meter

The charging meter is used as a charging mode in the SoftX3000. The system judges
the call prefix and service attributes, and converts the conversation duration into meter
counts.
The charging meter is used in local call charging. It accumulates the meter counts over
a period, generates a meter bill at certain time, and resets the meter.
III. Alarm bill

Alarm bill is a kind of call record in a certain format in prevention of bill loss when the
system cannot match any charging data for a call, including such information as calling
number, called number, answer time, and onhook time.
IV. Failure bill

Failure bill is a kind of call record generated to avoid bill loss in the case of call failures
occurring to a specific caller, callee, or trunk group.
V. Watch bill
Watch bill is also a kind of call record. It records the call information of specific callers,
callees, or trunk groups in the case of call failure, thus providing original data for such
activities as analysis of call completion rate and call watch. Different from failure bill,
watch bill is not used for charging.
VI. Segment bill

Segment bill is an intermediate bill outputted during a long call, recording some
information of the call periodically. When the call ends, the system generates a
complete bill finally. If an accident, for example, loss of onhook signal, occurs during the
call, segment bills can reduce the economical loss of carriers.

4-1

In application, you can use ADD TCTRL to control whether segment bills or complete
bills is used as detailed bills for charging.
VII. Charging complaint (complaint bill)

Charging complaint is an attribute of the subscriber and the trunk group. In case of
dubious charge, the charging complaint is used to query the charge of each call
intended for the subscriber or trunk group. When the charging complaint flag of a
subscriber or a trunk group is set to Yes, a complaint bill is generated together with
charging meter bills or detailed ticket. The complaint bill shares the same content as the
detailed ticket.
VIII. Charging category

It defines the meaningful subscriber charging attributes network-wide in the subscriber
data. Meaningful network wide means the outgoing connection sends the charging
category out and requests other exchanges to interwork with the operation of this call,
in addition to the specific operations on the charging category by the local exchange.
The charging categories defined in the SoftX3000 are period, immediate subscriber
table, "immediately sending to printer", and free.
z
Period: The charge is rendered regularly.
Immediate subscriber table: During conversation, the system periodically (for

example, every 60 seconds) sends charging pulse to the subscribers phone set. It
is mainly applicable to unattended public telephones.
Immediately sending to printer: When the call ends, the system immediately sends
bills to the subscribers phone set or the attendant console. This mode is used in
instant billing at attended public telephones.
Free: The free calls require no payment from caller party after service analysis,
such as police call, fire emergency call, ambulance emergency calls, traffic
accident calls, FPH calls, and collect calls. For calls defined as free in charging
category, the detailed call information of the caller is still recorded and the free call
detail record is generated.
IX. Conversation fee

It is calculated based on the resources occupied during the call such as distance,
duration, and number of channels, according to the uniform calculation specifications.
X. Additional fee
It is the fee added to the conversation fee as specified. The SoftX3000 only calculates
the additional fee of immediate sending to printer calls; the additional fee of period is
given by the offline charging system.

4-2

XI. No charge
It means that no call information is recorded, no call detail record is generated, and
there is no meter count.
No charge is for calls that are already charged in another office, and leave no record in
the office as specified by the service provider. For instance, the local calls are charged
in originating local office, the national toll calls are charged in originating toll office, and
the international toll calls are charged in originating toll office and international office.
XII. Caller charging

The originating party (subscriber or incoming trunk) bears part or all of the expense of
the call. When no intelligent services such as called charging is configured in the local
office, the caller should be charged for the call, except for the free calls.
XIII. Called charging

The called party (subscriber or outgoing trunk) bears part or all of the expense of the
call. In the SoftX3000, the called charging is caller-independent. A subscriber defined
as called charging is charged at the same tariff regardless of a local call or a toll call
that the subscriber receives.
XIV. Third party charging

It means that the fee is covered by a third party rather than the caller or the callee.
There are four types of third party charging.
z
On a third subscriber
The call is covered by a third subscriber whose number is specified in the bill. This
charging mode is implemented in offline charging, and is suitable for enterprise
subscribers. Call charges of all enterprise members are covered by one number.
z
On account card
The call is covered by an account card, whose number is specified in the bill. This
charging mode is implemented in offline charging, and is suitable for enterprise
subscribers as well as individual subscribers.
z
On Centrex group number
Centrex groups are organizations like enterprises, schools, hospitals, and government
organizations. All call charges of the Centrex group can be covered by a Centrex group
identifier. This mode is suitable for Centrex call charging.
z
On bank account
The call is covered by a bank account, whose account number is specified in the bill.
This charging mode is implemented in offline charging, and is suitable for enterprise
subscribers as well as individual subscribers.

4-3

XV. CRG charging

It is a charging process based on charging signaling messages. To be specific,
charging is implemented through the transmission of ISUP messages between offices
such as Charging Information Message (CRG), Charging Band Message (CHB),
Charging Information Message (CHG), Tariff Chang Message (TAC), Charging Unit
Message (CHU), and Charging Pulse Message (CHP). Comparing to the independent
charging modes, CRG charging requires the coordination of charging signaling among
all interworked offices in the network.
XVI. Centralized charging

It is to charge the incoming calls (typically tandem calls) from subscribers of other end
offices in the local network in a superior office (tandem or toll office). It is impossible for
the centralized charging office to have the charging meters of all the subscribers, so the
detailed bill charging mode is adopted.
The centralized charging is based on trunk charging. During charging analysis, the
SoftX3000 uses the charging source code of the incoming trunk. Different charging
source code can also be differentiated according to the prefix of the caller, so as to
charge distinctively.
The centralized charging is different from incoming trunk charging. The former
generates two billsone is trunk bill and the other is normal bill. The normal bill
generates a trunk bill only. The local office will request caller number from opposite
office from the incoming trunk during call initialization. Bills cannot be sorted without
caller number.
XVII. Uncentralized charging

It refers to charging the subscribers or trunks of local office.
XVIII. Charging point

It refers to the start point and end point of charging, which helps to calculate the
conversation duration for charging. By default, the charging start point is called party
answering, and end point is when the control party hangs up. The start points are
calling party dialing, called party answering, ringing, and trunk seizing. The end points
are calling party on-hook, called party on-hook, either party on-hook, second party
on-hook, and control party on-hook.
XIX. Charging duration

A minimum charging time is defined during which charging is not done.
When the charging duration does not exceed the minimum charging time, no charging
is done: charging meter is not counted, no detailed ticket is recorded, and no charging
pulse is sent. The design of minimum charging time is to avoid the calls mistakenly
connected or disconnected due to subscriber line instability or low connection rate.
4-4

XX. KC16/KC12
It refers to an implementation of instant charging. It is done in the following manner: A
KC16 or KC12 high-frequency pulse detection filter is connected to the telephone set at
subscriber side. During a call, the SoftX3000 controls the access gateway (for example,
IAD or AMG) to send a high-frequency pulse representing charging information to the
subscriber line every 60 seconds. Because the charge of one pulse is already set, the
charging device at the subscriber side can accomplish instant charging of the call
according to the number of pulses received.
XXI. Polarity reversal

It refers to an implementation of instant charging. It is done in the following manner: The
telephone set with polarity reversal charging function has already charging data, and
requires only the call start time. The SoftX3000 indicates the call start time by reversing
the polarity on the subscriber line through IAD or AMG.
The instant charging of polarity reversal is done on subscriber line rather than by the
charging system of the SoftX3000.
4.1.2 Charging Case and Charging Source Code

I. Charging case
The charging case is a collection of defined charging modes including
z
Charging office: Centralized charging or decentralized charging
Payer: Calling party, called party, free, no charge, or third party
Charging method: Charging meter, detailed ticket, or both
Pulse or metering mode: The interval defined between adding of a meter count or
sending of a pulse
Discount: Specifying the period and discount type
For instance, for a local call, its charging case can be as specified in the following table.
Here, 180/2/60/1 means to count twice the charging meter for the first 180 seconds,
and then to count once every 60 seconds.
Table 4-1 A charging case of local call
Item
Setting
Charging office
Uncentralized charging
Payer
Caller
Charging method
Charging meter
Charging meter
Metering type
180/2/60/1

4-5

For an instance of a toll call, its charging case can be as specified in the following table.
Here, the pulse sending mode indicates that the system sends a charging pulse every
six seconds.
Table 4-2 A charging case of toll call
Item
Setting
Charging office
Centralized charging
Payer
Caller
Charging method
Detailed ticket
First pulse
Subsequent pulse
Discount
40% off from 9 p.m. to 7 a.m.
II. Charging source code

The charging source code is a group of serial numbers that is distributed to identify the
charging attributes of local subscribers or trunk groups. For instance, all ordinary
subscribers of the local office share the same charging attributes, and their charging
source code can be set to 1. All Centrex subscribers have different charging attributes
from ordinary subscribers. Their charging source code can be set to 2.
4.1.3 Charging Method

I. Intra-office group charging
Intra-office group charging is based on the charging source code of both calling and
called parties. It is designed for charging between local subscribers, trunk groups, and
between subscriber and trunk group.
The charging source code is used when you configure subscriber and trunk group data.
It is known as caller charging source code or called charging source code specifically
when it belongs to calling or called parties.
The local grouped charging contains two layers as follows:
z
Intra-office means that it is charging between subscribers and trunk groups within
the office.
Group means that the charging case is determined by the combination of calling
and called parties, and their charging source code.
For instance in Table 4-3, there are two subscriber groups A and B, with charging
source code 1 and 2. There are four combinations as shown below.

4-6

Table 4-3 The charging case specified in intra-office group charging

Caller
Callee
Caller
charging
source code
Callee
charging
source code
Charging
case
Group A
Group A
Group B
Group B
Group A
Group B
Group B
Group A
II. DPC Charging

DPC charging, also known as charging case indexing, is based on charging selection
code and caller charging source code. It is used for outgoing calls of the local office.
The charging selection code is essential in DPC charging. It is used to specify the
destination of the call when you configure call analysis data. During charging, the
charging case is specified by the caller charging source code and the destination.
For instance in Table 4-4, the charging source codes for subscriber groups A and B are
1 and 2 respectively. The charging selection code is 10 for national toll call, and is 20 for
international toll call. Table 4-4 shows that there are four combinations of caller
charging source code and charging selection code.
Table 4-4 The charging case specified in DPC charging
Caller
Call type
Caller
charging
source code
Charging
selection
code
Charging
case
Group A
National toll
10
Group A
International
toll
20
Group B
National toll
10
Group B
International
toll
20
III. Called group charging

The called group charging is based on called charging source code. It is used when the
called party pays the charge.
The called charging source code is different from callee charge source code of
intra-office group charging.

4-7

Table 4-5 Differences between callee charging source code and called charging
source code
Name
Charging method
Payer
Caller
Called charging source

code
Called group charging
Callee
Can be of any
office
Callee charging source

code
Intra-office group
charging
Caller
Must be of local
office
The called group charging is generally used in the free service hotlines in enterprises
and corporations.
IV. Centrex intra-group charging

It is a charging mode dedicated to calls of Centrex subscribers within the Centrex
group.
V. Supplementary service charging

It is used to charge supplementary services based on supplementary service type and
charging source code.
The implementation of supplementary service charging is similar to DPC charging. The
supplementary service type in supplementary service charging functions similarly to
charging selection code in DPC charging.
VI. Priority in charging

In the SoftX3000, multiple charging methods can be defined for the same call. If so, the
adoption of the specific charging method is decided by priority. If no charging method is
defined, an alarm bill is recorded, and a charging alarm of critical or major severity is
generated.
The priority of charging methods is
1)
Supplementary service charging
2)
Centrex intra-group charging
3)
Intra-office group charging
4)
DPC charging
For instance, when you have defined intra-office group charging and DPC charging for
prefix PQR, the charging system will adopt the charging case defined in intra-office
group charging for the charging of calls with the prefix PQR.
The priority is for caller charging calls. If called group charging or third-party charging is
also defined, the charging should be done additionally.

4-8

4.1.4 Trunk Charging

The trunk charging refers to the charging of trunk calls. It includes incoming trunk
charging and outgoing trunk charging.
I. Incoming trunk charging

There are two cases:
z
Incoming call connection: The called party is from the local office. The incoming
call is directly connected to the destination party.
Incoming call tandem: The called party is from another office. The incoming call is
transferred through the outgoing trunk.
Incoming trunk charging means to charge the incoming trunk as a calling party. There
are two implementations:
z
Intra-office charging: It is based on the charging source code of the trunk group
and the local subscriber. It is suitable for calls connecting to the local subscribers.
DPC charging: It is based on the trunk group charging source code and charging
selection code. It is suitable for calls forwarded to another office.
II. Outgoing trunk charging

The charging of outgoing trunk is the charging of incoming trunk of the opposite office.
In this sense, the outgoing trunk is regarded as a calling party. There are two charging
modes:
z
Intra-group charging: It does not distinguish DPC, and is based on charging

source code of outgoing trunk. In this case, the caller charging source code and
callee charging source code are both outgoing trunk charging source code.
DPC charging: It distinguishes DCP and is based on the trunk group charging
source code and charging selection code.
The outgoing trunk charging is used to verify charging between different offices or
networks.
4.2 Configuring Basic Charging Data

4.2.1 Overview
Charging data defines charging related information of the office, and is usually done
after the configuration of office data. Refer to Figure 4-1 for details.

4-9

Start
Equipment data
Trunk data
Office data
Number analysis
Charging data
Subscriber data
MG data
Centrex data
MRS data
Call barring data
Protocol data
IN service data
Signaling data
Other service data
Routing data
Other application
data
End

During the process of SoftX3000 data configuration, some parameters defined during
the configuration of charging data are referenced when you configure trunk data,
subscriber data, and IP console data. The referencing relationship is presented as
broken lines in Figure 4-1. Refer to Table 4-6 for details.
Table 4-6 Parameter referencing relationship between charging data and other data
Input parameter
Name
Defined in
Output parameter
Name
Referenced in
Charging source code
Trunk data, subscriber data and IP

console data
Outgoing trunk charging

source code
Trunk data
Charging selection code

code
Trunk data, subscriber data and IP

console data
II. Preparations
The basic configuration principle is
1)
First determine the charging method and charging case of the office.

4-10

2)
Then plan the charging source code, charging selection code and called charging
source code accordingly.
Refer to U-SYS SoftX3000 SoftSwitch System Operation Manual-Configuration

Example for details.

Table 4-7 lists the general steps for configuring basic charging data.
Step
Description
Command
Add date category (optional)
ADD DCAT
Modify week category (optional)
MOD WCAT
Add charging case analysis
ADD CHGANA
Modify charging mode
MOD CHGMODE
Add intra-office group charging
ADD CHGGRP
Add charging case index
ADD CHGIDX
Add called group charging
ADD CHGCLD
Add supplementary service charging
ADD CHGSS
Note:
Refer to Chapter 13, Configuring Centrex Data, for detailed content of configuring
Centrex charging data.

you configure basic charging data.

4-11

ADD CHGANA
ADD CHGIDX
[Charging case]
[Charging selection code]
[Charging office]
[Caller charging source code]
[Payer]
[Bearer capability]
[CodeC]
[Charging case]
ADD CHGGRP
MOD CHGMODE

[Charging case]
[Called charging source code]
[Data category]
[Bearer capability]
[Time zone 1 switch

point]
[CodeC]
[Charging case]
ADD CHGCLD
MOD PLUSMOD
[Called charging source]
[Charging case]
[Bearer capability]
[Data category]
[CodeC]
[Time zone 1 switch

point]
[Charging case]
ADD CHGCX
[CENTREX group number]
[Charging case]
4.2.2 Adding Date Category (Optional)

I. Related commands
Command
Function
ADD DCAT
To add date category
RMV DCAT
To remove the specified date category
LST DCAT
To list all date category information

data configuration.
The configuration of date category is to define national and religious holidays as special
days during which the subscribers can enjoy charging discount.

4-12

The system defines six types of dates: normal working day, 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 considered. The
priority is category 5, category 4, category 3, category 2, category 1, and normal
working day.
By default, the date category is null and the week category is predefined as in
Table 4-8.
Table 4-8 Definition of week category
Week category
Date category
Sunday
Category 2
Monday
Normal working day
Tuesday
Normal working day
Wednesday
Normal working day
Thursday
Normal working day
Friday
Category 1
Saturday
Category 2
To modify the date category, execute ADD DCAT.

[Year], [Month], [Day]
They indicate a specific date. "Year must be four digits ranging form 1999 to 3000.
[Date category]
This parameter specifies date categories 1 to 5.
4.2.3 Modifying Week Category (Optional)

I. Related commands
Command
Function
MOD WCAT
To modify week category
LST WCAT
To list all week category information

data configuration.

4-13

By default, the week category is predefined as in Table 4-8.

To modify the week category into a different value other than the default one, execute
MOD WCAT. For instance, offline charging is adopted in the office, so all date types
should be normal working day. Execute MOD WCAT to modify the date category of
Friday, Saturday, and Sunday into normal working day.

[Week]
This parameter specifies a day from a week.
[Date category]
This parameter specifies the day in each week to be normal working day or date
category 1 to 5.
The modification of date category in the week category table changes the charging
information of the day every week, so be careful in modifying it.
4.2.4 Adding Charging Case Analysis

I. Related commands
Command
Function
ADD CHGANA
To add charging case
RMV CHGANA
To remove charging case
MOD CHGANA
To modify charging case
LST CHGANA
To list all specified charging cases

[Charging case]
The charging case globally and uniquely identifies a type of charging analysis data in
the SoftX3000, ranging from 0 to 29999.
[Charging manner]
It specifies if a charging case is applicable to CRG charging. It is Non_CRG charging
by default. Set this parameter by the following principles:
z
If a charging case is not applicable to CRG charging but applicable to a common

charging mode, use the default value or select Non_CRG charging and set the
corresponding charging band with MOD CHGMODE.
If a charging case is applicable to local office charging under CRG charging, that is,
when the local office acts as both a charging office and a terminating charging

4-14

office, select Charging local and set the corresponding charging band with ADD
CHGBAND.
z
If a charging case is applicable to originating office charging, terminating office

charging, or tandem office charging under CRG charging, set this parameter in
accordance with parameters of other offices in the network. For example,
z
If the terminating office determines the charging, set the charging manner of
the terminating office to Send CRG band number and that of the originating
office to Receive CRG band number. If there is a tandem office between, set
the charging manner of the tandem office to Transfer CRG band number. In
this case, the charges of the originating office can be calculated according to
the charging band number sent by the terminating office.
If the tandem office determines the charging, set the charging manner of the
tandem office to Send detailed charging info and that of the originating office
to Receive detailed charging info. In this case, the charges of the originating
office can be calculated according to the charging data of the tandem office.
If the terminating office determines the charging, set the charging manner of
the originating office to Receive CHU charging pulse. If there is a tandem
office between and the charging manner of the tandem office is set to
Convert CRG band number to pulse, set the charging manner of the
terminating office to Send CRG band number. If the charging manner of the
tandem office is set to "Convert detailed info to pulse, set the charging
manner of the terminating office to Send detailed charging info. If the
charging manner of the tandem office is set to Transfer CHU charging pulse,
set the charging manner of the terminating office to Send CRG charging
pulse. The originating office need not calculate the call charges, for the
charges can be calculated according to the charging pulses received.
All offices involved in a call such as originating office, tandem office, and
gateway office can charge the call. For example, the office determining the
charge can send charging messages to the charging office or charge calls
itself. In the CRG charging mode, if the local office need not charge a call, you
can set the parameter Payer to No charge.
If the AOC99 charging standard of Germany is used in the charging case, that is,
ISUP signaling is used between offices of different carriers to transmit charging
information, you need to configure the parameter in accordance with parameters
of other offices in the network. Generally, for a call, set the charging manner of the
terminating office to Send AOC99 charging information and that of the originating
office to Receive AOC99 charging information. If there is a tandem office
between, set the charging manner of the tandem office to Transfer AOC99
charging information
[Charging band number]

It is available only when Charging manner is set to Send CRG band number or
Send CHB band number, indicating the charging band number to be sent to the
4-15

charging office or tandem office from the local office (determining the charging) in a
CRG or CHB message.
Charging band number is an important parameter that must be numbered globally in
the network. When configuring this parameter, you need to negotiate with the charging
office or tandem office. This parameter must be defined in ADD CHGBAND before
being referenced here.
[Charging office]
It defines the charging to be centralized or decentralized. By default, it is decentralized
charging. If set to centralized charging, the local office requests the caller number from
opposite office incoming trunk during call initialization. Bills cannot be sorted without
caller number.
[Payer]
It specifies the payer of a call: calling party, called party, free, no charge, or third party.
The principles for setting this parameter are
z
By default, it is calling party.
If it is called party, the charging case can be used for called group charging only.
If it is free, the free detailed ticket is generated.
If it is no charge, no bill is generated.
If the payer is third party, it can be another subscriber number, an accounting card
number, a bank account, or Centrex group number.
[Charging method]
It defines the call recording method, which can be detailed ticket, charging meter, or the
combination of both. Generally, the charging meter is used in local call charging, and
detailed ticket is used in toll call charging. When immediate charge data is needed, the
charging tariffs read by the system are different.
z
If the charging method is set to Detailed ticket, the charging tariff is Detailed
ticket rate defined in the command.
If the charging method is set to Meter table, the charging tariff is defined in MOD
MTRR.
If the charging method is set to Meter and detailed ticket, the charging tariff is
Detailed ticket rate for a detailed ticket, and is defined in MOD MTRR for a meter
table ticket.
[Meter table]
It specifies the charging meter to be used in the charging case. Twenty charging meters
are configured for each subscriber, covering call types of local calls, local network calls,
special service calls, and supplementary service calls.
[Minimum charging time]

4-16

A minimum charging time (in seconds) is defined during which no charging is done. If
the conversation time is even shorter, an alarm is generated prompting that the
charging time is too short.
[Detailed ticket rate]
It defines the charging rate when instant charging is required and charging method is
detailed ticket. The unit is cent/pulse, meaning how many cents per KC16 charging
pulse. Here, cent is the minimal currency unit.
[Charging local DN set]
It defines the local DN set of the payer when the payer is set to third party. This
parameter is valid only when the number is of local office.
[Charging number type]
It defines the address nature of the third party number. It can be subscriber number,
national reserved, national valid number, account card, visa card, Centrex group
number, Centrex short number, and bank account.
[Charging number]
It refers to the number of the third party when the charge is covered by the third party.
The format for the charging number depends on the type of the charging number. If
what is charged is a subscriber number, the charging number is expressed in the
format of PQRABCD. If what is charged is a national significant number, the charging
number is expressed in the format of XXXPQRABCD in which XXX represents the
national toll area code.
[Start information quantity], [Start pulse], [Subsequent information quantity],
[Subsequent pulse]
The four parameters describe the frequency of pulse charging. The information
quantity refers to the unit of time. For instance, they are set to 30, 2, 10, and 1, which
means that in the first 30 information units, two charging pulses are sent and
subsequently one pulse is sent every 10 units.
[Charge point time]
It indicates the time when the system starts to charge a call. It has three options:
z
Caller off-hook: The system starts to charge a call when the caller picks up the
phone.
Callee off-hook: The system starts to charge a call when the callee picks up the
phone. This is the default option.
Ringing: The system starts to charge a call when the telephone set of the callee
rings.
[Confirm bill flag]

It defines the charge attributes for a collect call. The options are

4-17

z
No relation: It is the default value, indicating that this charing case is applicable to
charging of common calls, but not collect calls.
Bill point: When the lcoal SoftX3000 serves as the charging office (tandem office
or toll office, for example) for the collect call service, you need to set the charging
case corresponding to the collect call service prefix to Bill point.
Before bill point: When the lcoal SoftX3000 serves as the originating office for the
collect call service, you need to set the charging case corresponding to the collect
call service prefix to Before bill point. At this time, if a local subscriber dials the
collect call service prefix, the SoftX3000 generates a common call detail record
(CDR) and an outgoing trunk CDR with the parameter Free (charging-free flag)
set to Yes and Payer set to Called party.
Beyond bill point: When the lcoal SoftX3000 serves as the terminating office for
the collect call service, you need to set the charging case corresponding to the
collect call service prefix to Beyond bill point. At this time, if a local incoming trunk
calls the collect call service prefix, the SoftX3000 generates an incoming trunk
CDR with the parameter Free (charging-free flag) set to Yes and Payer set to
Called party.
By default, charging case is not a criterion for the system to judge whether the local
office is a charging office or not, because the SoftX3000 regards the local office as the
charging office whenever a subscriber or an incoming trunk calls the collect call service
prefix. To set the charging case as the judgment criterion, you must set BIT1 of the
parameter call internal parameter 9 (P141) to 0.
[Multiplier]
If the SoftX3000 needs to send a charging message to an ISDN phone set through
DSS1 during the Advice of Charge at Call End (AOCE), Advice of Charge at Call Start
(AOCS), or Advice of Charge during the Call (AOCD) service used by a BRA subscriber,
this parameter defines the value of the multiplier field in the charging message, and the
ISDN phone set will display the call charges with a certain currency unit based on this
field. For example, 1 stands for cent, 3 stands for dollar. This parameter (not used
currently) ranges from 0 to 6. It is 1 by default.
4.2.5 Modifying Charging Mode

I. Related commands
Command
Function
MOD CHGMODE
To modify charging mode
LST CHGANA
To list all specified charging cases

4-18


[Charging case]
It specifies the charging case whose charging mode is to be modified. This parameter
must first be defined by the ADD CHGANA command and referenced here.
[Date category]
It specifies the date category of the record. By default, it is normal working day. There
are six date categories. As listed in Table 4-8, normal working day, category 1 and
category 2 are already predefined. If the other date categories are to be selected, first
execute ADD DCAT or MOD WCAT to set them. For further information, refer to 4.2.2
Adding Date Category (Optional) and 4.2.3 Modifying Week Category (Optional).
[Time zone 1 switch point] to [Time zone 8 switch point]
They divide a day into different time segments in HH&MM format. HH stands for hour
and MM for minute. Set this parameter by the following principles:
z
To define one time zone, set both the time zone 1 switch point and time zone 2
switch point to 00&00. The charging mode and the tariff discount for the time zone
1 are used.
To define two time zones, two switch points are set. The segment before time zone
1 switch point and after time zone 2 switch point is time zone 1 and uses the
charging mode and the tariff discount defined for time zone 1. The segment before
time zone 2 switch point and after time zone 1 switch point is time zone 2 and uses
the charging mode and the tariff discount defined for time zone 2.
To define three time zones, three switch points are set. The segment before time
zone 1 switch point and after time zone 3 switch point is time zone 1 and uses the
the charging mode and the tariff discount defined for time zone 2. The segment
before time zone 3 switch point and after time zone 2 switch point is time zone 3
and uses the charging mode and the tariff discount defined for time zone 3.
The other time zones are defined in the same way.
The valid time zone switch points are incremental in time, which means that time
zone 2 switch point is later in time than time zone 1 switch point. The calls made in
invalid time zones are not charged.
[Start interval], [Start pulse], [Continued interval], [Continued pulse]

The four parameters define the charging mode in time zones. Here, start interval and
continued interval describe the metering duration in second; start pulse and continued
pulse describe the metering count. Refer to Table 4-1 for exemplification.
[Time zone 1 charge rate] to [Time zone 8 charge rate]
The parameters define the tariff discount in percentage in different time zones, ranging
from 0 to 100. The default value is 100, which means no discount; 60 means 40% off.

4-19

If it is less than a meter count after discount, make it one count.
4.2.6 Adding Intra-office Group Charging

I. Related commands
Command
Function
ADD CHGGRP
To add intra-office group charging
RMV CHGGRP
To remove intra-office group charging
MOD CHGGRP
To modify intra-office group charging
LST CHGGRP
To list intra-office group charging

[Caller charging source code], [Callee charging source code]
The parameters define the charging source code of subscribers or trunk group, ranging
from 0 to 254.The value 254 stands for all charging source code.
Table 4-9 Three settings of caller charging source code and callee charging source
code
When the call type is
The caller charging

source code is that of
The callee charging

source code is that of
Local call
Calling party
Called party
Incoming trunk call
Trunk group
Called
office
Outgoing trunk call
Outgoing trunk
Outgoing trunk
party
of
local
[Bearer capability]
It defines the distinctive charging of calls of different services or bearer capabilities. Set
it by the following principles:
z
If IP audio is selected, only IP audio part is charged.
If IP video is selected, only IP video part is charged.
If Unrestricted 384K is selected, only the audio and video communication through
384 kbit/s circuit-switched network is charged.
For other options, only the specific part is charged.
If several (usually two) Bearer capability parameters in the intra-office group charging
data match the current call when the call processing software is performing charging
analysis, the priority of the all option is the lowest. The system perfers the other
parameters. If it is not for a particular purpose, select All, and the distinctive charging
will not be implemented.
4-20

[Bill type]
It specifies a type of calls to be charged. For example, if the bill type is set to Normal,
only the calls for which normal bills are generated will be charged; if the bill type is set to
Free, only the calls for which free bills are generated will be charged, and so on.
When the call processing software analyzes the charging information, if the parameter
"bill type of several (usually two) charging case indexes can match the current call, the
option All enjoys the lowest priority, that is, the system matches the other parameters
as prior. Unless otherwise specified, set this parameter to All, that is, charging of a
specified type of calls is not implemented.
[Codec]
It defines the distinctive charging of calls of different media stream types.
z
If G.711 is selected, only the calls through circuit-switched network are charged.
If G.723 is selected, only the calls through VoIPnetwork are charged.
If several (usually two) Codec parameters in the intra-office group charging data
match the current call when the call processing software is performing charging
[Charging case]
The parameter defines the charging case corresponding to conditions defined in other
parameters. This parameter must first be defined by the ADD CHGANA command, and
modified by the command MOD CHGMODE before being referenced here.
The charging case referenced here specifies that the payer cannot be Called party.
4.2.7 Adding Charging Case Index

I. Related commands
Command
Function
ADD CHGIDX
To add charging case index
RMV CHGIDX
To remove charging case index
MOD CHGIDX
To modify charging case index
LST CHGIDX
To list all information of the charging case index

specified


4-21

It defines the selected code for charging based on different DPCs. The parameter is
referenced when you execute ADD CNCLD to configure number analysis data. A call
prefix (DPC) uniquely corresponds to one charging selection.
It defines the charging source code of subscribers or trunk group, including trunk
charging source code, ranging from 0 to 254. The value 254 stands for all caller
charging source code.
Table 4-10 Three settings of caller charging source code
When the call type is
The caller charging source code is
Local call
Charging source code of calling party
Incoming trunk call
Charging source code of trunk group
Outgoing trunk call
Outgoing trunk charging source code of trunk group
[Bearer capability]
It defines the distinctive charging of calls of different services or bearer capabilities.
z
If IP audio is selected, only IP audio part is charged
If IP video is selected, only IP video part is charged
If several (usually two) Bearer capability parameters in the charging case index data
[Codec]
z
If G.723 is selected, only the calls through VoIP network are charged.
If several (usually two) Codec parameters in the charging case index data match the
current call when the call processing software is performing charging analysis, the
priority of the all option is the lowest. The system perfers the other parameters. If it is
not for a particular purpose, select All, and the distinctive charging will not be
implemented.
[Charging case]

4-22

modified by MOD CHGMODE before it is referenced here.
The charging case referenced here specifies that the payer cannot be Called party.
4.2.8 Adding Called Group Charging

I. Related commands
Command
Function
ADD CHGCLD
To add called group charging
RMV CHGCLD
To remove called group charging
LST CHGCLD
To list called group charging data

Note that the called group charging is independent of the caller location.

The parameter is referenced when you configure the called subscriber data. It ranges
from 0 to 254. The value 254 stands for all caller charging source code, which is
generally not used.
Caution:
The called charging source code cannot be set to 254, or all calls of the office charge
the called party.
[Bearer capability]
It defines the distinctive charging of calls of different services or bearer capabilities.
z
If IP audio is selected, only IP audio part is charged
If IP video is selected, only IP video part is charged
If several (usually two) Bearer capability parameters in the called group charging data
4-23

[Codec]
z
If several (usually two) Codec parameters in the called group charging data match the
current call when the call processing software is performing charging analysis, the
priority of the all option is the lowest. The system perfers the other parameters. If it is
not for a particular purpose, select All, and the distinctive charging will not be
implemented.
[Charging case]
modified by MOD CHGMODE before it is referenced here.
The charging case referenced here specifies that the payer must be Called party.
4.2.9 Adding Supplementary Service Charging

I. Related commands
Command
Function
ADD CHGSS
To add supplementary service charging
RMV CHGSS
To remove supplementary service charging
LST CHGSS
To list supplementary service charging data

It specifies the charging method for supplementary services. There are two types of
charging methods applied.
z
Fixed charging: The supplementary services are charged by times, and are
irrelevant to conversation duration or distance between caller and callee. The
charging method is pulse metering. It is metered on the charging meter for every
registration or usage.
Periodic charging: The supplementary services applied in this charging method

include call waiting, 3-party service, and conference calling. Detailed ticket or
charging meter table is generated based on charging case.
The charging of supplementary services are independent from that of ordinary calls.
4-24


It specifies the supplementary service to be charged.
[Charging source code]
It defines the charging source code of the supplementary service. It ranges from 0 to
254. The value 254 stands for all charging source code. During charging process, the
system automatically decides it to be caller or callee charging source code.
[Meter table]
It decides which charging meter is metering the supplementary service. A maximum of
twenty charging meters are ready for choice.
[Pulse number]
The pulse number defines the number of pulses recorded in the charging meter for
registering, canceling, using or verifying the supplementary service. It then decides
charges of the supplementary service.
4.3 Configuring Addition Fee Data

4.3.1 Overview
The addition fee data is a part of charging data, and is not used until additional fee is to
be charged in instant charging.

Additional fee is added on basic call charging. The configuration of additional fee data
starts after the completion of basic charging configuration. Refer to Table 4-11 for its
configuration steps.
Step
Description
Command
ADD CHGANA
Modify charging mode
MOD CHGMODE
ADD CHGIDX
Add intra-office group charging
ADD CHGGRP
Add additional fee charging mode (optional)
ADD PLUSPAY
Modify additional fee charging mode
MOD PLUSMOD

4-25

4.3.2 Adding Additional Fee Charging Mode (Optional)

I. Related commands
Command
Function
ADD PLUSPAY
To add additional fee charging mode (optional)
RMV PLUSPAY
To remove additional fee charging mode (optional)
LST PLUSPAY
To list all additional fee charging modes

data configuration.
When you modify addition fee charging mode by using MOD PLUSMOD, if the item
query add charge mode with add charge tariff as index is selected, the modification
cannot be done until adding the additional fee charging mode with ADD PLUSPAY.

[Additional fee charging mode]
It defines the additional fee charging mode to be applied. The parameter is valid only
when the item query add charge mode with add charge tariff as index is selected, and is
referenced by the additional fee tariff in the additional fee charging mode table.
[Start interval], [Start fee], [Continued interval], [Continued fee]
The four parameters define the additional fee charging mode in specified call duration.
There are two settings examples, as shown in Table 4-12.
Table 4-12 Two examples of intervals and fee
Start interval
Start fee
Continued
interval
Continued fee
60
10
10
120
20
60
10
The first example means that 10 cents additional fee for every 60 seconds of call.
The second example means that 20 cents additional fee for the first 120 seconds, and
10 cents for every 60 seconds from then.

4-26

4.3.3 Modifying Additional Fee Charging Mode

I. Related commands
Command
Function
MOD PLUSMOD
To modify additional fee charging mode
LST CHGANA
To list all specified charging modes

[Charging case]
It specifies the charging case whose additional fee data is to be configured. This
parameter must first be defined by the ADD CHGANA command, and modified by
MOD CHGMODE before it is referenced here.
[Date category]
It specifies the date category of the record. By default, it is normal working day. There
are six date categories. As listed in Table 4-8, normal working day, category 1 and
category 2 are already predefined. If other date categories are to be selected, execute
ADD DCAT or MOD WCAT. For further information, refer to Sections 4.2.2 Adding
Date Category (Optional) and 4.2.3 Modifying Week Category (Optional).
[Time zone 1 switch point] to [Time zone 8 switch point]
They divide a day into different time segments in HH:MM format, ranging from 00:00 to
23:59.
z
To define one time zone, the time zone 1 switch point and time zone 2 switch point
are both set to 00:00. The charging mode and the tariff discount for the time zone
1 are used.
To define two time zones, two switch points are set. The segment before time zone
1 switch point and after time zone 2 switch point is the time zone 1 and uses the
charging mode and the tariff discount defined for the time zone 1. The segment
before time zone 2 switch point and after time zone 1 switch point is the time zone
2 and uses the charging mode and the tariff discount defined for the time zone 2.
To define three time zones, three switch points are set. The segment before time
zone 1 switch point and after time zone 3 switch point is the time zone 1 and uses
the charging mode and the tariff discount defined for the time zone 1. The segment
before time zone 2 switch point and after time zone 1 switch point is the time zone
2 and uses the charging mode and the tariff discount defined for the time zone 2.
The segment before time zone 3 switch point and after time zone 2 switch point is
the time zone 3 and uses the charging mode and the tariff discount defined for the
time zone 3.

4-27

z
The valid time zone switch points are incremental in time, which means that time
zone 2 switch point is later in time than time zone 1 switch point. The calls made in
invalid time zones are not charged.
[Time zone n additional fee type 1], [Time zone n additional fee type 2], [Time zone n
additional fee type 3], [Time zone n additional fee type 4]
The four parameters indicate that the additional fee of a certain time zone can be the
total of four modes at most.
Table 4-13 Five types of additional fee charging
Charging
mode
Additional fee type

Additional fee tariff
Fixed mode
Additional fee tariff*pulse number
Duration mode
Conversation
fee tariff
By call charge
charge*additional
Remark
Independent of call duration
Toll tariff
Fixed mode
Independent of call duration
Query Add. charge mode with

Add. charge tariff as index
Not defined
Defined by ADD PLUSPAY
[Time zone n tariff 1], [Time zone n tariff 2], [Time zone n tariff 3], [Time zone n tariff 4]
The four parameters correspond to the four types of additional fee. Refer to Table 4-14
for their meanings.
Table 4-14 Meaning of time zone tariff
Choice
Meaning
Additional fee tariff
Additional fee charged for every call (in cent)
Additional fee tariff*pulse number
Additional fee tariff for every pulse during

conversation
Conversation charge*additional fee

tariff
Percentage of additional fee over entire call

charge
Toll tariff
Toll tariff
Query Add. charge mode with Add.

charge tariff as index
The reference number of additional fee

charging mode.
Choice five must be defined in ADD PLUSPAY before it is referenced here.

[Time zone 1 charge discount] to [Time zone 8 charge discount]
The parameters define the tariff discount in percentage in different time zones, ranging
from 0 to 100. The default value is 100, which means no discount; 60 means 40% off.

4-28

If it is less than a meter count after discount, make it one count.
4.4 Configuring CRG Charging Data

4.4.1 Overview
CRG charging is a charging process based on charging messages, that is, charging is
implemented through the transmission of charging messages between offices. You
need to set such data as tariff indicator, time indicator, and charging band number only
when the carrier demands the CRG charging mode.
During the CRG charging, you must ensure the consistency or coordination of charging
data between offices; otherwise, charging errors will occur.
1)
First, ensure that there must be one charging-determining office during a call. If
there are several charging-determining offices, take the first one as the reference.
2)
Second, ensure the consistency of charging manner configured between offices,

that is, the charging manner must match the charging messages transmitted
between offices. For example, if the charging manner of the charging-determining
office is Send detailed charging info, the charging manner of the originating office
must be set to Receive detailed charging info. If the charging manner of the
originating office is set to Receive charging band number, the originating office
cannot obtain the charging band number message it needs.

Refer to Table 4-15 for the general steps for configuring CRG charging data.
Step
Description
Command
Configure related ISUP adaptation data
Modify fixed software parameter
MOD FSFP
Add tariff indicator (optional)
ADD RIND
Add time indicator (optional)
ADD TIND
Add charging band
ADD CHGBAND
ADD CHGANA
ADD CHGIDX

4-29

4.4.2 Configuring Related ISUP Adaptation Data

Because the ISUP specifications defined in various countries or regions might differ
from the ITU-T recommendations, Huawei provides carriers with corresponding ISUP
adaptation script (including CRG adaptation data) for equipment commissioning to
adapt the SoftX3000 with the ISUP of a specific country or region. Be sure to execute
the ISUP adaptation script before configuring CRG charging data.
4.4.3 Modifying Fixed Software Parameter

Different carriers might require different CRG charging specifications, so you need to
modify the related software parameters with MOD FSFP as needed during deployment
to make the SoftX3000 meet the actual needs of carriers. The meaning of the
parameters and bits is as follows:
I. P53 call test parameter 1 (it is FFFF by default)

Bit 1: It indicates whether to connect a call when charging data is wrong.
=1: connect the call
=0: not connect the call
Bit 2: It indicates whether to connect a call originated by an incoming trunk when

charging data is wrong.
=1: connect the call
=0: not connect the call (bit 1=0)
II. P95 Oversea SS7 parameter 2 (it is FFFF by default)

Bit 13: It indicates whether the charging field is two bytes long in a CRG message.
=0: one byte
=1: two bytes
Bit 14: It indicates whether to send in the subsequent CHU message the charging
units accumulated by the ISUP incoming trunk during T42/T43.
=0: send
=1: not send

4-30

III. P98 CCS7 test parameter 1 (it is FFFF by default)

Bit 9: It indicates whether the charging pulse field in a CRG message is two bytes
long.
=0: one byte
=1: two bytes
4.4.4 Adding Tariff Indicator (Optional)

I. Related MML command
Command
Function
ADD RIND
To add tariff indicator
RMV RIND
To remove tariff indicator
MOD RIND
To modify tariff indicator
LST RIND
To list tariff indicator

data configuration.
When a charging office cannot provide the detailed charging information and can only
be notified by the charging-determining office through CHG or TAC messages, you
need to configure the tariff indicator and time indicator at both the charging office and
the charging-determining office.
During CRG charging, when a charging-determining office transfers current charging
information, subsequent charging information, and new charging information to a
charging office through CHG or TAC messages, it needs to indicate the related call
charge information (that is, TA value) in two parameters tariff indicator and tariff
factor to the charging office. Then the charging office can calculate the corresponding
TA value according to the two parameters. There are two cases:
z
At the charging-determining office, the TA value is automatically generated by the

charging software. However, the charging-determining office does not send TA
information to the charging office directly; instead, it first converts the TA value to
the product of tariff factor (Detailed ticket rate in the corresponding charging case)
multiplied by time value, and then it searches in the local database for the tariff
indicator corresponding to the time value, and finally fills the tariff indicator and
tariff factor in the CHG or TAC messages to be sent to the charging office.
On receiving the tariff indicator and tariff factor, the charging office first
searches in the local database for the time value corresponding to the tariff
4-31

indicator, and then calculates the TA value according to the time value and tariff
factor, that is, TA=tariff factor x time value.
Therefore, during transmission of charging messages, CHG or TAC messages use the
tariff indicator but not the time value. That is, the tariff indicator is not used for
calculating TA directly. To ensure that the CRG charging can function well, both the
charging office and the charging-determining office need to set the corresponding tariff
indicator data. By default, the SoftX3000 has preset a tariff indicator table during
initialization. The default configuration of the table is as follows:
Tariff indicator
Time value(millisecond)
10
20
50
100
200
500
1000
2000
4000
Generally, the preset values of the system can satisfy most applications. To add tariff
indicators, execute ADD RIND.

[Tariff factor]
During CRG charging, this parameter defines a tariff indicator in the detailed charging
information and ranges from 0 to 255. The time values corresponding to tariff indicators
cannot be set arbitrarily, but must be planned globally in the network to ensure
one-to-one corresponding relationship between tariff indicators and time values.
[Time value]
This parameter defines a time value corresponding to a tariff indicator, ranging from 0 to
2147483647 in unit of millisecond.
4.4.5 Adding Time Indicator (Optional)

I. Related MML commands
Command
ADD TIND
Function
To add time indicator

4-32

Command
Function
RMV TIND
To remove time indicator
MOD TIND
To modify time indicator
LST TIND
To list time indicator

data configuration.
During CRG charging, when a charging-determining office transfers subsequent
charging information and new charging information to a charging office through CHG or
TAC messages, it needs to indicate the time information of the tariff change point in the
parameter time indicator to the charging office.
A time indicator is an index indicating a specific time point. Upon receiving the time
indicator, the charging office first searches in the local database for the specific time
corresponding to the time indicator, and then updates its charging data immediately to
facilitate conversion at the tariff change point indicated by the charging-determining
office.
By default, the SoftX3000 has preset a time indicator table during initialization. The
default configuration of the table is as follows:
Time indicator
Time
Change tariff immediately
00:15
00:30
00:45
01:00
01:15
01:30
...
95
23:45
96
00:00
In the table, time indicator 0 (non-configurable) stands for changing tariff immediately,
but not any specific time. The other time indicators are defined for every 15 minutes.
Generally, the preset values of the system can satisfy most applications. To add time
indicators, execute ADD TIND.

4-33


[Time code]
During CRG charging, this parameter defines a time indicator in the detailed charging
information and ranges from 1 to 127. The time corresponding to time indicators cannot
be set arbitrarily, but must be planned globally in the network to ensure one-to-one
corresponding relationship between time indicators and time points.
[Time]
This parameter defines a specific time indicated by a time indicator in the format of
HH&MM in 24-hour indication system. HH stands for hour and MM for minute.
4.4.6 Adding Charging Band

I. Related MML commands
Command
Function
ADD CHGBAND
To add charging band
RMV CHGBAND
To remove charging band
MOD CHGBAND
To modify charging band
LST CHGBAND
To list charging band

If a charging office can provide detailed charging information, but need to be notified by
the charging-determining office through CRG or CHB messages of starting charging,
you must set charging band data at both the charging office and the
charging-determining office using ADD CHGBAND.

It defines a charging band number for CRG charging in the local office. It is numbered
globally in the network and ranges from 0 to 254.
During CRG charging, if a charging office can provide detailed charging information but
cannot determine the type of the charging information to be used, the
charging-determining office can notify the charging office of it through the parameter
charging band number in a CRG or CHB message.
[Date category]
It specifies the date category of a record and is Normal workday by default. There are
six options. Normal workday, Category 1, and Category 2 have been preset by the
week category table of the system, and you can select them direclty. To select the other

4-34

date categories, first use ADD DCAT or MOD WCAT to set them. Refer to 4.2.2 Adding
Date Category (Optional) and 4.2.3 Modifying Week Category (Optional) for details.
[Time zone1 switch point] to [Time zone10 switch point]
They divide a day into different time segments in HH&MM format. HH stands for hour
and MM for minute. Set this parameter by the following principles:
z
All time zone switch points must be defined in ADD TIND before being referenced
here.
If the difference between two adjacent time zone switch points is less than eight
minutes, system errors might occur.
To define one time zone, set both the time zone 1 switch point and time zone 2
switch point to 00&00. The charging mode and the tariff discount of time zone 1
are used.
To define two time zones, set two switch points. The segment before time zone 1
switch point and after time zone 2 switch point is time zone 1 and uses the
charging mode and tariff discount defined for time zone 1. The segment before
the charging mode and the tariff discount defined for time zone 2.
To define three time zones, set three switch points. The segment before time zone
1 switch point and after time zone 3 switch point is time zone 1 and uses the
the charging mode and the tariff discount defined for time zone 2. The segment
before time zone 3 switch point and after time zone 2 switch point is time zone 3
and uses the charging mode and the tariff discount defined for time zone 3.
The valid time zone switch points are incremental, which means that time zone 2
switch point is later than time zone 1 switch point. The calls made in invalid time
zones are not charged.
[Start interval], [Start pulse], [Continued interval], [Continued pulse]

The four parameters define the charging mode in each time zone. Here, start interval
and continued interval describe the metering duration in second; start pulse and
continued pulse describe the metering count. For example, if the four parameters are
set to 180, 2, 60, and 1 respectively, it means that two counts are recorded within
the first 180 seconds of a call, and then one count is recorded for every 60 seconds.
[Time zone 1 charging discount] to [Time zone 10 charging discount]
They define the tariff discount in percentage in different time zones, ranging from 0 to
100. The default value is 100, which means no discount; 60 means 40% off.
If it is less than one meter count after discount, make it one count.

4-35

4.4.7 Adding Charging Case Analysis

Before configuring charging case data related to CRG charging, you must ensure the
consistency of charging manners between offices, that is, the charging manners must
match the charging messages transmitted between them. For further information, refer
to 4.2.4 Adding Charging Case Analysis.
4.4.8 Adding Charging Case Index

CRG charging is only applicable to destination code charging. For further information,
refer to 4.2.7 Adding Charging Case Index.
4.5 Other Charging-related Configurations

4.5.1 Modifying Charging Number
I. Related commands
Command
Function
MOD CHGNUM
To modify charging number
LST SBR
To list subscriber attribute

By default, the charging number in all bills generated for a local subscriber is his own
number. To assign it to another subscriber, use MOD CHGNUM.

[Local DN set]
It defines the local DN set to which the local subscriber belongs. The charging number
of the subscriber is to be modified. The fault value is 0.
[Original charging subscriber number]
It specifies the charging number currently used by the local subscriber. By default, it is
the number of the subscriber.
[New charging subscriber number]
It specifies the charging number to be assigned to the local subscriber. When the
command is executed, the charging number field of all bills generated is the new
charging subscriber number.

4-36

4.5.2 Modifying Meter Tariff Rate

I. Related commands
Command
Function
MOD MTRR
To modify meter tariff rate
LST MTRR
To list all meter tariff rates

During system initialization, all meter tariff rates are set to 10, meaning 10 cents per
pulse. To modify the tariff, execute the MOD MTRR command.
The meter tariff rate is valid only in instant charging. It is invalid in offline charging.

[Meter table]
It indicates the charging meter whose tariff is to be modified. The options are charging
meter 1 to charging meter 20, KC16, KC12, trunk charging pulse, and polarity reversal
pulse.
z
KC16, KC12, and polarity reversal pulse: The SoftX3000 sends these charging
pulses to subscribers through IAD or AMG.
Trunk charging pulse: The end office (SoftX3000) of the subscriber does not
provide toll call charging function. During toll calls, the end office accepts the trunk
charging pulse from trunk before forwarding it to the subscriber.
[Tariff]
The tariff of the charging meter is in unit of cent/pulse.
4.5.3 Checking Charging Configuration (Charging Emulation)

I. Related commands
Command
Function
CHK CHG
To check charge

To find charging data errors in advance and prevent various charging faults or
deviations after the equipment is put into operation, the SoftX3000 offers the charging
emulation function. That is, you can use the command CHK CHG to implement various
offline emulation tests on callers or trunk groups after configuring the charging data.

4-37


[Caller type]
This parameter specifies whether the calling party, on which the charge emulation tests
are to be performed, is a local office subscriber or a trunk.
[Caller local DN set]
When the caller type is set to local subscriber, this parameter is available to specify
the local DN set to which the local subscriber belongs.
[Caller subscriber number]
When the caller type is set to local subscriber, this parameter is available to specify
the calling number to be used in the charge emulation tests. This parameter is defined
in the ADD VSBR, ADD MSBR, ADD BRA, or ADD PRA command and reference
here.
[Caller trunk group number]
When the caller type is set to trunk, this parameter is available to specify the
incoming trunk group number to be used in the charge emulation tests. This parameter
is defined in the ADD SIPTG, ADD H323TG, ADD N7TG, or ADD N1TG command and
reference here.
[Caller number]
When the caller type is set to trunk, this parameter is available to specify a particular
calling number in the incoming trunk group to be used in the charge emulation tests.
[Caller address nature]
When the caller type is set to trunk, this parameter is available to specify the nature
of the calling number in the incoming trunk group to be used in the charge emulation
tests.
[Callee number]
This parameter specifies the called number or the called prefix to be used in the charge
emulation tests. To test intra-office group charging, do set a called number that is
defined in the ADD VSBR, ADD MSBR, ADD BRA, or ADD PRA command before
being referenced here. To test destination code charging, do set a called prefix that is
defined in the ADD CNACLD command before being referenced here.
4.5.4 Adding Conversation Duration Control

I. Related Commands
Command
Function
ADD TCTRL
To add conversation duration control
RMV TCTRL
To remove conversation duration control

4-38

Command
Function
MOD TCTRL
To modify conversation duration control
LST TCTRL
To list conversation duration control
II. Notes of Configuration

By default, the SoftX3000 generates only one bill at the end of a call. This bill records all
information of the call in detail, so it is also called complete bill. In some cases, the
carrier might require that the SoftX3000 can output intermediate bills during an
over-long call in case of any charging system error. Intermediate bills record partial
information of the call periodically, so they are also called segment bills.
To obtain segment bills, you use the command ADD TCTRL to add conversation
duration control. For calls with some specific prefixes, when the conversation duration
exceeds cetain time period, SofX3000 will generate segment bills periodically and
finally a complete bill at the end of the call. However, the billing center can only use one
charing mode (complete bill or segment bill), so this command is also used to set that
the SoftX3000 selects which type of bill as CDR to be output to the billing center.

It indicates the charging source code for the local callers or trunk groups for which
segment bills are to be generated. It must be defined in the ADD CHGGRP or ADD
CHGIDX command before being referenced here.
It indicates the charging selection code used for segment charging of different
destination codes (prefixes), ranging form 0 to 65534. It must be defined in the ADD
CHGIDX command first and referenced here.
[Time limit(*10min)]
It defines the duration (in unit of 10 minutes) of a call for which segment bills are to be
generated. That is, if a call lasts for an integral multiple of 10 minutes, the SoftX3000
will generate segment bills periodically.
By default, the system generates only one bill (complete bill) for all the calls. To make
the SoftX3000 generate segment bills, you must use MOD FSFP to set bit 8 of internal
call parameter 1 (P49) to 0.
[Detailed bill flag]
It determines whether the SoftX3000 selects complete bill or segment bill as detailed
bill to be output to the billing center.
z
If it is set to No (the default value), it means that segment bill is treated as failure
bill and complete bill is treated as detailed bill.
4-39

z
If it is set to Yes, it means that segment bill is treated as detailed bill and complete
bill is treated as failure bill.
[End flag]
It controls whether SofX3000 disconnects a call forcedly after the conversation duration
reaches the duration limit defined in the ADD TCTRL command. It is No by default,
meaning that the SoftX3000 will not disconnect the call forcedly.
[Alarm time]
It defines the duration (in seconds) between the time when the SoftX3000 plays an
alarm prompt to the caller for the reason that the conversation duration reaches the
limit defined in the ADD TCTRL command and the time when the SoftX3000
disconnects the call. It is valid only when "End flag is set to "Yes. By default, it is 0.
4.5.5 Adding Charging Pulse Control

I. Related Commands
Command
Function
ADD MTRPLS
To add charging pulse control
RMV MTRPLS
To remove charging pulse control
MOD MTRPLS
To modify charging pulse control
LST MTRPLS
To list charging pulse control

By default, the SoftX3000 send strings of pulse every 60 seconds to unattended public
phones applying KC16, KC12, or polarity reversal pulse in HANDSON mode when it
implements instant charging. The charging duration for the first string of pulse is also 60
seconds by default.
Suppose that the tariff for a string of pulse is 0.05 dollars, 0.05 dollars are charged
every minute for local calls, and 0.5 dollars are charged every minute for toll calls.
When a subscriber makes a local call on an unattended public phone, the SoftX3000
sends one initial string of pulse after call connection and then one string of pulse every
60 seconds to the public phone. When a subscriber places a toll call on an unattended
public phone, the SoftX3000 sends the initial 10 strings of pulse after call connection
and then 10 strings of pulse every 60 seconds to the public phone.
To modify the rules of sending string of pulse, for example, to enable the SoftX3000 to
send the initial string of pulse at 120 seconds after call connection and then one string
of pulse every 60 seconds, you must use the commmand ADD MTRPLS to add
charging pulse control.

4-40

III. Parameter Description

It indicates the charging selection code used for instant charging of different destination
codes (prefixes), ranging form 0 to 65534. It must be defined in the ADD CHGIDX
command first and referenced here.
It indicates the charging source code for the local callers or trunk groups requiring
instant charging. It must be defined in the ADD CHGGRP or ADD CHGIDX command
before being referenced here.
[Initial period]
It defines the conversation duration (in seconds) represented by the initial string of
pulse sent by the SoftX3000 after call connection to an unattended public phone
applying KC16, KC12, or polarity reversal pulse technology in the case of instant
charging. That is, during the conversation duration, the SoftX3000 sends only one
string of pulse to the public phone. After this duration, the SoftX3000 sends strings of
pulse to the public phone periodically based on the Subsequent period.
[Subsequent period]
It defines the period (in seconds) between which SofX3000 sends strings of pulse after
sending the initial string of pulse to an unattended public phone applying KC16, KC12,
or polarity reversal pulse technology in the case of instant charging.
For example, suppose that the initial period is set to 120, the subsequent period is set
to 60, one string of pulse stands for 0.05 dollars, and the toll call tariff is 0.50 dollars
per minute. When a subscriber makes a toll call on a public phone, the switch first
sends 20 strings of pulse to the public phone and then 10 strings of pulse every 60
seconds.
[Send alarm]
It indicates whether the SoftX3000 sends an alarm to the alarm console before sending
string of pulse to an unattended public phone.
[Alarm time to end]
It defines the duration (in seconds) before which the SoftX3000 sends an alarm to the
alarm console and after which the SoftX3000 sends string of pulse to an unattended
public phone. It is valid only when the parameter send alarm is set to Yes. It is 0 by
default.
[First send polarity pulse]
It indicates whether the SoftX3000 initially sends polarity reversal pulse or polarity
reversal signal to an unattended public phone applying polarity reversal pulse
technology in the case of instant charging. It is set to No by default, meaning that

4-41

polarity reversal signal is sent initially. if it is set to Yes, it means that polarity reversal
pulse is sent initially.
No matter whether the SoftX3000 sends polarity reversal pulse or polarity reversal
signal to an unattended public phone initially, it sends all polarity reversal pulse
subsequently.
4.5.6 Adding Charging Case Change

I. Related commands
Command
Function
ADD CHGCHG
To add charging case change
RMV CHGCHG
To remove charging case change
MOD CHGCHG
To modify charging case change
LST CHGCHG
To list charging case change

In normal cases, when the local office uses ordinary charging manner, the SoftX3000
does the charging analysis of an outgoing call or a tandem call according to the flow of
destination code charging. The SoftX3000 retrieves a charging case for the charging
of the call from the configuration database according to the combination conditions
such as charging source code of the caller/incoming trunk, charging selection code of
the call prefix, bearer capability of the service, codec of the media stream.
The situation is different in other cases. For example, when analyzing the route for the
same destination code, the local office can connect the call through an ISUP trunk to
PSTN network, or SIP trunk to VoIP network. If the carrier needs to distinguish the
charging of different connection modes, and concurrently keep the dial mode of
subscribers (that is, the system selects the route automatically, and subscribers do not
dial access codes), the SoftX3000 needs to select different charging cases according
to different outgoing trunk group numbers during charging analysis. Here you need to
add charging case change by executing the command ADD CHGCHG.

[Charging case]
It is one of the conditions for judging charging case changes. It specifies the default
charging information obtained when the system does charging analysis of a call. This
parameter must first be defined in the ADD CHGANA command, and modified in the
command MOD CHGMODE before being referenced here.
[Outgoing trunk group number]

4-42

It is one of the conditions for judging charging case changes. It specifies the number of
the outgoing trunk group used by the system to connect an outgoing call or a tandem
call. The parameter must be defined in the commands ADD SIPTG, ADD H323TG,
ADD N7TG, ADD N1TG, and ADD PRATG before being referenced here.
[Bearer capability]
It defines the distinctive charging of calls of different services or bearer capabilities. Set
it by the following principles:
z
If IP audio is selected, only IP audio part is charged.
If IP video is selected, only IP video part is charged.
[Codec]
z
[New charging case]
It specifies the new charging case obtained after the system analyzes the above
conditions. The parameter must be defined in the command ADD CHGANA and
modified in the command MOD CHGMODE before being referenced here.
4.5.7 Adding charging band number change

I. Related commands
Command
Function
ADD CHBCHG
To add charging band number change
RMV CHBCHG
To remove charging band number change
MOD CHBCHG
To modify charging band number change
LST CHBCHG
To list charging band number change

4-43


In normal cases, when the local office uses the charging manner of Receive CRG
band number, and acts as a charging office in a call, the SoftX3000 retrieves a
charging case for the charging of the call from the local database according to the
charging band number sent by the charging determining office (a tandem office or the
terminating office) in the charging analysis of an outgoing call or a tandem call.
When the local office acts a charging office, as in the above case, it uses the charging
band number sent by the charging determining office as the only reference for charging
analysis. However, the situation is different in other cases. For example, the carrier
wants to distinguish the charging of a call according to the bearer capability of the
service and codec of the media stream. That is, the local office concurrently uses the
charging band number, bearer capability of the service, and code of the media stream
sent by the charging determining office as the references for charging analysis. Here
you need to add charging band number change by executing the command ADD
CHBCHG.

It is one of the conditions for judging changes of charging band numbers. It specifies
the charging band number (contained in a CRG or CHB message) sent by the charging
determining office to the local office in a call when the local office uses Receive CRG
band number for Charging manner, and acts as a charging office in the call.
It is one of the conditions for judging charging case changes. It specifies the number of
the outgoing trunk group used by the system to connect an outgoing call or a tandem
call. The principles for configuring the parameter are as follows:
z
If the parameter is set to 65535 (default value), the system does not judge the
outgoing trunk group number when adding charging band number change. That is,
the configuration data is suitable for all outgoing trunk groups.
If the parameter is set to a specific outgoing trunk group, the system needs to
judge the outgoing trunk group number when adding charging band number
change. In this case, the parameter must be defined in the commands ADD
SIPTG, ADD H323TG, ADD N7TG, ADD N1TG, and ADD PRATG before being
referenced here.
[Bearer capability]
It is one of the conditions for judging charging case changes. It implements the
distinctive charging of calls of different services or bearer capabilities. For example,
suppose that subscriber A is an ESL subscriber, and subscriber B is an ISDN
subscriber. To implement the distinctive charging of the two subscribers, set Bearer

4-44

capability of subscriber A to Analog call analog or Analog call digital, and that of
subscriber B to Digital call digital or Digital call analog, and so on.
parameters.
[Codec]
z
[New charging band number]
It specifies the new charging band number obtained after the system analyzes the
above conditions. The parameter must be defined in the command ADD CHGBAND
4.5.8 Adding Caller Charge Failure Processing

I. Related Commands
Command
Function
ADD CLRCFP
To add caller charge failure processing
RMV CLRCFP
To remove caller charge failure processing
MOD CLRCFP
To modify caller charge failure processing
LST CLRCFP
To list caller charge failure processing

By default, the SoftX3000 neither records unsuccessful calls nor generates bills for
them.
In some speical applications, the carrier might expect the SoftX3000 to record the failed
calls of some callers or incoming trunks under certain conditions, that is, to generate
watch bills or failure bills that are different from detailed bills, thus providing original
data for such activities as analysis of call compleiton rate and failure cause and
charging.
4-45


[Watch point]
It determines the time when the SoftX3000 watches unsuccessful calls. The options are
z
Caller occupy: To watch the calls failed before callers dial the called numbers.
Call process: To watch the calls failed after callers dials the called numbers but
before the called phones ring.
Called occupy: To watch the calls failed after the called phones ring.

It indicates the charging source code for the local callers or incoming trunk groups for
which watch bills are to be generated. It must be defined in the ADD CHGGRP or ADD
CHGIDX command before being referenced here.
[Watch type]
It defines the type of failed calls to be watched, such as intra-office calls, local calls,
local toll calls, national toll calls, or international toll calls.
[Watch cause]
It indicates the specific cause for call or connection failure. It is a key parameter
determining whether a watch bill can be generated by being compared with the failure
cause code automatically generated by the call processing software or that pre-defined
in the prefix processing table (defined in the ADD PFXPRO command).
[Bill type]
It indicates the final processing for call watch. The options are
z
No fail bill: To generate no bill.
Watch detail bill: To generate watch bills that are not used for charging.
Charge bill: To generate detailed bills or meter bills used for charging purposes.
The bill type is determined by the parameter Charge case.
[Charge case]
It is valid only when Bill type is set to Charge bill, indicating the charge case used by
charge bill. At different watch points, the SoftX3000 judges charge cases through
different condition combinations.
z
When the watch point is caller occupy, the SoftX3000 can judge the charge case
by analyzing the caller charging source code only.
When the watch point is call process, the SoftX3000 can judge the charge case
by analyzing the caller charging source code and the destination code. It is similar
to destination code charging.
When the watch point is called occupy, the SoftX3000 can judge the charge case
by analyzing the caller charging source code and the called charging source code.
It is similar to local office packet charging.

4-46

It must be defined in the ADD CHGANA command and modified in the MOD
CHGMODE command before being referenced here.
[Destination code]
It is valid only when watch point is set to call process. It determines a charge case in
combination with the parameter caller charging source code in this command, which
is similar to destination code charging.
[Callee charging source code]
It is valid only when watch point is set to called occupy. It determines a charge case
in combination with the parameter caller charging source code in this command,
which is similar to local office packet charging.
4.5.9 Adding Callee Charge Failure Processing

I. Related Commands
Command
Function
ADD CLDCFP
To add callee charge failure processing
RMV CLDCFP
To remove callee charge failure processing
MOD CLDCFP
To modify callee charge failure processing
LST CLDCFP
To list callee charge failure processing

By default, the SoftX3000 neither records unsuccessful calls nor generates bills for
them.
In some speical applications, the carrier might expect the SoftX3000 to record the failed
calls of some callees or outgoing trunks under certain conditions, that is, to generate
watch bills or failure bills that are different from detailed bills, thus providing original
data for such activities as analysis of call compleiton rate and failure cause and
charging.

[Watch type]
It defines the type of failed calls to be watched, such as intra-office calls, local calls,
local toll calls, national toll calls, or international toll calls.
[Watch cause]
It indicates the specific cause for call or connection failure. It is a key parameter
determining whether a watch bill can be generated by being compared with the failure
cause code automatically generated by the call processing software or that pre-defined
in the prefix processing table (defined in the ADD PFXPRO command).
4-47

[Callee charging source code]s

It indicates the callee charging source code of intra-office subscribers for whom watch
bills are to be generated. It must be defined in the ADD CHGCLD command before
[Charge case]
It indicates the charge case used by charge bill, similar to callee packet charging. It
must be defined in the ADD CHGANA command and modified in the MOD CHGMODE
command before being referenced here.
For the charge case referenced here, the payer must be callee.

4-48

Chapter 5 Configuring MG Data

5.1.1 Types of Media Gateways
You can classify the Media Gateways (also known as MGs) in multiple ways, according
to different views such as purposes and control protocols.
I. Based on purposes
The media gateways based on purposes are classified as follows:
Integrated Access Device (IAD)
Access Media Gateway (AMG)
Trunk Media Gateway (TMG)
Universal Media Gateway (UMG)
Media Resource Server (MRS)
Media Terminal Adapter (MTA)
Integrated Access Device (IAD): IAD is a device on the subscriber access layer in the
Next Generation Network (NGN) system. IAD is used to access the data, voice and
video services of subscribers to the packet switched network. The number of its
subscriber ports is generally not more than 48.
Access Media Gateway (AMG): AMG is used to provide multiple types of service
access for subscribers, such as analog subscriber access, Integrated Services Digital
Network (ISDN) access, V5 access and x Digital Subscriber Line (xDSL) access.
Trunk Media Gateway (TMG): TMG is the gateway located between the circuit
switched network and IP packet network. TMG implements the format conversion
between Pulse Code Modulation (PCM) signal stream and IP media stream.
Universal Media Gateway (UMG): UMG is used to implement media stream format
conversion and signaling conversion. It can function as AMG, TMG, embedded
Signaling Gateway (SG) and Video Interworking Gateway (VIG), and can be used to
connect PSTN exchange, Private Branch Exchange (PBX), access network, Network
Access Server (NAS), Base Station Controller (BSC), and 3G multimedia gateway.
Media Resource Server (MRS): MRS is a special gateway device, used to provide the
media processing functions for the basic services and supplementary services,
including service tone provision, conference resources provision, Interactive Voice
Response (IVR), announcements, and advanced voice services.
Media Terminal Adapter (MTA): MTA is a device that is loaded with Network-based
Call Signaling (NCS) protocol and located at the subscriber access layer. MTA is used

5-1

to access the data, voice, and video services of users to the IP packet network through
the cable TV network.
II. Based on control protocols

The media gateways based on control protocols are classified as follows:
MGCP gateway
H.248 gateway
SIP gateway
H.323 gateway
MGCP gateway: Media gateways (usually IAD, AMG, MRS, and MTA) communicate
with the SoftX3000 (serving as an MGC) through the Media Gateway Control Protocol
(MGCP).
H.248 gateway: Media gateways (usually IAD, AMG, TMG, and UMG) communicate
with the SoftX3000 (serving as an MGC) through the H.248 protocol.
SIP gateway: Media gateways (usually multimedia terminal and IAD) communicate
with the SoftX3000 (serving as an SIP server) through the Session Initiation Protocol
(SIP).
H.323 gateway: Media gateways (usually multimedia terminal and IAD) communicate
with the SoftX3000 (serving as a gatekeeper) through the H.323 protocol.
5.1.2 Media Stream Codec Mode

A media gateway is used to convert the media (such as audio, video, or fax) in one
bearer network to the media in the format required by another.
For example, TMG can convert PCM media stream in the circuit switched network to
G.723.1 media stream in the packet switched network; VIG can convert H.263 media
stream in the fixed multimedia network to MPEG4 media stream in the 3G multimedia
network; MRS can convert media steams in duplex mode and play audio messages to
achieve Interactive Voice Response (IVR) function.
To implement the above functions, the media gateway must be able to support media
stream codec modes as follows.
Voice codec mode
Video codec mode
Facsimile codec mode
I. Voice codec mode

The media gateway supports four kinds of voice codec modes, namely G.711, G.726,
G.723.1, and G.729 A.
G.711

5-2

It is a waveform codec mode without compression involved. The data is directly derived
from PCM with the sampling rate of 8000 Hz and bit rate of 64 kbit/s. According to the
codec algorithm, 64 kbit/s can be further divided into A law and law. In this codec
mode, the voice quality is the best, and the codec mode requires the most bandwidth of
the transmission channel. G.711 is mainly used in the legacy circuit switched network.
G.726
It is a waveform codec mode with compression involved, with the sampling rate of 8000
Hz. There are four bit rates after compression, 16kbit/s, 24kbit/s, 32kbit/s, and 40kbit/s.
Being a complete ADPCM voice codec standard recommended by the ITU-T, G.726 is
widely used on the traditional circuit switched networks. The scheme at a low bit rate
can also be used for Voice over IP (VoIP).
G.723.1
It is a parameter codec mode with compression involved, with the sampling rate of 8000
Hz. There are two bit rates after compression, 6.3 kbit/s and 5.3 kbit/s. In this codec
mode, the voice quality is relatively good but the processing delay is rather great. It is
the standardized voice codec mode at the lowest rate currently.
G.729 A
It is a parameter codec mode with compression involved, with the sampling rate of 8000
Hz. The bit rate after compression is 8 kbit/s. The voice quality in this codec mode is
between those in G.711 and G.723.1. The capability to prevent random bit error is the
same with that to prevent random burst loss of frames. In the environment with loud
noise, the voice quality is good.
If the terminal has the three kinds of codecs: G.711, G.726, G.723.1, and G.729 A, the
mode to be used is determined through the capability negotiation between the media
gateways, or specified by the MGC through control protocol.
II. Video codec mode

The media gateway supports two kinds of video codec modes, namely H.261 and
H.263. H.261 is a video codec mode based on transmission rate of n64kbit/s, while
H.263 is based on lower bit rate (about 20 kbit/s). Table 5-1 shows the technical
specifications of video codec mode.
Table 5-1 Technical specifications of video codec mode
Codec mode
H.261
H.263
H.263
Output format
Maximum frame rate
Resolution
CIF
15 frames per second
352 288
QCIF
176 144
CIF
352 288
QCIF
176 144
S-QCIF
128 x 96

5-3

H.261
H.261 is also called Px64 kbit/s, with P ranging from 1 to 30. It uses the combined
coding algorithm of constant code stream & variable quality instead of constant quality
& variable code stream. H.261 is initially designed for video telephone and video
conference implemented on basis of ISDN, so it is mainly applicable for the circuit
switched network.
H.263
H.263 is an ultra-low-code-rate video coding standard defined by ITU-T for the
narrowband communication channels lower than 64 kbit/s. H.263 is developed on basis
of H.261, combining the algorithms of inter-frame prediction minus time redundancy
and DCT conversion coding minus space redundancy.
III. Facsimile codec mode

Media gateway supports the following facsimile codec modes:
Normal mode
Media gateway encodes facsimile signals sent by a facsimile machine to be voice
codes (such as G.711, G.723, or G.729), and encapsulates them in RTP data packets
which will be transmitted in real time on the IP network. Because the transmission of
RTP data packets is based on UDP only which does not provide a forward error
correction mechanism, facsimile communication in such a normal mode is sensitive to
loss of packets. Once some packets are lost during the transmission, the video at the
receiver may be incomplete or the facsimile may be interrupted.
T.38 mode
Media gateway encodes facsimile signals from a facsimile machine according to the
encoding mode recommended in the T.38 protocol, and encapsulates them in IFP data
packets which will be transmitted in real time on the IP network. The transmission of IFP
data packets is based on either TCP or UDP. In the case of TCP, the TCP provides a
mechanism to guarantee the reliability of the transmission by itself. In the case of UDP,
the T.38 protocol provides a forward error mechanism. Therefore, an outstanding
advantage of the T.38 mode is its high reliability which ensures a high quality of
facsimile.
5.1.3 Gateway Registration Mode

NGN is an open and distributed network, which separates bearer from control. An MGC
manages the media gateways through IP packet network, which is actually
implemented through the registration and authentication between the media gateways
and MGC.
Serving as MGC, the SoftX3000 supports multiple registration modes of media
gateways, and interconnects the media gateways of other manufacturers. It features
flexible networking capability and high security.
5-4

I. Adopting MGCP or H.248

When a media gateway adopts MGCP or H.248 protocol, the mode of its registration
with the SoftX3000 depends on the format of the MID carried in the registration request
from the media gateway to the SoftX3000.
When the MID is a string of characters (usually a domain name), the SoftX3000
authenticates the media gateway based on the domain name.
When the MID is in the format for IP address, the SoftX3000 authenticates the
media gateway based on the IP address.
When the MID is in the format of IP address + UDP port number, the SoftX3000
authenticates the media gateway based on both the IP address and the UDP port
number.
The SoftX3000 supports either of the preceding registration modes. The specific mode
to be used must be negotiated with the media gateway side.
II. Adopting SIP or H.323

When a media gateway adopts SIP or H.323 protocol, there are the following cases:
Based on user identifier + registration password
When the media gateway applies to the SoftX3000 for registration for the first time and,
after a successful registration, the SoftX3000 audits the media gateway periodically,
the SoftX3000 regards the user identifier and registration password of the media
gateway as the authentication elements.
Based on IP address
the SoftX3000 regards the IP address of the media gateway as the authentication
element.
Based on IP address + user identifier + registration password
the SoftX3000 regards the IP address of the media gateway, user identifier, and
registration password as the authentication elements.
5.2 Configuring Gateway Data

5.2.1 Overview
I. Configuration relationship
The gateway data is used to define the information such as equipment ID, IP address,
password and UDP port number of the media gateway connected to the SoftX3000.

5-5

Before configuring media gateway data, make sure that equipment information has
been configured. See Figure 5-1.
Start
Equipment data
Trunk data
Office data
Number analysis
Charging data
Subscriber data
MG data
Centrex data
MRS data
Call barring data
Protocol data
IN service data
Signaling data
Other service data
Routing data
Other application
data
End

During the configuration, some parameters defined in the equipment information are
referenced in the MG data, and the parameters defined in the MG are referenced when
MRS resource data, protocol data, signaling data, trunk data, subscriber data, and
Centrex data is configured. The broken lines in Figure 5-1 show the referencing
relationships and Table 5-2 shows the details.
Table 5-2 Parameter referencing relationship between MG data and other data
Input parameter
Name
Output parameter
Defined in
Name
Referenced in
Module number
of FCCU/FCSU
Equipment
information
Equipment ID
of the media
gateway
MRS resource data, protocol

data, signaling data, trunk
data and subscriber data
IP address of FE
port
Equipment
information

5-6

II. Preparations
Before configuring MG data, make sure that all preparations are done as specified in
Table 5-3.
SN
Item
Remark
Protocol adopted by the media

gateway
For interworking with the media gateway
IP address of the media gateway
For interworking with the MGCP gateway

or H.248 gateway
Domain name of the media

gateway

or H.248 gateway
Local UDP port number at the

MGC side

or H.248 gateway
Local UDP port number at the

MG side

or H.248 gateway
Interface name of the media

gateway
Codec of the media gateway

or H.248 gateway
Encryption algorithm and key of

the media gateway (optional)

or H.248 gateway
Subscriber ID
For interworking with the media gateway
10
Registration password
For interworking with the H.323 gateway

or SIP gateway

Table 5-4 lists the general steps for configuring the gateway data.
Step
Description
Command
Set MGCP protocol parameter (optional)
SET MGCPPARA
Set Diffie-Hellman Authentication P Parameter

(Optional)
SET DHAUP
Add termination ID layer configuration (Optional)
ADD TIDLAY
Add media gateway
ADD MGW

5-7

Step
Description
Command
ADD MMTE (Add one
multimeida device)
Add multimedia device
ADB MMTE (Add a

batch of multimedia
devices)

During the configuration, the key parameters of the data tables are not referenced
mutually.
5.2.2 Setting MGCP Protocol Parameter (Optional)

I. Related commands
Command
Function
SET MGCPPARA
To set MGCP protocol parameter
LST MGCPPARA
To list MGCP protocol parameter

This configuration is optional. Read the following contents before using the command.
By default, the SoftX3000 supports the MGCP of version 1.0 defined in RFC2705. This
version conforms to the following prescriptions:
The MGCP message codes are in text format.
The number of the UDP port at the MGC side is 2727.
Generally, you do not need to modify the above parameters. When the actual UDP port
number or version number is not consistent with the mentioned case, you need to use
the SET MGCPPARA command to modify the MGCP parameters.

[Local MGCP port]
It redefines the number of the UDP port involved in the communication between the
SoftX3000 and MGCP gateway. Actually, it is the local UDP port number at the MGC
side. By default, the value is 2727. Modifying this parameter may affect the
communication between the media gateways adopting MGCP (including MRS) and the
SoftX3000. More seriously, if the SoftX3000 has been configured with MGCP media
gateway data, modifying this parameter will lead to forced deregistration of the
registered media gateways, and then service congestion of most MGCP media
gateways. You must confirm the necessity before modification.
5-8

[Version]
It defines the version number of MGCP. The default value is 10, indicating that the
MGCP version number is 1.0. If the value is 11, it indicates that the version number is
1.1. You can assign the value according to this principle.
5.2.3 Setting Diffie-Hellman Authentication P Parameter (Optional)

I. Related commands
Command
Function
SET DHAUP
To set Diffie-Hellman authentication P parameter
LST DHAUP
To list Diffie-Hellman authentication P parameter

The Diffie-Hellman (DH) authentication algorithm is used to generate a secret key
shared between an MG and an MGC (SoftX3000) to protect the communication
between the MG and the MGC against unauthorized access of a gateway to the system
through IP address embezzlement. The basic theory of the DH authentication algorithm
is explained below:
1)
Set an index P and a base number G. Select a digit for the MG and the MGC
respectively randomly (a and b, for example). Calculate the common values with
the following formulas:
A=Ga mod P
2)
B=Gb mod P
The MG sends A to the MGC, and the MGC sends B to the MG. Calculate the
common values with the following formulas. Use the common values A and B as
the base numbers to generate the shared secret key.
Ba mod P=Gab mod P=Ab mod P
To use the DH authentication algorithm between the MG and the MGC, the MG must
negotiate with the MGC about the P parameter. At the SoftX3000, you can define P
parameter with SET DHAUP.

[P Parameter]
It is one of the parameters for the SoftX3000 to interconnect with a media gateway.
When the DH authentication algorithm is needed between the SoftX3000 and a media
gateway, this parameter defines the P parameter used in the DH authentication
algorithm. It is a string of 192 characters.

5-9

5.2.4 Adding Termination ID Layer Configuration (Optional)

I. Related commands
Command
Function
ADD TIDLAY
To add termination ID layer configuration
RMV TIDLAY
To remove termination layer configuration
MOD TIDLAY
To modify termination ID layer configuration
LST TIDLAY
To list termination ID layer configuration

This configuration step is optional. Read the following contents before using the
command.
According to MGCP or H.248, a media gateway identifies its internal termination
resources such as subscriber ports, circuit timeslots, digital and voice channels, and
RTP terminations in format of prefix + number. Number is mandatory and can only be
decimal digits; while prefix is optional and can only be a string of characters (digits are
also characters without specific meaning).
If a termination ID contains only a string of meaningful prefix + number, it is not
defined hierarchically. That is, the media gateway identifies its internal termination
resources from 0 or 1 in turn, for example, aaln/0, ms/cnf/100, A31, and RTP/20.
For the IAD applying MGCP, aaln/0 stands for subscriber port 0. For the MRS
applying MGCP, ms/cnf/100 stands for digital and voice channel 100. For the TMG
applying H.248, A31 stands for circuit timeslot 31, and RTP/20 stands for RTP
termination 20.
If a termination ID contains several strings of meaningful prefix + number, it is
defined hierarchically. That is, the media gateway identifies its internal termination
resources relatively by certain hierarchical relationship, for example, S01/A02 and
S02/E03/10. Each of S01, A02, S02, E03, and 10 indicates one layer with specific
meaning. For the AMG applying MGCP, S01/A02 stands for subscriber port 2 in
slot 1. For the TMG applying H.248, S02/E03/10 stands for circuit timeslot 10 of E1
port 3 in slot 2.
By default, the SoftX3000 regards that all media gateways interconnected with it
identify their termination resources non-hierarchically, and it has preset four
frequently-used prefixes (that is, interface names): A, RTP/, aaln/, and ms/cnf/.
Therefore, when the SoftX3000 interconnects with a media gateway manufactured by
Huawei, you can directly reference the termination ID layer configuration preset by the
system when executing ADD MGW.

5-10

When the SoftX3000 interconnects with a media gateway developed by other

companies (for example, Cisco, or Siemens), if the media gateway identifies its
termination resources hierarchically, you must first use ADD TIDLAY to add termination
ID layer configuration data, and then reference the data when executing ADD MGW.
Otherwise, the SoftX3000 cannot interwork well with the media gateway.

[TID layer Index]
It defines a TID layer index uniquely in the SoftX3000, ranging from 0 to 499. TID layer
indexes 0 to 3 are default values, and you cannot set or remove them.
TID layer index 0: There is only one layer; the prefix is A; the offset is 0; and the
length of digits is 0.
TID layer index 1: There is only one layer; the prefix is RTP/; the offset is 0; and the
TID layer index 2: There is only one layer; the prefix is aaln/; the offset is 0; and the
TID layer index 3: There is only one layer; the prefix is ms/cnf/; the offset is 0; and
the length of digits is 0.
[Layer number]
It defines the number of actual layers of a TID, ranging from 1 to 10. When it is 1, it
means that TIDs are defined non-hierarchically. When it is greater than 1, it means that
TIDs are defined hierarchically.
[Prefix of 1st layer] to [Prefix of 10th layer]
They are among the interconnection parameters between the SoftX3000 and a media
gateway and define the prefixes in various layers of prefix + number in a TID. Set this
parameter by the following principles:
A prefix is optional and can either be null or a string of characters. When it is a
string of characters, it can contain letters, digits, _, @, $, /, and -, and the
maximum length of a prefix is 16 characters. Digits are treated as characters
without specific meaning.
When the layer number is 1, the prefix of the first layer cannot be null generally,
that is, you need to define a valid character string as the prefix of the first layer.
This string is usually called interface name.
When the layer number is greater than 1, the system inserts a / between each
layer automatically. In this case, the layers are numbered from right to left. For
example, if a TID is A01/B02/C03, it means that it is defined by three layers: C03 is
the first layer; B02 is the second layer; and A01 is the third layer. The prefix of the
first layer cannot be null, while those of other layers can.
No matter how many the layers are, a TID cannot be longer than 64 characters.
The length of a TID is composed of that of prefixes of the layers, that of numbers of
the layers, and that of "/ between.
5-11

[Offset of 1th layer] to [Offset of 10th layer]

When processing a received TID, the SoftX3000 first abstracts the number (digit) in the
character string prefix + number of each layer, and then converts them into binary
codes, and finally reorganizes the binary codes into a 32-bit code (0 for vacant bits)
according to the sequence of the codes in the TID. Offset of each layer is used to define
the position of the lowest significant bit of the converted number of each layer in the
32-bit code. It ranges from 0 to 31. Set this parameter by the following principles:
Unless otherwise specified, set the offset of the first layer to 0.
The offset of a higher layer must be greater than that of a lower layer. For example,
if the offset of the second layer is 4, that of the third layer must be greater than 4;
otherwise, it is invalid.
Suppose the offset of a layer is a, the numer part of the layer is in length of n (n is
not 0). If the offset of its adjacent higher layer is b, the number of this layer ranges
from 0 to MIN (2b-a-1, 10n-1).
Suppose the offset of a layer is a, the numer part of the layer is in length of n (n is
not 0). If you do not define the offset of its adjacent higher layer, the number of this
layer ranges from 0 to MIN (232-a-1, 10n-1).
[Number length of 1th layer] to [Number length of 10th layer]
They define the length of the number in character string prefix + number of each layer
in a TID, ranging from 0 to 13. Set this parameter by the following principles:
If one of them is set to 0, it means that the number length of a certain layer is
variable. The maximum number length of the layer depends on the offset of the
layer and that of its adjacent higher layer. Refer to the above parameter for the
calculation.
If one of them is set to a non-zero value, it means that the number length of a
certain layer is fixed, and 0 is filled for vacant bits. For example, if the number
length is 3 but the number is 1, it will be converted to 001 in a TID.
5.2.5 Adding Media Gateway

I. Related commands
Command
Function
ADD MGW
To add media gateway
RMV MGW
To remove media gateway
MOD MGW
To modify media gateway
LST MGW
To list media gateway

5-12


Before adding MGCP gateway or H.248 gateway, use the related commands to get the
following parameters defined by the system.
Module number of FCCU/FCSU: LST MDU
IP address of FE port: LST FECFG

[Equipment ID]
This is one of the interconnection parameters between the SoftX3000 and the media
gateway, used to uniquely identify a media gateway in string of 32 characters at most.
The equipment ID is equivalent to the registration account of the media gateway. Its
expression depends on the format of the MID carried in the registration request sent by
the media gateway to the SoftX3000. For example, if the MID is a string of characters,
the equipment ID of the media gateway at the SoftX3000 side is a string of characters,
too. If the MID is an IP address, the equipment of the media gateway at the SoftX3000
is an IP address, too.
The SoftX3000 supports either 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.
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.
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, 210.10.11.86:
2944.
[Gateway type]
It defines the type of the media gateway to be added. There are totally six types,
namely Access Gateway (AG), Trunk Gateway (TG), IAD, UMG, MRS, and MTA.
If it is set to MRS, it indicates that the media gateway added is an external MRS (for
example, MRS6000 or MRS6100). To add an internal MRS, you need not execute the
command ADD MGW.
[MGW description]
It describes a media gateway to facilitate maintenance.
[FCCU/FCSU module number]
It specifies the module number of the FCCU or FCSU at the SoftX3000 side, which is
responsible for processing the call control messages of the media gateway. The value
range is from 22 to 101. This parameter must have been defined by the ADD BRD

5-13

Because one FCCU/FCSU can process a maximum of 50,000 voice subscribers or

50,000 SIP subscribers or 25,000 H.323 subscribers or call control messages of 9,000
TDM trunk circuits, you need to plan the processing ability of each FCCU/FCSU in
advance when adding a media gateway, so as to avoid overflow of tuples during
addition of subscribers or trunks.
[Protocol type]
It is one of the parameters used for interworking with the media gateway. It specifies the
protocol type adopted by the media gateway from MGCP and H.248 protocol. Currently,
TG and UMG adopt H.248 protocol, and you do not need to configure this parameter for
them.
[Support dynamic IP address]
It is one of the parameters used for interworking with the media gateway. When the
media gateway is an AMG, IAD, or MTA, this parameter is available to specify, at the
SoftX3000 side, the IP address assignment mode of the media gateway.
[Local IP address]
IP address of the FE port at the SoftX3000 side that processes all the protocol
messages of the media gateway. This parameter must have been defined by the ADD
FECFG command before being referenced here.
[Remote IP address 1] to [Remote IP address 5]
Used for interworking with the media gateway. Each specifies the IP address of the
media gateway. Remote address 1 must be specified, while the other addresses may
be specified according to the actual configuration of the media gateway (they are
mainly used for interworking with Huawei developed UMG8900).
Set it by the following principles:
If the type of the media gateway is AMG or IAD using a static IP address, the
remote address 1 is set to the actual IP address of the AMG or IAD and the
Support dynamic IP address parameter in this command must be set to Not
supported.
If the type of the media gateway is AMG or IAD using a dynamic IP address (or
connected to the SoftX3000 through NAT), the remote address 1 can be set to any
IP address that you make and the Support dynamic IP address parameter in this
command must be set to Supported.
If the type of the media gateway is TMG or UMG, the remote address 1 is set to the
IP address of the TMG or UMG for communications through H.248.
If the media gateway is MRS6100, the remote IP address 1 is set to the IP address
of the MCCU.
If the media gateway is MRS6000, the remote IP address 1 is set to the internal IP
address of the MPC.
[Remote port]
5-14

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.
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.
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 MGCP, the local
UDP port number at the SoftX3000 side is 2727 by default, and you can modify it
with the SET MGCPPARA command.
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]
codec capabilities supported by the media gateway.
The codec list for a media gateway configured at the SoftX3000 side must have
intersections with the codec capabilities supported by the media gateway actually;
otherwise, this media gateway cannot run normally.
Generally, the codec list for a media gateway configured at the SoftX3000 side
must be the same as the codec capabilities supported by the media gateway
actually. If the carrier has higher requirements on voice and fax quality, select
PCM A, PCM , and T.38.
If you do not know the codec capabilities supported by a media gateway, select
PCM A, PCM , G.723.1, G.729 A, G.726, and T.38.
For the UMG acting as VIG, select all codec types, or select PCM A, PCM ,
G.723.1, AMR, H.261, H.263, and MPEG4.
[Hairpin connection]
It is one of the parameters used for interworking 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.
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.

5-15

If you select Not Supported, the external IP packet network implements all the
media stream exchanges.
[EC]
It is one of the parameters used for interworking 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:
Support: This option indicates that 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.
Not Support: This option indicates that the media gateway does not have the EC
function. The SoftX3000 cannot operate the EC resources on the media gateway
through the MGCP or H.248 protocol.
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.
[Code type]
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.
For MGCP, the SoftX3000 only supports ABNF.
For H.248 protocol, the SoftX3000 supports both ABNF and ASN.1. By default, the
system supports ABNF.
[Special attributes]
It defines the special attributes of the media gateway when applied in the actual
networking. The parameter options are described as follows.
SDP HEX: This option indicates whether the Session Description Protocol (SDP)
packets sent by the SoftX3000 to the media gateway use the HEX format.
Because most media gateways only identify SDP packets in text format but not
those in hex format, select this option only when the media gateway is TMG8010
of Huawei. This option is not selected in other cases.
No BNC character: This option indicates whether the H.248 protocol messages
sent by the SoftX3000 to the media gateway do not carry a BNC Character packet
that identifies whether the bearer network is the ATM network or the IP network.
Because most media gateways regard the IP network as the bearer network by
default, that is, the H.248 protocol messages sent by the SoftX3000 to the media
gateway do not carry a BNC Character packet. Do not select this option only when
the media gateway is UMG8900 of Huawei. This option is selected in other cases.
No Echo cancellation: This option indicates whether the MGCP messages or
H.248 messages sent by the SoftX3000 to the media gateway do not carry an
5-16

Echo canceller field. Echo canceller is one of the attributes of media stream,
indicating the EC mode (not started, G.165, or G.168) that media stream adopts.
Currently, most media gateways support the Echo canceller field, so do not
select this option for most media gateways.
No jitter: This option indicates whether the MGCP messages or H.248 messages
sent by the SoftX3000 to the media gateway do not carry a Jitter Buffer field. Jitter
buffer is one of the attributes of media stream, indicating the duration (in
millisecond) of the jitter buffer needed by media stream. At present, most media
gateways do not support the Jitter buffer field, so select this option for most
media gateways.
No fax: This option indicates whether the MGCP messages or H.248 messages
sent by the SoftX3000 do not instruct the media gateway to detect the fax signal
tones of the terminal devices. If the media gateway does not support the detection
of fax signal tones, select this option to achieve correct interworking between the
SoftX3000 and media gateways provided by other vendors. If the media gateway
supports the detection of fax signal tones, do not select this option. If this option is
selected and the media gateway treats the detection of fax signal tones of terminal
devices as a permanent event, the SoftX3000 can still identify the related
messages reported from the media gateway. In other words, fax communication
can still work.
No modem: This option indicates whether the MGCP messages or H.248
messages sent by the SoftX3000 do not instruct the media gateway to detect the
modem signal tones of the terminal devices. If the media gateway does not
support the detection of modem signal tones, select this option to achieve correct
interworking between the SoftX3000 and media gateways provided by other
vendors. If the media gateway supports the detection of modem signal tones, do
not select this option. If this option is selected and the media gateway treats the
detection of modem signal tones of terminal devices as a permanent event, the
SoftX3000 can still identify the related messages reported from the media
gateway. In other words, modem communication can still work.
Local SDP address present: This option indicates whether to carry the local IP
address in the Add/Modify messages when the local codec is to be modified.
Because most media gateways need not carry the local IP address in modification
of the local Codec, so select this option only when the media gateway is a special
IAD (for example, IAD using waveform coding mode). This option is not selected in
other cases.
V3 fax flow: This option indicates whether the media gateway supports the T.38
fax communication procedure defined in the SoftX3000 V300R001 and later
software versions. Select this option in most cases. This option is not selected only
when the media gateway uses a software version that matches with the SoftX3000
V200R101.

5-17

Endpoint start from 0: The endpoints of the MGCP gateway are coded from 0. For
most MGCP media gateways, the endpoints are coded from 1.
Support 2833: This option indicates whether the media gateway supports the
RFC2833 protocol, that is, whether two media gateways (such as TMG and MRS)
interact with each other in the transparent transmission mode or through the
RFC2833 protocol to exchange number related information. In most cases, when
the media gateway is MRS6000 or MRS6100, select this option. For the other
media gateways, if they support RFC2833, it is recommended to select this option,
for it can facilitate the use of IN services.
MGW support send tone: This option indicates whether the media gateway
supports tone sending. Generally, when the terminal subscribers of such voice
media gateways as IAD and AMG use supplementary services such as call
waiting, the SoftX3000 controls the MRS to play the call waiting tone to the
subscribers. If the carrier expects that the SoftX3000 controls a media gateway to
play the call waiting tone to the subscribers of this media gateway, you must select
this option.
Support 2198: This option indicates whether the media gateway supports
RFC2198, that is, whether RTP payload (RFC2833 packets, for example) is
transmitted between two media gateways in redundancy mode so as to improve
the reliability of RTP payload transmission. If you select this option, when a media
gateway sends the RTP payload, it will first packetize the RTP payload into
primary packets and redundant packets and then send them to the IP network
simultaneously. The recipient determines whether to use or discard them
according to the time stamp in the packets. Generally, if a media gateway is
MRS6000 or MRS6100, you need to select this option. For other media gateways,
whether to select it depends on the actual situation. If a media gateway supports
RFC2198, this option is recommended, for it benefits IN services.
AUEP E parameter: This option indicates whether the E parameter is audited
during the audit of the endpoint status. If the option is selected, the SoftX3000
audits the E parameter (ReasonCode, the reason code in the last command being
restarted or the last command for deleting connection. The command is sent by
the endpoint of the gateway). If the option is not selected, the SoftX3000 audits the
R parameter (RequestedEvents, the current value of the request event being used
by the endpoint of the gateway). When the SoftX3000 interconnects with a
gateway manufactured by other companies (for exmaple, Cisco), select this option
according to the actual requirements.
Expand al star: This option indicates whether to expand the al/* event. If the option
is selected, the al/* event will be expanded to al/of, al/on, or al/fl when the gateway
does not support the al/* event . If the gateway is manufactured by Huawai, do not
select the option. If the gateway is manufactured by other companies (for example,
Nortel), select the option according to the actual requirements.

5-18

No expand tonedet: This option indicates whether to expand the tonedet packet. If
the option is selected, the SoftX3000 uses tonedet/std packet when issuing the
event of number receiving number by number to the gateway. If it is not selected,
the SoftX3000 uses dd/std packet when issuing the event of number receiving
number by number to the gateway. When using Huawei gateway, you should not
select this option; when using the gateway of other companies (like Nortel), you
should select this option according to the actual conditions.
Reserved bit: This option is reserved.
For different types of media gateway, different default values are set for the
above-mentioned options. After adding a media gateway, you can query it with the
command LST MGW.
[Encryption type]
It is one of the parameters used for interworking with the media gateway. It specifies
whether to encrypt the protocol messages between the SoftX3000 and the media
gateway, as well as the encryption type. The default option is Not Supported.
If you select MD5, it indicates that the protocol messages need to be encrypted
and the MD5 encryption algorithm is adopted.
If you select Diffie-Hellman, it indicates that the protocol messages need to be
encrypted and the DH authentication algorithm is adopted.
[Key]
It is one of the parameters used for interworking with a media gateway. When
MGCP/H.248 messages between the SoftX3000 and a media gateway need to be
encrypted, this parameter is used to define the key required by the MD5 encryption
algorithm or the DH authentication algorithm. It is a string of 8 to 20 characters for the
MD5 encryption algorithm; and for the DH authentication algorithm, it is a string of 8 to
16 characters
[Media resource server]
It is one of the parameters used for the interconnection between the SoftX3000 and
UMG. It specifies whether to support MRS. The parameter options are described as
follows.
If you select Not Supported, the MRS resources carried by the UMG are not
available, and the required MRS resources are provided by the dedicated MRS
server.
If you select Supported, the MRS resources carried by the UMG are available,
and the required MRS resources are provided by UMG itself.
[Resource capability]
It defines the capability of an interface of the MRS, that is, to define what resource
devices the interface can support. It is available only when Gateway type is MRS.
The parameter options are described as follows:

5-19

Tone: basic tone and ordinary service voice.

Play Tone: Variable tones and intelligent service voice.
Send DTMF: Sending DTMF signal tone.
Detect DTMF: Detecting DTMF signal tone (equivalent to DTMF digit receiving
resources)
Multiparty: Multi-party conversation.
[Rate of tone], [Rate of MPTY], [Rate of detect DTMF], [Rate of send DTMF]
When the type of the media gateway is MRS, these paramemters are avaiable to
specify the ratio of service tone resources, of conference resources, of DTMF detection
resources, and of DTMF sending resources, The value range for each is 0 to 99999.
The default value is 100 for each. The configuration principles of these parameters are
as follows:
If the quantity of a kind of resources is set to 0, the MRS does not provide that kind
of resources for the SoftX3000 or the MRS is not capable of providing that kind of
resources.
If the quantity of a kind of resources is set to an integer rather than 0, the MRS
provides that kind of resources for the SoftX3000. In this case, the MRS must be
capable of providing that kind of resources; otherwise, the SoftX3000 may fail to
allocate the MRS resources.
It is recommended to set the quantity of a kind of resources at the SoftX3000 side
to the number of that kind of resources the MRS is capable of providing. If what
you set is less than the number of that kind of resources the MRS is capable of
providing, the resource capability of the MRS is not used fully. If what you set is
greater than the number of that kind of resources the MRS is capable of providing,
the SoftX3000 may fail to allocate the MRS resources.
If the SoftX3000 controls more than two MRSs, the system will select and allocate
resources of the several MRSs according to their resource capabilities. For example,
three MRSs are able to provide DTMF detection resources for the same SoftX3000, in
which the MRS1 provides a maximum of 100 DTMF detection resources, the MRS2 a
maximum of 200 DTMF detection resources, and the MRS3 a maximum of 300 DTMF
detection resources. Normally, the probability for the SoftX3000 to select the DTMF
detection resources of the MRS1 is 1/6, the probability to select the resources of the
MRS2 is 2/6, and the probability to select the resources of the MRS3 is 3/6. If all the
DTMF detection resources of the MRS3 are occupied, the probability for the SoftX3000
to select the resources of the MRS1 is 1/3, and the probability to select the resources of
the MRS2 is 2/3. Other cases can be deduced in the same way.
[Minimum termination ID], [Maximum termination ID]
They are used to define the number range of the termination resources on the specified
MRS that are available for the SoftX3000. The parameters are available only when
Gateway type is MRS.

5-20

For example, an MRS has 1000 termination resources (such as voices and DTMF digit
receivers), its TID is not defined hierarchically, and its interface name is ms/cnf.
Assuming that its termination ID range is ms/cnf/1 to ms/cnf/1000: if you specify the
"Min termination ID as 10 and Max termination ID as 99, only the termination
resources in the range from ms/cnf/10 to ms/cnf/99 can be used by the SoftX3000.
[Termination allocated by MRS]
It sets whether the termination resources are managed by the MRS or the SoftX3000.
For external MRS (MRS6000 or MRS6100, for example), usually FALSE and
sometimes TRUE can be selected. This parameter is available only when Gateway
type is MRS.
[TDM TID layer index]
It specifies how a media gateway defines the TDM termination IDs such as user ports,
circuit timeslots, digital and voice channels. It must be defined in ADD TIDLAY before
If the gateway type is TG or UMG, the default value of the parameter is 0,
indicating that the TDM TID (that is, interface name) is A.
If the gateway type is AG or IAD, the default value of the parameter is 2, indicating
that the TDM TID (interface name) is aaln/.
If the gateway type is MRS, the default value of the parameter is 3, indicating that
the TDM TID (interface name) is ms/cnf/.
[RTP TID layer index]
It specifies how a media gateway defines the RTP termination IDs. It must be defined in
ADD TIDLAY before being referenced here. By default, it is 1, indicating that the RTP
TID of the media gateway is RTP/.
[Master/Slave type]
follows:
Slave: This record of data belongs to the assistant office and is valid only when the
local office is operating in the mutual assistance active state.
The default option of the parameter is master, indicating this record of data belongs to
the local office. When you want to configure dual homing data for the assistant office,
this parameter is set to slave.
[User rate]
Reserved.
[DH Authentication MG ID]
It is one of the parameters for the SoftX3000 to interconnect with a media gateway.
When the DH authentication algorithm is needed between the SoftX3000 and a media
5-21

gateway, this parameter defines the gateway ID used in the DH authentication

procedure.
Gateway ID contains the manufacturer and equipment information of the media
gateway, and it is unique for a media gateway. It is a string of 8 to 16 characters.
5.2.6 Adding a Multimedia Device

I. Related commands
Command
Function
ADD MMTE
To add a multimedia device
RMV MMTE
To remove a multimedia device
MOD MMTE
To modify a multimedia device
LST MMTE
To list the configuration information of a multimedia device

Before adding SIP gateway or H.323 gateway, use the related commands to get the
following parameters defined by the system:
To get the module ID of the FCCU/FCSU: LST MDU
To get the module ID of the IFMI: LST MDU

[Equipment ID]
It is one of the parameters used for interworking with the multimedia device. It uniquely
identifies a multimedia device, consisting of a maximum of 32 characters (usually
digits). It is equivalent to the registration account of the media gateway. Therefore, the
same equipment ID cannot be assigned to several multimedia gateways. The format
for the equipment ID depends on the registration or authentication mode to be used by
the multimedia gateway.
It specifies the module number of the FCCU or FCSU at the SoftX3000 side, which is
responsible for processing the call control messages of the multimedia device. The
value range is from 22 to 101. This parameter must have been defined by the ADD
BRD command before being referenced here.
Because one FCCU/FCSU can process a maximum of 50,000 voice subscribers or
50,000 SIP subscribers or 25,000 H.323 subscribers or call control messages of 9,000
TDM trunk circuits, you need to plan the processing ability of each FCCU/FCSU in
advance when adding a media gateway, so as to avoid overflow of tuples during
addition of subscribers or trunks.
5-22

[Protocol type]
It is one of the parameters used for interworking with the multimedia device. It specifies
the protocol type used by the multimedia device, including H.323 protocol and SIP.
When the protocol type is set to SIP, this parameter is available to specify the
module number of an IFMI board for dispatching SIP messages from the multimedia
device. The value range is 132 to 211. This parameter is defined in the ADD BRD
command and referenced here.
[Device type]
It is one of the parameters used for interworking with the multimedia device adopting
H.323 protocol. It specifies the type of the multimedia device, including terminal and
IAD.
[Authorization password]
the password used by the multimedia device when registering with the SoftX3000. Its
value is composed of digits (0 to 9) and letters (a to e), and the maximum length must
not be more than 16.
[Authorization type]
the registration/authorization type used by the multimedia device when registering with
the SoftX3000. The parameter options are described as follows:
No authorization: Authorization is not required.
Authorized by EID: Authorization is implemented based on Equipment ID +
Registration password".
Authorized by IP: Authorization is implemented based on IP address.
Authorization By IP and EID: Authorization is implemented based on Equipment
ID + Registration password + IP address.
Currently, the SoftX3000 only supports to authenticate MCU (through the H.323
protocol) based on IP address.
[IP address for authorization]
the IP address of the multimedia device. When IP address based authorization mode
is used, the media gateway can neither use dynamic IP address nor access the
SoftX3000 through an NAT device.
[Master/Slave type]
follows:

5-23

[H245 route supported]
It is available only when the protocol type is H.323. When both caller and callee of a
call use H.323 terminals and one of the terminals works in slow start mode, this
parameter indicates if the SoftX3000 supports the transfer of H.245 route messages
from the H.323 terminals. By default, it is Not supported.
If you set it to Not supported, it means that the direct route is adopted between
the calling and the called H.323 terminals. That is, H.245 route messages are
transmitted between them directly. In this case, all H.245 messages between them
are not transferred by the SoftX3000, so the SoftX3000 cannot obtain such call
related information as media channel attribute and cannot provide such data in
bills.
If you set it to Supported, it means that GK route is adopted between the calling
and called H.323 terminals. That is, they interchange H.245 route messages
through a GK (SoftX3000).
5.2.7 Adding a Batch of Multimedia Devices

I. Related commands
Command
Function
ADB MMTE
To add a batch of multimedia devices
RVB MMTE
To remove a batch of multimedia devices
MOB MMTE
To modify the configuration information of a batch of multimedia

devices
LST MMTE
To list the configuration information of a batch of multimedia devices

Before adding SIP gateway or H.323 gateway, use the related commands to get the
following parameters defined by the system:
To get the module ID of the FCCU/FCSU: LST MDU
To get the module ID of the IFMI: LST MDU

5-24

Note:
The parameters for the ADB MMTE command are similar to those for the ADD MMTE
command. This section only presents the dedicated parameters in the ADB MMTE
comand. For the description of the other parameters, refer to 5.2.6
Adding a
Multimedia Device of this chapter.
[Start equipment ID], [End equipment ID]

They identify the range of equipment IDs for a batch of multimedia devices. When
adding a batch of multimedia devices, type digits instead of characters for equipment
IDs.
[Equipment ID step]
It refers to the difference between two equipment IDs in the case of adding a batch of
multimedia devices. It is 1 by default.
[Authorization password]
It is one of the parameters for interworking with the multimedia device. It defines the
password used by the multimedia device for registration in the SoftX3000. It consists of
a maximum of 16 characters that are digits (0 to 9) and letters (a to e).
Because all multimedia devices share one authorization password when you use the
command ADB MMTE, do not type the authorization password in the command ADB
MMTE for security purposes; instead, use the software tool for automatic generation of
multimedia subscriber number allocation command provided by Huawei to generate
the authorization password corresponding to the multimedia devices.
5.3 Configuring VIG Data

5.3.1 Overview
I. Preparations
Before configuring VIG data, complete the following preparations as listed in Table 5-5.
Table 5-5 Preparations to be completed
No.
Item
Remark
IP address of VIG
It is one of the parameters for interworking with VIG
Local
SCTP
port
number of each H.245
link (at Server side)
It is one of the parameters for interworking with VIG.

They should be planned in coordination with those
of M2UA links, M3UA links, V5UA links, and IUA
links.

5-25

No.
Item
Remark
Peer
SCTP
port
number of each H.245
link (at Client side)
It is one of the parameters for interworking with VIG
Gateway
of VIG
VIG gateway capabilities include audio, H.263

video, MPEG4 video, H.223 bearer, and H.223
multiplex.
capabilities

See Table 5-6 for the steps of configuring VIG data.
Table 5-6 Steps of configuring VIG data
Step
Description
Command
Add VIG
ADD MGW
Add VIG H.245 link
ADD VIGLNK
Add VIG gateway capabilities
ADD VIGCAP
III. Referencing relationships between tables

See Figure 5-2 for the referencing relationships between key fields of various data
tables used in the configuration of VIG data.

5-26

ADD MGW
[Equipment ID]
[Gateway type]
[MGW description]
ADD VIGLNK
[BSGI module number]
[Link number]
[Equipment ID]
ADD VIGCAP
[MGW capability]
[Equipment ID]
Figure 5-2 Referencing relationships between tables
5.3.2 Adding VIG

I. Related commands
Command
Function
ADD MGW
To add VIG
RMV MGW
To remove VIG
MOD MGW
To modify VIG
LST MGW
To list the configuration information of VIG

The VIG is the UMG89000 developed by Huawei, so addition of a VIG is actually that of
a UMG.

Refer to 5.2.5 Adding Media Gateway for details.

5-27

5.3.3 Adding VIG H.245 Link

I. Related commands
Command
Function
ADD VIGLNK
To add VIG H.245 link
RMV VIGLNK
To remove VIG H.245 link
MOD VIGLNK
To modify VIG H.245 link
LST VIGLNK
To list VIG H.245 link

To ensure the successful interconnection between the SoftX3000 and the VIG through
H.245 signaling links, use ADD VIGLNK to add H.245 signaling links and keep the
SCTP protocol data at the VIG side consistent with that at the SoftX3000 side. That is,
the SCTP messages received or sent by both parties must be checked with the
recommended algorithm CRC32.
Because the default SCTP protocol parameters at the SoftX3000 side conform to the
above requirements, you need to ensure that the SCTP protocol parameters at the VIG
(UMG8900) side must also comply with the above requirements in actual deployment.

It indicates the module number of the BSGI processing H.245 link protocol. It must be
defined in the ADD BRD first before it can be referenced here.
[Link number]
It indicates the logical number of an H.245 link in the BSGI, ranging from 0 to 31. In one
BSG module, all H.245 links are numbered uniformly. That is, one BSGI supports a
maximum of 32 H.245 links.
[Equipment ID]
It identifies the VIG (UMG8900) providing H.245 links. It must be defined in the ADD
MGW first and then referenced here.
[Local SCTP port number]
It is one of the parameters for interworking with VIG. It specifies the SCTP port number
used by the H.245 link messages at the SoftX3000 side. Follow the principles below to
configure this port number:
If the SoftX3000 works as a Server for H.245 links, it is recommended to configure
the same local SCTP port number for all H.245 links when there are multiple H.245
links between the SoftX3000 and a VIG.
5-28

If the SoftX3000 works as a Client for H.245 links, it is recommended to configure

different local SCTP port numbers for all H.245 links when there are multiple
H.245 links between the SoftX3000 and a VIG.
Because M2UA, M3UA, V5UA, IUA, and H.245 protocols are all based on SCTP, it
is recommended to set the range of the local SCTP port numbers for each protocol
link before data configuration for ease of management. Port numbers should not
be repeatedly used.
[Local IP address 1], [Local IP address 2]
They are the parameters for interworking with VIG, specifying the IP address(es) of the
FE port distributing H.245 messages at the SoftX3000 side. It must be defined in the
ADD FECFG first and then referenced here. The local IP address 1 is mandatory.
If the SoftX3000 is inserted with several IFMIs, you also need to specify the local IP
address 2. This setting supports the multi-homing functions of SCTP connections at the
SoftX3000 side so as to improve networking reliability.
[Peer SCTP port number]
It is one of the parameters for interworking with VIG, specifying the SCTP port number
used by H.245 messages at embedded SG side. If VIG works as a Client for H.245
links, different peer SCTP port numbers must be set for different H.245 links at the
SoftX3000 side.
[Peer IP address 1], [Peer IP address 2]
They are the parameters for interworking with VIG, specifying the IP address(es) of VIG,
that is, the IP address of the VPU in the UMG8900. The peer IP address 1 is
mandatory.
If VIG also supports the multi-homing functions of SCTP connections, you need to
specify the peer IP address 2. This setting supports the multi-homing functions of SCTP
connections at VIG side so as to improve networking reliability.
[Maximum number of incoming streams]
It defines the maximum number of incoming streams allowed at the local end during
establishment of SCTP connections. Use the default value 33 generally. After an SCTP
connection is established, the actual number of incoming streams is negotiated by both
ends.
[Maximum number of outgoing streams]
It defines the maximum number of outgoing streams allowed at the local end during
establishment of SCTP connections. Use the default value 33 generally. After an SCTP
connection is established, the actual number of outgoing streams is negotiated by both
ends.
[Client/Server flag]

5-29

It is one of the parameters for interworking with VIG, specifying the application mode of
the SoftX3000 in SCTP connections. It is Server by default. If the SoftX3000 works as
a Server, VIG must be a Client, and conversely the same.
[Active/Standby flag]
It indicates the work state of an H.245 link in normal conditions. The setting of it is
related to the transmission mode of the link.
If active/standby mode is used, you can only set one of all H.245 links in one link
set to Active, and set the others to Standby.
If load sharing mode is used, set all H.245 links in one link set to Active.
[Link priority]
It defines the priority of an H.245 link. The link with higher priority will be selected first.
0 stands for the highest priority, 1 stands for the second highest priority, and so on.
5.3.4 Adding VIG Gateway Capabilities

I. Related commands
Command
Function
ADD VIGCAP
To add VIG gateway capabilities
RMV VIGCAP
To remove VIG gateway capabilities
MOD VIGCAP
To modify VIG gateway capabilities
LST VIGCAP
To list VIG gateway capabilities

None.

It specifies the module number of the FCCU/FCSU processing various audio and video
call control messages of a VIG. It must be defined in the ADD BRD first and then
referenced here.
The FCCU/FCSU module number defined here must be the same as that defined in the
command ADD MGW; otherwise, VIG cannot interconnect with the SoftX3000
sucessfully.
[MGW capability]
It specifies the capabilities of a VIG for processing audio, video, and multiplexing media
streams. In normal cases, set five gateway capabilities for VIG: audio, H.263 video,
MPEG4 video, H.223 bearer, and H.223 multiplex.

5-30

[Equipment ID]
It identifies the VIG (UMG8900) that provides audio, H.263 video, MPEG4 video, H.223
bearer, and H.223 multiplex capabilities. It must be defined in the ADD MGW first and
then referenced here.
[Encode delay]
It defines the delay generated when VIG encodes the audio streams. It is valid only
when the gateway capabilities include audio, H.263 video, or MPEG4 video. Its value
ranges from 0 to 120 in unit of millisecond. It is 0 by default.
This parameter is used for the lip synchronization between a calling terminal and a
called terminal and is used when VIG sends the H.223 Skew Indication message.
[Picture format]
It is valid only when the VIG capability is H.263 video, defining the H.263 video codec
resolution of VIG. It is QCIF by default. The resolutions of different formats are as
follows:
SQCIF: 128 x 96 (pixels)
QCIF: 176 x 144 (pixels)
CIF: 352 x 288 (pixels)
[Minimum picture interval]
It is valid only when the VIG capability is H.263 video, defining the refresh frequency of
the H.263 video codec of VIG. Its value ranges from 1 to 32 in unit of 1/30 seconds. It is
2 by default.
The refresh frequency equals to 30/minnum picture interval. For example, if the
minimum picture interval is 2, the refresh frequency is 15 pictures per second.
[Maximum bit rate]
It is valid only when the VIG capability is H.263 video or MPEG4 video, defining the
maximum bit rate that can be received or sent by the video codec of VIG. Its value
ranges from 1 to 192400 in unit of 100 bit/s. It is 640 by default, indicating that the
maximum bit rate is 64 kbit/s.
[Unrestricted vector capability]
It is valid only when the VIG capability is H.263 video, indicating whether the H.263
video codec of VIG supports the unrestricted vector capability defined in Annex D of the
H.263 protocol. By default, the unrestricted vector capability is not supported.
[Arithmetic coding flag]
video codec of VIG supports the arithmetic coding capability defined in Annex E of the
H.263 protocol. By default, the arithmetic coding capability is not supported.
[Advance prediction flag]

5-31

video codec of VIG supports the advance prediction capability defined in Annex F of the
H.263 protocol. By default, the advance prediction capability is not supported.
[PB frames flag]
video codec of VIG supports the PB frame sending capability defined in Annex G of the
H.263 protocol. By default, the PB frame sending capability is not supported.
[HRD parameter B/H.263]
It is valid only when the VIG capability is H.263 video. When the H.263 video codec of
VIG supports the HRD capability defined in Annex B of the H.263 protocol, this
parameter is used to define the maximum number of bits of all signals (that is, the size
of the whole buffer) that are received and can be processed by the H.263 video codec
of VIG. Its value ranges from 0 to 524287 in unit of 128bit. It is 0 by default.
[Maximum number of bits]
It is valid only when the VIG capability is H.263 video. When the H.263 video codec of
VIG supports the HRD capability defined in Annex B of the H.263 protocol, this
parameter is used to define the maximum number of bits of one picture (that is, the size
of the picture buffer) that are received and can be processed by the H.263 video codec
of VIG. Its value ranges from 0 to 65535 in unit of 1024bit. It is 0 by default.
[Audio codec]
It is valid only when the VIG capability is audio, indicating the audio codecs that VIG
can support. Generally, VIG must support G.711A 64 kbit/s, G.711 64 kbit/s, G.723.1,
G.729A, and AMR for audio interworking.
[Pack time]
It is valid only when the VIG capability is audio, indicating the packaging delay of the
audio codec of VIG. Its value ranges from 0 to 255 in unit of millisecond. If this
parameter is necessary, it is recommended to set it to 10, 20, 30, 40, 60, or 90.
[Profile combination]
It is valid only when the VIG capability is MPEG4 video, defining the capability of the
MPEG4 video codec of VIG for processing specific profile related to the ISO/IEC
14496-2 standards. Its value ranges from 0 to 255. It is 8 by default.
[Set of tools]
It is valid only when the VIG capability is MPEG4 video, defining the set of tools used by
the MPEG4 video codec of VIG for decoding the received video media streams
contained in the logical channel ISO/IEC 14496-2. Its value ranges from 0 to 255. It is 0
by default.
[Decoder configuration]

5-32

It is valid only when the VIG capability is MPEG4 video, indicating how VIG configures
the MPEG4 video codec for the video media streams contained in the logical channel
ISO/IEC 14496-2. It is a string of a maximum of 64 characters.
[Drawing order]
It is valid only when the VIG capability is MPEG4 video, indicating how VIG defines the
drawing order for the video media streams contained in the logical channel ISO/IEC
14496-2. Its value ranges from 0 to 65535. The default value is 32768.
[Backward channel messages]
It is valid only when the VIG capability is MPEG4 video, indicating whether the MPEG4
video codec of VIG supports the transmission and reception of backward channel
messages. By default, it is set to False.
[Transport with I-Frame]
It is valid only when the VIG capability is H.223 bearer, indicating whether the H.223
multiplexer of VIG uses LAPM-I frames to send and receive the control channel
messages. By default, it is set to False.
[Video capability using AL1]
multiplexer of VIG uses the specified adaptation layer AL1 to send and receive the
video media streams of the specific type. By default, it is set to False.
[Audio capability using AL1]
audio media streams of the specific type. By default, it is set to False.
audio media streams of the specific type. By default, it is set to True.

5-33

audio media streams of the specific type. By default, it is set to False.
[Data capability using AL1]
multiplexer of VIG uses the specified adaptation layer AL1 to send and receive the data
media streams of the specific type. By default, it is set to True.
media streams of the specific type. By default, it is set to False.
media streams of the specific type. By default, it is set to False.
[Maximum number of octets AL2]
It is valid only when the VIG capability is H.223 bearer, defining the maximum number
of octets in a single service data unit (SDU) when the H.223 multiplexer of VIG sends or
receives media streams using the adaptation layer AL2. Its value ranges from 0 to
65535. The default value is 255.
[Maximum number of octets AL3]
of octets in a single service data unit (SDU) when the H.223 multiplexer of VIG sends or
receives media streams using the adaptation layer AL3. Its value ranges from 0 to
65535. The default value is 4096.
[Maximum multiplexing jitter]
It is valid only when the VIG capability is H.223 bearer, defining the maximum delay
allowed for the H.223 multiplexer of VIG to send audio streams. Its value ranges from 0
to 1023 in unit of millisecond. The default value is 30.
[H223 skew]
It is valid only when the VIG capability is H.223 bearer, defining the fixed time deviation
when the H.223 multiplexer of VIG processes audio media streams and when it
processes video media streams. Less deviation indicates the better synchronization of
audio and video. Its value ranges from 0 to 20 in unit of millisecond. The default value is
0.
This parameter is used for lip synchronization between a calling terminal and a called
terminal. It is used when VIG sends the H.223 Skew Indication message.
[Maximum MuxPDU size capability]

5-34

multiplexer of VIG is able to transmit the MuxPDU of the maximum size. By default, it is
set to True.
[NSRP support]
multiplexer of VIG supports the NSRP mode defined in Annex A of the H.324 protocol.
By default, it is set to True.
[Mode change capability]
multiplexer of VIG can change the multiplexing level dynamically after a call is
established. By default, it is set to False. There are three multiplexing levels defined in
the H.223 protocol: Level1, Level2, and Level3.
[H223 AnnexA]
multiplexer of VIG is able to transmit the MuxPDU defined in Annex A of the H.223
protocol. By default, it is set to True.
[H223 AnnexA double flag]
multiplexer of VIG supports the double-frame MuxPDU defined in Annex A of the H.223
protocol. By default, it is set to True.
[H223 AnnexB]
multiplexer of VIG can transmit the MuxPDU defined in Annex B of the H.223 protocol.
By default, it is set to True.
[H223 AnnexB with header]
multiplexer of VIG supports the MuxPDU with control header filed defined in Annex B of
the H.223 protocol. By default, it is set to False.
[AL1 option]
multiplexer of VIG supports the segmented AL1 data frame. The default value is AL1
framed, meaning supported.
[AL2 option]
multiplexer of VIG supports the AL2 data frame with sequence number. The default
value is AL2 with SEQ, meaning supported.
[AL3 control field octets]

5-35

It is valid only when the VIG capability is H.223 bearer, defining the number of octets of
the AL3 control field received or sent by the H.223 multiplexer of VIG. Its value ranges
from 0 to 2. It is 2 by default.
[AL3 send buffer size]
It is valid only when the VIG capability is H.223 bearer, defining the size of the buffer
used when the H.223 multiplexer of VIG sends the PDUs of AL3. Its value ranges from
0 to 166777215 in unit of byte. The default value is 4096.
[Maximum H223MuxPDU size]
of bytes of MuxPDU that can be received by the H.223 multiplexer of VIG. Its value
ranges from 0 to 65535 in unit of byte. The default value is 256.
[H223 rate]
It is valid only when the VIG capability is H.223 bearer. When a multimedia terminal
subscriber in the fixed network places a call to a multimedia terminal subscriber in the
3G network, this parameter defines the communication rate between the calling
terminal and the called terminal after the calling terminal is multiplexed by the H.223
multiplexer of VIG. That is, the multiplexed media stream is a single-bit stream that can
be transmitted through ISUP trunk, and H223 bit rate refers to the rate of the single-bit
stream.
Its value is an integer in unit of kbit/s, ranging from 32 to 64. It is not set generally. The
default value is 64 kbit/s. If it is necessary, set it to 32, 56, or 64.
[Multiplex table entry number]
It is valid only when the VIG capability is H.223 multiplex, defining the multiplex table
entries for the H.223 multiplexer of VIG. Its value ranges from 1 to 15. Set the
Multiplex table entry 0 is used by the control channel fixedly. You cannot configure
it.
You need to configure two other multiplex table entries at least. The logical
channel corresponding to one multiplex table entry is used to transmit audio media
streams, and the logical channel corresponding to the other is used to transmit
video media streams.
[Logical channel 1]
It is valid only when the VIG capability is H.223 multiplex, indicating whether the logical
channel 1 of the H.223 multiplexer of VIG is used to send audio or video media
streams.
[Repeat count 1]
channel 1 (corresponding to multiplex table entry 1) of the H.223 multiplexer of VIG

5-36

transmits media streams in segments. Its value ranges from 0 to 65535 in unit of byte.
The default value is 0. Set the parameter by the following principles:
If it is set to 0, it indicates that the logical channel 1 does not transmit media
streams in segments; instead, it ends a transmission when receiving the
untilClosingFlag message.
If it is set to n (1n65535), it indicates that the logical channel 1 transmits media
streams in segments. n refers to the number of bytes transmitted in one
transmission process.
[Repeat count 2]
channel 1 (corresponding to multiplex table entry 2) of the H.223 multiplexer of VIG
transmits media streams in segments. Its value ranges from 0 to 65535 in unit of byte.
If it is set to 0, it indicates that the logical channel 1 does not transmit media
streams in segments; instead, it ends a transmission when receiving the
untilClosingFlag message.
If it is set to n (1n65535), it indicates that the logical channel 1 transmits media
streams in segments. n refers to the number of bytes transmitted in one
transmission process.

5-37

Chapter 6 Configuring MRS Data

6.1.1 MRS
Media Resource Server (MRS) is a special kind of media gateway device adopting
MGCP or H.248 protocol. It is used to provide the media processing functions for the
basic services and value added services, including service tone provision, conference
resource provision, Interactive Voice Response (IVR), announcement and advanced
voice services.
Under the control of various service logics in the SoftX3000, the MRS can provide
powerful supports to the media resources sharing for the supplementary services and
intelligent services. Figure 6-1 shows the MRS implementation in the Next Generation
Network (NGN).
Service
Management
iOSS
Policy
Server
Network Control
Location
Server
SoftSwitch
MRS
SCP
SoftSwitch
Packet core Network
Core SoftSwich
Edge Access
Application
Server
IAD
AMG
BroadBand
Access
SG
TMG
UMG
PSTN
UMG
PLMN/3G
Figure 6-1 MRS implementation in the NGN

The MRS supports playing tones and announcements as well as the extended
functions specified in RFC2705. For example, the MRS can play a series of
announcements, timing silence and repeated tone or announcement, as well as
announcement to the terminals attending a conference, set interval for repeated
playing and dynamically download latest announcements to the MRS.

6-1

6.1.2 MRS Networking Mode

Huawei U-SYS solution supports two kinds of MRS networking modes, namely MRS
embedded in the SoftX3000 and external MRS (MRS6000 and MRS6100).
I. MRS embedded in the SoftX3000

The MRS embedded in the SoftX3000 is implemented by the MRCA board and MRIA
board in pair configured in the frame of the SoftX3000 to carry out service tone playing,
conference resources provision, Dual Tone Multi-Frequency (DTMF) digit receiving,
and variable tone playing.
z
MRCA: MRCA is the media resource control board. As a front board, it is

responsible for storing service tones, providing DTMF resources, processing
media streams and assigning resources in cooperation with its sub-board MRP.
MRIA: MRIA is the media resource interface board. As a back board, it is

responsible for providing IP channel that bears MRS resources. That is, it provides
the FE port for the embedded MRS to connect with the IP packet network.
Each MRCA can be configured with two MRP sub-boards, and each MRIA can provide
two FE ports, each of which corresponds to one MRP sub-board.
In the SoftX3000, each pair of MRCA plus MRIA can be regarded as a small-sized
MRS with complete functions, which has their individual control agent and control
protocol. In the case of a single frame fully configured, they function as 12 MRSs
embedded in the SoftX3000 (which are controlled by the SoftX3000 software and work
in the load sharing mode). Figure 6-2 shows the configuration.
M M M M M M S
R R R R R R I
Back boards
I I I I I I U
A A A A A A I
0
M
R
Front boards
C
A
M
R
C
A
M
R
C
A
M
R
C
A
M
R
C
A
H
S
C
I
S
I
U
I
H M M M M M M
S R R R R R R
C I I I I I I
I A A A A A A
M S
R M
C U
A I
S
M
U
I
10 11 12
M
R
C
A
M
R
C
A
M
R
C
A
13 14
M
R
C
A
M
R
C
A
U
P
W
R
15 16
M
R
C
A
A
L
U
I
U
P
W
R
17 18 19 20
U
P
W
R
U
P
W
R
Figure 6-2 MRS embedded in the SoftX3000 (a single frame fully configured)
This kind of embedded MRS is flexible in configuration and low in networking cost.
Hence it is applicable to a small capacity of end office, for example, an office with less
than 100,000 equivalent subscribers.

6-2

II. External MRS (MRS6000)

The external MRS (MRS6000) is designed specially for the NGN. It features large
capacity and complete service categories, and is applicable to the offices with large
capacity (for example, an office with more than 100 thousand subscribers).
MRS6000, in the form of a frame, is composed of the SCC and the MPC. The SCC is
the system control card, responsible for implementing device management, data
management, and resources assignment. The MPC is the media resource processing
card, responsible for implementing service tone storage, DTMF resources assignment,
conference resources assignment and media stream processing.
In the case of full configuration, MRS6000 is configured with the boards as shown in
Figure 6-3.
S M M M M M M M M M M M M S
C P P P P P P P P P P P P C
C C C C C C C C C C C C C C
10 11 12
13
Figure 6-3 Board configuration of MRS6000 in full configuration
III. External MRS (MRS6100)

MRS6100, in the form of a frame, is composed of the MCCU, EAM, VPS, MSU and
other boards. The functions of the key boards are as follows:
z
The MCCU is the media call control unit, responsible for processing SIP and
MGCP and managing media resources. It provides IP interfaces for external
devices in cooperation with the BFII.
The EAM is the embedded administration module, completing management

functions under the control of the BAM software.
The VPS is the VXML paser server in charge of resolving VXML scripts.
The MSU is the media service unit, capable of storing service tones, providing
DTMF resources, and synthesizing and identifying voices.
In the case of full configuration, the boards in the MRS6100 are shown in Figure 6-4.

6-3

B
Back boards F
I
I
B
F
I
I
E
A
I
E
A
I
M
R
I
A
M
R
I
A
S
I
U
I
M
Front boards C
C
U
M
C
C
U
E
A
M
V
P
S
M
S
U
M
S
U
S
M
U
I
H
S
C
I
S
I
U
I
H
S
C
I
M
R
I
A
S
M
U
I
M
R
I
A
M
R
I
A
M
R
I
A
M
R
I
A
10 11 12
13
14
15 16
M
S
U
M
S
U
M
S
U
M
S
U
M
R
I
A
M
S
U
U
P
W
R
U
P
W
R
17 18
19 20
U
P
W
R
U
P
W
R
M A
S L
U U
I
Figure 6-4 Boards in the MRS6100 in the case of full configuration (typical
configuration)
6.1.3 MRS Voice Categories

The MRS is mainly applied to provide the voices required by the services to the
subscribers. Before configuring MRS data and intelligent tone data, you need to make a
basic concept about MRS voice categories.
I. Divided according to playing

z
Synchronous voice: the digital voice played by the MRS from its beginning every
time for each tone playing request. From the view of subscriber, the heard voice is
played from the beginning of the voice file. From the view of the MRS, the voice at
a moment is only for a single subscriber, instead of for multiple subscribers. The
intelligent service voice is one of the common synchronous voices.
Asynchronous voice: the digital voice played by the MRS unnecessarily from the
beginning of the voice file every time for each tone playing request. From the view
of subscriber, the heard voice may be played from the middle of the voice file and
repeatedly. From the view of the MRS, the voice at a moment can be played for a
number of subscribers (not limited). The supplementary service voice is one of the
common asynchronous voices.
II. Divided according to contents

z
Fixed voice: the digital voice with constant contents played every time. Most of the
supplementary service voices and intelligent service voices are fixed voices.
Variable voice: the digital voice with dynamically variable contents played every
time. It is composed of voice elements, such as phone number, integer, time, date,
week and price, by the internal syntax analysis program of the MRS in conformity
with a certain regulation, and its contents are variable and denote specific

6-4

meanings. The common variable voices include time notification announcement,

malicious call identification announcement, and balance announcement.
III. Divided according to services

z
Signal tones: the digital tones involved in the basic service, including dialing tone,
busy tone, ringback tone, howling tone, test tone and silence.
Basic voice: the digital voice shared by the intelligent services and supplementary
services, including such voice elements as numerals, time units and monetary unit.
These voice elements must be composed before being played.
Supplementary service voice: the digital voice (generally the asynchronous voice)
used by the supplementary services, such as supplementary service registration
announcement,
cancellation
announcement,
malicious
call
identification
announcement and wakeup announcement.

z
Intelligent service voice: the digital voice (generally the synchronous voice) used
by the intelligent services, for example, Welcome you to use IP card services,
press 1 for national part and Please enter your account number followed by the
pound key. The heard voice is played from the very beginning of the voice file.
The start time, end time, playing times and playing duration are controlled by the
intelligent services.
6.1.4 Voice File Description

I. Introduction
The MRS is mainly applied to provide the voices required by the services to the
subscribers. The voices have been recorded by the equipment manufacturer and
stored as digital voice files in a certain format. During the deployment, loading these
digital voice files to the MRS can enable the tone playing function.
According to the terms in the contract, Huawei Technologies provides the standard
English or Chinese digital voice files to the MRS embedded in the SoftX3000 or
MRS6000 or MRS6100 through U-SYS SoftX3000 Operation and Maintenance
Application Software CD Pack. However, because there are many different languages,
the voice files provided by Huawei Technologies may not meet the specific demands of
the operators. In this case, besides the English voice files, the voice files in local
language or dialect for the MRS must be recorded by the operators themselves. That is,
the operator must record the voice files in their own languages or dialects according to
the contents in the standard voice files, and load them to the MRS.
II. Directory structure

If you select the default directories or paths when installing the BAM software, the voice
files used by the MRS will be stored under the directory D:\Data\voice in the BAM hard
disk after the BAM software has been installed. See Table 6-1.

6-5

Table 6-1 Directory structure

File path
Description
To store the voice files required by the embedded
MRS in the SoftX3000 (all voice files)
D:\Data\voice
To store the voice files required by MRS6000 (signal

tones and supplementary tones)
D:\Data\voice\Fin\chi
To store the Chinese voice files required by MRS6000

(intelligent service tones).
D:\Data\voice\Fin\eng
To store the English voice files required by MRS6000

(intelligent service tones).
D:\Data\voice\varible\chi
To store the Chinese voice files required by MRS6000

(basic tones).
D:\Data\voice\varible\eng

(basic tones).
D:\Data\voice\RACF

(RACF service tones)
From the view of directory structure, the voice files required by the MRS embedded in
the SoftX3000 are all stored in the directory D:\Data\voice, while the voice files
required by MRS6000 are distributed in different directories.
The mrc all voice file script.txt file on the D:\Data\voice on the BAM hard disk provides
details about the various voice files required by the MRS embedded in the SoftX3000.
III. Major voice files

Table 6-2 shows the major voice files used by the MRS.
Table 6-2 Description of major voice files
File name format
Remark
Voice file with suffix as .chi
The Chinese voice file to be loaded to the MRS

embedded in the SoftX3000.
Voice file with suffix as .eng
The English voice file to be loaded to the MRS

Voice file with suffix as .may
The Malaysia voice file to be loaded to the MRS

Voice file with suffix as .wav
The voice file to be loaded to MRS6000.
From the view of suffix, all the voice files required by MRS6000 are suffixed with .wav,
while the voice files required by the MRS embedded in the SoftX3000 are suffixed with
the language abbreviations, such as .chi, .eng, and .may.

6-6

IV. Loading mode

Table 6-3 shows the modes for loading voice files to the MRS.
Table 6-3 Loading mode
MRS networking mode
MRS embedded
SoftX3000
in
the
Loading mode
Loaded by the ADD MRCV command from the
SoftX3000 maintenance console
External MRS (MRS6000)
Loaded through Web management interface of

MRS6000 or loaded in batch with software tools
External MRS (MRS6100)
Loaded through the client of MRS6100
6.2 Configuring Embedded MRS Data

6.2.1 Overview
The complete data of the embedded MRS is composed of two parts, the data at the
embedded MRS side and that at the SoftX3000 side. The data at the embedded MRS
side is used to define board information, bearer IP interface, and MGC parameters of
the embedded MRS, and the data at the SoftX3000 side is used to define the mapping
relationship between tone IDs and voice files.
This section introduces you to the configuration of the equipment data, MGC data, and
MRS resource data related to the embedded MRS. The MRS resource data
configuration must not be conducted before the equipment data or media gateway data
is configured. See Figure 6-5.

6-7

Start
Equipment data
Trunk data
Office data
Number analysis
Charging data
Subscriber data
MG data
Centrex data
MRS data
Call barring data
Protocol data
IN service data
Signaling data
Other service data
Routing data
Other application
data
End

During the configuration, some parameters defined in the media gateway data will be
referenced in the MRS data. The broken lines in Figure 6-5 show the referencing
Table 6-4 Parameter referencing relationships between MRS data and other data
Input parameter
Output parameter
Name
Defined in
Equipment ID of the MRS
Media gateway data
Name
/
Referenced in
/
II. Preparations
Before configuring the media gateway data, make sure that all preparations are done
as specified in Table 6-5.
SN
1
Item
Remark
Domain names of MRCA

boards
For interworking with the embedded MRS

6-8

SN
Item
Remark
IP addresses
sub-boards
of
MRP
Used to define the IP address of the service

bearer channel of the embedded MRS
Local UDP port number at

the MGC side
Local UDP port number at

the MG side
Coding/decoding modes of
MRP sub-boards
Digital voice files recorded
Used to load voice files to the embedded MRS

Table 6-6 shows the general steps for configuring the embedded MRS data. Steps 1 to
3 are to configure the data at the embedded MRS side. Step 4 is to load voice files to
the embedded MRS. Step 5 is to configure the data at the SoftX3000 side.
Step
Description
Command
Add MRCA board
ADD BRD
Add MRC configuration
ADD MRCCFG
Add MRP configuration
ADD MRPCFG
Add MRC voice file
ADD MRCV
Add mapping between tone ID and tone file (optional)
ADD TONEID
Add tone ID configuration (optional)
ADD TONECFG
Add language zone (optional)
ADD LZONE
Add mapping relation between release cause value and

tone ID (optional)
ADD CVTOTID

the embedded MRS data is configured.

6-9

ADD BRD
ADD MRCCFG
[Frame number]
[MRC module number]
[Slot number]
[Default language]
[Module number]
[MRC domain name]

[MGC IPv4 address]
ADD MRPCFG
[MRC module number]
[MRP board]
[MRP IP address]
ADD TONEID
[Equipment ID]
[Tone ID]
[File name]
6.2.2 Adding MRCA Board

I. Related commands
Command
Function
ADD BRD
To add board
RMV BRD
To remove board
LST BRD
To list the configured parameters of board

z
When you add the MRCA board with the command ADD BRD, its back board
MRIA will be added automatically, and you need not add it again.
The MRCA board runs independently, so the Assistant slot number in the ADD
BRD command must be set to 255.

For detailed information, refer to Chapter 2, Configuring Equipment Information, in
this manual.

6-10

6.2.3 Adding MRC Configuration

I. Related commands
Command
Function
ADD MRCCFG
To add MRC board configuration
RMV MRCCFG
To remove MRC board configuration
MOD MRCCFG
To modify MRC board configuration
LST MRCCFG
To list MRC board configuration

[MRCA module number]
It is used to specify the module number of the MRCA board to be configured. This
parameter must be defined by the ADD BRD command before being referenced here.
[Default language]
It is used to specify the default language of the voice files. If the SoftX3000 sends tone
playing command to the MRCA board without specifying the language, the MRCA will
play voice files in the default language.
[MGC port]
One of the parameters used for interworking with the embedded MRS. It is used to
specify the number of the UDP port used by the SoftX3000 to communicate with the
MRS, that is, the number of the local UDP port at the MGC side. Because the
embedded MRS adopts MGCP, the port number at the MGC side is 2727.
[MRC port]
specify the number of the UDP port used by the MRS to communicate with the
SoftX3000, that is, the number of the local UDP port at the MG side. Because the
embedded MRS adopts MGCP, the port number at the MRC side is 2427.
[MRC domain name]
define the domain name of the embedded MRS in MGCP.
[MGC IPv4 address]
specify the IP address of the FE port at the SoftX3000 side that processes all protocol
messages of the embedded MRS. This parameter must be defined by the ADD FECFG

6-11

This parameter specifies the module number of the FCCU or FCSU at the SoftX3000
side, which is responsible for processing the call control messages of the embedded
MRS. The value range is from 22 to 101. This parameter is defined in the ADD BRD
[TDM TID layer index]
This parameter specifies the TDM termination identification corresponding to the
embedded MRS (that is, digital voice channel). Its default value is 3, indicating the TDM
termination identification (that is, Interface name) is ms/cnf/ by default. The interface
name is one of the interconnection parameters between the embedded MRS and the
SoftX3000 and its corresponding parameter of TID layer index is first defined with the
command ADD TIDLAY before being referenced here.
[Resource capability]
This parameter specifies the capability of an interface of the embedded MRS, that is, to
define the resource devices supported on the interface.
z
Tone: basic tone and ordinary service voice.
Play Tone: Variable tones and intelligent service voice.
Send DTMF: Sending DTMF signal tone.
Detect DTMF: Detecting DTMF signal tone (equivalent to DTMF digit receiving
resources)
Multiparty: Multi-party conversation.
[Codec list]
This is one of the interconnection parameters between the embedded MRS and the
SoftX3000. This parameter specifies the codecs supported by the embedded MRS.
Currently, the choices include PCMA, PCM, G.723.1, G.729.A, G.726 and T.38.
6.2.4 Adding MRP Configuration

I. Related commands
Command
Function
ADD MRPCFG
To add MRP configuration
RMV MRPCFG
To remove MRP configuration
MOD MRPCFG
To modify MRP configuration
LST MRPCFG
To list MRP configuration

[MRCA module number]
It is used to specify the module number of the MRCA board where the MRP sub-board
is located. It must be defined by the ADD BRD command before being referenced here.
6-12

[MRP board location]

It is used to specify the location of the MRP sub-board to be configured on the MRCA
board, including Lower MRPA and Upper MRPA.
[MRP IP address], [MRP IP mask]
They are used to define the IP address of the FE port bearing the MRS resources (such
as service tones) of the MRP sub-board. The FE port is provided by the back board
MRIA. The mask is in dotted decimal notation, for example, 255.255.255.0.
[MRP default router address]
It is used to specify the IP address of the router to which the FE port of the MRP
sub-board is connected. This parameter must be configured correctly; otherwise, the
embedded MRS cannot provide MRS resources to the network.
[PF enable flag]
It is used to determine whether to enable the G.723.1 base tone post-filter on the MRP
sub-board. By default, it is set to True.
[HPF enable flag]
It is used to determine whether to enable the G.723.1 high-pass filter on the MRP
sub-board. By default, it is set to True.
[VAD enable flag]
It is used to determine whether to enable the Voice Activity Detection (VAD) function on
the MRP sub-board. By default, it is set to True.
[EC enable flag]
Reserved.
[CNG enable flag]
It is used to determine whether to enable the Comfortable Noise Generation (CNG)
function on the MRP sub-board. By default, it is set to True.
[EC tail length]
It is used to specify the delay of the echo that the MRP can eliminate. ECT16 indicates
that the echo less than or equal to 16 ms delay can be eliminated, and ECT32
indicates that the echo less than or equal to 32 ms delay can be eliminated. The other
options follow this principle.
[Hybrid loss]
It is used to indicate the attenuation value of the EC signals. Its value ranges from 0 to
255 in unit of dB. It is 6 by default.
[Play announcement volume]
It is used to adjust the volume of the service tones. Its value ranges from 0 to 62 in unit
of dB. It is 0 by default.
[Input gain]
6-13

It is used to adjust the volume of the input voices. Its value ranges from 0 to 62 in unit of
dB. It is 0 by default.
[Jitter buffer enable flag]
It is used to indicate whether to enable the jitter buffer on the MRP sub-board. It is set to
False by default. At present, most media gateways do not support the Jitter buffer
field contained in MGCP or H.248 messages, so the jitter buffer is not enabled
generally.
[Jitter buffer mode], [Jitter buffer optimization factor]
Reserved.
[Jitter buffer length]
It is used to define the length of the jitter buffer. Its value ranges from 5 to 200 in unit of
millisecond. The default value is 5.
[Channel mode]
It is used to define the transmission mode that the MRP sub-board employs. The
default value is Mode inactive, indicating that no transmission mode is defined. If the
MGC (SoftX3000) does not specify the transmission mode of media streams in the
CRCX message sent to the MRP sub-board, the MRP will use the mode defined here.
[Coder]
It is used to define the coding method that the MRP sub-board employs. The default
value is G.729A. If the MGC (SoftX3000) does not specify the media stream coder in
the CRCX message sent to the MRP sub-board, the MRP will use the coder defined
here.
[Decoder]
It is used to define the decoding method that the MRP sub-board employs. The default
value is G.729A. If the MGC (SoftX3000) does not specify the media stream decoder
in the CRCX message sent to the MRP sub-board, the MRP will use the coder defined
here.
[Coder packet length]
It is used to specify the time segment in which the coder of the MRP sub-board
fragments and assembles the media streams, with the unit of millisecond. The default
value is 10.
[Decoder packet length]
It is used to specify the time segment in which the decoder of the MRP sub-board
fragments and disassembles the media streams, with the unit of millisecond. The
default value is 10.
[CPU threshold]
It is used to specify the alarm threshold when the CPU of the MRP sub-board is
overloaded. The unit is % and the system default value is 80.
6-14

[First UDP port], [UDP port number]

They are used to specify the number and the range of the UDP ports available for the
Real-time Transport Protocol (RTP) media streams. By default, the first UDP port
number is 10000, and the quantity of ports is 240. That is, the range of the UDP ports
available for the RTP media streams is 10000 to 100239.
6.2.5 Adding MRC Voice File

I. Related commands
Command
Function
ADD MRCV
To add MRC voice file
RMV MRCV
To remove MRC voice file
MOD MRCV
To modify the configuration information of MRC voice file
LST MRCV
To list the configuration information of MRC voice file

z
The ADD MRCV command is used to define the voice files to be stored in the
memory of each MRCA. That is, when an MRCA restarts, the system
automatically loads the corresponding voice files from the BAM to the memory of
the MRCA based on the setting of this command.
When you use the ADD MRCV command to add MRC voice files, because there
are hundreds of voice files to be added, there may be hundreds of script
configuration files that you should compile with the ADD MRCV command. To
prevent error and save time, the SoftX3000 has configured the corresponding
script configuration files in the directory D:\Data\voice in the BAM hard disk
automatically, as shown in Figure 6-7.
Figure 6-7 Preset script configuration files

You can directly use these script files to conduct data configuration. If you need to add
all voice files to the embedded MRS, use the file mrc all voice file script.txt.

6-15


[Voice file name]
It is used to specify the name of the voice file to be loaded to the MRCA memory. The
voice files are stored in the directory D:\Data\voice in the BAM hard disk.
[Upload to MRP flag]
It is used to indicate whether each MRCA loads the voice file that has been loaded to its
memory to the Flash of the MRP sub-board again. It is set to False by default.
Because the MRP sub-board reads the voice file from the Flash more quickly than from
the MRCA memory when it processes various announcement requests, you can set the
frequently used voice files to Upload. However, the Flash of the MRP sub-board has
limited memory, so you cannot set all voice files to Upload.
For replacement of the MRCA, the system automatically judges if the MRP sub-board
on the new MRCA stores the fixed voice files (in the Flash) when the new MRCA loads
voice files from the BAM. If so, the system cannot reload the voice files to the MRP
according to the current data configuration. In this case, if the fixed voice files in the
MRP are inconsistent with the data configuration, wrong announcements will be played.
To ensure correct announcement, you must update the voice files on the MRP with the
command UPD MRPAWF in time after the new MRCA runs normally.
[File description]
It is used to describe the meaning of the voice file.
6.2.6 Adding Mapping Relation between Tone ID and Voice File (Optional)
I. Related commands
Command
Function
ADD TONEID
To add mapping between tone ID and tone file
RMV TONEID
To remove mapping relation between tone ID and tone file
MOD TONEID
To modify mapping between tone ID and tone file
LST TONEID
To list mapping between tone ID and tone file

This configuration step is optional. Read the following before you use the command.
When you are adding an embedded MRS by using the ADD MRCCFG command, the
system automatically adds the mapping relation between some frequently used tone
IDs and tone files. You can view the details by using the LST TONEID command. That
mapping relation can meet most of requirements for basic announcements and
supplementary service announcements. If you still have other special requirements,

6-16

you can add the corresponding mapping relation between additional tone IDs and tone
files by using the ADD TONEID command.

[Equipment ID]
It is used to specify the equipment ID of the MRS to be configured. For an embedded
MRS, this parameter (domain name) is defined in the ADD MRCCFG command and
referenced here. For a physically separate MRS, this parameter is defined in the ADD
MGW command and referenced here.
[Tone ID]
It is used to specify the ID of a signal tone or voice defined in the SoftX3000 software.
The description in the bracket indicates the meaning of the tone ID, for example,
TID_0x0001~1 (Time announcement) and "TID_0x0004~4(Wakeup tone)". Refer to
Appendix B for details.
[File name]
It is used to specify the name of the MRS voice file corresponding to a tone ID at the
SoftX3000 side. It is an integer that can be directly converted from the hex in the tone
ID in normal cases. For example, if the tone ID is TID_0x0001, the voice file name is
1. If the tone ID is TID_0x0010, the voice file name is "16.
6.2.7 Adding Language Zone (Optional)

I. Related commands
Command
Function
ADD LZONE
To add language zone
RMV LZONE
To remove language zone
MOD LZONE
To modify language zone
LST LZONE
To list language zone

By default, when the SoftX3000 controls the MRS to play announcements to
subscribers subject to various MGs, the language, number of languages, and
sequence of announcements are fixed. For example, the MRS plays only Chinese
announcements, or Chinese announcements first and then the English ones. That is,
for all MGs and voice subscribers, the MRS uses the same language(s) for
announcements.

6-17

However, in some applications such as NGN networking over countries, subscribers in

different countries might require to hear announcements in different languages; or in a
local network, some enterprise subscribers (regional offices of an international
company) might require to hear announcements in different languages. To meet this
requirement, the SoftX3000 can play announcements in different languages to different
MGs or subscribers. In this case, you need to execute ADD LZONE to add language
zone data.

[Local DN set]
It defines the local DN set of the voice subscribers for whom language zone data is to
be set. It ranges from 0 to 65535. Set this parameter by the following principles:
z
65534 is a wildcard character, indicating that all voice subscribers subject to an

MG hear the announcements in the same language.
If you set it to other values (A, for example), it means that all voice subscribers
whose local DN set is A under an MG hear the announcements in the same
language.
[MGW index]
It defines the index of an MG in the database, under which the voice subscribers are
added with language zone data. Set this parameter by the following principles:
z
If no parameter is typed, it means that the voice subscribers under all MGs hear
the announcements in the same language.
If you want to sepcify a specific MG, first use LST MGW to query the index of the
MG by its equipment ID, and then type the index. Then all voice subscribers under
this MG will hear the announcements in the same language.
[Language index]
It defines the language and sequence of announcements contained in the control
message sent by the SoftX3000 to the MRS. The language and sequence in the control
message are defined in the command ADD LKNDIDX. That is, this parameter must be
defined in the command ADD LKNDIDX first before it can be referenced here.
6.2.8 Adding Tone ID Configuration (Optional)

I. Related commands
Command
Function
ADD TONECFG
To add tone ID configuration
RMV TONECFG
To remove tone ID configuration
MOD TONECFG
To modify tone ID configuration
LST TONECFG
To list tone ID configuration

6-18


This configuration step is optional. Read the following before you start:
By default, the SoftX3000 controls the MRS to play only one piece of announcement
that is recorded in one language or two languages at most to a terminal user for one
time. However, carriers may expect that an announcement can be played in multiple
languages. In this case, there are three options for them:
z
Record a piece of announcement in multiple languages, and then save it as a new

voice file with the same name as that of the original one. Finally, load the new
voice file to the MRS.

voice file with a different name from that of the original one. Next, load the new
voice file to the MRS. Finally, use the ADD TONECFG command to add tone ID
configuration.
Record several pieces of announcement in multiple languages, and then save

them as new voice files with different names. Next, load the voice files to the MRS.
Finally, use the command ADD TONECFG to add tone ID configuration.

[Internal tone ID]
It is used to define the internal tone ID used when the SoftX3000 controls the MRS to
play announcement. It is a decimal numeral. Set it by the following principles:
z
For the basic tone and supplementary service voice, you can set it with reference
to the parameter File name in the command ADD TONEID.
For the IN service voice, you can set it by converting the parameter recorded
notification ID in the IN recorded announcement message ID.
[Local DN set]
It defines the local DN set of the voice subscribers for whom language ID data is to be
set. It ranges from 0 to 65535. Set this parameter by the following principles:
z

MG hear the announcements (corresponding to internal tone IDs) in the same
language.
whose local DN set is A under an MG hear the announcements (corresponding to
internal tone IDs) in the same language.
[MGW index]
added with language ID data. Set this parameter by the following principles:
z
the announcements (corresponding to internal tone IDs) in the same language.

6-19

z
this MG will hear the announcements (corresponding to internal tone IDs) in the
same language.
[Cycle number]
It defines the times for which the SoftX3000 allows the MRS to play one piece of
announcement cyclically . It is 1 by default.
[Interval time]
It defines the interval for the cyclic playing of one piece of announcement by MRS. Its
value ranges from 1 to 1600 in unit of second. The default value is 10.
[Duration]
Reserved.
[External tone number]
It defines the number of the external voice files when it is necessary to split a voice file
into several external voice files to play. Its value ranges from 1 to 5. If it is set to 1, it
means no split.
[External tone ID 1][External tone ID 5]
They define the names of the external voice files when it is necessary to split a voice file
into several external voice files to play. They are integers. Refer to the parameter File
name in the command ADD TONEID for the value setting rule of this parameter.
When the system plays multiple external voice files in a combined way, the sequence of
them to be played is irrelevant to their tone IDs; instead, it is finaly defined in the
command ADD LKNDIDX.
6.2.9 Adding Mapping Relation between Release Cause Value and Tone ID
(Optional)
I. Related commands
Command
Function
ADD CVTOTID
To add mapping relation between tone ID and release cause

value
RMV CVTOTID
To remove mapping relation between tone ID and release cause

value
MOD CVTOTID
To modify mapping relation between tone ID and release cause

value
LST CVTOTID
To list mapping relation between tone ID and release cause value

6-20


When releasing calls, the call control software of the SoftX3000 automatically
generates the release cause value and release position no matter whether the calls
succeed or fail. By default, the SoftX3000 defines the mapping relation between each
combination of release cause value & release position and tone ID. That is, for each
pair of release cause value & release position, the SoftX3000 controls the MRS to play
one default announcement to the corresponding caller, prompting the current state of
the call.
In actual applications, carriers may expect to change the mapping relation between
some release cause values (or release positions) and tone IDs. For example, for a call
with the release cause value as ringed no answer, the system plays the busy tone to
the corresponding caller by default. To change the busy tone to the ringed no answer
announcement in this case, use the command ADD CVTOTID.

[Cause value]
It defines the specific cause for call release. It is one of the key factors that determine
whether the system plays announcement to a caller after a call is released. It
codetermines with the release position parameter in the ADD CVTOTID command
the announcement to be played to the caller.
This parameter needs to be matched precisely with the release cause value
automatically generated by the call control software of SofX3000. If you cannot judge
the actual release cause value for a certain type of calls accurately, you can obtain it
with such tracing tasks as interface signaling tracing or connection tracing.
[Position]
It defines the specific position where a call is released. It is one of the key factors that
determine whether the system plays announcement to a caller after a call is released. It
codetermines with the cause value parameter in the ADD CVTOTID command the
announcement to be played to the caller.
This parameter is only an internal parameter for judgement, with no special meaning.
Generally, set it to 65534 (wildcard character), indicating any release position. To set it
to other values for special applications, contact Huawei technical support personnel for
help.
[Tone ID]
It specifies the ID of a signal tone or supplementary service voice defined in the
SoftX3000 software. It corresponds to the combination of cause value & position,
defining the announcement to be played by MRS to a caller. The description in the
bracket indicates the meaning of a tone ID, for example, TID_0x0001~1 (Time
announcement) and "TID_0x0004~4(Wakeup tone)". Refer to Appendix B for details.
6-21

6.3 Configuring External MRS Data

6.3.1 Overview
The external MRS data is used to define the MRS routes and tone ID mapping. To
configure the external MRS data, make sure that the equipment data and MG data has
been configured. The sequence is shown in Figure 6-8.
Start
Equipment data
Trunk data
Office data
Number analysis
Charging data
Subscriber data
MG data
Centrex data
MRS data
Call barring data
Protocol data
IN service data
Signaling data
Other service data
Routing data
Other application
data
End

During the configuration, some parameters defined in the MG data will be referenced in
the MRS data. The broken lines in Figure 6-8 show the referencing relationships and
Table 6-7 shows the details.
Table 6-7 Parameter referencing relationships between MRS data and other data
Input parameter
Output parameter
Name
Defined in
Equipment ID of the MRS
Media gateway data

6-22
Name
/
Referenced in
/

II. Preparations
Before configuring the external MRS data, make sure that all preparations are done as
SN
Item
Remark
IP address of external MRS
For interworking with external MRS
Domain name of external MRS
Local UDP port number at the MGC

side
Local UDP port number at the MG side
Interface name of external MRS
Coding/decoding mode of external

MRS
Internal IP addresses of MPCs in

MRS6000
For interworking with MRS6000
Digital voice files recorded
Used to load voice files to external

MRS

Table 6-9 shows the general steps for configuring the external MRS data.
Step
Description
Command
Add MRS gateway
ADD MGW
Add MRS route (only for MRS6000)
ADD MRSRT
Add mapping relation between tone ID and voice file

(optional)
ADD TONEID
Add language zone (optional)
ADD LZONE
Add tone ID configuration (optional)
ADD TONECFG
Add mapping between cause value and tone ID

(optional)
ADD CVTOTID

the external MRS data is configured.

6-23

ADD MGW
ADD TONEID
[Equipment ID]
[Equipment ID]
[Gateway type]
[Tone ID]
[MGW descriptiont]
[File name]
[Control MID]
6.3.2 Adding MRS Gateway

I. Related commands
Command
Function
ADD MGW
To add voice media gateway
RMV MGW
To remove voice media gateway
MOD MGW
To modify the configuration information of voice media gateway
LST MGW
To list the configuration information of voice media gateway

The SoftX3000 regards the MRS as a voice media gateway, so addition of an MRS
gateway is actually that of a voice media gateway. When using the ADD MGW
command to add MRS gateway, pay attention to the following points:
z
The Equipment ID in the command must be consistent with the domain name of
the external MRS.
The Gateway type in the command must be MRS.
The Protocol type in the command must be MGCP.
The Interface name1 in the command must be ms/cnf.
The Local IP address in the command is the external IP address of the

corresponding IFMI (defined by the ADD FECFG command).
If the external MRS is MRS6100, because the entire MRS6100 functions as an

independent MRS, the Remote IP address 1 in the command is the IP address of
the MCCU board in the MRS6100.
If the external MRS is MRS6000, because each MPC in the frame serves as an
independent MRS, the Remote IP address 1 in the command is the internal IP
address of each MPC in the MRS6000.
The Remote port in the command is generally 2427 (which needs negotiation).
The Code list in the command must be G.711 A, G.711 , G723.1 G729 A.

For detailed information, refer to Chapter 5, Configuring MG Data, in this manual.
6-24

6.3.3 Adding MRS Route (Only for MRS6000)

I. Related commands
Command
Function
ADD MRSRT
To add MRS route
RMV MRSRT
To remove MRS route
LST MRSRT
To list the configuration information of MRS route

Although each MPC in the MRS6000 serves as an independent MRS, the control
information sent by the MGC to each MPC must be transferred by the SPC. That is, the
communication path is MGC external bearer IP network SCC Ethernet in frame
MPC. In this case, the SPC is equivalent to a gateway for IP communication
between the external MGC and the internal MPCs.
Therefore, to achieve the IP communication between the SoftX3000 and the MPCs in
the MRS6000, you must add the MRS route with the command ADD MRSRT.

[Destination IP address]
One of the parameters used for interworking with MRS6000. It is used to specify the
internal IP address of each MPC in MRS6000.
[Gateway IP address]
One of the parameters used for interworking with MRS6000. It is used to specify the
external IP address of the SCC in MRS6000.
6.3.4 Adding Mapping between Tone ID and Tone File (Optional)

I. Related commands
Command
Function
ADD TONEID
To add mapping between tone ID and tone file
RMV TONEID
To remove mapping between tone ID and tone file
MOD TONEID
To modify mapping between tone ID and tone file
LST TONEID
To list mapping between tone ID and tone file

This configuration step is optional. Read the following before you start.
6-25

When you are adding an embedded MRS by using the ADD MRCCFG command, the
system automatically adds the mapping relation between some frequently used tone
IDs and tone files. You can view the details by using the LST TONEID command. That
mapping relation can meet most of requirements for basic announcements and
supplementary service announcements. If you still have other special requirements,
you can add the corresponding mapping relation between additional tone IDs and tone
files by using the ADD TONEID command.

[Equipment ID]
It is used to specify the equipment ID of the MRS to be configured. For an embedded
MRS, this parameter (domain name) is defined in the ADD MRCCFG command and
referenced here. For a physically separate MRS, this parameter is defined in the ADD
MGW command and referenced here.
[Tone ID]
It is used to specify the ID of a signal tone or voice defined in the SoftX3000 software.
The description in the bracket indicates the meaning of the tone ID, for example,
TID_0x0001~1 (Time announcement) and "TID_0x0004~4(Wakeup tone)". Refer to
Appendix B for details.
[File name]
It is used to specify the name of the MRS tone file corresponding to a tone ID at the
SoftX3000 side. It is an integer that can be directly converted from the hex in the tone
ID in normal cases. For example, if the tone ID is TID_0x0001, the tone file name is
1. If the tone ID is TID_0x0010, the tone file name is "16.
6.3.5 Adding Language Zone (Optional)

I. Related commands
Command
Function
ADD LZONE
To add language zone
RMV LZONE
To remove language zone
MOD LZONE
To modify language zone
LST LZONE
To list language zone

By default, when the SoftX3000 controls the MRS to play announcements to
subscribers subject to various MGs, the language, number of languages, and
6-26

sequence of announcements are fixed. For example, the MRS plays only Chinese
announcements, or Chinese announcements first and then the English ones. That is,
for all MGs and voice subscribers, the MRS uses the same language(s) for
announcements.
However, in some applications such as NGN networking over countries, subscribers in
different countries might require to hear announcements in different languages; or in a
local network, some enterprise subscribers (regional offices of an international
company) might require to hear announcements in different languages. To meet this
requirement, the SoftX3000 can play announcements in different languages to different
MGs or subscribers. In this case, you need to execute ADD LZONE to add language
zone data.

[Local DN set]
It defines the local DN set of the voice subscribers for whom language zone data is to
be set. It ranges from 0 to 65535. Set this parameter by the following principles:
z

MG hear the announcements in the same language.
whose local DN set is A under an MG hear the announcements in the same
language.
[MGW index]
added with language zone data. Set this parameter by the following principles:
z
the announcements in the same language.
this MG will hear the announcements in the same language.
[Language index]
It defines the language and sequence of announcements contained in the control
message sent by the SoftX3000 to the MRS. The language and sequence in the control
message are defined in the command ADD LKNDIDX. That is, this parameter must be
defined in the command ADD LKNDIDX first before it can be referenced here.
6.3.6 Adding Tone ID Configuration (Optional)

I. Related commands
Command
ADD TONECFG
Function
To add tone ID configuration

6-27

Command
Function
RMV TONECFG
To remove tone ID configuration
MOD TONECFG
To modify tone ID configuration
LST TONECFG
To list tone ID configuration

By default, the SoftX3000 controls the MRS to play only one piece of announcement
that is recorded in one language or two languages at most to a terminal user for one
time. However, carriers may expect that an announcement can be played in multiple
languages. In this case, there are three options for them:
z

tone file with the same name as that of the original one. Finally, load the new tone
file to the MRS.

tone file with a different name from that of the original one. Next, load the new tone
file to the MRS. Finally, use the ADD TONECFG command to add tone ID
configuration.
Record several pieces of announcement in multiple languages, and then save

them as new tone files with different names. Next, load the tone files to the MRS.
Finally, use the command ADD TONECFG to add tone ID configuration.

[Internal tone ID]
It is used to define the internal tone ID used when the SoftX3000 controls the MRS to
play announcement. It is a decimal numeral. Set it by the following principles:
z
For the basic tone and supplementary service voice, you can set it with reference
to the parameter File name in the command ADD TONEID.
For the IN service voice, you can set it by converting the parameter recorded
notification ID in the IN recorded announcement message ID.
[Local DN set]
It defines the local DN set of the voice subscribers for whom language ID data is to be
set. It ranges from 0 to 65535. Set this parameter by the following principles:
z

MG hear the announcements (corresponding to internal tone IDs) in the same
language.

6-28

z
whose local DN set is A under an MG hear the announcements (corresponding to
internal tone IDs) in the same language.
[MGW index]
added with language ID data. Set this parameter by the following principles:
z
the announcements (corresponding to internal tone IDs) in the same language.
this MG will hear the announcements (corresponding to internal tone IDs) in the
same language.
[Cycle number]
It defines the times for which the SoftX3000 allows the MRS to play one piece of
announcement cyclically . It is 1 by default.
[Interval time]
It defines the interval for the cyclic playing of one piece of announcement by MRS. Its
value ranges from 1 to 1600 in unit of second. The default value is 10.
[Duration]
Reserved.
[External tone number]
It defines the number of the external tone files when it is necessary to split a tone file
into several external tone files to play. Its value ranges from 1 to 5. If it is set to 1, it
means no split.
[External tone ID 1][External tone ID 5]
They define the names of the external tone files when it is necessary to split a tone file
into several external tone files to play. They are integers. Refer to the parameter File
name in the command ADD TONEID for the value setting rule of this parameter.
When the system plays multiple external voice files in a combined way, the sequence of
them to be played is irrelevant to their tone IDs; instead, it is finaly defined in the
command ADD LKNDIDX.
6.3.7 Adding Mapping between Cause Value and Tone ID (Optional)

I. Related commands
Command
Function
ADD CVTOTID
To add mapping between cause value and tone ID
RMV CVTOTID
To remove mapping between cause value and tone ID

6-29

Command
Function
MOD CVTOTID
To modify mapping between cause value and tone ID
LST CVTOTID
To list mapping between cause value and tone ID

When releasing calls, the call control software of the SoftX3000 automatically
generates the release cause value and release position no matter whether the calls
succeed or fail. By default, the SoftX3000 defines the mapping relation between each
combination of release cause value & release position and tone ID. That is, for each
pair of release cause value & release position, the SoftX3000 controls the MRS to play
one default announcement to the corresponding caller, prompting the current state of
the call.
In actual applications, carriers may expect to change the mapping relation between
some release cause values (or release positions) and tone IDs. For example, for a call
with the release cause value as ringed no answer, the system plays the busy tone to
the corresponding caller by default. To change the busy tone to the ringed no answer
announcement in this case, use the command ADD CVTOTID.

[Cause value]
It defines the specific cause for call release. It is one of the key factors that determine
whether the system plays announcement to a caller after a call is released. It
codetermines with the release position parameter in the ADD CVTOTID command
the announcement to be played to the caller.
This parameter needs to be matched precisely with the release cause value
automatically generated by the call control software of SofX3000. If you cannot judge
the actual release cause value for a certain type of calls accurately, you can obtain it
with such tracing tasks as interface signaling tracing or connection tracing.
[Position]
It defines the specific position where a call is released. It is one of the key factors that
determine whether the system plays announcement to a caller after a call is released. It
codetermines with the cause value parameter in the ADD CVTOTID command the
announcement to be played to the caller.
This parameter is only an internal parameter for judgement, with no special meaning.
Generally, set it to 65534 (wildcard character), indicating any release position. To set it
to other values for special applications, contact Huawei technical support personnel for
help.

6-30

[Tone ID]
It specifies the ID of a signal tone or supplementary service voice defined in the
SoftX3000 software. It corresponds to the combination of cause value & position,
defining the announcement to be played by MRS to a caller. The description in the
bracket indicates the meaning of a tone ID, for example, TID_0x0001~1 (Time
announcement) and "TID_0x0004~4(Wakeup tone)". Refer to Appendix B for details.

6-31

Chapter 7 Configuring Protocol Data

This chapter details how to configure protocol data, such as Session Initiation Protocol
(SIP), H.323, and Simple Traversal of UDP Through Network Address Translators
(STUN). Protocol data is preceded by the configuration of MRS resource data. See
Figure 7-1.
Start
Equipment data
Trunk data
Office data
Number analysis
Charging data
Subscriber data
MS data
Centrex data
MRS data
Call barring data
Protocol data
IN service data
Signaling data
Other service data
Routing data
Other application
data
End

7.1.1 SIP
I. Basic concepts
Put forward and studied by the IETF, the Session Initiation Protocol (SIP) is an
application-layer control protocol for multimedia communication over IP network, which
can be used for creating, modifying and terminating sessions with one or more
participants. These sessions include Internet multimedia conferences, Internet
telephone calls, distance learning, telemedicine, and similar applications.
Being an application-layer multimedia session protocol, SIP can be used to initiate
sessions as well as invite members to sessions that have been advertised and
7-1

established by other means. Sessions can be advertised using multicast protocols

such as Session Announcement Protocol (SAP), electronic mail, web pages or
Lightweight Directory Access Protocol (LDAP), among others. SIP transparently
supports name mapping and redirection services, allowing the implementation of ISDN
and IN telephony subscriber services. These facilities also enable personal mobility.
That is, the ability of end users to request and access subscribed telecommunication
services on any terminal in any location at any time. SIP supports five facets of
establishing and terminating multimedia communications:
z
User location: determination of the end system to be used for communication.
User capabilities: determination of the media and media parameters to be used.
User availability: determination of the willingness of the called party to engage in

communications.
Call setup: "ringing", establishment of call parameters at both called and calling
party.
Call handling and control: including redirection, transfer and termination of calls.
II. Well-known port and local port

In SIP, the Via field is defined to indicate the path for a request to pass through, It can
prevent the request from looping during the forwarding process and guarantee that the
response follows the same path as the request, for the purpose of traversing firewalls or
satisfying other specific routing demands.
The client initiating a request must insert its own host name or network address to the
Via field of the request. If the well-known (UDP) port number is not used, it is also
required to insert the local (UDP) port number.
z
Well-known port number: also known as famous port number or default port
number. It is 5060 defined in SIP and it is used for communications in default
cases.
Local port number: also known as client port number. You can customize it for
communications in specific cases. In the SoftX3000, it is used to achieve the load
sharing of protocol processing among multiple MSGI boards.
7.1.2 H.323
I. Basic concepts
The ITU-T Recommendation H.323 describes a communications control protocol for
providing multimedia communications services over packet-based networks. The
H.323 protocol suite is composed of H.225.0 and H.245.
z
H.225.0: including several sub protocol stacks such as Registration, Admission,

and Status (RAS), Q.931, and Real Time Protocol (RTP)/Real Time Control
Protocol (RTCP), used for registration, authentication, call control and media
stream packetization.

7-2

z
H.245: multimedia communications control protocol, used for negotiation of

capabilities and opening and closing of logical channels.
H.323 describes terminals and other entities that provide multimedia communications
services over packet-based networks which may not provide a guaranteed Quality of
Service (QoS). These include Terminals, Gateways, Gatekeepers, and Multipoint
Control Units.
II. Gatekeeper
Gatekeeper (GK) is an administration point in a network. All terminals, gateways, and
MCUs managed by a GK are grouped as a zone. One zone contains at least one
terminal and one and only one GK (MCU and gateway are optional).
GK provides H.323 terminals with the following services:
z
Access authentication: network resource allocation and identity authentication.
Address resolution: translation between alias and network address.
Bandwidth administration: application for initial bandwidth and control of

bandwidth change.
Billing management: provisioning of billing channel.
Area administration: management of the subordinate devices.
Call control: provisioning of various supplementary services.
III. Gateway
Gateway (GW) is an endpoint device supporting realtime communication between one
H.323 terminal and one ITU terminal in WAN. Conceptually, GW functions in converting
media information codes and signaling. In signaling conversion, if GW is regarded as a
terminal in one network, it implements conversion between user signaling and H.323
protocol; if GW connects two different networks, for example, Packet Based Network
(PBN) and Switched Circuit Network (SCN), it implements the conversion between
other signaling and H.323 protocol.
H.323 GW accomplishes interworking between different types of networks as well as
conversion of format and contents of signaling messages, communication protocol
procedures, and media stream format.
IV. Port number for call signaling

When H.323 is borne over an IP network, call signaling requires TCP port number
(Q.931 or H.245 messages) to identify different calls. The protocol defines that
z
Each call such as a multimedia call occupies a maximum of two port numbers.
That is, H.225.0 and H.245 occupy different port numbers;
If multiple calls exist at the same time, the different calls must use different port
numbers. That is, the same port number cannot be shared by more than one call
at the same time;

7-3

Whenever a call ends, the port number resources occupied by the call are
released.
According to the preceding rules, to configure the local port number range for call
signaling in the ADD H323APP command, it is recommended to double the number of
Q.931 calls, which each MSG module is capable of processing, as the local port
number range for call signaling.
7.2 Configuring SIP Data

7.2.1 Overview
SIP data defines a well-known port number, several local port numbers and a local IP
address used for SIP of the local office. To configure SIP trunk and SIP user data, SIP
protocol data must have been configured. Otherwise, the SIP protocol stack in the host
software may not run normally. See Figure 7-1.
During the process of SoftX3000 data configuration, some parameters defined when
you configure equipment data will be referenced during the configuration of SIP data.
The referencing relationship is presented as the broken lines in Figure 7-1. For the
parameter referencing relationship between SIP data and other data, see Table 7-1.
Table 7-1 Parameter referencing relationship between SIP data and other data
Input parameter
Output parameter
Name
Defined in
Name
Referenced in
Equipment information
MSGI module number
IFMI module number
II. Preparations
Before configuring SIP data, make sure that all preparations are done as specified in
Table 7-2.
SN
Item
Remark
Range
of
local
port
numbers for SIP processing
modules of the local office
Used to achieve the load sharing among the

SIP processing modules of the local office
Well-known port number for

SIP of the local office
One of the interconnection parameters

between the SoftX3000 and a variety of SIP
devices

7-4

SN
3
Item
Remark
Local IP address for SIP of

the local office

between the SoftX3000 and a variety of SIP
devices

Table 7-3 lists the general steps for configuring SIP data.
Step
Description
Command
Set SIP global configuration
SET SIPCFG
Set SIP local port
SET SIPLP

There is no referencing relationship between key parameters used when you configure
SIP data.
7.2.2 Setting SIP Global Configuration

I. Related commands
Command
Function
SET SIPCFG
To set SIP global configuration
RMV SIPCFG
To remove SIP global configuration
LST SIPCFG
To list SIP global configuration

z
There are two interconnection parameters between the SoftX3000 and the variety
of SIP devices. One is the well-known port number of SIP. The other is the local IP
address.
The local port numbers serve the IFMI to share incoming SIP message traffic
among processing modules. The SET SIPCFG command defines the range of
local port numbers to be used by the SIP processing modules of the local office.

[T1 timer length (*100ms)]

7-5

This parameter defines the value of the T1 timer specified by SIP. Its value ranges from
2 to 2 in unit of 100 ms. The default value is 5 x 100 (that is, 500 ms).
[T2 timer length (*100ms)]
This parameter defines the value of the T2 timer specified by SIP. Its value ranges from
10 to 100 in unit of 100 ms. The default value is 40 x 100 (that is, 4000 ms).
[Use compact header]
This parameter specifies whether to use the compact coding mode in SIP messages
that are transmitted from the SoftX3000. By default, it is set to False.
[Use session timer]
This parameter specifies whether to start the heartbeat timer in call messages sent
from the SoftX3000 to SIP users. By default, it is set to True.
[Session timer length (min)]
This parameter defines the value of the SIP heartbeat timer. It is valid only when the
heartbeat timer is started. Its value ranges from 1 to 100 in unit of minute. The default
value is two minutes.
[Minimum registeration expires duration (min)], [Maximum registeration expires
duration (min)]
These parameters specify the minimum and maximum durations for SIP users to
re-send registration requests to the SoftX3000. Its value ranges from 1 to 100 in unit of
minute. By default, the minimum registration duration is 5 minutes, and the maximum
registration duration is 60 minutes.
The purpose of these two parameters: After an SIP user registers in the SoftX3000
sucessfully for the first time, the SoftX3000 notifies the SIP user in the registration
response message of the duration for re-sending the registration request to the
SoftX3000. If the SIP user does not send the request within the specified period of time,
the SoftX3000 sets this SIP user to offline state.
[Minimum Local Port], [Maximum Local Port]
These two parameters define the range of local port numbers available for SIP
processing module (the MSGI) in the SoftX3000. The default values are 5061 and 5188
respectively. That is, 128 local port numbers are available.
It is not recommended that the port number range conflicts with other protocol port
numbers in the database, for the variety of protocol messages transferred through the
same FE port (the IFMI board).
[Server Port]
Server port is also known as the well-known port number of SIP. It is one of the
interconnection parameters between the SoftX3000 and a variety of SIP devices. It
specifies the UDP port number to be used for communication for the first time between

7-6

the SoftX3000 and a SIP device. By default, it is 5060, as defined by SIP. Do not modify
this port number if it is not for a specific purpose.
[Software parameter of service control]
It indicates if SIP supports some special services or applications. There are 16 options
in total, but only two are used currently and the others are reserved. The meaning of the
two options is as follows:
z
Release early-dialog by BYE: It indicates if the SoftX3000 can release the calls
that are released before pickup with the BYE method. By default, it is not
supported. If you select this option, after a caller hangs up when the SIP callee
hears the ringing tone,. the SoftX3000 will send a message to the peer softswitch
or the called SIP terminal to end the call with the BYE method. If you do not select
the option, the SoftX3000 will end the call by sending a message to the called SIP
terminal or the peer softswitch with the CANCEL method.
Support redirect: It indicates if the SoftX3000 supports the call redirection function
of SIP trunks. By default, it is not supported. When the SoftX3000 receives a call
redirection acknowledgement message 300, 301, 302, or 305 (meaning that the
callee is in the local office) from the peer office after sending an INVITE request
through an SIP outgoing trunk, if this option is selected, the SoftX3000 will
originate a call to the new address to complete call connection; otherwise, the
SoftX3000 will directly release the call.
7.2.3 Setting SIP Local Port

I. Related commands
Command
Function
SET SIPLP
To set SIP local port
RMV SIPLP
To remove SIP local port
LST SIPLP
To list SIP local port

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 opposite and the outgoing SIP message packet carries that port
number. What is specified by the system is the local port number of an MSGI. On
receipt of the returned SIP message packet, the IFMI dispatches it to that MSGI
according to the carried port number.
For the first SIP message from other office, the well-known port number, 5060, is
carried usually. 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
7-7

packet, processes it, and returns an outgoing SIP message packet which carries a port
number to receive responses from the opposite. For the subsequent SIP message
packets in the same call procedure, that local port number will be used for
communication.

[MSGI module number]
This parameter specifies the module number of the MSGI where a local UDP port
number for SIP is to be configured. This parameter is defined in the ADD BRD
[Port]
This parameter defines the local port number of the MSGI for processing SIP. The value
of the port number must be in the range defined by the minimum local UDP port number
and the maximum local port number in the SET SIPCFG command.
7.3 Configuring H.323 Data

7.3.1 Overview
H.323 data defines gateway (GW) registration information, Q.931 signaling port
number range used for H.323 of the local office. To configure H.323 trunk, H.323 user
and videoconferencing service data, H.323 protocol data must have been configured.
Otherwise, the H.323 protocol stack in the host software may not run normally. See
Figure 7-1.
you configure equipment data will be referenced during the configuration of H.323 data.
parameter referencing relationship between H.323 data and other data, see Table 7-4.
Table 7-4 Parameter referencing relationship between H.323 data and other data
Input parameter
Output parameter
Name
Defined in
Name
Referenced in
MSGI module number
IFMI module number
II. Preparations
Before configuring H.323 data, make sure that all preparations are done as specified in
Table 7-5.
7-8


SN
Item
Remark
GW identifier (alias)
One of the interconnection parameters between the

SoftX3000 and external gatekeeper (GK) when the
SoftX3000 implements GW functions.
Port number range

for Q.931 signaling
Port number for the SoftX3000 to process call

signaling

Table 7-6 lists the general steps for configuring H.323 data.
Step
Description
Command
Add H.323 system information
ADD H323SYS
Add H.323 application information
ADD H323APP

There is no referencing relationship between key parameters used when you configure
H.323 data.
7.3.2 Adding H.323 System Information

I. Related commands
Command
Function
ADD H323SYS
To add H.323 system information
RMV H323SYS
To remove H.323 system information
MOD H323SYS
To modify H.323 system information
LST H323SYS
To list H.323 system information

In the H.323 network, the SoftX3000 can implement both GW and GK functions. In
different applications, the SoftX3000 plays a different role. For example, the SoftX3000
always acts as a GK for local H.323 users; the SoftX3000 may be a GW or a GK for
H.323 trunks according to a specific networking.
The ADD H323SYS command defines certain key parameters of the H.323 protocol of
the local office when the SoftX3000 acts as a GW or GK. Configure them carefully.
7-9


[System name]
The system name is one of the interconnection parameters between the SoftX3000 and
an external GK when the SoftX3000 acts as a GW. It defines the device identifier (alias)
for the SoftX3000 to register to the external GK.
[IRR message retry count]
By default, the Information Request Response (IRR) retry count is 3. If an H.323
terminal sends an IRR message to the SoftX3000 but receives no Information
Acknowledgement (IACK), the terminal will repeat sending the same IRR. When the
IRR is retransmitted for the maximum times, the terminal stops retransmitting the IRR
again.
7.3.3 Adding H.323 Application Information

I. Related commands
Command
Function
ADD H323APP
To add H.323 application information
RMV H323APP
To remove H.323 application information
MOD H323APP
To modify H.323 application information
LST H323APP
To list H.323 application information

When you use the SET DPA command to set protocol dispatch abilities, H.323 dispatch
abilities cannot be set for the corresponding MSGI. To let an MSGI have the H.323
protocol processing functionality, H.323 application-layer configuration for the
corresponding MSG module must be added in the ADD H323APP command.
In the SoftX3000 V300R003 and the later versions, the commands ADD H323APP and
MOD H323APP do not support setting online, that is, after the commands are used to
add or modify H. 323 application-layer configuration, the related configuration does not
take effect immediately. The configuration is invalid unless resetting the corresponding
MSGI module.

This parameter specifies the module number of the MSGI (or IFMI) where H.323
application-layer configuration is to be added. This parameter is defined in the ADD
BRD command and referenced here.
7-10

This parameter specifies the module number of the IFMI to dispatch H.323 protocol
messages at the SoftX3000 side. This parameter is defined in the ADD BRD command
and referenced here.
[MSGI module type]
This parameter specifies the type of H.323 application-layer protocols for the MSGI
module to process. The options are
z
RAS application: processing H.323 RAS signaling.
CALL application: processing H.323 call signaling, that is, Q.931 messages.
RAS & CALL application: processing both RAS signaling and call signaling of
H.323.
If only one pair of MSGIs (in active/standby mode) is required to process H.323 protocol,
select RAS & CALL application as the type of the MSG module. If more than one pair
of MSGIs is required to process H.323 protocol, configure this parameter according to
the load-sharing principle, with the functions separated.
[Call local minimum port value], [Call local maximum port value]
These two parameters 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:
z
The minimum local port number or the maximum local port number can only be an
integer from 0 to 65535.
It is recommended to set the local TCP port number range for each MSGI to the
integral multiple of 2000. For example, set the local minimum port value to 6000,
and the local maximum port value to 8000.
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).
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.
7.4 Configuring STUN Data

7.4.1 Overview
STUN data defines the module number of the IFMI that dispatches STUN messages at
the transport layer. Therefore, STUN data only references the IFMI module number
parameter defined when you configure equipment data.

Table 7-7 lists the general steps for configuring STUN data.
7-11


Step
Description
Command
Add STUN protocol dispatch
ADD STUNDISP
Set dispatch ability
SET DPA
7.4.2 Adding STUN Protocol Dispatch

I. Related commands
Command
Function
ADD STUNDISP
To add STUN protocol dispatch
RMV STUNDISP
To remove STUN protocol dispatch
LST STUNDISP
To list STUN protocol dispatch

This parameter specifies the module number of the IFMI that dispatches STUN
messages at the transport layer. This parameter is defined in the ADD BRD command
7.4.3 Setting Dispatch Ability

I. Related commands
Command
Function
SET DPA
To set dispatch ability
LST DPA
To list dispatch ability

[Module number]
This parameter specifies the module number of the IFMI for which the STUN protocol
dispatch ability is to be set. This parameter is defined in the ADD BRD command and
referenced here.
[Dispatch ability]
This parameter defines the protocol(s) that the corresponding module can dispatch. Set
it to STUN here.

7-12

Chapter 8 Configuring Signaling Data

This chapter details how to configure signaling data, such as Message Transfer Part
2-User Adaptation Layer (M2UA), Message Transfer Part 3-User Adaptation Layer
(M3UA), V5.2-User Adaptation Layer (V5UA), ISDN Q.921-User Adaptation Layer
(IUA), Message Transfer Part (MTP), Signaling Connection and Control Part (SCCP),
V5 interface, and Primary Rate Access (PRA) link. To configure signaling data,
equipment data and media gateway data must have been configured. See Figure 8-1.
Only when configuring V5 interface data
Start
Equipment data
Trunk data
Office data
Number analysis
Charging data
Subscriber data
MG data
Centrex data
MRS data
Call barring data
Protocol data
IN service data
Signaling data
Other service data
Routing data
Other application
data
End

It should be noted that other signaling data, except V5 interface, should have been
configured before the corresponding trunk data is configured. V5 interface data must be
configured after V5UA data and V5 trunk data has been configured because the V5
trunk group number parameter defined in V5 trunk data is referenced in V5 interface
data.

8-1


8.1.1 SIGTRAN
I. Basic concepts
Signaling Transport (SIGTRAN) is a protocol that supports transmission of Switched
Circuit Network (SCN) signaling protocol through IP network. SIGTRAN supports the
inter-layer standard primitive interface defined in SCN signaling protocol hierarchy
model, so as to ensure utilization of the existing SCN signaling application without
modification. It also uses the standard IP transport protocol as the transmission bottom
layer, and satisfies the special transmission requirements of SCN signaling by adding
its own functions.
SIGTRAN is a protocol stack. Two layers of protocols are included in the SIGTRAN
protocol stack, that is, transmission protocols and adaptation protocols. Examples of
transmission protocols are Stream Control Transmission Protocol (SCTP)/IP. Examples
of adaptation protocols are M2UA (MTP2 User adaptive), M3UA (MTP3 User adaptive),
V5UA (V5 User adaptive), and IUA (Q.921 User adaptive). The SIGTRAN protocol
model is illustrated in Figure 8-2.
M3UA
M2UA
M2PA
V5UA
IUA
SUA
SCTP
IP
MAC
M3UA: MTP3-User Adaptation Layer

M2UA: MTP2-User Adaptation Layer
IUA: ISDN Q.921-User Adaptation Layer
M2PA: MTP2-User Peer-to-Peer Adaptation Layer
V5UA: V5.2-User Adaptation Layer
SUA: SCCP-User Adaptation Layer
SCTP: Stream Control Transmission Protocol
IP:Internet Protocol
MAC: Media Access Control
Figure 8-2 SIGTRAN protocol model
II. Signaling Gateway

Signaling Gateway (SG), a signaling agent, can translate and terminate SCN signaling
to IP signaling at the edge of SCN and IP network. In actual networking applications, an
SG may exist in different forms.

8-2

z
Independent SG: Being a physically separate device, the SG converts and adapts
Signaling System No.7 (SS7) to M3UA, such as U-SYS SG7000 Signaling
Gateway (SG7000 for short) developed by Huawei.
Embedded SG: Also known as built-in SG. SG functions are embedded in a

media gateway. In a specific networking application, the embedded SG can
convert and adapt SS7 to M2UA, V5 to V5UA, or DSS1 to IUA, such as U-SYS
TMG8010 Trunk Media Gateway (TMG8010 for short) and HUAWEI UMG8900
Universal Media Gateway (UMG8900 for short) developed by Huawei.
Integrated SG: SG functions are embedded in a softswitch. That is, the softswitch
provide signaling conversion and adaptation functions in addition to media
gateway control and call processing functions. For example, the SoftX3000 of
Huawei can act as an integrated SG.
III. Client/Server model for SCTP associations

SCTP, with associations structured in a Client/Server model, is the transport layer of
SIGTRAN. To ensure the normal functioning of SIGTRAN, it is recommended to learn
the working mode of a variety of devices in SCTP associations. Typically, a device
acting as an SG is usually configured as a server in SCTP associations and other
device interconnected to the SG must be configured as a client in SCTP associations.
For example, the SoftX3000 interconnects with an SG7000 and the SG7000 acts as a
signaling gateway. In this case, the SG7000 is the server and the SoftX3000 is the
client in the SCTP associations bearing M3UA. Another example, the SoftX3000
interconnects with a TMG8010 and the TMG8010 acts as an embedded signaling
gateway. In this case, the TMG8010 is the server and the SoftX3000 is the client in the
SCTP associations bearing M2UA. Other cases can be deduced in the same way.
IV. Peer-to-peer and non-peer-to-peer networking models regarding M3UA

Two signaling devices communicate with each other through SIGTRAN. If one is an
Application Server (AS) and the other a Signaling Gateway (SG), it is called a
non-peer-to-peer" network model. If both are ASs or SGs, it is called a peer-to-peer
networking model.
In the SIGTRAN protocol suite, the M2UA, V5UA and IUA protocols support
non-peer-to-peer network model only; the M3UA protocol supports both peer-to-peer
and non-peer-to-peer networking models.
V. Four parameters identifying an SCTP association

In SIGTRAN, local IP address, local port number, peer IP address, and peer port
number uniquely identify an SCTP association. In the SoftX3000, it may be an M2UA
link, M3UA link, V5UA link, IUA link, or H.245 link. When adding such a link, conform to
the following rules:
8-3

z
Local IP address, local SCTP port number, peer IP address, and peer SCTP port
number are used for device interconnection usage and should be negotiated
between both devices.
When local IP address and peer IP address are determined, a link between the
signaling devices depends on the combination of the local SCTP port number and
the peer SCTP port number. That is, if several links use the same peer SCTP port
number, their local SCTP port numbers cannot be the same, and it is the same
case conversely.
For a specific protocol, if the SoftX3000 functions as a client through that protocol,
it is recommended to use the same peer SCTP port number for the links related to
that protocol. However, local SCTP port numbers cannot be the same and should
be planned for assignment.
For a specific protocol, if the SoftX3000 functions as a server through that protocol,
it is recommended to use the same local SCTP port number for the links related to
that protocol. However, peer SCTP port numbers cannot be the same and should
be planned for assignment.
VI. M3UA local entity and destination entity

M3UA local entity and destination entity can be considered as the mirror of SS7 local
signaling point and destination signaling point in the M3UA protocol. The concepts of
adjacent destination entity and non-adjacent destination entity can be considered as
the extension of the related SS7 concepts in the M3UA protocol. Accordingly, the M3UA
data configuration process is basically the same as the MTP data configuration
process.
8.1.2 SS7
I. Basic concepts
The International Telegraph and Telephone Consultative Committee (CCITT) (now the
ITU) 1988 Blue Book Recommendation Q.700 provides the basic structure of the
Signaling System No. 7 (SS7). The whole signaling system is composed of Message
Transfer Part (MTP), Signaling Connection Control Part (SCCP), Telephone User Part
(TUP), ISDN User Part (ISUP), and Transaction Capabilities Application Part (TCAP)
over four functional levels.
Figure 8-3 shows the architecture of the SS7 and illustrates the functional relationship
between the various functional blocks of the SS7 and between the SS7 levels and the
Open Systems Interconnection (OSI) reference model layers.

8-4

Users of SS7
OSI layers
7
6
5
4
TCAP
Transaction Capabilities
(TC)
ISDN
User Part
Telephone
User Part
(ISUP)
(TUP)
Signaling Connection Control Part

(SCCP) Level 4
Level 4
Level 4
Other MTP users
2
1
Level 3 Signaling network functions
Level 2 Signaling link functions
Level 1 Signaling data link functions
Other SS7 signaling nodes
Figure 8-3 Architecture of SS7

As shown in Figure 8-3, the MTP level 1 implements the OSI layer 1 (physical layer)
functions; the MTP level 2 implements the OSI layer 2 (data link layer) functions; the
MTP level 3 along with the SCCP implements the OSI layer 3 (network layer) functions;
the TC implements the functions of the OSI layers 4 to 6 (transport layer, session layer,
and presentation layer); the TCAP implements part of OSI layer 7 functions and the TC
users implement the remaining.
The 1980 Yellow Book SS7 Recommendation only provides four functional levels to
achieve communications and transport connection-related signals. However, with the
development of ISDN and Intelligent Network (IN), signals both related to circuit
connection and not related to circuit connection have to be conveyed, for example,
ISDN user oriented end-to-end information used for maintenance and administration
purposes. The original MTP functions are unable to meet that requirement. Therefore,
the SCCP is added in 1984 Red Book. That is, on the premise of not modifying the MTP,
connection oriented and non-connection end-to-end signal transport requirement is
satisfied by adding the SCCP to enhance the MTP functions. At this time, there are still
four functional levels in the SS7, and the combination of the MTP and the SCCP is
named Network Service Part (NSP).

8-5

II. Signaling point and signaling point code

A signaling point is the origination (OPC) and destination (DPC) of signaling messages.
It may be one of a variety of exchanges with SS7 signaling functions, such as a PSTN
exchange, a data exchange or an ISDN exchange. It may also be one of the various
special service centers, such as a network management center, a maintenance center,
or a service control point (SCP).
All signaling points in a signaling network are identified by a unique code known as a
point code. As specified in the SS7, there are four types of signaling networks, namely
international network, international reserved network, national network, and national
reserved network. A signaling point can show its presence in the preceding four
signaling networks and has different point codes in respective signaling networks.
Recommended by the CCITT, there are 24-bit and 14-bit encoding schemes for
signaling point codes. The encoding principles are as follows:
z
Do employ the 14-bit encoding scheme for the international network.
The encoding scheme for the national network varies with countries. For instance,
in China it is 24 bit in length.
The encoding schemes for the international reserved network and the national
reserved network can be customized.
III. Signaling link code

According to the SS7 Recommendations, there are a maximum of 16 signaling links
between two adjacent signaling points. The 16 signaling links are called one signaling
link set (also known as linkset). To uniquely identify the signaling links in the same
signaling link set, Signaling Link Code (SLC) comes into being.
The 4-bit SLC in the range from 0 to 15 is specified during data configuration process.
In the actual device interconnection, the SLC value for the same signaling link between
signaling points must be negotiated and be the same. Otherwise, MTP links cannot be
aligned successfully.
IV. SCCP addressing

Signaling Connection Control Part (SCCP) provides additional functions for the MTP.
The SCCP along with the MTP level 3 is equivalent to the OSI layer 3, responsible for
packet-switched functions of virtual circuits and datagrams. The purpose is to convey
circuit related and non-circuit related signaling messages and other types of messages,
across the SS7 signaling network, between exchanges and between exchanges and
special centers (such as SCP and network management center) in the
telecommunication
networks,
as
well
as
to
connection-oriented network services.

8-6
establish
connectionless
and

There are the following SCCP addressing modes:

z
DPC
DPC + (SSN or GT or both)
GT + (SSN)
In which, DPC refers to Destination Point Code, SSN refers to Subsystem Number, and
GT refers to Global Title.
The SSN identifies a subsystem accessed through the SCCP within a node and may be
a User Part, such as ISUP, MAP and TCAP, to make up for the weakness that there are
insufficient MTP users. The purpose is to enlarge the addressing scope and meet
requirements for supplementary services. The GT may be composed of dialed digits,
such as international telephone numbers, national telephone numbers, and ISDN
numbers. The GT does not explicitly indicate the routing information in the signaling
network and must be translated. As we know, the DPC is significant only in the defined
signaling network. Different from that, the GT is significant globally and provides a far
larger addressing scope than the DPC. Accordingly, non-circuit related messages can
be conveyed between any two signaling points on the world-wide basis. The powerful
addressing capability of the GT is an outstanding characteristic of the SCCP.
8.1.3 V5 Interface Protocol

I. Basic concepts
V5 interface between a Local Exchange (LE) and an Access Network (AN) includes
V5.1 interface and V5.2 interface.
z
A V5.1 interface is composed of a 2048 kbit/s link, responsible for supporting the
access of analog calls and 64 kbit/s based ISDN. These access types provide
assigned bearer channel allocation. One user port matches one bearer channel.
That is, there are invariable correspondence between user ports and bearer
channels, and thus concentration capability is not provided within the AN. In a
V5.1 interface, one time slot (TS16) is used to carry signaling and the others
except TS0 to carry voice signals.
A V5.2 interface may be composed of one to sixteen 2048 kbit/s links according to
actual requirements. A V5.2 interface supports all the access types supported by a
V5.1 interface as well as ISDN primary rate access. The access types supported
by a V5.2 interface provide flexible bearer channel dynamic allocation on a call by
call basis. That is, user ports match bearer channels dynamically. Therefore,
Concentration capability is provided within the AN and over the V5.2 interface.

8-7

II. Configuration of physical Communication channel

1)
The physical C-channel can only be configured at the time slot 16, 15, or 31.
If there is only one 2.048 Mbit/s link on the V5.2 interface, the time slot 16 of the
link is preferentially occupied for the physical C-channel, the time slot 15 occupied
secondly, and the time slot 31 finally.
If there are more than one 2.048 Mbit/s link on the V5.2 interface, the time slots 16
of all the links are preferentially occupied for the physical C-channel. When the
time slots 16 of all the links have been occupied, the time slots 15 of the links
become available. Similarly, the time slots 31 of the links become available after all
the time slots 15 have been occupied.
2)
If the V5.1 interface supports PSTN user ports only, it is required to configure two
C-channels, assigned by provisioning.
3)
If the V5.1 interface supports ISDN user ports or supports ISDN and PSTN user
ports, it is required to configure three C-channels, assigned by provisioning.
4)
If there is only one 2.048 Mbit/s link on the V5.2 interface, the time slot allocated
for the physical C-channel is the same as that for the physical C-channel on the
V5.1 interface, to ensure the full compatibility with the V5.1 interface.
III. Setting of primary and secondary links

The primary link is one of the several 2048 kbit/s links on the V5.2 interface. The
physical C-channel on the time slot 16 must bear the following protocols: protection
protocol, control protocol, link control protocol, and Bearer Channel Connection (BCC)
protocol. The secondary link also corresponds to a 2.048 Mbit/s link. Being the standby
C-channel for the primary link, the secondary link is allocated on the time slot 16,
bearing the protection protocol only.
The PSTN protocol, ISDN Ds (DSS1 signaling), ISDN P (packet-based trunk), and
ISDN F (frame relay) as the protection group 1 can be borne over the primary link,
protected by the secondary link. They, as the protection group 2, can also be borne
over a physical C-channel on a non-primary link and non-secondary link and can be
protected only when the protection group 2 is configured with standby physical
C-channels. At most three standby physical C-channels can be configured.
IV. Configuration of physical C-channel of primary link

The physical C-channel of the primary link can only be borne over the time slot 16 of an
E1. Except that the physical C-channel for the PSTN protocol can be the primary link
C-channel, the corresponding circuit numbers of other physical C-channels cannot be
the same.

8-8

8.1.4 DSS1
I. Basic concepts
The Digital Subscriber Signaling No. 1 (DSS1) for coordination and control between
ISDN terminal devices and ISDN network devices provides signaling functions
necessary for basic bearer services and supplementary services for both voice and
non-voice usages on the ISDN network. The DSS1 signaling is applicable to the
subscriber-network interface specifications such as Basic Rate Interface (2B+D) and
Primary Rate Interface (30B+D).
In the SoftX3000, the PRA link is a type of signaling link. It can only occupy the time slot
16 of an E1, used to bear the DSS1 signaling on the primary rate interface.
II. Network indicator for PRA link

The DSS1 signaling is not a peer-to-peer subscriber signaling. Before a PRA link is set
up, both ends detect the network indicator of the opposite. The network indicator at one
end must indicate network side and the network indicator at the other end must
indicate subscriber side, before the PRA link is set up successfully. Therefore, the
network indicators for a PRA link must be negotiated and determined with the opposite
office before the PRA link is configured. The purpose is to ensure that the network
indicators at the link ends are not the same.
8.1.5 Mask
Mask is used when M3UA destination entity, M3UA link set, MTP destination signaling
point, MTP link set, and so on, are configured. Mask is introduced for load sharing
among signaling links if there are multiple signaling routes or links.
I. Link selection mask

Link selection mask is used for selecting different signaling links in one link set
(signaling route). The following example of MTP link selection mask illustrates the
application of a mask.
1)
The Signaling Link Selection (SLS) code is composed of four binary bits. It is an
independent field in ISUP messages. For TUP messages, it is the four least
significant bits of the Circuit Identification Code (CIC) carried in the MSU. The SLS
value varies with calls. The change of the SLS code causes the link, which the
Message Signal Unit (MSU) selects and seizes, to change accordingly.
Consequently, the load sharing among the signaling links is achieved.
2)
The mask is also composed of four binary bits. The seizure of a link to convey the
MSU depends on a particular operation of the mask and the SLS code. It is

8-9

prescribed that 1 indicates to retain the corresponding bit of the SLS code and 0 to
mask the corresponding bit of the SLS code. In this way, a valid link selection bit is
found by masking or retaining the specified SLS bits. For example,
SLS = 1 0 1 0
Mask = 0 0 1 1
Result = 0 0 1 0
3)
The result of the SLS ANDed with the mask is a 4-bit binary, whose value range
depends on the mask. Theoretically, if only the decimal value of the mask equals
to the result of the total number of links in a link set minus 1, the signaling unit can
directly use this result for link selection. For example, if a link set has four links in
total and the link selection mask is 0011, the calculation result of the SLS ANDed
with the mask must be between 0-3 no matter what SLS is. This result can be
directly or indirectly used for link selection.
4)
The above-mentioned algorithm can achieve load sharing among links in one link
set, but it has a strict requirement on the number and position of 1 in the link
selection mask. In this case, overlapping of bits between the link selection mask
and the link set selection mask may occur easily when they are both used for link
selection.
5)
To solve this problem, the SoftX3000 uses the following algorithm for link selection:
Suppose the result of the SLS ANDed with the link selection mask is A, the total
number of links in a link set is S, the first link is numbered B, and the link to be
selected is C, then, C=A%S+B. A%S indicates the remainder of dividing A by S.
if A<S, the remainder is A.
6)
Through the calculation of remainder, no matter how many links in a link set, if only
you ensure that the decimal value of the link selection mask is larger than or
equals to the result of the total number of links in the link set minus 1, the system
will automatically select the available link, thus enhancing flexibility in data
configuration greatly.
II. Link set selection mask

Link set selection mask is used for selecting different signaling link sets (routes) in one
office direction. The concept and algorithm of link set selection mask are the same as
those of link selection mask.
III. Overlapping of bits

It means that the same link set number and link number are used when the signaling
unit selects link set and signaling link.
Suppose there are two MTP link sets (numbered 0 and 1) in one office direction, each
MTP link set has two links (numbered 0 and 1), and both the link set selection mask and
the link selection mask are 0010. Because the link set selection mask and the link
8-10

selection mask share the same algorithm, when the system originates calls, link 0 of
link set 0 and link 1 of link set 1 will always be occupied; while link 1 of link set 0 and link
0 of link set 1 will be idle all the time.
To prevent overlapping of bits when the system selects M3UA link set and M3UA link or
selects MTP link set and MTP link, you canot set the link set selection mask and the link
selection mask to the same value. It is recommended to set 1 in the two masks in
different positions. For example, if the link set selection mask is 0110, you can set the
link selection mask to 1001.
8.2 Configuring M2UA Data

8.2.1 Overview
M2UA data defines link related information including local and peer IP addresses and
local and peer port numbers used for interconnection between the SoftX3000 and an
embedded signaling gateway supporting M2UA (for example, TMG8010 or UMG8900).
To configure M2UA data, equipment data and media gateway data must have been
configured. See Figure 8-1.
During the process of the SoftX3000 data configuration, some parameters defined
when you configure equipment data and media gateway data will be referenced during
the configuration of M2UA data, and some parameters defined here will be referenced
during the configuration of MTP link (based on M2UA) data. See Table 8-1.
Table 8-1 Parameter referencing relationship between M2UA data and other data
Input parameter
Name
Output parameter
Defined in
Name
Referenced in
IP address of FE
port
Equipment
information
M2UA link number
MTP link data
BSGI
number
Equipment
information
Media gateway data
module
Equipment identifier
of media gateway
II. Preparations
Before configuring M2UA data, make sure that all preparations are done as specified in
Table 8-2.
8-11


SN
Item
Remark
IP address of the
embedded signaling
gateway

SoftX3000 and the embedded signaling gateway
Local SCTP port

number for M2UA
links (at client side)

SoftX3000 and the embedded signaling gateway. This
port number should be planned and assigned in a
unified way with the local SCTP port numbers for
M3UA links, V5UA links, and IUA links.
Peer SCTP port

number for M2UA
links (at server side)


Table 8-3 lists the general steps for configuring M2UA data.
Step
Description
Command
Add embedded signaling gateway
ADD ESG
Add M2UA link set
ADD M2LKS
Add M2UA link
ADD M2LNK

you configure M2UA data.

8-12

ADD ESG
[SG ID]
[SG name]
[Equipment ID]
ADD M2LNK
[Module number]
[Link No]
[SG ID]
8.2.2 Adding Embedded Signaling Gateway

I. Related commands
Command
Function
ADD ESG
To add embedded SG
RMV ESG
To remove embedded SG
MOD ESG
To modify embedded SG
LST ESG
To list embedded SG

[SG ID]
The SG ID uniquely identifies an embedded signaling gateway which supports M2UA
and/or V5UA and/or IUA. The value range is 0 to 511.
[SG name]
This parameter is used to describe the embedded signaling gateway in character string
for identification purposes.
[Equipment ID]

8-13

This parameter specifies the media gateway in which the signaling gateway is
embedded. This parameter is defined in the ADD MGW command and referenced here.
Currently, a signaling gateway supporting M2UA can be embedded in a TMG8010 or
UMG8900.
8.2.3 Adding M2UA Linkset

I. Related commands
Command
Function
ADD M2LKS
To add M2UA linkset
RMV M2LKS
To remove M2UA linkset
MOD M2LKS
To modify M2UA liskset
LST M2LKS
To list M2UA linkset

[M2UA linkset index]
It uniquely identifies an M2UA link set, ranging from 0 to 511.
[Linkset name]
It names a link set with a string of characters.
[SG ID]
It specifies the embedded signaling gateway to which an M2UA link set belongs. It must
be defined in ADD ESG before being referenced here.
[Traffic mode]
As one of the parameters for the SoftX3000 to interconnect with an embedded
signaling gateway (UMG8900), it specifies the traffic mode used by an M2UA link set.
There are two traffic modes:
z
Override mode: N+1 backup mode. In this mode, only one link in a link set is
activated, and the other links are standby. When the activated link is faulty, one
standby link will be activated immediately for traffic transmission.
Load-sharing mode: In this mode, all links in a link set are activated and they share
load.
When the SoftX3000 interconnects with the embedded signaling gateway, the link set
for interconnection must keep the same traffic mode at both ends (load-sharing mode is
recommended); otherwise, M2UA links cannot work well.

8-14

[Interface ID type]
As one of the parameters for the SoftX3000 to interconnect with an embedded
signaling gateway (UMG8900), it specifies the interface ID type of MTP links carried on
an M2UA link set. By default, it is Interger. You can set it to Text as needed, but it
must be negotiated with the embedded signaling gateway.
8.2.4 Adding M2UA Link

I. Related commands
Command
Function
ADD M2LNK
To add M2UA link
RMV M2LNK
To remove M2UA link
MOD M2LNK
To modify M2UA link
LST M2LNK
To list M2UA link

This parameter specifies the module number of the BSGI to process the M2UA link
protocol. This parameter is defined in the ADD BRD command and referenced here.
[Link number]
This parameter specifies the logical number of the M2UA link in the corresponding
BSGI module. The value range is 0 to 31. In the same BSGI module, all M2UA links
must be numbered universally. That is, one BSGI module supports a maximum of 32
M2UA links.
It specifies the M2UA link set to which a specific M2UA link belongs. It must be
definedin ADD M2LKS before being referenced here.
For the M2UA links in one M2UA link set, all of them can only be configured on one
BSGI. To ensure reliability of M2UA links, the M2UA links from the SoftX3000 to the
same embedded signaling gateway should be allocated to different BSGIs. Therefore,
you need to set the M2UA links on different BSGIs to belong to different M2UA link sets.
[Maximum in streams]
This parameter specifies the maximum number of streams allowed to be received at
the local end when an SCTP association is established. Usually, this parameter is 1
8-15

plus the number of the MTP links actually borne over M2UA link. This parameter can
also be the default value, 33. The actual number of streams received after an SCTP
association is established is negotiated between both ends.
[Maximum out streams]
This parameter specifies the maximum number of streams allowed to be transmitted
from the local end when an SCTP association is established. Usually, this parameter is
1 plus the number of the MTP links actually borne over M2UA link. This parameter can
also be the default value, 33. The actual number of streams transmitted after an SCTP
[Local port]
One of the interconnection parameters between the SoftX3000 and the embedded
signaling gateway (TMG8010 or UMG8900). This parameter specifies the SCTP port
number used for M2UA messages at the SoftX3000 side. The configuration principles
for this port number are as follows:
z
If the SoftX3000 acts as a server in the M2UA link, it is recommended to set the
local SCTP port numbers of several M2UA links configured between the
SoftX3000 and the embedded signaling gateway to the same value.
If the SoftX3000 acts as a client in the M2UA link, the local port numbers of several
M2UA links configured between the SoftX3000 and the embedded signaling
gateway cannot be the same.
Because the M2UA, M3UA, V5UA, IUA, and H.245 protocols are all transported
on the basis of the SCTP, it is recommended to universally plan the ranges of local
SCTP port numbers for the links of different protocols before data configuration.
Do not assign the same port number to several links.
[Local IP address1], [Local IP address2]

A local IP address is one of the interconnection parameters between the SoftX3000 and
the embedded signaling gateway. It specifies the IP address of the FE port used for
dispatching M2UA messages in the SoftX3000. This parameter is defined in the ADD
FECFG command and referenced here. The local IP address 1 is a mandatory
parameter.
If the SoftX3000 accommodates more than one IFMI, you can specify the local IP
address 2. Such a configuration supports the multi-homing function of the SCTP
associations at the SoftX3000 side to improve the networking reliability of the system.
[Peer port]
signaling gateway. This parameter specifies the SCTP port number used for M2UA
messages at the embedded signaling gateway. If the embedded signaling gateway acts
as a server in the M2UA link, from the point of view of the SoftX3000, the peer port
8-16

numbers for different M2UA links can be the same. For example, if the well-known port
number for M2UA is used at the embedded signaling gateway, the peer port numbers
for different M2UA links at the SoftX3000 can be the default value, 2904.
[Peer IP address1], [Peer IP address2]
A peer IP address is one of the interconnection parameters between the SoftX3000 and
the embedded signaling gateway. It specifies the IP address of the embedded signaling
gateway. The peer IP address 1 is a mandatory parameter.
If the embedded signaling gateway also supports the multi-homing function of the
SCTP associations, you can specify the peer IP address 2. Such a configuration
supports the multi-homing function of the SCTP associations at the signaling gateway
side to improve the networking reliability of the system.
[Priority]
It specifies the routing priority for an M2UA link. An M2UA link with currently the highest
priority is preferred. A link will be selected to convey signaling traffic only after there are
absolutely no available links with a priority higher than it. The greater the value is, the
lower the priority is. 0 indicates the highest priority.
[Client/Server mode]
It is one of the interconnection parameters between the SoftX3000 and the embedded
signaling gateway. This parameter specifies the application mode of the SoftX3000 in
the M2UA link. By default, it is set to Client. If the SoftX3000 is set to Client, you must
set the embedded signaling gateway to Server, and conversely the same.
This parameter specifies the work state of an M2UA link in normal cases. The
configuration of this parameter is closely related to the traffic mode of the M2UA link
set.
z
In the override traffic mode, only one M2UA link in the same link set can be set to
Active and the other links must be set to Standby.
In the load-sharing traffic mode, all the M2UA links in the same link set must be set
to Active.
[Master/Slave flag]
follows:
z

8-17

set this parameter to slave.
8.3 Configuring M3UA Data

8.3.1 Overview
M3UA data defines related information for the SoftX3000 to interconnect with SG or
SCP through M3UA link. M3UA data includes signaling point code of the local entity,
signaling point code of the destination entity, local and peer IP addresses, local and
peer port numbers, C/S working mode for the links, and traffic mode for the links. To
configure M3UA data, the equipment data, office data, and media gateway data must
have been configured. See Figure 8-1.
you configure office data, equipment data, and media gateway data will be referenced
during the configuration of M3UA data, and some parameters defined here will be
referenced during the configuration of SCCP data and routing data. The referencing
relationship is presented as the broken lines in Figure 8-1. For the parameter
referencing relationship between M3UA data and other data, see Table 8-4.
Table 8-4 Parameter referencing relationship between M3UA data and other data
Input parameter
Name
Output parameter
Defined in
Name
Referenced in
Equipment
information
Signaling point code

of local entity
SCCP data and

routing data
BSGI module number
Equipment
information
Signaling point code

of destination entity
SCCP data and

routing data
IFMI module number
Equipment
information
Local signaling point

code
Office data
II. Preparations
Before configuring M3UA data, make sure that all preparations are done as specified in
Table 8-5.

8-18


SN
Item
Remark
Signaling point code of local

entity

between the SoftX3000 and SG or SCP.
Signaling point code of

destination entity

IP address of destination
entity

Local SCTP port number for

M3UA links (at client side)

between the SoftX3000 and SG or SCP. This
port number should be planned and assigned
in a unified way with the local SCTP port
numbers for M2UA links, M3UA links, and
IUA links.
Peer SCTP port number for

M3UA links (at server side)

Routing context (optional)


Table 8-6 lists the general steps for configuring M3UA data.
Step
Description
Command
Add M3UA local entity
ADD M3LE
Add M3UA destination entity
ADD M3DE
Add M3UA additional destination service (optional)
ADD M3DS
Add M3UA link set
ADD M3LKS
Add M3UA link
ADD M3LNK
Add M3UA route
ADD M3RT

you configure M3UA data.

8-19


ADD M3LKS
ADD M3LE
[Local entity index]
[LinkSet index]
[NI]
[Adjacent entity index]
[Local entity point code]
[Link select mask]
ADD M3LNK
ADD M3DE
[Destination entity index]
[Module number]
[Link No]
[NI]
[LinkSet index]
ADD M3DS
ADD M3RT
[Destination service index]
[Route name]
[OPC]
[LinkSet index]
8.3.2 Adding M3UA Local Entity

I. Related commands
Command
Function
ADD M3LE
To add M3UA local entity
RMV M3LE
To remove M3UA local entity
MOD M3LE
To modify M3UA local entity
LST M3LE
To list M3UA local entity

The local entity index uniquely identifies a local entity. The value range is 0 to 253. The
quantity of configured local entities depends on the number of the local office signaling
point codes for signaling which is borne over the M3UA.

8-20

For example, the SoftX3000 shows its presence in both international and national
networks with one signaling point code for the international network and four signaling
point codes for the national network. Accordingly,
z
If the M3UA is used to carry signaling in both international and national networks, it
is required to define five local entities;
If the MTP is used to carry signaling in the international network and the M3UA to
bear signaling in the national network, it is required to define four local entities.
[Local entity name]

It identifies a local entity with a string of characters.
[Network indicator]
The network indicator specifies the signaling network where the signaling point code of
the local entity is resident. It may be the international network, the international
reserved network, the national network, or the national reserved network. This
parameter must be set the same as the network indicator pertaining to the signaling
point code in the local office information table.
[Local entity point code]
The signaling point code of the local entity is one of the interconnection parameters
between the SoftX3000 and SG, used to specify the corresponding local signaling point
code of the local entity. This parameter is defined in the SET OFI or ADD OFI command
[Local entity type]
The type of the local entity is one of the interconnection parameters between the
SoftX3000 and SG or SCP, used to specify the application mode of the SoftX3000 in an
M3UA link. Set this parameter by the following principles:
z
In a non-peer-to-peer networking mode, set this parameter to Application Server

(AS) if the SoftX3000 interconnects with SP and SCP in the SS7 network through
SG.
In a non-peer-to-peer networking mode, set this parameter to SG if the

SoftX3000 functions as an integrated signaling gateway.
In a peer-to-peer networking mode, set this parameter to AS if the SoftX3000

interconnects with other softswitch or SCP through M3UA links (instead of through
SG).
[Routing context]
The route context (also known as routing context) is one of the interconnection
parameters between the SoftX3000 and SG. When the type of the local entity is set to
AS, this parameter is available to define the routing key used by the SoftX3000 to
send registration requests to the signaling gateway. The routing context may be a

8-21

decimal number or may be null (that is, not configured). It must be negotiated and
determined before the interconnection.
8.3.3 Adding M3UA Destination Entity

I. Related commands
Command
Function
ADD M3DE
To add M3UA destination entity
RMV M3DE
To remove M3UA destination entity
MOD M3DE
To modify M3UA destination entity
LST M3DE
To list M3UA destination entity

The destination entity index uniquely identifies a destination entity. The value range is 0
to 65534. Set this parameter by the following principles:
z
When there are associated M3UA signaling routes between the SoftX3000 and
the opposite signaling device, that signaling device must be defined to be a
destination entity. For example, if the SoftX3000 interconnects with SG, SCP and
softswitch through M3UA links directly, these devices have to be defined to be
destination entities.
When the opposite signaling device is a destination signaling point, that signaling
device must be defined to be a destination entity. For example, the SoftX3000
interconnects with five PSTN switches and two SCPs through the transfer of
signaling gateway and signaling transfer point; it is required to define seven
destination entities including all those PSTN switches and SCPs.

The local entity index identifies the local entity corresponding to the destination entity.
This parameter is defined in the ADD M3LE command and referenced here.
[Destination entity name]
It identifies a destination entity with a string of characters.
[Network indicator]
the destination entity is resident. It may be the international network, the international

8-22

parameter must be set according to the actual networking.
[Destination entity point code]
The signaling point code of the destination entity is one of the interconnection
parameters between the SoftX3000 and SG or SCP, used to specify the signaling point
code of the destination entity in the SS7 signaling network.
In the SoftX3000 SG opposite device networking model, if the opposite device
also supports M3UA and the SG works as a non-exclusive signaling point, the opposite
device uses the same signaling point code assigned to the SG. That is, the two
destination entities share the same signaling point code (that assigned to the SG) at the
SoftX3000 side.
[STP flag]
This parameter specifies whether or not the destination entity has the signaling transfer
functions. Set this parameter to YES only when the destination entity is an associated
SG of the SoftX3000. Set this parameter to NO in other cases.
[Linkset selection mask]
This parameter specifies how the SoftX3000 shares signaling traffic load among
multiple M3UA link sets to the destination entity. Set the parameter by the following
principles:
z
When there is only one link set between the SoftX3000 and the destination entity,
select the default value B1111 for the link set selection mask.
When there are two or more than two link sets between the SoftX3000 and the
destination entity, you must ensure that the decimal value of the link set selection
mask is bigger than or equals to the result of the total number of link sets minus 1.
For example, if the total number of link sets is 2, you cannot set the link set
selection mask to B0000.
To prevent overlapping of bits, you canot set the link set selection mask and the
link selection mask of any link set to the same value. It is recommended to set 1
in the two masks in different positions. For example, if the link set selection mask is
0110, you can set the link selection mask to 1001.
[Destination entity type]

It is one of the parameters for interworking with SG or SCP, used to specify the
application mode of the destination entity in an M3UA link set. Set this parameter by the
z
In a non-peer-to-peer networking model, set this parameter to SP if the

destination entity is a PSTN switch or SCP that is resident in the SS7 network and
interconnects with the SoftX3000 through SG.

8-23

z
In a non-peer-to-peer networking model, set this parameter to SG if the

destination entity is an associated SG of the SoftX3000.
In a non-peer-to-peer networking model, set this parameter to AS if the

SoftX3000 functions as an integrated SG, that is, the destination entity is an AS.
In a peer-to-peer networking model, set this parameter to AS if the destination

entity is a softswitch or SCP that directly interconnects with the SoftX3000 through
M3UA links (not transferred through SG).
[Adjacent flag]
When the type of the destination entity is set to SG or AS, this parameter is available to
specify whether or not there is any associated M3UA signaling route between the
SoftX3000 and the peer destination entity. If the M3UA messages between the
SoftX3000 and the destination entity are unnecessarily transferred through an SG, set
this parameter to YES. If necessarily transferred through an SG, set this parameter to
NO. For example:
z
In a non-peer-to-peer networking model, set this parameter to YES if the

destination entity is an associated SG of the SoftX3000.
In a non-peer-to-peer networking model, set this parameter to NO if the

destination entity is an SP or SCP that interconnects with the SoftX3000 through
an SG and is resident in the SS7 signaling network.
In a peer-to-peer networking model, always set this parameter to YES no matter

which type of device the destination entity is.
[Networking mode]
When the type of the destination entity is set to AS, this parameter is available to
specify whether the AS interconnected with the SoftX3000 has an exclusive signaling
point code or shares a signaling point code with other ASs (The SoftX3000 functions as
an SG). By default, it is Exclusive SPC.
[Routing context]
The route context (also known as routing context) is one of the interconnection
parameters between the SoftX3000 and AS. That is, when the type of the destination
entity is set to AS, this parameter is available to define the routing key used by the AS to
send registration requests to the SoftX3000. The routing context may be a decimal
number or may be null (that is, not configured). It must be negotiated and determined
before the interconnection.
[Protocol version]
As one of the interconnection parameters between the SoftX3000 and SG or SCP, it
specifies the M3UA version supported by the destination entity. By default, the system
supports M3UA RFC3332.

8-24

8.3.4 Adding M3UA Additional Destination Service (Optional)

I. Related commands
Command
Function
ADD M3DS
To add M3UA additional destination service
RMV M3DS
To remove M3UA additional destination service
MOD M3DS
To modify M3UA additional destination service
LST M3DS
To list M3UA additional destination service

data configuration.
If the SoftX3000 acting as an integrated signaling gateway works as a non-exclusive
signaling point, M3UA additional destination service has to be added for every AS
sharing the same signaling point code with the SoftX3000 in the ADD M3DS command.

[Destination service index]
The destination service index uniquely identifies an M3UA additional destination
service inside the SoftX3000.
This parameter specifies the destination entity to which the SoftX3000 transfers the
received M3UA messages from the originating signaling point. This parameter is
defined in the ADD M3DE command and referenced here.
[OPC]
The originating point code delimitates the scope of M3UA messages for the SoftX3000
to transfer. That is, the SoftX3000 only transfers the M3UA messages that are sent by
the AS and in which the value of the OPC field matches the originating point code
defined here; otherwise, the SoftX3000 discards them. By default, it is All. That is, the
OPC field in the M3UA messages sent from the AS to the SoftX3000 will not be
compared.
[Service indication]
The service indicator delimitates the scope of M3UA messages for the SoftX3000 to
transfer. That is, the SoftX3000 only transfers the M3UA messages that are sent by the
8-25

AS and in which the value of the SI field matches the service indicator defined here;
otherwise, the SoftX3000 discards them. By default, it is All. That is, the SI field in the
M3UA messages sent from the AS to the SoftX3000 will not be compared.
[Start CIC], [End CIC]
When the service indicator is TUP or ISUP, the start circuit identification code and the
end circuit identification code are available to delimitate the scope of the M3UA
messages for the SoftX3000 to transfer. That is, the SoftX3000 only transfers the M3UA
messages that are sent by the AS and in which the value of the CIC field is within the
range of the circuit identification code defined here; otherwise, the SoftX3000 discards
them. If no values are specified for these parameters, the CIC field in the M3UA
messages sent from the AS to the SoftX3000 will not be compared.
8.3.5 Adding M3UA Link Set

I. Related commands
Command
Function
ADD M3LKS
To add M3UA link set
RMV M3LKS
To remove M3UA link set
MOD M3LKS
To modify M3UA link set
LST M3LKS
To list M3UA link set

[Linkset index]
The M3UA link set index uniquely identifies an M3UA link set. The value range is 0 to
65534. Because one link set stands for one signaling route, only one M3UA link set can
be configured between the local entity (SoftX3000) and an adjacent destination entity.
[Linkset name]
It identifies a link set with a string of characters.
[Adjacent entity index]
This parameter specifies the destination entity that has an associated signaling route
with the SoftX3000. This parameter is defined in the ADD M3DE command and
referenced here. Set this parameter by the following principles:
z
In a non-peer-to-peer networking model, if the local office functions as an AS in the

link set, the SG interconnected with the local office is considered as an adjacent

8-26

destination entity and other devices are considered as non-adjacent destination

entities.
z
In a non-peer-to-peer networking model, if the local office functions as an SG in

the link set, all the devices such as SP and SCP interconnected with the local
office are considered as adjacent destination entities.
In a peer-to-peer networking model, all the opposite devices are considered as

adjacent destination entities.
[Link selection mask]

This parameter specifies how the SoftX3000 shares signaling traffic load among
multiple M3UA links in one link set. Set the parameter by the following principles:
z
When there is only one link in a link set, select the default value B1111 for the link
selection mask.
When there are two or more than two links in a link set, you must ensure that the
decimal value of the link selection mask is bigger than or equals to the result of the
total number of links minus 1. For example, if the total number of links is 2, you
cannot set the link selection mask to B0000.
[Traffic mode]
This is one of the interconnection parameters between the SoftX3000 and SG or SCP,
used to specify the traffic mode for the M3UA link set to use. There are two traffic
modes:
z
Override mode: N + 1" backup mode. In this mode, only one link in the link set
keeps active and the other links are in the standby state. When the active link
becomes faulty, one of the standby links is activated immediately to convey the
traffic.
Load-sharing mode: In this mode, all the links in the link set are active and the
traffic to be conveyed is shared among the links.
To interconnect the SoftX3000 with SG or SCP, both ends of the interconnecting link set
must be set to the same traffic mode; otherwise, the M3UA links cannot work normally.
We recommend the load-sharing mode.
[Work mode]
This is one of the interconnection parameters between the SoftX3000 and SG or SCP,
used to specify the work mode of the M3UA link set. Set this parameter by the following
principles:
z
In a non-peer-to-peer networking model, set this parameter to ASP (Application

Server Process) if the SoftX3000 functions as an AS.
8-27

z
In a non-peer-to-peer networking model, set this parameter to SGP (Signaling

Gateway Process) if the SoftX3000 functions as an SG.
In a peer-to-peer networking model, set this parameter to IPSP (IP Server

Process) if the SoftX3000 interconnects with SP or SCP through M3UA links (not
transferred through SG).
8.3.6 Adding M3UA Link

I. Related commands
Command
Function
ADD M3LNK
To add M3UA link
RMV M3LNK
To remove M3UA link
MOD M3LNK
To modify M3UA link
LST M3LNK
To list M3UA link

This parameter specifies the module number of the BSGI to process the M3UA link
[Link number]
This parameter specifies the logical number of the M3UA link in the corresponding
BSGI module. The value range is 0 to 63. In the same BSGI module, all M3UA links
must be numbered uniquely. That is, one BSGI module supports a maximum of 64
M3UA links.
[Link name]
It identifies a link with a string of characters.
SG or SCP. It specifies the IP address of the FE port used for dispatching M3UA
messages in the SoftX3000. This parameter is defined in the ADD FECFG command
and referenced here. The local IP address 1 is a mandatory parameter.
If the SoftX3000 accommodates more than one IFMI, you can also specify the local IP

8-28

[Local port]
One of the interconnection parameters between the SoftX3000 and SG or SCP. This
parameter specifies the SCTP port number used for M3UA messages at the SoftX3000
side. The configuration principles for this port number are as follows:
z
If the SoftX3000 acts as a server in the M3UA link, it is recommended to set the
local SCTP port numbers of several M3UA links configured between the
SoftX3000 and an SG or SCP to the same value.
If the SoftX3000 acts as a client in the M3UA link, the local port numbers of several
M3UA links configured between the SoftX3000 and an SG or SCP cannot be the
same.

SG or SCP. It specifies the IP address of the signaling gateway. The peer IP address 1
is a mandatory parameter.
If the signaling gateway also supports the multi-homing function of the SCTP
associations, you can specify the peer IP address 2. Such a configuration supports the
multi-homing function of the SCTP associations at the signaling gateway side to
improve the networking reliability of the system.
[Peer port]
It is one of the interconnection parameters between the SoftX3000 and SG or SCP.
This parameter specifies the SCTP port number used for M3UA messages at the SG or
SCP side. If the SG or SCP works as a server in the M3UA link, from the point of view of
the SoftX3000, the peer port numbers for its different M3UA links can be the same. For
example, if the SG or SCP uses the well-known M3UA port number, the peer port
numbers for the M3UA links at the SoftX3000 side can be the default value, 2905.
It is one of the parameters for the SoftX3000 to interwork with SG or SCP. This
parameters specifies the application mode of the SoftX3000 in the SCTP association.
z
In a non-peer-to-peer networking model, for example, the SoftX3000

interconnects with a signaling gateway, the application mode of the SoftX3000, if
functioning as an AS, in the M3UA link must be set to Client.
In a non-peer-to-peer networking model, for example, the SoftX3000 is applied as

an integrated signaling gateway, the application mode of the SoftX3000, if
functioning as an SG, in the M3UA link must be set to Server.
8-29

z
In a peer-to-peer networking model, for example, the SoftX3000 directly

interconnects with other softswitch or SCP instead of being transferred through an
SG, the application mode of the SoftX3000 in the M3UA link must be set to Client.
[Linkset index]
This parameter specifies the M3UA link set to which the M3UA link belongs. This
parameter is defined in the ADD M3LKS command and referenced here.
This parameter specifies the work state of the M3UA link in normal cases. The
configuration of this parameter is closely related to the traffic mode of the M3UA link
set.
z
In the override traffic mode, only one M3UA link in the same link set is set to be
active and the other links are set to be standby.
In the loadshare traffic mode, all the M3UA links in the same link set are set to be
active.
[Priority]
This parameter specifies the routing priority for the M3UA link to convey signaling traffic.
A link with currently the highest priority is preferred. A link will be selected to convey
signaling traffic only after there are absolutely no available links with a higher priority
than it. The greater the value is, the lower the priority is. 0 indicates the highest priority.
This parameter specifies the maximum number of SCTP streams contained in each
M3UA message received by the SoftX3000. By default, it is 17. The actual number of
SCTP streams received by the SoftX3000 after the SCTP association is established is
the result negotiated by both parties.
This parameter specifies the maximum number of SCTP streams contained in each
M3UA message sent by the SoftX3000. By default, it is 17. The actual number of SCTP
streams sent by the SoftX3000 after the SCTP association is established is the result
negotiated by both parties.
[Congestion onset threshold]
The unit for this parameter is %. Whenever the signaling traffic loaded on the M3UA
link reaches this threshold, the SoftX3000 starts the congestion control automatically
and the M3UA link will not be used to convey the traffic until the congestion is cancelled.
[Congestion offset threshold]

8-30

The unit for this parameter is %. Whenever the signaling traffic loaded on the M3UA
link is reduced to this threshold, the SoftX3000 cancels the congestion control
automatically and the M3UA link will be brought into service again. By default, it is 40.
[Self loop flag]
This parameter specifies whether or not to enable the self loop function for the M3UA
link. By default, it is set to NO. That is, the self loop function is not enabled. This
parameter is only used for debugging purposes. Be careful to set it.
[Master/Slave flag]
follows:
z
8.3.7 Adding M3UA Route

I. Related commands
Command
Function
ADD M3RT
To add M3UA route
RMV M3RT
To remove M3UA route
MOD M3RT
To modify M3UA route
LST M3RT
To list M3UA route

[Route name]
This parameter is used to describe the M3UA route with a string of characters for
identification purposes.
This parameter specifies the destination entity the M3UA route will be directed to. This
parameter is defined in the ADD M3DE command and referenced here.

8-31

It should be noted that an M3UA route is added, in this command, for all destination
entities defined in the ADD M3DE command except SG.
[Linkset index]
This parameter specifies the M3UA route toward the destination entity, that is, through
which M3UA link set to convey signaling traffic. This parameter is defined in the ADD
M3LKS command and referenced here.
[Priority]
This parameter specifies the routing priority for the M3UA link set (signaling route) to
convey signaling traffic. A link set with currently the highest priority is preferred. A link
set will be selected to convey signaling traffic only after there are absolutely no
available signaling routes with a higher priority than it. The greater the value is, the
8.4 Configuring V5UA Data

8.4.1 Overview
V5UA data defines link related information including local and peer IP addresses, local
and peer port numbers, C/S working mode of link, and link traffic mode, used for
interconnection between the SoftX3000 and an embedded signaling gateway
supporting V5UA (for example, UMG8900). To configure V5UA data, equipment data
and media gateway data must have been configured. See Figure 8-1.
you configure equipment data and media gateway data will be referenced during the
configuration of V5UA data, and some parameters defined here will be referenced
during the configuration of V5 trunk data. The referencing relationship is presented as
the broken lines in Figure 8-1. For the parameter referencing relationship between
V5UA data and other data, see Table 8-7.
Table 8-7 Parameter referencing relationship between V5UA data and other data
Input parameter
Name
Output parameter
Defined in
Name
Referenced in
Equipment
information
V5UA link number
V5 trunk data
BSGI module number
Equipment
information

8-32

Input parameter
Name
Output parameter
Defined in
media gateway
of
Media gateway
data
Name
Referenced in
II. Preparations
Before configuring V5UA data, make sure that all preparations are done as specified in
Table 8-8.
SN
Item
Remark
IP address of
embedded signaling
gateway

Local SCTP port

number for V5UA
links (at client side)

SoftX3000 and the embedded signaling gateway.
This port number should be planned and assigned
in a unified way with the local SCTP port numbers
for M2UA links, M3UA links, and IUA links.
Peer SCTP port

number for V5UA
links (at server side)


Table 8-9 lists the general steps for configuring V5UA data.
Step
Description
Command
ADD ESG
Add V5UA link set
ADD V5UALKS
Add V5UA link
ADD V5UALNK

you configure V5UA data.

8-33

ADD ESG
[SG ID]
[SG name]
[Equipment ID]
ADD V5UALKS
[LinkSet index]
[Traffic mode]
[SG ID]
ADD V5UALNK
[Module number]
[Link No]
[LinkSet index]

I. Related commands
Command
Function
ADD ESG
To add embedded signaling gateway
RMV ESG
To remove embedded signaling gateway
MOD ESG
To modify embedded signaling gateway
LST ESG
To list embedded signaling gateway

[SG ID]
[SG name]

8-34

This parameter is used to describe the embedded signaling gateway with a string of
characters for identification purposes.
[Equipment ID]
The signaling gateway supporting V5UA can only be embedded in a UMG8900
currently.
8.4.3 Adding V5UA Link Set

I. Related commands
Command
Function
ADD V5UALKS
To add V5UA link set
RMV V5UALKS
To remove V5UA link set
MOD V5UALKS
To modify V5UA link set
LST V5UALKS
To list V5UA link set

[Linkset index]
The V5UA link set index uniquely identifies a V5UA link set. The value range is 0 to
65534.
[Linkset name]
[Traffic mode]
This is one of the interconnection parameters between the SoftX3000 and the
embedded signaling gateway (UMG8900), used to specify the traffic mode for the
V5UA link set to use. There are two traffic modes:
z
traffic.

8-35

To interconnect the SoftX3000 with the embedded signaling gateway, both ends of the
interconnecting link set must be set to the same traffic mode; otherwise, the V5UA links
cannot work normally. We recommend the load-sharing mode.
[SG ID]
This parameter specifies the embedded signaling gateway to which the V5UA link set
belongs. This parameter is defined in the ADD ESG command and referenced here.
8.4.4 Adding V5UA Link

I. Related commands
Command
Function
ADD V5UALNK
To add V5UA link
RMV V5UALNK
To remove V5UA link
LST V5UALNK
To list V5UA link

This parameter specifies the module number of the BSGI to process the V5UA link
[Link number]
This parameter specifies the logical number of the V5UA link in the corresponding BSGI
module. The value range is 0 to 31. In the same BSGI module, all V5UA links must be
numbered universally. That is, one BSGI module supports a maximum of 32 V5UA
links.
[Linkset index]
This parameter specifies the V5UA link set to which the V5UA link belongs. This
parameter is defined in the ADD V5UALKS command and referenced here.
plus the number of the V5 interfaces actually borne over V5UA link. This parameter can
also be the default value, 33. The actual number of streams received after an SCTP

8-36


1 plus the number of the V5 interfaces actually borne over V5UA link. This parameter
can also be the default value, 33. The actual number of streams transmitted after an
SCTP association is established is negotiated between both ends.
[Local port]
signaling gateway (UMG8900). This parameter specifies the SCTP port number used
for V5UA messages at the SoftX3000 side. The configuration principles for this port
number are as follows:
z
If the SoftX3000 works as a server in the V5UA link, it is recommended to set the
local SCTP port numbers of several V5UA links configured between the SoftX3000
and an embedded signaling gateway to the same value.
If the SoftX3000 works as a client in the V5UA link, the local port numbers for the
several V5UA links configured between the SoftX3000 and an embedded
signaling gateway cannot be the same.
port numbers for the links of different protocols before data configuration. Do not
assign the same port number to several links.

an embedded signaling gateway. It specifies the IP address of the FE port used for
dispatching V5UA messages in the SoftX3000. This parameter is defined in the ADD
parameter.
[Peer port]
It is one of the interconnection parameters between the SoftX3000 and an embedded
signaling gateway. This parameter specifies the SCTP port number used for V5UA
messages at the embedded signaling gateway side. If the embedded signaling
gateway works as a server in the V5UA link, from the point of view of the SoftX3000, the
peer port numbers for different V5UA links can be the same. For example, if the
well-known port number for V5UA is used at the embedded signaling gateway, the peer
port numbers for different V5UA links at the SoftX3000 can be the default value, 5675.

8-37


the V5UA link. By default, it is set to Client. If the SoftX3000 is set to Client, you must
set the embedded signaling gateway to Server, and conversely the same.
This parameter specifies the work state of the V5UA link in normal cases. The
configuration of this parameter is closely related to the transmission mode of the link
set.
z
In the override traffic mode, only one V5UA link in the same link set is set to be
active and the other links are set to be standby.
In the loadshare traffic mode, all the V5UA links in the same link set are set to be
active.
[Master/Slave flag]
follows:
z

8-38

8.5 Configuring IUA Data

8.5.1 Overview
IUA data defines link related information including local and peer IP addresses, local
and peer port numbers, C/S working mode of link, and link traffic mode, used for
interconnection between the SoftX3000 and an embedded signaling gateway
supporting IUA (for example, UMG8900). To configure IUA data, equipment data and
media gateway data must have been configured. See Figure 8-1.
you configure equipment data and media gateway data will be referenced during the
configuration of IUA data, and some parameters defined here will be referenced during
the configuration of PRA link data. The referencing relationship is presented as the
broken lines in Figure 8-1. For the parameter referencing relationship between IUA data
and other data, see Table 8-10.
Table 8-10 Parameter referencing relationship between IUA data and other data
Input parameter
Name
Output parameter
Defined in
Name
Referenced in
IP address of FE
port
Equipment
information
IUA link number
PRA link data and BRA

subscriber data
BSGI
number
Equipment
information
Media
gateway data
module
of media gateway
II. Preparations
Before configuring IUA data, make sure that all preparations are done as specified in
Table 8-11.
SN
1
Item
Remark
IP address of
embedded signaling
gateway


8-39

SN
Item
Remark
Local SCTP port

number for IUA links
(at client side)

SoftX3000 and the embedded signaling gateway. This
port number should be planned and assigned in a
unified way with the local SCTP port numbers for
M2UA links, M3UA links, and IUA links.
Peer SCTP port

number for IUA links
(at server side)


Table 8-12 lists the general steps for configuring IUA data.
Step
Description
Command
ADD ESG
Add IUA link set
ADD IUALKS
Add IUA link
ADD IUALNK

you configure IUA data.

8-40

ADD ESG
[SG ID]
[SG name]
[Equipment ID]
ADD IUALKS
[LinkSet index]
[Traffic mode]
[SG ID]
ADD IUALNK
[Module number]
[Link No]
[LinkSet index]

I. Related commands
Command
Function
ADD ESG
To add embedded signaling gateway
RMV ESG
To remove embedded signaling gateway
MOD ESG
To modify embedded signaling gateway
LST ESG
To list embedded signaling gateway

[SG ID]
[SG name]
8-41

This parameter is used to describe the embedded signaling gateway with a string of
characters for identification purposes.
[Equipment ID]
The signaling gateway supporting IUA can be embedded in a TMG8010 or UMG8900.
8.5.3 Adding IUA Link Set

I. Related commands
Command
Function
ADD IUALKS
To add IUA link set
RMV IUALKS
To remove IUA link set
MOD IUALKS
To modify IUA link set
LST IUALKS
To list IUA link set

[Linkset index]
The IUA link set index uniquely identifies an IUA link set. The value range is 0 to 65534.
[Linkset name]
[Traffic mode]
This is one of the parameters for the SoftX3000 to interwork with the embedded
signaling gateway (UMG8900), used to specify the transmission mode for the IUA link
set to use. There are two traffic modes:
z
traffic.
To interconnect the SoftX3000 with the embedded signaling gateway, both ends of the
interconnecting link set must be set to the same traffic mode; otherwise, the IUA links
cannot work normally. We recommend the load-sharing mode.

8-42

[Device type]
This parameter specifies the type of the D-channel signaling messages of the ISDN
subscribers that are carried over the IUA link set. That is, the D-channel signaling
messages of BRA subscriber or the D-channel signaling messages of PRA subscriber.
By default, it is BRA.
When the device type is set to BRA, this parameter is available to specify the module
number of the FCCU/FCSU that processes the BRA subscriber calls at the SoftX3000
side. The value range is 22 to 101. This parameter is defined in the ADD BRD
command ADD MGW for adding the embedded IUA SG; otherwise, the BRA subscriber
terminals connected to this MGW cannot work normally.
[Interface ID type]
embedded signaling gateway (UMG8900). When the device type is set to PRA, this
parameter is available to specify the type of the interface identifier of the PRA link that
the IUA link set carries. By default, it is "integer. You can also define it to be a text
interface according to the actual situations after you have negotiated with the
embedded signaling gateway side.
[SG ID]
This parameter specifies the embedded signaling gateway to which the IUA link set
belongs. This parameter is defined in the ADD ESG command and referenced here.
8.5.4 Adding IUA Link

I. Related commands
Command
Function
ADD IUALNK
To add IUA link
RMV IUALNK
To remove IUA link
LST IUALNK
To list IUA link


8-43

This parameter specifies the module number of the BSGI to process the IUA link
[Link number]
This parameter specifies the logical number of the IUA link in the corresponding BSGI
module. The value range is 0 to 31. In the same BSGI module, all IUA links must be
numbered universally. That is, one BSGI module supports a maximum of 32 IUA links.
[Linkset index]
This parameter specifies the IUA link set to which the IUA link belongs. This parameter
is defined in the ADD IUALKS command and referenced here.
plus the number of the PRA links actually borne over IUA link. This parameter can also
be the default value, 33. The actual number of streams received after an SCTP
1 plus the number of the PRA links actually borne over IUA link. This parameter can
also be the default value, 33. The actual number of streams transmitted after an SCTP
[Local port]
signaling gateway (UMG8900). This parameter specifies the SCTP port number used
for IUA messages at the SoftX3000 side. The configuration principles for this port
number are as follows:
z
If the SoftX3000 works as a server in the IUA link, it is recommended to set the
local SCTP port numbers for the several IUA links configured between the
SoftX3000 and an embedded signaling gateway to the same value.
If the SoftX3000 works as a client in the IUA link, the local port numbers for the
several IUA links configured between the SoftX3000 and an embedded signaling
gateway cannot be the same.

8-44

the embedded signaling gateway. It specifies the IP address of the FE port used for
dispatching IUA messages in the SoftX3000. This parameter is defined in the ADD
parameter.
[Peer port]
signaling gateway. This parameter specifies the SCTP port number used for IUA
messages at the embedded signaling gateway side. If the embedded signaling
gateway works as a server in the IUA link, from the point of view of the SoftX3000, the
peer port numbers for different IUA links can be the same. For example, if the
well-known port number for IUA is used at the embedded signaling gateway, the peer
port numbers for different IUA links at the SoftX3000 can be the default value, 9900.
the IUA link. By default, it is set to Client. If the SoftX3000 is set to Client, you must set
the embedded signaling gateway to Server, and conversely the same.
This parameter specifies the work state of the IUA link in normal cases. The
configuration of this parameter is closely related to the traffic mode of the link set.
z
In the override traffic mode, only one IUA link in the same link set is set to be active
and the other links are set to be standby.
In the loadshare traffic mode, all the IUA links in the same link set are set to be
active.
[Master/Slave flag]
8-45

follows:
z
8.6 Configuring MTP Data

8.6.1 Overview
MTP data defines MTP signaling related information for the SoftX3000 to interconnect
with SP, STP or SCP. MTP data includes destination signaling point code, signal circuit
number, signaling link code, and signaling link code send. To configure MTP data, the
equipment data, office data, media gateway data, and M2UA data (configured only
when the SS7 at the SoftX3000 is borne over M2UA) must have been configured. See
Figure 8-1.
you configure equipment data, media gateway data, and M2UA data will be referenced
during the configuration of MTP data, and some parameters defined here will be
referenced during the configuration of SCCP data and routing data. The referencing
referencing relationship between MTP data and other data, see Table 8-13.
Table 8-13 Parameter referencing relationship between MTP data and other data
Input parameter
Name
Output parameter
Defined in
Name
Referenced in
FCSU module number
Equipment
information
Destination signaling
point code
SCCP data and

routing data
Local
code
Office data
signaling
point

8-46

II. Preparations
Before configuring MTP data, make sure that all preparations are done as specified in
Table 8-14.
SN
Item
Remark
Destination
point code
signaling
One of the interconnection parameters between

the SoftX3000 and SP, STP or SCP.
STP flag

Signaling link code

Signaling link code send

Signal circuit number

the SoftX3000 and SP, STP or SCP (when the
SoftX3000 provides MTP links).
Integer interface ID

the SoftX3000 and SP, STP or SCP (when the
SoftX3000 provides M2UA links).

Table 8-15 lists the general steps for configuring MTP data.
Step
Description
Command
Add MTP destination signaling point
ADD N7DSP
Add MTP link set
ADD N7LKS
Add MTP link
ADD N7LNK
Add MTP route
ADD N7RT

you configure MTP data.

8-47

ADD N7DSP
[DSP index]
[Network indicator]
[DPC]
ADD M2LNK
[BSGI module
number]
[Link number]
ADD N7LKS
[SG ID]
[Linkset index]
[Adjacent DSP index]
ADD N7LNK
[FCCU/FCSU module
number]
[Link number]
[M2UA link number]
[Linkset index]
ADD N7RT
[Linkset index]
[DSP index]
[Route priority]
8.6.2 Adding MTP Destination Signaling Point

I. Related commands
Command
Function
ADD N7DSP
To add MTP destination signaling point
RMV N7DSP
To remove MTP destination signaling point
MOD N7DSP
To modify MTP destination signaling point
LST N7DSP
To list MTP destination signaling point

[DSP index]

8-48

The destination signaling point index uniquely identifies a destination signaling point.
The value range is 0 to 65534. The quantity of configured destination signaling points
depends on the number of the destination signaling point codes for SS7 signaling traffic
which is borne over MTP links and M2UA links. For example,
z
if the SoftX3000 interconnects with five end offices, one transit office, and two
SCPs through MTP links (not through STP), it is required to define eight
destination signaling points;
SCPs through MTP links (through two STPs), it is required to define ten
destination signaling points (including the STPs);
SCPs through M2UA links, it is required to define eight destination signaling
points.
[Network indicator]
the destination signaling point is resident. It may be the international network, the
international reserved network, the national network, or the national reserved network.
This parameter must be set according to the networking fact.
[DPC]
The destination signaling point code is one of the interconnection parameters between
the SoftX3000 and SP, STP or SCP, used to specify the signaling point code of the
destination signaling point in the SS7 signaling network.
[OPC]
The local signaling point code is one of the interconnection parameters between the
SoftX3000 and SP, STP or SCP, used to specify the originating signaling point code
corresponding to the destination signaling point. This parameter is defined in the SET
OFI or ADD OFI command and referenced here.
If you do not type OPC, the default OPC is the local signaling point code defined in
the command SET OFI.
[DSP name]
It identifies a DSP with a string of characters.
[STP flag]
This parameter specifies whether or not the destination signaling point is an STP. Set
this parameter to YES only when the destination signaling point is an STP actually.
[Adjacent flag]

8-49

This parameter specifies whether or not there is any associated MTP signaling route
between the SoftX3000 and the destination signaling point. Set this parameter by the
z
If what is interconnected with the local office is an associated STP, set this
parameter to YES.
If what is interconnected with the local office is an associated SP or SCP, set this
parameter to YES.
If what is interconnected with the local office is a quasi-associated SP or SCP

(That is, STP is needed to transfer signaling), set this parameter to NO.
[Linkset selection mask]

This parameter specifies how to share signaling traffic among the several MTP link sets
to the destination signaling point. Set this parameter by the following principles:
z
When there is only one link set between the SoftX3000 and the DSP, select the
default value B1111 for the link set selection mask.
When there are two or more than two link sets between the SoftX3000 and the
DSP, you must ensure that the decimal value of the link set selection mask is
bigger than or equals to the result of the total number of link sets minus 1. For
example, if the total number of link sets is 2, you cannot set the link set selection
mask to B0000.
[Signaling specification]
It indicates the organization who stipulates the SS7 applied between the local the
SoftX3000 and the DSP. By default, it is ITU-T. If the SoftX3000 interconnects with the
signaling point device complying with ANSI specifications, you must select ANSI;
otherwise, the MTP links between two signaling devices cannot work normally.
[Support TUP flag]
It indicates whether the STP or SP interconnected with the SoftX3000 supports TUP. By
default, it is Yes.
8.6.3 Adding MTP Link Set

I. Related commands
Command
ADD N7LKS
Function
To add MTP link set

8-50

Command
Function
RMV N7LKS
To remove MTP link set
MOD N7LKS
To modify MTP link set
LST N7LKS
To list MTP link set

[Linkset index]
The MTP link set index uniquely identifies an MTP link set. The value range is 0 to
65534. Because one link set is equivalent to a signaling route, only one MTP link set
can be configured between the local office (SoftX3000) and an adjacent destination
signaling point.
[Adjacent DSP index]
This parameter specifies the destination signaling point that has an associated
signaling route with the SoftX3000. This parameter is defined in the ADD N7DSP
command and referenced here in the following cases:
z
The destination signaling point index of the STP that is interconnected with the
local office in the associated mode.
The destination signaling point index of the SP or SCP that is interconnected with
the local office in the associated mode. (STP is not needed to transfer signaling.)
[Linkset name]
This parameter specifies how to share signaling traffic among the several MTP links in
one link set. Set this parameter by the following principles:
z
When there is only one link in a link set, select the default value B1111 for the link
selection mask.
When there are two or more than two links in a link set, you must ensure that the
decimal value of the link selection mask is bigger than or equals to the result of the
total number of links minus 1. For example, if the total number of links is 2, you
cannot set the link selection mask to B0000.

8-51

8.6.4 Adding MTP Link

I. Related commands
Command
Function
ADD N7LNK
To add MTP link
RMV N7LNK
To remove MTP link
MOD N7LNK
To modify MTP link
LST N7LNK
To list MTP link

Because the SoftX3000 can provide an MTP link in different ways, the appropriate type
of the link should be selected on the basis of the networking fact during the
configuration of MTP link data.
z
When the SoftX3000 provides an MTP link through E1 (borne over TDM), select
TDM 64kbit/s link or TDM 2Mbit/s link.
When the SoftX3000 provides an MTP link through an embedded signaling

gateway (borne over M2UA), select M2UA 64kbit/s link or M2UA 2Mbit/s link.

[FCSU/BSGI module number]
When the SoftX3000 provides an MTP link through E1 (borne over TDM), this
parameter specifies the module number of the FCSU that is processing the MTP link
protocol. When the SoftX3000 provides an MTP link through an embedded signaling
gateway (borne over M2UA), this parameter specifies the module number of the BSGI
that is processing the MTP link protocol. The module number is defined in the ADD
[Link number]
There are two cases to set the MTP link number:
1)
When the SoftX3000 provides an MTP link through E1 (borne over TDM), this
parameter specifies the physical number of the MTP link in the corresponding
FCSU module. One FCSU may be pinched with two CPC cards, and each CPC is
capable of processing sixteen (limited by the signaling link code) 64 kbit/s MTP
links or one 2 Mbit/s MTP link. Therefore, Set this parameter by the following
principles:
In the case of a 64 kbit/s MTP link, the range of the link number is 0 to 31, in which
0 to 15 are used for the upper CPC and 16 to 31 for the lower CPC.
8-52

z
In the case of a 2 Mbit/s MTP link, the link number can only be either 0 or 16, in
which 0 is used for the upper CPC and 16 for the lower CPC.
2)
When the SoftX3000 provides an MTP link through an embedded signaling

gateway (borne over M2UA), this parameter specifies the logical number of the
MTP link in the corresponding BSGI module. The numbering range is 0 to 31. In
the same BSGI module, all MTP links must be numbered universally. That is, one
BSGI module supports a maximum of 32 MTP links.
[Link name]
It identifies a link with a string of characters.
[Link type]
This parameter specifies the type of the MTP link. This parameter must be configured
according to the actual networking; otherwise, the MTP link cannot work. The meanings
of the parameter options are as follows:
z
TDM 64kbit/s link: 64 kbit/s MTP link that is carried over TDM. The SoftX3000
physically provides this kind of MTP link.
TDM 2Mbit/s link: 2 Mbit/s MTP link that is carried over TDM. The SoftX3000
physically provides this kind of MTP link.
M2UA 64kbit/s link: 64 kbit/s MTP link that is carried over M2UA. The embedded
signaling gateway (for example, TMG8010 or UMG8900) physically provides this
kind of MTP link.
M2UA 2Mbit/s link: 2 Mbit/s MTP link that is carried over M2UA. The embedded
signaling gateway (for example, TMG8010 or UMG8900) physically provides this
kind of MTP link.
[Start circuit number]

When the MTP link is borne over TDM, this parameter is available to specify the E1
time slot number occupied by the MTP link. Set this parameter by the following
principles:
z
Because the FCSU module number for processing the MTP link protocol has been
specified and there is one-to-one correspondence between the slot number of the
FCSU and the slot number of the EPII, the E1 slot to be occupied by this MTP link
can only be provided by the EPII (back board) with the same slot number as that of
the FCSU. One pair of EPIIs (in active/standby mode) can provide eight active E1
ports. The provided time slots are numbered together in the order from the time
slot 0 of the first E1. The numbering range is 0 to 255.
The MTP link is not allowed to occupy the time slot 0 (for synchronization usage)
of each E1. That is, the time slots 0, 32, 64, 96, 128, 160, 192 and 224 of the
preceding time slots are not available for MTP links.

8-53

z
In the case of a 64 kbit/s MTP link, if its link number is an integer from 0 to 15, the
available range for the start circuit number is 1 to 127; if its link number is an
integer from 16 to 31, the available range for the start circuit number is 128 to 255.
In the case of a 2 Mbit/s MTP link, if its link number is 0, the available start circuit
number can only be 1, 33, 65 or 97; if its link number is 16, the available start
circuit number can only be 129, 161, 193 or 225.
[Time slot number]

When the type of the link is set to TDM 2 Mbit/s, this parameter is available to specify
how many 64 kbit/s time slots are occupied by the 2 Mbit/s link. This parameter must be
set consistent with the opposite device. By default, it is 31.
When the SoftX3000 provides an MTP link through an embedded signaling gateway
(carried over M2UA), this parameter is available to specify the M2UA link set that is
used to carry the SS7 signaling traffic of the MTP link (considered as a logical link at the
SoftX3000 side). This parameter is defined in the ADD M2LKS command and
referenced here.
[Integer interface ID]
signaling gateway. When the SoftX3000 provides an MTP link through an embedded
signaling gateway (borne over M2UA), this parameter is available to uniquely identify
this MTP link from all MTP links that are borne over the M2UA link.
If an embedded signaling gateway provides several MTP links, the interface ID of an
MTP link cannot be the same as others despite their carrier which is either the same
M2UA link or not.
[Linkset index]
This parameter specifies the MTP link set to which the MTP link belongs. This
parameter is defined in the ADD N7LKS command and referenced here.
[Signalling link code]
The signaling link code is one of the interconnection parameters between the
SoftX3000 and SP, STP or SCP (in the associated mode), used to specify the logical
number of the MTP link in the MTP link set to which it belongs. As defined in the MTP
protocol specification, the 4-bit signaling link code is in the range from 0 to 15, and all
the signaling link codes for all the signaling links in the same link set must be numbered
uniquely and cannot be the same.
[Signalling link code send]

8-54

This parameter is used for the self-loop test between two MTP links of the local office.
The configuration principles are as follows:
z
When the self-loop test for MTP links is not enabled, the signaling link code send
and the signaling link code must be set to the same value; otherwise, signaling
interworking may not be achieved.
When the self-loop test for MTP links of the local office is enabled, the signaling
link code send and the signaling link code cannot be set the same. Meanwhile, the
signaling link code of the link 1 must equal the signaling link code send of the link 2
and the signaling link code of the link 2 must equal the signaling link code send of
the link 1.
[Link priority]
This parameter specifies the routing priority for the MTP link to convey signaling traffic.
A link with currently the highest priority is preferred. A link will be selected to convey
signaling traffic only after there are absolutely no available links with a higher priority
than it. The greater the value is, the lower the priority is. 0 indicates the highest priority.
[Satellite flag]
This parameter specifies whether or not the MTP link is borne over a satellite circuit.
This parameter must be set according to the actual situations. Generally, it is set to NO.
[Link congestion begin]
The unit for this parameter is %. Whenever the signaling traffic loaded on the MTP link
reaches this threshold, the SoftX3000 starts the congestion control automatically and
the MTP link will not be used to convey the traffic until the congestion is cancelled. By
default, it is 80.
[Link congestion end]
The unit for this parameter is %. Whenever the signaling traffic loaded on the MTP link
is reduced to this threshold, the SoftX3000 cancel the congestion control automatically
and the MTP link will be brought into service again. By default, it is 70.
[Test code], [Test code length]
These parameters are used for testing the MTP link only.
[Sending SLTM periodically]
It indicates whether the SoftX3000 sends Signaling Link Test Messages (SLTM) to the
peer STP or SP through the MTP link periodically. It is Yes by default.
[Master/Slave flag]

8-55

follows:
z
8.6.5 Adding MTP Route

I. Related commands
Command
Function
ADD N7RT
To add MTP route
RMV N7RT
To remove MTP route
MOD N7RT
To modify MTP route
LST N7RT
To list MTP route

[Linkset index]
This parameter specifies the MTP route toward the corresponding destination signaling
point, that is, through which MTP link set to convey signaling traffic. This parameter is
defined in the ADD N7LKS command and referenced here.
[DSP index]
This parameter specifies the destination signaling point the MTP route will be directed
to. This parameter is defined in the ADD N7DSP command and referenced here.
It should be noted that an MTP route is added, in this command, for all destination
signaling points defined in the ADD N7DSP command except STP.
[Route priority]
This parameter specifies the routing priority for the MTP link set (signaling route) to
convey signaling traffic. A link set with currently the highest priority is preferred. A link
set will be selected to convey signaling traffic only after there are absolutely no
available signaling routes with a higher priority than it. The greater the value is, the
8-56

[Route name]
It identifies an MTP route with a string of characters.
8.7 Configuring SCCP Data

8.7.1 Overview
SCCP data defines information related to SCCP addressing for interconnection
between the SoftX3000 and SCP, including SCCP destination signaling point, SCCP
subsystem, and global title. To configure SCCP data, the equipment data, office data,
MTP data (or M3UA data) must have been configured. See Figure 8-1.
you configure office data, MTP data, and M3UA data will be referenced during the
configuration of SCCP data, and some parameters defined here will be referenced
during the configuration of Intelligent Network (IN) service data. The referencing
referencing relationship between SCCP data and other data, see Table 8-16.
Table 8-16 Parameter referencing relationship between SCCP data and other data
Input parameter
Name
Output parameter
Defined in
Name
Referenced in
Local signaling
point code
Office data
SCCP destination signaling

point code
IN service data
Destination
signaling point code
MTP data or
M3UA data
SCCP subsystem number
IN service data
SCCP global title (optional)
IN service data
II. Preparations
Before configuring SCCP data, make sure that all preparations are done as specified in
Table 8-17.
SN
1
Item
Remark
SCCP destination signaling point

code

between the SoftX3000 and SCP

8-57

SN
Item
Remark



Table 8-18 lists the general steps for configuring SCCP data.
Step
Description
Command
Add SCCP destination signaling point
ADD SCCPDSP
Add SCCP subsystem
ADD SCCPSSN
Add SCCP new global title (optional)
ADD SCCPNGT
Add SCCP global title (optional)
ADD SCCPGT

you configure SCCP data.

8-58

ADD N7DSP
ADD SCCPDSP
[DSP index]
[DSP index]
[NI]
[NI]
[DPC]
[DPC]
or
ADD M 3DE
ADD SCCPSSN
[SSN index]
[SSN]
[Destination entity point

code]
[SPC]
ADD SCCPNGT
[New GT index]
[GT indicator]
[Translation type]
ADD SCCPGT
[GT index]
[SSN]
[SPC]
[New GT index]
8.7.2 Adding SCCP Destination Signaling Point

I. Related commands
Command
Function
ADD SCCPDSP
To add SCCP destination signaling point
RMV SCCPDSP
To remove SCCP destination signaling point
MOD SCCPDSP
To modify SCCP destination signaling point
LST SCCPDSP
To list SCCP destination signaling point

8-59


[DSP index]
The SCCP destination signaling point index uniquely identifies an SCCP destination
signaling point. The value range is 0 to 511.
The DSP index here is different from the destination signaling point index defined in the
ADD N7DSP command or the destination entity index defined in the ADD M3DE
command. They are different parameters and have no referencing relationship with
each other.
[Network indicator]
the SCCP destination signaling point is resident. It may be the international network,
the international reserved network, the national network, or the national reserved
network. This parameter must be set according to the networking fact.
[DPC]
This is one of the interconnection parameters between the SoftX3000 and SCP. That is,
the SCCP destination signaling point code (the signaling point code of the SCP). This
parameter is defined in the ADD N7DSP or ADD M3DE command and referenced
here.
[OPC]
This is one of the interconnection parameters between the SoftX3000 and SCP. That is,
the SCCP local signaling point code (the signaling point code of the SoftX3000). This
parameter is defined in the SET OFI command and referenced here.
Although the SoftX3000 supports multi-siganling-point-code, it is not recommended to
use the command ADD OFI to define the local signaling point code in the SCCP
destination signaling point code table.
[Load sharing function flag]
This parameter specifies whether or not the SoftX3000 supports the load sharing or
standby function of the SCCP destination signaling point. The meanings of the options
are as follows:
z
No standby DSP: By default, no standby function is supported.
Backup DSP: The active/standby function is supported. That is, when an SCCP
DSP is unreachable, the local office sends the signaling messages to its standby
SCCP DSP.
Loadshare DSP: The load sharing function is supported. That is, the signaling
messages sent by the local office to an SCCP DSP are shared by the two SCCP
DSPs.
8-60

[Standby DSP index]

When the SoftX3000 supports the load sharing or standby function of the SCCP
destination signaling point, this parameter is available to specify the standby SCCP
destination signaling point. Because this parameter involves an invocation to another
SCCP destination signaling point data table, what is specified in this parameter must
have been defined in that SCCP destination signaling point data table. It is
recommended to first define all the SCCP destination signaling points in the ADD
SCCPDSP command and then modify this parameter in the MOD SCCPDSP
command.
8.7.3 Adding SCCP Subsystem

I. Related commands
Command
Function
ADD SCCPSSN
To add SCCP subsystem
RMV SCCPSSN
To remove SCCP subsystem
MOD SCCPSSN
To modify SCCP subsystem
LST SCCPSSN
To list SCCP subsystem

[SSN index]
The subsystem number index uniquely identifies a local subsystem of the SCCP. The
value range is 0 to 1023.
[Network indicator]
The network indicator specifies the signaling network where the SCCP subsystem is
resident. It may be the international network, the international reserved network, the
national network, or the national reserved network. This parameter must be set
according to the networking fact. Generally, set it to National network.
[SSN]
This parameter specifies the subsystem number carried in the local SCCP messages to
be delivered to the SCCP destination signaling point. For fixed IN services, you need to
set two subsystem numbers:
z
SCMG: used to manage the various states of the SCCP.
INAP or BSSAP/INAP: used to deliver INAP messages to the upper layer. The
configuration of this code must be negotiated with the interconnected SCP.
8-61

Generally, select INAP (Intelligent net application part 0x0C) if what is

interconnected is an SCP developed by Huawei; select INAP or BSSAP/INAP (A
Interface/INAP 0xFE) if what is interconnected is an SCP provided by other
vendor.
[SPC]
This parameter specifies the destination signaling point code of the corresponding
subsystem (the local receiver of SCCP messages). For each subsystem, you must
define two destination signaling points:
z
SCCP destination signaling point, defined in the ADD SCCPDSP command;
Local signaling point, defined in the SET OFI or ADD OFI command.
[OPC]
This parameter specifies the originating signaling point code of the corresponding
subsystem (the local transmitter of SCCP messages). For each subsystem, this
originating signaling point code is the local signaling point code. This parameter is
defined in the SET OFI or ADD OFI command and referenced here.
Caution:
According to the preceding description, to interconnect with an SCP (it is assumed that
the SCP is provided by Huawei), four pieces of SCCP subsystem data should be
configured in the SoftX3000 for the same SCCP destination signaling point. Supposing
the local signaling point code is 001130 and the SCCP destination signaling point code
is 001260, the corresponding configuration scripts are as follows:
z
ADD SCCPSSN: SSNX=0, NI=NN, SSN=SCMG, SPC="001130", OPC="001130";
ADD SCCPSSN: SSNX=1, NI=NN, SSN=INAP, SPC="001130", OPC="001130";
ADD SCCPSSN: SSNX=2, NI=NN, SSN=SCMG, SPC="001260", OPC="001130";
ADD SCCPSSN: SSNX=3, NI=NN, SSN=INAP, SPC="001260", OPC="001130";
[Local concerned SSN1] to [Local concerned SSN5]

These parameters are used to specify the local subsystems associated with the SCCP.
For IN services, you dont have to configure these parameters.
[Backup SSN index]
When the SoftX3000 supports the load sharing or standby function of the SCCP
destination signaling point, this parameter is available to specify the standby
subsystem of the SCCP. Because this parameter involves an invocation to another
SCCP subsystem data table, what is specified in this parameter must have been
8-62

defined in that SCCP subsystem data table. It is recommended to first define all the
SCCP subsystems in the ADD SCCPSSN command and then modify this parameter in
the MOD SCCPSSN command.
If the IN does not support or does not provide the standby subsystem function, set this
parameter to 65535 (indicating the disability of the function).
[SSN name]
It identifies an SCCP subsystem with a string of characters.
8.7.4 Adding SCCP New Global Title (Optional)

I. Related commands
Command
Function
ADD SCCPNGT
To add SCCP new global title
RMV SCCPNGT
To remove SCCP new global title
MOD SCCPNGT
To modify SCCP new global title
LST SCCPNGT
To list SCCP new global title

data configuration.
When you add a global title by using the ADD SCCPGT command, if the type of the
translation result is DPC + NEW GT, the new global title must have been defined in
the ADD SCCPNGT command.

[New GT index]
The new GT index uniquely identifies a new global title. The value range is 0 to 4095.
[GT indicator]
The global title indicator specifies the type of the new global title. It may be Type 1, Type
2, Type 3, and Type 4. In an intelligent network, select Type 4.
[Translation type]
This parameter specifies the translation function used for the new global title. Currently,
it is not used and thus set it to 00.
8-63

[Numbering plan]
This parameter specifies the numbering plan used for the new global title. In an
intelligent network, select ISDN/telephony numbering plan.
[Nature of address indicator]
This parameter specifies the nature of address of the new global title. In an intelligent
network, select International number.
[GT address information]
This parameter defines the value of the new global title, that is, the specific address
signal.
8.7.5 Adding SCCP Global Title (Optional)

I. Related commands
Command
Function
ADD SCCPGT
To add SCCP global title
RMV SCCPGT
To remove SCCP global title
MOD SCCPGT
To modify SCCP global title
LST SCCPGT
To list SCCP global title

data configuration.
In an SCCP message, the DPC, SSN and GT fields in the called address parameter
are used for the addressing of the SCCP message. To interconnect the SoftX3000 with
an SCP, these fields must be negotiated with the opposite device.
z
If the SCP uses signaling point code format as its physical address, the DPC and
SSN fields are enough to achieve the addressing function of the SCCP messages,
and thus global title is not needed.
If the SCP uses global title format as its physical address, global title must be
added in the SoftX3000 in the ADD SCCPGT command.

[GT index]
The GT index uniquely identifies a global title. The value range is 0 to 4095.
8-64

[GT name]
It identifies a global title with a string of characters.
[Network indicator]
the local SCCP is resident. It may be the international network, the international
parameter must be set the same as the network indicator pertaining to the signaling
point code in the local office information table.
[GT indicator]
The global title indicator specifies the type of the global title. It may be Type 1, Type 2,
Type 3, and Type 4. In an intelligent network, select Type 4.
[Translation type]
This parameter specifies the translation function used for the global title. Currently, it is
not used and thus set it to 00.
[Numbering plan]
This parameter specifies the numbering plan used for the global title. In an intelligent
network, select ISDN/telephony numbering plan.
This parameter specifies the nature of address of the global title. In an intelligent
network, select International number.
This parameter defines the value of the global title, that is, the specific address signal.
According to the preceding default configuration principles, the global title address is
composed of the country code, the long-distance area code, and the subscriber
number. For example, a global title is 8675528970132, in which 86 is the country code,
755 is the long-distance area code, and 28970132 is the subscriber number.
[Translation result type]
This parameter specifies to which type the local SCCP translates the content of the
global title. The available types are different combinations of SPC, SSN and GT. There
are totally four types:
z
STP1: DPC + OLD GT
LSPC1: DPC + SSN
STP2: DPC + NEW GT
LSPC2: DPC

8-65

[SSN]
When the translation result type is DPC + SSN, this parameter must be entered to
specify the subsystem number in the translation result. This parameter is defined in the
ADD SCCPSSN command and referenced here.
[SPC]
This parameter specifies the SCCP destination signaling point code in the translation
result. This parameter is defined in the ADD SCCPDSP command and referenced
here.
[New GT index]
When the translation result type is DPC + NEW GT, this parameter must be entered to
specify the new global title in the translation result. This parameter is defined in the
ADD SCCPNGT command and referenced here.
8.8 Configuring V5 Interface Data

8.8.1 Overview
V5 interface data defines V5.1 or V5.2 interface information for interconnection
between the SoftX3000 and a variety of V5 devices such as access network device and
base station controller. V5 interface data includes V5 interface identifier, primary link
circuit number, secondary link circuit number, and V5 interface variant. To configure V5
interface data, the equipment data, media gateway data, V5UA data, and V5 trunk data
must have been configured. See Figure 8-1.
you configure equipment data and V5 trunk data will be referenced during the
configuration of V5 interface data, and some parameters defined here will be
referenced during the configuration of subscriber data. The referencing relationship is
presented as the broken lines in Figure 8-1. For the parameter referencing relationship
between V5 interface data and other data, see Table 8-19.
Table 8-19 Parameter referencing relationship between V5 interface data and other
data
Input parameter
Name
Output parameter
Defined in
FCCU
or
FCSU
module number
Equipment
information
Name
V5 interface identifier

8-66
Referenced in
Subscriber data

Input parameter
Output parameter
Name
Defined in
V5 trunk group number
V5 trunk data
Name
/
Referenced in
/
II. Preparations
Before configuring V5 interface data, make sure that all preparations are done as
SN
Item
Remark
V5 interface type

SoftX3000 and a variety of V5 access network devices
V5 interface
identifier

Primary link circuit

number
This is a logical number assigned inside the SoftX3000

to an E1 time slot in the V5 trunk group. The
corresponding physical number assigned inside the
access media gateway is specified in the "start E1
identifier of MG parameter.
Termination
identifier of primary
link circuit number

SoftX3000 and an access media gateway
Identifier of logical
C-channel on
primary link

Protection
type

group
Secondary link
circuit number
This is a logical number assigned inside the SoftX3000

to an E1 time slot in the V5 trunk group. The
corresponding physical number assigned inside
UMG8900 is specified in the "start E1 identifier of MG
parameter.
Termination
identifier of
secondary link
circuit number

SoftX3000 and UMG8900
Circuit number of
physical C-channel
for PSTN (optional)
Ensure the correct correspondence with the circuit

number of the physical C-channel for the PSTN in the
V5 access network device.
10
Identifier of PSTN
logical C-channel
(optional)


8-67

SN
Item
Remark
11
V5 interface variant
(optional)


Table 8-21 lists the general steps for configuring V5 interface data.
Step
Description
Command
1:
Add V5 interface
ADD V5I
Add V5 variant (optional)
ADD V5VAR

you configure V5 interface data.
ADD V5TG
[Trunk group number]
[Equipment ID]
[Trunk group name]
ADD V5I
[Module number]
[V5 interface ID]
[V5 variant number]
ADD V5VAR
[V5 interface ID]
[V5 variant number]
[New V5 interface ID]

8-68

8.8.2 Adding V5 Interface

I. Related commands
Command
Function
ADD V5I
To add V5 interface
RMV V5I
To remove V5 interface
MOD V5I
To modify V5 interface
LST V5I
To list V5 interface

[V5 interface ID]
The V5 interface identifier is one of the interconnection parameters between the
SoftX3000 and V5 access network device, used to uniquely identify a V5 interface
between the LE and the AN. In the SoftX3000, V5 interface identifiers are numbered
universally. That is, the same interface identifier cannot be shared by several V5
interfaces. The value range is 0 to 16777215.
This parameter specifies the V5 trunk group to which the E1 port(s) controlled by the V5
interface belongs. (A V5.1 interface controls one E1; a V5.2 interface controls a
maximum of sixteen E1s.) This parameter is defined in the ADD V5TG command and
referenced here.
[Primary link circuit number]
This parameter specifies the E1 time slot of the V5 trunk group that will be occupied by
the physical C-channel on the primary link in the V5 interface. Set this parameter by the
z
This is a logical number assigned inside the SoftX3000 to an E1 time slot in the V5
trunk group. The corresponding physical number assigned inside the access
media gateway is specified in the "start E1 identifier of MG parameter.
This circuit number must be the time slot 16 of an E1.
This circuit number must be in the range of the E1 time slot numbers defined in the
ADD V5TKC command.
This parameter must be negotiated with the AN side before the configuration, to
ensure that the circuit numbers at both ends are the same time slot physically.
[Primary link logical C-channel ID]

8-69

This is one of the interconnection parameters between the SoftX3000 and V5 access
network device, used to uniquely identify a primary link between the LE and the AN.
The value range is 0 to 65534. Set this parameter by the following principles:
z
When the protection group 1 is used, the logical C-channel identifier of the primary
link must be set to the same value as the logical C-channel identifier for the PSTN.
link must be numbered universally with the logical C-channel identifier for the
PSTN. They cannot be the same.
[Interface usage flags]

This parameter specifies whether or not to start the link check function for the V5
interface in appropriate conditions. By default, it is ALL FALSE, indicating that the link
check function is not started. The meanings of the start conditions are as follows:
z
Timer start: Support outband calling number presentation.
Start it when restarted: Start the link check when the link is restarted.
Start it when resigned: Start the link check when the link is re-provisioned.
Start it when recover from fault: Start the link check when the link is recovered from
a fault.
[Interface type]
network device, used to specify the protocol type of the V5 interface, that is, either V5.1
protocol or V5.2 protocol. By default, it is V5.2 Interface.
[Protect group type]
network device, used to specify the protection mode to be used by the V5 interface.
The meanings of the options are as follows:
z
No protection: No protection mechanism is provided.
Protect group 1: The protection group is only composed of the time slot 16 of
primary and secondary links. The primary and secondary links are structured in
the 1+1 backup mode. That is, the secondary link is the standby C-channel of the
primary link. By default, the system employs the protect group 1.
Protect group 2: The protection group includes not only the time slot 16 of the
primary and secondary links, but also includes N (1 N 43 45) logical
C-channels and K (1 K 3) standby C-channels. The primary and secondary links
are structured in the 1+1 backup mode, and the N logical C-channels and K
standby C-channels in the N+K backup mode.
[Secondary link circuit number]

8-70

the physical C-channel on the secondary link in the V5 interface (that must be a V5.2
interface). Set this parameter by the following principles:
z
If it is a V5.1 interface, this parameter is not configured.
This is a logical number assigned inside the SoftX3000 to an E1 time slot in the V5
trunk group. The corresponding physical number assigned inside UMG8900 is
specified in the "start E1 identifier of MG parameter.
This circuit number must be the time slot 16 of an E1.
ADD V5TKC command.
[PSTN link circuit number]

the physical C-channel, bearing the PSTN protocol, in the V5 interface. This parameter
is optional. If it is not configured, the PSTN protocol is borne over the physical
C-channel on the primary link; if it is configured, the PSTN protocol is borne over the
physical C-channel specified here. Set this parameter by the following principles:
z
If it is a V5.1 interface, this parameter is not configured.
If the physical C-channel for the PSTN protocol is configured specifically, the
protect group 2 must be selected as the protection group type, and at least one
standby C-channel for the protection group 2 is defined necessarily.
This circuit number can be the time slot 15, 16 or 31 of an E1, but it cannot conflict
with the primary link circuit number or the secondary link circuit number.
ADD V5TKC command.
[PSTN logical C-channel ID]

z
This is one of the interconnection parameters between the SoftX3000 and V5

access network device, used to uniquely identify a physical C-channel for the
PSTN between the LE and the AN. The value range is 0 to 65534. Set this
parameter by the following principles: When the protection group 1 is used, the
logical C-channel identifier of the primary link must be set to the same value as the
logical C-channel identifier for the PSTN.
link must be numbered universally with the logical C-channel identifier for the
PSTN. They cannot be the same.
[PG2 standby C-channel 1 circuit number]

8-71

The circuit number for the standby C-channel 1 of the protection group 2 is available to
be specified only when protect group 2 is selected as the protection group type. It is
one of the interconnection parameters between the SoftX3000 and V5 access network
device, used to define the first standby C-channel of the K (1 K 3) standby
C-channels.
device, used to define the second standby C-channel of the K (1 K 3) standby
C-channels.
device, used to define the third standby C-channel of the K (1 K 3) standby
C-channels.
[V5 variant number]
network device, used to define the V5 variant (also known as V5 variant) number used
during an initialization process. The value range is 0 to 127. Generally, set it to 0.
[ETSI CLIP]
It indicates whether a V5 interface supports the CLIP function defined by ETSI. It is not
supported by default.
8.8.3 Adding V5 Variant (Optional)

I. Related commands
Command
Function
ADD V5VAR
To add V5 variant
RMV V5VAR
To remove V5 variant
MOD V5VAR
To modify V5 variant
LST V5VAR
To list V5 variant

8-72


data configuration.
Generally, V5 variant is seldom used in an actual deployment. When it is required to
re-specify information like a new interface identifier for a V5 interface, V5 variant is
necessarily added in the ADD V5VAR command.

[V5 interface ID]
This parameter specifies the V5 interface identifier for which the V5 variant is
necessarily added. This parameter is defined in the ADD V5I command and referenced
here.
[V5 variant number]
This parameter defines the V5 variant number for the V5 variant to be added.
[New V5 interface ID]
network device, used to define the new interface identifier for the V5 interface after
re-provisioning. This new interface identifier is numbered universally with the other V5
interface identifiers already defined in the database and thus cannot be repeated. The
value range is 0 to 16777215.
[Device type of region 1] to [Device type of region 3]
These parameters specify the device types supported in the various provisioning
regions. PSTN indicates analog subscriber line interface; BRA indicates digital
subscriber line interface; PRA indicates 30B + D subscriber interface; and DCN
indicates digital console interface.
[Start device number of region 1] to [Start device number of region 3]
These parameters specify the start logical device number for valid V5 user ports in
each provisioning region. The value range is 0 to 8191.
[Continuous device quantity of region 1] to [Continuous device quantity of region 3]
These parameters specify the quantity of valid V5 user ports in each provisioning
region. The value range is 1 to 2000.

8-73

8.9 Configuring PRA Link Data

8.9.1 Overview
PRA link data defines information related to DSS1 signaling for interconnection
between the SoftX3000 and Network Access Server (NAS), Private Branch Exchange
(PBX) or IP Front End Processor. PRA link data includes interface identifier, signaling
type, and signaling link circuit number. To configure PRA link data, the equipment data,
media gateway data, and IUA data must have been configured. See Figure 8-1.
you configure equipment data and IUA data will be referenced during the configuration
of PRA link data, and some parameters defined here will be referenced during the
configuration of PRA trunk data. The referencing relationship is presented as the
broken lines in Figure 8-1. For the parameter referencing relationship between PRA link
data and other data, see Table 8-22.
Table 8-22 Parameter referencing relationship between PRA link data and other data
Input parameter
Name
Output parameter
Defined in
Name
Referenced in
FCCU or FCSU
module number
PRA link number
PRA trunk data
IUA link set index
IUA data
Number change
index (optional)
II. Preparations
Before configuring PRA link data, make sure that all preparations are done as specified
in Table 8-23.
SN
Item
Remark
Integer interface ID
Text
interface
(optional)

ID


8-74

SN
Item
Remark
Network check flag

SoftX3000 and NAS or PBX.
Signal circuit number

Length of the CR Value

field in Q.931 call
messages (optional)


Table 8-24 lists the general steps for configuring PRA link data.
Step
Description
Add PRA link
Command
ADD PRALNK

you configure PRA link data.
ADD IUALKS
[LinkSet index]
[Traffic mode]
[SG ID]
ADD PRALNK
[Link number]
[Module number]
[IUA linkset index]

8-75

8.9.2 Adding PRA Link

I. Related commands
Command
Function
ADD PRALNK
To add PRA link
MOD PRALNK
To remove PRA link
RMV PRALNK
To modify PRA link
LST PRALNK
To list PRA link

[Link number]
This parameter specifies the logical number of the PRA link in the corresponding FCCU
or FCSU module. The default value range is 0 to 999. In the same FCCU or FCSU
module, all PRA links must be numbered universally. That is, one FCCU or FCSU
module supports a maximum of 1000 PRA links.
If you operators want to widen the value range of the PRA signaling link, please contact
Huawei for help and execute the command MOD MAXT to modify the value range
under the instructions of Huawei experts.
[Signal circuit number]
This parameter specifies the E1 time slot of the PRA trunk group that will be occupied
by the PRA link. The configuration principles for this parameter are as follows:
z
This is a unique logical number assigned inside the SoftX3000 to a trunk circuit of
SS7, PRA or R2. The corresponding physical number inside the trunk media
gateway is specified in the start circuit termination identifier parameter.
As defined in the DSS1 signaling, this circuit number can only be the time slot 16
of an E1.

This parameter specifies the module number of the FCCU or FCSU to process the PRA
link protocol. This parameter is defined in the ADD BRD command and referenced
here.
command ADD MGW for adding the embedded IUA SG; otherwise, the PRA subscriber
terminals connected to this MGW cannot work normally.
[IUA linkset index]

8-76

This parameter specifies the IUA link set that bears the PRA link (That is, the signaling
link carrying the D-channel signaling messages of the PRA subscribers). This
parameter is defined in the ADD IUALKS command and referenced here.
[Integer interface ID]
embedded signaling gateway supporting IUA, used to uniquely identify this PRA link
from all the D-channel signaling messages of the PRA subscribers that are borne over
the IUA link set. The SoftX3000 supports both integer interface ID and text interface ID.
In the actual applications, the integer interface ID is preferred.
[Text interface ID]
embedded signaling gateway supporting IUA, used to uniquely identify this PRA link
from all the D-channel signaling messages of the PRA subscribers that are borne over
the IUA link set. The SoftX3000 supports both integer interface ID and text interface ID.
In the actual applications, the integer interface ID is preferred.
[Signaling type]
This is one of the interconnection parameters between the SoftX3000 and PRA device,
used to identify the application mode of the local end in the PRA link. By default, it is
DSS1 Network Side.
In the actual applications, the SoftX3000 generally provides PRA link through TMG or
UMG. You must observe the following configuration guidance to set the PRA signaling
type at the SoftX3000, TMG, and the peer end PRA device:
z
Regard the SoftX3000 and TMG as a unit. Set the same signaling typeDSS1
network side or DSS1 subscriber side for the SoftX3000 and the TMG.
The signaling type of the local end must not be the same as the peer end. If the
local end is DSS1 network side, the opposite end must be DSS1 subscriber
side, and it is the same case conversely.
[Outgoing CR length]
This is one of the interconnection between the SoftX3000 and PRA device, used to
specify the length of the CR Value field, in bytes, in Q.931 call messages. By default,
it is 2, indicating the field has two bytes. This parameter is used to adapt PRA devices
provided by different vendors. It should be set to 1 when applied in certain countries.
[Caller number check mode]
This parameter is valid only to incoming trunks. It indicates whether the SoftX3000
performs a validity check to the caller number of an incoming call originated by the peer
PRA device (for example, PBX) through a PRA link so as to determine the calling
number for call connection.
8-77

1)
If the calling number sent by the peer office is not a PRA subscriber number
defined in the local office, that is, if the received number cannot be found in the
PRA subscriber number data table of the local office, the calling number is invalid.
2)
If the following conditions are met, the received calling number is valid; otherwise,
the received calling number is invalid.
The calling number sent by the peer office is a PRA subscriber number defined in
the local office, that is, the received number can be found in the PRA subscriber
number data table of the local office.
The route selection code used by the PRA subscriber is one of the the route
selection codes pre-defined for the default calling numbers of several (one to five)
PRA trunk groups controlled by PRA signaling links.
The setting of this parameter affects charging, for the calling number used here is the
one in a bill. Set this parameter by the following principles:
z
Allow all: It means that no validity check will be performed. If not receiving the
calling number from the peer office, the local office will use the default calling
number on the PRA trunk group as the one for the call. If receiving the calling
number from the peer office, the local office will use it as the calling number of the
call (that is, the local office transmits all numbers from the peer office
transparently). To enable the transparent transmission, you need to execute MOD
FSFP to set bit 10 of internal call parameter 3 (P51) to 0.
Allow national number: It means that no validity check will be performed. If no

calling number is received from the peer office or the address nature of the calling
number sent by the peer office is not a national number, the local office will use the
default calling number on the PRA trunk group as the one for the call. If the calling
number is received from the peer office and the address nature of the calling
number is a national number, the local office will use this number as the calling
number for the call (that is, the local office will transmit the national number from
the peer office transparently).
Use default number: It means that validity check will be performed. If not receiving
the calling number from the peer office, the local office will use the default calling
number on the PRA trunk group as the one for the call. If receiving the calling
number from the peer office, the local office will first judge the validity of the calling
number. If the calling number is valid, the local office will use it as the calling
number for the call; otherwise, the local office will use the default calling number
on the PRA trunk group as the one for the call.
Reject invalid number: It means that validity check will be performed. If not
receiving the calling number from the peer office, the local office will use the
default calling number on the PRA trunk group as the one for the call. If receiving
the calling number from the peer office, the local office will first judge the validity of
the calling number. If the calling number is valid, the local office will use it as the
calling number for the call; otherwise, the local office will reject the call.
[Caller number change index]

8-78

When it is required to change the caller number of a call on the PRA link, this parameter
is available to specify the caller number change index. This change index is defined in
the ADD DNC command and referenced here. By default, it is set to 0, indicating not
to change.

8-79

Chapter 9 Configuring Routing Data

9.1.1 Office Direction, Sub-route and Route
Figure 9-1 shows the trunk networking between office A and office B, where the real
lines indicate the voice channels, and the broken lines indicate the signaling channels.
STP
Subroute 1
Office A
Office B
Subroute 2
Office C
Office D
Figure 9-1 Trunk networking
I. Office direction
If two offices have direct voice path, one office is called the office direction of the other.
For example, there are direct voice channels between office A and office B, and
between office A and office C as shown in Figure 9-1, so office B is an office direction of
office A and office C is an office direction of office C. In addition, because there is no
direct voice channel between office A and office D, office D is not an office direction of
office A.
In the SoftX3000, office direction number is used to uniquely identify an office direction.
For example, for office direction A in Figure 9-1, the office direction from A to B can be
assigned with 1 and the office direction from A to C can be 2.

9-1

II. Sub-route
If there is a direct voice channel or an alternative channel between two offices, we say
there is a sub-route between the two offices. The direct voice channel is the direct
sub-route and the alternative channel is the alternative sub-route. For example, there
are two sub-routes between office A and office B shown in Figure 9-1, where sub-route
1 is direct from office A to office B and it is the direct sub-route, and sub-route 2 is from
office A to office B through office and it is the alternative sub-route.
III. Route
A route is a set of all sub-routes from local office to a destination office. A router
contains multiple sub-routes and different routes may contain the same sub-routes. For
example, the route from office A to office B shown in Figure 9-1 contains sub-route 1
and sub-route 2, while the route from office A to office D only contains sub-route 2.
9.1.2 Route Selection Source Code and Route Selection Code

I. Route selection source code
The route selection source code is a parameter defined when the ADD CALLSRC
command is used to add call source. It distinguishes the outgoing route selection policy
of the calling subscribers with different call sources. The policies include whether to
dynamically select route based on time segment, which kind of trunk is selected
preferably as the outgoing route, whether it is possible to use all sub-routes and the
trunk group selection policies.
II. Route selection code

The route selection code is a parameter referenced when the ADD CNACLD command
is used to add outgoing call prefix. It distinguishes the outgoing route selection policies
of different call prefixes.
Based on the above description, the route selection source code is closely related to
the attributes of call source (caller), and the route selection code is closely related to
the attributes of call prefix (callee). These two concepts are different and you must
make clear of them.
9.1.3 Route Analysis Process

The route analysis involved in the SoftX3000 is implemented through querying and
analyzing the data tables in the SoftX3000 database, as shown in Figure 9-2.

9-2

Call prefix table
ADD CNACLD
Route analysis
table
ADD RTANA
Routing table
Subroute table
Trunk group
table
ADD RT
ADD SRT
ADD N7TG / ADD SIPTG
Figure 9-2 SoftX3000 route analysis process

With the outgoing call of a local subscriber as example, the basic process of route
analysis is described as follows.
When you define the outgoing call prefix, it is required to specify the corresponding
route selection code for the purpose to indicate the route selection policy used by the
system to query the outgoing call.
The system queries the corresponding route analysis table through the route selection
code. The route analysis table, through the judgment on the route selection source
code, calling subscriber category, address information indicator, transmission capability
and time, decides whether the call is permitted to use the route and which route is used.
If the authentication is passed, the system can finally obtain the number of a route.
The system then queries the corresponding routing table through the route number.
The routing table, through the predefined sub-route selection policy (sequence-based
or percentage-based), determines which sub-route is used for the call and obtains the
sub-route number.
After that, the system queries the corresponding sub-route table through the sub-route
number. The sub-route table, through the predefined trunk group selection policy
(cyclic or random), determines which trunk group is used for the call and obtains the
trunk group number.
By now, the route analysis process has finished, and the system continues to query the
corresponding trunk, signaling data table and finally determines which trunk circuit and
signaling link are used for the outgoing call.

9-3

9.1.4 Hierarchical Route Networking in NGN

I. Reason for Deploying Hierarchical Route Networking
It is essential to optimize the route among switching nodes before telecom carriers can
roll out their business and services. When there are rather few switching nodes in a
network, telecom carriers tend to use mesh topology, in which there is always a direct
route between any two nodes. However, when the number of nodes reaches a certain
level, the route data configured at every node becomes so huge and complicated that it
is extremely difficult to maintain all the routes in the network. When one node has
modified its route data, all the other node shall be informed to make relevant changes,
which greatly reduces the operability and maintainability of the network.
II. Overview of Hierarchical Route Networking

To improve the operability and maintainability of the telecom networks, a hierarchical
route network is introduced by setting necessary tandem and toll exchanges to manage
inter-nodal routes. A packet-switched NGN network separates the call control and
bearer, which enables the separation of routing features from the softswitch. Observing
the GK-GW architecture in an H.323 network, carriers can deploy a dedicated routing
device in NGN to achieve hierarchical routing. Such routing device is known as local
server, which provides similar functions as the GK in an H.323 network.
III. Benefits of Hierarchical Route Networking

It simplifies route data configuration in softswitches in each IP telephony administration
domain (IPTD), which
z
Greatly facilitating the routine maintenance of route information.
Eliminating bottleneck of rout-processing capability of softswitch in a

pure-softswitch, large-scale network.
It separates route data from softswitch, which

z
Boosting the processing capability of softswitch.
Safeguarding the synchronization of route data in the network.
Facilitating a universal management of all routes in the network.
Effectively diminishing the congestion and call losses caused by routing problems.
It introduces the location server, which

z
Ensuring a high efficiency of processing route data.
Meeting the requirements of a large-scale network.
Simplifying the domain dividing and management of NGN.
Facilitating the maintenance of network.

9-4

IV. A Typical Networking Solution of Hierarchical Route Networking

Figure 9-3 shows a typical networking solution of hierarchical route networking based
on Huawei U-SYS NGN.
ITAD-A
SX
ITAD-B
TGREP/
SIP
TGREP/
SIP
TRIP
TGREP/SIP
SX
TGREP/SIP
LS-B
LS-A
SX-A
SX
IP
TGREP/
SIP
TRIP
SX
TGREP/
SIP
TRIP
SX-B
ITAD-C
LS
TGREP/
SIP
Subsriber A
TGREP/
SIP
Subscriber B
TGREP/
SIP
SX
SX
SX
SX: Soft Switch (SoftX3000)

TRIP: Telephone Route Information Protocol
LS: Location Server
TGREP: Telephony Gateway Registration Protocol
ITAD: IP Telephony Administration Domain
SIP: Session Initiation Protocol
Figure 9-3 A typical network solution of hierarchical route networking in NGN

As shown in Figure 9-3, a geographical area (usually a local network), containing
several softswitches, is set to an ITAD. In each ITAD, a pair of location servers working
in active/standby mode is configured. The softswitches communicate with location
servers through TGREP and SIP within an ITAD. ITADs communicate with each other
through TRIP.
z
TGREP: Used by the softswitch to inform the route updates to the location server.
When an operator modifies the route information, the softswitch will immediate
send a TGREP message to the location server to update the route information in
the latter.
SIP: Used by the softswitch to query route information in the location server.
TRIP: Used between location servers to dynamically sharing route updates. When
the route information is updated in a certain location server, it will send TRIP
messages to other location servers to update their route information.
9-5

V. Route analysis procedure of Hierarchical Route Networking

Here is the route analysis procedure of a subscriber A in ITAD-A calling subscriber B in
ITAD-B, as shown in Figure 9-3.
1)
Subscriber A in ITAD-A initiates a call. The called number is subscriber B in

ITAD-B.
2)
SX-A analyzes the number, finds that the subscriber B is of another softswitch,
and sends a SIP message INVITE to LS-A, asking for the route from SX-A to
subscriber B.
3)
After route analysis, LS-A finds that SX-A needs to connect subscriber through
SX-B, and returns a 302 response message containing the IP address, protocol
type, and port number of SX-B.
4)
When SX-A obtains the IP address and port number of SX-B, it starts the call
through SIP (assume that SIP is the protocol using in SX-B).
5)
When SX-B receives the request from SX-A, it analyzes the called number, finds
that subscriber B is in the local office, and starts calling subscriber B.
6)
After subscriber B picks up, the conversation begins between the two subscribers.
9.2 Configuring Routing Data

9.2.1 Overview
The routing data is used to define the office direction, route, sub-route and route
analysis information pertaining to route selection during the number analysis and call
connection. The routing data must not be configured before the local office data and
signaling data is configured. See Figure 9-4.

9-6

Start
Equipment data
Trunk data
Office data
Number analysis
Charging data
Subscriber data
MG data
Centrex data
MRS data
Call barring data
Protocol data
IN service data
Signaling data
Other service data
Routing data
Other application
data
End

During the configuration, some parameters defined in the local office data and signaling
data will be referenced in the routing data. Meanwhile, some parameters defined in the
routing data will be referenced when the trunk data, number analysis data and PRA
subscriber data is configured. The broken lines in Figure 9-4 show the referencing
Table 9-1 Parameter referencing relationship between routing data and other data
Input parameter
Name
Output parameter
Defined in
Name
Referenced in
Route selection
source code
Local office
data
Sub-route
number
Trunk data
Destination signaling
point code (DPC)
M3UA data or
MTP data
DPC in the
office direction
Trunk data (only

available for No. 7 trunk)
Route
selection code
Number analysis data,

PRA subscriber data

9-7

II. Preparations
Before configuring the routing data, make sure that all preparations are done as
SN
Item
Remark
Route planning
To determine the planning of direction route and alternative

route of each office direction according to the network
planning.
Route
selection
policy
To determine the preferential trunk, sub-route selection

policy and trunk group selection policy of each route
according to the network planning.
Basic routing
data planning
To dial for the routes, sub-routes and office directions in the

routing data, and determine the corresponding route
selection code according to the route planning.

Table 9-3 lists the general steps for configuring the routing data.
Step
Description
Command
Add office direction
ADD OFC
Add sub-route
ADD SRT
Add route
ADD RT
Add time index (optional)
ADD TMIDX
Add route analysis
ADD RTANA

the routing data is configured.

9-8

ADD OFC
[Office direction number]
[Peer office type]
[Peer office level]
ADD SRT
[Sub-route number]
[Group selection mode]
ADD RT
[Route number]
[Route type]
[1st sub-route]
[2st sub-route]
ADD TMIDX
[Week]
[Hour]
[Time index]
ADD RTANA
[Route selection code]
[Time index]
[Route number]
9.2.2 Adding Office Direction

I. Related commands
Command
Function
ADD OFC
To add office direction
RMV OFC
To remove office direction
MOD OFC
To modify office direction
LST OFC
To list office direction

9-9


In the actual networking, the SoftX3000 may be interconnected with multiple offices,
and all the trunk circuits between each office and the local office compose an office
direction. In the SoftX3000, the office direction data is used to describe the type, level,
attributes, signaling network indicator and destination signaling point code of the peer
office, and it is generally used in the traffic statistics. If an office direction contains No. 7
trunk, the office direction data is also used to select No. 7 signaling route in the call
connection process.

It uniquely identifies an office direction. Its value s assigned globally, ranging from 0 to
65534.
[Office direction name]
It describes an office direction for the ease of identification. Its value is character string.
[Peer office type]
It specifies the type of the peer office in the switching network. The choices include PBX,
Local/rural call office, Toll, urban & rural call office, National toll office, International toll
office, and Manual toll office. You can select according to the actual networking
conditions.
[Peer office level]
It specifies the level of the opposite office relative to the local office. The options include
Superior, Peer, and Inferior, and you can select an option according to the actual
networking conditions.
If the offices A and B are set to be the same level, to avoid alternative routing between
the offices of the same level, the local office can neither transit the traffic originated by
the office A to the office B nor transit the traffic originated by the office B to the office A.
Therefore, when the SoftX3000 acts as a gateway, you must set the interconnected
gateway and the local toll office to be higher than the SoftX3000 and the other
exchanges in the local network to be lower than the SoftX3000. In this way, the local
office can achieve traffic transit across networks, for example, can transit traffic from a
fixed network to a mobile network or from a mobile network to a fixed network.
[Peer office attribute]
It specifies the device type of the peer office, including exchange, crossbar-system
exchange, Step-by-Step-system exchange, voice mailbox, voice mailbox station,
manual station, console, public data network, Signaling Transfer Point (STP) and
9-10

Service Control Point (SCP). You can select according to the actual networking
conditions.
[Network indicator]
It specifies which signaling network the peer office (SP or STP) exists in. This
parameter is valid only when the office contains No. 7 trunk. You can select according
to the actual networking conditions, and the system default option is National.
[Destination point code 1] to [Destination point code 16]
They are used to specify the signaling point codes of the peer office in the
corresponding signaling networks. The value is hexadecimal and there are a maximum
of 24 bits. These parameters are valid only when the office direction contains No. 7
trunk. They must be defined by the ADD N7DSP command or ADD M3DE command
Generally, it is required only to configure one destination signaling point for an office
direction. If the peer office adopts multiple signaling point codes, one office direction
can be configured with a maximum of 16 destination point codes (DPCs) belonging to
the same network indicator. If you use the ADD N7TG command to add No. 7 trunk
group, the DPC must be specified here before being referenced in the command.
Otherwise, errors may occur to the system.
[Method of selecting SP]
Reserved.
[ISUP transmit mask]
It is used for converting ISUP messages sent by the local office in an office direction to
adapt to the ISUP signaling used by the switch in the office direction. You cannot set it
at will, but refer to the ISUP signaling adaptation script provided by Huawei.
[ISUP receive mask]
It is used for converting ISUP messages received by the local office in an office to adapt
to the ISUP signaling used by the switch in the office direction. You cannot set it at will,
but refer to the ISUP signaling adaptation script provided by Huawei.
[Common language location identification]
It is one of the parameters for the SoftX3000 to interwork with the switch applying ANSI
ISUP signaling, identifying the location of the peer office. It is allocated by the network
uniformly.
It is valid only in ISUP defined by ANSI and indicates the location identification in the
CVR message set by the local office in the CVT/CVR procedure. It is composed of a
maximum of 11 characters. The default value is Anonymous.
9-11

[SS7 type]
It indicates the type of the SS7 that is applied between the local SoftX3000 and the DSP.
By default, it is ITU-T. If the SoftX3000 is to interconnect with the signaling device
complying with ANSI specifications, select ANSI; otherwise, the MTP link between
two signaling devices cannot work normally.
[MTP congestion step rate]
It indicates the ratio used by the local office to restrict outgoing or transferred calls to an
office when the MTP links between the local office and the office are congested. It
ranges from 0 to 100 in unit of %.
[ACC congestion level 1 step rate]
office when call congestion level 1 occurs in the office and the local office has received
the auto-congestion control message from the office. It ranges from 0 to 100 in unit of
%.
When TUP is used as the inter-office signaling, the auto-congestion level information
is contained in the ACC message sent from the peer office to the local office. When
ISUP is used as the inter-office signaling, the auto-congestion level information is
contained in the REL message sent from the peer office to the local office.
[ACC congestion level 2 step rate]
office when call congestion level 2 occurs in the office and the local office has received
the auto-congestion control message from the office. It ranges from 0 to 100 in unit of
%.
When TUP is used as the inter-office signaling, the auto-congestion level information
is contained in the ACC message sent from the peer office to the local office. When
ISUP is used as the inter-office signaling, the auto-congestion level information is
contained in the REL message sent from the peer office to the local office.
[ACC support flag]
It indicates if the peer office supports auto-congestion control. By default, it is Yes. In
this case, when the CPU usage of the local office reaches the overload threshold for
auto-congestion level 1 or 2, the local office will send an auto-congestion control
message to the peer office through SS7 to notify it of the congestion at the local office.
If you set it to No, the local office will not send any auto-congestion control message to
the peer office in any cases.
[Fallback support flag]

9-12

It indicates if the peer office supports fallback of bearer capability. By default, it is No.
In this case, the local office will not send the fallback support flag contained in the IAM
to the peer office through ISUP in any cases.
[ISUP compatibility TX mask]
It is used for parameter compatibility adaptation between ISUP messages sent by the
local office and ISUP signaling used by the peer office. It cannot be set arbitrarily;
instead, take the ISUP signaling adaptation script provided by Huawei as the reference
when setting it.
[ISUP compatibility RX mask]
It is used for parameter compatibility adaptation between ISUP messages received by
the local office and ISUP signaling used by the peer office. It cannot be set arbitrarily;
instead, take the ISUP signaling adaptation script provided by Huawei as the reference
when setting it.
9.2.3 Adding Sub-Route

I. Related commands
Command
Function
ADD SRT
To add sub-route
RMV SRT
To remove sub-route
MOD SRT
To modify sub-route
LST SRT
To list sub-route

[Sub-route number]
It uniquely identifies a sub-route. Its value is assigned globally, ranging from 0 to 65534.
It specifies the office direction to which the sub-route belongs. This parameter must be
defined by the ADD OFC command before being referenced here.
[Sub-route name]
It identifies a sub-route with a string of characters.
[Group selection mode]

9-13

It specifies the trunk group selection policy of the sub-route. There are four selection
modes as choices.
z
Cycle: The system will select a group number starting from the next one to the last
selected group number each time when it selects a trunk group. If the last selected
number is the maximum one, the next one is the minimum group number. The load
sharing of the trunk groups can be realized through this mode.
Minimum: The system always selects a trunk group from the minimum number. If
the trunk group is faulty or all circuits are busy, the system will select the next one
in the ascending order. The preferential selection of the trunk groups can be
realized through this mode.
Maximum: The system always selects a trunk group from the maximum number. If
the trunk group is faulty or all circuits are busy, the system will select the next one
in the descending order. The preferential selection of the trunk groups can be
realized through this mode.
Random: The system selects a trunk group randomly. This mode is seldom used.
The default mode is Cycle, and you can select other mode according to the actual
conditions.
9.2.4 Adding Route

I. Related commands
Command
Function
ADD RT
To add route
RMV RT
To remove route
MOD RT
To modify route
LST RT
To list route

[Route number]
It uniquely identifies a route. Its value is assigned globally, ranging from 0 to 65535.
[Route name]
It identifies a route with a string of characters.
[Route type]
It specifies whether the route is an ordinary route or queue route. The default type is
ordinary route.

9-14

z
Ordinary route: The queuing is unnecessary when the routing fails, and the call is
immediately released (the calling subscriber hears busy tone).
Queue route: The queuing will take place at the subscriber side for idle circuits if
routing fails, and the call is temporarily held (the calling subscriber does not hear
busy tone) until there is idle circuit or the call is released due to timeout.
[Sub-route selection mode]

It specifies the sub-route selection policy of the route. There are two selection modes
as choices.
z
Sequential selection: It means to select a sub-route in the sequence from the first
one to the thirty-second one. That is, if sub-route 1 (direct sub-route) is busy or
unavailable, sub-route 2 will be selected; if sub-route 2 is unavailable, sub-route 3
will be selected, and so on.
Select by percentage: It indicates that the 32 sub-routes are grouped according to

the percentage. The sub-routes whose total percentage is 100% are grouped
together. In each group, the sub-routes work in load sharing mode based on the
percentage, and the groups are selected according to the sequence. For example,
if it is required to select sub-route 1 as prior, and that sub-routes 2 and 3 work in
load sharing mode when sub-route 1 is busy or unavailable, the Select by
percentage option can be selected and the their percentages are 100%, 50% and
50%.
Select by cost: The sub-route with the lowest cost will be selected as prior. If this
sub-route is busy or unavailable, the one with the second lowest cost will be
selected, and so on. If several sub-routes cost the same, they will be selected by
percentage.
The default mode is Select by sequence.

[1st sub-route] to [32nd sub-route]
They are used to specify the numbers of the sub-routes. They must be defined in the
ADD SRT command before being referenced here. If there is only one sub-route, you
can ignore from 2nd sub-route to 32nd sub-route. If there are only two sub-routes, you
can ignore from 3rd sub-route to 32nd sub-route, and so on.
[Percentage of sub-route1] to [Percentage of sub-route32]
They specify the probability of each sub-route to be selected. Set this parameter by the
1)
They are valid only when Sub-route selection mode is Select By Percentage".
The value ranges from 1 to 100 with the unit as %. Because the grouping is
conducted according to the percentage of the sub-routes, no matter how much the
percentage of each sub-route is, their total percentage must be the integral times
of 100. Otherwise, the system may fail. For example, if a route contains five
sub-routes, there are the following grouping methods for them:
9-15

z
One group: The percentage sum of the sub-routes is 100%. For example, the
percentage of each sub-route is 20%.
Two groups: The percentage sum of the sub-routes is 200%. For example, the
percentage of sub-route 1 is 100% and it is in one group, and the percentage of
each sub-route from sub-routes 2 to 5 is 25% and they are in one group.
Three groups: The percentage sum of the sub-routes is 300%. For example, the
percentage of sub-route 1 is 100% and it is in one group, the percentage of each of
sub-route 2 and sub-route 3 is 50% and they are in one group, and the percentage
of each of sub-route 4 and sub-route 5 is 50% and they are in one group.
Other groups apply the same method.
2)
When Sub-route selection mode is Select By Cost", if several sub-routes cost

the same, you must specify percentages for them (otherwise, the system might
fail), and the system will select a sub-route among them by percentage. At this
time, sub-routes are not grouped by percentage, so the total percentage of the
sub-routes may not be the integral multiples of 100, and the probability of a
sub-route to be selected is calculated by the system according to the absolute
percentage of the sub-route. Suppose sub-route 2 and sub-route 3 have the same
cost; the percentage of sub-route 2 is A; and the percentage of sub-route 3 is B.
The probability of sub-route 2 to be selected is A/(A+B), and that of sub-route 3 to
be selected is B/(A+B).
[Cost of sub-route1] to [Cost of sub-route32]

They are available only when Sub-route selection mode is Select by Cost", ranging
from 0 to 65535 without unit. The value 65535 indicates invalid.
[TRIP flag]
It specifies whether the SoftX3000, during the system performs route analysis, sends
the INVITE message to the location server through SIP to query the route information
from the local office to relevant destination code. The default value is No. If the value
is set to "Yes" and you have set Enable LS query to Yes through the command SET
LSAGENT, the analysis procedures of relevant route are as follows:
z
For an outgoing destination code, the SoftX3000 performs route analysis

according to the default routing mode configured in the local office: Call prefix >
Route selection code > Route number > Sub-route number > Trunk group
number.
If the system succeeds in route analysis, the SoftX3000 performs the connection
according to the default route configured in the local office. If not, the SoftX3000
holds the calling, and sends the INVITE message to the location server through
SIP to query the route information from the local office to relevant destination
code.
After the successful query, the location server sends the 302 response message to
the SoftX3000 through SIP. This message carries the IP address, type and the port

9-16

number of the application protocol of the SoftSwitch (destination office or gateway

office) that connects the destination code. If the application protocol is SIP, the
local office initiates a call to the destination SoftSwitch in SIP trunk mode
according to the IP address of the SoftSwitch and the port number SIP.
9.2.5 Adding Time Index (Optional)

I. Related commands
Command
Function
ADD TMIDX
To add time index
RMV TMIDX
To remove time index
LST TMIDX
To list time index

The time index is mainly involved in dynamic route selection. It divides a day into
different time segments (identified by time index) according to the specific day in a
week. During the route analysis, the system will select different routes according to the
different time segments to implement dynamic route selection.
During the initialization, the system has preset a time index table (with the time index
value as 0), in which the day is not divided. In this case, using this table will not
implement the dynamic route selection (the default route selection mode). If the carrier
requires selecting routes based on different time segments, you must use the ADD
TMIDX command to add time index.
When selecting the route, the system matches the parameter of "Week (or Date)",
Time defined in "Time index. If the match fails, the route selection fails. For instance,
if you have added two time indexes 1 and 2 through the command ADD TMIDX, the
previous time segments corresponding to the time index 0 should be changed, which
indicates the time segment of a whole day no more in a certain date. Because there is
only time index 0 in the route analysis data list, the system only selects route in the time
segments corresponding to time index 0 instead of time indexes 1 and 2. So, when you
add time index through the command ADD TMIDX, you must configure the route
analysis data corresponding to the newly-added time index through the command ADD
RTANA for all the route selection codes. If not, you will fail in route selection.

[Time index]
9-17

It defines the value of the time index corresponding to the time segment. Its value
ranges from 1 to 253. Set this parameter by the following principles:
z
Time index 0 has been pre-set during the initialization of the system, so you cannot
set it.
A time index can correspond to multiple time segments, that is, you can use the
command ADD TMIDX to define different time segments for one time index for
several times.
When the call processing software analyzes the route, if the time index of two route
analysis data records (one by month and one by week) matches the current call, the
time index by month is prior to that by week.
[Service type]
It indicates the range of services to which a time index is applicable. The options are
z
Route selection: Indicates that a time index is used for route selection, that is, the
parameter will be referenced in the command ADD RTANA.
Caller number analysis: Indicates that a time index is used for caller number
analysis, that is, the parameter will be referenced in the command ADD CNACLR.
[Index type]
It defines the index type for a time index. The options are
z
Week index: Indicates that the time index data is defined by weekday (Sunday,
Monday, Tuesday Saturday).
Month index: Indicates that the time index data is defined by month (a day in a
month).
[Week]
It is valid only when the index type is Week index. It specifies a specific day in a week,
such as Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, and Saturday.
[Month], [Day]
It is valid only when the index type is Month index. It specifies a specific day in a
month and must be a valid date in the current year.
[Hour]
It specifies the last time of the time segment of each day, with the unit as hour. The
value range is 1 to 24. If the time point at which the corresponding call occurs is smaller
than or equal to the set value of the parameter, this parameter will be matched.
For example, if Sunday is divided into two time segments, the segment from 0 to 10
o'clock is assigned with the time index value of 1, and the segment from 10 to 24 o'clock
is assigned with the time index value of 2. According to the matching principle, the
parameter in the first segment must be set to 10, indicating that the time index value

9-18

from 0 to 10 oclock on Sunday is 1, and the parameter in the second segment must be
set to 24, indicating that the time index value from 10 to 24 oclock on Sunday is 2.
9.2.6 Adding Route Analysis

I. Related commands
Command
Function
ADD RTANA
To add route analysis
RMV RTANA
To remove route analysis
MOD RTANA
To modify route analysis
LST RTANA
To list route analysis

It defines uniquely a route selection code in the SoftX3000. The value range is 0-65534.
The route selection code is the indication code when the system selects outgoing route
during the number analysis on a call prefix. The parameter will be referenced to define
outgoing call prefix when the ADD CNACLD command is used..
It uniquely defines a route selection code in the SoftX3000 and the value ranges from 0
to 65534. The route selection code is the indication code when the system selects
outgoing route during the number analysis. The parameter must be configured through
the command ADD CNACLD first (when defining outgoing call prefix) and then
referenced here.
[Caller category]
One of the route selection conditions. It specifies the category of the calling subscriber
that can use the route, that is, to define which categories of calling subscribers can use
the route. The value is generally set to All categories. If there is special demand, for
example, if only the prior subscribers can use this route, the parameter must be set to
Prior.
When the call processing software is performing a route analysis, if the caller
subscriber category parameter defined in more than one (usually two) pieces of route
analysis data records can match the current call, the priority of the all categories
option is the lowest. That is, the system preferentially selects other matching options.
[Address information indicator]
9-19

One of the route selection conditions. It specifies the service attributes of the call using
the route, that is, to define which types of calls can use the route. The value is generally
set to All categories. If there is special demand, for example, if only the national toll
calls can use this route, the parameter must be set to National Toll.
When the call processing software is performing a route analysis, if the address
information indicator parameter defined in more than one (usually two) pieces of route
analysis data can match the current call, the priority of the all categories option is the
lowest. That is, the system preferentially selects other matching options.
[Caller access]
It is one of the conditions for route selection, specifying the access type(s) of callers
using a route. It is set to All categories generally. If there is a special requirement, set
the parameter as needed. For example, if it is required that only ISDN subscribers can
use this route, you can set the parameter to ISDN.
When the call processing software analyzes the route, if the "caller access option of
several (usually two) route analysis data records matches with the current call, the
option All categories enjoys the lowest priority.
[Transmission capability]
It is one of the route selection conditions, specifying the service types that the route can
bear, for example, voice service, digital service and video service. Generally, the value
is set to All categories.
When the call processing software is performing a route analysis, if the transmission
capability parameter defined in more than one (usually two) pieces of route analysis
data can match the current call, the priority of the all categories option is the lowest.
That is, the system preferentially selects other matching options.
[Time index]
It is one of the route selection conditions, specifying the time index value used by the
route analysis table. The system has defined the time index 0 during initialization, and
the value can be referenced directly. If it is required to use other time index values, they
must be defined by the ADD TMIDX command before being referenced here. Note the
following matters when configuring this parameter:
z
When you add time index through the command ADD TMIDX, you must configure
the route analysis data corresponding to the newly-added time index through the
command ADD RTANA for all the route selection codes. If not, you will fail in route
selection.
When the call processing software analyzes the route, if the time index of two
route analysis records (one by month and the other by week) matches the current
call, the time index by month is prior to that by week.

9-20

[Route number]
It specifies the route number used by the route analysis table. This parameter must be
defined by the ADD RT command before being referenced here.
[Signaling as prior]
It indicates which signaling trunk is used first for outgoing calls when the route contains
multiple types of signaling trunks. The parameter options are described as follows:
z
Prefer to select ISUP: It indicates that the ISUP trunk of the route will be selected
first. That is, the system will not select other types of trunks until there is an idle
ISUP trunk in this route. When the ISUP trunk circuits are all busy or unavailable,
the system selects other types of trunks.
Must select ISUP: It indicates that the ISUP trunk must be selected. That is, the
system can only select ISUP trunk when selecting trunk circuits in the route. If you
defined other non-ISUP trunks, all of the non-ISUP trunk will never be selected. In
this case, make sure that the route contains ISUP trunk when you select this
option. Otherwise, the route selection will be failed.
Prefer to select SIP: It indicates that the SIP trunk in the route will be selected first.
The description is the same as that of ISUP select first.
Must select SIP: It indicates that the SIP trunk in the route must be selected. The
description is the same as that of ISUP select must.
Prefer to select H323: It indicates that the H.323 trunk in the route will be selected
first. The description is the same as that of ISUP select first.
Must select H323: It indicates that the H.323 trunk in the route must be selected.
The description is the same as that of ISUP select must.
No change: It indicates that the trunk will be selected according to the sub-route
selection policy and trunk group selection policy. During the transition, if the
incoming trunk is ISUP trunk, the trunk will be selected according to the forward
call indicator in the IAM/IAI message sent from the peer office.
Note that preference of a signaling trunk is not done among different sub-routes of a
route, but among different trunk groups of a sub-route. That is, selection of sub-route is
not controlled by this parameter.
9.3 Configuring Location Server Data

9.3.1 Overview
The location server data defines the IP address of the main/standby location server
interconnected with the SoftX3000 in the local office. SIP data must have been
configured before configuring the location server data.
9-21

II. Configuration procedures

Table 9-4lists the general steps for configuring the location server data.
Step
Description
Command
Adding Location Server
ADD LS
Setting Location Server Agent
SET LSAGENT
Activating Location Server Link
ACT LSLNK
9.3.2 Adding Location Server

I. Related commands
Command
Function
ADD LS
Add Location Server
RMV LS
Remove Location Server
MOD LS
Modify Location Server
LST LS
List Location Server

[Main LS IP address]
It is one of the parameters for interconnecting the SoftX3000 and the location server. It
specifies the IP address of the main location server interconnected with the SoftX3000
in the local office.
[Main LS name]
It specifies the name of the main location server. The value range of this parameter is a
string of characters, used to specify a main location server in detail.
[Standby LS IP address]
It specifies the IP address of the standby location server. It is one of the parameters for
interconnecting the SoftX3000 and the location server. It specifies the IP address of the
standby location server interconnected with the SoftX3000 in the local office.
[Standby LS name]

9-22

It specifies the name of the standby location server. The value range of this parameter
is a string of characters, used to specify a standby location server in detail.
9.3.3 Setting Location Server Agent

I. Related commands
Command
Function
SET LSAGENT
Set Location Server Agent
LST LSAGENT
List Location Server Agent

In the model of hierarchical route networking in NGN, the SoftX3000 sends route query
message to the location server through SIP. So, before setting the location server agent
data through the command SET LSAGENT, you should configure the SIP data.

[Enable TGREP]
It specifies whether the SoftX3000 enables the TGREP function. The default value is
No. If set to Yes, as soon as you modify the route information in the SoftX3000
database, the SoftX3000 notifies the location server in the ITAD domain to refresh the
route information through TGREP.
[Enable LS query]
It specifies whether the SoftX3000 enables the LS query function when performing
route analysis. The default value is No. If the value is "Yes" and you have set TRIP
flag to Yes through the command MOD RT, the analysis procedures of relevant route
are as follows:
z
For an outgoing destination code, the SoftX3000 performs route analysis

according to the default routing mode configured in the local office: Call prefix >
Route selection code > Route number > Sub-route number > Trunk group
number.
If the system succeeds in route analysis, the SoftX3000 performs the connection
according to the default route configured in the local office. If not, the SoftX3000
holds the calling, and sends the INVITE message to the location server through
SIP to query the route information from the local office to relevant destination
code.
After the successful query, the location server sends the 302 response message to
the SoftX3000 through SIP. This message carries the IP address, type and the port
9-23

number of the application protocol of the SoftSwitch (destination office or gateway

office) that connects the destination code. If the application protocol is SIP, the
local office initiates a call to the destination SoftSwitch in SIP trunk mode
according to the IP address of the SoftSwitch and the port number SIP.
[ITAD ID]
It is one of the parameters for interconnecting the SoftX3000 and the LS. When
modifying the route information of the SoftX3000, it specifies the ITAD ID (IP Telephone
Administration Domain ID) carried by the TGREP message that is sent by the
SoftX3000 to the LS. Its value range is 1-2147483647. This value is allocated in the
whole network by operators instead of casual configuration.
[Application protocol type]
For the call prefix in the local office, when the SoftX3000 notifies the LS in the ITAD to
refresh the route information through the TGREP message, this parameter specifies
the field value of application protocol in the TGREP message. It can be SIP or
H.323_Q931.
When the SoftSwitch A queries the route information related to the call prefix in local
office through the LS in the ITAD to which the local office belongs, the LS sends SIP
response message carrying the information of Application protocol type specified
here to the SoftSwitch A. According to the application protocol type, the SoftSwitch A
initiates a call to the SoftSwitch of the local office in trunk mode of the protocol type.
It specifies the module number of the IFMI board used to send the TGREP message in
the local office. It must be configured through the command ADD BRD first and then
referenced here.
[TGREP module number]
It specifies the module number of the MSGI board used to process the TGREP
message in the local office. It must be configured through the command ADD BRD first
and then referenced here.
[LSC module number]
It specifies the module number of the MSGI board used to run the LS client program in
the local office. It must be configured through the command ADD BRD first and then
referenced here.

9-24

9.3.4 Activating Location Server Link

I. Relevant commands
Command
Function
ACT LSLNK
Activate Location Server Link
DEA LSLNK
De-activate Location Server Link

[Location server name]
It specifies the name of the LS to be operated. This parameter must be configured
through the command ADD LS first and then referenced here.

9-25

Chapter 10 Configuring Trunk Data

This chapter presents the trunk data, including SIP trunk data, H.323 trunk data, No. 7
trunk data, R2 trunk data, Primary Rate Access (PRA) trunk data, AT0 trunk data, and
V5 trunk data. The trunk data must not be configured before the equipment data, local
office data, charging data, MG data, protocol data, signaling data and routing data is
Only when V5 interface data is configured
Start
Equipment data
Trunk data
Office data
Number analysis
Charging data
Subscriber data
MG data
Centrex data
MRS data
Call barring data
Protocol data
IN service data
Signaling data
Other service data
Routing data
Other application
data
End
Note:
Except V5 trunk data, the other trunk data must not be configured before the
corresponding signaling data is configured. Besides, because the parameter V5 trunk
group number defined in the V5 trunk data will be referenced in V5 interface data, the
V5 interface data must be configured after the V5UA data and V5 trunk data are
configured.

10-1


10.1.1 SIP Trunk
I. Basic concept
As a kind of packet trunk, Session Initiation Protocol (SIP) trunk is different from the
physical channel defined in the circuit trunk. It is a logical channel for interworking
authentication and call addressing between the local office and the peer office.
II. SIP URL

SIP adopts Uniform Resource Locators (URL) for addressing. SIP URL defines the
syntax according to the URI rule prescribed in RFC2396. The user name field can be a
telephone number to support IP telephone gateway addressing for the purpose of
interworking between IP network and PSTN. SIP identifies terminal users using the
WWW technology.
See the following for the general structure of SIP URL:
SIP: user name: password @ host: port; transmission parameters; user parameters;
method parameters; TTL parameters; server address parameters? Header name =
header value
z
SIP: It indicates that SIP is used to communicate with the specific end system.
User name: It can be composed of any characters. Generally, it can be phone

number or user name as in E-mail address. Currently, the SoftX3000 treats
telephone numbers as user names.
Host: It can be the domain name of the host or the IPv4 address.
Port: It indicates the number of the port to which the message is sent. The default
value is 5060, that is, the public SIP port number.
Password: It can be placed in the SIP URL. However, it is not recommended to do

so for safety purposes.
Transmission parameters: It indicates whether TCP or UDP is used for

transmission. By default, it is UDP.
User parameters: The SIP URL allows the host to be an IP telephone gateway. In
this case, a user name can be a common telephone number. Because BNF syntax
fails to distinguish telephone numbers from user names, so the field user
parameters is added after the domain name. This field has two options: IP and
telephone. When it is set to phone, it indicates that the user name is a telephone
number and the corresponding end system is an IP telephone gateway.
Method parameters: It indicates the methods or options used.
TTL parameters: It indicates the lifespan of a UDP multi-cast data packet. It is

available only when the field transmission parameters is set to UDP and server
address parameters is set to multi-cast address.

10-2

Server address parameters: It indicates the address of the server communicating
with a specific user. It covers the address in the host field and is set to muti-cast
address usually.
Transmission parameters, TTL parameters, server address parameters, and
method parameters are all URL parameters that can be used in the Contact field
(described in the later part) only.
The following are several examples of SIP URL:
SIP URL example
Meaning
Sip;
55500200@191.169.1.112;
55500200 is the user name, and 191.169.1.112 is

the IP address of the IP telephone gateway.
Sip;
55500200@127.0.0.1:5061;
User=phone;
55500200 is the user name, 127.0.0.1 is the IP

address of the host, and 5061 is the port number of
the host. User parameters is phone, indicating
that the user name is a telephone number.
Sip:
alice@registrar.com;
method=REGISTER;
Alice is the user name, and registrar.com is the

domain name of the host. Method parameters is
Register.
III. SIP-T
SIP-T is based on the SIP and enables the extension mechanism to implement the
interworking between SIP network and PSTN. The features are described as follows:
1)
Encapsulation: The SIP message body carries Integrated Services Digital

Network (ISDN) User Part (ISUP) message, that is, the SIP message can
transparently transmit ISUP message.
2)
Mapping: It includes the mapping between ISUP message and SIP message, and
the mapping between ISUP parameters and SIP header fields. The mapping
between ISUP message and SIP message is briefed as follows:
IAM = INVITE
ACM = 180 RINGING
ANM = 200 OK
RLS = BYE
RLC = 200 OK
10.1.2 H.323 Trunk

I. Basic concept
As a kind of packet trunk, H.323 trunk is different from the physical channel defined in
the circuit trunk. Instead, it is a logical channel for access authentication, address
resolution, route selection, and charging between the SoftX3000 and GW, gatekeeper
(GK), and outer GK in the H.323 network.

10-3

The SoftX3000 can be interconnected with softswitch, GK, outer GK, and GW in the
H.323 network, so the status of the SoftX3000 in the H.323 network varies with different
networking applications. For networking, the SoftX3000 classifies H.323 trunks as five
types: plain trunk, GW trunk, GK trunk, outer GK trunk, and virtual trunk. You must
correctly configure the type of the H.323 trunk; otherwise, the interconnection between
the SoftX3000 and the peer H.323 device will fail.
II. H.323 plain trunk

H.323 plain trunk is applicable to the application that the local office and the opposite
office are both softswitches. It is used for interworking authentication and call
addressing between the local office and the opposite office, as shown in Figure 10-2.
H.323 trunk
IP Metropolitan A rea
Netw ork/Bac kbone
Netw ork
S o ftX3 0 0 0
H.323 tr unk
O th e r S o ftS w itch
Figure 10-2 H.323 plain trunk
III. H.323 GW trunk

In the traditional H.323 network, if the SoftX3000 serves as a GK and the opposite
device serves as a GW such as A8010 Expert, the trunk from the SoftX3000 to the
opposite office must be H.323 GW trunk. The H.323 GW trunk is used for access
authentication, address resolution, route selection, and charging of the H.323 GW at
the SoftX3000 side. Figure 10-3 shows the typical networking.
H.323 netw ork
SoftX3000 (GK)
H.323 trunk
H.323 trunk
IP Metropolitan Area
Network/Backbone
Network
PSTN office
in city A
H.323 GW
H.323 GW
PSTN office
in city B
Figure 10-3 H.323 GW trunk
IV. H.323 GK trunk

In the legacy H.323 network, if the SoftX3000 serves as a GK and the opposite device
serves as an upper-layer GK in the H.323 network (or a GK in other H.323 network), the
trunk from the SoftX3000 to the opposite office must be H.323 GK trunk. The H.323 GK
trunk is used for address resolution and route selection between the SoftX3000 and the
upper GK. Figure 10-4 shows the typical networking.

10-4

Upper GK
H.323 trunk
H.323 trunk
Low er GK
SoftX3000 (GK)
H.323 network
H.323 GW
H.323 network
Backbone network
H.323 terminal
H.323 GW
H.323 GW
Figure 10-4 H.323 GK trunk
V. H.323 outer GK trunk

The SoftX3000 can serve as a GW in the H.323 network, and the opposite device is an
outer GK. In this case, the trunk from the local office to the opposite office must be
H.323 outer GK trunk. The H.323 outer GK trunk is used for access authentication
between the SoftX3000 and its upper GK when the SoftX3000 serves as an H.323 GW.
Figure 10-5 shows the typical networking.
Outer GK
H.323 trunk
H.323 trunk
SoftX3000 (GW)
IP Metropolitan
Area Network
in City A
IP backbone
A8010 Expert
(GW)
H.323
Phone
SIP
Phone
AMG
TMG
Figure 10-5 H.323 outer GK trunk

10-5
PSTN exchange
in City B

VI. H.323 virtual trunk

H.323 virtual trunk is applicable to the situation in which the local office acts as a GK
and the opposite office acts as a GW controlled by another GK (supporting RAS but not
Q.931). It is used together with the H.323 GK trunk for charging and authentication of
incoming calls to GW only.
10.1.3 No. 7 Trunk

I. Basic concept
No.7 trunk is a kind of circuit trunk and adopts SS7 as the inter-office signaling.
Because both the TUP and the ISUP in the SS7 can be used to control the inter-office
trunk circuits, No.7 trunks can be classified as TUP trunk and ISUP trunk.
II. CIC
The Circuit Identification Code (CIC) is one of the important parameters used for
interworking with No. 7 trunk, and it uniquely identifies the trunk circuit between two
signaling points. The CIC only exists in the Telephone User Part (TUP) and ISUP
messages, and it contains 12 bits. In this case, one office direction can have a
maximum of 212 (212 = 4096) trunk circuits.
Between the two offices using No. 7 signaling for interconnection, the CIC of the same
trunk circuit must be consistent, otherwise, there might be exceptions, for example, the
voice channel is through in a single direction.
III. Master/slave
In the bi-directional trunk group, the ITU-T prescribes that the each of the two
interconnected offices can control half of the trunk circuits for the purpose of preventing
the two offices occupying the same trunk circuit at the same time. The office with larger
signaling code controls the circuits with even CICs, and the office with smaller signaling
code controls the circuits with odd CICs.
Based on this principle, while selecting outgoing trunk, each office will first occupy the
trunk circuits controlled by itself. When the circuits controlled by an office are all busy,
the office tries occupying the trunk circuits controlled by the other office. If the two
offices try to occupy the same trunk circuit at the same time, the office will abandon the
circuit and try to occupy the next one.
10.1.4 R2 Trunk
I. Basic concept
R2 trunk is a kind of circuit trunk and adopts R2 as the inter-office signaling. R2 trunk
refers to the trunk using the R2 signaling as the inter-office signaling. Because the R2

10-6

signaling is a kind of Channel Associated Signaling (CAS), some R2 signaling

parameters have to be set when you configure the R2 trunk data.
The R2 signaling is defined in the ITU-T Recommendations Q.400 to Q.490, but it is
implemented differently in different countries or areas. There is a variety of R2 signaling
versions in the world. Some versions, for example, Russia CAS, are greatly different
from the standard R2 signaling. This chapter describes some basic concepts related to
the standard R2 signaling.
II. Register signaling

The R2 register signaling adopts the Multi-Frequency Control (MFC) signaling. For the
forward signaling, two from six frequencies are combined. The range of the frequencies
is 1380 Hz to 1980 Hz. The frequency difference is 120 Hz. For the backward signaling,
two from six frequencies are combined. The range of the frequencies is 1140 Hz to 540
Hz. The frequency difference is 120 Hz.
The forward signaling is classified into forward groups I and II. The backward signaling
is classified into backward groups A and B. The forward group I is the connection
signaling, and the forward group II is the caller category signaling. The backward group
A is the acknowledgement and control signaling to the forward group I, and the
backward group B is the callee state signaling. The forward group I and the backward
group A are a combination of mutual control signaling. The forward group II and the
backward group B are another combination of mutual control signaling. The meanings
of the combinations of signaling are shown in Table 10-1.
Table 10-1 Meanings of the signaling combinations
Forward signaling
Signalin
g No.
Connection
signaling
group I
Backward signaling
Caller category signaling

group II
(answering A3 and A5
signaling)
Acknowledgemen
t and control
signaling group A
(answering group
I signaling)
Callee state
signaling
group B
A1: Send the next

digit (n+1)
B1: Ready to
trace
the
malicious caller
A2:
Send
the
previous digit (n-1)
B2: Subscriber
transfer
A3: To the group B

signaling
B3: The callee is

busy
(Reserved)
services
A4: Congestion
B4: Congestion
Operator
A5: Send the caller

category
B5: Unallocated
number
Ordinary
subscriber
Digit 1
Digit 2
Digit 3
Maintenance
National
Digit 4
Digit 5
Preferred
subscriber
device

10-7

Forward signaling
Signalin
g No.
Connection
signaling
group I
Backward signaling
Caller category signaling

group II
(answering A3 and A5
signaling)
Acknowledgemen
t and control
signaling group A
(answering group
I signaling)
Callee state
signaling
group B
A6: Set up the voice

channel (charge)
B6: The callee is

idle (charge)
Ordinary
subscriber
A7:
Send
the
previous two digits
(n-2)
B7: The callee is

idle (no charge)
Data
A8:
Send
the
previous
three
digits (n-3)
B8: The callee is

suspended
temporarily
A9: (Reserved)
(Reserved)
A10: (Reserved)
(Reserved)
A11: Send the start

digit
of
the
international
number
(Reserved)
(Reserved)
A12: Send the start

digit of the national
number
(Reserved)
13
Calling
maintenance
device
(Reserved)
A13: Check the

sending of the start
digit
of
the
international
number
(Reserved)
14
Inserting
echo
suppresser
(Reserved)
A14: Whether the

echo suppresser is
needed
(Reserved)
15
Sending
completed
(Reserved)
(Reserved)
(Reserved)
Digit 6
Data transmission
Digit 7
Digit 8
Digit 9
Preferred
International
10
Digit 0
Operator
services
11
Calling
manual
operator
12
Rejecting the
signaling As
request
transmission
subscriber
Coin
subscriber
III. Transmission modes

CAS is transmitted over multiple segments of routes in two modes: end-to-end
transmission and segment-by-segment transfer.
z
End-to-end transmission: The originating office sends to the first transfer office a
called number that has sufficient digits for routing. The first transfer office judges
the route and connects the corresponding incoming trunk circuit to an outgoing
trunk circuit. At this time, the call from the originating office is connected to the next

10-8

transfer office. Subsequently, the originating office sends to the second transfer
office a called number that has sufficient digits for routing. The second transfer
office judges the route and connects the corresponding incoming trunk circuit to an
outgoing trunk circuit. At this time, the call from the originating office is connected
to a third transfer office (or the terminating office). The following operations can be
deduced in the same way. With this transmission mode, the call is connected
rapidly and the register is used efficiently. Nevertheless, the same register
signaling mode of the exchanges must be used through the multiple segments of
routes.
z
Segment-by-segment transfer: Each transfer office must have received all called
number digits from the previous exchange before it transfers the called number to
the next transfer office (or the terminating office). With this transmission mode, the
requirements for the line are low and different register signaling modes of the
exchanges can be used through the multiple segments of routes. However, the
call is connected slowly.
For the register signaling, the R2 signaling system of the SoftX3000 provides both
transmission modes. You can select one according to the quality of the line: the
segment-by-segment transfer mode is suitable for low-quality line and the end-to-end
transmission mode for high-quality line. For the line signaling, only the
segment-by-segment transfer mode can be selected.
IV. Control modes

A control mode refers to a method of controlling the sending of the signaling.
z
Non mutual control mode (pulse mode): The originating office keeps sending one
or a group of expected pulse signals to the terminating office despite the reception
of the correct signals at the terminating office. This mode requires simple devices,
but the reliability of the transmission is very poor.
Half mutual control mode: Whenever sending one or a group of pulse signals to
the
terminating
office,
the
originating
office
waits
for
the
positive
acknowledgement signal before sending the next signal.

z
Full mutual control mode: The originating office keeps sending forward signals
until it receives the acknowledgement signal returned by the terminating office.
The terminating office keeps sending acknowledgement signals until the
originating office stops sending forward signals. Because the forward and
backward signals are all continuous, this mode is also called continuous mutual
control mode.
The R2 signaling system of the SoftX3000 employs the full mutual control mode and
provides the non mutual control mode and the half mutual control mode.

10-9

10.1.5 PRA Trunk

I. Basic concept
Extensively speaking, PRA trunk is a kind of circuit trunk. It is a PRA digital subscriber
line actually, that is, 30B+D 2 Mbit/s subscriber line. PRA trunk uses DSS1 as its control
signaling. Because DSS1 is designed on the basis of the model of network side and
subscriber side, the system manages and controls a PRA trunk as a subscriber (PRA
subscriber).
II. PRA subscriber

The SoftX3000 manages the call-in and call-out authorities, charging, and route
selection attributes of a PRA trunk group by controlling these attributes of the PRA
subscriber (that is, the default calling number) corresponding to the PRA trunk group.
Therefore, you must set the PRA subscriber data correctly before setting the PRA trunk
data.
III. Multi-PCM system

Normally, one PRA link only controls one PCM system, that is, 32 trunk circuits.
However, when PRA link resource is not enough, you can use one PRA link to control a
maximum of four PCM systems.
In the SoftX3000, the system manages such attributes of the PRA trunk group as call-in
authorities, call-out authorities, charging and route selection by controlling those
attributes of the PRA subscriber corresponding to the PRA trunk group. In this case,
you must correctly configure the PRA subscriber data before configuring the PRA trunk
data.
10.1.6 AT0 Trunk

I. Basic concept
Extensively speaking, AT0 trunk is a circuit trunk, but it is actually an analog subscriber
line for Direct-Dial-In (DDI) functions of PBX. When AT0 trunk is used in networking, the
SoftX3000 interacts with the peer PBX through the common analog subscriber line
signaling. See Figure 10-6 for the networking.

10-10

SoftX3000
Inserted with the CDI
Inserted with the analog

subscriber board
Analog subscriber line (AT0 trunk)
IP MAN
PBX
AMG / IAD
Figure 10-6 AT0 trunk networking
II. Purpose of AT0 trunk

Direct-Dialing-In (DDI) means that a subscriber can directly dial the number of a PBX
subscriber from the PSTN side (that is, the SoftX3000 side) instead of using dual-stage
dialing.
In the above figure, PBX occupies the number resources of PSTN and AT0 trunk can
only support single-directional calls, that is, calls from the PSTN side (the SoftX3000
side) to the PBX side.
10.1.7 V5 Trunk
I. Basic concept
Extensively speaking, V5 trunk is a circuit trunk, but it is actually a 2.048-Mbit/s link at a
V5 interface. V5 trunk is located between a local exchange and the access network,
adopting V5.1/V5.2 as the call control protocol, so one V5 trunk group can be
configured with a maximum of 16 E1s.
II. V5 link ID
V5 link ID is one of the concepts in the V5 protocol. Because one V5.2 interface can
support a maximum of sixteen 2.048-Mbit/s links, V5.2 protocol involves two
parameters, V5 link ID and V5 time slot number, to uniquely identify a V5 time slot over
multiple 2.048-Mbit/s links.
z
V5 link ID: An 8-bit field, used to identify a specific 2.048-Mbit/s link among the
2.048-Mbit/s links composing the V5.2 interface. This specific link contains the V5
time slot selected to be bearer channel. The V5 link ID needs to be determined by
the negotiation between the Local Exchange/Office (LE) side and Access Network
(AN) side, and it must be consistent with that in the data configuration.
10-11

z
V5 time slot number: A 5-bit field, used to identify the V5 time slot that is to be used
or being used as bearer channel. The V5 time slot number is controlled and
assigned by the Bearer Channel Connection (BCC) protocol.
III. MG E1 ID
MG E1 ID is one of the concepts in the V5UA protocol. Because one V5UA link set can
bear the protocol messages of multiple V5.2 interfaces, and one V5.2 interface can
support multiple 2.048-Mbit/s links, you need to map the V5 link ID of the V5.2 interface
to the MG E1 ID in the V5UA link set so that a 2.048-Mbit/s link can be uniquely
identified among the messages in the same V5UA link set.
10.2 Configuring SIP Trunk Data

10.2.1 Overview
The SIP trunk data is used to configure interconnection information between the
SoftX3000 and other softswitch or SIP application server, such as SIP-URL and SIP-T.
The SIP trunk data configuration must not be done before the equipment data, local
office data, charging data, protocol data and routing data is configured. See
Figure 10-1.
During the configuration, some parameters defined in the local office data, charging
data and routing data will be referenced in the SIP trunk data. Besides, the Network
management source code defined in the SIP trunk data will be referenced when the
network management data is configured. Table 10-2 shows the details.
Table 10-2 Parameter referencing relationship between SIP trunk data and other data
Input parameter
Name
Output parameter
Defined in
Name
Referenced in
Call source code
Basic call data
Network
management
source code
Network
management data
Charging data
Outgoing trunk
charging source code
Charging data
Subroute number
Routing data
Caller number
discrimination group
number (optional)
Call barring data

10-12

II. Preparations
Before configuring the SIP trunk data, make sure that all preparations are done as
SN
Item
Remark
IP address of the
opposite office
For interworking with other SoftSwitch or SIP

application server
SIP port number of

the opposite office

application server
Whether SIP-T
supported

application server
is

Table 10-4 lists the general steps for configuring the SIP trunk data.
Step
1
Description
Command
Add SIP trunk group
ADD SIPTG

mutually.
10.2.2 Adding SIP Trunk Group

I. Related commands
Command
Function
ADD SIPTG
To add SIP trunk group
RMV SIPTG
To remove SIP trunk group
MOD SIPTG
To modify SIP trunk group
LST SIPTG
To list SIP trunk group

Before adding SIP trunk group, use the related commands to obtain the following
parameters defined by the system:
10-13

Call source: LST CALLSRC
Subroute number: LST SRT
Charging source code: LST CHGGRP, LST CHGIDX
Caller number discrimination group number (optional): LST CLRDSN
Note:
This section only introduces the parameters closely related to SIP trunk group. For the
other parameters, refer to online help or 10.4.5 "Adding No. 7 Trunk Group.

It uniquely identifies a trunk group, which can be SIP trunk group, H.323 trunk group,
No. 7 trunk group, R2 trunk group, PRA trunk group, AT0 trunk group, or V5 group.
Assign its value globally. The value ranges from 0 to 65534.
[Call source code]
It specifies the call source to which the trunk group belongs. This parameter must be
defined in the ADD CALLSRC command before being referenced here.
[Sub-route number]
It specifies the subroute to which the trunk group belongs. This parameter must be
defined in the ADD SRT command before being referenced here.
[Trunk group name]
It identifies a trunk group with a string of characters.
[Call-in authority]
It defines the call-in authorities of the trunk group, such as intra-office, local, local toll,
national toll, international toll, intra-office national toll (in multi-zone-code application),
and intra-office international toll (in multi-country-code application). The system
enables all call-in authorities of the trunk group by default.
[Call-out authority]
It defines the call-out authorities of the trunk group, such as intra-office, local, local toll,
enables all call-out authorities of the trunk group by default.
It is one of the charging attributes of the trunk group. Its value ranges from 0 to 255. The
value 254 is the wildcard that cannot be used for trunk charging. The value 255
indicates no charging of incoming trunks. This parameter must be defined in ADD
10-14

CHGIDX or ADD CHGGRP before being referenced here. For the detailed information
about charging, see Chapter 4, Configuring Charging Data, in this manual.
[Outgoing trunk charging source code]
indicates no charging of outgoing trunks. This parameter must be defined in ADD
[EC capability]
It is one of the parameters used for interworking with the opposite office. It controls the
SIP trunk to enable the EC function. The default option is YES, indicating that the EC
function is enabled.
This parameter specifies the module number of the IFMI dispatching SIP trunk protocol
messages at the SoftX3000 side. The value range is 132 to 211. This parameter is
defined in the ADD BRD command and referenced here.
[Remote URI]
It is one of the parameters used for interworking with other softswitch or SIP application
server. It specifies the IP address and SIP port number of the opposite device. The
format is xxx.xxx.xxx.xxx:port, where, xxx.xxx.xxx.xxx is the IP address and port is the
port number (the default value is 5060). For example, the SIP-URI of an office is
191.169.150.80:5060.
[Use heartbeat]
This parameter specifies whether the SoftX3000 periodically sends heartbeat signals to
the SIP device in the opposite office. The default setting is NO, indicating that the
SoftX3000 does not send heartbeat signals. This parameter must be set to YES in the
following applications:
z
This SIP trunk interconnects two assistant softswitches in the dual homing
networking.
It is demanded to improve the call completion rate and prevent the SIP trunk from
being suspended at the occurrence of network interruption.
[Minimum heartbeat timer length in minutes]

It specifies the minimum duration of the timer that controls the sending of heartbeat
signals in the SoftX3000. It is valid only when the SoftX3000 needs to send heartbeat
signals. The value range is 1 to 60. The unit is minute. The default value is 1.
[Maximum heartbeat timer length in minutes]
It specifies the maximum duration of the timer that controls the sending of heartbeat
signals in the SoftX3000. It is valid only when the SoftX3000 needs to send heartbeat
signals. The value range is 1 to 60. The unit is minute. The default value is 5.
10-15


It is the additional service flag used to set whether a SIP trunk supports some special
services or applications. There are 16 options for this parameter. Currently, only two
options are used, and the others are reserved. The meanings of the used options are
as follows:
z
Redirection enable: It indicates whether the SoftX3000 supports the function of

call redirection of SIP trunks. It is not support by default. Suppose that the
SoftX3000 initiates INVITE request to the peer office through outgoing SIP trunks.
The SoftX3000 receives call redirection response message 300, 301, 302, or 305
returned by the peer office. The called subscriber is in the local office. If the option
is selected, the SoftX3000 initiates a call to the new address to complete the
connection. If not, the SoftX3000 releases the call.
Disable default caller number: It is valid only for incoming trunks. By default, it is
not selected. When the message of incoming SIP trunk does not contain calling
number information such as anonymous card call, the SoftX3000 uses the default
calling number of the trunk group as the calling number of this call. If the option is
selected, the SoftX3000 does not use the default calling number of the trunk group
as the calling number of this call. That is, the call has no calling number.
[Stop call restriction]

When the total number of calls decreases to less than the quantity defined in this
parameter, the system stops the enabled call restriction automatically. Its value ranges
from 0 to 65535. The default value is 65535, indicating that the system cannot stop call
restriction automatically.
The value of stop call restriction must be smaller than that of maximum caller number
restriction. For example, if the parameter stop call restriction is set to 1800 and
maximum caller number restriction is set to 2000, the system starts call restriction
automatically when the total number of incoming and outgoing calls on one SIP trunk
group reaches 2000, and stops call restriction automatically when the total number of
calls falls back less than 1800 ( 1799).
[Maximum caller number restriction]
It defines the maximum number of calls allowed on one SIP trunk group. That is, when
the total number of incoming and outgoing calls on the SIP trunk group reaches the
quantity defined in this parameter, the system starts call restriction automatically. The
system stops call restriction automatically when the total number of calls falls back less
than Stop call restriction defined by this command. Its value ranges from 0 to 65535.
The default value is 65535, indicating that the system does not start call restriction.
[Video supported]
It indicates whether one SIP trunk can bear video transmission. It is True by default.
[Time delay value]

10-16

It is the maximum transmission delay that can be tolerated by the trunk group circuit.
The value ranges from 0 to 1023 with the unit as second. When the transmission delay
of the call circuits is greater than the maximum value, it is necessary to install echo
canceller. The parameter is used when satellite circuits are connected. In other cases, it
is set to 0.
[Software parameter of signalling control]
It is the additional signaling flag used to set whether a SIP trunk supports some special
signaling modes. There are 16 options for this parameter. Currently, ten options are
used, and the others are reserved. The meanings of the used options are as follows:
z
Calling party number with ST: If it is selected, an ST signal is added after the end
of the calling number.
Called party number with ST: If it is selected, an ST signal is added after the end of
the called number.
Connected party number with ST: If it is selected, an ST signal is added after the
end of the connected number.
Generic number with ST: If it is selected, an ST signal is added after the end of the
generic number.
Original called party number with ST: If it is selected, an ST signal is added after
the end of the original called number.
Redirecting number with ST: If it is selected, an ST signal is added after the end of
the redirecting number. The redirecting number is the forward sent information
that represents the last redirecting number.
Redirection number with ST: If it is selected, an ST signal is added after the end of
the redirection number. The redirection number is the backward sent information
indicating that the call must reselect route-to-number or forward-transfer number.
Intercept COT: Suppose that a networking of tandem offices is in the format of

ABC. No. 7 trunk is the only inter-office trunk. A SoftX3000 is in tandem
office B. Suppose that A calls C through sending an IAM message to B. If A, in the
IAM message, requests to check the continuity of circuits from A to B, tandem
office B forwards the IAM message to C only after receiving the COT message
(indicating that the continuity check is successful) sent by A. If the option is
selected, office B does not need to wait for the COT message sent by A. Office B
forwards the IAM message to C immediately after receiving it from A.
Peer office no ringback tone: It is valid only for outgoing trunks. If it is selected, the
caller (no matter the caller is in the local office or not) hears the ringback tone sent
by the local office when the local office initiates calls to the peer office. That is, the
peer office is regarded to have no capability of sending the ringback tone by
default. The option is mainly used in Russia.
Anonymous card auth by SX3000: If it is selected, the SoftX3000, through INAP

message, sends the card number and password information sent by the SIP soft
terminal to the U-NICA for authentication (the mode used in R002). If it is not
selected (system default), the SoftX3000, through SIP trunks, sends the card
10-17

number and password sent by the SIP soft terminal to the U-NICA for
authentication.
[ISUP transmit mask]
It transforms the ISUP message encapsulated by the SIP-T trunk on the transmission
direction to adapt to the ISUP signaling used by the peer office. You must configure the
parameter according to the ISUP signaling script provided by Huawei.
[ISUP receive mask]
It transforms the ISUP message encapsulated by the SIP-T trunk on the receiving
direction to adapt to the ISUP signaling used by the peer office. You must configure the
parameter according to the ISUP signaling script provided by Huawei.
[Outgoing type for caller office]
When the local office initiates a call to the peer SoftSwitch through outgoing SIP trunks,
the parameter specifies whether the local office sends SIP message or SIP-T message
to the peer SoftSwitch. It is valid only for outgoing trunks. The meanings of the options
are as follows:
z
Never use SIP-T: It indicates that the local office does not send SIP-T message to
the peer SoftSwitch in all cases. That is, the local office sends SIP message to the
peer SoftSwitch in all cases.
Use SIP-T when caller is ISUP incoming trunk: It indicates that the local office
sends SIP-T message to the peer SoftSwitch only when the caller is an ISUP
incoming trunk. In other cases, the local office sends SIP message to the peer
SoftSwitch.
Use SIP-T when caller is not SIP or H.323 subscriber: It indicates that the local
office sends SIP-T message to the peer SoftSwitch only when the caller is not a
SIP subscriber or an H.323 subscriber. When the caller is a SIP subscriber or an
H.323 subscriber, the local office sends SIP message to the peer SoftSwitch.
Always use SIP-T: It indicates that the local office sends SIP-T message to the
[Incoming type for callee office]

It is valid only for incoming trunks. When the peer SoftSwitch initiates a call to the local
office through incoming SIP trunks, the local office can judge whether the received
incoming signaling is carried in a SIP message or SIP-T message. However, the local
office needs to further judge the terminal type at the called side to determine whether to
reply SIP or SIP-T message to the peer SoftSwitch. The meanings of the options are as
follows:
z
Never use SIP-T: It indicates that the local office does not reply SIP-T messages
but SIP messages to the peer SoftSwitch in all cases.
Use SIP-T when callee is ISUP outgoing trunk: It indicates that the local office
replies SIP-T message only when the callee side is outgoing ISUP trunk. In other
cases, the local office replies SIP message to the peer SoftSwitch.
10-18

z
Use SIP-T when callee is not SIP or H.323 subscriber: It indicates that the local
office replies SIP-T message to the peer SoftSwitch only when the callee is not a
SIP subscriber or an H.323 subscriber. When the callee is a SIP subscriber or an
H.323 subscriber, the local office replies SIP message to the peer SoftSwitch.
Always use SIP-T: It indicates that the local office replies SIP-T message to the
[Privacy level]
It indicates what information related to the caller in the incoming or outgoing SIP/SIP-T
message needs to be shielded by the SoftX3000 to provide privacy services such as
CLIR and RIO for the caller. The meanings of the options are as follows:
z
Privacy user: It indicates to use security service of the user level, that is, to shield
the user information in the field of the SIP message head.
Privacy header: It indicates to use security service of the head field level, that is, to
shield the field of the SIP message head.
Privacy ID: It indicates to use security service of the ID level. If the message
includes field of P-Asserted-ID head (inter-office transmission), the local office
obtains caller information from field of P-Asserted-ID. If the message includes field
of P-Prefered-ID head (caller terminal transmission), the local office obtains caller
information from field of P-Prefered-ID. In other cases, the local office shields the
caller information fully.
Privacy untrusted: The peer end is an untrusty entity, and the caller information is
fully shielded.
If services such as CLIR and RIO are to be implemented, select Privacy ID.
[Release call]
It indicates whether the SoftX3000 supports batch releasing of all calls on the trunk
group when it cannot detect the heartbeat signal periodically sent by the peer SIP
device (SIP trunk might be faulty). It is supported by default. For example, 50 calls are
released per second.
If the batch releasing of calls is enabled, the system will not send many BYE messages
when SIP trunk is faulty. Therefore, the overload of system resources such as memory
usage and CPU usage during heavy traffic does not happen.
10.3 Configuring H.323 Trunk Data

10.3.1 Overview
The H.323 trunk data is used to configure interconnection information between the
SoftX3000 and other softswitch and between the SoftX3000 and GK or GW in the
traditional H.323 network, such as IP address of other softswitch, IP address of GK,
alias of GW, CALL port number, and RAS port number. The H.323 trunk data
10-19

configuration must not be done before the equipment data, local office data, charging
data, protocol data and routing data is configured. See Figure 10-1.
data, routing data and call barring data will be referenced in the H.323 trunk data.
Besides, the Network management source code defined in the H.323 trunk data will
be referenced when the network management data is configured. Table 10-5 shows the
details.
Table 10-5 Parameter referencing relationship between H.323 trunk data and other
data
Input parameter
Name
Output parameter
Defined in
Referenced
in
Name
Call source code
Basic Call Data
Network
management
source code
Network
management
data
Charging data

source code
Charging data
Subroute number
Routing data
Caller number discrimination

group number (optional)
Call barring data
Call barring group (optional)
Call barring data
II. Preparations
Before configuring the H.323 trunk data, make sure that all preparations are done as
SN
Item
Remark
Position of the SoftX3000 in

H.323 network
To determine the type of the H.323 trunk at the

SoftX3000 side
IP address of SoftSwitch or
GK
For interworking with other SoftSwitch or GK
CALL port number
For interworking with other SoftSwitch
RAS port number
For interworking with GK
GK entity type
GK ID

10-20


Table 10-7 lists the general steps for configuring the H.323 trunk data.
Step
Description
Command
Add H.323 virtual IP list
ADD IPLIST
Add H.323 trunk group
ADD H323TG

mutually.
10.3.2 Adding Virtual IP List (Optional)

I. Related commands
Command
Function
ADD IPLIST
To add virtual IP list
RMV IPLIST
To remove virtual IP list
MOD IPLIST
To modify virtual IP list
LST IPLIST
To list virtual IP list

data configuration.
In some countries or regions, the carrier might have already fully developed an H.323
network. When you connect such an H.323 network to an NGN, the carrier might
require that multiple H.323 gateways access the SoftX3000 in a trunk group model.
They need this model reflected in the bill. Therefore, you need to use ADD IPLIST to
configure a list of IP address and use it to a virtual H.323 trunk.
III. Description of parameters

[IP list number]
It uniquely defines a list of IP address in the SoftX3000. Here are the configuration
guidelines:
z
An IP list contains multiple IP address. An IP address is included in one IP list only.

10-21

z
The IP list is used to authenticate the incoming calls from a virtual H.323 trunk.
When a virtual H.323 incoming trunk initiates a call, and the IP address of the peer
H.323 entity is included in the IP list defined in the office, the authentication
succeeds; otherwise the authentication fails and the SoftX3000 rejects the call.
[IP address]
It defines a specific IP address in the IP list. The IP address is the one of an H.323 entity
interacting the local office through the virtual H.323 trunk.
[Mask]
It defines the subnet mask of the IP address.
10.3.3 Adding H.323 Trunk Group

I. Related commands
Command
Function
ADD H323TG
To add H.323 trunk group
RMV H323TG
To remove H.323 trunk group
MOD H323TG
To modify H.323 trunk group
LST H323TG
To list H.323 trunk group

Before adding H.323 trunk group, use the related commands to obtain the following
z
Call barring group number (optional): LST GRPAC
Module number of FCCU or FCSU (optional): LST BRD
Note:
This section only introduces the parameters closely related to H.323 trunk group. For
the other parameters, refer to online help or 10.4.2

10-22
Adding No. 7 Trunk Group.

No. 7 trunk group, R2 trunk group, PRA trunk group, AT0 trunk group, or V5 trunk group.
Trunk groups are uniformly numbered in the network. The value ranges from 0 to
65534.
[Call source code]
[Sub-route number]
[Group direction]
It specifies the call connection direction of the H.323 trunk group. The default option is
Bidirectional trunk. The parameter options are described as follows:
z
Incoming trunk: It indicates that only the incoming calls from the opposite office are
processed.
Outgoing trunk: It indicates that only the outgoing calls to the opposite office are
processed by default. If the controlling software parameter is modified, the
incoming calls from the opposite office can also be processed.
Bidirectional trunk: It indicates that the calls from and to the opposite office are
processed.
[Trunk group name]

[Call-in authority]

10-23


[EC capability]
It is one of the parameters used for interworking with the opposite office. It controls the
H.323 trunk to enable the EC function. The default option is YES, indicating that the
EC function is enabled.
[H323 trunk type]
It is one of the parameters used for interworking with the opposite office. It specifies the
type of the H.323 trunk at the SoftX3000 side. The parameter options are described as
follows:
z
H323 peer trunk: It is applicable to the case that the local office and opposite office
are both SoftSwitch.
H323 GW trunk: It is applicable to the case that the local office is a GK and the
opposite office is a GW in the same H.323 network.
H323 GK trunk: It is applicable to the case that the local office and the opposite
office are both GKs.
H323 outer GK trunk: It is applicable to the case that the local office is a GW and
the opposite office is a GK in the same H.323 network.
H323 virtual trunk: It is applicable to the case that the local office is a GK and the
opposite office is a GW under the control of other GK (supporting RAS protocol,
but not supporting the Q.931 protocol). It is usually used with H.323 GK trunk only
for incoming calls. The purpose is to charge and authenticate the incoming calls
from the GW.
[Trunk IP address]
It is one of the parameters used for interworking with other SoftSwitch or GK. It
specifies the IP address of the opposite office (SoftSwitch or GK). This parameter is
valid only when the H323 trunk type is H323 peer trunk, H323 GK trunk, or H.323
outer trunk.
[CALL trunk port number]
It is one of the parameters used for interworking with other SoftSwitch. It specifies the
number of the TCP port processing the call signaling in the opposite office (SoftSwitch),
and the default value is 1720. This parameter is valid only when H323 trunk type is
H323 Plain Trunk.
[RAS trunk port number]

10-24

It is one of the parameters used for interworking with GK. It specifies the number of the
UDP port processing the RAS signaling in the opposite office (GK), and the default
value is 1719. This parameter is valid only when H323 trunk type is H323 GK trunk
or H323 outer GK trunk.
It specifies the module number of the FCCU or FCSU processing the call signaling of
the H.323 trunk. This parameter is valid only when H323 trunk type is H323 GW
Trunk, and it must be defined in the ADD BRD command before being referenced
here.
[GW alias]
It is one of the parameters used for interworking with GW. It specifies the alias of the
GW (such as A8010 Expert) connected to the local office (GK). This parameter is valid
only when H323 trunk type is H323 GW Trunk".
[Entity name]
When the type of trunk is H323 Outer GK Trunk, this parameter is available to
specifically describe an outer GK.
[Entity type]
It is one of the parameters used for interworking with GK. It specifies the entity type of
the opposite office (GK). This parameter is valid only when H323 trunk type is H323
Outer GK Trunk.
z
Primary GK: It indicates that the SoftX3000 first registers with this GK during
initialization.
Alternate: It indicates that the SoftX3000 registers with this GK if it fails to register
with the primary GK.
[Gatekeeper ID]
It is one of the parameters used for interworking with GK. It specifies the alias of the
opposite office (GK). This parameter is valid only when H323 trunk type is H323
Outer GK Trunk.
[Support gatekeeper release]
It specifies whether the opposite office (GK) can control the local office to release the
calls. This parameter is valid only when H323 trunk type is H323 Outer GK Trunk.
The default option is YES, indicating that the GK can control the local office to release
the calls.
[Manufacturer code]
It specifies the code of the upper GK interconnecting with the SoftX3000. It is valid only
when "H323 trunk type is set to H323 GK trunk.
[Incoming trunk TOS]

10-25

It specifies the TOS conversion index used by the incoming H.323 trunk. It is valid only
when H323 trunk type is set to H323 GK trunk. The parameter must be defined by
the command ADD TOSC before being referenced here.
[Outgoing trunk TOS]
It specifies the TOS conversion index used by the outgoing H.323 trunk. It is valid only
when H323 trunk type is set to H323 GK trunk. The parameter must be defined by
the command ADD TOSC before being referenced here.
[Stop call restriction]
When the total number of calls is less than the quantity defined in this parameter, the
system stops the enabled call restriction automatically. Its value ranges from 0 to 65535.
The default value is 65535, indicating that the system cannot stop call restriction
automatically.
The value of stop call restriction must be smaller than that of maximum caller number
restriction. For example, if the parameter stop call restriction is set to 1800 and
maximum caller number restriction is set to 2000, the system starts call restriction
automatically when the total number of incoming and outgoing calls on one H.323 trunk
group reaches 2000, and stops call restriction automatically when the total number of
calls falls back less than 1800 ( 1799).
[Maximum caller number restriction]
It defines the maximum number of calls allowed on one H.323 trunk group. That is,
when the total number of incoming and outgoing calls on the H.323 trunk group reaches
the quantity defined in this parameter, the system starts call restriction automatically.
The system stops call restriction automatically when the total number of calls falls back
less than Stop call restriction defined by this command. Its value ranges from 0 to
65535. The default value is 65535, indicating that the system does not start call
restriction.
[Video supported]
It indicates whether one H.323 trunk can bear video transmission. It is True by default.
[H245 route supported]
It controls whether the SoftX3000 forwards the H.245 route message sent by the H.323
equipment when the caller and callee are both H.323 equipment, and at least one of
them uses slow start work mode. The default option is No.
z
If it is set to No, direct route exists between the calling and called H.323
equipment. That is, the calling and called equipment exchanges H.245 route
message directly. No H.245 messages between the caller and callee are
forwarded by the SoftX3000. Therefore, the SoftX3000 cannot obtain information
such as media channel attribute and provide related data on bills

10-26

If it is set to Yes, GK route is used between the calling and called H.323
equipment. That is, the calling and called equipment exchanges H.245 route
message through GK (SoftX3000).
10.4 Configuring No. 7 Trunk Data

10.4.1 Overview
The No. 7 trunk data is used to configure the No. 7 trunk related information used for
interconnection between the SoftX3000 and PSTN switch, such as signaling type of No.
7 trunk circuit, and circuit identification code. The No. 7 trunk data configuration must
not be done before the equipment data, local office data, charging data, media gateway
data, signaling data and routing data is configured. See Figure 10-1.
data, media gateway data, and routing data will be referenced in the No. 7 trunk data.
Besides, the Network management source code defined in the No. 7 trunk data will be
referenced when the network management data is configured. Table 10-8 shows the
details.
Table 10-8 Parameter referencing relationships between No. 7 trunk data and other
data
Input parameter
Name
Output parameter
Defined in
Name
Call source code
Local office data
Network
management
source code
Network
management
data
Charging data

source code
Charging data
Equipment ID of trunk media

gateway (TMG)
Media gateway
data
Subroute number
Routing data

Call barring data
Call barring group number

(optional)
Call barring data

10-27
Referenced in

II. Preparations
Before configuring the No. 7 trunk data, make sure that all preparations are done as
SN
Item
Remark
Originating signaling Point Code

(OPC) of the signaling in No. 7 trunk
group
For interworking with PSTN switch
Destination signaling Point Code

(DPC) of the signaling in No. 7 trunk
group
Group direction of No. 7 trunk group,

including outgoing trunk, incoming
trunk or bidirectional trunk
Signaling type of No. 7 trunk group,

including TUP and ISUP
Circuit selection mode of No. 7 trunk

group
It must be correctly planned to avoid

that a circuit is occupied by two
offices at the same time.
Range of circuit numbers for No. 7

trunk circuits
These are unified logical numbers

assigned inside the SoftX3000 to No.
7, PRA, and R2 trunk circuits. The
corresponding physical numbers
assigned at the TMG are specified in
the start circuit termination
identifier parameter.
Termination identifier of circuit number
For interworking with TMG
Start CIC

Table 10-10 lists the general steps for configuring the No. 7 trunk data.
Step
Description
Command
Add carrier access code (optional)
ADD CAC
Add carrier selection code (optional).
ADD CSC
Add originating network ID (optional).
ADD ONID
Add No. 7 trunk group
ADD N7TG
5:
Add part calling line identification (optional)
ADD PCLI

10-28

Step
Description
Command
Add No. 7 trunk circuit
ADD N7TKC
Add PCM port (optional).
ADD PCMPORT

the No. 7 trunk data is configured.
ADD N7TG
[Equipment ID]
[Group direction]
ADD N7TKC
[Module]
[Trunk group]
[Start circuit]
10.4.2 Add Carrier Access Code (optional)

I. Related commands
Command
Function
ADD CAC
To add carrier access code
RMV CAC
To add carrier access code
MOD CAC
To modify carrier access code
LST CAC
To list carrier access code

data configuration.
By default, the SoftX3000 does not authenticate the CAC in the pre-selected call. The
SoftX3000 does not authenticate the CAC of the calls initiated by the ISUP incoming
trunk until you use ADD CAC to add the authentication data for the ISUP incoming
trunk.

10-29


It specifies the number of the incoming trunk group of the carrier access code to be
configured. This parameter must be defined in the command ADD SIPTG, ADD
H323TG, ADD N7TG, or ADD N1TG before being referenced here.
It instructs the SoftX3000 to authenticate the CAC of the calls initiated by the ISUP
incoming trunk by specifying the number of the incoming trunk. The parameter must
first be defined by ADD N7TG before it can be used here.
[CAC source code]
It specifies the part of the IAM message (received from the peer office) in which the
local office shall retrieve the CAC information for authentication. Here are the
descriptions of options:
z
By callee number: Retrieve from callee number.
By CAC IE: Retrieve from a special information element.
This parameter is used in Argentina only.

[CAC discriminate]
It specifies whether the local office shall authenticate the CAC in the IAM message
received from the peer office. Here are the descriptions of options:
z
No discriminate: Usually used when the local office is a local exchange
No discriminate send: Reserved option.
Discriminate: Usually used when the local office is a gateway office.
[CAC send]
It is a reserved parameter.
[CAC number]
10.4.3 Adding Carrier Selection Code (optional)

I. Related commands
Command
Function
ADD CSC
To add carrier selection code
RMV CSC
To remove carrier selection code
MOD CSC
To modify carrier selection code
LST CSC
To list carrier selection code

10-30


data configuration.
The carrier access code is used when a gateway office authenticates a pre-selected
call. That is, you can set this parameter only when the local office serves as a gateway
office.
When the local office receives a call from the peer gateway office, and its ISUP trunk
group has been configured with authentication information using ADD CAC, the
SoftX3000 shall start CAC authentication for the calls from the ISUP incoming trunk.
The basic authentication procedure is as follows:
1)
After receiving the IAM containing "carrier selection code" from the peer office, the
local office judges if the carrier selection code in the IAM is the same as the "Local
office CAC" in the local office information table (which can be configured with the
command SET OFI). If so, the authentication succeeds, and the local office will
delete the parameter "carrier selection code" in the IAM when transferring the
message to the lower-level office. If not, carry out the following actions.
2)
The local office judges if the carrier selection code table (which can be configured
with the command ADD CSC) contains the "carrier selection code" in the IAM. If
so, the authentication succeeds, and the local office will transparently transfer the
IAM to the lower-level office. If not, the local office will reject the call.

[Carrier selection code]
It defines the carrier selection code to be configured, ranging from 0 to 9 and A to E with
a maximum length of six characters. The parameter is used when the local office is a
gateway office, and needs to authenticate the pre-selected call initiated by the ISUP
incoming trunk; that is, the local office shall authenticate the "carrier selection code" in
the IAM message sent by the peer office. The parameter must be allocated uniformly by
the telecom department on nation-wide basis.
10.4.4 Add Originating Network ID (optional)

I. Related commands
Command
Function
ADD ONID
To add originating network ID
RMV ONID
To remove originating network ID
MOD ONID
To modify originating network ID
LST ONID
To list originating network ID

10-31


data configuration:
The original network ID is used by the peer office to authenticate a pre-selected call.
The basic authentication procedure is as follows:
z
When a local caller uses the pre-selection service, the local office (that is,
originating office) will send an IAM containing this parameter in the local office
information table (which can be set with the command SET OFI) through the
outgoing trunk. This parameter will be transmitted transparently to the terminating
office finally during the call connection process.
Upon receiving the IAM, the terminating office judges if the originating network
identifier table (which can be set with the command ADD ONID) contains this
parameter in the IAM. If so, the authentication succeeds, and the terminating office
will connect the call. If not, the terminating office will release the call (the release
cause value is 21).
By default, the SoftX3000 does not authenticate the ONID for calls of pre-selected
routes. When you set the bit7 of call internal parameter 8 (P122) to 0, the SoftX3000
shall authenticate the ONID of the calls from the ISUP incoming trunk.

[Originating network ID]
It defines the originating network ID to be configured, ranging from 0 to 9 and A to E
with a maximum length of six characters. The parameter is used when the local office is
a gateway office, and needs to authenticate the pre-selected call initiated by the ISUP
incoming trunk; that is, the local office shall authenticate the "carrier selection code" in
the IAM message sent by the peer office. It is one of the important parameters for the
interconnection of two offices. The two offices must negotiate the value of the
parameter.
10.4.5 Adding No. 7 Trunk Group

I. Related commands
Command
Function
ADD N7TG
To add No. 7 trunk group
RMV TG
To remove No. 7 trunk group
MOD N7TG
To modify No. 7 trunk group
LST TG
To list No. 7 trunk group

10-32


Before adding No. 7 trunk group, use the related commands to obtain the following
z
Equipment ID of the TMG: LST MGW

[Equipment ID]
It specifies the equipment ID of the TMG (such as TMG8010 or UMG8900) providing
No. 7 trunk circuits. This parameter must be defined in the ADD MGW command before
[Group direction]
It specifies the call connection direction of the No. 7 trunk group. The default option is
Bidirectional trunk The parameter options are described as follows:
z
Incoming trunk: It indicates that the local office only processes the incoming calls
from the opposite office.
Outgoing trunk: It indicates that the local office only processes the outgoing calls
to the opposite office.
Bi-directional trunk: It indicates that the local office processes the calls from and to
the opposite office.
[Sub-route number]
[OPC]
OPC of the No. 7 trunk group. The default code is the signaling point code of the local
office in the national network defined in the SET OFI command. If it is required to use
signaling point code in other signaling network, such as international network, you must
specify it separately.
Due to the limitation of the No. 7 signaling CIC length (12 bits), two offices can enable a
maximum of 4096 No. 7 trunk circuits in the case of using a single signaling point code.
10-33

If it is necessary to enable more trunk circuits, multi-signaling-point-code is required in

either the local office or the peer office. If the multi-signaling-point-code is used in the
local office, this parameter must be defined in the ADD OFI command before being
referenced here.
[DPC]
DPC of the No. 7 trunk group. The system uses the DPC1 defined in the ADD OFC
command by default.
Due to the limitation of the No. 7 signaling CIC length (12 bits), two offices can enable a
maximum of 4096 No. 7 trunk circuits in the case of using single signaling point code. If
it is necessary to enable more trunk circuits, multi-signaling-point-code is required in
either the local office or the peer office. If the multi-signaling-point-code is used in the
peer office, this parameter must be defined in the ADD OFC command before being
referenced here.
[Trunk group name]
[Call source code]
[Circuit type]
It specifies the signaling type used by the No. 7 trunk group, including ISUP and TUP.
The default type is ISUP.
[Circuit selection mode]
It specifies the policy for selecting the trunk circuits in a trunk group. The default mode
is Master/slave. The options are
z
Minimum: The system always selects a trunk circuit from the minimum number.
The preferential selection of the trunk circuits can be realized through this mode.
Maximum: The system always selects a trunk circuit from the maximum number.
Cyclic: The system selects a circuit from the next one to the last selected circuit
number each time. If the last selected number is the maximum one, the next one is
the minimum number.
FIFO: For all the circuits of the trunk group, the system selects a circuit according
to the first in, first out principle. That is, the circuit released first will be selected
first.
Master/slave: For the circuits controlled by the local office, the system selects a
circuit according to the first in, first out principle. For the circuits not controlled by
the local office, the system selects a circuit according to the first in, last out
principle. That is, the circuit released first will be selected last.

10-34

Random: The system selects a trunk circuit randomly. This mode is seldom used.
User side allocation: The system selects a circuit according to the instruction from
the user side.
If the No. 7 trunk group is a bidirectional one, it is recommended to set Circuit selection
mode to Master/slave for the purpose to prevent two offices occupying the same
circuit at the same time.
[Connect satellite circuit]
It identifies whether the No. 7 trunk is carried over a satellite circuit. You need to set it
according to the actual conditions. Generally, the option is NO".
[International call]
It indicates whether the local office sets the bit national/international call indicator of
the forward call indicator parameter to 1 in the Initial Address Message (IAM) sent to
a lower national office or a peer international office when the SoftX3000 connects
international incoming or outgoing calls. 1 means that the call is processed as an
international call.
The default value is No, indicating that the local office does not process the
international calls on the No.7 trunk group in the above-mentioned way. This feature is
mainly used in Hong Kong.
[Number incomplete]
It specifies whether the SoftX3000 sets the bit caller number incomplete indicator of
the parameter caller number in the IAM to "1, which indicates that the caller number
is incomplete.
The default value is No, indicating that the local office does not process the IAM in the
above-mentioned way. This feature is mainly used in Hong Kong.
[Call-in authority]
[DOD2]
This parameter is available only to outgoing trunks. It is used together with the software
parameters TUP operation reserved parameter 3 (P10) and TUP operation reserved
parameter 4 (P11) to control the preset value of the caller category in the IAM/Initial
Address Message with Information (IAI) sent by the local office.
10-35

If it is set to Yes and bit 2 of the TUP operation reserved parameter 4 is set to 0, the
preset value of the caller category in the IAM/IAI is bit 138 of the TUP operation
reserved parameter 3.
[CLIR flag]
It is used to manually force to set the value of CLIP flag in the Initial Address Message
(IAM) or Initial Address Message with Information (IAI) of the incoming call signaling or
outgoing call signaling, that is, the original value of CLIP in the call signaling is invalid.
z
Nothing: It is the default option, indicating that the original value of CLIP flag in
the call signaling need not be changed necessarily.
Incoming CLIR: Indicates to set the CLIP flag bit in IAM or IAI in the incoming call
signaling to 1 (CLIR) forcedly.
Outgoing no CLIR: Indicates to set the CLIP flag bit in IAM or IAI in the outgoing
call signaling to 0 (CLIP allowed) forcedly.
[Send initial tone]

This parameter is available only to incoming trunks. It is used together with the software
parameters TUP operation reserved parameter 3 (P10) and TUP operation reserved
parameter 4 (P11) to control the preset value of the caller category in the IAM/IAI
received by the local office.
If it is set to Yes and bit 2 of the TUP operation reserved parameter 4 is set to 0, the
preset value of the caller category in the IAM/IAI is bit 70 of the TUP operation
reserved parameter 3.
[Initial tone type]
It specifies the type of the initial tone. This parameter is valid only when the Send initial
tone is set to YES.
[Send exceptional tone]
It controls the local office to send exceptional tone to the opposite office through the
Address Complete Message (ACM) when the call through the incoming trunk fails. This
parameter is available only to incoming trunks.
z
If the parameter is set to NO, the local office will send Release (REL) message to
the opposite office when the call fails. In this case, the call will be released and the
opposite office will send busy tone to the caller.
If the parameter is set to YES, the local office will send ACM to the opposite
office when the call fails. In this case, the call will be held temporarily and the local
office will send exceptional tone to the caller through the incoming trunk; if the
caller hangs up or the timer times out, the call will be released.
[Exceptional tone type]

It specifies the type of the exceptional tone. This parameter is valid only when the
Send exceptional tone is set to YES.
10-36

[Use opposite pulse]
It is used for the inter-office trunk cooperation in the real-time charging. When it is set to
YES, its meanings for outgoing trunk and incoming trunk are different.
z
Outgoing trunk: When there is an outgoing call from the trunk group, the local
office needs to receive the charging pulse in the signaling sent back from the
opposite office, and the opposite office needs to cooperate to send charging pulse
to the local office through signaling.
Incoming trunk: When there is an incoming call to the trunk group, the local office
needs to send charging pulse to the opposite office through signaling, and the
opposite office needs to cooperate to receive the charging pulse sent from the
local office through signaling.
[CAMA]
This parameter is available only to incoming trunks, used to set whether the local office
performs centralized accounting operations on the incoming trunk. If the value is YES,
the local office adopts the centralized accounting mode for the incoming trunk. In this
case, when the opposite office originates a call through the incoming trunk, the local
office requests the calling number on initiative through signaling if the signaling from the
originating office does not carry the calling number.
[Can request caller number]
It sets whether to request caller number. This parameter is available only to incoming
trunks. When the Whether request caller number parameter is set to YES, if the
incoming call signaling through the trunk does not contain caller number, this parameter
is used to ask the local office to request caller number from the opposite office. The
default option is YES, indicating that the local office can request caller number on
initiative. However, if this feature affects connection or connection time, the option can
be set to NO.
[Connect without valid caller number]

10-37

It sets whether the local office gets a call through if the incoming call signaling through
the trunk does not contain caller number or the contained number is invalid. This
parameter is available only to incoming trunks, and the default option is YES.
[Caller number provision mode]
When the opposite office originates a call through the incoming trunk, this parameter
indicates how the local office obtains the calling number from the incoming trunk if the
call signaling from the opposite office contains no calling number. This parameter is
available only to incoming trunks.
z
Trunk line ID: It indicates that the calling number is an ID of a trunk circuit.
Default number: It indicates that the calling number is the default one pre-defined
in this command.
If the opposite office sends the calling number in the incoming call signaling, the local
office will use it and this parameter is invalid.
[Default caller number]
If the Caller number provision mode of the trunk group is Default number and no
caller number is contained in the call signaling message sent by the peer office when it
originates a call through the incoming trunk, the local office will use the default caller
number. The parameter is valid only for incoming trunks.
[Call barring group number]
It specifies the call barring group to which the trunk group belongs. The parameter
configuration principle is described as follows:
z
If the value is not specified or 65535, it indicates that the call barring function is not
enabled.
If the black/white list barring is used, the preset three call barring groups can be
referenced directly, that is black list 60001, white list 60002 and ordinary call
barring group 65534.
If other call barring groups are expected, this parameter must be defined in the
SET GRPAC command before being referenced here.
During the number analysis process of inter-group call barring authentication, the
SoftX3000 shall authenticate twice the caller, called prefix, and the callee. To help you
correctly use the parameter, here is an illustration of the inter-group call barring
authentication procedure:
1)
When a local subscriber or incoming trunk initiates a call, the SoftX300 first
authenticates the call barring group number of the caller or incoming trunk (caller
barring group number), by comparing with the call barring group of the called
prefix (called barring group number, configured by ADD CLDGRP, 65534 by
default). If the authentication succeeds the SoftX3000 will proceed with
subsequent procedures; otherwise, the SoftX3000 will reject the call.
2)
When the call passes the first inter-group call barring authentication, the
SoftX3000 will again authenticate the call barring group number of the caller or
10-38

incoming trunk (caller barring group number) and that of the callee or outgoing
trunk (called barring group). If the authentication succeeds the SoftX3000 will
proceed with subsequent procedures; otherwise, the SoftX3000 will reject the call.
[Upper seizure threshold]
It defines the maximum seizure duration of a trunk circuit. If a trunk circuit has been
seized for longer than this threshold, the system will check the circuit status and
generates an alarm. Its value ranges from 0 to 65535 with the unit as second. 0 or
65535 indicates that the threshold is invalid.
[Lower seizure threshold]
It defines the minimum seizure duration of a trunk circuit. If a trunk circuit has been
seized for shorter than this threshold, the system will count one over-short seizure. If
the number of over-short seizures is bigger than the value of the lower 8 bits in the TUP
operation reserved parameter 1, the system will generate an alarm. Its value ranges
from 0 to 65535 with the unit as second. 0 or 65535 indicates that the threshold is
invalid.
[Continuity check]
It sets whether the local office conducts continuity check. The default value is No,
indicating that the local office supports continuity check response only. If it is set to
Yes, it indicates that the local office supports both start and response of continuity
check.
[Time delay value]
It sets the maximum transmission delay allowed by the circuits of a trunk group. Its
value ranges from 0 to 1023 with the unit as second. If the transmission delay of a call
through the circuit segments is larger than the maximum transmission delay allowed by
the system, it is required to configure echo canceller. This parameter is generally used
for the case of connecting satellite circuits. In other cases, set it to 0.
[Group message timeout to single]
When the local office cannot receive the acknowledgment messages from the peer
office for the sent group messages, this parameter is used to set whether the local
office forwards the related signaling message, that is, to send RSC message instead of
GRS message. Generally, the option is set to NO.
[Transmission capability]
It is one of the route selection conditions. It specifies the service types that the route
can bear, for example, voice service, digital service and video service. Generally, the
option is set to All.
[Transmission mode]
It specifies the transmission rates that the trunk group can provide, including packet
mode, 64 kbit/s, 128 kbit/s and 1920 kbit/s. If there is no special requirement, the option
is set to Multiple rate.
10-39

[CIC change type]

It is mainly used for the self-loop test of the two No. 7 trunk groups (outgoing trunk E1
and incoming trunk E1) with the same office direction in the local office. The
z
When the self-loop test is not enabled, you must set this parameter to No change;
otherwise, the trunk interconnection will fail.
When the self-loop test is enabled, if the "CIC change type of the outgoing trunk
group is set to Increase, the "CIC change type of the incoming trunk group must
be set to Decrease, and conversely the same.
[CIC change value]

It sets the CIC change value. Because the self-loop test is performed between two E1s,
the CIC change value must be the integral times more than 32. This parameter is valid
only when CIC change is necessary.
[Availability]
It defines the times that a trunk group can be selected in the corresponding subroute.
Its value ranges from 0 to 255. In a subroute, every time the system selects the trunk
group, the available times of the trunk group will be decreased by 1. When the available
times become 0, the system cannot select the trunk group. If the available times of all
trunk groups in the corresponding subroute become 0, those times will be assigned
with new values, which intend to distribute the traffic over all trunk groups of the
subroute according to the expected principle. The default value is 255, indicating that
the parameter is invalid.
It sets whether an ISUP trunk supports some special services or applications. There
are 16 options for this parameter. Currently, only six options are used, and the others
are reserved. The meanings of the options are as follows:
z
Wide area network Centrex service: It is used together with bit 4 of the parameter
ISUP operation reserved parameter 9 (P26). If you select this option and bit 4 of
the ISUP operation reserved parameter 9 is 0, the local office will send a short
number contained in the IAM to the peer office in the WAN Centrex service.
Blocked ISUP circuit cannot be reset: If you do not select this option and the circuit
is blocked at the peer office currently, the circuit will be idle after reset. If you select
this option (mainly applicable to Hong Kong), the blocked circuit will still be
blocked after reset. At this time, you can only use the unblocking command to
release the blocked circuit.
Use default caller number in incoming call: It is used together with bit 12 of the
parameter ISUP operation reserved parameter 9 (P26). If you select this option
and bit 12 of the ISUP operation reserved parameter 9 is 0, the local office will
mask the real caller number sent by the opposite office and use the default caller

10-40

number in this command when the peer office originates a call through the
incoming trunk to the local office.
z
Send default caller number in outgoing call: It is used together with bit 13 of the
parameter ISUP operation reserved parameter 9 (P26). If you select this option
and bit 13 of the ISUP operation reserved parameter 9 is 0, the local office will
mask the real caller number and use the default caller number in this command
when the local office originates a call through the outgoing trunk to the peer office.
Send ringback tone for HK: It is available to incoming trunks only. If you select this
option, the local office (no matter whether it is a terminating office or not) will send
the ringback tone to the peer office when the peer office originates a call through
the incoming trunk. This feature is mainly applicable to Hong Kong.
IDR/IDS flag: It indicates whether the No. 7 trunk group uses IDR/IDS signaling
flow when implementing the MCID service. If the option is selected (mainly used in
Russia), IDR/IDS signaling flow is to be used. If not, INR/INF signaling flow is to be
used.
[Network management source code]

It defines the network management attributes of a trunk group. This parameter is
available only to incoming trunks and will be referenced when the network
management data is configured.
[Idle circuits for weak call restriction]
It is used together with the NM trunk reserved control instruction for call restriction.
Idle circuits for weak call restriction must be more than those for forced call restriction.
The applications of the parameter are as follows:
z
No call restriction: When the actual idle circuits of the controlled trunk group are
more than or equal to those for weak call restriction, the NM trunk reserved control
function is disabled, that is, the system does not start call restriction.
Weak call restriction: When idle circuits for forced call restriction actual idle
circuits of the controlled trunk group < idle circuits for weak call restriction, the
system implements call restriction by percentage of weak call restriction.
Forced call restriction: When the actual idle circuits of the controlled trunk group
are less than those for forced call restriction, the system implements call restriction
by percentage of forced call restriction.
[Idle circuits for forced call restriction]

It is used together with the NM trunk reserved control instruction for call restriction.
Idle circuits for weak call restriction must be more than those for forced call restriction.
Refer to the above for details.
[Bar forwarded call]
It sets whether to bar the forwarded calls unconditionally. The default option is NO,
indicating no barring. If the value is set YES, the system will bar all the calls forwarded
through the trunk group.
10-41

[Default connect]
If querying caller number discrimination group failed, it is used to set whether to get the
call through. The default option is YES, indicating that the call will be connected
through.
[Whether request caller number]
If the incoming call signaling through the trunk does not contain caller number, it is used
to define whether the local office requests caller number from the opposite office on
initiative. It is valid only for incoming trunks. The default option is NO, indicating that
the local office will not request caller number on initiative.
[Request original called number]
It sets whether to request the original called number. This parameter is available only to
incoming trunks. In a forwarded call (the call redirection indicator is 1), if the incoming
call signaling through the trunk does not contain the original called number, this
parameter is used to tell the local office whether to request the original called number
from the opposite office. The default option is NO, indicating that the local office will
not request the original called number on initiative.
It should be noted that if the incoming trunk needs to conduct caller number
discrimination, the system only discriminates the original called number in the
forwarded call instead of the caller number. If the opposite office does not send the
original called number on initiative: for the TUP trunk, the original called number can be
obtained when this parameter is set to YES; for the ISUP trunk, the local office can
only get the false number even when this parameter is set to YES. Therefore, for the
ISUP trunk, if it is required to discriminate the original called number in the forwarded
call, the opposite office must send the original called number on initiative.
[Connect without valid original called number]
This parameter is available only to incoming trunks. It sets whether the local office gets
a call through if the incoming call signaling through the trunk does not contain the
original called number or the contained number is invalid in a forwarded call (the call
redirection indicator in the signaling message is 1). The default option is YES.
[Overlap send called number]
It specifies whether a trunk group supports overlap code sending mode. The SoftX3000
supports the following two code sending modes:
z
Overlap code sending: When the system receives enough digits of the called
number for judging the route, it sends them to the opposite office through the
signaling Initial Address Message (IAM) or Initial Address Message with
Information (IAI), and then sends the remained digits of the called number one by
one through other signaling messages, for example, Subsequent Address
Message with One signal (SAO) or Subsequent Address Message (SAM).
Group code sending: After the system collects all the digits of the called number, it
sends them to the opposite office through one signaling message.
10-42

The overlap code sending mode features fast connection but it occupies a plenty of
CPU resources. The group code sending mode occupies a few of CPU resources, but
the connection is slow, which might affect the quality of the telecom services. The
default mode is overlap code sending. However, when the SoftX3000 interconnects
with a switch complying with ANSI through the No.7 trunk group, you must set this
parameter to No.
[Circuit pool number]
It defines the number of circuits in a trunk group reserved for subscribers with higher
priority. When the number of idle circuits in the trunk group equals to the number
defined here, the system only allocates trunks for the new calls originated by the
subscribers with higher priority or those with priority (defined in SET PFXPRI). Its value
ranges from 0 to 255. The default value is 255, indicating no reserved circuits.
[Software parameter of signaling control]
It specifies whether ISUP trunk supports some special signaling modes. There are 16
options for this parameter. At present, nine options are used, and the others are
reserved. The meanings of the options are as follows:
z
Calling party number with ST: If this option is selected, ST signal will be added at
the end of a calling number.
Called party number with ST: If this option is selected, ST signal will be added at
the end of a called number.
Connected party number with ST: If this option is selected, ST signal will be added
at the end of a connected number.
Generic number with ST: If this option is selected, ST signal will be added at the
end of a generic number.
Original called party number with ST: If this option is selected, ST signal will be
added at the end of an original called number.
Redirecting number with ST: If this option is selected, ST signal will be added at
the end of a redirecting number. The redirecting number is the information sent
forward and indicates the number to which a call is sent at last.
Redirection number with ST: If this option is selected, ST signal will be added at
the end of a redirection number. The redirection number is the information sent
backwardly and indicates the number to which a call is forwarded.
Intercept COT: Suppose the networking is ABC, only No.7 trunks are used
between offices, and the SoftX3000 acts as transit office B. By default, when office
A calls office C, it sends an IAM to office B. If office A requests continuity check to
the circuit between office A and office B through the IAM, transit office B transfers
the IAM to office C only after receiving the Continuity (COT) message from office A
indicating successful continuity check. If this option is selected, it indicates that the
local office (transit office B) transfers the IAM to office C immediately after
receiving it from office A, without waiting for the COT message from office A.

10-43

z
Peer office no ringback tone: This option is available to outgoing trunks only. If this
option is selected, the caller (of the local office or not) can hear the ringback tone
sent by the local office when the local office originates a call to the peer office
through outgoing trunks. That is, the local office takes it for granted that the peer
office cannot send the ringback tone. This feature is used in Russia.
[Extended overlap send called number]

It sets whether a No.7 trunk group supports extended overlap code sending mode, that
is, whether the trunk group can send the remained digits of the called number to the
peer office through an SAM.
It is different from the overlap code sending mode. In the latter mode, the remained
digits of the called number can be sent to the peer office in one or several SAOs/SAMs.
However, this mode only allows that the remained digits are sent to the peer office in
one SAM.
[Disconnection procedure]
In ISUP trunk, when the circuit release mode is Calling party release or Called party
release, if the slave party (not controlling the release) hangs up while the master party
(controlling the release) hangs on, this parameter is used to control which message the
slave party resident office sends to the opposite office. The opposite office will not
release the call after receiving the message. There are different specifications in
different countries. For example, this message in China is Suspend (SUS).
[Inter-gateway circuit flag]
It specifies whether the SoftX3000 flags the circuits in a trunk group as inter-gateway
circuits (IGC). The default value is No. If it is set to Yes, all circuits in the trunk group
are flagged as IGC, which means that the ISUP signaling in the trunk group direction
supports the Incoming Route Identifier (IRI) in the IAM and the Outgoing Route
Identifier (ORI) in the ACM.
z
IRI is an additional parameter in the IAM, containing the (incoming) trunk group
identifier field and used for charging and routing. After the terminating office
receives the IAM containing IRI from the local office, it can judge the incoming
trunk group of the local office through which the call is transferred.
ORI is an additional parameter in the ACM, containing the message indicator

field and the (outgoing) trunk group identifier field and used for charging. After
the terminating office receives the ACM containing ORI from the local office, it can
judge the route or outgoing trunk group of the local office through which the call is
transferred.
This feature is applicable to Singapore. The two fields message indicator and trunk
group identifier in the IRI/ORI are defined in the two parameters Route ID message
indicator and Route ID trunk group ID in this command.
[Route ID message indicator]

10-44

It specifies the message indicator field in the ORI of the ACM. It is available only
when Inter-gateway circuit flag is set to Yes, The options are
z
National route
Transit route
Terminating route
Spare route
[Route ID trunk group ID]

It is valid only when Inter-gateway circuit flag is set to Yes. Set this parameter by the
z
For outgoing trunks, it is used to define the trunk group identifier field in the IRI of
the IAM, that is, it defines the incoming trunk group of the local office through
which a call is connected.
For incoming trunks, it is used to define the trunk group identifier field in the ORI
of the ACM, that is, it defines the outgoing trunk group of the local office through
which a call is connected.
Trunk group identifier is a trunk group ID identified by two offices interworking through
IGC. It is different from the trunk group number defined in the SoftX3000 in functions.
[EC use mode]
It specifies how the SoftX3000 distributes EC parameter to the TMG. The default setting
is Always send EC. When the TMG has the echo cancellation function, the parameter
options are described as follows:
z
Always send EC: For incoming trunks or outgoing trunks, the SoftX3000 always
sends EC=ON to the TMG despite the value of the EC indicator carried in the
IAM or the ACM/CON sent by the peer office.
Never send EC: For the incoming trunk or the outgoing trunk, the SoftX3000
always sends EC=OFF to the TMG despite the value of the EC indicator carried
in the IAM or the ACM/CON sent by the peer office.
Send EC if needed: For incoming trunks, the SoftX3000 sends EC=ON to the
TMG if the value of the EC indicator carried in the IAM sent by the peer office is
NO; the SoftX3000 sends EC=OFF to the TMG if the value of the EC indicator
in the IAM is YES. For outgoing trunks, the SoftX3000 sends EC=ON to the
TMG if the value of the EC indicator in the ACM/CON sent by the peer office is
NO; the SoftX3000 sends EC=OFF to the TMG if the value of the EC indicator
in the ACM/CON is YES.
Send EC if mandatory: For incoming trunks, the SoftX3000 sends EC=ON to the
TMG only when the value of the EC indicator carried in the IAM sent by the peer
office is NO and the delay is bigger than that defined in this command. In other
cases, the SoftX3000 sends EC=OFF to the TMG. For outgoing trunks, the
SoftX3000 always sends EC=OFF to the TMG.

10-45

If the TMG has no echo cancellation function, the SoftX3000 always sends EC=OFF
to the TMG.
[Support EC in hairpin call]
It sets whether the TMG supports EC for hairpin call. If the option is No, it indicates
that the SoftX3000 will not send EC parameter to the TMG. This parameter is set to
YES" if the TMG is UMG8900. It is set to No in other cases.
[Codec prefer]
It specifies the codec mode used by MG (instructed by the SoftX3000 during call control
process) for the RTP audio media streams of the MG in the trunk group direction. Set
this parameter by the following principles:
z
The "codec prefer" defined here has already been defined in the codec list in
ADD MGW. Otherwise, it is invalid.
If the option is set to None" (the default option), the preferred codec mode is
determined by the sequence of the codec list of the TMG in the MG data table, that
is, the first codec mode that can be queried with LST MGW.
You can specify a specific codec mode.
When all MGs in a call process are controlled by the SoftX3000, and the SoftX3000
finds intersections, covering the "codec prefer", between the codec of the caller and the
callee, the SoftX3000 shall use the "codec prefer" to control the MG at the caller sideto
start stream connections.
You can configure the "codec prefer" parameter in user data table (ADD VSBR), trunk
data table (ADD N7TG), called number analysis table (ADD CNACLD), and caller
number discrimination table (ADD CLRDSN). When a call has two or more codec
preferences, select one according to the following principles:
z
The "codec prefer" in the caller number discrimination table takes the highest
priority, and then the called number analysis table.
When the call does not involve the "codec prefer" in the caller number
discrimination table or the called number analysis table, the SoftX300 will queue a
codec mode in the first position of the list according to the principle of caller and
subscriber prior to callee and trunk during call connection. For example, for an
intra-office call, if the preferred codec mode of the caller is different from that of the
callee, that of the caller is valid. For an outgoing call, if the preferred codec mode
of the caller is different from that of the outgoing trunk group, that of the caller is
valid. For a transit call, if the preferred codec mode of the local incoming trunk
group is different from that of the local outgoing trunk group, that of the local
incoming trunk group is valid. For an incoming trunk terminated call, if the
preferred codec mode of the local incoming trunk group is different from that of the
local callee, that of the local callee is valid.
[Transparent callee NOA]

10-46

It determines whether the local office forwards the address nature of a called number
carried in an incoming office signaling message (IAM, for example) transparently when
it acts as a transit office. The default value is No, indicating that the local office does
not send the address nature of the called number transparently. This parameter is used
together with the parameters Cast called NOA and Called NOA in this command.
z
If this parameter is set to Yes, the local office will transparently transmit the
address nature of the called number carried in the incoming signaling message in
any cases.
If both this parameter and Cast called NOA are set to No, the local office will
transparently transmit the address nature of the called number carried in the
incoming signaling message.
If this parameter is set to No and Cast called NOA is set to Yes, the local office
will transmit the address nature of the called number specified in this command.
[Cast callee NOA]

It determines whether the local office re-sets the called NOA parameter in an outgoing
signaling message (IAM, for example). The default value is No, indicating that the
local office does not re-set the called NOA. If it is set to Yes",
z
For outgoing calls made by local subscribers, the local office always transmits the
called NOA defined in this command in an outgoing signaling message.
For outgoing calls forwarded by the local office, when Transparent called NOA is
set to Yes, the local office transparently transmits the called NOA carried in the
incoming signaling message.
For outgoing calls forwarded by the local office, when Transparent called NOA is
set to No, the local office transmits the called NOA defined this command in an
outgoing signaling message.
[Callee NOA]
It is used to manually set the parameter called NOA in an outgoing signaling message
(IAM, for example). It is available only when Cast called NOA is set to Yes. The
default value is Unknown1(national use).
[Cast caller NOA]
It determines whether the local office re-sets the caller NOA parameter in an outgoing
signaling message (IAM, for example). The default value is No, indicating that the
local office does not re-set the caller NOA. If it is set to Yes, the local office always
transmits the called NOA defined in this command in an outgoing signaling message.
[Caller NOA]
It is used to manually set the parameter caller NOA in an outgoing signaling message
(IAM, for example). It is available only when Cast caller NOA is set to Yes. The
default value is Unknown1(national use).
[HOP counter flag]

10-47

It indicates whether the system initiates the HOP counter function on the No. 7 trunk
group. The default option is No.
It is one of the parameters in forward IAM message. It controls the maximum number of
segments of ISUP circuits that can be connected in one call. This is to minimize the
occurrence of route selection loop because of errors in the network route organization.
If the parameter is set to Yes, the operations vary under different conditions:
z
If the local office is the originating office in a call, it should carry the HOP counter
parameter when sending IAM message forward. The initial value of the HOP
counter parameter is defined by the HOP counter value parameter in this
command.
If the local office is a tandem office in a call, and the received IAM message
includes the HOP counter parameter, and the HOP counter is not 0, the local office
fill the value of the HOP counter parameter minus 1 in the IAM message and
forwards it to subsequent office. If the HOP counter is 0, the local office returns the
REL message (the cause value is #25, indicating switching route error) to the
originating office to release the call.
If the local office is the terminating office of a call, no operation should be

performed to the HOP counter parameter in the received IAM message.
[HOP counter value]

It defines the initial value of the HOP counter parameter when the local office sends
(not forwards) an IAM message forward. It is valid only when "HOP counter flag is set
to Yes.
[SS7 type]
It indicates the type of the SS7 applied by the No.7 trunk group. By default, it is ITU-T.
If the SoftX3000 is to interconnect with the switch complying with ANSI specifications
through the No.7 trunk group, you must select ANSI. At this time, the No.7 trunk group
cannot use the overlap code sending mode.
[Allow divert]
It indicates whether the No. 7 trunk group allows call divert. The default option is Yes.
[MPM type]
During the process of CRG charging, if the local office acts as a tandem office in a call,
and the charging signaling message received by the local office from the charging
office does not specify the MPM type, the parameter specifies the MPM type used in
the charging signaling message forwarded by the local office to the charging office.
[Timer group index]

10-48

10.4.6 Adding No. 7 Trunk Circuit

I. Related commands
Command
Function
ADD N7TKC
To add No.7 trunk circuit
RMV TKC
To remove No.7 trunk circuit
MOD N7TKC
To modify No.7 trunk circuit
LST TKC
To list No.7 trunk circuit

It specifies the module number of the FCCU or FCSU processing the No. 7 trunk calls.
This parameter must be defined in the ADD BRD command before being referenced
here.
command ADD MGW for adding the TG; otherwise, the TG circuits cannot work
normally.
It specifies the No. 7 trunk group to which the No. 7 trunk circuit to be added belongs.
This parameter must be defined in the ADD N7TG command before being referenced
here.
[Start circuit number], [End circuit number]
They are used to specify the range of the E1 circuit numbers for the No. 7 trunk circuits
inside the SoftX3000. The value ranges from 0 to 9999. The configuration principles of
these parameters are as follows:
z
These are unified logical numbers assigned in a particular FCCU/FCSU module to

E1 trunk circuits regarding No. 7, PRA, R2 and V5 inside the SoftX3000. The
corresponding physical numbers at the TMG are specified in the start circuit
termination identifier parameter of the command.
A maximum of 320 trunk circuits can be added in one execution of this command.
To add more, execute the command again.
The absolute value of the difference between the start circuit number and the start
circuit termination identifier (decimal value after converting from binary value)
must be a multiple of 32, such as 0, 32, 64, and 96.
[Start CIC]
It is one of the parameters used for interworking with the opposite office. It defines the
CIC corresponding to the start circuit number. The CIC is an important parameter used
10-49

for the interconnection of No. 7 trunk circuit, and it needs to be determined and kept
consistent through the negotiation between the local office and opposite office. If
inconsistent, single pass of trunk circuits might occur.
[Controlling flag of start circuit]
It is one of the parameters used for interworking with the opposite office. It identifies the
mode of the local office to control the start circuit when the circuit selection mode of the
trunk group is Master/slave. After the controlling mode of the start circuit is specified,
the controlling modes of the other circuits in the trunk group are thus specified.
Suppose that the controlling mode of the start circuit is Master", the controlling modes
of the following circuits will be Slave, Master, Slave, "Master and so on.
According to the ITU-T recommendations, to avoid that a circuit is occupied by two
offices at the same time, the office with larger signaling point code is responsible for
controlling the circuits with even CICs and the office with smaller signaling point code is
responsible for the circuits with odd CICs. It should be noted that this parameter is
unavailable if the trunk group is a single-direction one.
[Circuit state]
It sets the initial state of a trunk circuit. Generally, the default value Available is used.
When adding several circuits continuously, you need to set it to Unavailable if a circuit
of the TMG is used as a signaling timeslot.
[Start circuit termination ID]
It defines the identifier of the start circuit timeslot in the trunk media gateway to which a
specified batch of trunk circuits belongs. It consists of digits and/or the symbol "/". Set
z
If the prefix of a termination ID is not hierarchical in structure, enter digits for this
parameter.
If the prefix of a termination ID is hierarchical, set this parameter in format of

digit/digit/digit... The maximum values for hierarchical layers and digits are defined
in ADD TIDLAY. Do not add "/" at the end of the last digit.
circuit termination ID (a decimal value converted from a binary code) must be
integral multiples of 32, for example, 0, 32, 64, or 96.
For the conversion calculation of a termination ID, refer to the explanation of offset
parameters of various layers in ADD TIDLAY. The basic process is as follows: After
you enter a termination ID, the system abstracts the digit of each layer, converts it into a
binary code (whose length depends on the offset of the layer), and finally re-organize
those binary codes into a 32-bit binary code according to their sequence in the
termination ID (0 is filled for vacant bits).
[Circuit engineering number]
It is one of the parameters for the SoftX3000 to interwork with the peer office. It
specifies the start engineering number of the circuits in an ISUP trunk group complying
10-50

with ANSI specifications. It is used in such messages of the ANSI ISUP as CVT and
CVR.
10.4.7 Adding PCM Port (Optional)

I. Related commands
Command
Function
ADD PCMPORT
To add PCM port
RMV PCMPORT
To remove PCM port
MOD PCMPORT
To modify PCM port
LST PCMPORT
To list PCM port

data configuration.
1)
For ISUP/TUP circuit: By default, the PCM type is E1, and the PCM codec mode is
A law when you use the command ADD N7TKC to add No. 7 trunk circuit. For
networking in countries such as the USA and Japan, the PCM type is T1, and the
PCM codec mode is law generally. In this case, you need to use the command
ADD PCMPORT to add PCM port.
2)
For PRA circuits: By default, one PRA signaling link can only control one Pulse
Code Modulation (PCM) system. Correspondingly, you can only add a maximum
of 32 PRA trunk circuits when using the ADD PRATKC command. However, when
the PRA link resources are not enough, if one PRA link is required to control
multiple PCM systems (a maximum of four E1s), you must use the ADD
PCMPORT command to add PCM port.

It specifies the module number of the FCCU or FCSU processing the trunk calls. This
parameter must be defined in the ADD BRD command before being referenced here.
normally.
[Port number]
It specifies the logical number in the FCCU/FCSU for timeslot 0 of the PCM port. It must
be an integral multiple of 32.

10-51

Because one PRA link can control a maximum of four PCM ports, you need to pay
attention to this limitation when using the command.
[Device type]
It specifies the device type of the PCM port. It can be PRA, ISUP or TUP.
[PRA link number]
It specifies the PRA link bearing the call signaling at the PCM port. It is valid only when
"Device type is PRA. This parameter must be defined in the ADD PRALNK command
[PCM port interface identification]
It is one of the parameters used for interconnecting the SoftX3000 with the PRA device.
It defines the interface identification of the PCM port to be added. It is valid only when
"Device type is PRA. This parameter at the SoftX3000 side must be consistent with
that at the PRA device side; otherwise, the interconnection might fail.
[PCM type]
It specifies the physical interface of the trunk circuit, E1 or T1. The default value is E1.
[PCM companding law]
It specifies the voice codec mode supported by the PCM port. That is, A law or law is
used in the PCM compression algorithm.
10.5 Configuring R2 Trunk Data

10.5.1 Overview
The R2 trunk data defines the R2 trunk related information at the SoftX3000 side, such
as charging, call barring and interconnection. To configure the R2 trunk data, make
sure that the equipment data, local office data, charging data, MG data, signaling data,
and routing data has been configured. See Figure 10-1.
During the configuration, the R2 trunk data will reference some parameters defined in
the local office data, charging data, MG data, and routing data. Besides, the network
management data will reference the network management source code defined in the
R2 trunk data. Table 10-11 shows the details.

10-52

Table 10-11 Parameter referencing relationships between R2 trunk data and other
data
Input parameter
Parameter
Output parameter
Defined in
Parameter
Referenced in
Call source code
Local office data
Network
management
source code
Network
management
data
Charging data

source code
Charging data
Equipment ID of the TMG
MG data
Subroute number
Routing data

Call barring data

(optional)
Call barring data
II. Preparations
Before configuring the R2 trunk data, make sure that all preparations are done as
SN
Item
Remark
Group direction of R2
trunk group, including
outgoing trunk, incoming
trunk or bidirectional trunk
It is one of the interconnection parameters

between the SoftX3000 and PBX devices
Cooperation of caller
number
Because the R2 signaling is transmitted with low

efficiency, you have to consider the
requirements of connection speed, charging,
and caller number display for the transmission of
caller numbers when you are interconnecting
the SoftX3000 to PBX devices.
Numbering range of R2
trunk circuits
These are unified logical numbers assigned

inside the SoftX3000 to No. 7, PRA, and R2
trunk circuits. The corresponding physical
numbers at the TMG are specified in the start
circuit termination identifier parameter.
Termination ID of circuit
number
It is one of the interconnection parameters

between the SoftX3000 and TMG.

10-53


Table 10-13 lists the general steps for configuring the R2 trunk data.
Step
Description
Command
Add R2 incoming caller category conversion (optional)
ADD CATICVT
Add R2 outgoing caller category conversion (optional)
ADD CATOCVT
Add R2 trunk group
ADD N1TG
Add R2 trunk circuit
ADD N1TKC
Add CAS signaling configuration
ADD CASCFG
Add R2 trunk group tandem (optional)
ADD N1TDM
Add R2 trunk group caller number segment (optional)
ADD TKDNSEG

the R2 trunk data is configured.
ADD N1TG
ADD CATICVT
[Incoming convert index]
[Stardard caller calling
category]
[Inner caller calling
category]
[Trunk group]
[Equipment ID]
[Group direction]
[Incoming cat convert
index]
[IOutgoing cat convert
index]
ADD CATOCVT
ADD N1TKC
[Outgoing convert index]

[Stardard caller calling
category]
[Module]
[Inner caller calling

category]
[Start circuit]
[Trunk group]
ADD N1TDM
[Incoming trunk group]
[Outgoing trunk group]
[Tandem mode]

10-54

10.5.2 Adding R2 Incoming Caller Category Conversion (Optional)

I. Related commands
Command
Function
ADD CATICVT
To add R2 incoming caller category conversion
RMV CATICVT
To remove R2 incoming caller category conversion
MOD CATICVT
To modify R2 incoming caller category conversion
LST CATICVT
To list R2 incoming caller category conversion

data configuration.
Different countries or regions might define different quantity and code of caller
categories. To enable the SoftX3000 adaptive to the R2 signaling in different countries
and regions, Huawei provides a separate R2 signaling adaptation script that contains
the definition data about caller category conversion on R2 trunk group during
equipment commissioning.

[Incoming conversion index]
This parameter defines a caller category conversion index of incoming trunk. The index
is unique inside the SoftX3000. The value range is 0 to 7.
[Standard caller category]
This parameter defines the code of the caller category that is sent by the opposite office
to the SoftX3000 through the incoming R2 trunk. This code must be consistent with that
of the opposite office. The value range is 1 to 15.
[Internal caller category]
This parameter specifies the caller category code that is defined inside the SoftX3000
and corresponds to the standard caller category of the incoming R2 trunk. The value
range is 0 to 254. For the conversion relationship between the internal caller category
and the standard caller category, refer to the R2 signaling adaptation script provided by
Huawei.

10-55

10.5.3 Adding R2 Outgoing Caller Category Conversion (Optional)

I. Related commands
Command
Function
ADD CATOCVT
To add R2 outgoing caller category conversion
RMV CATOCVT
To remove R2 outgoing caller category conversion
MOD CATOCVT
To modify R2 outgoing caller category conversion
LST CATOCVT
To list R2 outgoing caller category conversion

data configuration.:
Different countries or regions might define different quantity and code of caller
categories. To enable the SoftX3000 adaptive to the R2 signaling in different countries
and regions, Huawei provides a separate R2 signaling adaptation script that contains
the definition data about caller category conversion on R2 trunk group during system
commissioning.

[Outgoing conversion index]
This parameter defines a caller category conversion index of outgoing trunk. The index
is unique inside the SoftX3000. The value range is 0 to 7.
[Internal caller category]
This parameter specifies the caller category code that is defined inside the SoftX3000
and corresponds to the standard caller category of the outgoing R2 trunk. The value
range is 0 to 254. For the conversion relationship between the internal caller category
and the standard caller category, refer to the R2 signaling adaptation script provided by
Huawei.
[Standard caller category]
This parameter defines the code of the caller category that is sent by the SoftX3000 to
the opposite office through the outgoing R2 trunk. This code must be consistent with
that of the opposite office. The value range is 1 to 15.

10-56

10.5.4 Adding CAS Signaling Configuration

I. Related commands
Command
Function
ADD CASCFG
To add CAS signaling configuration
RMV CASCFG
To remove CAS signaling configuration
MOD CASCFG
To modify CAS signaling configuration
LST CASCFG
To list CAS signaling configuration

Different countries or regions might have defined the specifications of CAS different
from the standard ones in ITU-T. Before configuring R2 trunk data, use the command
ADD CASCFG to add CAS signaling configuration for the SoftX3000 to adapt to the
CAS specifications of your countries or regions and ensure the normal interoperation of
inter-office signaling.

[CAS signaling name]
It identifies a CAS signaling uniquely in the SoftX3000. It is a character string with a
maximum length of 16 characters.
[Signaling type]
It specifies the specification to which the CAS signaling conforms. For example, R2
signaling, R1 signaling, No. 5 signaling, China No. 1 signaling, and Russia CAS
signaling. You must select the correct signaling type. Otherwise, the inter-office
signaling cooperation will be abnormal.
[Line signal]
It defines the type of the line signal.
[Register signal]
It defines the type of the register signal.
[Line signal conversion index]
It specifies the conversion operation that needs to be performed when the local office
converts the line signal (the local office receives incoming line signal). It is reserved at
present.
[Line command conversion index]
converts the line signal (the local office sends outgoing line signal). It is reserved at
present.
10-57

[RSD signal conversion index]

converts the RSD signal (the local office receives incoming line signal). It is reserved at
present.
[RSD command conversion index]
converts the RSD signal (the local office sends outgoing line signal). It is reserved at
present.
[Circuit type]
It specifies the type of the circuit that bears the CAS signaling.
[PTS mode]
It defines the use mode of pulse signal.
[Send EOS]
It specifies whether the SoftX3000 sends the EOS signal. The default value is No.
[Send RLG]
It specifies whether the SoftX3000 sends the RLG signal. The default value is No.
[Send MCT]
It specifies whether the SoftX3000 sends the MCT signal. The default value is No.
[Send congestion]
It specifies whether the SoftX3000 sends the congestion signal. The default value is
No.
10.5.5 Adding R2 Trunk Group

I. Related commands
Command
Function
ADD N1TG
To add R2 trunk group
RMV TG
To remove R2 trunk group
MOD N1TG
To modify R2 trunk group
LST TG
To list R2 trunk group

Before adding an R2 trunk group, use the related commands to obtain the following
1)

10-58

2)
3)
4)
5)
6)

[Equipment ID]
R2 trunk circuits. This parameter is defined in the ADD MGW command and referenced
here.
[Group direction]
It specifies the call connection direction of the R2 trunk group. The default option is
bidirectional trunk. The parameter options are described as follows:
z
Bi-directional trunk: It indicates that the local office processes the calls from and to
[Sub-route number]
It specifies the subroute to which the trunk group belongs. This parameter is defined in
the ADD SRT command and referenced here.
[CAS signal name]
It specifies which type of CAS signal the trunk group uses. The parameter must be
defined by the command ADD CASCFG before being referenced here.
[Trunk group name]
[Call source code]
It specifies the call source to which the trunk group belongs. This parameter is defined
in the ADD CALLSRC command and referenced here.
It specifies the trunk circuit selection policy of the trunk group. The default mode is
Cyclic. The meanings of the options are

10-59

z
Recycle: The system selects a circuit from the next one to the last selected circuit
the minimum number.
first.
User side allocation: The system selects a circuit according to the instruction from
the user side.

It identifies whether the R2 trunk is carried over the satellite circuits. You need to set it
[EC support]
This parameter specifies whether the local office starts the echo suppress function to
the incoming trunk group circuits or the outgoing trunk group circuits. By default, the
system does not start the echo suppress function. The setting of this parameter must
be consistent with that of the opposite office. In other words, to successfully complete
call connection through the R2 trunk, both exchanges must provide the echo suppress
function. This premise must be satisfied first. Otherwise, the connection might fail. The
parameter options are described as follows:
z
No EC support: Do not start the echo suppress function to the R2 trunk circuits.
EC support for outgoing call: Start the echo suppress function only to the outgoing
R2 trunk circuits. In this case, the corresponding incoming trunk circuits of the
opposite office must support the echo suppress function.
EC support for incoming call: Start the echo suppress function only to the incoming
R2 trunk circuits. In this case, the corresponding outgoing trunk circuits of the
Bi-directional EC support: Start the echo suppress function to both outgoing and
incoming R2 trunk circuits. In this case, the corresponding incoming and outgoing
trunk circuits of the opposite office must support the echo suppress function.
When the R2 trunk is carried over the satellite circuits, this parameter is set to
bidirectional echo suppress.
[Call-in authority]

10-60


[DOD2]
This parameter is available to outgoing trunks to control whether the local callers can
hear the secondary dial tone sent by the peer office after seizing the outgoing trunk. For
the AT0 outgoing trunk group, you can set this parameter to YES as needed. In other
cases, set this parameter to NO.
[Send initial tone]
This parameter is available only to incoming trunks and only when the register signaling
adopts MFP, Pulse, and DTMF. It controls the local office to send the initial signal tone
to the peer office during the transition. This feature is used for the transit office with R2
trunks. Because the connection speed of R2 trunks is slow, the caller listens to nothing
for a long time before connected to the callee, which seriously affects the quality of
service. If the transit office enables the initial tone function, it will send the specified
signal tone, such as music, to the caller in the connection process after the call gets to
the transit office. After successful connection, the destination office will play ring-back
tone to the caller, thus improving the satisfaction of the subscribers.
[Initial tone type]
It specifies the type of the initial tone. This parameter is available only when the send
initial tone is set to YES.
It controls the local office to send exceptional tone to the opposite office through a B7
signal when the call through the incoming trunk fails. This parameter is available only to
incoming trunks.
z
If this parameter is set to NO, the local office sends a B3 signal to the opposite
office after the call fails. In this case, the call is released and the opposite office
sends the busy tone to the caller.
If the parameter is set to YES, the local office sends a B7 signal to the opposite
office when the call fails. In this case, the call is held temporarily and the local
office sends the exceptional tone to the caller through the incoming trunk; if the
caller hangs up or the timer times out, the call will be released.

It specifies the type of the exceptional tone. This parameter is available only when the
send exceptional tone is set to YES.
10-61


indicates no charging of incoming trunks. This parameter is defined in the command
ADD CHGIDX or ADD CHGGRP and referenced here. For the detailed information
value 254 is the wildcard that cannot be used for trunk charging. The value 255"
indicates no charging of outgoing trunks. This parameter is defined in the command
ADD CHGIDX or ADD CHGGRP and referenced here. For the detailed information
[Use opposite pulse]
It is used for the inter-office trunk cooperation in the immediate charging. When it is set
to YES, its meanings for outgoing trunk and incoming trunk are different.
z
Outgoing trunk: When there is an outgoing call from the trunk group, the local
office needs to receive the charging pulse sent back from the opposite office, and
the opposite office needs to cooperate to send the charging pulse to the local
office.
Incoming trunk: When there is an incoming call to the trunk group, the local office
needs to send charging pulse to the opposite office, and the opposite office needs
to cooperate to receive the charging pulse sent from the local office.
[CAMA]
performs the centralized charging on the incoming trunks. If it is set to YES, the local
office performs the centralized charging on the incoming trunks. In this case, when the
opposite office originates a call through an incoming trunk and the call signaling does
not carry the caller number, the local office requests the caller number through
signaling.
This parameter is available only to incoming trunks. When the Whether request caller
number parameter is set to YES, this parameter defines whether the local office can
request the caller number from the opposite office if the incoming call signaling through
the trunk contains no caller number. The default option is YES, indicating that the local
office can request the caller number on initiative. However, if this feature affects call
completion rate or connection time, you can set the option to NO.
[Connect without or with invalid caller number]
This parameter is available only to incoming trunks. If the incoming call signaling
through the trunk does not carry a caller number or the carried caller number is invalid,

10-62

this parameter indicates the local office whether to connect the call, that is, whether the
call is not rejected. The default option is YES.
[Minimum caller number length]
number parameter is set to YES, this parameter specifies the minimum number
length of the caller number if the incoming call signaling through the trunk carries the
caller number. If the actual length of the caller number is less than the defined minimum
number length, the local office does not connect the call, that is, the local office rejects
the call. By default, the minimum number length of the caller number is seven digits.
When the opposite office originates a call through the incoming trunk, this parameter
indicates how the local office obtains the calling number from the incoming trunk if the
call signaling from the opposite office contains no calling number. This parameter is
available only to incoming trunks.
z
Trunk line ID: It indicates that the calling number is an ID of a trunk circuit.
Default number: It indicates that the calling number is the default one pre-defined
in this command.
If the opposite office sends the calling number in the incoming call signaling, the local
office will use it and this parameter is invalid.
This parameter is available only to incoming trunks. If the Caller number provision
mode of the trunk group is Default number and no caller number is contained in the
call signaling message sent by the peer office when it originates a call through the
incoming trunk, the local office will use the default caller number.
It specifies the call barring group to which the trunk group belongs. The parameter
z
If the value is not specified or specified with 65535, it indicates that the call
barring function is not enabled.
If the black/white list barring is used, the three preset call barring groups can be
referenced directly, that is black list 60001, white list 60002 and ordinary call
barring group 65534.
If other call barring groups are expected, this parameter must have been defined
in the SET GRPAC command before being referenced here.
During the number analysis process of inter-group call barring authentication, the
SoftX3000 shall authenticate twice the caller, called prefix, and the callee. To help you
correctly use the parameter, here is an illustration of the inter-group call barring
authentication procedure:

10-63

1)
When a local subscriber or incoming trunk initiates a call, the SoftX300 first
authenticates the call barring group number of the caller or incoming trunk (caller
barring group number), by comparing with the call barring group of the called
prefix (called barring group number, configured by ADD CLDGRP, 65534 by
default). If the authentication succeeds the SoftX3000 will proceed with
subsequent procedures; otherwise, the SoftX3000 will reject the call.
2)
When the call passes the first inter-group call barring authentication, the
SoftX3000 will again authenticate the call barring group number of the caller or
incoming trunk (caller barring group number) and that of the callee or outgoing
trunk (called barring group). If the authentication succeeds the SoftX3000 will
proceed with subsequent procedures; otherwise, the SoftX3000 will reject the call.
[Signaling link number]

Reserved.
[Upper seizure threshold]
It defines the maximum occupancy time length of the trunk circuit. If the time that the
trunk circuit has been occupied exceeds the threshold, the system will check the circuit
status and generates alarm. Its value ranges from 0 to 65535 with the unit as second. 0
or 65535 indicates that the threshold is invalid.
[Lower seizure threshold]
It defines the minimum occupancy time length of the trunk circuit. If the time that the
trunk circuit has been occupied is lower than the threshold, the system will count once.
If the number of times is larger than the value presented by the lower 8 bits in TUP
operation reserve parameter 1, the system will generate alarm. Its value ranges from 0
to 65535 with the unit as second. 0 or 65535 indicates that the threshold is invalid.
If the incoming call signaling through the trunk does not contain caller number, it defines
whether the local office requests caller number from the opposite office on initiative. It is
valid only for incoming trunks. The default option is NO, indicating that the local office
will not request caller number on initiative.
[Request caller number position]
number parameter is set to YES", this parameter specifies the digit from which the
opposite office sends the caller number as requested by the local office.
[ANI request count]
This parameter is available only to incoming trunks and applicable only to the R1.5
signaling. When the local office requests the caller number from the peer office but fails,
this parameter specifies the maximum number of request attempts. By default, it is 3
times.
[Request caller category]
10-64

If the incoming call signaling through the trunk does not contain the call category, it
defines whether the local office requests the call category from the opposite office on
initiative. It is valid only for incoming trunks. The default option is NO, indicating that
the local office will not request the call category on initiative.
[Request caller category position]
This parameter is available only to incoming trunks. When the request call category
parameter is set to YES", this parameter specifies the digit from which the opposite
office sends the call category as requested by the local office.
[Receive caller number]
This parameter is available only to incoming trunks, used to specify whether the local
office continues to receive the caller number sent by the opposite office after the local
office has received the call category. The default option is YES, indicating that the
local office continues to receive the caller number from the opposite office. If this
parameter is set to NO, the local office receives only the call category from the
opposite office; the local office does not receive the caller number.
The setting of this parameter must be consistent at both offices. If the opposite office is
defined not to send the caller number but the local office defined to receive the caller
number, the local office considers the caller number sent by the opposite office as the
called number.
[Send caller number]
This parameter is available only to outgoing trunks, used to specify whether the local
office continues to send the caller number to the opposite office after the local office has
sent the call category to the terminating office. The default option is YES, indicating
that the local office continues to send the caller number to the opposite office. If this
parameter is set to NO, the local office sends only the call category to the opposite
office; the local office does not send the caller number.
The setting of this parameter must be consistent at both offices. If the local office is
defined not to send the caller number but the opposite office defined to receive the
caller number, the opposite office considers the caller number sent by the local office as
the called number.
[Send caller category]
This parameter is available only to outgoing trunks, used to specify whether the local
office sends the call category to the opposite office. The default option is NO,
indicating that the local office does not send the call category to the opposite office.
The setting of this parameter must be consistent at both offices. If the local office is
defined not to send the call category, when the opposite office requests the call
category from the local office, the local office cannot respond correctly.
[Request HES]

10-65

through the trunk does not contain the echo suppress signal, this parameter defines
whether the local office requests the echo suppress signal from the opposite office on
initiative. The default option is NO, indicating that the local office does not request the
echo suppress signal from the opposite office on initiative. If this parameter is set to
YES", the echo suppress parameter in this command must be set correctly.
[Request circuit type]
through the trunk does not contain the circuit type signal, this parameter defines
whether the local office requests the circuit type signal from the opposite office on
initiative. The default option is NO, indicating that the local office does not request the
circuit type signal from the opposite office on initiative.
[Waiting seizure ACK time]
This parameter is available only to outgoing trunks. After the local office seizes a trunk
circuit and sends the seizure signal (line signaling) to the opposite office, this parameter
specifies the maximum time for waiting for the seizure acknowledgement that is
returned by the opposite office. The value range is 0 to 5, and the unit is second. The
default value is 3.
z
For the line signaling mode requiring the seizure acknowledgement signal, if the
local office does not receive a seizure acknowledgement signal from the opposite
office after the expiration, the call fails.
For the line signaling mode not requiring the seizure acknowledgement signal, if
the local office does not receive a seizure acknowledgement signal from the
opposite office after the expiration, the local office automatically enters the seizure
acknowledged state.
[Number interval duration]

This parameter defines the inter-digit time interval when an incoming R2 trunk sends a
number to an outgoing R2 trunk. The value range is 0 to 60, and the unit is second. The
[Waiting caller category time]
This parameter is available only to incoming trunks. After the local office sends an A5
signal to the opposite office, this parameter specifies the maximum time for waiting for
the call category signal that is returned by the opposite office. The value range is 0 to 60,
and the unit is second. The default value is 50.
[Waiting callee state time]
This parameter is available only to outgoing trunks. After the local office sends all
signals to the opposite office, this parameter specifies the maximum time for waiting for
the callee state signal that is returned by the opposite office. The value range is 0 to 60,
and the unit is second. The default value is 10.

10-66

[Ringing duration]
This parameter is available only to incoming trunks. When an originating subscriber
calls a local office subscriber through an incoming trunk, if the callee is idle, the local
office simultaneously sends the ringing tone to the callee and the ringback tone to the
originating office. This parameter specifies the maximum time the local office monitors
the ringing at the callee. The value range is 0 to 65535, and the unit is second. The
[Listening to ringback tone time]
This parameter is available only to outgoing trunks. It defines the maximum duration
during which a local caller (or an incoming trunk) can hear the ringback tone. The value
range is 0 to 65535, and the unit is second. The default value is 240.
The time when the local caller enters the state of hearing the ringback tone is not the
time when the terminating office starts sending the ringback tone to the local office, but
the time after one timer duration when all digits of the called number are sent. The timer
duration is defined in the parameter Listening to ringback tone delay in this command.
[Number send delay]
This parameter is available only to outgoing trunks, used to specify the duration
between the time when the local office receives the outgoing trunk circuit seizure
acknowledgement message returned by the peer office and the time when the local
office sends the first digit. The value range is 0 to 10, and the unit is second. The default
value is 1.
If the time when the local office starts to seize the outgoing trunk circuit is counted, the
delay for the local office to send the first digit to the peer office is Waiting seizure ACK
time + Number send delay.
[Listening to ringback tone delay]
This parameter is available only to outgoing trunks. When the register signaling through
the outgoing trunk adopts the non MFC mode, if the length of the called number sent
from the local office to the terminating office is less than the minimum number length
defined at the terminating office, this parameter specifies the delay the ringback tone is
automatically played to the local office subscriber (or the incoming trunk). The value
range is 0 to 30, and the unit is second. The default value is 5.
If the register signaling through the outgoing trunk adopts the MFC mode, this
parameter is invalid. Whether to play the ringback tone to the caller depends on the
register signal or the line signal that is sent by the terminating office.
[Automatic answer time]
This parameter is available only to outgoing trunks. After the ringback tone is played to
the local subscriber (through the incoming trunk), this parameter specifies the
monitoring duration after the local subscriber automatically enters the conversation

10-67

state (suppose the callee has picked up the phone). The value range is 0 to 30, and the
unit is second. The default value is 6.
[Ringback tone send delay]
This parameter is available only to incoming trunks, used to specify the time gap
between the sending of the KB signal from the local office to the originating office and
the sending of the ringback tone. The value range is 0 to 5, and the unit is second. The
default value is 0.
[Priority]
This parameter specifies the routing priority for the R2 trunk group. A trunk group with
currently the highest priority is preferred. A trunk group will be selected to convey traffic
only after there are absolutely no available trunk circuits with a higher priority than it.
The greater the value is, the lower the priority is. 0 indicates the highest priority.
[Availability]
It defines the times that the trunk group can be selected in the corresponding subroute.
Its value ranges from 0 to 255. In a subroute, every time the system selects the trunk
group, the allowable times of the trunk group will be decreased by 1. When the times
become 0, the system cannot select the trunk group. If the allowable times of all trunk
groups in the corresponding subroute become 0, those times will be assigned with new
values, which intend to distribute the traffic over all trunk groups of the subroute
according to the expected principle. The default value is 255, indicating that the
parameter is invalid.
It sets whether R2 trunks support some special services or applications. There are 16
options for this parameter. Currently, only seven options are used, and the others are
z
number to the peer office in the WAN Centrex service.
Set caller type as operator: It is available only to incoming trunks. If you select this
option, the local office will set the caller category to Operator" forcedly no matter
whether the peer office sends the caller category through the incoming trunk and
no matter what the value of the caller category is.
Trunk send ringback tone: It is available to incoming trunks only. If you select this
option, when a call originated by the peer office to the local office through the
incoming trunk is connected successfully, the local office will send the ringback
tone to the peer office no matter whether the local office is the terminating office or
not. This feature is applicable to Hong Kong.
Trunk is Brunei: If you select this option, the trunk group complies with the R2
signaling of Brunei.
10-68

z
No answer if free: It is available only to incoming trunks. If you select this option,
the local office will return to the originating office the response signal with a delay
of two seconds when the local callees are idle. If you do not select this option, the
local office will return the response signal to the originating office immediately.
A6 signaling special release: It is available only to outgoing trunks. If you select

this option, after the local office originates a call, the local office can display its
outgoing trunk circuits as idle without receiving the backward release monitor
signal from the terminating office when the caller or callee hangs up. If you do not
select this option, the local office can display its outgoing trunk circuits as idle only
after receiving the backward release monitor signal from the terminating office.
Trunk group caller number segment: This parameter indicates whether the
SoftX3000 shall judge the validity of the caller number sent by the peer office
through the incoming trunk. It verifies whether the caller number sent by the peer
office is in the number segment defined by ADD TKDNSEG. If so, the caller
number is valid; otherwise, it is invalid. The parameter is valid only for incoming
trunks. When you select this option, the local office shall judge the validity of the
caller number sent by the peer office. If so, the local office shall use the original
caller number in charging, display it on the callee's telephone; otherwise, the local
office shall use the default caller number of the trunk group in charging, and
display it on the callee's telephone. When you leave the option unselected, the
local office will not judge the validity of the caller number sent by the peer office;
always charge it and display it on the callee's telephone.
[Send A9 signal]
This parameter is available only to incoming trunks. It defines whether the local office
sends A9 signal to the originating office. A9 signal is the reserved signal in the standard
R2 signaling. The SoftX3000 defines it as follows: In the auto toll telephone network, A9
signal is used to restrict the toll calls of common subscribers so as to ensure the calling
priority of the subscribers with higher authorities and the toll operators.
This parameter is only applicable to the channel associated signaling TB85_No1 or
TB93_No1 in the China railway dedicated network.
[International call]
This parameter is available only to outgoing trunks. It specifies whether the outgoing
trunk is used to transit international calls. The default option is NO.
z
If this parameter is set to YES, the outgoing trunk is used to transit international
calls. In this case, when the terminating office sends an A5 signal to the local office
to request the call category, the local office returns the group II signaling whose
signal ranges from 7 to 11.
If this parameter is set to NO, the outgoing trunk is used to transit national calls.
In this case, when the terminating office sends an A5 signal to the local office to
request the call category, the local office returns the group II signaling whose
signal ranges from 1 to 6.
10-69

[Number incomplete]
When the local office connects the R2 incoming trunk with the ISUP outgoing trunk, this
parameter specifies whether the SoftX3000 sets the bit caller number incomplete
indicator in the message sent by the R2 incoming trunk to the call processing software
to "1, which indicates that the caller number is incomplete. It is available only to
incoming trunks.
[Name valid]
This parameter is available only to incoming trunks. It specifies whether the parameter
Trunk group name in the message sent by the R2 incoming trunk to the call
processing software is valid or not. The parameter Trunk group name is the one
defined in this command and it is equivalent to caller name.
[Operator call barring]
This parameter is available only to outgoing trunks, used to specify whether the
subscriber whose call category is operator has the permission to seize the outgoing
trunk. The default option is NO, indicating that the operator can seize the outgoing
trunk.
[First backward code]
signaling. When the register signaling adopts the MFS mode, this parameter specifies
the first backward signal returned by the local office. It may be B1, B2, or B3. The
default option is B2". To receive all of the called number, set this parameter to B1 or
B2. To receive part of the called number, set this parameter to B2.
[Reset flag]
signaling. When the originating office calls a local office subscriber through the
incoming trunk, this parameter specifies whether the local office sends the ringing tone
to the local office subscriber as requested by the originating office. The default option is
YES". If the incoming trunk is used only to connect toll calls, set this parameter and the
receive ringing signal parameter to YES. In other cases, set this parameter to NO.
[Send ringing signal]
This parameter is available only to outgoing trunks and applicable only to the R1.5
signaling. When the local office calls a terminating office subscriber through the
outgoing trunk, this parameter controls whether the local office sends the ringing signal
to the terminating office as requested by the local office. The default option is NO". If
the outgoing trunk is used only to connect outgoing toll calls, this parameter is set to
YES. In other cases, this parameter is set to NO.
[Receive ringing signal]
signaling. When the originating office calls a local office subscriber through the
10-70

incoming trunk, this parameter specifies whether the local office receives the ringing
signal from the originating office. The default option is NO". If the incoming trunk is
used only to connect incoming toll calls, this parameter is set to YES (and the reset
flag parameter must be set to YES). In other cases, this parameter is set to NO.
[Response to B6]
This parameter is available only to outgoing trunks and applicable only to the R1.5
signaling. When the register signaling adopts the MFS mode and the local office
receives the B6 signal from the terminating office, this parameter specifies the
operations for the local office to perform.
z
Reattempt: Re-attempt to connect the call.
Resend: Re-send the called number.
Disconnect: Disconnect the call. In other words, the call fails.
[Trunk name]
It identifies a trunk with a string of characters.
[Block the blocker]
This parameter is available only to outgoing trunks. It specifies whether an R2 trunk
group supports the block the blocker service. That is, when a call originated by the local
office seizes the R2 outgoing trunk, the system will reject the call if it judges that there is
no caller number in the call. This feature is applicable to Hong Kong only. By default, it
is set to False.
[EC signaling flag]
This parameter specifies whether the local office starts the echo suppress function
according to the echo suppress signal sent by the originating office or the echo
suppress data configured at the local office. The default option is YES.
[EC use mode]
This parameter specifies the mode in which the local office starts the echo suppress
function to the R2 trunk circuits. The default option is providing none echo suppress.
The setting of this parameter must be consistent with that of the opposite office. In other
words, to successfully complete call connection through R2 trunk, both exchanges
must provide the echo suppress function. This premise must be satisfied first.
Otherwise, the connection might fail. The parameter options are described as follows:
z
No internal EC support: Do not start the echo suppress function to the R2 trunk
circuits.
EC support for outgoing call: Start the echo suppress function only to the outgoing
R2 trunk circuits. In this case, the corresponding incoming trunk circuits of the
EC support for incoming call: Start the echo suppress function only to the incoming
R2 trunk circuits. In this case, the corresponding outgoing trunk circuits of the

10-71

z
Bi-directional EC support: Start the echo suppress function to both outgoing and
incoming R2 trunk circuits. In this case, the corresponding incoming and outgoing
trunk circuits of the opposite office must support the echo suppress function.
External EC support: Use an external echo suppress device that is interconnected

between the exchange and the transmission device.
When the R2 trunk is carried over the satellite circuits, this parameter is set to
bidirectional echo suppress.
[Forward office EC]
This parameter is available only to incoming trunks, used to specify the mode in which
the originating office starts the echo suppress function to the R2 trunk circuits. The
default option is unknown. For the meanings of the parameter options, refer to the
description of the using EC mode parameter.
[Backward office EC]
This parameter is available only to outgoing trunks, used to specify the mode in which
the terminating office starts the echo suppress function to the R2 trunk circuits. The
default option is unknown. For the meanings of the parameter options, refer to the
description of the using EC mode parameter.
[Connect without EC]
The local office has started the echo suppress function to the R2 trunk circuits. When
the related echo suppress device becomes faulty during the call, this parameter
specifies whether the local office continues the call. The default option is YES.
[EC index]
This parameter specifies the EC data to be used in this command. This parameter is
defined in the ADD ECPARA command and referenced here.
[Default connect]
If querying caller number discrimination group failed (that is, the queried record is not
found), it is used to set whether to get the call through. The default option is YES,
indicating that the call will be connected through.
[Whether request caller number for CCB]
available only to incoming trunks. The default option is NO, indicating that the local
office will not request caller number on initiative.
[Send MPM message]
This parameter is available only to incoming trunks, used for inter-office trunk
cooperation during the immediate charging process. The default option is YES,
indicating that the local office sends charging pulse to the opposite office through
signaling, and the opposite office cooperates to receive the charging pulse sent from
the local office through signaling.
10-72

[Waiting PTS time]

This is a reserved parameter.
[Codec prefer]
It specifies the codec mode used by the RTP audio media streams of the TMG in the
trunk group direction. Set this parameter by the following principles:
z
The preferred codec mode defined here must have been defined in the codec list
in ADD MGW. Otherwise, it is invalid.
Preferred codec is the first mode in the codec list that is supported by the MGs of both
the caller and the callee. If the codec list contains the preferred codec modes of the
caller, callee, incoming trunk group, and outgoing trunk group at the same time, the
SoftX3000 will queue a codec mode in the first position of the list according to the
principle of caller and subscriber prior to callee and trunk during call connection.
For example, for an intra-office call, if the preferred codec mode of the caller is different
from that of the callee, that of the caller is valid. For an outgoing call, if the preferred
codec mode of the caller is different from that of the outgoing trunk group, that of the
caller is valid. For a transit call, if the preferred codec mode of the local incoming trunk
group is different from that of the local outgoing trunk group, that of the local incoming
trunk group is valid. For an incoming trunk terminated call, if the preferred codec mode
of the local incoming trunk group is different from that of the local callee, that of the local
callee is valid.
[Incoming caller category conversion index]
This parameter specifies the caller category conversion index to be used by the
incoming R2 trunk group. This parameter is defined in the ADD CATICVT command
[Outgoing caller category conversion index]
This parameter specifies the caller category conversion index to be used by the
outgoing R2 trunk group. This parameter is defined in the ADD CATOCVT command
10.5.6 Adding R2 Trunk Circuit

I. Related commands
Command
Function
ADD N1TKC
To add R2 trunk circuit
RMV TKC
To remove R2 trunk circuit

10-73

Command
Function
MOD N1TKC
To modify R2 trunk circuit
LST TKC
To list R2 trunk circuit

This parameter specifies the module number of the FCCU or FCSU processing the R2
trunk calls. This parameter is defined in the ADD BRD command and referenced here.
normally.
This parameter specifies the R2 trunk group to which the R2 trunk circuits to be added
belongs. This parameter is defined in the ADD N1TG command and referenced here.
They specify the E1 numbering range of the R2 trunk circuits in the SoftX3000. The
value ranges from 0 to 6399. Set this parameter by the following principles:
z
These are unified logical numbers assigned inside the SoftX3000 to No. 7, PRA,
R2, and V5 E1 trunk circuits in an FCCU/FCSU module. The corresponding
physical numbers at the TMG are specified in the start circuit termination ID
parameter in this command.
A maximum of 320 trunk circuits can be added in one execution of this command.
If you want to add more than 320 trunk circuits, execute the command appropriate
times.
circuit termination ID (decimal value after converting from binary value) must be an
integer multiple of 32, such as 0, 32, 64, and 96.
[Master ID of start circuit]

It is one of the parameters used for interworking with the opposite office. It identifies the
mode of the local office to control the start circuit when the circuit selection mode of the
trunk group is master/slave. After the controlling mode of the start circuit is specified,
the controlling modes of the other circuits in the trunk group are thus specified.
Suppose that the controlling mode of the start circuit is Master", the controlling modes
of the following circuits will be Slave, Master, Slave, Master, and so on.
[Circuit state]
This parameter specifies the initial state of the trunk circuits. The meanings of the
parameter options are as follows:

10-74

z
Unavailable: The trunk circuits specified in this command are not used. In this
case, the state of the trunk circuits is displayed as uninstalled.
Available: The trunk circuits specified in this command are used as the inter-office
trunk to interconnect the exchange devices like PBX.
Resource: The trunk circuits specified in this command are used as the ordinary
E1 circuits to interconnect the voice card of the voice mailing system.
Usually, this parameter is set to the default option, available.

[Fill the engineer number]
This parameter specifies whether to number, at the local office, the R2 trunk circuits to
be added here. This number is used for maintaining the R2 trunk circuits conveniently,
such as blocking, unblocking, and resetting R2 trunk circuits. This is not an
interconnection parameter between the exchanges. If this parameter is set to YES,
the circuits in the same R2 trunk group must be numbered with different engineering
numbers.
[Start engineer number]
This parameter is valid only when Fill the engineer number is set to Yes. It specifies
the start number for the batch of the trunk circuits in the resident R2 trunk group.
It defines the identifier of the start circuit timeslot in the trunk media gateway to which a
specified batch of trunk circuits belongs. It consists of digits and/or the symbol "/". Set
z
parameter.

digit/digit/digit.... The maximum values for hierarchical layers and digits are
defined in ADD TIDLAY. Do not add "/" at the end of the last digit.
parameters of various layers in ADD TIDLAY. The basic process is as follows: After
you enter a termination ID, the system abstracts the digit of each layer, converts it into a

10-75

10.5.7 Adding R2 Trunk Group Tandem (Optional)

I. Related commands
Command
Function
ADD N1TDM
To add R2 trunk group tandem
RMV N1TDM
To remove R2 trunk group tandem
LST N1TDM
To list R2 trunk group tandem

This configuration step is optional. Read the following description before using this
command.
When the local office acts as a transit office and interconnects with multiple office
directions through R2 trunks, the system adopts, by default, the transfer tandem
mode for the register signaling between the R2 trunk groups. In other words, the local
office does not transfer the called number to an outgoing R2 trunk until all the number
digits are received from the incoming R2 trunk. This tandem mode does not require
high-quality line, but the connection speed is very low.
If the line has a high quality and the originating and terminating offices interconnected
with the local office have the same mode of register signaling, the register signaling
between the R2 trunk groups can adopt the end-to-end tandem mode. In this case, you
can use the ADD N1TDM command to add an R2 trunk tandem mode such as prolong
mode and resend mode. (The added tandem mode is prior to the default mode.)

[Incoming trunk group number]
This parameter specifies the incoming R2 trunk group for which the tandem mode of
register signaling is to be added. This parameter is defined in the ADD N1TG command
This parameter specifies the outgoing R2 trunk group for which the tandem mode of
register signaling is to be added. This parameter is defined in the ADD N1TG command
[Tandem mode]
This parameter specifies the tandem mode with which the local office transits the
register signaling from an incoming R2 trunk group to an outgoing R2 trunk group. The
meanings of the parameter options are as follows:
z
No tandem: The local office adopts the default transfer" tandem mode.

10-76

z
Prolong: On receipt of sufficient called number digits for judging the outgoing route
from the originating office, the local office sends the corresponding group A signal
to the originating office and then connects the related incoming and outgoing R2
trunk circuits. After the circuit connection, the originating office sends the called
number (part of the called number starting with the next digit after the prolong
length) to the terminating office with the end-to-end mode according to the group A
signal. This mode is applicable only to urban call end office or PBX as the
terminating office. In other words, the terminating office conducts analysis from an
intermediate digit, rather than the first digit, of the complete called number during
the call connection.
Resend: On receipt of sufficient called number digits for judging the outgoing route
from the originating office, the local office sends the corresponding group A signal
to the originating office and then connects the related incoming and outgoing R2
trunk circuits. After the circuit connection, the originating office sends the called
number (the complete called number starting with the first digit) to the terminating
office with the end-to-end mode according to the group A signal. This mode is
applicable to upper-level transit office or toll office as the terminating office. In
other words, the terminating office conducts analysis from the first digit of the
complete called number during the call connection.
Transfer: After receiving all called number digits from the originating office, the
local office transfers them to the terminating office. The local office does not
connect the related incoming and outgoing R2 trunk circuits until the terminating
office returns a B6 or B7 signal.
[Prolong length]
This parameter is available to the prolong tandem mode. Before the local office
connects the related incoming and outgoing R2 trunk circuits, this parameter specifies
the digit after which the originating office sends the called number digits to the
terminating office. For example, if this parameter is set to 3, the originating office
sends to the terminating office the called number digits starting with the fourth digit.
The setting of the prolong length must meet the requirements of the terminating office
for the minimum length of the called number in the connection of an incoming call. For
example, the number segment allocated for an end office is 654XXXX. (The number
length is 7.) In this case, the minimum called number length required by the end office
in the connection of an incoming call is 4, and thus set the prolong length to 3. Another
example, the format for national significant numbers in a local network is
0811XXXXXXX. (The number length is 11.) In this case, the minimum called number
length required by a toll office in the connection of an incoming toll call is 7, and thus set
the prolong length to 4.
[RSD transfer code]
The register signaling mode transfer code is applicable only to the Russian channel
associated signaling (also called R1.5 signaling) and is available only to the transfer
10-77

tandem mode. When the local office needs to convert the register signaling mode from
the MFS mode of the incoming R2 trunk to the DP mode of the outgoing R2 trunk, this
parameter specifies the conversion signal that is sent by the local office to the
originating office.
The following signals are frequently used in the actual data configuration.
z
B8: The complete called number is sent.
B9: The called number digits from the next digit are sent.
B10: The called number digits from the previous digit are sent.
On receipt of the conversion signal from the local office, the originating office changes
to send the register signaling with the DP mode. The local office still adopts the transfer
mode for transit.
10.5.8 Adding R2 Trunk Group Caller Number Segment (Optional)

I. Related commands
Command
Function
ADD TKDNSEG
To add trunk group caller number segment
RMV TKDNSEG
To remove trunk group caller number segment
LST TKDNSEG
To list trunk group caller number segment

This configuration step is optional. Read the following descriptions before using the
command.
By default, when the peer office initiates a call through R2 trunks to the local office, the
local office does not judge the validity of the caller number sent by the peer office;
always charge it and display it on the callee's telephone.
However, the carrier might need to precisely charge the call initiated through R2
incoming trunks to accurately distribute call charges to caller numbers during bill
sorting. In addition, to prevent charge disputes caused by a wrong caller number from
the peer office, the local office need to judge the validity of the received caller number.
The local office shall judge whether the caller number is in the number segment defined
by ADD TKDNSEG. If so, the number is valid; otherwise, it is invalid.
To ensure the judging process, you have to run MOD N1TG, and select "Trunk group
caller number segment" (for the R2 incoming trunk group) in "Software parameter of
service control". Then the the local office shall judge the validity of the caller number
sent by the peer office. If so, the local office shall use the original caller number in
charging, display it on the callee's telephone; otherwise, the local office shall use the

10-78

default caller number of the trunk group in charging, and display it on the callee's
telephone.

It specifies the R2 incoming trunk group to configure caller number segment. The
parameter must first be defined by ADD N1TG before it can be used here. You can only
configure one caller number segment for each trunk group.
[Start caller number], [End caller number]
The two parameters define the range of trunk group caller number segment. The trunk
group caller number segment can overlap the subscriber segment defined by ADD
DNSEG.
10.6 Configuring PRA Trunk Data

10.6.1 Overview
The PRA trunk data is used to configure interconnection information between the
SoftX3000 and PBX, NAS, or other PRA device. The interconnection information
includes start E1 number, end E1 number and default caller number. The PRA trunk
data configuration must not be done before the equipment data, local office data,
charging data, signaling data and routing data and PRA subscriber data is configured.
See Figure 10-1.
data, routing data and PRA subscriber data will be referenced in the PRA trunk data.
Table 10-14 Parameter referencing relationships between PRA trunk data and other
data
Input parameter
Name
Output parameter
Defined in
Name
Referenced in
Call source code
Local office data
Subroute number
Routing data
PRA link ID
Signaling data
PRA subscriber number
Subscriber data
Caller number discrimination group

number (optional)
Call barring data

10-79

II. Preparations
Before configuring the PRA trunk data, make sure that all preparations are done as
SN
Item
Remark
Start E1 number and

end E1 number of the
PRA trunk group
These are unified logical numbers assigned inside the

SoftX3000 to No. 7, PRA, and R2 trunk circuits. The
corresponding physical numbers at the TMG are
specified in the start circuit termination identifier
parameter.
Termination identifier
of circuit number
For interworking with TMG

Table 10-16 lists the general steps for configuring the PRA trunk data.
Step
Description
Command
Add PRA trunk group
ADD PRATG
Add PCM port (optional)
PCMPORT
Add PRA trunk circuit
ADD PRATKC

the PRA trunk data is configured.

10-80

ADD PRATG
[Equipment ID]
[Sub-route number]
ADD PRATKC
[Module]
[Trunk group]
[Start circuit]
10.6.2 Adding PRA Trunk Group

I. Related commands
Command
Function
ADD PRATG
To add PRA trunk group
RMV TG
To remove PRA trunk group
MOD PRATG
To modify PRA trunk group
LST TG
To list PRA trunk group

Before adding PRA trunk group, use the related commands to obtain the following
z
PRA subscriber number: LST PRA

10-81

[Equipment ID]
PRA trunk circuits. This parameter must be defined in the ADD MGW command before
[Sub-route number]
[Signaling link number]
It specifies the PRA signaling link used by the PRA trunk group. This parameter must be
defined in the ADD PRALNK command before being referenced here.
It specifies the PRA subscriber number used by the PRA trunk group. This parameter
must be defined in the ADD PRA command before being referenced here. PRA
subscriber number is very important to a PRA trunk group and is used to control the
attributes of the PRA trunk group, such as call-in and call-out authorities, charging and
route selection. Therefore, the preceding attributes of the PRA subscriber must be
defined correctly in the ADD PRA command; otherwise, the PRA trunk might fail to be
interconnected.
[Trunk group name]
[Group direction]
It specifies the call connection direction of the PRA trunk group. The default option is
Bidirectional trunk The parameter options are described as follows:
z
Bidirectional trunk: It indicates that the local office processes the calls from and to
[Call source code]

[Circuit type]
It is reserved currently. The options include only PRA.
It specifies the trunk circuit selection policy of the trunk group. The default mode is
Cyclic. The meanings of the options are as follows:

10-82

z
Recycle: The system selects a circuit from the next one to the last selected circuit
the minimum number.
first.
User side allocation: The system selects a trunk circuit according to the command
at the user side.

It is valid for both incoming and outgoing trunks. Set the parameter by the following
principles:
z
For incoming trunks, when a subscriber of the peer office originates a call through
the incoming trunk, this parameter defines the mode how the local office obtains
the caller number from the incoming trunk if the call signaling contains no caller
number. If this parameter is set to Trunk line ID, the caller number is the trunk
circuit number. If this parameter is set to Default number, the caller number is the
default one defined in this command, that is, the PRA subscriber number.
For incoming trunks, when a subscriber of the peer office originates a call through
the incoming trunk and the incoming office signaling from the peer office contains
the caller number, the local office uses this caller number for the call. The setting is
invalid here.
For outgoing trunks, when a local subscriber originates a call through the outgoing
trunk and this parameter is set to Trunk line ID, the called number dialed by the
local subscriber must be a PRA subscriber number defined by the local office.
Otherwise, the system will reject the call. If this parameter is set to Default
number, the system allows the call.
When the PBX accesses the SoftX3000 through the PRA trunk and it occupies the
subscriber number resources of the local office, you can set the parameter caller
number provision mode of the corresponding PRA outgoing trunk to Trunk line ID so
as to prevent the PBX from using unauthorized PSTN numbers.
It identifies whether the PRA trunk is carried over a satellite circuit. You need to set it
[Call-in authority]
This parameter is reserved in the system and unnecessarily configured.

10-83

[Send initial tone]
This parameter is available only to incoming trunks, specifying whether the local office
sends the busy tone to the peer office for failed incoming trunk calls. By default, it is set
to No.
z
If it is set to No, when a call fails, the local office sends to the peer office the
Disconnect message without the Send busy tone flag. At this time, the call is
released and the peer office sends the busy tone to the caller.
If it is set to Yes, when a call fails, the local office sends to the peer office the
Disconnect message with the Send busy tone flag. At this time, the call is held
temporarily and the local office sends the busy tone to the caller through the
incoming trunk. After the caller hangs up or the timer times out, the call will be
released.
[Initial tone type]

Reserved.
This parameter is available only to incoming trunks. It controls whether the local office
sends the exceptional tone to the opposite office through the Alerting message when
the call through the incoming trunk fails.
z
If the parameter is set to No, the local office will send the Disconnect message to
the opposite office when the call fails. In this case, the call will be released and the
opposite office will send busy tone to the caller.
If the parameter is set to Yes, the local office will send the Alerting message to
the opposite office when the call fails. In this case, the call will be held temporarily
and the local office will send the exceptional tone to the caller through the
incoming trunk. The type of the exceptional tone is determined by the call
processing software based on the failure cause code. After the caller hangs up or
the timer times out, the call will be released.

Reserved.
It sets whether to request caller number. This parameter is available only to incoming
trunks. When the Whether request caller number parameter is set to YES, if the
10-84

incoming call signaling through the trunk does not contain caller number, this parameter
is used to ask the local office to request caller number from the opposite office. The
default option is YES, indicating that the local office can request caller number on
initiative. However, if this feature affects connection or connection time, the option can
be set to NO.
[Connect without or with invalid caller number]
It sets whether the local office gets a call through if the incoming call signaling through
the trunk does not contain caller number or the contained number is invalid. This
parameter is available only to incoming trunks, and the default option is YES.
[Default connect]
If querying caller number discrimination group failed (that is, the queried record is not
found), it is used to set whether to get the call through. The default option is YES,
indicating that the call will be connected through.
available only to incoming trunks. The default option is NO, indicating that the local
office will not request caller number on initiative.
[Codec prefer]
It specifies the codec mode used by the RTP audio media streams of the TMG in the
trunk group direction. Set this parameter by the following principles:
z
The preferred codec mode defined here must have been defined in the codec list
in ADD MGW. Otherwise, it is invalid.
Preferred codec is the first mode in the codec list that is supported by the MGs of both
the caller and the callee. If the codec list contains the preferred codec modes of the
caller, callee, incoming trunk group, and outgoing trunk group at the same time, the
SoftX3000 will queue a codec mode in the first position of the list according to the
principle of caller and subscriber prior to callee and trunk during call connection.
For example, for an intra-office call, if the preferred codec mode of the caller is different
from that of the callee, that of the caller is valid. For an outgoing call, if the preferred
codec mode of the caller is different from that of the outgoing trunk group, that of the
caller is valid. For a transit call, if the preferred codec mode of the local incoming trunk
group is different from that of the local outgoing trunk group, that of the local incoming
trunk group is valid. For an incoming trunk terminated call, if the preferred codec mode
of the local incoming trunk group is different from that of the local callee, that of the local
callee is valid.
10-85

[CAMA]
performs centralized accounting operations on the incoming trunk. If the value is YES,
the local office adopts the centralized accounting mode for the incoming trunk. In this
case, when the opposite office originates a call through the incoming trunk, the local
office requests the calling number on initiative through signaling if the signaling from the
originating office does not carry the calling number.
[Software parameter of service CTRL]
It sets whether PRA trunks support some special services or applications. There are 16
options for this parameter. Currently, only two options are used, and the others are
z
number contained in the IAM to the peer office in the WAN Centrex service.
Progress send tone: It is available to outgoing trunks only. If you select this option,
when the local office originates a call to the peer office through the outgoing trunk,
the local office will send to the caller resident office the Alerting message with the
Send ringback tone flag if receiving the Progress message with the progress
indicator as 1 or 8 from the peer office. At this time, the caller hears the ringback
tone sent by the terminating office. If the local office receives the Progress
message with the progress indicator as other values from the peer office, it will
send to the caller resident office the Alerting message without the Send ringback
tone flag. At this time, the caller hears the ringback tone sent by the resident office.
If the peer office connects the call slowly, the ringback tone can be sent to the
caller faster through the setting of this parameter.
Audio to speech OutTrunk:
Audio to speech InTrunk:
10.6.3 Adding PCM Port (Optional)

I. Related commands
Command
Function
ADD PCMPORT
To add PCM port
MOD PCMPORT
To remove PCM port
RMV PCMPORT
To modify PCM port
LST PCMPORT
To list PCM port

10-86


data configuration..
1)
For ISUP/TUP circuit: By default, the PCM type is E1, and the PCM codec mode is
A law when you use the command ADD N7TKC to add No. 7 trunk circuit. For
networking in countries such as the USA and Japan, the PCM type is T1, and the
PCM codec mode is law generally. In this case, you need to use the command
ADD PCMPORT to add PCM port.
2)
For PRA circuits: By default, one PRA signaling link can only control one Pulse
Code Modulation (PCM) system. Correspondingly, you can only add a maximum
of 32 PRA trunk circuits when using the ADD PRATKC command. However, when
the PRA link resources are not enough, if one PRA link is required to control
multiple PCM systems (a maximum of four E1s), you must use the ADD
PCMPORT command to add PCM port.

For detailed description, refer to 10.4.7 "Adding PCM Port (Optional).
10.6.4 Adding PRA Trunk Circuit

I. Related commands
Command
Function
ADD PRATKC
To add PRA trunk circuit
RMV TKC
To remove PRA trunk circuit
MOD PRATKC
To modify PRA trunk circuit
LST TKC
To list PRA trunk circuit

It specifies the module number of the FCCU or FCSU processing the PRA calls. This
normally.
It specifies the PRA trunk group to which the PRA trunk circuit to be added belongs.
This parameter must be defined in the ADD PRATG command before being referenced
here.
10-87

[Start circuit], [End circuit]

They are used to specify the range of the E1 circuit numbers for the PRA trunk circuits
inside the SoftX3000. The value ranges from 0 to 9999. The configuration principles of
these parameters are as follows:
z
R2, and V5 trunk circuits. The corresponding physical numbers at the TMG are
specified in the start circuit termination identifier parameter of the command.
circuit termination identifier (decimal value after converting from binary value)
must be a multiple of 32, such as 0, 32, 64, and 96.
If you does not use the ADD PCMPORT command to add PCM port, the system
regards that the PRA link only control one PCM system by default, that is, only 32
PRA trunk circuits can be added in maximum once.
If you have used the ADD PCMPORT command to add n (1 n 4) PCM ports for
a PRA link, a maximum of n*32 PRA trunk circuit can be added once.

It is one of the parameters used for interworking with the AMG. It specifies the number
of the physical port of the AMG (UMG8900) corresponding to time slot 0 of the start
PRA trunk E1. It consists of digits and/or the symbol "/". Set this parameter by the
z
parameter.

parameters of various layers in ADD TIDLAY. The basic process is as follows: After you
enter a termination ID, the system abstracts the digit of each layer, converts it into a
[Circuit state]
It sets the initial state of a trunk circuit. Generally, the default value Available is used.
When adding several circuits continuously, you need to set it to Unavailable if a circuit
of the TMG is used as a signaling timeslot.

10-88

10.7 Configuring AT0 Trunk Data

10.7.1 Overview
The AT0 trunk data defines the AT0 trunk information at the SoftX3000 side, such as
charging, call barring and interconnection. To configure the AT0 trunk data, make sure
that the equipment data, local office data, charging data, MG data, and routing data
have been configured. See Figure 10-1.
During the configuration, the AT0 trunk data will reference some parameters defined in
the local office data, charging data, MG data, and routing data. Table 10-17 shows the
details.
Table 10-17 Parameter referencing relationships between AT0 trunk data and other
data
Input parameter
Parameter
Output parameter
Defined in
Parameter
Referenced in
Call source code
Local office data
Charging data

source code
Charging data
Equipment ID of the TMG
MG data
Subroute number
Routing data
II. Preparations
Before configuring the AT0 trunk data, make sure that all preparations are done as
SN
Item
Remark
Numbering
range of AT0
trunk circuits
These are unified logical numbers assigned inside the

SoftX3000 to No.7, PRA, and AT0 trunk circuits. The
corresponding physical numbers at the TMG are specified
in the start circuit termination identifier parameter.
Termination ID
of circuit number
It is one of the interconnection parameters between the

SoftX3000 and the TMG.

10-89


Table 10-19 lists the general steps for configuring the AT0 trunk data.
Step
Description
Command
Add AT0 trunk group
ADD AT0TG
Add AT0 trunk circuit
ADD AT0TKC

Figure 10-10 illustrates the referencing relationship between key parameters used
when the AT0 trunk data is configured.
ADD AT0TG
[Equipment ID]
[Sub-route number]
ADD AT0TKC
[Start circui numbert]
10.7.2 Adding AT0 Trunk Group

I. Related commands
Command
Function
ADD AT0TG
To add AT0 trunk group
RMV TG
To remove AT0 trunk group
MOD AT0TG
To modify AT0 trunk group
LST TG
To list AT0 trunk group

10-90


Before adding an AT0 trunk group, use the related commands to obtain the following
1)
2)
3)
Note:
This section only introduces the parameters closely related to AT0 trunk group. For the
other parameters, refer to online help or 10.5.5 Adding R2 Trunk Group.

[Group direction]
It specifies the call connection direction of the AT0 trunk group. For the AT0 trunk group,
you need to set this parameter to outgoing trunk, indicating that the AT0 trunk group
only processes the outgoing calls to the peer office.
[Equipment ID]
It specifies the equipment ID of the access media gateway (such as UMG8900 or
AMG5000) providing AT0 trunk circuits. This parameter must be defined in the ADD
MGW command before being referenced here.
[Sub-route number]
[Trunk group name]
[Call source code]
It specifies the trunk circuit selection policy of the trunk group. For the AT0 trunk group,
you can only select "Minimum. The other options will lead to connection failure.
10-91

[Call-in authority]
[DOD2]
This parameter is available to outgoing trunks to control whether the local callers can
hear the secondary dial tone sent by the peer office after seizing the outgoing trunk. If
AT0 trunk is used for PBX DDI networking, set the parameter to No.
It is one of the charging attributes of the (incoming) trunk group. Its value ranges from 0
to 255. The value 254 is the wildcard that cannot be used for trunk charging. The
value 255 indicates no charging of incoming trunks. This parameter must be defined
in ADD CHGIDX or ADD CHGGRP before being referenced here. For the detailed
information about charging, see Chapter 4, Configuring Charging Data, in this
manual.
It is one of the charging attributes of the (outgoing) trunk group. Its value ranges from 0
to 255. The value 254 is the wildcard that cannot be used for trunk charging. The
value 255 indicates no charging of outgoing trunks. This parameter must be defined in
ADD CHGIDX or ADD CHGGRP before being referenced here. For the detailed
manual.
[Waiting seizure ACK time]
This parameter is available only to outgoing trunks. After the local office seizes a trunk
circuit and sends the seizure signal (line signaling) to the opposite office, this parameter
specifies the maximum time for waiting for the seizure acknowledgement signal (dial
tone) that is returned by the opposite office. The value range is 0 to 10, and the unit is
second. The default value is 5.
If the local office receives no seizure acknowledgment signal after waiting timeout, it
automatically enters the seizure acknowledgment state.
[Ringing duration]
This parameter is available only to incoming trunks. When an originating subscriber
calls a local office subscriber through an incoming trunk, if the callee is idle, the local
10-92

office simultaneously sends the ringing tone to the callee and the ringback tone to the
originating office. This parameter specifies the maximum time during which the local
office monitors the ringing at the callee. The value range is 0 to 65535, and the unit is
second. The default value is 240.
[Back tone time]
This parameter is available only to outgoing trunks and only when the parameter
Polarity check in this command is set to Yes. It defines the maximum duration during
which a local caller (or an incoming trunk) can hear the ringback tone. The value range
is 0 to 90, and the unit is second. The default value is 30.
If the local office detects the polarity reversal signal on the trunk when the caller (or the
incoming trunk) hears the ringback tone, it regards this time point as the start time for
charging. If the caller hears the ringback tone until timeout, the local office automatically
releases the call.
The time when the local caller enters the state of hearing the ringback tone is not the
time when the terminating office starts sending the ringback tone to the local office, but
the time after one timer duration when all digits of the called number are sent. The timer
duration is defined in the parameter Listening to ringback tone delay in this command.
[Number send delay]
This parameter is available only to outgoing trunks, used to specify the duration
between the time when the local office receives the outgoing trunk circuit seizure
acknowledgement message returned by the peer office and the time when the local
office sends the first digit. The value range is 0 to 10, and the unit is second. The default
value is 1.
If the time when the local office starts to seize the outgoing trunk circuit is counted, the
delay for the local office to send the first digit to the peer office is Waiting seizure ACK
time + Number send delay.
[Automatic answer time]
This parameter is available only to outgoing trunks and only when the parameter
Polarity check in this command is set to No. After the ringback tone is played to the
local subscriber (through the incoming trunk), this parameter specifies the monitoring
duration after the local subscriber automatically enters the conversation state (suppose
the callee has picked up the phone). The value range is 0 to 30, and the unit is second.
The default value is 6.
If the peer PBX does not provide the polarity reversal function on subscriber boards,
the local office cannot judge accurately the answer time of an AT0 outgoing trunk call
according to the off-hook of the callee. After this parameter is set, the local office takes
the Alerting signal send delay + Automatic answer time after all digits of the called
number are sent as the charging start time by default no matter whether the callee picks
up the phone or when the callee picks up the phone.
[Polarity check]
10-93

It defines whether the local office detects the polarity reversal signal sent by the peer
PBX after an outgoing trunk of the local office seized. It is available only to outgoing
trunks. The default value is Yes.
If the local office detects no polarity reversal signal on the trunk within the specified
timer duration, the call fails. The timer length is defined in the parameter Alerting signal
send delay in this command.
[Alerting signal send delay]
It specifies the delay for a local caller (or an incoming trunk) to hear the ringback tone
after the local office sends all digits of the called number through the outgoing trunk. It is
available only to outgoing trunks. The value range is 0 to 30, and the unit is second.
The default value is 5.
10.7.3 Adding AT0 Trunk Circuit

I. Related commands
Command
Function
ADD AT0TKC
To add AT0 trunk circuit
RMV TKC
To remove AT0 trunk circuit
MOD AT0TKC
To modify AT0 trunk circuit
LST TKC
To list AT0 trunk circuit

This parameter specifies the module number of the FCCU or FCSU processing the AT0
trunk calls. This parameter is defined in the ADD BRD command and referenced here.
normally.
This parameter specifies the AT0 trunk group to which the AT0 trunk circuits to be
added belongs. This parameter is defined in the ADD AT0TG command and
referenced here.
They specify the E1 numbering range of the AT0 trunk circuits in the SoftX3000. The
value ranges from 0 to 6399. Set this parameter by the following principles:
z
R2, V5, and AT0 E1 trunk circuits in an FCCU/FCSU module. The corresponding
10-94

physical numbers at the TMG are specified in the start circuit termination ID
parameter in this command.
z
A maximum of 32 trunk circuits can be added in one execution of this command. If

you want to add more than 32 trunk circuits, execute the command several times.
[Master ID of start circuit]

Reserved. Generally, the default value Master is used.
[Circuit state]
This parameter specifies the initial state of trunk circuits. Generally, the default value
Available is used.
This parameter specifies the start physical port number of a batch of trunk circuits in the
resident AMG (UMG8900 or AMG5000).It consists of digits and/or the symbol "/". Set
z
parameter.

10.8 Configuring V5 Trunk Data

10.8.1 Overview
The V5 trunk data is used to configured the E1 information of the SoftX3000 for
interconnecting with such V5 devices as access network devices and base station
controller. The E1 information includes start E1 number, end E1 number and V5 link ID.
The V5 trunk data configuration must not be done before the equipment data, MG data
and V5UA data is configured. See Figure 10-1.
During the configuration, some parameters defined in the equipment data, MG data
and V5UA data will be referenced in the V5 trunk data. Besides, some parameters
10-95

defined in the V5 trunk data will be referenced when the V5 interface data is configured.
Table 10-20 Parameter referencing relationships between V5 trunk data and other
data
Input parameter
Name
Output parameter
Defined in
Name
Referenced in
Equipment ID of the media

gateway
MG Data
V5 trunk group
number
V5 interface
data
Module number of
FCCU/FCSU
Equipment data
V5UA link set index
V5UA data
II. Preparations
Before configuring the V5 trunk data, make sure that all preparations are done as
SN
Item
Remark
Start E1 number and end E1 number

of V5 trunk group
The internal E1 numbers of the

SoftX3000
V5 link IDs of E1s in V5 trunk group
For interworking with V5 access

network device
Terminal ID of the MG corresponding

to the start E1 of V5 trunk group
For interworking with access media

gateway
MG E1 link IDs of V5 trunk group
For interworking with access media

gateway

Table 10-22 lists the general steps for configuring the V5 trunk data.
Step
Description
Command
Add V5 trunk group
ADD V5TG
Add V5 trunk circuit
ADD V5TKC

10-96


when the V5 trunk data is configured.
ADD V5TG
[Equipment ID]
ADD V5TKC
[Module number]
[Start E1 number]
[End E1 number]
10.8.2 Adding V5 Trunk Group

I. Related commands
Command
Function
ADD V5TG
To add V5 trunk group
RMV V5TG
To remove V5 trunk group
MOD V5TG
To modify V5 trunk group
LST V5TG
To list V5 trunk group

[Equipment ID]
It specifies the equipment ID of the AMG (such as UMG8900) providing V5 trunk
circuits. This parameter must be defined in the ADD MGW command before being
referenced here.
[Trunk group name]

10-97

10.8.3 Adding V5 Trunk Circuit

I. Related commands
Command
Function
ADD V5TKC
To add V5 trunk circuit
RMV V5TKC
To remove V5 trunk circuit
MOD V5TKC
To modify V5 trunk circuit
LST V5TKC
To list V5 trunk circuit

It specifies the module number of the FCCU or FCSU processing the V5 calls. This
command ADD MGW for adding the UMG; otherwise, the UMG circuits cannot work
normally.
[Start E1 number], [End E1 number]
They are used to specify the E1 number range of the V5 trunk circuits in the SoftX3000.
The value ranges from 0 to 312. The configuration principles for these two parameters
are described as follows:
z
This range of E1 numbers includes the unified logical numbers assigned in a

particular FCCU/FCSU module to E1 trunk circuits regarding No. 7, PRA, R2, and
V5 inside the SoftX3000. The corresponding physical numbers at the access
media gateway are specified in the start MG E1 link ID parameter in this
command.
For V5.1 interface, the end E1 number must be equal to the start E1 number, that
is, only one E1 can be configured.
For V5.2 interface, the difference between the end E1 number and the start E1
number must be less than or equal to 15, that is, a maximum of 16 E1s can be
configured.

It specifies the V5 trunk group to which the V5 trunk circuit to be added belongs. This
parameter must be defined in the ADD V5TG command before being referenced here.
[Start E1 link ID]

10-98

It is one of the parameters used for interworking with the V5 access network device. It
uniquely identifies a 2.048 Mbit/s link in the corresponding V5 interface. In the same V5
trunk group, the E1 link IDs must not be repeated.
[V5UA linkset number]
It specifies the V5UA link set bearing the physical C channels of the corresponding V5
interface. This parameter must be defined in the ADD V5UALKS command before
[Start MG termination ID]
It is one of the parameters used for interworking with the AMG. It specifies the circuit
terminal ID of the time slot 0 on the start E1 for the V5 trunk circuit at the AMG side
(UMG8900). It consists of digits and/or the symbol "/". Set this parameter by the
z
parameter.

[Start MG E1 link ID]
It is one of the parameters used for interworking with the AMG. It specifies the E1 link ID
at the AMG side corresponding to the start E1 of the V5 trunk group. In the same
access media gateway, the E1 link IDs must not be repeated.
[Equipment ID]
It specifies the equipment ID of the media gateway (UMG8900) to which the V5 trunk
circuit belongs. This parameter must be defined in the ADD MGW command before
being referenced here. The parameter configuration principle is described as follows:
z
When the active and standby links of a V5 interface are provided by a media
gateway, that is, the V5 interface is homed to one UMG8900, you must not specify
the parameter.
Suppose that the active and standby links of a V5 interface are provided by two
media gateways, that is, the V5 interface is homed to two UMG8900s controlled by
the same SoftX3000. If the V5 trunk circuit belongs to the UMG8900 specified by
10-99

the command ADD V5TG, you must not specify the parameter. Otherwise, set the
parameter to the equipment ID of the UMG8900 to which the V5 trunk circuit
belongs.
The parameter backs up the V5 interface in equipment level. That is, the V5 interface of
a V5 access network equipment can be homed to two UMG8900s controlled by the
same SoftX3000. In normal cases, the two UMG8900s bear all calls between
subscribers of the V5 access network in load sharing mode. When one UMG8900 is
faulty, the other can bear all calls between subscribers of the V5 access network.
10.9 Configuring Trunk Group Bearer Data

10.9.1 Overview
The trunk group bearer data is used to configure information related to outgoing trunk
calls (that is, outgoing calls), such as trunk occupancy point, caller number change and
called number change. During the configuration, some parameters defined in the
number analysis data and trunk group data will be referenced in the trunk group bearer
data. Table 10-23 shows the details.
Table 10-23 Parameter referencing relationship between trunk group bearer data and
other data
Input parameter
Name
Output parameter
Defined in
Name
Referenced in
Trunk group number
Trunk data
Number change index

Table 10-24 lists the general steps for configuring the trunk group bearer data.
Step
Description
Command
Add TOS changing index (optional)
ADD TOSC
Add trunk group bearer
ADD TGLD
Add trunk group bearer index
ADD TGLDIDX

10-100

III. Parameter referencing relationship

when the trunk group bearer data is configured.
ADD TGLD
[Bearer index]
[Trunk occupy point]
[Caller number sending change index]
[Callee number sending change index]
ADD TGLDIDX
[Trunk group]
[Call source]
[Call prefix]
[Bearer index]
10.9.2 Adding TOS Changing Index (Optional)

I. Related commands
Command
Function
ADD TOSC
To add TOS changing index
RMV TOSC
To remove TOS changing index
MOD TOSC
To modify TOS changing index
LST TOSC
To list TOS changing index

data configuration.:
Type of Service (TOS) is an 8-bit field in the header of the IP packet, used to control the
router to transfer the IP packet. See Figure 10-13 for its bit structure.
Priority sub-field
7
TOS sub-field
5
Reserved
2
Figure 10-13 Bit structure of TOS

10-101

In Figure 10-13, the priority sub-field occupies three bits and is not used currently (all
bits must be set to 0). The TOS sub-field occupies four bits: bit 4 stands for the
minimum delay, bit 3 stands for the maximum throughput, bit 2 stands for the highest
reliability, and bit 1 stands for the minimum charge. Among the four bits, only one can
be set to 1 at one time. If the four bits are all set to 0, it means common service. The
reserved bits must be set to 0.
In actual application, TOS is used to control the router of the gateway office to route the
outgoing traffic. For example, the pure audio traffic is routed to the dedicated VoIP
network so as to ensure Quality of Service (QoS), and the video traffic is routed to the
Internet. To set traffic routing control, you must use the command ADD TOSC to add
the TOS changing index.

[TOS changing index]
It defines a TOS changing index uniquely in the SoftX3000. Its value ranges from 0 to
255.
[TOS changing type]
It defines the type of the TOS change. The options are
z
Not need to change TOS value: It indicates that the SoftX3000 neither modifies
the TOS field in the IP packet, nor notifies the GW, terminal, or NAT device with a
signaling message to modify the TOS field in the media stream packet.
Need to change TOS value: It indicates that the SoftX3000 not only modifies the
TOS field in the IP packet, but also notifies the GW, terminal, or NAT device with a
signaling message to modify the TOS field in the media stream packet.
[TOS value after changing]

As one of the parameters for the SoftX3000 to interwork with the router of the gateway
office, it defines the TOS field in a specified IP packet manually. The parameter is valid
only when there is a need to change the TOS value. It is a decimal value, ranging from
0 to 255. Generally, bigger TOS value indicates higher service level. If it is set to 255,
it indicates no change.
The carrier must plan the relationship between various services and TOS values in
advance, and the related GW, terminal, NAT, and router must support the identification
of the TOS field in the IP packet; otherwise, the TOS traffic routing function cannot be
implemented.
10.9.3 Adding Trunk Group Bearer

I. Related commands
Command
ADD TGLD
Function
To add trunk group bearer
10-102

Command
Function
RMV TGLD
To remove trunk group bearer
MOD TGLD
To modify trunk group bearer
LST TGLD
To list trunk group bearer

[Bearer index]
It identifies a piece of trunk group bearer data uniquely in the SoftX3000. If you bind a
trunk group bearer index parameter with a trunk group with ADD TGLD or ADD
TGLDIDX, the trunk group can implement number change, TOS change, and other
special services through trunk group bearer.
[Trunk seizure point]
It defines the minimum length of the called number that causes the local office to
occupy the outgoing trunk. The length here refers to the length after number change.
During the trunk number analysis, the system first judges whether the called number
complies with the number length prescribed by Minimal number length in the call
prefix data. If not, the system continues to wait for the called number. If yes, the system
then judges whether the called number complies with the number length prescribed by
Trunk occupy point in the trunk bearer data. When the called number complies with
the number length prescribed by Trunk occupy point, the system begins occupying
the outgoing trunk.
[Caller sending change index]
It specifies the index for calling number change before the local office sends the calling
number through the outgoing trunk. This parameter must be defined in the ADD DNC
[Callee sending change index]
It specifies the index for called number change before the local office sends the called
number through the outgoing trunk. This parameter must be defined in the ADD DNC
[Caller TOS change index]
It specifies the change of the TOS field of the IP packet made by the local office when
there is an incoming call. It is available only to incoming trunks. It must be defined in the
command ADD TOSC before being referenced here.
[Callee TOS change index]
It specifies the change of the TOS field of the IP packet made by the local office when
there is an outgoing call. It is available only to outgoing trunks. It must be defined in the
command ADD TOSC before being referenced here.
10-103

If the original TOS value in the incoming signaling message is inconsistent with that
after callee TOS change, or the TOS value after caller TOS change is inconsistent with
that after callee TOS change, the system will use the TOS value with higher priority for
the call.
[Direct national route]
It specifies whether the local office shall forcibly set the national/international call
indicator bit to 1 (that is, process the call as an international call) when the SoftX3000
transits an incoming or outgoing international call. The bit is in the forward call
indicator field in the IAM message sent from the local office to a lower national office or
the peer international office.
The default option is No, indicating that the local office does not process the
international call on the trunk group according to the above description.
[Echo suppress]
It specifies whether the local office enables the echo suppress function on the incoming
trunk direction. The default option is No, indicating that the echo suppress function is
disabled.
It specifies whether the local office sends the caller number to the peer office. It is valid
only for outgoing trunks. The default option is No, indicating that the local office does
not send the caller number to the peer office.
[DOD2]
It controls whether the local caller can hear the secondary dial tone sent by the peer
office after seizing the outgoing trunk. It is valid only for outgoing trunks. The default
option is NO.
[DOD2 position]
It specifies the duration between the time when a local caller seizes the outgoing trunk
and the time when the caller hears the secondary dial tone sent by the peer office. It is
valid only when "DOD2" is set to Yes. The value of the parameter ranges form 0 to 15
with the unit as second. The default value is 1.
[Delay ring back position]
It specifies how long the local office delays to send Alerting message to the peer office
after the peer office initiates a call through an incoming trunk, and the call is connected
successfully. It is valid only for incoming trunks. The value of the parameter ranges form
0 to 15 with the unit as second. The default value is 7.
[FAS]
It specifies whether the local office can receive the FAS signal sent by the peer office. It
is valid only for incoming trunks. The default option is "No.
[Overlap send called number]

10-104

It specifies whether a trunk group supports overlap code sending mode. The SoftX3000
supports the following two code sending modes:
z
Overlap code sending: When the system receives enough digits of the called
number for judging the route, it sends them to the opposite office through the
signaling Initial Address Message (IAM) or Initial Address Message with
Information (IAI), and then sends the remained digits of the called number one by
one through other signaling messages, for example, Subsequent Address
Message with One signal (SAO) or Subsequent Address Message (SAM).
Group code sending: After the system collects all the digits of the called number, it
sends them to the opposite office through one signaling message.
The overlap code sending mode features fast connection but it occupies more CPU
resources. The group code sending mode occupies fewer CPU resources, but the
connection is slow, which might affect the quality of the telecom services. The default
mode is overlap code sending. However, when the SoftX3000 interconnects with a
switch complying with ANSI through the No.7 trunk group, you must set this parameter
to No.
[Extend overlap send called number]
It sets whether a No.7 trunk group supports extended overlap code sending mode, that
is, whether the trunk group can send the remained digits of the called number to the
peer office through an SAM.
It is different from the overlap code sending mode. In the latter mode, the remained
digits of the called number can be sent to the peer office in one or several SAOs/SAMs.
However, this mode only allows the remained digits to be sent to the peer office in one
SAM.
10.9.4 Adding Trunk Group Bearer Index

I. Related commands
Command
Function
ADD TGLDIDX
To add trunk group bearer index
RMV TGLDIDX
To remove trunk group bearer index
MOD TGLDIDX
To modify trunk group bearer index
LST TGLDIDX
To list trunk group bearer index


10-105

It specifies the number of the outgoing trunk group to which the trunk group bearer
index is to be added. This parameter must be defined in the command ADD SIPTG,
ADD H323TG or ADD N7TG before being referenced here.
[Call source code]
It is one of the match conditions for trunk group bearer data. When a call seizes the
outgoing trunk group, the parameter defines the call source code of the calling number
that matches the trunk group bearer data. The value range is 0 to 65535. 65534 is a
wildcard that represents all call source codes. This parameter must be defined in the
ADD CALLSRC command before being referenced here.
When the call processing software analyzes the trunk group bearer, if the call source
code of several trunk group bearer indexes matches the current call in the system, the
wildcard 65534 has the lowest priority, that is, the system matches the other call source
codes as prior.
[Call prefix]
outgoing trunk group, the parameter defines the prefix of the called number that
matches the trunk group bearer data. It is the first several digits of the called number.
eeeeeeee is the wildcard, indicating all prefixes.
When the call processing software analyzes the trunk group bearer, if the call prefix of
several trunk group bearer indexes matches the current call in the system, the wildcard
eeeeeeee has the lowest priority, that is, the system matches the other call prefixes as
prior.
[Local DN set]
outgoing trunk group, the parameter defines the local DN set of the call prefix that
matches the trunk group bearer data. It must be defined in the command ADD
LDNSET before being referenced here.
[Bearer index]
It specifies the trunk group bearer index used by the trunk group. This parameter must
be defined in the ADD TGLD command before being referenced here.
10.10 Other Commands

10.10.1 Adding Trunk Group Append Configuration
I. Related commands
Command
Function
ADD TGAP
To add trunk group append configuration
RMV TGAP
To remove trunk group append configuration

10-106

Command
Function
MOD TGAP
To modify trunk group append configuration
LST TGAP
To list trunk group append configuration

data configuration.
The command ADD TGAP is used to add trunk group append configuration data such
as convert cause value, convert protocol cause value, charging complaint, incomplete
call watch, allow divert, UC analysis flag, and AOC99 flag.

It specifies the number of the trunk group to which append configuration data of the
trunk group is to be added. This parameter must be defined in the command ADD
SIPTG, ADD H323TG, ADD N7TG, ADD N1TG, and ADD PRATG before being
referenced here.
[Convert cause value]
Reserved. It indicates whether to convert the release cause code.
[Convert protocol cause value]
Reserved. It indicates whether to convert the protocol cause code.
[Charging complaint]
It is one of the charging attributes of the trunk group. It sets whether to generate a
complaint ticket when the trunk group is charged. The default value is NO, indicating
that the system will not generate a complaint ticket. If it is set to YES, complaint tickets
will be generated for both incoming and outgoing trunk calls.
[Incomplete call watch]
It defines whether the system records the failed calls on one trunk group, that is,
whether the system generates watch bills for failed calls. The options are
z
No watch: It is the default value, indicating that the system does not record the
failed calls occurred on the trunk group.
Watch caller: It indicates that the system only records the failed calls occurred on
the incoming trunk group.
Watch callee: It indicates that the system only records the failed calls occurred on
the outgoing trunk group.
Watch both: It indicates that the system records all failed calls occurred on the
trunk group.

10-107

[Allow divert]
It indicates whether the SoftX3000 supports the call redirection function in the direction
of an outgoing trunk. It is available to outgoing trunks only. It is No by default, for
preventing nested dialing on the outgoing trunk. If you set it to Yes, the local office will
connect the call it originated to the peer office through the outgoing trunk if the peer
office redirects the call to the local office after call analysis (that is, the signaling
message returned by the peer office contains redirection number).
[UC analysis flag]
In UC service, UC subscribers can bind the numbers of non-local subscribers as
original binding numbers. The bound numbers of non-local subscribers can be fixed
numbers or mobile numbers. The parameter specifies whether the system immediately
triggers caller UC service when there is an incoming call on the trunk group, and the
calling number of the incoming call fully matches an original binding number in the
system. It is valid only for incoming trunks. The default option is No.
[AOC99 flag]
It specifies if the SoftX3000 sends or receives AOC99 charging information in the ISUP
signaling messages on the No.7 trunk group. It is No by default. If the charging
manner (which can be set with ADD CHGANA) of the charging source code of the trunk
group or the outgoing trunk charging source code is Send AOC99 charging
information, Receive AOC99 charging information, or Transfer AOC99 charging
information, you need to set this parameter to Yes.
[Carrier selection flag]
It specifies if the SoftX3000 needs to contain carrier selection code in the IAM sent
through the No. 7 outgoing trunk group. It is available to No. 7 outgoing trunk groups
only. It is No by default.
When the local office serves as a gateway office and the peer office needs to perform
CAC authentication to the IAM sent by the local office, you must set this parameter to
Yes. At this time, when the local office originates a call to the peer gateway through
the No. 7 outgoing trunk group specified in this command, it will contain the parameter
carrier access code of the local office information table (which can be set with SET
OFI) in the IAM on the outgoing trunk.
[AOC99 national regulation]
It indicates the nation identification code contained in the AOC99 charging information
sent by the SoftX3000 through the No. 7 trunk group. It is available to outgoing trunks
only. It ranges from 0 to 65535. It is a fixed code.
[AOC99 network]
It indicates the network identification code (also called carrier identification code)
contained in the AOC99 charging information sent by the SoftX3000 through the No.7

10-108

trunk group. It ranges from 0 to 65535. It is allocated country-wide by the telecom

department.
[AOC99 node identification]
It indicates the node identification code (also called office identification code) contained
in the AOC99 charging information sent by the SoftX3000 through the No.7 trunk group.
It ranges from 0 to 65535. It is allocated country-wide by the telecom department.
10.10.2 Adding Caller Category Transform Index

I. Related commands
Command
Function
ADD CATRNS
To add caller category transform index
RMV CATRNS
To remove caller category transform index
MOD CATRNS
To modify caller category transform index
LST CATRNS
To list caller category transform index

data configuration.
When the SoftX3000 interconnects with the switching equipment of other manufactures
through ISUP trunk, the caller category transmitted through signaling messages
between two offices might not meet the requirements of each other, because
differences might exist in definition and usage of caller category in different countries or
by different equipment manufacturers. In this case, you can use the commands ADD
CATRNS and ADD ICATRNS at the SoftX3000 side to add the conversion relationship
between caller categories to make them of both offices matched.

[Call source code]
It specifies the call source whose caller category transform index is to be configured.
This parameter must be defined in the ADD CALLSRC command before being
referenced here.
It specifies the number of the trunk group whose caller category transform index is to be
configured. This parameter must be defined in the command ADD SIPTG, ADD N7TG,
or ADD N1TG before being referenced here.
[Transform index]

10-109

It identifies a transform index uniquely for the specified incoming trunk group of a call
source in the SoftX3000. That is, you can only use one transform index for the call
source code and trunk group number defined in this command.
Although the value of this parameter is of enumeration type, it has no special meanings
and is only used to set up the indexing relationship with the internal caller category
transform index table (defined in ADD ICATRNS). There are 11 options for this
parameter.
10.10.3 Adding Internal Caller Category Transform

I. Related commands
Command
Function
ADD ICATRNS
To add internal caller category transform
RMV ICATRNS
To remove internal caller category transform
MOD ICATRNS
To modify internal caller category transform
LST ICATRNS
To list internal caller category transform

data configuration.
When the SoftX3000 interconnects with the switching equipment of other manufactures
through ISUP trunk, the caller category transmitted through signaling messages
between two offices might not meet the requirements of each other, because
differences might exist in definition and usage of caller category in different countries or
by different equipment manufacturers. In this case, you can use the commands ADD
CATRNS and ADD ICATRNS at the SoftX3000 side to add the conversion relationship
between caller categories to make them of both offices matched.

[Transform index]
It identifies a transform index uniquely for an internal caller category in the SoftX3000.
Although the value of this parameter is of enumeration type, it has no special meanings.
There are 11 options for this parameter.
[Caller inner calling category]
It defines the caller category before change, that is, the caller category received by the
local office from the incoming signaling messages (for example, ISUP messages). Its
value ranges from 0 to 255. It must be negotiated and kept consistent with that of the
opposite office.

10-110

[New inner calling category]

It defines the caller category in the SoftX3000 after change, that is, the new caller
category transformed from the one received by the local office from the incoming
signaling messages (for example, ISUP messages). Its value ranges from 0 to 255.
Before setting this parameter, consult Huawei technical engineers.

10-111

Chapter 11 Configuring Number Analysis Data

11.1.1 Call Prefix
I. Basic concept
A call prefix is the first few digits or the complete form of the called number. It is the
subset of the called number. For instance, the call prefix of called number 28970133
can be
z
The first digit:
The first three digits:
289
The first five digits:
28970
The complete number:
28970133
The number analysis table is the collection of all prefixes. If multiple prefixes exist in
the same number analysis table as exemplified above, the one matches the most
digits of the called number will be used. The call prefix determines the service
category, service attribute, and route selection.
For instance, if the dialed number is 55551345, the prefix 55551 will be used, rather
than 5 or 555.
II. Relationship between call prefix and DN set

The call prefix is the prefix of the number dialed by the call source. The DN set is a
collection of prefixes. To meet the requirement of different networking applications,
the DN set is divided into global DN set and local DN set.
1)
Global DN set
The SoftX3000 supports the hybrid of public and private networks. An office can be
logically divided into public network and private network applications. To identify these
networks, a global DN set is used to represent a public or private network.
2)
Local DN set
The SoftX3000 supports the application of multiple area codes and multiple national
codes. To identify these logical networks, a local DN set is used to represent a local
network or national network.

11-1

Figure 11-1 illustrates the relationship between call prefix, local DN set and global DN
set.
Call prefix
Local DN
set 0
Call prefix
Global DN set 0
Call prefix
Local DN
set 1
Call prefix
Call prefix
Local DN
set 2
Global DN set 1
Call prefix
Figure 11-1 Relationship between call prefix, local DN set and global DN set
z
A local DN set stands for a local or national network. Multiple DN sets can share
the same call prefix.
The call prefix is valid only within the local DN set which it belongs to. It is invalid
for the call source of another local DN set to dial the call prefix directly.
For calls between call sources of the same global DN set but different local DN
set, it is not required to change the global DN set.
For calls between call sources of the different global DN sets, it is required to
change the global DN set.
11.1.2 Digit Map

A digit map is a dialing plan resident in the Media Gateway (MG) used for detecting
and reporting digit events received on a Termination. The digit map is used to improve
the efficiency of MG sending dialed digits. MG will send all digits of a called number in
a message when they conform to one of the dialing plans defined in the digit map. If
the dialed number conforms to none of the dialing plans defined in the digit map, the
MG releases the call and sends the busy tone to the caller.
The format of digit map has been strictly defined in MGCP and H.248 protocol
respectively. The digit map includes a collection of digit strings. When the dialed digits
received by MG conform to any one of the digit strings, the number collection
completes.
11-2

I. Digit map defined in MGCP

Table 11-1 lists the meanings of digits or letters defined in MGCP.
Table 11-1 Digit map defined in MGCP
Digit or letter
Meaning
0 to 9
A to D
It is used as a wildcard, representing any digit from 0 to 9.
It means that on detection of timer timeout is detected. If there are

still digits remained when the dialing plan is matched, they will be
reported one after another.
It stands for * in DTMF mode.
It stands for # in DTMF mode.
It stands for zero or more digits or letters that precedes it.
It is used to separate digit strings. Each digit string is a dialing plan.
[]
It indicates that any one of the digits or digit strings can be

selected.
For instance, when you use ADD LDNSET to add the local DN set, the SoftX3000 will
automatically configure the MGCP-based digit map by default as:
[2-8]xxxxxx|13xxxxxxxxx|0xxxxxxxxx|9xxxx|1[0124-9]x|*|#|x. #|[0-9*#]. T
II. Digit map defined in H. 248

Table 11-2 lists the meaning of digits or letters defined in H.248.
Table 11-2 Digit map defined in H.248
Digit or letter
Meaning
0 to 9
A to D
It stands for * in DTMF mode.
It stands for # in DTMF mode.
It is used as a wildcard, designating any event corresponding to

symbols in the range of 0 to 9.

11-3

Digit or letter
Meaning
It stands for short (S) timer. If a string of digits received matches a

dialing plan in the digit map, but it is possible that it might match
several dialing plans when more digits are received, the match
shall not be reported immediately. MG must use the short timer S
(for example, 8 seconds) to receive more digits.
It stands for long (L) timer. If MG finds that at least one more digit is
needed for matching the dialing plan, the inter-digit timer value
should be set to the long timer L (for example, 16 seconds).
A "Z" designates a long duration event: placed in front of the

symbol(s) designating the event(s) which satisfy a given digit
position, it indicates that that position is satisfied only if the duration
of the event exceeds the long-duration threshold.
It stands for zero or more digits or letters that precedes it.
It is used to separate digit strings. Each digit string is a dialing plan.
[]
It indicates that any one of the digits or digit strings can be

selected.
For instance, when you use ADD LDNSET to add the local DN set, the SoftX3000 will
automatically configure the H.248 digit map by default as:
[2-8]xxxxxx|13xxxxxxxxx|0xxxxxxxxx|9xxxx|1[0124-9]x|E|F|x.F|[0-9].L
11.1.3 Number Change

There are two types of number changecaller number change and called number
change. The former is the conversion of caller number, address nature, call source
attributes, charging attributes, route selection attributes, and subscriber type. The
latter is the conversion of a called number. The SoftX3000 provides three kinds of
number change features.
1)
Number change based on call source
The SoftX3000 implements number change on the caller (including incoming trunks)
number and the dialed number of a certain call source before starting number
analysis.
2)
Number change based on call prefix
The SoftX3000 implements number change when the caller dials a certain prefix. The
SoftX3000 starts number change before starting number analysis.
3)
Number change based on caller prefix
When the caller number sent by the originating office through the incoming trunk
matches a certain caller prefix, the SoftX3000 starts number change of the caller
number before starting number analysis.

11-4

Table 11-3 Implementations of three number change features

Number change based on
Implementation
Caller number discrimination and number preparation
of call source (ADD CALLSRC)
Call source
Caller number analysis (ADD CNACLR)

Call prefix
Processing call prefix (ADD PFXPRO)

Trunk group bearing (ADD TGLD)
Caller prefix
Caller number discrimination (ADD CALLSRC)
In addition, the SoftX3000 supports the special called number change to meet the
requirement of the remote network access function on changing large quantity of
irregular called numbers.
I. Caller number change

Caller number change is used for:
z
PBX subscriber sending the same caller number (PBX pilot number)
Distinctive charging for different callers of the same call source
Universally changing the format of caller number sent from incoming trunk to the
local office.
The SoftX3000 provides multiple solutions on caller number change:

z
By caller number discrimination of call source (ADD CALLSRC)
The call source, which defines caller attributes, can also be modified when you wish to
implement caller number change. You can use this option to change the address
nature of the caller number. During charging, the caller number displayed on the bill is
the new caller number.
z
By caller number discrimination (ADD CLRDSN)
The caller number discrimination is used for call barring. It also changes the charging
source code of the caller or the trunk group. During charging, the caller number
displayed on the bill is the new caller number.
z
By caller number analysis (ADD CNACLR)
It can implement caller number change and called number change. It focuses on
caller number change according to different combinations of call prefix and call source.
It not only changes the number, but also changes the route selection source code,
failure source code, charging source code, and subscriber category. During charging,
the caller number displayed on the bill is the new caller number.
z
By processing call prefix (ADD PFXPRO)

11-5

It implements both caller number change and called number change. It focuses on
caller number change according to different combinations of call prefix and call source.
This method changes the contents of the caller number only. During charging, the
caller number in a bill is the changed caller number.
z
By trunk bearer (ADD TGLD)
It implements caller number change and called number change of outgoing trunk
groups. The caller number change is done after number analysis. It changes the
address nature and contents of the caller number. During charging, the caller number
in a bill is the old one before number change.
II. Called number change

The SoftX3000 provides multiple solutions on called number change.
z
By number change of call source (ADD CALLSRC)
The call source defines the attributes of a caller and can achieve called number
change through number preparation. It is applicable to the situation that one office has
different prefixes when serving different networks. Its priority is higher than the other
number change methods. It is done before number analysis. During charging, the
called number in a bill is the changed called number.
z
By caller number analysis (ADD CNACLR)
called number change according to different combinations of call prefix and call
source. During charging, the called number in a bill is the changed called number.
z
By processing call prefix (ADD PFXPRO)
called number change according to different combinations of call prefix and call
source. During charging, the called number in a bill is the changed called number.
z
By trunk group bearing (ADD TGLD)
It implements caller number change and called number change of outgoing trunk
groups. The called number change is done after number analysis, and does not affect
charging, emergency calling, or control mode. During charging, the called number in a
bill is the original called number before change.
III. Special called number change

It is used to meet the requirement of such functions as remote network access and
Wide Area Centrex (WAC) on changing large quantity of irregular called numbers.
The SoftX3000 supports the change of 1,000,000 called numbers currently. The call
processing software re-analyzes the new called number after changing the called
prefix. During charging, the called number in a bill is the original called number before
change.
11-6

11.1.4 Sequence of Number Analysis

Learn the sequence of number analysis methods before you start to use them
together.
1)
Implementing number analysis table (ADD CNACLD)
2)
Implementing caller analysis table (ADD CNACLR)
3)
Implementing prefix processing table (ADD PFXPRO)
4)
Implementing trunk group bearing table (ADD TGLD)
In addition, the SoftX3000 uses the failure processing table (ADD CFPRO)
independently only during call releases.
11.2 Configuring Number Analysis Data

11.2.1 Overview
The number analysis data defines information related to number analysis and call
processing. The configuration of number analysis data cannot be started until that of
office data, charging data, protocol data, signaling data and routing data is done.
Refer to Figure 11-2 for details.

11-7

Start
Equipment data
Trunk data
Office data
Number analysis
Charging data
Subscriber data
MG data
Centrex data
MRS data
Call barring data
Protocol data
IN service data
Signaling data
Other service data
Routing data
Other application
data
End

During the process of SoftX3000 data configuration, some parameters defined in the
configuration of number analysis data will be referenced in the configuration of office
data, trunk data, call barring data, IN service data and IPN service data. The
referencing relationship is presented as the broken lines in Figure 11-2. Refer to
Table 11-4 Parameter referencing relationship between number analysis data and
other data
Input parameter
Name
Output parameter
Defined in
Name
Referenced in
Local DN set
Office data
Number
change index
Office data, trunk data, and

call barring data
Global DN set
Office data
Call prefix
IN service data
service data
Charging
selection code
Charging data
Route selection
source code
Routing data

11-8
and
IPN

II. Preparations
Before configuring number analysis data, make sure that all preparations are done as
SN
Item
Remark
Call prefix table of local

office subscribers
Toll call prefix table
Including normal toll prefix and toll prefix for

multi-area code
Special service call prefix

table
Police emergency call, fire emergency calls,

ambulance calls, and traffic accident calls
IN service call prefix table
Web 800 after-sale service calls; account card

call prefix
VAS call prefix table
IPN service call prefix

Table 11-6 lists the general steps for configuring number analysis data.
Step
Description
Command
Modify DigitMap (optional)
MOD LDNSET
Add called number analysis
ADD CNACLD
For the other commands about number analysis, refer to Section 11.3 for details.

Figure 11-3 illustrates the referencing relationship between key parameters that are
used to configure number analysis data.

11-9

ADD LDNSET
SET RLSMOD
[Local DnSet]
[Local DnSet]
[DnSet]
[Call prefix]
[Service attribute]
ADD CNACLR
[Call source code]
ADD CALLSRC
[Local DnSet]
[Call source]
[Call prefix]
[Call source name]
[Calling party number changing index]
[Local DnSet]
[Called party number changing index]
ADD PFXPRO
ADD CNACLD
[Call source code]
[Local DnSet]
[Local DnSet]
[Call prefix]
[Call prefix]
[Service category]
[Caller party number change index]

[Callee party number change index]
[Fail cause code]
ADD DGTMAP
[Protocol type]
ADD CFPRO
[Local DnSet]
[Call source code]

[Local DnSet]
[Call prefix]
ADD DNC
[Number change index]

[Fail cause code]

[Number change type]
[Change location]
ADD AUSSIG
[Call source]
[Local DnSet]
[Call prefix]

11-10

11.2.2 Modifying Local DN Set (Optional)

I. Related commands
Command
Function
MOD LDNSET
To modify local DN set (including digit map)
LST LDNSET
To list local DN set (including digit map)

data configuration.
When you add a local DN set by using ADD LDNSET, the SoftX3000 automatically
configures H.248-based digit map and MGCP-based digit map by default. The
settings can meet most cases and require no modification. Use MOD LNDSET to
modify digit map in any of the following conditions
z
The number length of the local office number is less than seven.
The minimum number length of toll calls is less than ten, including prefix 0.

[Local DN set]
It defines the local DN set to which the digit map belongs. The value 65534 means
that the digit map can be used by any local DN set, yet the priority is lowest. The local
DN set other than 65534 must first be defined in the ADD LDNSET command before
[H248 digit map]
It defines the H.248-based digit map corresponding to the defined local DN set. The
SoftX3000 supports a maximum of 1024 characters to form a digit map. For the
meaning of digit map, refer to 11.1.2 Digit Map.
[MGCP digit map]
It defines the MGCP-based digit map corresponding to the defined local DN set. The
SoftX3000 supports a maximum of 1024 characters to form a digit map. For the
meaning of digit map, refer to 11.1.2 Digit Map.

11-11

11.2.3 Adding Called Number Analysis

I. Related commands
Command
Function
ADD CNACLD
To add called number analysis data
RMV CNACLD
To remove called number analysis data
MOD CNACLD
To modify called number analysis data
LST CNACLD
To list called number analysis data

Before starting configuration, obtain the following defined parameters by executing
the command in bold face.
z
Local DN set: LST LDNSET
Route selection source code: LST RTANA
Charging selection code: LST CHGIDX

[Local DN set]
It defines the local DN set to which a call prefix belongs. It must be defined in the ADD
LDNSET command before being referenced here.
Its value ranges from 0 to 65534. 65534 is the wildcard, indicating that the call prefix
can be used by any local DN set with lowest priority. That is, if a call prefix can match
the local DN set of two pieces of call prefix data simultaneously, the SoftX3000
matches the call prefix data with the specified local DN set.
[Call prefix]
The call prefix indicates the connected number, the numbering plan, charging
specifications and routing plan of the office. The value ranges from 0 to 9, including *
and #. During the number analysis process, the SoftX3000 matches a called number
with a call prefix based on the maximum matching principle to determine the call
attributes.
[Service category]
It indicates the first step to be implemented by the call processing software during call
prefix analysis. The options are
z
Basic service: It refers to intra-office calls and inter-office calls.

11-12

Supplementary service: It refers to supplementary services, such as abbreviated
dialing, hotline, wakeup, call forwarding, and so on.

Test: It refers to the test calls. For instance, if you dial a certain test number
previously defined, the SoftX3000 will automatically announce the number of the
line.
Intelligent service: It triggers IN services, such as collect call, account card call,
number portability and IPN service.

Special access code: It triggers the special IN service, such as Wide Area
Centrex (WAC).
z
Internet access code: It is used for dial-up internet access.
Value-added service: It refers to value-added service. It is the access code for

triggering the voice mail service.
[Service attribute]
It indicates the next step to be implemented by the call processing software during call
prefix analysis, each of which corresponds to a specific service type. Table 11-7 lists
the valid parameters of service attributes for each corresponding service category.
Table 11-7 Relationship between service categories and service attributes
SN
Service
category
Valid service attributes
Basic service
Intra-office, Local, Local toll, National toll, International

toll, Intra-office national toll, Intra-office international toll
Supplementary
service
All service attributes ending with by DTMF or by pulse;

also including Cancel all registered new service, Display
this phone number, Play voice, Trunk line intrusion, Trunk
line monitoring, Trunk line interrupt, Console emergency
call override, call transfer, and Query fee 180.
Test
Special line call, Telephone self-test, start ATME test,

Stop ATME test, Special number prefix test, Maintain
number, and MRS test.
IN service
Intelligent service, Assist SSP request, Intelligent route

control, Special function number, Card service 1: access
code, Card service 2: access code
Special
code
access
Internet
code
access
Increment
service
Local, local toll
Collect Call
service
Collect Call (Brazil)
Intelligent service, Assist SSP request, Intelligent route

control, Special function number, Card service 1: access
code, Card service 2: access code
Intra-office, Local, Local toll, National toll, International
toll, Intra-office national toll, Intra-office international toll

11-13

Note:
z
During initialization, the SoftX3000 has defined all supplementary service prefixes
for local DN set 65534. The priority is lowest. During number analysis process, the
SoftX3000 will first search and try to match in the user-defined prefix table. If no
match is found, the SoftX3000 will then turn to the pre-defined prefix table.
The preset prefix for supplementary service might not be consistent with the local
standards. Modify the prefixes in local DN set accordingly.
When the service attribute of a call prefix is Collect Call (Brazil), and the callee is
in the same office, the SoftX3000 will start a Collect Call service; when the callee is
of another office, the SoftX3000 will indicate the destination office using inter-office
signaling (ISUP or R2) that the call is a collect call. When the destination office
identifies the signaling, it will start a Collect Call service.
[Customize attribute]
It defines a call prefix as a customized service authority to achieve some special call
authority control functions. The SoftX3000 supports a maximum of 16 customized
service authorities.
Suppose you define call prefix 0755 as custom 1, and the service attribute is
national toll. When you use the command ADD VSBR or ADD MSBR to add a
subscriber whose call-in and call-out authorities do not contain custom 1 although
the subscriber can make national toll calls, the subscriber cannot place calls to called
numbers with prefix 0755.
It defines the route selection code adopted when the SoftX3000 originates an
outgoing call, that is, the route selection policy corresponding to the call prefix. The
value range is 0 to 65535. The default value is 65535 which means no need to select
a route for the outgoing call. Set this parameter by the following principles:
z
When service attribute is local, local toll, national toll, or international toll, you
must configure a valid routing selection code. This parameter must first be
defined in the ADD RTANA command before being referenced here.
In the other cases, it is set to 65535 generally.
[Minimum number length]

It defines the minimum digits required for the called number having this call prefix.
When the called number is less than the minimum number length, number analysis
[Maximum number length]

11-14

It defines the maximum digits permitted for the called number having this call prefix.
When the length of the called number exceeds the maximum number length, the
excessive digits are ignored. The number analysis will only be done on the digits
within the maximum number length.
When the digits you dial are between the minimum number length and maximum
number length, and the two are not the same, you can press the pound key # to end
the dialing process.
[Query area code]
If defines whether the call processing software queries the area code table in
processing toll calls.
z
For national toll call, the call processing software checks whether the area code
of the called number exists in the national area code table. If so the call
connection continues; otherwise, the call fails. The national area code is defined
in the ADD ACODE command.
For international toll call, the call processing software checks whether the
nation/region code of the called number exists in the nation/region code table. If
so the call connection continues; otherwise, the call fails. The nation/region code
is defined in the ADD NCODE command.
[Gain]
It defines the power amplification multiples sent by the related subscriber board when
the local office subscriber starts an outgoing call and hears the ringback tone.
Normally, it is set to the default value local gain.
[Ring delay time]
It defines the delay time for sending the ringing tone to the callee (that is, sending the
ringing signaling to MG) after the call processing software analyzes the called number
and starts to connect the callee. Its unit is second. Set the parameter by the following
principles:
z
For normal calls, it is usually set to 0, meaning instant ringing on connection

completion.
For special services as fire emergency calls and police emergency calls, it is
usually set to 3 to avoid mistakenly-placed calls.
For outgoing call prefix, the parameter is invalid.

It specifies the charging selection code used for charging of different DPCs. It is the
basis of DPC charging, ranging from 0 to 65534. This parameter must first be defined
in the ADD CHGIDX command before being referenced here.

11-15

If the system has adopted intra-office group charging mode for calls represented by
the call prefix, you must specify a valid value for the parameter. In this way, there are
two charging mode (intra-office group charging mode and destination code charging
mode) that match the call prefix in the host database. On the basis of the priority of the
charging modes, the system charges the call prefix according to the charging situation
defined in the intra-office group charging table.
[Destination]
It is used in traffic measurement only. The same destination value is defined for all
prefixes sharing the same statistical requirement.
[Service sequence number]
It is a universal numbering of a group of services, including
z
0: Queuing
1: INtess service
2 and 3: Automatic paging
4: Voice mailbox service
Such services are normally provided by the IN service platform rather than by the
SoftX3000.
[Time delay trigger point]
The parameter ranges from 0 to 15, and serves two purposes:
z
Setting the start waiting location of number analysis process in value-added

services
If there is a new number inputted, the SoftX3000 will continue with number analysis. If
waiting is timeout, the SoftX3000 will regard it as a complete number and attempt to
connect the called party.
z
Setting the start waiting location of number analysis process in CNF
If there is a new number inputted, the SoftX3000 will continue with number analysis. If
waiting timeout, the SoftX3000 will regard it as a complete number and release the
call with failure reason of augmentation delay insertion.
For instance, assume that for a certain call prefix, the minimum number length is 7,
the maximum number length is 8, and the time delay trigger point is at the seventh
digit. When the caller is dialing the first six digits, the SoftX3000 will activate the
dialing interval delay timer to monitor the dialing interval based on the duration of 20
seconds. When the caller dials the seventh digit, the SoftX3000 will automatically
activate the trigger delay timer to monitor the maximum delay duration (which you
defines in the parameter time delay trigger point) before the caller dials the next digit.
You must not define a value smaller than the minimum number length; otherwise, the
SoftX3000 cannot activate the trigger delay timer
11-16

[Triggering delay]
It defines the delay time in second in value-added services and number augmentation.
It ranges from 0 to 15.
[Release mode]
It defines the call release mode on call completion. The options are
z
First party release: When either party hangs up, the call is released. It is suitable
for calls between common subscribers.
Calling party release: The call is released only when caller hangs up. If the called
party instead of the calling party hangs up, the call is held within a period of time
specified by the timer. If the called party picks up again within the period, the call
is resumed; otherwise, the call is released. This release control mode is mainly
used in toll call.
Called party release: The call is released only when called party hangs up. If the
calling party instead of the called party hangs up, the call is held within a period
specified by the timer. If the calling party picks up again within the period, the call
is resumed; otherwise, the call is released. This mode applies to special services
as police emergency calls, fire emergency calls, ambulance calls and traffic
accident calls.
Last party release: The call is released only when both the calling party and the
called party hang up. This mode is rarely used.
By default, the release control modes listed here do not distinguish service attributes
or signaling types. They are for all service attributes and signaling types. To customize
the release control mode for a specific service attribute or a certain signaling type, use
SET RLSMOD. The priority of the customized mode is higher than that of the default
mode.
[Emergency call observation flag]
It specifies whether the SoftX3000 observes an emergency call prefix and is only
used for this purpose. By default, it is set to No. If it is set to Yes, the SoftX3000
generates an event alarm at the alarm console when a subscriber dials this
emergency call prefix.
If it is necessary to set the authority for overriding the emergency call prefix, you must
execute the command ADD AUSSIG; otherwise, when maintenance personnel
suspends an owing-charge subscriber or restricts the calling authority of a common
subscriber, the subscriber cannot dial the emergency call prefix.
[Description]
It identifies a call prefix with a string of characters.
[RM source]

11-17

This parameter specifies the resource management source code to be used by the
call prefix. When a call is made to the call prefix, the SoftX3000 instructs the
corresponding resource management device to reserve bandwidth for the bearer
channel to be used in the call. This parameter is defined in the ADD RMANA
[HongKong NP query start length]
It defines the length of a called number obtained from the first digit by the SoftX3000
when the SoftX3000 sends a number query command to the NP server during
analysis of the call prefix by the call processing software. Its value ranges from 0 to 12.
z
If it is set to a value other than 0, during analysis of the call prefix, the call
processing software obtains the called number based on the length defined in
this parameter, and then sends the obtained called number to the NP server for
query. If the query succeeds, the SoftX3000 re-analyzes the new called number
returned by the NP server. If the query fails, the SoftX3000 continues the
analysis of the original call prefix. Therefore, if the callee corresponding to the
call prefix registers the HongKong NP service, you must set this parameter to the
actual length of the NP number (that is, the logical number).
If it is set to 0, the call processing software never sends a number query

command to the NP server during analysis of the call prefix. Therefore, if the
local callee corresponding to the call prefix does not register the Hongkong NP
service, you must set this parameter to 0 to enhance the efficiency of the call
processing software for number analysis.
The SoftX3000 starts the callee NP service analysis flow for the call prefix dialed by a
call source only when this parameter is set to a non-zero value and you set the
HongKong NP flag of the call source to True with the command ADD CALLSRC.
[Antipole]
Reserved.
[Send calling name]
It specifies whether the call processing software sends the caller name to the callee
when connecting the call. By default, it is set to No. If the callee at the local office or
at the terminating office registers the caller name display service, you must set this
parameter of the corresponding call prefix to Yes; otherwise, the caller name will not
be displayed even if the callee has the authority for the caller name display service.
[Special called number change]
It specifies whether the call processing software implements special called number
change to a specific call prefix, that is, whether the call processing software queries

11-18

the special called number change data table (defined in the ADD SPDNC command).
The default value is No.
If it is set to Yes, the call processing software queries the special called number
change data table every time when analyzing the call prefix. If the query succeeds,
that is, a record matching the call prefix is found in the data table, the call processing
software re-analyzes the changed called number. If the query fails, the call processing
software continues the analysis of the original call prefix.
[Priority select number]
It defines in the SoftX3000 the priority selection number used by a call prefix. Its value
ranges from 0 to 255. The default value is 0. It must be defined in the command SET
PFXPRI. There are four options: no priority, protected priority, ordinary priority, and
priority of insert.
The call prefixes with the same priority can use either the same priority selection
number or different ones. However, the call prefixes with different priorities must use
different priority selection numbers.
[Codec list]
It specifies the codec capabilities supported by a call prefix. By default, all codec
capabilities are supported. Set this parameter by the following principles:
z
Unless otherwise noted, set the parameter to All.
For the connection of calls to the called numbers with a specified call prefix, the
codec capabilities supported by the call prefix must have intersection with those
supported by the caller and the callee; otherwise, the call will fail.
The priority sequence of the codec capabilities is decided by the configuration

sequence of codec list of the call prefix in the called number analysis table. That
is, when you use the command LST CNACLD to query a call prefix, the
sequence of the codec modes in the query result is the priority sequence.
Codec prefer data can be configured in commands such as ADD VSBR (in the
subscriber data table), ADD N7TG (in the trunk data table), ADD CNACLD (in the
called number analysis table), and ADD CLRDSN (in the caller number discrimination
table). Therefore, it is possible that two or more codec modes are related to a call. In
this case, the SoftX3000 selects one according to the following principles:
z
The codec mode configured in the caller number discrimination table has the
highest priority, and that configured in the called number analysis table has the
second highest priority.
If the codec modes related to a call are not configured in either the caller number
discrimination table or the called number analysis table, the SoftX3000 selects
the codec mode according to the caller first and subscriber first principle. For
example, during an intra-office call, if the caller and the callee have different
preferred codec modes, only the codec mode of the caller is valid. During an
11-19

outgoing call, if the caller and the outgoing trunk group have different preferred
codec modes, only the codec mode of the caller is valid. During a transit call, if
the incoming trunk group and the outgoing trunk group of the local office have
different preferred codec modes, only the codec mode of the incoming trunk
group is valid. During an incoming terminated call, if the incoming trunk group
and the callee of the local office have different preferred codec modes, only the
codec mode of the callee is valid.
[VIG capability]
It indicates whether it is necessary to trigger the VIG related analysis procedure when
the call processing software analyzes a call prefix. By default, it is set to False.
When the call prefix is the one of a multimedia outgoing call from the local office to the
3G network through the VIG, you must set this parameter to Yes.
[Outgoing traffic dispersion ID]
It defines the outgoing traffic dispersion. Its value ranges from 0 to 65535. The default
value is 65535 indicating invalid. The parameter must be defined in the command
ADD CLRCODEC before being referenced here.
[SHLR prefix flag]
It specifies whether the called number returned by the SHLR is with an MON prefix in
the MON service flow when the SoftX3000 sends a query command to the SHLR
through MAP messages. The default value is No. You must set the parameter to
Yes when the call prefix is used for the MON service.
[Early ACM delay value]
Suppose that the local office acts as a tandem office, and the incoming trunk is an
ISUP trunk n a call. The local office has found that the address signal in the incoming
call is complete, but has not received the signal indicating complete address signal
from the terminating office. The parameter specifies whether the local office replies
ACM signaling to the originating office ahead of schedule and how long the local office
delays to reply the ACM signaling.
The parameter value ranges from 0 to 255 with the unit as second. The default value
is 255, indicating that the local office does not reply ACM signaling to the originating
office ahead of schedule. The local office sends CPG signaling to the originating office
after receiving the signal indicating complete address signal from the terminating
office.
[SHLR select code]
When a local subscriber dials a call prefix through the incoming trunk, the parameter
specifies the SHLR select code used when the system triggers the service flow
related to SHLR. It ranges from 0 to 65535. By default, it is set as 65535, indicating
11-20

the call prefix does not trigger the service flow related to SHLR. Here are the
configuration guidelines:
z
Before the call prefix triggers the service flow related to SHLR, you need to set a
valid SHLR selection code. In addition, the parameter should be defined first with
the command ADD SHLRCFG before being referenced here
In other cases, the SHLR selection code is usually set as 65535.
11.3 Other Commands

11.3.1 Setting Prefix Priority (Optional)
I. Related commands
Command
Function
SET PFXPRI
To set prefix priority
RMV PFXPRI
To remove prefix priority
MOD PFXPRI
To modify prefix priority
LST PFXPRI
To list prefix priority

By default, if call congestion occurs, the SoftX3000 only allows the new calls
originated by priority subscribers to seize the reserved outgoing trunk circuits, but
rejects all new calls originated by common subscribers.
The command SET PFXPRI enables the setting of call priority in the SoftX3000. You
can define some call prefixes such as those of special services (for example, fire
emergency calls and ambulance calls) as priority call prefixes. In this case, if call
congestion occurs, the emergency calls originated by common subscribers can also
be connected.

[Local DN set]
It defines the local DN set of a call prefix for which the call priority is set. It must be
defined in the ADD LDNSET command before being referenced here.
[Call prefix]
It defines the call prefix for which the call priority is set. It must be defined in the ADD
CNACLD command before being referenced here.
11-21

[Caller category]
It defines the category of the callers who have the call priority corresponding to a call
prefix. That is, when a caller dials this prefix, the new call priority is enabled only if the
category of the caller matches the setting here. If there is no special requirement, set
this parameter to All categories.
When the call processing software analyzes the number, if the caller category of
several pieces of service prefix priority data matches the call, the option All
categories enjoys the lowest priority. That is, the SoftX3000 matches the other
options as prior.
[Priority]
It defines the call priority of a prefix. To enable a call prefix to seize the reserved
circuits of the trunk group during congestion, select Priority of insert. The options are
z
No priority: With this priority, the calls with the specified prefix have no queue
authority during connection and can be released forcedly, but the other
non-priority calls cannot be released forcedly.
Protected priority: With this priority, the calls with the specified prefix have no
queue authority during connection, and neither they nor the other non-priority
calls can be released forcedly.
Ordinary priority: With this priority, the calls with the specified prefix can be
queued during connection, but cannot seize the reserved trunk circuits in the
case of congestion. Neither they nor the other non-priority calls can be released
forcedly.
Priority of insert: With this priority, the calls with the specified prefix can be
queued during connection and can seize the reserved trunk circuits in the case of
congestion. They cannot be released forcedly, but the other non-priority calls can
be released forcedly.
11.3.2 Setting Release Control Mode

I. Related commands
Command
Function
SET RLSMOD
To set release control mode
RMV RLSMOD
To remove release control mode
MOD RLSMOD
To modify release control mode
LST RLSMOD
To list release control mode

11-22


When you add a call prefix by using ADD CNACLD, the SoftX3000 automatically
configures the release control mode by default. However, this release control mode
does not distinguish service attributes or signaling types, and it is for all service
attributes and signaling types. To customize the release control mode for a specific
service attribute or a certain signaling type, use SET RLSMOD. The priority of the
customized mode is higher than that of the default mode.

[Local DN set]
It defines the local DN set of a call prefix for which the release control mode is set.
This parameter must first be defined in the ADD LDNSET command before being
referenced here.
[Call prefix]
It specifies the call prefix for which the release control mode is set. This parameter
must first be defined in the ADD CNACLD command before being referenced here.
[Service attribute]
It determines the release control mode together with signaling mode.
[Signaling mode]
It determines the release control mode together with service attribute.
[Release mode]
It defines the call release control mode on call completion. The options are
z
First party release: When either party hangs up, the call is released. It is suitable
for calls between common subscribers.
Calling party release: The call is released only when caller hangs up. If the called
party hangs up instead of the calling party, the call is held within a period
specified by the timer. If the called party picks up again within the period, the call
is resumed; otherwise, the call is released. This release control mode is mainly
used in toll call.
Called party release: The call is released only when called party hangs up. If the
calling party hangs up instead of the called party, the call is held within a period
specified by the timer. If the calling party picks up again within the period, the call
is resumed; otherwise, the call is released. This mode applies to such special
services as police emergency calls, fire emergency calls, ambulance calls, and
traffic accident calls.

11-23

z
Last party release: The call is released only when both the calling party and the
called party hang up. This mode is rarely used.
11.3.3 Adding Cause Code Conversion (Optional)

I. Related commands
Command
Function
ADD CAUSEC
To add cause code conversion
RMV CAUSEC
To remove cause code conversion
MOD CAUSEC
To modify cause code conversion
LST CAUSEC
To list cause code conversion

The call processing software of the SoftX3000 might release calls due to various
reasons during call processing. Some releases are normal, but most of them are
abnormal. As defined in the call processing software, the SoftX3000 identifies all
release causes with only one cause code whose value ranges from 0 to 255. 0127
indicates the cause code customized for the SoftX3000 and identified internally only.
128255 indicates the cause code transmitted between offices and defined in ITU-T
recommendations.
The cause codes (128255) transmitted through signaling messages between two
offices might not meet the requirements of both offices during interconnection,
because differences might exist in requirement and understanding of call releases in
different countries or by different equipment manufacturers. In this case, you can use
the command ADD CAUSEC at the SoftX3000 side to add the conversion
relationship between release cause codes to make them of both offices matched.
To set the release cause code, one must be familiar with the call processing software
of the SoftX3000. You must set this parameter according to the adaptation script of
the release cause code provided by Huawei. This manual only introduces the use of
the command.

[Old value]
It indicates the release cause code defined in the SoftX3000. Its value ranges from 0
to 255.

11-24

The release cause code set in this command must be the same as that automatically
generated by the call processing software. If you cannot judge the actual release
cause code for a certain type of calls accurately, you can obtain it through the
interface signaling tracing task and the connection tracing task.
[Release position]
It defines the specific position of release. It is for judgement only without special
meanings. Generally, set it to 254 (wildcard), indicating any release position. If it is
necessary to set it to other values, contact Huawei technical engineers for help.
[Release PID]
It defines the release sequence number at a certain position during call release. It is
for judgement only without special meanings. Generally, set it to 254 (wildcard),
indicating any release sequence. If it is necessary to set it to other values, contact
Huawei technical engineers for help.
[Receiver PID]
It defines the release sequence number at a certain position after the conversion of
the release cause code. It is for judgement only without special meanings. Generally,
set it to 254 (wildcard), indicating any release sequence. If it is necessary to set it to
other values, contact Huawei technical engineers for help.
[New value]
It defines the new release cause code after conversion to be adapted with that of the
opposite office. Its value ranges from 0 to 255. As specified in ITU-T
recommendations, the actual value range of this parameter is from 128 to 255.
11.3.4 Adding Preselection Access Code Index (Optional)

I. Related commands
Command
Function
ADD PRECODE
To add preselection access code index
RMV PRECODE
To remove preselection access code index
MOD PRECODE
To modify preselection access code index
LST PRECODE
To list preselection access code index

11-25


The preselection access code is used along with the caller number analysis data to
implement the preselection function of toll calls. That is, when making a toll call, a
local subscriber can use the pre-registered toll network of the carrier to connect the
call instead of dialing the access code of the carrier before the called number. The
implementation procedure is as follows:
1)
Configure the preselection access code data for all toll carriers with the
command ADD PRECODE.
2)
The local subscriber applies for the toll preselection service .
3)
The local subscriber applies for the toll preselection service to the carrier of the
local office.
4)
Enable the toll preselection service for the subscriber with the command ADD
CNACLR.
5)
If the subscriber does not dial the access code of the toll carrier when making a
toll call, the local office automatically inserts the preselection access code before
the called number during number analysis.
6)
The local office transits the call to a gateway office according to the preselection
access code during route analysis. The gateway office continue to process the
call.

[Access code index]
It identifies a preselection access code uniquely in the SoftX3000. Its value ranges
from 0 to 254. It is referenced during the setting of caller analysis data with the
command ADD CNACLR.
[Access code]
It defines a preselection access code. The parameter must be defined by the
command ADD CNACLD before being referenced here. During number analysis, the
SoftX3000 automatically inserts this access code before the specific call prefix dialed
by a caller. [Company name]
It identifies the carrier corresponding to a specific access code with a string of
characters.
[Carrier selection code]
It specifies the carrier selection code corresponding to the access code. Its value
ranges from 0 to 9 and A to E with the maximum length of six characters. The
parameter must be allocated uniformly by the telecom department on nation-wide
basis.

11-26

The parameter is optional. It is used for authentication of preselection calls by

gateway offices. If the parameter is configured, it will be carried in the forward IAM
message on the outgoing trunk direction when the local office initiates an outgoing call
related to preselection. The peer office (it is a gateway office normally) authenticates
the carrier selection code parameter in the IAM message after receiving the IAM
message:
z
Step 1: The gateway office judges whether the carrier selection code in the IAM
message is consistent with that in the local office information table configured by
the command SET OFI. If yes, the authentication is passed. When forwarding
the IAM message to the lower office, the gateway office deletes the carrier
selection code parameter carried in it. If not, proceed with subsequent operation.
Step 2: The gateway office judges whether the carrier selection code table
configured by the command ADD CSC contains the carrier selection code in the
IAM message. If yes, the authentication is passed. When forwarding the IAM
message to the lower office, the gateway office transparently transmits the
carrier selection code parameter carried in it. If not, the gateway office rejects the
call.
11.3.5 Adding Number Change (Optional)

I. Related commands
Command
Function
ADD DNC
To add number change data
RMV DNC
To remove number change data
MOD DNC
To modify number change data
LST DNC
To list number change data

The dial number change defines the rule of change, insertion and deletion of caller or
called number. It is uniquely identified by the number change index, which is
referenced in the data configuration procedures of adding caller number analysis,
adding prefix special processing and adding call failure processing.

It uniquely identifies a number change in the SoftX3000. Its value ranges from 1 to
65535. The default value 0, which you cannot set with, represents no number change.

11-27

[Number change type]

It defines the number change method. Select one from the following options:
z
No change: Modifying the address nature without changing the number. Select
this option if you want to change the address nature of a caller number into
national number, international number or subscriber number.
Number changed: Replacing the digits specified with new digits. The process is
removing the original digits and inserting new ones.
Delete number: Deleting the specified digits.
Insert number: Inserting new digits before the specified location of a number.
[Change location]
It changes the start location of number change, including number changed, delete
number and insert number. The location number of the first number is 0.
During number change or deletion, if change location + change length is bigger than
the length of the original number, the number change operation is invalid. During
number insertion, if change location is bigger than the original number length, the
number change operation is also invalid.
[Change length]
It specifies the length of the digits to be replaced or deleted.
It specifies the address nature of the new number. It is available only when number
change type is set to no change. Select one from the following four options:
z
Address nature not changed: Not changing the address nature of the original
number.
International number: Changing the address nature of the original number to

international number in format of nation code + national toll code + subscriber
number.
National number: Changing the address nature of the original number to national
number in format of national toll code + subscriber number.
Subscriber number: Changing the address nature of the original number to

subscriber number.
When the SoftX3000 changes the address nature of a number, if the address nature
of the original number is the same as that of the new number, the number change
operation is invalid.
[New number]
It is valid only to number changed or insert number. The change location and change
length codetermine the range of digits to be changed. When you wish to change

11-28

number, replace the digits in the range with new digits. When you wish to insert
number, insert the new digits at the change location of the original number.
11.3.6 Adding Special Called Number Change (Optional)

I. Related commands
Command
Function
ADD SPDNC
To add special called number change data
RMV SPDNC
To remove special called number change data
MOD SPDNC
To modify special called number change data
LST SPDNC
To list special called number change data

The special called number change aims to meet the requirement of remote network
access and WAC on changing large quantity of irregular called numbers. The
SoftX3000 can change a maximum of 1,000,000 called numbers at present. After
carrying out the special called number change to a called prefix, the call processing
software reanalyzes the new called number. During charging, the called number in a
bill is the original called number.

[Local DN set]
It defines the local DN set of a call prefix for which the special called number change is
needed. This parameter must first be defined in the ADD LDNSET command before
[Call prefix]
It defines the call prefix for which the special called number change is needed. This
parameter must first be defined in the ADD CNACLD command before being
referenced here.
[Called number change type]
It indicates the change type of called numbers. Select one from the following options:
z
No change: Modifying the address nature without changing the number. Select
this option if you want to change the address nature of a caller number into
national number, international number or subscriber number.

11-29

z
Number changed: Replacing the digits specified with new digits. The process is
removing the original digits and then inserting new ones.
Delete number: Deleting the specified digits.
Insert number: Inserting new digits before the specified location of a number.
[Change location]
It changes the start location of number change, including number changed, delete
number and insert number. The location number of the first number is 0.
During number change or deletion, if change location + change length is bigger than
the length of the original number, the number change operation is invalid. During
number insertion, if change location is bigger than the original number length, the
number change operation is also invalid.
[Change length]
It specifies the length of the digits to be replaced or deleted.
[New number]
It is valid only to number changed or insert number. The change location and change
length codetermine the range of digits to be changed. When you wish to change
number, replace the digits in the range with new digits. When you wish to insert
number, insert the new digits at the change location of the original number.
It specifies the address nature of the new number. It is available only when number
change type is set to no change. Select one from the following four options:
z
Address nature not changed: Not changing the address nature of the original
number.
International number: Changing the address nature of the original number to

international number in format of nation code + national toll code + subscriber
number.
National number: Changing the address nature of the original number to national
number in format of national toll code + subscriber number.
Subscriber number: Changing the address nature of the original number to

subscriber number.
When the SoftX3000 changes the address nature of a number, if the address nature
of the original number is the same as that of the new number, the number change
operation is invalid.

11-30

11.3.7 Adding Caller Number Analysis (Optional)

I. Related commands
Command
Function
ADD CNACLR
To add caller number analysis data
RMV CNACLR
To remove caller number analysis data
MOD CNACLR
To modify caller number analysis data
LST CNACLR
To list caller number analysis data
ADB CNACLR
To add a batch of caller number analysis data
RVB CNACLR
To remove a batch of caller number analysis data

A call source code defines the call source attributes of a caller. Several call sources
(local office subscribers or incoming trunks) can share one call source code. That is,
they can have the same call source attributes, such as route selection source code,
failure source code, and charging source code.
To modify the attributes of a call source code is to modify those of all callers. This
method cannot meet some special application requirements. To set different call
source attributes (for example, route selection mode, failure processing mode, and
charging mode) for a specific prefix dialed by a specific type of callers, you can use
the command ADD CNACLR to redefine it.
Suppose the calls from incoming trunk group 0 (call source code 0) can be originated
by subscribers of office 66 or 88. To set different charging modes for the calls from
office 66 and those from office 88, use the command ADD CNACLR.

[Call source code]
It specifies the call source that requires additional caller number analysis. That is, the
call processing software triggers the caller number analysis procedure for the call
prefixes dialed by this call source. This parameter must first be defined in the ADD
CALLSRC command before being referenced here.
[Caller number]
It specifies the caller number for which the caller number analysis is to be
implemented. It can be a complete subscriber number or a prefix.

11-31

[Call prefix]
It specifies the call prefix that requires caller number analysis. That is, when a specific
caller dials this call prefix, the SoftX3000 triggers the caller number analysis
procedure. To type a specific call prefix, this parameter must first be defined in the
ADD CNACLD command before being referenced here. The wildcard *65534#
represents all call prefixes (but with the lowest priority). That is, if a call prefix can
match that of two pieces of caller number analysis data, the SoftX3000 uses the caller
number analysis data with the specified call prefix as prior.
[Time index]
It defines the time index used by the caller number analysis data table. It is used to
implement different caller number analysis procedures in different dates or time
segments.
The SoftX3000 has pre-defined time index 0 (not implementing caller number
analysis dynamically) during initialization and it can be referenced directly here. The
other time index values must be defined in the command ADD TMIDX before being
referenced here.
[Function code]
It specifies the caller number analysis procedure to be implemented by the call
processing software when a caller specified in this command dials the call prefix
defined in this command. The options are
z
Reject call: The SoftX3000 disallows the caller to dial the call prefix.
Preselection: The SoftX3000 inserts the preselection access code before the call
prefix.
Modify caller attribute: The SoftX3000 modifies the call source attributes of the
caller, including route selection source code, failure source code, charging
source code, and caller category.
Preselection and modify caller attribute: The SoftX3000 can either insert the
preselection access code before the call prefix or modify the call source
attributes of the caller.

It re-defines the route selection source code after caller number analysis, which is
different from the one defined in ADD CALLSRC. The default value is 65535,
meaning no re-definition of the route selection source code.
It re-defines the failure source code after caller number analysis, which is different
from the one defined in ADD CALLSRC. The default value is 255, meaning no
re-definition of the failure source code.

11-32

[Caller category]
It re-defines the caller category after caller number analysis, which is different from
the one defined in ADD VSBR or ADD MSBR or the one sent by the originating office
through incoming signaling messages. The default value is No change.
It re-defines the charging source code after caller number analysis, which is different
from the one defined in ADD VSBR, ADD MSBR, ADD SIPTG, or ADD N7TG. The
default value is 255, meaning no re-definition of the charging source code.
[Call barring group]
It re-defines the call barring group after caller number change, which is different from
the one defined in ADD VSBR, ADD MSBR, ADD SIPTG, or ADD N7TG. The default
value is 65535, meaning no re-definition of the call barring group.
[Calling party number changing index]
It specifies the index for caller number change. This parameter must first be defined in
the ADD DNC command before being referenced here. The default value is 0,
meaning no re-definition of the caller number change index.
[Called party number changing index]
It specifies the index for called number change. This parameter must first be defined
in the ADD DNC command before being referenced here. The default value is 0,
meaning no re-definition of the called number change index.
When you carry out the called number change to the call prefix, the SoftX3000 still
implements the corresponding number analysis procedure according to the attributes
of the original call prefix in the number analysis table if you do not set Reanalysis
flag in this command to Yes. Therefore, when defining the attributes of the call
prefix, you need to consider such aspects as the minimum number length, maximum
number length, service category, and service attribute of the new called number.
[Preselection access code index]
It specifies the index of the preselection access code to be inserted before a call prefix.
It must first be defined in ADD PRECODE before being referenced here. The default
value is 255, meaning that it is unnecessary to insert the preselection access code
before a call prefix.
When the SoftX3000 inserts the preselection access code before a call prefix, it is
required to reanalyze the new called number after the insertion.
[Reanalysis flag]

11-33

It defines whether the call processing software reanalyzes the called number that is
changed or inserted with the preselection access code. Set this parameter by the
z
If the processing of the new called number is different from that of the original call
prefix, you must set this parameter to Yes if only any of the call attributes is
consistent. At this time, the SoftX3000 reanalyzes the new called number
according to the call attributes of the new call prefix in the number analysis table.
If the processing of the new called number is the same as that of the original call
prefix, you must set this parameter to No. At this time, the SoftX3000
reanalyzes the new called number according to the call attributes of the original
call prefix in the number analysis table.
If the three functions related to the processing of a called number are all required, the
SoftX3000 first changes the called number, then inserts the preselection access code
before the call prefix, and finally reanalyzes the new called number.
11.3.8 Adding Call Prefix Processing (Optional)

I. Related commands
Command
Function
ADD PFXPRO
To add call prefix processing data
RMV PFXPRO
To remove call prefix processing data
MOD PFXPRO
To modify call prefix processing data
LST PFXPRO
To list call prefix processing data

Generally, you do not have to implement special processing on caller number and the
called number before number analysis and call connection. In the following cases,
you must use ADD PFXPRO to process the caller or called number before number
analysis and call connection phase.
z
The call prefix is an access code.
The call prefix is used only for announcement tones of the local office, such as
time announcement and number change announcement.
In the hybrid application of public network and private network, the global DN set
of the called number must be changed.
The actual number of the caller is to be masked for some prefixes.
The call is automatically sent to failure processing for some prefixes.

11-34

When you have defined multiple prefix processing modes, the SoftX3000 will select
only one of them. The priority is
1)
Called number change/caller number change (set to Yes),
2)
Send tone method (set to SEND TONE or INTER-DIGIT SEND TONE)
3)
Fail process flag (set to Yes)
4)
Reanalysis (set to Yes).
You can use the first, the third and the fourth method together.

[Call source code]
It specifies the call source that requires additional prefix processing. That is, the call
processing software triggers the prefix processing procedure for the specific call
prefix dialed by the call source. This parameter must first be defined in the ADD
CALLSRC command before being referenced here.
[Local DN set]
It specifies the local DN set of the call prefix that requires prefix processing. This
parameter must first be defined in the ADD LDNSET command before being
referenced here.
[Call prefix]
It specifies the call prefix for caller number analysis. This parameter must first be
[Called number change flag]
It indicates whether the call processing software needs to change a called number.
When you set it to Yes, you must specify the Called number change index field in
this command.
[Method of sending tone]
It indicates whether a call prefix is used for sending tone or sending tone between
digits. The options are
z
Send tone: The SoftX3000 sends the specified signal tone to the caller when a
caller dials this call prefix. The tone type is defined in the parameter Tone type
in this command.
Inter-digits send tone: When a caller dials this call prefix, the SoftX3000 sends
intermittent signal tone of 450 Hz prompting the caller to continue dialing. When
the caller continues to dial the subsequent digits, the SoftX3000 stops sending
the signal tone and starts number analysis. The time when the SoftX3000 starts
to send tone is defined in the Tone position in this command.

11-35

z
Not send tone: The SoftX3000 does not send the signal tone.
You can use the inter-digits send tone and called number change coordinately. The
SoftX3000 will implement the latter first, then the former, before implementing the
other number analysis steps according to the attributes defined by the original call
prefix.
[Failure processing flag]
It defines whether the call processing software starts the failure processing procedure
for a call prefix forcedly. The default value is No". When you set it to Yes, all call
attempts to this call prefix fail. If you also specify the failure cause code in the
command, the call processing software will query the failure processing method in the
failure processing data table based on this code. The failure processing method is
defined in ADD CFPRO.
[Caller number change flag]
It indicates whether the call processing software changes a caller number. When you
set it to Yes, you must specify the value in the Caller number change index field.
[New DN set]
It specifies the global DN set in whose number analysis table the call processing
software reanalyzes a call prefix. It is available only when Reanalysis is set to Yes.
This parameter must first be defined in the ADD NCODE command before being
referenced here.
[Called number change index]
It indicates the number change index of the called number, and is available only when
called number change flag is set to Yes. This parameter must first be defined in the
ADD DNC command before being referenced here.
It indicates the number change index of the caller number, and is available only when
Caller number change flag is set to Yes. This parameter must first be defined in the
[Reanalysis]
It indicates whether the call processing software reanalyzes a called number after
change. Set this parameter by the following principles:
z
To change the global DN set of the call prefix, you must set this parameter to
Yes. The call processing software will reanalyze the call prefix in the number
analysis table of the new global DN set.
You must set the parameter to "Yes when you need to perform called number
change and any of such call attributes as minimum number length, maximum
11-36

number length, service type, service attribute, route selection code, charging
selection code, or emergency call observation flag is changed. The SoftX3000
will reanalyze the new called number according to the call attributes of the new
call prefix in the number analysis table.
z
When you need to change the called number, and all the above-listed call
attributes are the same before and after the number change, you must set the
parameter to No. The SoftX3000 will continue to analyze the new called
number according to the call attributes of the original call prefix in the number
analysis table.
Note:
The reanalysis can be used together with called number change. The SoftX3000 first
changes the called number and then reanalyzes the new called number.
[Tone type]
It indicates the tone played by the SoftX3000 when a caller dials a specific call prefix.
It is available only when Method of sending tone is set to Send tone. Select an
appropriate tone type accordingly.
[Failure cause code]
It indicates the cause for call failure or connection failure, and is available only when
Failure processing flag is set to Yes. After you set the failure cause code, you must
also set the corresponding failure processing method in the failure processing table
by executing ADD CFPRO.
[Tone position]
It indicates from which digit of the called number the SoftX3000 starts to send the
signal tone to a caller. It is available only when Method of sending tone is set to
Inter-digits send tone. Its value ranges from 0 to 15. The default value is 0, meaning
not sending tone.
11.3.9 Adding Call Failure Processing (Optional)

I. Related commands
Command
Function
ADD CFPRO
To add call failure processing data
RMV CFPRO
To remove call failure processing data

11-37

Command
Function
MOD CFPRO
To modify call failure processing data
LST CFPRO
To list call failure processing data

During a call attempt, the caller might encounter call failure or connection failure due
to all kinds of reasons. If the SoftX3000 always plays the busy tone, the caller can
never know why the call fails. In this case, especially when the dialed number is a
wrong number or an unallocated number, the caller might try several times after the
first failure, which reduces the call completion ratio.
If the SoftX3000 sends an announcement indicating call failure and gives further
instructions, the problem is solved. There will be less invalid call attempts, and the call
completion ratio will be increased. You can execute ADD CFPRO to add the failure
processing method and solve the issue as described above.
When you define the failure processing method of a certain prefix by executing ADD
CFPRO, the precise-matching mode is used. The SoftX3000 will generate a failure
cause code (which can be traced) only when the call fails after the caller dials the
prefix. The SoftX3000 will implement failure processing defined in the failure
processing table only when the generated failure source code exactly matches the
one defined in the table.
When you define the failure processing method of the prefix by executing ADD
PFXPRO, the universal mode is used. Whenever a subscriber dials the prefix, the call
fails. The SoftX3000 either sends the busy tone or specifies a failure cause code and
searches for a failure processing method in the failure processing table as specified in
the precise-matching mode.

[Local DN set]
It specifies the local DN set of the call prefix that requires failure processing. This
referenced here.
[Call prefix]
It specifies the call prefix that requires failure processing. If you enter no value in this
field, the record is a wildcard that is applicable to all call prefixes. For setting of a call
prefix, this parameter must first be defined in the ADD CNACLD command before
11-38


As one of the conditions for determining if failure processing is needed, it defines the
specific cause for the call failure or connection failure. The SoftX3000 decides the
failure processing method based on the failure cause code automatically generated
by the call processing software or that pre-defined in the prefix processing table
(defined in ADD PFXPRO).
It specifies the failure source code that requires failure processing for the
corresponding callers. As one of the attributes of call source code, this parameter
must first be defined in the ADD CALLSRC command before being referenced here.
[Caller category]
It specifies the type of callers who require failure processing.
[Service attribute]
It specifies the call prefixes that require failure processing.
[Processing type]
It defines the failure processing method. Here are meanings of the options:
z
Send signal tone: The SoftX3000 informs a caller of the failure cause with
announcement. When the duration of sending signal tone exceeds that of the
timer, the SoftX3000 releases the call and the caller hears the busy tone.
Re-select route: If it is an outgoing call, the SoftX3000 re-selects the route until
rerouting succeeds or the system is timeout.
Reanalysis after number change: The SoftX3000 first changes the called
number and then reanalyzes the new number. It is frequently used in digit
expansion and number change.
CFP trigger DP4: The SoftX3000 triggers IN services at the Trigger Detection
Point (TDP) with DP=4. That is, the SoftX3000 reports route selection failure to
the SCP through an INAP message, and then it processes the call under the
control of the SCP. The service procedure at the SCP side determines how the
SCP processes the call.
[Signal tone type]

It indicates the signal tone played by the SoftX3000 to a caller. It is available only
when Processing type is set to Send signal tone. Select an appropriate tone type
accordingly. Note that the SoftX3000 sends the number change notification tone with
the number only when Failure cause code is Number change.
[Send answer signal]

11-39

It decides whether the local office sends an answer signal to the opposite office during
failure processing of incoming calls. It is available only when Processing type is set
to Send signal tone. By default, it is set to No. If you set it to Yes, the opposite
office will charge the failed calls.
Processing type is set to Reanalysis after number change. This parameter must first
be defined in the ADD DNC command before being referenced here.
11.3.10 Adding Auxiliary Signaling (Optional)

I. Related commands
Command
Function
ADD AUSSIG
To add auxiliary signaling data
RMV AUSSIG
To remove auxiliary signaling data
MOD AUSSIG
To modify auxiliary signaling data
LST AUSSIG
To list auxiliary signaling data

Auxiliary signaling is used by the local office to send or request caller number to or
from the opposite office for a specific call prefix. In addition, it can be used to set a
specific call prefix to a prefix for emergency calls or free calls.

[Local DN set]
It defines the local DN set of a call prefix that requires auxiliary signaling. This
referenced here.
[Call prefix]
It specifies the call prefix that requires auxiliary signaling. This parameter must first be
[Call source code]
It specifies the call source that requires auxiliary signaling. That is, the call processing
software triggers the auxiliary signaling analysis procedure for a specific call prefix
11-40

dialed by the call source. This parameter must first be defined in the ADD CALLSRC
[Request caller number]
It indicates whether the local office shall request caller number from the opposite
office, when such information is not included in the messages received from the peer
through incoming trunk. By default, it is set to No, meaning not requesting caller
number. In the R2 signaling, this parameter is used to indicate whether the local office
sends A6 signal to the opposite office.
[Request caller position]
It indicates from which digit of the called number the opposite office starts to send the
caller number to the local office. It is available only when Request caller number is
set to Yes. In the R2 signaling, this parameter is used to indicate the local office
sends A6 signal to the opposite office to request caller number after sending how
many digits of the called number.
It decides whether the local office shall send the caller number through outgoing
signaling. By default, it is set to No, meaning not sending.
[Translate caller number]
During a call forwarding service, the parameter decides whether the number
displayed on the phone of the local callee is the caller number or the original called
number if the opposite office sends both the caller number and the original called
number to the local office through incoming signaling messages. By default, it is set to
No, meaning the caller number is displayed; if it is set to "Yes, the original called
number is displayed.
For instance, subscriber A of opposite office calls subscriber B, who forwards the call
to local subscriber C. When the number sent by the opposite office through incoming
trunk includes number of A and B, C displays the number of A in default condition;
when Translate caller number is set to Yes, C displays the number of B.
[Send original called number]
When the local subscriber applies call forwarding service, it specifies whether the
local office shall forward the original called number to the opposite office through the
outgoing trunk. By default, it is set to No, which means that the SoftX3000 will not
send the original called number.
For instance, the local subscriber A calls B, who forwards it to C of opposite office.
The local office will not send the number of B to the opposite office unless Send
original called number is set to Yes.

11-41

[Emergency call override]

It defines whether a call prefix is an emergency call prefix. The default value is No. If
it is set to Yes, the calls can always be connected successfully if any subscriber
(defaulting subscriber or not) or incoming trunk of the local office dials this emergency
call prefix. It is applicable to special service prefixes.
[Mincode occupy trunk]
It specifies whether the call processing software seizes the outgoing trunk
immediately when a subscriber or an incoming trunk dials the call prefix whose length
reaches the minimum length (defined in ADD CNACLD) required in the number
analysis table. The default value is Yes.
[Send the toll connection type]
It specifies whether the local office sends the toll connection type to the opposite
office through outgoing signaling messages. By default, it is set to No, which means
not sending the toll connection type. In the R2 signaling, this parameter indicates
whether the local office sends KC signal to the opposite office on initiative.
KC signal is the connection control signal sent forwardly between toll offices. It
ensures the communication quality of priority subscribers, controls the number of
satellite circuits, and connects specified calls.
[Position to send toll connection type]
It indicates from which digit the local office starts to send the toll connection type to the
opposite office. It is available only when Send the toll connection type is set to Yes.
In the R2 signaling, this parameter indicates the local office sends KC signal to the
opposite office after sending how many digits of the called number.
[Free right call]
It defines whether a call prefix is a free call prefix. The default value is No. If it is set
to Yes, the system generates a free bill when any subscriber or incoming trunk of the
local office dials the call prefix. In this call, the caller is not charged in the default mode
defined in ADD CNACLD.

11-42

Chapter 12 Configuring Subscriber Data

12.1.1 Subscriber Terminal Category
From different views, there are multiple ways to classify the subscriber terminals.
I. Based on supported media type

z
Voice subscriber: The subscriber terminal only supports voice services. The
terminals include common analog phone set, MGCP soft terminal, MGCP hard
terminal, H.248 soft terminal and H.248 hard terminal.
Multimedia subscriber: The subscriber terminal supports not only the voice
services, but also the video and data services. The terminals include videophone,
SIP soft terminal, SIP hard terminal, H.323 soft terminal and H.323 hard terminal.
II. Based on connected MG type

z
ESL subscriber: The subscriber terminal can get access to MGCP gateway or
H.248 gateway through ordinary twisted pair, or the subscriber equipment itself is
an MGCP soft terminal, MGCP hard terminal, H.248 soft terminal or H.248 hard
terminal.
V5 subscriber: The subscriber terminal can get access to the V5 access network
(AN) device through ordinary twisted pair, and the V5 AN device interworks with
the SoftX3000 through the V5.2 protocol by a V5UA signaling gateway (for
example, UMG8900).
ISDN subscriber: The ISDN subscriber terminals are classified as BRA subscriber
terminals (2B+D) that are connected to the MGCP gateway or the H.248 gateway
through ordinary twisted pair and PRA subscriber terminals (30B+D) that are
connected to the MGCP gateway or the H.248 gateway through E1 cable. The
MGCP or H.248 gateway interworks with the SoftX3000 through DSS1 with the
help of an IUA signaling gateway (for example, UMG8900).
SIP subscriber: The subscriber terminal is SIP soft terminal or SIP hard terminal.
H.323 subscriber: The subscriber terminal is H.323 soft terminal or H.323 hard
terminal, or the subscriber terminal accesses H.323 IAD through ordinary twisted
pair.
III. Based on purpose

z
Ordinary subscriber: Each ordinary subscriber has a public telephone number,

that is, Public Switched Telephone Network (PSTN) telephone number, a long
number.

12-1

z
PBX subscriber: Private Branch Exchange subscriber. PBX subscriber line can be
used as an analog trunk to connect the PBX to the network or as an automatic call
distributor to implement Call Centrex function. Multiple PBX subscribers make up
of a PBX group, which is identified by PBX indicating number (sometimes called
PBX pilot number). A subscriber can call the PBX indicating number to
implement PBX line selection or call distribution. The PBX subscribers may either
occupy number resources or not. However, the PBX indicating numbers must
occupy number resources.
Centrex group subscriber: Centrex means to implement subscriber exchange

functions over the PSTN, that is, the subscribers of a Centrex group can use
Centrex intra-group numbers (similar to PBX extension numbers) to make calls.
Each Centrex subscriber has two phone numbers, namely PSTN number (long
number) and Centrex intra-group number (short number).
12.1.2 Identification of Subscriber Line Physical Port

According to the type of the MG to which a subscriber terminal connects or belongs,
there are different ways to identify the subscriber terminal. Meanwhile, for the MGs of
different manufacturers, the methods for identifying subscriber terminals are different.
I. ESL/BRA subscriber in MGCP gateway

When the MG adopts MGCP, the physical port of its subscriber line is identified by the
domain name of the MG, the prefix part of the termination ID, and the number part of the
termination ID. The format of the ID of the physical port is Prefix part of the termination
ID/Number part of the termination ID @ domain name.
For example, the domain name of an MG is amg1.huawei.com. The prefix of the
termination ID of the MG does not adopt the layered structure. The prefix of the
termination ID (that is, the interface name) is aaln. Supposing the MG has four analog
subscriber line ports, the four ports are identified as follows.
z
Physical port 1: aaln/1 @ amg1.hauwei.com
Another example, the domain name of an MG is amg2.cisco.com and the termination

ID of the MG adopts a two-layer structure. The format of the termination ID is
slot-mm/port-nn (mm and nn are the number part). Suppose the MG has four digital
subscriber line (BRA subscriber) ports, and the four ports are identified as follows.
(Each BRA subscriber occupies two termination IDs.)
z
Physical port 0 of slot 1: slot-01/port-00 @ amg2.cisco.com

12-2

While configuring ESL/BRA subscriber data, you can specify the number part of the
termination ID to identify a subscriber line physical port of the MGCP gateway.
II. ESL/BRA subscriber in H.248 gateway

When the MG adopts H.248 protocol, there are two methods to identify the physical
ports of its subscriber lines.
z
When the protocol is in text format, the identification format is Prefix part of the
termination ID/Number part of the termination ID.
When the protocol is in binary format, the identification format is Number part of
the termination ID.
While configuring ESL/BRA subscriber data, you can specify the number part of the
termination ID to identify a subscriber line physical port of the H.248 gateway no matter
which format the gateway protocol is in.
III. V5 subscriber in V5 AN device

When the V5 AN device adopts V5.1 or V5.2 protocol, the physical port of its subscriber
line is identified by L3 address in the V5.1 or V5.2 protocol.
L3 address, the layer-3 address, is the address of the PSTN protocol or control protocol
of EFaddr type in the layer-3 message.
z
When used for PSTN protocol, L3 address is used to identify the PSTN subscriber
port and the valid address contains 15 bits, that is, a maximum of 32768 analog
subscribers can be supported.
When used for control protocol, L3 address is used to identify PSTN subscriber
port, ISDN subscriber port, or V5 public control function. When L3 address is used
to identify PSTN subscriber port, its valid length is 15 bits, which means that a
maximum of 32768 analog subscribers can be supported. When It identifies ISDN
subscriber port or public control function, its valid length is 13 bits, which means
that a maximum of 8175 ISDN subscribers can be supported. The public control
function needs to occupy part of the L3 address.
Note:
Because V5.1 protocol only supports one E1 and has no convergence function, it can
give access to 30 V5 subscribers in maximum except time slot 0 (synchronization time
slot) and time slot 16 (signaling time slot) fixedly occupied by the system.
While configuring V5 subscriber data, you can specify L3 address to identify a

subscriber line physical port of the V5 AN device no matter which protocol, V5.1
protocol or V5.2 protocol, is adopted.

12-3

IV. Subscriber in H.323 IAD

When the IAD adopts H.323 protocol, the identification format for the physical port of its
subscriber line is Termination ID. While configuration H.323 subscriber data, you can
specify Termination ID to identify a subscriber line physical port of the H.323 IAD.
12.1.3 ISDN Subscriber-Network Interface

Figure 12-1 illustrates the reference configuration (reference model) for the ISDN
subscriber-network interface, which is an abstract interface arrangement designed by
the ITU-T for standardizing the subscriber-network interface. The reference
configuration involves several reference ports to be standardized and various
functional groups relating to them.
R
TE1
U
NT1
NT2
R
TE2
Transmission media
S
TA
Reference point
Functional group
TE1: ISDN standard terminal

TE2: ISDN non-standard terminal
NT1: Network terminal type 1
NT2: Network terminal type 1 (such as PBX, LAN, and router)
TA: Terminal adapter
Figure 12-1 Reference configuration for ISDN subscriber-network interface

z
Functional group: A rectangle shown in Figure 12-1 represents a functional group

that is a combination and arrangement of various functions necessary on the ISDN
subscriber interface. Several functional groups might be achieved in a physical
device.
Reference point: A crossing shown in Figure 12-1 represents a reference point

that is a conceptual reference point for classifying functional groups. It can be a
physical interface between device units in subscriber access. When several
functional groups are integrated in the same physical device, the reference point
between the functional groups is merely a conceptual point because you cannot
find the physical interface.
I. Reference point
1)
U reference point

12-4

The U reference point, also called the U interface, is the line interface between the
network and a subscriber. The ITU-T defines the U interface to be specifically the line
interface between an ISDN BRA subscriber and the network.
The BRA U interface defines code types for transmission lines. For 2B1Q line encoding
format, the element rate (the baud rate) on the line is 80 kbit/s and the corresponding
bandwidth is 160 kbit/s, with the following allocations:
z
2B channel: Service channel at the rate of 128 kbit/s.
D channel: Signaling channel at the rate of 16 kbit/s.
M channel: Maintenance channel for conveying maintenance related information

between the network and the terminal at the rate of 4 kbit/s.
U port synchronization field: Used for conveying clock signals at the rate of 12
kbit/s.
2)
S reference point and T reference point
The S reference point, also called the S interface, is the line interface between an ISDN
terminal (Terminal Equipment Type 1 or Terminal Adapter) and a Network Terminal
(NT). The T reference point, also called the T interface, is the line interface between a
Network Terminal Type 1 (NT1) and a Network Terminal Type 2 (NT2).
The ITU-T recommends the same specifications for the S interface and the T interface.
When an NT2 device does not exist, the S interface and the T interface combine to be
the S/T reference point, which is also called the S/T interface.
3)
R reference point
The R reference point, also called the R interface, is a non-standard ISDN terminal
interface, such as RS-232 interface, IEEE-488 interface, and analog telephone
interface.
II. Functional group

1)
Network Terminal Type 1 (NT1)
NT1 provides the U interface and the S/T interface, connecting ISDN terminal and
ISDN switch. NT1 is used for code conversion between the U interface and the S/T
interface.
Being a purely physical-layer device, NT1 has no software intelligence but provides line
maintenance and performance monitor functions to ensure clock synchronization
between the ISDN terminals and the network.
Note:
If NT1 provides terminal adapter functions, the NT1 is usually named NT1+.
2)
Network Terminal Type 2 (NT2)

12-5

NT2 is an intelligent terminal device. Examples of NT2 are terminal control devices
such as Private Automatic Branch Exchanges (PABXs) with ISDN functions, and LAN
routers.
3)
Terminal Equipment Type 1 (TE1)
TE1 is a standard ISDN terminal. TE1 provides the standard S interface. It can be
interconnected to NT1 or NT2 through the S interface. Examples of TE1 are ISDN
digital telephone, G4 fax machines, and video telephones.
4)
Terminal Equipment Type 2 (TE2)
TE2 is a non-standard ISDN terminal. TE2 does not provide the S interface. It cannot
be interconnected to NT1 or NT2. Through a terminal adapter, TE2 can be connected
to an S interface. Examples of TE2 are ordinary computers, ordinary telephones, X.25
packet-based terminals, and G3 fax machines.
5)
Terminal Adapter (TA)
TA provides the S or U interface at one end and provides an interface to various

non-standard ISDN terminals at the other end. TA is used for rate adaptation and
protocol conversion. Because a non-standard ISDN terminal does not have CAS
channels (D-channels), the non-standard ISDN terminal (TE2) must pass through rate
adaptation and protocol conversion of a TA before being connected to the S or U
interface.
AT command set is built in some TAs. AT command set is a universal command format
for computer to operate modem, supporting to originate and answer calls directly
through computer (i.e. converting AT commands to D-channel signaling). Therefore,
through a TA, computer can be used in call and data transfer simultaneously.
B-channel protocol passing through a TA is V.110, which converts low-rate serial port
data to 64 kbit/s B-channel so that a non-standard ISDN terminal can communicate
with the network through a standard ISDN interface.
12.2 Configuring Ordinary Subscriber Data

12.2.1 Overview
The ordinary subscriber data is used to define the configuration information of the voice
subscribers and multimedia subscribers managed by the SoftX3000. To configure the
ordinary subscriber data, ensure that the equipment data, local office data, charging
data, MG data, protocol data (for adding SIP subscriber and H.323 subscriber) and
signaling data (for adding V5 subscriber) has been configured. See Figure 12-2.

12-6

Start
Equipment data
Trunk data
Office data
Number analysis
Charging data
Subscriber data
MG data
Centrex data
MRS data
Call barring data
Protocol data
IN service data
Signaling data
Other service data
Routing data
Other application
data
End

During the configuration, some parameters defined in the equipment data, local office
data, charging data, MG data and signaling data will be referenced in the ordinary
subscriber data (the broken lines in Figure 12-2 show the referencing relationship).
Table 12-1 Parameter referencing relationship between ordinary subscriber data and
other data
Input parameter
Name
Output parameter
Defined in
Name
referenced in
Module number of FCCU/FCSU
Equipment data
Local DN set
Local office data
Call source code
Local office data
Charging data
Called charging source code (optional)
Charging data
Equipment ID of the media gateway
MG data
V5 interface ID (optional)
Signaling data

12-7

II. Preparations
Before configuring the ordinary subscriber data, make sure that all preparations are
done as specified in Table 12-2.
SN
Item
Remark
Termination
ID
range of the MG
For determining the subscriber number allocation

scheme.
Subscriber number
assignment
planning
For assigning a number for the termination ID of each

MG according to the number segment planning of local
office.
PRA
subscriber
attribute planning
Including subscriber type, call-in/call-out right and

charging category.
L3 address
For specifying the logical port address of V5 subscriber

in the V5 AN device when the SoftX3000 interworks
with the V5 AN device.

Table 12-3 lists the general steps for configuring the ordinary subscriber data. There is
no strict requirement for the sequence of these steps.
Step
Description
Command
Add
voice
subscriber
ADD VSBR (to add a voice subscriber)
Add
multimedia
subscriber
ADD MSBR (to add a multimedia subscriber)
Add wide area

Centrex
subscriber
ADD WACSBR (to add a wide area Centrex subscriber)
ADB VSBR (to add a batch of voice subscribers)
ADB MSBR (to add a batch of multimedia subscribers)
ADB WACSBR (to add a batch of wide area Centrex

subscribers)

During the configuration, the key fields of the data tables are not referenced mutually.

12-8

12.2.2 Adding a Voice Subscriber

I. Related commands
Command
Function
ADD VSBR
To add a voice subscriber
RMV VSBR
To remove a voice subscriber
MOD VSBR
To modify a voice subscriber
LST VSBR
To list the configuration information of a voice subscriber

Before adding a voice subscriber, use the related commands to get the following
parameters defined by the system.
z
Called charging source code (optional): LST CHGCLD
Equipment ID of the media gateway: LST MGW
V5 interface ID (for adding V5 interface): LST M5I

[Subscriber number]
It specifies the phone number assigned to the subscriber. The specified number must
be in the number segment defined in the ADD DNSEG command. This parameter must
be specified for the subscribers except those PBX subscribers not occupying number
resources.
[Local DN set]
It specifies the local DN set to which the subscriber belongs. That is, it indicates the
local DN set in whose number analysis table the call processing software analyzes all
called numbers dialed by the subscriber. This parameter must be defined in the ADD
[Port type]
It specifies the port type of the subscriber, ESL or V5. The default is ESL.
It specifies the module number of the FCCU or FCSU processing the calls of the
subscriber at the SoftX3000 side. Its value ranges from 22 to 101. This parameter must
be defined in the ADD BRD command before being referenced here.

12-9

command ADD MGW; otherwise, the subscriber terminals subject to the media
gateway cannot work normally.
[Equipment number]
It specifies the equipment number assigned to the subscriber. Generally, this parameter
need not be specified, and it is allocated by the system with the value range from 0 to
59999. That is, one module can process the calls of a maximum of 60,000 subscribers.
[Equipment ID]
It specifies the equipment ID of the MG to which the ESL subscriber belongs, that is, to
indicate which MG the ESL subscriber is connected to. This parameter is available
when the ESL subscriber is configured. This parameter must be defined in the ADD
MGW command before being referenced here.
[Termination ID]
It specifies the physical port number of the MG to which the ESL subscriber belongs.
This parameter is available when the ESL subscriber is configured. It only consists of
digits and/or the symbol "/". Set this parameter by the following principles:
z
parameter. For example, the domain name of a gateway is amg1.huawei.com.
The prefix (that is, the interface name) of the termination ID is aaln. If the
Termination ID is 0 here, aaln/0 @ amg1.hauwei.com indicates physical interface
0 of the media gateway.

[V5 interface ID]

It specifies the ID of the interface connecting with the V5 AN device to which the V5
subscriber belongs. This parameter is available when the V5 subscriber is configured.
This parameter must be defined in the ADD V5I command before being referenced
here.
[L3 address]
It identifies the physical port address of the V5 subscriber in the V5 AN device. This
parameter is available when the V5 subscriber is configured.
L3 address is the address of the PSTN protocol or control protocol of EFaddr type in the
layer-3 message.
z
port and the valid address contains 15 bits, that is, a maximum of 32768 analog
12-10

[V51 B1 circuit number]
It specifies the timeslot in the 2.048 Mbit/s circuit to be used by the V5 subscriber. This
parameter is available when the V5 subscriber is configured and the V5 AN device
adopts V5.1 protocol. Among the 30 B circuits, one B circuit corresponds to one V5
subscriber because the V5.1 protocol only supports one E1 but does not support
convergence function.
[Codec prefer]
It specifies the voice codec mode preferred by the media gateway (controlled by the
SoftX3000 during call connection process) to process the RTP audio media streams of
the subscriber. The default value is G.711A. It must be one among the codec list defined
in the command ADD MGW. Otherwise, it is invalid.
When all media gateways involved in a call are controlled by the SoftX3000, if the
SoftX3000 finds that there are codec modes concurrently supported by the caller and
the callee during call connection, and the codec modes include the preferred codec
mode configured in this parameter, the SoftX3000 will use the signaling to control the
media gateways at both the caller and callee sides to directly use the preferred codec
mode to connect the media stream.
z
discrimination table or the called number analysis table, the SoftX3000 selects the
codec mode according to the caller first and subscriber first principle. For
codec modes, only the codec mode of the caller is valid. During a transit call, if the
incoming trunk group and the outgoing trunk group of the local office have different
preferred codec modes, only the codec mode of the incoming trunk group is valid.
During an incoming terminated call, if the incoming trunk group and the callee of

12-11

the local office have different preferred codec modes, only the codec mode of the
callee is valid.
It is one of the charging attributes of the subscriber. This parameter must be defined in
the command ADD CHGGRP or ADD CHGIDX before being referenced here. For the
detailed information about charging, see Chapter 4, Configuring Charging Data, in
this manual.
[Call source code]
It specifies the call source to which the subscriber belongs. This parameter must be
[Subscriber type]
It defines the type of the caller. The options are
z
Ordinary: It is applicable to ordinary subscribers who have no route selection

priority during congestion. For example, they cannot seize the reserved circuits of
the ISUP trunk group; their calls are restricted first when the system is overloaded;
their calls are permitted last when the system is recovered from overload.
Priority: It is applicable to priority subscribers who have route selection priority

during congestion. For example, they can seize the reserved circuits of the ISUP
trunk group; their calls are restricted last when the system is overloaded; their calls
are permitted first when the system is recovered from overload.
Operator: It is applicable to operators who have the authorities for forced insertion,
forced release, interception, and recording.
Data: It is applicable to data subscribers or subscribers needing protection. Others

(including operators) are not allowed to break in or release their calls.
Test: It is applicable to test subscribers Only test subscribers or operators can use
the dedicated call service.
Payphone: It is applicable to such pre-payment subscribers as Advanced Prepaid

Service (APS) subscribers.
[Subscriber status]
It indicates the status of the subscriber, normal or owing charge. Generally, it is set to
Normal". The options are
z
Normal: The subscriber can originate or receive calls normally and is flagged as a
normal subscriber.
Owing fee in call-out: The subscriber can receive but cannot originate calls except
emergency calls.
Owing fee in call-in: The subscriber cannot receive but can originate calls.
Owing fee in call-out and call-in: The subscriber can neither receive nor originate
calls except emergency calls.
Owing fee but have right: The subscriber can originate or receive calls normally
but is flagged as an owing-fee subscriber.
12-12

z
Owing fee forward to operator: All calls to the subscriber are forwarded to the
operator, and the subscriber cannot originate calls except emergency calls.
[Additional status]
This parameter sets whether the subscriber is a PBX subscriber. By default, it is set to
Ordinary. The options are
z
Ordinary: The subscriber is not a PBX subscriber.
PBX non-pilot number occupying number: The subscriber is a PBX subscriber,

and you need to specify the subscribers phone number in the Subscriber
number field.
PBX non-pilot number: The subscriber is a PBX subscriber, but you need not
specify the subscribers phone number in the Subscriber number field. The PBX
subscriber not occupying number resource cannot be a Centrex subscriber.
[Call-in authority]
It defines the call-in authorities of the subscriber, including intra-office, local, local toll,
national toll, international toll, intra-Centrex, incoming Centrex, intra-office national toll
(in multi-zone-code application) and intra-office international toll (in multi-country-code
application). The system enables all call-in authorities of the subscriber by default.
It should be noted that when the subscriber is a Centrex group subscriber, the call-in
authorities cannot be higher than Console call in right defined in this command.
It defines the call-out authorities of the subscriber, including intra-office, local, local toll,
application). By default, the system enables all call-out authorities of the subscriber
except national toll, international toll, intra-office national toll and intra-office
international toll.
It should be noted that when the subscriber is a Centrex group subscriber, the call-out
authorities cannot be higher than Console call out right defined in this command.
It defines the supplementary service authorities of the subscriber. By default, the
subscriber has no supplementary service authorities.
It should be noted that when the subscriber is a Centrex group subscriber, the
supplementary service authorities cannot be higher than Console supplementary
service defined in this command.
[Centrex flag]
It indicates whether the subscriber is a Centrex subscriber. Select "No for ordinary
subscribers, and select Yes for Centrex subscribers.
[Centrex group number]

12-13

It specifies the number of the Centrex group to which the subscriber belongs. This
parameter is available when "Centrex flag is Yes. This parameter must be defined in
the ADD CXGRP command before being referenced here.
[Centrex short number]
It specifies the extension number (short number) of the subscriber in the Centrex group.
This parameter is available when "Centrex flag is Yes. The Centrex short numbers
must comply with the rule (number length and prefix) for Centrex intra-group numbers,
and the rule is defined in the ADD ICXPFX command.
[Call pickup]
It specifies the number of the call pickup group of the subscriber in the Centrex group.
This parameter is available when Centrex flag" is set to Yes. Its value ranges from 0
to 255, and the value 255 indicates that the setting is invalid.
[Tariff pulse type]
It defines whether the physical port where the subscriber is located supports to send
immediate charging signals such as 16KC, 12KC, polarity reversal signals, and polarity
reversal pulse. By default, it is set to Null. If you set it to any of the above-mentioned
signals, the subscriber board of the related media gateway or the V5 AN device must
support the transmission of the specified immediate charging signals; otherwise, the
immediate charging function of the subscriber's phone set is disabled.
[Call-out password]
It defines the initial call-out password used when the subscriber registers outgoing
restricted supplementary service (sometimes called number restriction service). The
password contains four to six decimal digits and the specific length depends on the
service syntax. By default, the password is 000000, and you can change the password
by telephone.
[Charging category]
It specifies the charging category of the subscriber number. The default value is
Period. The options are
z
Period: The system charges the subscribers periodically (for example, every
month) instead of for each call.
Immediate subscriber table: During a call, the system sends charging pulse
regularly (for example, every 60 seconds) to the subscribers phone set according
to the charging tariff of the call. This category is mainly applied to the immediate
charging of unattended public phones.
Immediately sending to printer: After a call ends, the system immediately sends a
bill to the subscribers phone set or the agent (for example, the console). This
category is mainly applied to the immediate charging in the telecom service
counter hall, IP supermarket, and so on.
Free: The calls that require no payment from the calling party after service
analysis, such as police call, fire emergency call, ambulance emergency calls,
12-14

traffic accident calls, FPH calls, and collect calls. For calls defined as free in
charging category, the detailed call information of the caller will still be recorded,
and the free call detailed ticket will be generated.
It defines whether the system generates an additional complaint bill for the call
originated by the subscriber for query. The default value is No. If a subscriber
questions a bill, you can set this parameter to Yes.
After you set Charging complaint of a subscriber number to Yes, a large number of
complaint bills may be generated and occupy normal bill space. If the subscriber is
satisfied with the check result, you need to set this parameter to No in time.
One of the charging attributes of the subscriber. This parameter must be defined in the
ADD CHGCLD command before being referenced here. The default value is 255,
indicating that called charging is not conducted. For the detailed information about
charging, see Chapter 4, Configuring Charging Data, in this manual.
It specifies the call barring group to which the subscriber belongs. The configuration
principle is described as follows:
z
enabled.
If the black & white list is used for call barring, the preset three call barring groups
can be referenced directly, that is black list 60001, white list 60002 and ordinary
call barring group 65534.
If the other call barring groups are used, this parameter must be defined in the
If the subscriber is a Centrex subscriber and the time-based call barring function is
adopted, this parameter must be defined in the ADD LCGRP command before
It should be noted that the call barring group number can be used for both time-based
call barring and inter-group call barring. Meanwhile, inter-group barring is prior to
time-based barring, that is, the system first judges whether to implement inter-group
barring and then whether to implement time-based barring. The SoftX3000
authenticates inter-group call barring twice for the call prefix, and the caller and callee
sides during the number analysis process. To use the function correctly and avoid
mistakes, read the following inter-group call barring procedure:
1)
The SoftX3000 authenticates the inter-group call barring for the first time for the
call barring group number (calling number barring group) of the caller/incoming
trunk and that (called number barring group with the default value as 65534. it can
be configured in the command ADD CLDGRP) of the call prefix. If the

12-15

authentication is passed, the SoftX3000 continues with the subsequent procedure.

Otherwise, the call is rejected.
2)
If the first authentication is passed, the SoftX3000 authenticates the inter-group

call barring for the second time for the call barring group numbers (calling number
barring group) of the caller/incoming trunk and that (called number barring group)
of the callee/outgoing trunk. If the second authentication is passed, the SoftX3000
continues with the subsequent procedure. Otherwise, the call is rejected.
[PBX pilot number]

It defines the indicating number of a PBX subscriber in the PBX group. This parameter
must be defined in the ADD PBX command before being referenced here.
[PBX subscriber priority]
It defines the priority of the PBX subscriber. Its value ranges from 0 to 255. The value
0 indicates the highest priority. The larger the value is, the lower the priority. If the
priorities of the PBX subscribers are the same, the system will perform PBX line
selection according to the selection mode defined in the PBX group (through the ADD
PBX command). If a PBX subscriber has the highest priority, the system will select the
PBX subscriber line first while performing PBX line selection.
For example, there are ten PBX subscribers in a PBX group. The priority of five
subscribers is 0 and that of the others is 1. When the system performs PBX line
selection, it will first select the five PBX subscribers with priority 0, and these five PBX
subscribers will be further selected according to the selection mode defined in the PBX
group. When the five PBX subscribers are all occupied, the system selects the other
five PBX subscribers with priority 1.
[Console call-in authority]
It specifies which call-in rights the console of the subscriber resident Centrex group can
control for the subscriber. This parameter is available when Centrex flag is "Yes, and
the default setting is All.
If the subscriber is a Centrex intra-group subscriber, Console call in right must be
higher than the call-in rights of the subscriber; otherwise, the system prompts errors
when you are configuring the data.
[Console call-out authority]
It specifies which call-out rights the console of the subscriber resident Centrex group
can control for the subscriber. This parameter is available when Centrex flag is "Yes,
and the default setting is All except international toll and intra-office international toll.
If the subscriber is a Centrex intra-group subscriber, Console call out right must be
higher than the call-out rights of the subscriber; otherwise, the system prompts errors
when you are configuring the data.
[Console supplementary service]

12-16

It specifies which supplementary service rights the console of the subscriber resident
Centrex group can control for the subscriber. This parameter is available when
Centrex flag is "Yes, and the default setting is All.
If the subscriber is a Centrex intra-group subscriber, Console supplementary
service must be higher than the supplementary service rights of the subscriber;
otherwise, the system prompts errors when you are configuring the data.
[Limited time]
It defines the maximum conversation duration of a call. If the conversation of a call
exceeds the set value, the system will force to release the call. This parameter is
available when the subscriber registers the timed restriction service. Its value ranges
from 1 to 65535 with the unit as minute.
[Limited money]
It defines the maximum money that the subscriber can spend every month. In each
month, if the accumulated charge of the subscriber exceeds the set value, the system
will prohibit the subscriber from making calls. This parameter is available when the
subscriber registers the quota limited calling service. Its value ranges from 50 to
10000000, with the unit as cent.
The limited money is resumed every month, and the resumption time is controlled by
the parameter Upper limit resumed time per month (P87). When the subscriber
registers the restriction alarm service, the limited money stands for the remaining
money. If the subscriber registers the quota limited calling service and restriction
alarm service at the same time, the system only enables the quota limited calling
service.
[Customize subscriber type]
It specifies the customized subscriber type of the subscriber number. There are 16
options. The customized subscriber types are used for inter-office transmission and bill
display.
[RM source]
This parameter specifies the resource management source code to be used by the
subscriber. When the subscriber dials any call prefix, the SoftX3000 instructs the
corresponding resource management device to reserve bandwidth for the bearer
channel to be used in the call. This parameter is defined in the ADD RMANA command
[Ringing mode]
This parameter specifies the ringing mode of the voice subscriber, that is, the type of
ringing current that the SoftX3000 controls the associated MGW to send to the called
subscriber. Available options are as follows:
z
Normal: ringing for 1 second, then no ringing for 4 seconds;
Special: ringing for 1 second, then no ringing for 2 seconds;

12-17

z
Hongkong: ringing for 4 seconds, no ringing for 2 seconds, then ringing for 4
seconds, no ringing for 4 seconds;
Long: keep ringing;
FSK: ringing for 1 second, then no ringing for 4 seconds. The FSK signals will be
transmitted to the telephone from the exchange between the first ring and the
second ring, for the purpose of presenting the caller number.
Hongkong special: ringing for 0.4 seconds, no ringing for 0.2 seconds, then ringing
for 0.4 seconds, no ringing for 0.2 seconds, and then ringing for 0.4 seconds, no
ringing for 2.4 seconds.
Whether the selected ringing mode can be achieved depends on the related MG or V5
AN device.
[User name]
It identifies the subscriber with a maximum of 32 characters.
[NP number]
It defines the NP number used by the subscriber. If the NP number is within the
subscriber number segment defined by the local office, it cannot be used in the
database. That is, it cannot be allocated to other subscribers.
If you specify an NP number for the subscriber, the SoftX3000 uses the NP number
instead of the real number as the caller number during call connection when the
subscriber originates a call. The caller number displayed on the callees telephone and
the charged number in a bill are the NP number of the subscriber.
[Call watch flag]
It specifies whether the SoftX3000 watches all calls of the subscriber. By default, it is
set to No. If you set it to Yes, the SoftX3000 generates an alarm at the alarm console
for any call activities such as offhook, dialing, call-in, or call-out.
[Super Do-Not-Disturb]
It defines the initial password for the super do-not-disturb service. It contains four to
six decimal digits and the specific length depends on the service syntax. The default
password is 000000, which can be modified through phone set.
[Incomplete call watch]
It defines whether the system records the failed calls of the subscriber, that is, whether
the system generates watch bills for failed calls. The options are
z
No watch: It is the default value, indicating that the system does not record the
failed calls of the subscriber.
Watch caller: It indicates that the system only records the failed calls originated by
the subscriber.
Watch callee: It indicates that the system only records the failed calls to the
subscriber.

12-18

z
Watch both: It indicates that the system records all failed calls originated or
received by the subscriber.
[Display fee ring flag]

It specifies whether the SoftX3000 sends ringing current to the subscribers phone set
before sending charging signals (FSK signals) when the subscriber uses the Advice of
Charge at the End of Conversation service. The default value is "Yes. If you set it to
No, the SoftX3000 only sends charging signals to the subscriber's phone set.
[Executive busy override level] and [Executive busy override protection level]
They define the levels of busy override authorities and busy override protection
authorities had by the subscriber. The default is No level.
Busy override is a supplementary service. In this service, when subscriber A calls
subscriber B who is talking with subscriber C, subscriber A can break in, and the three
subscribers form a three-party call. To prevent arbitrary use of the busy override
function, in this example, the SoftX3000 allows subscriber A to use the function only
when the following conditions are all met:
z
Subscribers A, B, and C are all in the local office.
Subscriber A has supplementary service authorities of busy override or call

break-in.
The executive busy override level of subscriber A is higher than the executive
busy override protection levels of subscribers B and C.
The executive busy override invocation types of subscribers B and C must not be
Invalid.
[Executive busy override invocation type]

It specifies whether the SoftX3000 allows other subscribers to break in by using the
busy override function during a conversation. The meanings of the options are as
follows:
z
Invalid: It is the default value, indicating that other subscribers cannot use the busy
override function to break in a conversation in any case.
Consultation: It indicates that other subscribers can use the busy override function
to break in a conversation by pressing the hook and then dialing the access code
(*33, for example).
Immediate: It indicates that other subscribers can use the busy override function to
directly break in a conversation.
[Bill time identifier]

It defines the time identifier in the call meter bill of the subscriber. Its value ranges from
0 to 255. The parameter is mainly used in Thailand. The iGWB maps the time identifier
in the call meter bill to a specific date. The iGWB then sends call meter bills of the
subscriber to the billing center periodically according to the date.
[Online observation flag]

12-19

It specifies whether the SoftX3000 observes successful calls of the subscriber. The
default value is No. The meanings of the options are as follows:
z
On line incoming: It indicates to online observe incoming calls. When other

subscribers call the subscriber, and the subscribers phone rings, the SoftX3000
generates an alarm of the call for the subscriber on the alarm console.
On line outgoing: It indicates to online observe outgoing calls. When the

subscriber makes a call, and the callees phone rings, the SoftX3000 generates an
alarm of the call for the subscriber (caller) on the alarm console.
Log observation: When a call related to the subscriber is released, the SoftX3000
creates a log in the hard disk of the BAM. You can read the log by using
professional browsing tools.
12.2.3 Adding a Batch of Voice Subscribers

I. Related commands
Command
Function
ADB VSBR
To add a batch of voice subscribers
RVB VSBR
To remove a batch of voice subscribers
MOB VSBR
To modify a batch of voice subscribers
LST VSBR
To list a batch of voice subscribers

Before adding a batch of voice subscribers, use the related commands to get the
following parameters defined in the system.
z
V5 interface ID (for adding V5 interface): LST M5I

Most of the parameters in the ADB VSBR command are the same as those in the ADD
VSBR command. This section only presents the special parameters in the ADB VSBR
command. For the detailed information about other parameters, see 12.2.2 Adding a
Voice Subscriber in this chapter.
[Start subscriber number], [End subscriber number]

12-20

They are used to specify the range of the phone numbers of the batch of the
subscribers. The numbers of this range must be in the number segment defined in the
ADD DNSEG command.
[Local DN set]
It specifies the local DN set to which the batch of subscribers belong. That is, it
indicates the local DN set in whose number analysis table the call processing software
analyzes all called numbers dialed by these subscribers. This parameter must be
[Subscriber number step]
It specifies the value difference between a phone number and its previous adjacent
phone number when a batch of subscribers are added. The default value is 1.
It specifies the module number of the FCCU or FCSU processing the calls of these
subscribers at the SoftX3000 side. Its value ranges from 22 to 101. This parameter
must be defined in the ADD BRD command before being referenced here.
command ADD MGW; otherwise, the subscriber terminals subject to the media
gateway cannot work normally.
[Equipment number], [Equipment number step]
It defines the start equipment number and the number step when you add the batch of
subscribers. Generally, the start equipment number is not set, but allocated by the
system in the database. Its value ranges from 0 to 59999. The default equipment
number step is 1.
[Port type]
It specifies the port type of the batch of subscribers, ESL or V5. The default is ESL.
[Equipment ID]
It specifies the equipment number of the media gateway to which a batch of ESL
subscribers are connected. It is available only when you set the ESL subscriber data.
This parameter must be defined in the ADD MGW command before being referenced
here.
[Start MG termination ID], [MG termination ID step]
They are used to specify the start terminal number and the number increment
difference of the batch of the ESL subscribers in the resident MG. They are available
when ESL subscribers are configured. The default value for MG termination ID step is
1.
[V5 interface ID]

12-21

It specifies the interface ID of the V5 AN device to which a batch of V5 subscribers are

connected. It is available only when you set the V5 subscriber data. This parameter
must be defined in the ADD V5I command before being referenced here.
[Start L3 address], [L3 address step]
They are used to specify the start L3 address and address value difference of the batch
of the V5 subscribers in the resident V5 AN device. They are available when V5
subscribers are configured. The default value for L3 address step is 1.
[Start V51 B1 circuit number.], [V51 B1 circuit number step]
They are used to specify the start timeslot number and the timeslot number increment
difference of the 2.048 Mbit/s link used by the batch of the V5 subscribers. They are
available when V5 subscribers are configured and V5.1 protocol is adopted. The
default value for V51 B1 circuit No step is 1.
[Start Centrex short number], [Short number step]
They are used to specify the start Centrex short number and number step of a batch of
the Centrex subscribers in the resident Centrex group. They are available when
Centrex flag is Yes. The default value for Short number step is 1.
12.2.4 Adding a Multimedia Subscriber

I. Related commands
Command
Function
ADD MSBR
To add a multimedia subscriber
RMV MSBR
To remove a multimedia subscriber
MOD MSBR
To modify a multimedia subscriber
LST MSBR
To list the configuration information of a multimedia subscriber

To ensure the normal operation of SIP and H.323 protocol stacks in the SoftX3000
software, make sure that SIP data and H.323 protocol data has been configured
correctly before adding multimedia subscriber, and use the related commands to get
the following parameters defined in the system.
z
Equipment ID of the media gateway: LST MMTE

12-22

Note:
Most of the parameters in ADD MSBR are the same as those in ADD VSBR, so this
section only describes the dedicated parameters in ADD MSBR. For the other
parameters, refer to 12.2.2 Adding a Voice Subscriber.
[Subscriber number]
It specifies the phone number assigned to the subscriber. The specified number must in
the number segment defined in the ADD DNSEG command. This parameter must be
specified for the subscribers except those Private Branch Exchange (PBX) subscribers
not occupying number resources.
[Local DN set]
called numbers dialed by the subscriber. This parameter must be defined in the ADD
[Equipment number]
It specifies the equipment number assigned to the subscriber. Generally, this parameter
need not be specified, and it is allocated within the data by the system with the value
range from 0 to 59999, that is, one FCCU/FCSU can process the calls of a maximum of
60,000 subscribers.
[Equipment ID]
It specifies the equipment ID of the multimedia device to which the multimedia
subscriber connects. This parameter must be defined in the ADD MMTE command
[Termination ID]
It is one of the interconnection parameters between the SoftX3000 and the H.323 IAD,
used to specify the termination ID of the subscriber in the IAD. This parameter is
available when the H.323 IAD subscriber is configured. When what is interconnected
with the SoftX3000 is an H.323 IAD provided by Huawei, the termination ID of the
subscriber must be set to the E.164 number of the subscriber, that is, the telephone
number of the subscriber. Otherwise, the subscriber cannot register with the SoftX3000
successfully.
One of the charging attributes of the subscriber. This parameter must be defined in
ADD CHGGRP or ADD CHGIDX before being referenced here. For the detailed
manual.

12-23

[Call source code]

[Subscriber type]
z



(including operators) are not allowed to insert or release their calls.
Test: It is applicable to test subscribers Only test subscribers or operators can use
Payphone: It is applicable to such pre-payment subscribers as Advanced Prepaid

Service (APS) subscribers.
12.2.5 Adding a Batch of Multimedia Subscribers

I. Related commands
Command
Function
ADB MSBR
To add a batch of multimedia subscribers
RMV MSBR
To remove a batch of multimedia subscribers
MOD MSBR
To modify a batch of multimedia subscribers
LST MSBR
To list a batch of multimedia subscribers

To ensure the normal operation of SIP and H.323 protocol stacks in the SoftX3000
software, make sure that SIP data and H.323 protocol data has been configured
correctly before adding multimedia subscribers, and use the related commands to get
the following parameters defined in the system:
z

12-24

Equipment ID of the media gateway: LST MMTE
Note:
Most of the parameters in ADD MSBR are the same as those in ADD VSBR, so this
section only describes the dedicated parameters in ADD MSBR. For the other

subscribers. The numbers of this range must be in the number segment defined in the
ADD DNSEG command.
[Local DN set]
[Equipment number], [Equipment number step]
It defines the start equipment number and the number step when you add the batch of
subscribers. Generally, the start equipment number is not set, but allocated by the
system in the database. Its value ranges from 0 to 59999. The default equipment
number step is 1.
[Equipment type]
It specifies whether the subscribers to be added are separated terminals or all
connected to the IAD.
[Start equipment ID], [Equipment ID step]
They are used to specify the start equipment number and the number step when you
add a batch of terminal subscribers. The default value for Equipment ID step is 1.
[Equipment ID]

12-25

It specifies the ID of the H.323 IAD to which a batch of IAD subscribers are connected.
It is available only when you set the IAD subscriber data. This parameter must be
defined in the ADD MMTE command before being referenced here.
When you add a batch of multimedia devices using ADB MMTE, all devices share one
authentication password. To ensure subscriber information security, do not enter the
authentication password in ADB MMTE; instead, use the tool for automatic generation
of multimedia subscriber number allocation command provided by Huawei to generate
the authentication password for each multimedia device automatically.
[Start MG termination ID], [MG termination ID step]
They are available only when you set the IAD subscriber data, specifying the start
termination ID and ID step of the H.323 IAD to which a batch of IAD subscribers are
connected. The default MG termination ID step is 1.
They are used to specify the start Centrex short number and number step of a batch of
the Centrex subscribers in the resident Centrex group. They are available when
Centrex flag is Yes. The default value for Short number step is 1.
12.2.6 Adding a Wide Area Centrex Subscriber

I. Related commands
Command
Function
ADD WACSBR
To add a wide area Centrex subscriber
RMV WACSBR
To remove a wide area Centrex subscriber
MOD WACSBR
To modify a wide area Centrex subscriber
LST WACSBR
To list a wide area Centrex subscriber

The key for implementing the wide area Centrex (WAC) function is that the equipment
can find the mapping between long numbers and short numbers of WAC subscribers.
The SoftX3000 can implement the WAC function by multiple modes such as number
change mode, number translation mode, IN service platform mode, and SHLR mode.
The number change mode is the simplest, but is only suitable for implementing the
WAC function with regular mapping between long numbers and short numbers.
If the carrier wants to implement the WAC fucntion with irregular mapping between long
numbers and short numbers, you can select the number translation mode. In this case,
use the command ADD WACSBR to configure the mapping between long numbers
and short numbers of WAC subscribers.

12-26

Note:
Most of the parameters in ADD WACSBR are the same as those in ADD VSBR, so this
section only describes the dedicated parameters in ADD WACSBR. For other

It specifies the number of the Centrex group to which the WAC subscriber belongs. This
parameter must be defined in the ADD CXGRP command before being referenced
here.
[Subscriber number]
It specifies the long number of the WAC subscriber. Theoretically, the WAC subscriber
can be any subscriber. For example, local network subscriber, national subscriber, and
PLMN subscriber.
[Operator attrbiute]
It specifies whether the WAC subscriber is a local operator or a remote operator.
It specifies the extension number (short number) of the WAC subscriber in the Centrex
group. The Centrex short numbers must comply with the rule (number length and prefix)
for Centrex intra-group numbers, and the rule is defined in the ADD ICXPFX command.
When a Centrex subscriber in the local office dials the short number of a WAC
intra-group subscriber, the call processing software searches the long number of the
WAC subscriber according to the command configuration and then analyzes the call
prefix of the long number to complete the call connection.
When a WAC subscriber calls a Centrex subscriber in the local office through an
incoming trunk, use the command ADD CLRDSN (the function code is Judge caller
type) to discriminate the caller number in the incoming call to display the short number
of the WAC subscriber on the callees phone.
12.2.7 Adding a Batch of Wide Area Centrex Subscribers

I. Related commands
Command
Function
ADB WACSBR
To add a batch of wide area Centrex subscribers
RVB WACSBR
To remove a batch of wide area Centrex subscribers

12-27

Command
Function
MOB WACSBR
To modify a batch of wide area Centrex subscribers
LST WACSBR
To list a batch of wide area Centrex subscribers

Before adding a batch of WAC subscribers, use the related commands to get the
z
Centrex group number: LST CXGRP
Note:
Most of the parameters in ADB WACSBR are the same as those in ADD VSBR, so this
section only describes the dedicated parameters in ADB WACSBR. For other
[Start subscriber number] and [End subscriber number]

They are used to specify the range of the phone numbers (long numbers) of the batch
of the WAC subscribers. Theoretically, the WAC subscribers can be any type of
subscribers. For example, local network subscribers, national subscribers, and PLMN
subscribers.
[Start Centrex short number] and [Short number step]
They specify the start Centrex short number and the number increment for the batch of
Centrex subscribers in the resident Centrex group. The default value for Short number
step is 1.
12.3 Configuring ISDN Subscriber Data

12.3.1 Overview
ISDN subscriber data defines BRA subscribers and PRA subscribers that are managed
in the SoftX3000. To configure ISDN subscriber data, ensure that equipment data, local
12-28

office data, charging data, media gateway data, signaling data (when you are adding
BRA subscribers), and routing data (when you are adding PRA subscribers) has been
Start
Equipment data
Trunk data
Office data
Number analysis
Charging data
Subscriber data
MG data
Centrex data
MRS data
Call barring data
Protocol data
IN service data
Signaling data
Other service data
Routing data
Other application
data
End

For PRA subscribers, the SoftX3000 manages the call-in right, call-out right, charging
and route selection of PRA trunk group by controlling the call-in right, call-out right,
charging and route selection of the PRA subscriber (the default caller number)
corresponding to the PRA trunk group. Therefore, to configure PRA trunk related data,
make sure that PRA subscriber data has been configured.
During the configuration, some parameters defined in the equipment data, local office
data, charging data, media gateway data, signaling data, and routing data will be
referenced in the ISDN subscriber data, and some ISDN subscriber parameters will be
referenced when the PRA trunk data is configured. Table 12-4 shows the details.

12-29

Table 12-4 Parameter referencing relationship between ISDN subscriber data and
other data
Input parameter
Name
Output parameter
Defined in
Name
referenced in
Equipment data
PRA subscriber
number
PRA trunk data
Local DN set
Local office data
Call source code
Local office data
Charging data

code (optional)
Charging data
MG equipment ID
MG data
IUA link set index
IUA signaling data
Route selection code
Routing data
Module
number
FCCU/FCSU
of
II. Preparations
Before configuring the ISDN subscriber data, make sure that all preparations are done
as specified in Table 12-5.
SN
Item
Remark
Range of MG
equipment IDs
Used to determine the allocation plan of BRA

subscriber numbers
Subscriber number
allocation plan
Used to allocate a number for each MG termination ID
Subscriber attribute
planning
Includes subscriber category, call-in and call-out

rights, and charging class
Interface ID planning

SoftX3000 and embedded signaling gateway (when
you are adding BRA subscribers)

Table 12-6 lists the general steps for configuring the ISDN subscriber data.
Step
1
Description
Add ISDN data
Command
ADD ISDNDAT

12-30

Step
Description
Add BRA subscriber
Add PRA subscriber
Command
ADD BRA (to add a subscriber)
ADB BRA (to add a batch of subscribers)
ADD PRA

the ISDN subscriber data is configured.
ADD ISDNDAT
[Index]
[Transfer capability]
[Transfer speed]
ADD BRA
[Subscriber number]
[Local DnSet]
[ISDN data index]
ADD MSN
[Original telephone number]
[Multi-subscriber number]
[Local DnSet]
ADD PRA
[Telephone number]
[Route select code]
[ISDN data index]

12-31

12.3.2 Adding ISDN Data

I. Related commands
Command
Function
ADD ISDNDAT
To add ISDN data
RMV ISDNDAT
To remove ISDN data
MOD ISDNDAT
To modify ISDN data
LST ISDNDAT
To list ISDN data

The ISDN data is used to describe the transmission attributes and call attributes of
ISDN subscribers, including transfer capability, transfer speed, maximum number of B
channels, and call forward mode. Because 2B+D transmission is used for BRA
subscribers, but 30B+D transmission is used for PRA subscribers, you must define
different ISDN data for BRA subscribers and PRA subscribers respectively using ADD
ISDNDAT.

[Index]
It identifies a piece of ISDN data in the SoftX3000. Its value ranges from 0 to 99.
[Transfer capability]
One of the route selection conditions. It specifies the service types that the ISDN
subscriber can bear, for example, voice service, data service, and video service.
Generally, the value is set to All.
[Transfer speed]
It specifies the transfer speed that the ISDN subscriber can provide, including packet
rate, 64 kbit/s, 128 kbit/s and 1920 kbit/s. If there is no special requirement, it is set to
Multiple rate.
[Call forward mode]
It specifies the mode of notifying an ISDN subscriber of an incoming call by the system
if the ISDN subscriber has registered the call forwarding service. By default, it is set to
No. The options are
z
Subscriber receives the information of call forwarding: When any call to the ISDN
subscriber is forwarded, the system sends a corresponding notification message
to the subscriber.

12-32

Subscriber receives the information of call forwarding activation: When the ISDN
subscriber activates the call forwarding service, the system sends a

corresponding notification message to the subscriber.
Subscriber provides forwarded number: When any call to the ISDN subscriber is
forwarded, the system provides the forwarded-to number to the caller who must be
an ISDN subscriber, too. If the caller has the authority for call forwarded to inform
caller of the forwarded-to number, the selection of this option can make the caller
know whether the call is forwarded as well as the forwarded-to number.
[Call forwarded to inform caller]
It defines whether the system notifies the caller (also an ISDN subscriber) of the call
forwarding and the forwarded-to number. It is available only when the called ISDN
subscriber registers the call forwarding service. By default, it is set to No. The options
are
z
No: The system does not notify the caller of any call forwarding information.
Without call forwarding subscriber number: The system only notifies the caller of
call forwarding.
With call forwarding subscriber number: The system notifies the caller (also an
ISDN subscriber) of call forwarding and the forwarded-to number if Call forward
mode of the callee is set to Subscriber provides forwarded number.
[Maximum B channel]
It specifies the maximum number of B channels allowed for a call originated by an ISDN
subscriber. For BRA subscribers, set the value to 2 generally; for PRA subscribers, set
the value to 30 generally.
[Index of called party number]
It specifies the transform index of the called number when it is necessary to transform
the called number dialed by an ISDN subscriber. This index must be defined in the ADD
DNC command before being referenced here.
[Maximum call times]
It defines the maximum call times (including originated calls and received calls) allowed
for ISDN subscribers at the same time. The value must be larger than 2. Generally, it is
recommended to use the default value. For BRA subscribers, it is suggested to set the
parameter to 5; for PRA subscribers, it is suggested to set it to 20.
12.3.3 Adding a BRA Subscriber

I. Related commands
Command
Function
ADD BRA
To add a BRA subscriber
RMV BRA
To remove a BRA subscriber

12-33

Command
Function
MOD BRA
To modify a BRA subscriber
LST BRA
To list the configuration information of a BRA subscriber

Before adding a BRA subscriber (2B+D), use the related commands to get the following
parameters defined in the system.
1)
2)
3)
4)
5)
6)
IUA link set index: LST IUALKS
Note:
Most of the parameters in ADD BRA are the same as those in ADD VSBR, so this
section only describes the dedicated parameters in ADD BRA. For the other
[Subscriber number]
This parameter specifies the telephone number (default number) assigned to the BRA
subscriber. The specified number must be in the number segment defined in the ADD
DNSEG command. Except the PBX subscribers not occupying number resources, the
other subscribers must have a subscriber number.
[Local DN set]
This parameter specifies the local DN set to which the subscriber belongs. That is, it
analyzes all called numbers dialed by the subscriber. This parameter is defined in the
ADD LDNSET command and referenced here.
[Port type]
It specifies whether the BRA subscriber is an ordinary BRA subscriber or a V5 BRA
subscriber.
[Equipment ID]

12-34

This parameter is available only when an ordinary BRA subscriber is configured. It

specifies the equipment identification of the media gateway to which the BRA
subscriber belongs. This parameter is defined in the ADD MGW command and
referenced here.
[Termination ID]
specifies the physical port number assigned to the BRA subscriber in the media
gateway to which the BRA subscriber belongs. It only consists of digits and/or the
symbol "/". Set this parameter by the following principles:
z
Termination ID is 0 here, aaln/0 @ amg2.hauwei.com indicates physical interface
0 of the media gateway.

Each BRA subscriber occupies two equipment IDs, compliant with the rule: if what is
typed as the equipment ID is a number n, the equipment IDs actually occupied by the
BRA subscriber include n and n+1. Therefore, when you are configuring several BRA
subscribers, the incremental step must be 2.
[IUA linkset index]
specifies the IUA link set carrying BRA link messages (that is, D-channel signaling
messages of the BRA subscriber). This parameter is defined in the ADD IUALKS
[Interface ID]
This parameter is available only when an ordinary BRA subscriber is configured. It is
one of the interconnection parameters between the SoftX3000 and the embedded
signaling gateway supporting the IUA protocol. This parameter uniquely identifies a
BRA link from all BRA subscribers D-channel signaling messages that are carried over
the IUA link set.
For different BRA subscribers whose D-channel signaling messages are carried over
the same IUA link set, their corresponding interface IDs in the IUA link set cannot be the
same. To deploy a large number of BRA subscribers, plan the BRA link interface IDs in
advance.
[V5 interface ID]
This parameter is available only when a V5 BRA subscriber is configured. It specifies
the interface ID of the V5 AN device to which the BRA subscriber belongs. This
parameter must be defined in the ADD V5I command before being referenced here.
12-35

[L3 address]
This parameter is available only when a V5 BRA subscriber is configured. It identifies
the physical port address of the BRA subscriber in the V5 AN device. L3 address is the
address of the PSTN protocol or control protocol of EFaddr type in the layer-3
message.
z
port, and the valid address contains 15 bits, that is, a maximum of 32768 analog

This parameter is available only when a V5 BRA subscriber is configured, and the V5
AN device adopts V5.1 protocol. It specifies the timeslot in the 2.048 Mbit/s circuit to be
used fixedly by the B1 channel of the BRA subscriber.
This parameter is available only when a V5 BRA subscriber is configured, and the V5
AN device adopts V5.1 protocol. It specifies the timeslot in the 2.048 Mbit/s circuit to be
used fixedly by the B2 channel of the BRA subscriber.
[ISDN index]
It defines the ISDN data used by the BRA subscriber. It must be defined in the ADD
ISDNDAT command before being referenced here.
[ISDN features]
This parameter specifies the ISDN features of the BRA subscriber. The meanings of the
options are as follows:
1)
Network detection: It indicates whether the network side performs a validity check
on the caller number of a call that is originated from the subscriber side on the
BRA link, in other words, to judge whether that caller number is a BRA subscriber
number defined in the local office (whether that number can be found in the BRA
subscriber number data table of the local office). If so, the caller number is valid;
otherwise, the caller number is invalid.
If it is set to YES (the default value), the network side performs a validity check. If
the caller number is valid, the network side considers the caller number sent
through the BRA link as the caller number of the call. If the caller number is invalid,
the network side considers the BRA subscribers default number as the caller
number of the call.
12-36

If it is set to NO", the network side does not perform a validity check. The network
side always considers the caller number sent through the BRA link as the caller
number of the call.
2)
Point-to-multipoint configuration: It indicates whether the S interface of an NT2

device at the subscriber side can be connected to multiple terminal devices, such
as TE1 and TA. If it is set to YES, the NT2 can be connected to multiple terminal
devices. In this case, if the terminal devices share the same telephone number,
they are ringing simultaneously when the ringing tone is sent from the network
side to the subscriber side.
3)
Multi-subscriber number: It indicates whether the BRA subscriber has multiple

subscriber numbers. If it is set to YES, the BRA subscriber can have multiple
subscriber numbers. For the same U interface, the system allocates a maximum of
eight subscriber numbers. The numbers can either identify different terminals at
the same U interface or be shared by the same terminal.
By default, the BRA subscriber has the network detection and point-to-multipoint
configuration features. To configure the multi-subscriber-number feature for the BRA
subscriber, select the multi-subscriber number option for the subscriber.
[ISDN Ds logical C-channel ID]
the ID of the logical C-channel that bears the signaling message (Ds type) of the D
channel of the BRA subscriber. It must be defined by the command ADD V5I before
[ISDN P logical C-channel ID]
the ID of the logical C-channel that bears the packet signaling message (P type) of the
BRA subscriber. It must be defined by the command ADD V5I before being referenced
here.
[ISDN F logical C-channel ID]
the ID of the logical C-channel that bears the frame relay signaling message (F type) of
the BRA subscriber. It must be defined by the command ADD V5I before being
referenced here.
12.3.4 Adding a Batch of BRA Subscribers

I. Related commands
Command
Function
ADB BRA
To add a batch of BRA subscribers
RVB BRA
To remove a batch of BRA subscribers

12-37

Command
Function
MOB BRA
To modify a batch of BRA subscribers
LST BRA
To list a batch of BRA subscribers

Before adding a batch of BRA subscribers, use the related commands to get the
1)
2)
3)
4)
5)
6)
IUA link set index: LST IUALKS

Most of the parameters in the ADB BRA command are the same as those in the ADD
VSBR command. This section only presents the special parameters in the ADB BRA
command. For the detailed information about other parameters, see Section 12.3.3
Adding a BRA Subscriber in this chapter.
subscribers. The numbers in this range must be in the number segment defined in the
ADD DNSEG command.
[Local DN set]
[Port type]
It specifies whether the batch of subscribers are BRA subscribers or V5 BRA
subscribers.
[Equipment ID]
This parameter is available only when ordinary BRA subscribers are configured. It
specifies the equipment ID of the MG to which the batch of BRA subscribers are

12-38

connected. This parameter must be defined in the ADD MGW command before being
referenced here.
[IUA linkset index]
This parameter is available only when ordinary BRA subscribers are configured. It
specifies the IUA link set carrying BRA link messages (that is, D-channel signaling
messages of the BRA subscriber). This parameter is defined in the ADD IUALKS
[Start interface ID] and [Interface ID step]
The parameters are available only when ordinary BRA subscribers are configured.
They are used to specify the start interface ID and the ID increment for the D-channel
signaling messages of the batch of the BRA subscribers in the corresponding IUA link
set. The default value for Interface ID step is 1.
[Start MG termination ID] and [MG termination ID step]
The parameters are available only when ordinary BRA subscribers are configured.
They are used to specify the start terminal number and the number increment
difference for the batch of the BRA subscribers in the media gateway to which the
subscribers belong. The default value for MG termination ID step is 2.
[V5 interface ID]
The parameter is available only when V5 BRA subscribers are configured. It specifies
the interface ID of the V5 AN device to which the BRA subscribers belongs. This
parameter must be defined in the ADD V5I command before being referenced here.
[Start L3 address] and [L3 address step]
The parameters are available only when V5 BRA subscribers are configured. They are
used to specify the start L3 address and address value difference of the batch of BRA
subscribers in the resident V5 AN device. The default value for L3 address step is 1.
[Start V51 B1 circuit number] and [V51 B1 circuit number step]
used to specify the start timeslot number and the timeslot number increment difference
of the 2.048 Mbit/s link used by the B1 channel of the batch of BRA subscribers. The
default value for V51 B1 circuit number step is 1.
[Start V51 B2 circuit number] and [V51 B2 circuit number step]
used to specify the start timeslot number and the timeslot number increment difference
of the 2.048 Mbit/s link used by the B2 channel of the batch of BRA subscribers. The
default value for V51 B2 circuit number step is 1.

12-39

They are used to specify the start Centrex short number and the number increment for
the batch of the Centrex subscribers in the resident Centrex group. They are available
when Centrex flag is Yes. The default value for Short number step is 1.
[ISDN index]
It defines the ISDN data used by the BRA subscriber. It must be defined in the ADD
12.3.5 Adding a PRA Subscriber

I. Related commands
Command
Function
ADD PRA
To add a PRA subscriber
MOD PRA
To modify a PRA subscriber
RMV PRA
To remove a PRA subscriber
LST PRA
To list the configuration information of a PRA subscriber

During the configuration, the following two supplementary service authorities of the
PRA subscriber greatly affect the Calling Line Identification Presentation (CLIP) service
of the PRA trunk group.
z
If the opposite office sends subscriber number instead of national significant

number as the called number to the local office, the Direct Dialing-In (DDI)
authority must be enabled for the PRA subscriber.
If the local office is required to provide the caller number to the opposite office, the
CLIP authority must be enabled for the PRA subscriber.

[Subscriber number]
It specifies the subscriber number assigned to the subscriber. The specified number
must be in the number segment defined in the ADD DNSEG command.
[Local DN set]
called numbers dialed by the subscriber. This parameter is defined in the ADD
LDNSET command and referenced here.
It defines the route selection code for outgoing calls of the system. This parameter is
defined in the ADD RTANA command and referenced here.
12-40

As you know, a default caller number (PRA subscriber number) must be specified in the
definition of a PRA trunk group in the ADD PRATG command. To ensure that the
system can select an appropriate PRA trunk group for outgoing purposes, the route
selection code parameter (defined in this command) used by that default caller number
must be set to the same value as route selection code used by the outgoing call prefix
(defined in the ADD CNACLD command) through that PRA trunk group. Otherwise, the
system might fail to route.
[ISDN data index]
It specifies the ISDN data used by the PRA subscriber. It must be defined in the ADD
It specifies the module number of the FCCU or FCSU at the SoftX3000 side processing
the PRA subscriber call. Its value ranges from 22 to 101. This parameter must be
defined in the ADD BRD command before being referenced here.
command ADD MGW for adding the MG providing PRA trunks; otherwise, the PRA
subscriber terminal subject to the MG cannot work normally.
[Call source code]
command ADD CHGGRP or ADD CHGIDX before being referenced here. For the
detailed information about charging, see Chapter 4, Configuring Charging Data, in
this manual.
It should be noted that the charging of a PRA trunk group is actually implemented by
charging its default caller number (that is, PRA subscriber number).
[Subscriber type]
z


12-41

z

(including operators) are not allowed to insert or release their calls.
Test: It is applicable to test subscribers. Only test subscribers or operators can use
[Call out password]

It defines the initial call-out password used when the subscriber registers outgoing
restricted supplementary service. The password contains four decimal digits and the
default password is 1000. The subscriber can modify this password on a phone set.
It specifies the call barring group to which the subscriber belongs. The configuration
principle is described as follows.
z
enabled.
can be referenced directly, that is black list 60001, white list 60002 and ordinary
If the other call barring groups are used, this parameter must be defined in the
It should be noted that the call barring group number can be used for both time-based
call barring and inter-group call barring. Meanwhile, inter-group barring is prior to
time-based barring, that is, the system first judges whether to implement inter-group
barring and then whether to implement time-based barring. The SoftX3000
authenticates inter-group call barring twice for the call prefix, and the caller and callee
sides during the number analysis process. To use the function correctly and avoid
mistakes, read the following inter-group call barring procedure:
1)
2)


12-42

originated by the subscriber for query. The default value is No. If a subscriber
questions a bill, you can set this parameter to Yes.
ADD CHGCLD command before being referenced here. The default value is 255,
indicating that called charging is not conducted. For the detailed information about
charging, see Chapter 4, Configuring Charging Data, in this manual.
[Charging type]
It specifies the charging category used for the subscriber. The default value is Period.
The options are
z
Period: The system charges the subscribers periodically (for example, every
month) instead of for each call.
charging of unattended public phones.
Free: This option is applicable for the calls that are determined to be free for the
calling subscriber by the service analysis, such as commonweal phone, alarm
phones and free phones. For the Free calls, the system still records the detailed
call information of the calling subscriber to generate free free detailed bill.
[Centrex group flag]

It indicates whether the subscriber is a Centrex subscriber. Select "No for ordinary
subscribers, and Yes for Centrex subscribers.
It specifies the number of the Centrex group to which the subscriber belongs. This
parameter is available when "Centrex flag is Yes. This parameter must be defined in
the ADD CXGRP command before being referenced here.
It specifies the extension number (short number) of the subscriber in the Centrex group.
This parameter is available when "Centrex flag is Yes. The Centrex short numbers

12-43

must comply with the rule for Centrex intra-group numbers, and the rule is defined in
the ADD ICXPFX command.
[Call replace]
It specifies the number of the call pickup group in the Centrex group for the subscriber.
This parameter is available when Centrex flag" is set to Yes. Its value ranges from 0
to 255, and the value 255 indicates that the setting is invalid.
[Call-in authority]
It defines the call-in authorities of the subscriber, including intra-office, local, local toll,
application). The system enables all call-in authorities of the subscriber by default.
It should be noted that the call-out rights of the PRA trunk group are controlled based on
the call-in rights of its default caller number (that is, PRA subscriber number).
It defines the call-out authorities of the subscriber, including intra-office, local, local toll,
application). By default, the system enables all call-out authorities of the subscriber
except national toll, international toll, intra-office national toll and intra-office
international toll.
It should be noted that the call-in rights of the PRA trunk group are controlled based on
the call-out rights of its default caller number (that is, PRA subscriber number).
[Supplementary service authority]
It defines the supplementary service authorities of the subscriber. By default, the
subscriber has no supplementary service authorities.
When the subscriber is a Centrex group subscriber, the supplementary service
authorities cannot be higher than Console supplementary service defined in this
command.
12.4 Configuring Other Subscriber Data

12.4.1 Adding Multi-Subscriber Number
I. Related commands
Command
Function
ADD MSN
To add multi-subscriber number
RMV MSN
To remove multi-subscriber number
LST MSN
To list multi-subscriber number

12-44


Multi-subscriber number means that the system can allocate several telephone
numbers to one subscriber line. For ESL subscribers, it allows one terminal to have
several numbers. For BRA subscribers, it supports the multi-subscriber-terminal
function of the TA adapter. The number allocated to a subscriber line using ADD VSBR
or ADD BRA is called the original number, and the number allocated to the subscriber
line using ADD MSN is called multi-subscriber number.

[Original subscriber number]
This parameter specifies the telephone number allocated to a subscriber through the
command ADD VSBR or ADD BRA in a multi-subscriber-number application.
[Multi-subscriber number]
This parameter specifies the multi-subscriber number used by a subscriber. It must be
in the number segment defined in the ADD DNSEG command. Note the following:
z
For one ESL subscriber line, you can only set one multi-subscriber number for it,
and this number is valid only when the subscriber acts as the callee. That is, the
ESL subscriber can have two telephone numbers simultaneously and the calls to
any of them can be connected. When this ESL subscriber originates a call, the call
processing software only analyzes and connects the original subscriber number.
For one BRA subscriber line, you can set several multi-subscriber numbers. When
the TA adapter has several analog subscriber line interfaces, you can allocate
multi-subscriber numbers to these interfaces. When other subscribers call one of
these multi-subscriber numbers, the TA sends the ringing current to the
corresponding analog subscriber line interface. If it is required to set the
multi-subscriber-number function for a BRA subscriber line, you need to add the
default number for the BRA subscriber first using ADD BRA, and at the same time
select Multi-subscriber number for the parameter ISDN function in the
command.
[Local DN set]
This parameter specifies the local DN set to which the multi-subscriber-number
subscriber belongs. That is, it indicates the local DN set in whose number analysis table
the call processing software analyzes all called numbers dialed by the
multi-subscriber-number subscriber. This parameter is defined in the ADD LDNSET
[Centrex flag]
This parameter specifies whether the multi-subscriber-number subscriber is a Centrex
subscriber. Select No for ordinary subscribers, and Yes for Centrex subscribers.

12-45

When the Centrex flag parameter is set to Yes, this parameter is available to specify
the number of the Centrex group to which the multi-subscriber-number subscriber
belongs. This parameter is defined in the ADD CXGRP command and referenced here.
When the Centrex flag parameter is set to Yes, this parameter is available to specify
the extension number of the Centrex group to which the multi-subscriber-number
subscriber belongs. What is typed in this parameter must comply with extension
numbering rules (regarding number length and prefix) of the Centrex group. The
extension numbering rules are defined in the ADD ICXPFX command.
12.4.2 Setting String of Anonymous Card Flag

I. Related commands
Command
Function
ADD SOCF
To add string of anonymous card flag
RMV SOCF
To remove string of anonymous card flag
MOD SOCF
To modify string of anonymous card flag
LST SOCF
To list string of anonymous card flag

If the local SoftX3000 serves as an SSP in IN, the command ADD SOCF is used to
support the anonymous card calling service on the SIP soft terminal (for example,
OpenEye of Huawei). The anonymous card calling service allows an SIP soft terminal
on which a card number call is originated to occupy no E.164 number resources of the
network. That is, the SIP soft terminal can be a non-registered subscriber in NGN.
In the traditional card calling service, the SSP first authenticates the local caller or the
incoming trunk originating the call when analyzing the access code of the card calling
service. If the local caller has the valid telephone number or the call is originated from
the incoming trunk, the authentication succeeds and the SSP triggers the IN service.
Otherwise, the authentication fails and the SSP does not trigger the IN service.
Because the SIP soft terminal on which an anonymous card call is originated does not
occupy any E.164 number resources of the network, the SSP rejects the call if no
special processing is made to the call according to the call processing procedure of the
SSP. To support the anonymous card calling service when serving as an SSP, the
SoftX3000 simulates a card call originated on an SIP soft terminal as an SIP incoming
trunk call, and authenticates String of Card Flag sent by the SIP soft terminal to avoid
malicious calls.

12-46


[String of card flag]
It is one of the parameters for the SoftX3000 to interwork with the SIP soft terminal. It
specifies the string of card flag used to authenticate an anonymous card call originated
on an SIP soft terminal, for example, PureCard. This string is sent by the SIP soft
terminal to the SoftX3000 through an SIP message. Both parties should negotiate it to
ensure the consistency; otherwise, the call fails.
In the anonymous card calling service, the SoftX3000 simulates a card call originated
on an SIP soft terminal as an SIP incoming trunk call. This parameter specifies the
number of this SIP trunk group. It must be defined in ADD SIPTG before being
referenced here.

12-47

Chapter 13 Configuring Centrex Data

13.1.1 Centrex Prefix and Centrex Out-Group Prefix
The call processing software in the SoftX3000 analyzes numbers dialed by a Centrex
subscriber differently from those dialed by an ordinary subscriber. For an ordinary
subscriber, the SoftX3000 provides only one number analysis table. That is, the call
processing software in the SoftX3000 analyzes all numbers dialed by the ordinary
subscriber in that table. For a Centrex subscriber, the SoftX3000 provides two number
analysis tables, namely, intra-group number analysis table and out-group number
analysis table. The out-group number analysis table is the same as the number
analysis table used for an ordinary subscriber. The call processing software determines
the specific table to be used by judging the prefix dialed by the Centrex subscriber.
I. Centrex prefix
If what is dialed is a Centrex prefix, the Centrex prefix invokes the intra-group number
analysis table. The functions of a Centrex prefix are as follows:
z
Enables subscribers in the same group to make calls to each other. You can set
this prefix according to actual situations.
Enables WAC access. You can set this prefix according to actual situations.
Enables subscribers in the group to use supplementary services. Because the

initial prefix of a supplementary service usually begins with the asterisk sign * or
the pound sign #, such a configuration avoids the conflict with the out-group
prefix. During initialization, the SoftX3000 presets the prefixes of various
supplementary services for all Centrex groups (indicated by the wildcard character
65534). These prefixes can be used by all Centrex groups. You can modify them
using MOD ICXPFX as needed.
Enables subscribers in the group to originate emergency calls. Subscribers can

originate outgoing calls by directly dialing the specific number for a special service,
such as the fire emergency service, so as not to alter the widely accepted
practices for the special service. In this case, the call processing software
analyzes the call based on the intra-group number analysis table first of all. When
the call is judged to be an emergency call, the call processing software transfers it
to the out-group number analysis table for further processing.
Enables the access of Wide Area Centrex (WAC).

13-1

II. Centrex out-group prefix

If what is dialed is a Centrex out-group prefix, the Centrex out-group prefix invokes the
out-group number analysis table, that is, the number analysis table for an ordinary
subscriber. The functions of a Centrex out-group prefix are as follows:
z
Enables subscribers in the group to originate calls to other subscribers in the local
office, such as local calls, national toll calls within the local office, and international
toll calls within the local office.
Enables subscribers in the group to originate outgoing calls, such as local toll calls,
national toll calls, and international toll calls.
13.1.2 IP Console and IP Supermarket

I. IP console
An IP console refers to a multimedia computer installed with a network adapter and a
sound card, which achieves the remote access of the console through the IP network to
provide intra-Centrex call transfer, subscriber management and charging functions.
U-Path is an IP console product of Huawei and is a key element in the Huawei NGN IP
Centrex solution. U-Path communicates with the SoftX3000 through a private protocol,
and it is equivalent to an MGCP soft terminal.
II. IP supermarket
An IP supermarket refers to the IP toll call service deployed by telecommunication
carriers or telephone business outlets that are authorized to provide public telephone
service. The SoftX3000 provides the IP supermarket service in the IP Centrex manner.
Through IP console, the subscribed telephones in the IP supermarket business hall are
charged and managed.
13.2 Configuring Centrex Data

13.2.1 Overview
Centrex data defines configuration information related to the IP Centrex service, such
as Centrex group information, Centrex group charging information, Centrex prefix, and
IP console information. To configure Centrex data, the equipment data, office data and
charging data must have been configured. There is no compelling configuration
sequence rule between Centrex data and subscriber data, but it is recommended to
configure subscriber data before Centrex data. See Figure 13-1.
13-2

Start
Equipment data
Trunk data
Office data
Number analysis
Charging data
Subscriber data
MG data
Centrex data
MRS data
Call barring data
Protocol data
IN service data
Signaling data
Other service data
Routing data
Other application
data
End

you configure equipment data, office data and charging data will be referenced during
the configuration of Centrex data. Some parameters defined here will be referenced
during the configuration of subscriber data. The referencing relationship is presented
as the broken lines in Figure 13-1. For the parameter referencing relationship between
Centrex data and other data, see Table 13-1.
Table 13-1 Parameter referencing relationship between Centrex data and other data
Input parameter
Name
Output parameter
Defined in
Name
Referenced in
IP address of FE
port
Equipment
information
Centrex
number
FCCU/FCSU
module number
Equipment
information
Short number
Centrex group
Local DN set
Office data
Charging source
code
Charging data

13-3
group
in
Subscriber data
Subscriber data

Input parameter
Name
Charging
(optional)
Output parameter
Defined in
case
Charging data
Name
Referenced in
Note:
If Centrex data is configured before subscriber data, Centrex group number and
Centrex short number will be referenced by subscriber data in the ADD VSBR,
ADB VSBR and ADD MSBR commands.
If Centrex data is configured after subscriber data, Centrex group number and
Centrex short number will be referenced by subscriber data in the MOD VSBR,
MOB VSBR and MOD MSBR commands.
II. Preparations
Before configuring Centrex data, make sure that all preparations are done as specified
in Table 13-2.
SN
Item
Remark
Centrex group number
Used to identify a Centrex group
Centrex subscriber capacity
Planned in advance
Intra-Centrex numbering plan
Including prefix and length in bits for

subscribers in the group
Centrex out-group prefix
Usually 0 or 9 is selected as the out-group

prefix
Whether or not to charge

intra-Centrex calls
Not to charge usually.
IP console number

between the SoftX3000 and the IP console
IP address of IP console

User name and password for

IP console to register to the
SoftX3000


13-4


Table 13-3 lists the general steps for configuring Centrex data.
Step
Description
Command
Add Centrex group
ADD CXGRP
Add Centrex intra-group prefix
ADD ICXPFX
Add Centrex out-group prefix (optional)
ADD OCXPFX
Add Centrex prefix special processing (optional)
ADD CXPFXPRO
Add Centrex intra-group charging (optional)
ADD CHGCX
Add Centrex out-group authority (optional)
ADD CXOCR
Add Centrex group abbreviated dialing (optional)
ADD CXSD
Set local IP address for Controlling console
SET CONADDR
Add Centrex console
ADD CXCON
10
Add ISDN Centrex console
ADD ISDNCON
11
Modify Centrex group (optional)
MOD CXGRP

during the configuration of Centrex data.

13-5

ADD CXGRP
ADD FECFG
[Centrex group name]
[IFM Module]
[IP address]
[Out-group prefix]
[Mask address]
SET CONADDR
ADD ICXPFX
[Console local IP]

[Centrex call prefix]
ADD CXCON
ADD OCXPFX
[Centrex group
name]
[Out-group prefix]
MOD CXGRP
ADD CHGCX
[Centrex group
name]
[Charging case]
[Capacity]
13.2.2 Adding Centrex Group

I. Related commands
Command
Function
ADD CXGRP
To add Centrex group
RMV CXGRP
To remove Centrex group
MOD CXGRP
To modify Centrex group
LST CXGRP
To list Centrex group


13-6

It uniquely identifies a Centrex group in the SoftX3000. In certain MML commands, you
can reference a Centrex group by either its group name or its group number. A Centrex
group cannot be referenced by both its group name and its group number at the same
time; otherwise, errors will occur.
It uniquely identifies a Centrex group. A maximum of 65534 Centrex groups can be
configured in the SoftX3000. The numbering range is 0 to 65533.
Because the maximum number of tuples is limited in the host database, the maximum
number of Centrex groups that you can configure actually is less than 65534. To modify
the maximum number of tuples in the host database, contact Huawei technical support
engineers for help. Do not modify it by yourself.
[Out-group prefix]
It defines the prefix to be dialed by subscribers in the Centrex group to originate
outgoing calls. It can be presented in one or two digits only.
When you add a Centrex group using ADD CXGRP, the system generates an internal
digit map for this Centrex group automatically. This digit map contains the digit
collection mode corresponding to the out-group prefix. When a Centrex subscriber
picks up the phone, the SoftX3000 sends the intra-group digit map to the subscriber
resident MG first through a control message. After the subscriber dials the out-group
prefix, the MG immediately reports it to the SoftX3000. Upon receiving the prefix, the
SoftX3000 sends to the MG the digit map of the local DN set to which the MG belongs,
in order to instruct the MG to continue collecting digits in the new mode.
[Second dial tone]
It specifies whether or not to play the secondary dial tone to subscribers in the Centrex
group after they dial the out-group prefix. To enable the Centrex subscribers to hear the
secondary dial tone, you need to set this parameter to Yes, and the "Pre-received
digits of the call source of the Centrex subscribers (which can be modified by MOD
CALLSRC) cannot be greater than the length of the Centrex out-group prefix.
[Capacity]
It defines the maximum number of subscribers supported by the Centrex group. The
value range is 0 to 32767, that is, the maximum subscriber capacity is 32767.
[Internal ringing]
It defines the ringing mode when there is a call from a subscriber in the same Centrex
group. That is, the SoftX3000 controls the ringing current sent by the MG to the called
phone set. Available options are as follows:
z
Normal: ringing for 1 second, then no ringing for 4 seconds;

13-7

Special: ringing for 1 second, then no ringing for 2 seconds;
Hongkong: ringing for 4 seconds, no ringing for 2 seconds, then ringing for 4
seconds, no ringing for 4 seconds;
Long: keep ringing;
FSK: ringing for 1 second, then no ringing for 4 seconds. The FSK signal of the
caller number is sent to the called phone set between the first ringing tone and
second ringing tone. That is, the caller number is displayed on the phone set of the
callee.
It should be noted that the implementation of the selected ringing mode depends on the
hardware support from the associated media gateway device or V5 access network
device.
[External ringing]
It defines the ringing mode when there is a call from a subscriber outside the Centrex
group. The meanings of the options are the same as those for inter ringing.
[Delete out-group prefix]
It specifies whether or not the call processing software deletes the out-group prefix
before analyzing the called number dialed by a Centrex subscriber or when a call detail
record (CDR) is generated. By default, it is Yes. That is, the out-group prefix will be
deleted. If it is set to No, the out-group prefix will appear during number analysis and
in the CDR.
[WAN Centrex]
It specifies whether or not the Centrex group supports the IN WAC functions.
[WAN access code]
When the SoftX3000 needs to trigger the WAC services in IN mode, this parameter is
available to define the access code that the SoftX3000 inserts before the WAC short
number dialed by a Centrex group subscriber. The implementation of the WAC
functions requires the support from an IN service platform. That is, the mapping
between long and short numbers of all subscribers in the WAC group is stored in the
database of the IN service platform. The following describes the basic procedures for
the SoftX3000 to trigger the WAC services in IN mode.
Suppose that the prefix of a Centrex group is 2, short number length is 4, and the
number segment plan is as follows: 20XX26XX is allocated to the local Centrex
group subscribers (subscriber data need be set); 27XX29XX is allocated to the WAC
group subscribers (no subscriber data can be set). When a local intra-Centrex
subscriber dials a short number 2XXX, the call processing software first searches this
short number in the subscriber data table, and then determines the subsequent number
analysis procedure according to the search result.

13-8

z
If this short number (for example, 2199) exists in the subscriber data table, it
means that the callee is a local Centrex group subscriber, and the call processing
software will connect the call based on the corresponding procedure.
If this short number (for example, 2799) does not exist in the subscriber data table,
it means that the callee is a WAC group subscriber, and the call processing
software will insert the WAC access code before the short number automatically,
and then re-analyze it. In terms of the WAC access code, the call processing
software of the SoftX3000 will trigger a WAC IN service, and then the IN service
platform will analyze the short number based on the long-to-short number
mapping table.
[Forward charge not record in console]

When outgoing calls made by Centrex subscribers are forwarded by the console of this
Centrex group, this parameter specifies whether the SoftX3000 charges this console.
z
By default, it is set to No, indicating that forward charges are paid by the Centrex
subscribers. That is, the charged number in a bill is a Centrex subscriber number.
If it is set to Yes, the forward charges are counted on the console. That is, the
charged number in a bill is the console number.
[IP market flag]

It specifies whether or not the Centrex group is used for the IP supermarket service. By
default, it is set to No, indicating that the Centrex group is not used for the IP
supermarket service and thus the IP console (U-Path) for the Centrex group starts the
ordinary console software. If it is set to YES, the IP console for the Centrex group must
start the IP supermarket software.
[IP market out control flag]
When the IP supermarket is offline, the parameter specifies whether the SoftX3000
restricts outgoing calls from Centrex subscribers in the IP supermarket. It is available
only when IP market flag is Yes. The default value is No, indicating not to restrict. If
the parameter is set to "Yes, Centrex subscribers in the IP supermarket cannot call out
when the IP supermarket is offline.
[Centrex name]
It identifies a Centrex group with a string of 32 characters at most. Centrex name is
different from Centrex group name. Centrex group name is used in the software only
and it is invisible for terminal users; while Centrex name is used for the caller name
display service and it is visible for terminal users.
[Centrex name valid]
When a Centrex subscriber calls an out-group subscriber who has registered the caller
name display service, this parameter indicates whether the SoftX3000 sends the

13-9

Centrex name (masking the real name of the Centrex subscriber) to the out-group
subscriber.
z
By default, it is set to No, indicating that the real caller name of the Centrex
subscriber is displayed on the out-group subscribers phone set.
If it is set to Yes, the name of the caller resident Centrex group is displayed on the
out-group subscribers phone set.
When a Centrex subscriber calls another Centex subscriber, the real name of the caller
is always displayed on the callees phone set.
[Centrex CFNR timer]
When a subscriber calls a Centrex subscriber who has registered the CFNR service,
this parameter specifies the ringing duration after which the SoftX3000 forwards the call.
Its value ranges from 12 to 30 in unit of second. By default, it is set to 16.
[Out-group prefix display]
When a Centrex subscriber calls an out-group subscriber who has registered the CLIP
service, this parameter indicates whether the SoftX3000 sends the out-group prefix
(that is, adding the out-group prefix before the long number of the Centrex subscriber)
to the out-group subscriber. By default, it is set to "No.
[Key system flag]
It specifies whether the Centrex group supports the Key system service, that is,
whether the status subscription function of Centrex subscribers is supported. The
default value is No. To enable the Key system service, you must set bit 8 of internal
parameter 7 (P121) to 0 by executing the command MOD FSFP and the Key system
flag" of the Centrex group to Yes .
13.2.3 Adding Centrex Intra-Group Prefix

I. Related commands
Command
Function
ADD ICXPFX
To add Centrex intra-group prefix
RMV ICXPFX
To remove Centrex intra-group prefix
MOD ICXPFX
To modify Centrex intra-group prefix
LST ICXPFX
To list Centrex intra-group prefix

13-10

It specifies the name of the Centrex group for which the Centrex prefix is to be set. It is
defined in the ADD CXGRP command and referenced here.
In this command, you can reference a Centrex group by either its group name or its
group number, but you cannot reference a Centrex group by both parameters at the
same time; otherwise, errors will occur.
It specifies the group number of the Centrex group for which the Centrex prefix is to be
set. 65534 is a wildcard character and can indicate all Centrex groups. When it
indicates a specific Centrex group, this parameter must have been defined in the ADD
CXGRP command before being referenced here.
[Centrex call prefix]
It defines the Centrex prefix. You need to set the Centrex prefix only in the following
cases:
z
Defining the initial prefix for the Centrex short numbers. For example, if the short
numbers of a Centrex group are designed as 2XXX, you need to set the intial
prefix of short numbers to 2.
Defining emergency call prefixes. To keep the speical service numbers unchanged,
you need to define these prefixes as emergency call prefixes. In this case, Centrex
subscribers need not dial the out-group prefix additionally before dialing the
emergency service numbers.
Defining supplementary service prefixes. Although the SoftX3000 has preset the
prefixes of various supplementary services during initialization for all Centrex
groups (indicated by the wildcard character 65534), some prefixes may not
conform to the practices of the carriers. To simplify the prefix configuration, you
can define some supplementary service prefixes for a Centrex group separately,
the priority of which is higher than that of the supplementary service prefixes of
65534.
Defining WAC access code. For the WAC functions that can be implemented
through regular number change, you need to define the intial prefix as the WAC
access code. Suppose a company registers the Centrex services in both areas A
and B, the Centrex services in the two areas are provided by two offices separately,
the short numbers of area B are designed as 3XXX and the long numbers of area
B are designed as 8783XXX. In this case, office A can define 3 as the WAC
access code, and then convert 3XXX to 8783XXX to achieve WAC functions.
When you add a Centrex prefix using ADD ICXPFX, the system modifies the internal
digit map of this Centrex group automatically. This digit map contains the digit collection
mode corresponding to the Centex prefix defined here. When a Centrex subscriber
picks up the phone, the SoftX3000 sends the intra-group digit map to the subscriber
resident MG through a control message. If the initial prefix dialed by the subscriber is

13-11

not the out-group prefix, the MG continues to collect digits in the mode defined by the
intra-group digit map until the requirement is met.
[Service attribute]
It specifies the steps for the call processing software to analyze a Centrex prefix. Set
z
For a Centrex short number prefix, select CIG(Intra-Centrex).
For the access code of a WAC whose functions are achieved through regular
number change, select CWA(Centrex WAN access code). At the same time, you
must define number change index in the command. The implementation of the
WAC functions in this mode requires no support from an IN service platform. The
SoftX3000 matches and finds short numbers and long numbers for subscribers in
the WAC group through number change.
For supplementary service prefix, select an appropriate option according to the

actual requirement.
For emergency call prefix, select EMCOUT(Out-group emergency call).
For PBX group prefix, select PIC(PBX Intra-Centrex).
Note:
The SoftX3000 has preset the prefixes of various supplementary services during
initialization for all Centrex groups (indicated by the wildcard character 65534). The
preset prefix table serves all Centrex groups, but with the lowest priority. That is, during
a number analysis procedure, the customized Centrex prefix table dedicated to the
Centrex group is searched first; when no matching item is found, the preset prefix table
in the system is searched.
[Minimum number length], [Maximum number length]

These parameters specify the minimum and maximum number lengths for the Centrex
prefix. For intra-Centrex short number prefix, the minimum and maximum number
lengths must be the same, ranging from one to eight digits. In addition, when the
Centrex prefix is a supplementary service prefix, the wildcard character 65534 can
indicate all Centrex groups if you need to modify all Centrex prefixes. To modify the
prefix of one Centrex group, enter the specific Centrex group number or name.
When the service attribute is CWA(Centrex WAN access code)", this parameter is
available to specify the number change index to be referenced by the prefix. It is
defined in the ADD DNC command and referenced here.

13-12

[Local DN set]
This parameter is available only when the service attribute is PIC(PBX Intra-Centrex),
defining the local DN set to which the PBX group prefix belongs. It must be defined in
ADD LDNSET before being referenced here.
[PBX pilot number]
defining the PBX pilot number corresponding to the PBX group prefix. It must be
defined in ADD PBX before being referenced here.
The basic procedure of PBX group calls is as follows:
1)
Suppose the source PBX supports the function of automatically inserting the
outgoing prefix of PBX group calls. When an extension of the source PBX calls an
extension of the destination PBX, the source PBX will send outgoing prefix of
PBX group calls + destination PBX extension number to the SoftX3000 through
the connected IAD.
2)
Upon receiving the destination PBX extension number sent the source PBX, the
SoftX3000 analyzes it in the prefix table of the corresponding Centrex group. If the
prefix of the destination PBX extension number can match with a PBX group prefix
defined in the command, the SoftX3000 will originate a call automatically to the
destination PBX pilot number.
3)
After a subscriber line to which the destination PBX pilot number belongs rings,
the destination PBX plays an announcement to the IAD connected with the source
PBX through the IAD or plays the dial tone directly.
4)
After the SoftX3000 delays the PBX announcement duration defined in the
command, it will instruct the IAD connected with the source PBX to send the
destination PBX extension number to the destination PBX in DTMF mode through
an MGCP message (carrying the destination PBX extension number).
5)
After receiving the PBX extension number, the destination PBX rings the
destination PBX extension. The call is connected after the callee picks up the
phone.
[PBX announcement duration]

defining the duration of the announcement played by the PBX equipment. It ranges
from 0 to 30 in unit of second. The default value is 5. For the specific purposes of this
parameter, refer to the above explanation.

13-13

13.2.4 Adding Centrex Out-Group Prefix (Optional)

I. Related commands
Command
Function
ADD OCXPFX
To add Centrex out-group prefix
RMV OCXPFX
To remove Centrex out-group prefix
MOD OCXPFX
To modify Centrex out-group prefix
LST OCXPFX
To list Centrex out-group prefix

data configuration.
Usually, the Centrex out-group prefix is defined before you add a Centrex group with
the ADD CXGRP command, and thus this step is unnecessary. However, in certain
cases, you can add a new Centrex out-group prefix by using the ADD OCXPFX
command. For example:
Short numbers in a Centrex group are 2xxx and the Centrex out-group prefix is 9.
Accordingly, Centrex subscribers must dial 9 first to originate outgoing calls no matter
which type of prefix with which the called number starts. That may cause much
inconvenience. If Centrex subscribers do not want to dial 9 to originate calls to the local
telephone numbers started with an integer from 3 to 8 or to toll calls, you can add the
Centrex out-group prefix to those called numbers by using the ADD OCXPFX
command. However, in this case, the Delete out-group prefix parameter in the
command must be set to No.

It specifies the name of the Centrex group for which the Centrex out-group prefix is to
be set. It is defined in the ADD CXGRP command and referenced here.
It should be noted that, in this command, the Centrex group can be referenced by either
its group name or its group number. The Centrex group cannot be referenced by both at
the same time; otherwise, errors will occur.
It specifies the group number of the Centrex group for which the Centrex out-group
prefix is to be set. 65534 is a wildcard character and can indicate all Centrex groups.
13-14

When it indicates a specific Centrex group, this parameter must have been defined in
the ADD CXGRP command before it is referenced here.
[Out-group prefix]
It defines the prefix to be dialed by subscribers in the Centrex group to originate
outgoing calls. It can be presented in one or two digits only. The out-group prefix
defined here must be consistent with that defined in the command ADD CXGRP.
[Second dial tone]
It specifies whether or not to play the secondary dial tone to subscribers in the Centrex
group after they dial the out-group prefix. To enable the Centrex subscribers to hear the
secondary dial tone, you need to set this parameter to Yes, and the "Pre-received
digits of the call source of the Centrex subscribers (which can be modified by MOD
CALLSRC) cannot be greater than the length of the Centrex out-group prefix.
[Delete out-group prefix]
It specifies whether or not the call processing software deletes the out-group prefix
before analyzing the called number dialed by a Centrex subscriber or when a CDR is
generated. By default, it is Yes. That is, the out-group prefix will be deleted. If it is set
to No, the out-group prefix will appear during number analysis and in the CDR.
13.2.5 Adding Centrex Prefix Special Processing (Optional)

I. Related commands
Command
Function
ADD CXPFXPRO
To add Centrex prefix special processing data
RMV CXPFXPRO
To remove Centrex prefix special processing data
MOD CXPFXPRO
To modify Centrex prefix special processing data
LST CXPFXPRO
To list Centrex prefix special processing data

data configuration.
Generally, the number of a Centrex caller and the Centrex prefix can be used for
number analysis and call connection directly. In some special cases, you must process
caller numbers or Centrex prefixes using ADD CXPFXPRO before the system
implements number analysis or call connection. These cases are

13-15

z
For some specific Centrex prefixes, the corresponding number change is

necessary to mask the real caller numbers.
If a Centrex prefix is an access code only, it must be changed for call connection.
If a Centrex prefix is used for announcement only, it must be changed.
For some Centrex prefixes, failure processing is manually set.
If you define several prefix processing modes in the command, the SoftX3000 only
selects one of them. The selection priority is called number change, sending
tone/sending tone between number, failure processing, and re-analysis. Called number
change can be used in cooperation with sending tone between number or re-analysis.

It specifies the group number of the Centrex group for which the Centrex prefix is to be
set. 65534 is a wildcard character and can indicate all Centrex groups. When it
CXGRP command before it is referenced here.
[Call prefix]
It specifies the prefix of the Centrex group for which prefix processing is needed. It must
have been defined in the ADD ICXPFX command before it is referenced here.
[Call source code]
It specifies the call source for which prefix processing data is to be set. That is, the call
processing software triggers the prefix processing procedure for the Centrex prefixes
dialed by this call source. It must have been defined in the ADD CALLSRC command
before it is referenced here.
[Address nature]
It specifies the address nature of the call source for which the prefix processing
procedure is triggered. Unless otherwise noted, set it to All number.
[Called number change flag]
It indicates whether the call processing software needs to change a called number. If
you set it to Yes, you must define the Called number change index in the command.
[Send tone]
It indicates whether a call prefix is used for sending tone or sending tone between digits.
The options are
z
Sending tone: The SoftX3000 sends the specified signal tone to the caller when a
caller dials this call prefix. The tone type is defined in the parameter Tone type in
this command.
13-16

z
Sending tone between number: When a caller dials this call prefix, the SoftX3000
sends intermittent signal tone of 450 Hz prompting the caller to continue dialing.
When the caller continues to dial the subsequent digits, the SoftX3000 stops
sending the signal tone and starts number analysis. The time when the SoftX3000
starts to send tone is defined in the Tone position in this command.
Not sending tone: The SoftX3000 does not send the signal tone.
You can use the Sending tone between number and called number change
coordinately. The SoftX3000 will implement the latter first, then the former, and then the
subsequent number analysis steps according to the attributes defined by the original
call prefix.
[Failure processing]
It defines whether the call processing software starts the failure processing procedure
for a call prefix forcedly. The default value is No".
When you set it to Yes, all call attempts to this call prefix fails. If you also specify the
failure cause code in the command, the call processing software will query the failure
processing method in the failure processing data table based on this code. The failure
processing method is defined in ADD CFPRO.
[Caller number change flag]
It indicates whether the call processing software needs to change a caller number.
When you set it to Yes, you must specify the value in the Caller number change
index field.
[New DN set]
It specifies the global DN set in whose number analysis table the call processing
software reanalyzes a call prefix. It is available only when Reanalysis is set to Yes.
This parameter must first be defined in the ADD NCODE command before being
referenced here.
[Called number change index]
called number change flag is set to Yes. It must first be defined in the ADD DNC
[Re-analysis]
It indicates whether the call processing software reanalyzes a called number after
change. Set this parameter by the following principles:
z
To change the global DN set of the call prefix, you must set this parameter to Yes.
The call processing software will reanalyze the call prefix in the number analysis
table of the new global DN set.

13-17

z
You must set the parameter to "Yes when you need to perform called number
change and any of such call attributes as minimum number length, maximum
number length, service type, service attribute, route selection code, charging
selection code, or emergency call observation flag is changed. The SoftX3000 will
reanalyze the new called number according to the call attributes of the new call
prefix in the number analysis table.
When you need to change the called number, and all the above-listed call
attributes are the same before and after the number change, you must set the
parameter to No. The SoftX3000 will continue to analyze the new called number
according to the call attributes of the original call prefix in the number analysis
table.
Note:
The reanalysis can be used together with called number change. The SoftX3000 first
changes the called number and then reanalyzes the new called number.
[Tone position]
It indicates from which digit of the called number the SoftX3000 starts to send the signal
tone to a caller. It is available only when Send tone is set to Sending tone between
number. Its value ranges form 0 to 15. The default value is 0, meaning not sending
tone.
[Signal tone type]
It indicates the tone played by the SoftX3000 when a caller dials a specific call prefix. It
is available only when Send tone is set to Sending tone. Select an appropriate tone
type accordingly.
It indicates the cause for call failure or connection failure, and is available only when
Failure processing flag is set to Yes. After you set the failure cause code, you must
also set the corresponding failure processing method in the failure processing table by
executing ADD CFPRO.
[Caller change index]
It indicates the number change index of the caller number, and is available only when
Caller number change flag is set to Yes. This parameter must first be defined in the

13-18

13.2.6 Adding Centrex Intra-Group Charging (Optional)

I. Related commands
Command
Function
ADD CHGCX
To add Centrex intra-group charging data
RMV CHGCX
To remove Centrex intra-group charging data
LST CHGCX
To list Centrex intra-group charging data

data configuration.
It should be negotiated between the carrier and the Centrex customers whether or not
to charge intra-Centrex calls.
If intra-Centrex calls are necessarily charged, an appropriate charging case can be
added for charging intra-Centrex calls in ADD CHGCX and consequently the system
will not distinguish specific charges for intra-Centrex calls. That is, the charge of each
call will not be detailed to caller, callee or bearer capability.
If distinguishing charging for intra-Centrex calls is expected, you can set an intra-office
group-based charging or destination code charging to achieve that.

It specifies the group number of the Centrex group for which the Centrex group
charging data is to be set. 65534 is a wildcard character and can indicate all Centrex
groups. When it indicates a specific Centrex group, this parameter must have been
defined in the ADD CXGRP command before it is referenced here.
[Charging case]
It specifies the charging case applicable to the intra-Centrex calls. It is defined in the
ADD CHGANA command and referenced here. For details about charging, refer to
Chapter 4, Configuring Charging Data.

13-19

13.2.7 Adding Centrex Out-Group Authority (Optional)

I. Related commands
Command
Function
ADD CXOCR
To add Centrex out-group authority
RMV CXOCR
To remove Centrex out-group authority
LST CXOCR
To list Centrex out-group authority

data configuration.
When Centrex subscribers use the outgoing call barring supplementary service, a K
value is required in service logics to restrict outgoing call rights. The range of K value
is K0 to K24, each of which represents a unique restriction level. K1, K2 and K3 are
preset by system automatically. Their meanings are as follows:
z
K1: Local, local toll, national toll, international toll, outgoing Centrex, intra-office
national toll, and intra-office international toll calls are restricted.
K2: National toll, international toll, intra-office national toll, and intra-office
international toll calls are restricted.
K3: International toll and intra-office international toll calls are restricted.
To re-define the preceding K values or add other K values, use the ADD CXOCR
command to add new outgoing call rights for the Centrex group.
To add an outgoing call right K value for ordinary subscribers, use the SET PFXOCR
command.

It specifies the group number of the Centrex group for which the outgoing call right is to
be set. 65534 is a wildcard character and can indicate all Centrex groups. When it
CXGRP command before it is referenced here.
[K value]
It specifies the K value of restricted rights to be configured. Its value ranges from K0 to
K24. K1, K2, and K3 have been preset during system initialization. You can query the
preset values using LST CXOCR.
13-20

[Restricted rights]
It specifies the outgoing call restricted rights corresponding to the preceding K value.
Totally, there are nine types, namely local-office, local, local toll, national toll,
international toll, intra-Centrex, outgoing Centrex, intra-office national toll (multi-area
code application), and intra-office international toll (multi-country code application).
13.2.8 Adding Centrex Group Abbreviated Dialing (Optional)

I. Related commands
Command
Function
ADD CXSD
To add Centrex group abbreviated dialing data
RMV CXSD
To remove Centrex group abbreviated dialing data
MOD CXSD
To modify Centrex group abbreviated dialing data
LST CXSD
To list Centrex group abbreviated dialing data

data configuration.
ADD CXSD is used to achieve the intra-Centrex abbreviated dialing service that
enables one or two digits to represent a complete called number. You can register or
cancel the intra-Centrex abbreviated dialing service directly with MML commands, and
all members of the Centrex can enjoy this service after registration. However, the
common abbreviated dialing service can only be registered or cancelled on a phone set,
and is valid on this phone set only.

[Centrex group]
It specifies the group number of the Centrex for which the intra-Centrex abbreviated
dialing service is to be set. It must first be defined in the ADD CXGRP command before
[Speed number]
It defines an abbreviated number uniquely in a Centrex. If the service logic adopts
one-digit number, this parameter ranges from 0 to 9. If the service logic adopts 2-digit
number, this parameter ranges from 00 to 99.
[Subscriber number]
13-21

It specifies a complete called number that is represented by an abbreviated number.
13.2.9 Adding Centrex Subscriber Status Subscribing (Optional)

I. Related commands
Command
Function
ADD LAMPST
To add Centrex subscriber status subscribing
RMV LAMPST
To remove Centrex subscriber status subscribing
MOD LAMPST
To modify Centrex subscriber status subscribing
LST LAMPST
To list Centrex subscriber status subscribing

Follow the steps below to enable the Key system service in the local office:
1)
Set Key system flag of the Centrex group to Yes by executing the command
MOD CXGRP.
2)
Set bit 8 of internal call parameter 7 (P121) to 0 by executing the command MOD
FSFP.
3)
Add Centrex subscriber status subscribing data by executing the command ADD
LAMPST.

[Local DN set]
It specifies the local DN set to which the subscriber number belongs. The parameter
must be defined in the ADD LDNSET command before being referenced here.
[Subscriber number]
It specifies the long number of the Centrex subscriber who uses the Key system service.
The configuration principles of this parameter are as follows:
z
You must set "Key system flag of the Centrex group to which the subscriber
belongs to Yes. Otherwise, the configuration command cannot be executed
successfully.
The service subscriber and the subscribed subscriber must be ESL subscribers
(including V5 subscribers) in the same Centrex group.
[Lamp number]

13-22

It specifies the number of the indicator on the special phone set of the service
subscriber. Its value ranges from 0 to 47, indicating that a service subscriber can
subscribe the status of a maximum of 48 subscribers.
[Lamp associated short number]
It specifies the short number of the subscribed subscriber corresponding to the above
indicator. The configuration principles of the parameter are as follows:
1)
The indicator on the phone set of a service subscriber must correspond to the
short number of a subscribed subscriber. That is, an indicator can only represent
the status of a subscribed subscriber.
2)
A subscriber can only be subscribed by a maximum of 16 service subscribers.
13.2.10 Setting Local IP Address for Controlling Console

I. Related commands
Command
Function
SET CONADDR
To set local IP address for controlling console
LST CONADDR
To list local IP address for controlling console

The SoftX3000 supports multiple IP signaling interfaces, but the system cannot
automatically designate a specific IP signaling interface to process protocols between
the SoftX3000 and the IP console. That is, the system considers the IP address for
controlling the IP console is 225.255.255.255 by default. Therefore, you must set the
local IP address for the IP console using SET CONADDR before adding the IP console.

[Local IP address]
It is one of the interconnection parameters between the SoftX3000 and the IP console,
used to specify the local IP address for processing protocols of the IP console at the
SoftX3000 side. This address is one of the IP addresses of FE ports in the SoftX3000. It
is defined in the ADD FECFG command and referenced here.

13-23

13.2.11 Adding IP Console

I. Related commands
Command
Function
ADD CXCON
To add IP console
RMV CXCON
To remove IP console
MOD CXCON
To modify IP console
LST CXCON
To list IP console

Before adding an IP console, use the following commands to get the following
parameters that have been defined in the system:
z
FCCU/FCSU module number: LST MDU
Charging source code: LST CHGGRP and LST CHGIDX

[Subscriber number]
It specifies the telephone number allocated to the console. This number must be in the
number segment defined by the ADD DNSEG command.
[Local DN set]
It specifies the local DN set to which the console belongs. That is, it indicates the local
DN set in whose number analysis table the call processing software analyzes all called
numbers dialed by the console. It is defined in the ADD LDNSET command and
referenced here.
It specifies the module number of the FCCU/FCSU responsible for processing call
control messages of the console at the SoftX3000 side. The value range is 22 to 101. It
is defined in the ADD BRD command and referenced here.
[Equipment number]

13-24

It specifies the equipment number allocated to the console. Usually, this number is
assigned in a unified way by the system in the database and thus unnecessarily typed
here.
[Console number]
It is one of the interconnection parameters between the SoftX3000 and the console,
used to uniquely identify a console at the SoftX3000 side. A maximum of 10,000
consoles can be configured in the SoftX3000. The numbering range is 0 to 9999.
An IP console is actually an MGCP gateway. The SoftX3000 regards the console
number as the equipment ID of the console for authentication and management, so this
parameter must be negotiated between the SoftX3000 and the IP console.
[Console IP address]
It is one of the interconnection parameters between the SoftX3000 and the console,
used to define the IP address of the console. The configuration principles of this
parameter are as follows:
z
To use a public dynamically-obtained IP address for the console, you must use
255.255.255.255. The SoftX3000 will not authenticate the IP address.
To use a public static IP address for the console, you can use a valid IP address
(such as 191.169.150.99, or use 255.255.255.255. The SoftX3000 will
authenticate the IP address in the former case.
To use a private IP address for the console, you must use 255.255.255.255 no
matter whether the IP address is dynamic or static. The SoftX3000 will not
authenticate the IP address.
[Codec list]
This is one of the interconnection parameters between the SoftX3000 and the console,
used to specify the codec capabilities supported by the console. For U-Path, select
G.711 A and G.711 .
[Account name], [Password]
These are interconnection parameters between the SoftX3000 and the console, used
to specify the related authentication information for the console to register to the
SoftX3000.
It specifies the group number of the Centrex group to which the console belongs. It is
defined in the ADD CXGRP command and referenced here.
It specifies the extension number, that is, the short number, for the console in the
Centrex group to which the console belongs. The definition of the Centrex short
13-25

number must comply with the intra-Centrex numbering rules including number length
and prefix for the Centrex group. The rules are defined in the ADD ICXPFX command.
[Console access code]
It defines the access code for extensions to originate calls to the console in the same
Centrex group. Usually, this access code is a number composed of one or two bits.
For example, you can define 0 as the out-group prefix for a Centrex group and 9 as the
access code to the console. There are three ways for the extensions in the Centrex
group to originate calls to the console, that is, dialing the long number, the short number,
or the access code allocated to the console. It is easy to find that the simplest way is
dialing the access code, that is, dialing 9.
This is one of the charging attributes of the console. It is defined in the ADD CHGGRP
or ADD CHGIDX command and referenced here. For details about charging, refer to
Chapter 4, Configuring Charging Data.
[Call source code]
It specifies the call source to which the console belongs. It is defined in the ADD
CALLSRC command and referenced here.
[Additional status]
It specifies whether the console is a PBX subscriber, that is, whether the function of
queuing multiple consoles (call center function) is supported. Set this parameter by the
z
If the console does not require the queuing function, select ordinary.
If the console requires the queuing function, select PBX non-indicating number
occupying number.
[Operator attribute]
This is a reserved parameter.
[Call-in authority]
It specifies the call-in authority for the console. Totally, there are nine types, namely,
intra-office, local, local toll, national toll, international toll, intra-Centrex, incoming
Centrex, intra-office national toll (multi-area code application), and intra-office
international toll (multi-country code application). By default, the subscriber has all the
call in authorities.
It specifies the call-out authority for the console. Totally, there are nine types, namely
intra-office, local, local toll, national toll, international toll, intra-Centrex, outgoing
13-26

Centrex, intra-office national toll (multi-area code application), and intra-office

international toll (multi-country code application). By default, the subscriber has all
except the national toll, international toll, intra-office national toll, and intra-office
international toll call out authorities.
It specifies the supplementary service authority for the subscriber. By default, the
subscriber does not have any supplementary service authority.
[Call pickup group]
It specifies the number of the co-group pickup group in the Centrex to which the
console belongs. The value range is 0 to 255. The value 255 indicates invalid.
[Call-out password]
It defines the initial call-out password used by the console for the outgoing call barring
supplementary service. The password is a decimal number composed of four to six
digits, and the specific length depends on the service syntax. By default, it is 0000.
The subscriber can modify this password on the phone set.
[Charging category]
It specifies the charging category of the subscriber number. By default, it is Period.
The options are
z
Period: Communication fee is rendered regularly, for example, every month.
charging of unattendent public phones.
Free: The calls that require no payment from the calling party after service analysis,
such as police call, fire emergency call, ambulance emergency calls, traffic
accident calls, FPH calls, and collect calls. For calls defined as free in charging
category, the detailed call information of the caller will still be recorded, and the
free call detailed ticket will be generated.
originated by the console for query. The default value is No. If a subscriber questions
a bill, you can set this parameter to Yes.

13-27

This is one of the charging attributes of the subscriber. It is defined in the ADD
CHGCLD command and referenced here. By default, it is 255, indicating that the called
charging is not performed. For details about charging, refer to Chapter 4, Configuring
Charging Data.
It specifies the call barring group to which the console belongs. Set this parameter by
the following principles:
z
enabled.
can be referenced directly, that is, black list 60001, white list 60002 and ordinary
If the other call barring groups are used, this parameter must be defined in the SET
GRPAC command before being referenced here.
The call barring group number can be used for both time-based call barring and
inter-group call barring. Meanwhile, inter-group barring is prior to time-based barring.
That is, the system first judges whether to implement inter-group barring and then
whether to implement time-based barring.
[Console call-in authority]
It specifies the subscribers call-in rights that can be controlled by the console of the
subscriber resident Centrex group. By default, it is set to All.
[Console call-out authority]
It specifies the subscribers call-out rights that can be controlled by the console of the
subscriber resident Centrex group. By default, the console can control all call-out
authorities except international toll and intra-office international toll.
[Console supplementary service]
It specifies the subscribers supplementary service rights that can be controlled by the
console of the Centrex group to which the subscriber belongs. By default, the console
can control all supplementary service rights.

13-28

[PBX pilot number]

If the console acts as a PBX subscriber, this parameter specifies the indicating number,
sometimes called pilot number, of the PBX group to which the subscriber belongs. This
indicating number is defined in the ADD PBX command and referenced here.
[PBX subscriber priority]
It specifies the priority of the PBX subscriber. The value range is 0 to 255. The less the
value, the higher the priority is. 0 indicates the highest priority. If several PBX
subscribers have the same priority, the system will select a subscriber line according to
the line hunting mode defined in the ADD PBX command. If a PBX subscriber has a
higher priority than others, the system will select that subscriber line preferentially.
For example, there are ten PBX subscribers in the same PBX group. The priority for
five subscribers is 0, and the priority for the remaining is 1. In this case, the system will
prefer the five PBX subscribers with the priority 0 during a line hunting process, and
furthermore for the five PBX subscribers with the priority 0, the system will comply with
the line hunting mode defined for the PBX group. When the lines of all the five
subscribers with the priority 0 are occupied, the system turns to the remaining PBX
subscribers with the priority 1.
[Call watch flag]
It specifies whether the SoftX3000 watches all calls of the subscriber. By default, it is
set to No. If you set it to Yes, the SoftX3000 generates an alarm at the alarm console
for any call activities such as offhook, dialing, call-in, or call-out.
[Super Do-Not-Disturb Password]
It defines the initial password for the super do-not-disturb service. It contains four to
six decimal digits and the specific length depends on the service syntax. The default
password is 000000, which can be modified through the console.
[Bill type]
It defines the format of the bills sent by the SoftX3000 to the IP console. For the IP
console used with the SoftX3000 V300R001, select Old bill format. For the IP console
used with the SoftX3000 V300R002, select New bill format.
13.2.12 Adding ISDN Centrex console

I. Related commands
Command
ADD ISDNCON
Function
To add ISDN Centrex console

13-29

Command
Function
MOD ISDNCON
To modify ISDN Centrex console
LST CXCON
To list Centrex console

Before adding an IP console, use the following commands to get the following
parameters that have been defined in the system:
z
FCCU/FCSU module number: LST MDU
Charging source code: LST CHGGRP and LST CHGIDX
Note:
Most of the parameters in ADD ISDNCON are the same as those in ADD CXCON, so
this section only describes the dedicated parameters in ADD ISDNCON. For the other
parameters, refer to 13.2.11 Adding IP Console.
[Subscriber number]
It specifies the telephone number allocated to the subscriber. This number must be in
the number segment defined by the ADD DNSEG command. The parameter must be
specified for all subscribers except PBX subscribers who do not occupy number
resources.
[Local DN set]
called numbers dialed by the subscriber. It must be defined in the ADD LDNSET
[Equipment ID]
It specifies the equipment ID of the media gateway to which the ISDN console belongs.
It must be defined in the command ADD MGW before being referenced here.
13-30

[Termination ID]
It specifies the physical port number of the media gateway to which the ISDN console
belongs. It only consists of digits and/or the symbol "/". Set this parameter by the
z
termination ID is 0, aaln/0 @ amg2.hauwei.com indicates physical port 0 of the
gateway.

Each ISDN console uses two termination IDs. If the termination ID specified by the
subscriber is n, the termination IDs used by the ISDN console are n and n + 1.
[IUA linkset index]
It specifies the IUA linkset that bears BRA link messages. The BRA links carry the D
channel signaling messages of the BRA subscriber. The parameter must be defined in
the command ADD IUALKS before being referenced here.
[Interface ID]
It is one of the parameters for interconnecting the SoftX3000 with the built-in signaling
gateway that supports IUA protocol. It identifies the BRA link in the D channel signaling
messages of all BRA subscribers borne by the IUA linkset.
For BRA subscribers who use the same IUA linkset to bear the D channel signaling
messages, their interface IDs in the IUA linkset are not repeatable. If many BRA
subscribers are to be configured, uniformly plan the interface IDs of the BRA links.
[Codec prefer]
It specifies which voice codec mode will be preferred by the media gateway to encode
the RTP audio media streams of the subscriber. The codec mode must be in the codec
list defined in the command ADD MGW. Otherwise, it is invalid.
If there are codec modes concurrently supported by the calling and called media
gateways, the first codec mode in the codec list is preferred. This is called codec
prefer. If the prefered codec modes of caller, callee, incoming trunk group, and
outgoing trunk group are all contained in the codec list, the SoftX3000 prefers the
codec mode according to the caller first and subscriber first principle.
For example, for an intra-office call, if the preferred codec modes of the caller and
callee are not the same, the preferred codec mode of the caller is valid. For an outgoing
trunk call of the local office, if the preferred codec modes of the caller and outgoing
13-31

trunk group are not the same, the preferred codec mode of the caller is valid. For a
tandem call, if the preferred codec modes of the incoming and outgoing trunk groups of
the local office are not the same, the preferred codec mode of the incoming trunk group
is valid. For an incoming terminating trunk call, if the preferred codec modes of the
incoming trunk group and the callee of the local office are not the same, the preferred
codec mode of the callee is valid.
[ISDN index]
It specifies the ISDN data used by the BRA subscriber. The parameter must be defined
in the command ADD ISDNDAT before being referenced here.
It specifies the number of the Centrex group to which the console belongs. The
parameter must be defined in the command ADD CXGRP before being referenced
here.
It specifies the extension number, that is, the short number, of the console in the
Centrex group to which the console belongs. The definition of the Centrex short
number must comply with the intra-Centrex numbering rules including number length
and prefix for the Centrex group. The rules are defined in the ADD ICXPFX command.
13.2.13 Modifying Centrex Group (Optional)

I. Related commands
Command
Function
MOD CXGRP
To modify Centrex group
LST CXGRP
To list Centrex group

data configuration.
The IP console in a Centrex group has six attributes: Call Forwarding Busy (CFB) to
console, Call Forwarding No Reply (CFNR) to console, call forwarding on
do-not-disturb to console, sending ticket to console, not charging console for
forwarding calls, and operator extension number. When you added a Centrex group by
using the ADD CXGRP command, the system automatically sets the preceding

13-32

attributes to NO or NULL. If you do not want to use those preset values, you can modify
the IP console attributes of the Centrex group by using the MOD CXGRP command.
Note:
Most of the parameters in MOD CXGRP are the same as those in ADD CXGRP, so this
section only describes the dedicated parameters in MOD CXGRP. For the other
parameters, refer to 13.2.2 Adding Centrex Group.

It specifies the name of the Centrex group for which the IP console attributes are to be
modified. It is defined in the ADD CXGRP command and referenced here.
In this command, you can reference the Centrex group by either its group name or its
group number. However, you cannot reference the Centrex group by both at the same
time; otherwise, errors will occur.
It specifies the group number of the Centrex group for which the IP console attributes
are to be modified. It must have been defined in the ADD CXGRP command before
referenced here.
[CFB to console]
It specifies whether the system forwards calls originated by out-group subscribers to
Centrex subscribers (except the operator) to a designated operator extension (usually
the console) when the callee is busy. By default, it is No, indicating not to forward the
calls to the console. If this parameter is set to Yes, you must set the forwarded-to
number in the operator extension number parameter of this command; otherwise, the
configuration will fail.
[CFNR to console]
the console) when no reply is received from the callee. By default, it is No, indicating
not to forward the calls to the console. If this parameter is set to Yes, you must set the
forwarded-to number in the operator extension number parameter of this command.
Otherwise, the configuration will fail.
[Send ticket to console]
13-33

It specifies whether or not the SoftX3000 sends the generated tickets to the console, for
the purpose of intra-Centrex settlement, when Centrex subscribers originate calls. By
default, tickets are not sent.
If it is expected to immediately charge the Centrex subscribers through the IP console,
for example, in an IP supermarket, you must set this parameter appropriately. That is,
set the type of the tickets sent by the SoftX3000 to the console appropriately. The
options are
z
Not send: The SoftX3000 does not send any tickets to the console.
Detailed ticket: When the calls from Centrex subscribers are recorded in the
format of CDR, the SoftX3000 sends CDRs to the console.
Detailed ticket and meter table: When the calls from Centrex subscribers are
recorded in the format of CDR, the SoftX3000 sends CDRs to the console. When
the calls are recorded in the format of meter table, the SoftX3000 sends meter
tickets to the console.
Detailed ticket of all calls: Regardless of the format of tickets (including free calls)
for Centrex subscribers, the SoftX3000 always sends CDRs to the console.
Detailed ticket of out group call: For outgoing calls, the SoftX3000 always sends
CDRs to the console no matter whether the format of call records for Centrex
subscribers is detailed ticket" or meter table.
Detailed ticket for toll call and farther: For local toll calls and farther calls, the
SoftX3000 always sends CDRs to the console no matter whether the format of call
records for Centrex subscribers is detailed ticket or meter table.
Detailed ticket for national call and farther: For national toll calls and farther calls,
the SoftX3000 always sends CDRs to the console no matter whether the format of
call records for Centrex subscribers is detailed ticket or meter table.
Detailed ticket for international toll: For international toll calls, the SoftX3000
always sends CDRs to the console no matter whether the format of call records for
Centrex subscribers is detailed ticket" or meter table.
[Operator extension number]

It defines the forwarded-to number for the CFB to console, CFNR to console, and
Forward to console in Do-Not-Disturb service. It should conform to the numbering
rules of the Centrex group on length and prefix. These rules are defined in ADD
ICXPFX.
Being the forwarded-to number, the operator extension number is usually configured as
the corresponding Centrex short number of a console or the short number for a Centrex
subscriber in the same group. If you enter the asterisk sign *, the operator extension
number is to be deleted from the database and meanwhile the CFB to console,
CFNR to console, and Forward to console in Do-Not-Disturb service attributes of the
Centrex group are automatically set to No.
[Forward to console in Do-Not-Disturb service]
13-34


the console) when the callee has registered the do-not-disturb service. By default, it is
No, indicating not to forward the calls to the console. If this parameter is set to Yes,
you must set the forwarded-to number in the operator extension number parameter of
this command. Otherwise, the configuration will fail.
[Centrex CFNR timer]
When a subscriber calls a Centrex subscriber who has registered the CFNR service,
this parameter specifies the ringing duration after which the SoftX3000 forwards the call.
Its value ranges from 12 to 30 in unit of second. By default, it is set to 16.
[Out-group prefix display flag]
When a Centrex subscriber calls an out-group subscriber who has registered the CLIP
service, this parameter indicates whether the SoftX3000 sends the out-group prefix
(that is, adding the out-group prefix before the long number of the Centrex subscriber)
to the out-group subscriber. By default, it is set to "No.
[Console message resend interval]
It indicates the duration after which the console re-sends a message to the SoftX3000
after the first transmission failure. Its value ranges from 1 to 5 in unit of second.
[Console message resend times]
It indicates the maximum resend times allowed for the console to re-send a message to
the SoftX3000. Its value ranges from 1 to 8.
[SoftX to IP market number change index]
It specifies the number change index of a caller number when the caller number
contained in the message (bill) sent by the SoftX3000 to the IP supermarket needs to
be changed. For example, change a 12-digit caller number to an 8-digit one. It must be
defined in ADD DNC before being referenced here.
[IP market to SoftX number change index]
It specifies the number change index of a caller number when the caller number
contained in the message sent by the IP supermarket to the SoftX3000 needs to be
changed. For example, change an 8-digit caller number to a 12-digit one. It must be
defined in ADD DNC before being referenced here.

13-35

Chapter 14 Configuring Call Barring Data

14.1.1 Caller Number Discrimination
I. Basic concepts
Particular caller number rules are pre-defined in the system. Whenever the SoftX3000
receives an incoming trunk call, the call processing software checks and judges the
validity of the nature of address, length of number, call prefix, and other attributes of the
caller number, which are sent by the originating office, complying with those caller
number rules. Accordingly the call processing software makes a determination that the
call is received or rejected. That is a caller number discrimination.
The purpose of caller number discrimination is to prevent incoming trunks from sending
caller numbers without any restriction. That is, any caller number sent by the originating
office through an incoming signaling message must comply with the caller number rules
pre-defined in the local office; otherwise, the call will be rejected. For example, a PSTN
gateway office can require the opposite mobile gateway office to send the caller
numbers only in the segment 13XXXXXXXXX to itself through the caller number
discrimination function. Other caller numbers not in that segment will be rejected
thoroughly.
II. Implementation
The SoftX3000 implements the caller number discrimination functionality in two ways
as follows:
1)
Setting an attribute of the call source
Call source represents the attributes of the calling party. By setting the caller address
discrimination parameter, you can achieve that the caller number discrimination is
performed on all the incoming trunks that belong to that call source. In this
implementation, the call source code is used as the basis to judge whether or not to
perform a caller number discrimination on the concerned incoming trunk. Therefore,
this implementation is applicable only to the cases in which incoming trunks are not
classified further.
2)
Setting a caller discrimination group

14-1

Through a caller discrimination group, a particular caller number can be discriminated.

Different discrimination functions can be implemented on the incoming trunk groups by
making reference to different caller discrimination group numbers. In this
implementation, the caller discrimination group number is used as the basis to judge
whether or not to perform a caller number discrimination on the concerned incoming
trunk. Therefore, this implementation distinguishes further classified incoming trunks
and is widely applied to caller number discrimination cases of incoming trunks.
If you configure the preceding two discrimination implementations, both have an effect
on the calls from incoming trunks. The analysis flow of the call processing software is
like this: the system queries the call source table based on the call source code of the
caller number resident incoming trunk group and judges whether or not to perform
discrimination on the nature of caller address; subsequently the system queries the
caller number discrimination group table based on the caller discrimination group
number of the incoming trunk group and then performs a caller number discrimination
by selecting the function code.
14.1.2 Inter-Group Call Barring and Black and White Lists

I. Inter-group call barring
Some local office subscribers, trunk groups or call prefixes may have been classified
into different call barring groups. If a call is originated from a group identified as
the caller barring group to another group identified as the callee barring group", the
system depends on the pre-defined call barring relationship between the caller barring
group and the callee barring group to receive or reject the call. That is inter-group call
barring.
The process of inter-group call barring can be summarized like this: what type of
caller allows or rejects a call from what type of callee. A simple inter-group call
barring relationship is shown in Table 14-1.
Table 14-1 Inter-group call barring relationship
Caller barring group
number
Callee barring group

number
Call indication
101
101
Call allowed
101
102
Call allowed
102
102
Call allowed
102
101
Call barred

14-2

The SoftX3000 authenticates inter-group call barring twice for the call prefix, and the
caller and callee sides during the number analysis process. To use the function
correctly and avoid mistakes, read the following inter-group call barring procedure:
1)
2)

II. Black and white lists

Black and white lists are actually a special kind of inter-group call barring relationship.
During the initialization process, the system presets respective call barring group
numbers for black and white lists 60001 for the black list and 60002 for the white list.
In addition, the system presets an ordinary call barring group whose group number is a
wildcard value 65534. The call barring-related relationship between them is fixed (you
cannot set it) as shown in Figure 14-1.
Call allowed
Black
Caller
Black
Oridinary
Oridinary
White
White
Callee
Figure 14-1 Inter-group call barring relationship between black and white lists
1)
A caller in the black list can only call a callee in the white list.
2)
A caller in the ordinary call barring group can call a callee in the white list or in the
ordinary call barring group, but cannot call a callee in the black list.
3)
A caller in the white list can call any subscribers.
According to the preceding relationship, the system presets an inter-group call barring
indication table for the groups 60001, 60002, and 65534, as shown in Table 14-2.

14-3

Table 14-2 Inter-group call barring relationship between black and white lists
Caller barring group
number
Callee barring group number
Call indication
60001
60002
Call allowed
60001
65534
Call barred
60002
60001
Call allowed
60002
65534
Call allowed
65534
60002
Call allowed
65534
60001
Call barred
As shown in Table 14-2, 65534 is a wildcard character and represents all call barring
group numbers including the black and white lists, but with the lowest priority. For
example, for the first two records as shown in Table 14-2, the callee barring group
65534 in the second record also represents 60002, but the callee barring group in the
first record is 60002. The call barring relationship between the caller barring group
60001 and the callee barring group 60002 complies with the first record as shown in
Table 14-2.
It should be noted that when used as a callee barring group, the call barring group
numbers 60001, 60002 and 65534 are applicable only to the cases in which the callee
is a local office subscriber or an outgoing trunk group. For outgoing trunk calls, the
system cannot distinguish further classified called numbers. If you want to classify
outgoing called numbers, you need to define the corresponding outgoing call prefix for
the black list, white list, or other ordinary call barring groups using the ADD CLDGRP
command.
14.1.3 Time-Based Call Restriction

Time-based call restriction is designed for Centrex subscribers. In the SoftX3000, the
time-based call restriction function can be implemented in flexible ways.
1)
The SoftX3000 supports a maximum of four time segments for call restriction. That
is, call restriction can be carried out in four time segments every day.
2)
The SoftX3000 can restrict both call-in and call-out authorities of Centrex
subscribers.
3)
The SoftX3000 supports to group Centrex subscribers into different call restriction
groups. That is, in the same Centrex, different call restriction groups employ
different call restriction policies.
For example, the time-based call restriction service restricts ordinary subscribers in a
Centrex group to originate national toll calls and international toll calls after work time.

14-4

14.1.4 Other Call Restriction Methods

I. Timed restriction
The timed restriction supplementary service enables the system to control the
conversation duration of each call by defining the maximum duration allowed for each
call. That is, once a conversation exceeds the defined limit, the system will forcedly
release the call and prohibit the user from continuing the conversation.
II. Quota restricted calling

The quota restricted calling supplementary service enables the system to control a
users calling expenses by defining the maximum fee allowed for the user to enjoy calls
in one month. That is, when the accumulated calling expenses of the user in that month
exceed the defined limit, the system will prohibit the user from making a new call or
forcedly terminate the on-going conversation.
It should be noted that the quota restricted calling service is used only for immediately
chargeable calls and the maximum conversation fee is recovered once per month. That
is, the fee limit is valid only in that month.
III. Network management commands

Network management commands, a set of Man Machine Language (MML) commands,
are designed for the network management center to perform network management
operations through the SoftX3000 and to schedule and manage trunk circuits and trunk
routes. Network management commands can also implement call restriction functions,
such as originating destination code restriction control, outgoing destination code
restriction control, call gapping control, and special recorded announcements.
It should be noted that what network management commands do is to control activation
and deactivation of associated commands through the network management system.
This is a temporary and dynamic call restriction policy, while other call restriction
methods are permanent and static ones. This chapter does not describe the network
management commands. For information about them, refer to Chapter 17, Configuring
Network Management Data, of this manual.
14.1.5 Analysis of Number Restriction

The SoftX3000 supports multiple call restriction functions. When several call restriction
functions are enabled together, call restriction may not be implemented correctly if you
do not know the number restriction analysis procedure of the call processing software.
The analysis procedure can be briefed as follows: number preparation caller number
discrimination called number analysis called number barring analysis
14-5

subscriber call-out authority analysis NM instruction barring analysis black &

white lists analysis subscriber call-in authority analysis. See Figure 14-2 for details.

14-6

Offhook and dialup

Call failure
Number preparation
Failure processing (number

change re-analysis)
Discrimination of local caller

number
Discrimination of incoming
trunk group caller number
Called number analysis

Special called number
change
LST CALLSRC
LST CLRDSN
LST CNACLD
Called number barring
analysis
LST CLDGRP
Caller number analysis
LST CNACLR
Special processing of prefix
LST PFXPRO
Designated destination code

barring service
Call barring service
Supplementary
service analysis
procedure
Time-based restriction of intra-Centrex

calls (call-out authority)
LST LCGRP
Analysis of call-out authority
LST VSBR
Originating destination code

control
HTR control
LST NMIDEST
LST HTRDESC
Call gap control

Special record notification
control
Outgoing destination code
control
Other NM instructions
LST NMGAP
Black & w hite lists barring

analysis
LST GRPAC
Absent subscriber service

Do-not-disturb service
Timed restriction service
LST NMTONE
LST NMODEST
LST NM
Supplementary
service analysis
procedure
Time-based restriction of intra-Centrex

calls (call-in authority)
LST LCGRP
Call-in authority analysis
LST VSBR
Quota-restricted calling
service
Call connection
Figure 14-2 number restriction analysis procedure

14-7
Supplementary
service analysis
procedure

In a number analysis procedure, you can change the calling number or the called
number at several analysis points with MML commands, which will greatly affect the call
restriction result.
z
If you change the calling number or the called number at the number preparation
stage using ADD CALLSRC, the system first changes the number, and then
carries out the call restriction analysis procedure. That is, the calling number or the
called number after change is analyzed in the procedure.
If you change the calling number or the called number at the caller number
analysis stage using ADD CNACLR or at the prefix special processing stage
using ADD PFXPRO, the system first carries out the call restriction analysis
procedure, and then changes the number. That is, the calling number or the called
number before change is analyzed in the procedure.
If you change the called number at the called number analysis stage using ADD
SPDNC, the system first changes the called number, and then carries out the call
restriction analysis procedure. That is, the called number after change is analyzed
in the procedure.
For forwarded calls, caller number discrimination and black & whiter lists analysis
are performed on the original called number. For example, if A calls B and the call
is forwarded to C, the system uses the number of B instead of that of A during
caller number discrimination or black & white lists analysis.
14.1.6 Applications of Call Barring Data

Call barring data defines call barring attributes of local office subscribers or trunk
groups. When you configure subscriber data or trunk group data, the system has to
reference the caller discrimination group number or barring group number
parameters defined in the call barring data. During an office deployment, it is not
recommended to reference any call barring data when you add subscribers or trunk
groups by using the ADD commands. The purpose is not to affect the debugging of the
basic functions provided for the subscribers or trunk groups due to the call barring.
After the basic functions of the subscribers or trunk groups are debugged, you can set
appropriate call barring attributes for them using the MOD commands. Such MOD
commands are as follows:
z
MOD CALLSRC: To modify the caller number discrimination attribute of call

source codes
MOD VSBR: To modify the call barring attribute of voice subscribers
MOD MSBR: To modify the call barring attribute of multimedia subscribers
MOD BRA: To modify the call barring attribute of BRA subscribers
MOD PRA: To modify the call barring attribute of PRA subscribers
MOD TGDSG: To modify the caller number discrimination attribute of trunk groups
MOD SIPTG: To modify the call barring attribute of SIP trunk groups
MOD H323TG: To modify the call barring attribute of H.323 trunk groups
14-8

MOD N7TG: To modify the call barring attribute of SS7 trunk groups
MOD N1TG: To modify the call barring attribute of R2 trunk groups
14.2 Configuring Call Barring Data

14.2.1 Overview
Call barring data defines caller number discrimination, inter-group call barring, and
time-based call restriction. To configure call barring data, make sure that the office data,
charging data, trunk data, number analysis data, subscriber data, and Centrex data has
been configured. See Figure 14-3.
Start
Equipment data
Trunk data
Office data
Number analysis
Charging data
Subscriber data
MG data
Centrex data
MRS data
Call barring data
Protocol data
IN service data
Signaling data
Other service data
Routing data
Other application
data
End

you configure office data and Centrex data will be referenced during the configuration
of call barring data, and some parameters defined here will be referenced during the
configuration of trunk data and subscriber data. The referencing relationship is

14-9

presented as the broken lines in Figure 14-3. For the parameter referencing
relationship between call barring data and other data, see Table 14-3.
Table 14-3 Parameter referencing relationship between call barring data and other
data
Input parameter
Name
Output parameter
Defined in
Name
Referenced in
Local DN set
Office data
Caller discrimination group

number
Trunk data
Centrex group
number
Centrex data
Trunk data and

subscriber data
II. Preparations
Before configuring call barring data, make sure that all preparations are done as
SN
Item
Remark
Call barring method
Plan appropriate call barring methods to be used for

different trunk groups or subscriber groups.
Planning caller
discrimination group
numbers
Plan the caller numbers and discrimination types

suitable for each caller discrimination group number.
Planning black and

white lists
Determine whether or not to define outgoing call

prefix in a black or white list (which is applicable only
to a callee barring group).
Planning call
timingly restriction
group numbers
Determine time-based call restriction

suitable for Centrex subscribers.
policies

Table 14-5 lists the general steps for configuring call barring data.
Step
Description
Command
Modify call source code
MOD CALLSRC
Add caller number discrimination group
ADD CLRDSN

14-10

Step
Description
Command
Add trunk discrimination group
ADD TGDSG
Set inter-group call barring indication
SET GRPAC
Add called number barring group
ADD CLDGRP
Add call timingly restriction group
ADD LCGRP

the call barring data is configured.
ADD CLRDSN
SET GRPAC
[Source call barring group
number]
[Discrimination group number]

[Caller number]
[Destination call barring group

number]
[Address nature]
[Call indication]
ADD TGDSG
ADD CLDGRP
[Local DN set]
[Caller category]
[Called prefix]
[Called barring group number]
14.2.2 Modifying Call Source Code

I. Related commands
Command
Function
ADD CALLSRC
To add call source code
RMV CALLSRC
To remove call source code
MOD CALLSRC
To modify call source code
LST CALLSRC
To list call source code

14-11


Call source represents the attributes of the calling party. By setting the caller address
discrimination parameter, you can achieve that the caller number discrimination is
performed on all the incoming trunks that belong to that call source. In this
implementation, the call source code is used as the basis to judge whether or not to
perform a caller number discrimination on the concerned incoming trunk. Therefore,
this implementation is applicable only to the cases in which incoming trunks are not
classified further.
Note:
Most of the parameters in MOD CALLSRC are the same as those in ADD
CALLSRC, so this section only describes the dedicated parameters in MOD
CALLSRC. For the other parameters, refer to section 3.2.9, Adding Call Source
Code of this manual.
[Call source code]

This parameter specifies the call source whose attribute, caller address discrimination
flag, is to be modified. This parameter is defined in the ADD CALLSRC command and
referenced here.
[Caller address discrimination]
In number analysis, the system determines the corresponding connection operation
according to the caller address nature and this parameter. The options are
z
Not identifying: Do not discriminate.
Reject call if not consistent: If the nature of address of the caller number sent by
the opposite office through an incoming office signaling message is not consistent
with the actual number length, the call will be refused. Two cases may occur:
maximum length defined for local numbers (which is determined by a software
parameter and is 8 digits by default), the nature of address of the caller number must
indicate a subscriber number; otherwise, the local office will reject the call.
length defined for local numbers, the nature of address of the caller number must
indicate a national or international number; otherwise, the local office will reject the call.

14-12

z
Modify address nature if not consistent: If the nature of address of the caller
number sent by the opposite office through an incoming office signaling message
is not consistent with the actual number length, the system will modify the nature
of address of the caller number before other call processing. Two cases may
occur:
maximum length defined for local numbers, the system will modify the nature of
address of the caller number to a subscriber number.
length defined for local numbers, the system will modify the nature of address of the
caller number to a national or international number.
z
Only allow national and international number: If the nature of address of the caller
does not indicate a national or international number, the local office will reject the
call.
Change to subscriber number: If the national toll area code in the caller number
sent by the opposite office through an incoming office signaling message is the
same as the national toll area code defined for local office subscribers, the caller
number will be changed to a subscriber number without area code. If they are the
same, no modification will be made.
Change to toll number without 0: If the nature of address of the caller number sent
by the opposite office through an incoming office signaling message indicates a
national number, the received caller number is changed to a national number
without 0.
Change to toll number with 0: If the nature of address of the caller number sent by
the opposite office through an incoming office signaling message indicates a
national number, the received caller number is changed to a national number with
0.
Change international toll number without 0: If the nature of address of the caller
indicates an international number, the received caller number is changed to an
international number without 00.
Change international toll number with 0: If the nature of address of the caller
indicates an international number, the received caller number is changed to an
international number with 00.
14.2.3 Adding Caller Number Discrimination Group

Related commands

14-13

Command
Function
ADD CLRDSN
To add caller number discrimination group
RMV CLRDSN
To remove caller number discrimination group
MOD CLRDSN
To modify caller number discrimination group
LST CLRDSN
To list caller number discrimination group
ADB CLRDSN
To add a batch of caller number discrimination groups
RVB CLRDSN
To remove a batch of caller number discrimination groups
I. Notes of configuration
Through a caller number discrimination group, a particular caller number can be
discriminated. Different discrimination functions can be implemented on the incoming
trunk groups by making reference to different caller discrimination group numbers. In
this implementation, the caller discrimination group number is used as the basis to
judge whether or not to perform a caller number discrimination on the concerned
incoming trunk. Therefore, this implementation distinguishes further classified
incoming trunks and is widely applied to caller number discrimination cases of incoming
trunks.

It uniquely identifies a caller discrimination group in the SoftX3000. The value range is 0
to 65534. Set this parameter by the following principles:
z
Several caller numbers can be configured in the same discrimination group. That
is, when you are adding a caller discrimination group, several ADD CLRDSN
commands may reference the same discrimination group number.
65534 is a wildcard group number and indicates that the discrimination group can
be used by any trunk group (but with the lowest priority). That is, if the
discrimination group number specified for a trunk group is not 65535, the trunk
group can also use the caller discrimination group numbered 65534, in addition to
the specified group. When the two discrimination groups match a caller number
simultaneously, the one in the specified caller discrimination group is preferred.
[Caller number]
It specifies the prefix of the caller number to be discriminated. Because more than one
caller number can be configured in the same discrimination group, the call processing
software adopts the maximum matching principle to perform a number discrimination.

14-14

What is maximum matching? For a specific caller number, the system searches all
caller prefixes for the most similar one, based on which the corresponding number
discrimination will be carried out. For example, a discrimination group is configured with
three caller number prefixes, 13, 139, and 1390. If the caller number sent by the
opposite office is 13901234567, according to the maximum matching principle, the
system finds the most similar caller prefix 1390. Neither 13 nor 139 complies with
the maximum matching principle.
[Address nature]
It specifies the nature of address of the caller number to be discriminated, such as
unknown type number, international number, national number, or subscriber number.
[Function code]
When the caller number in the incoming trunk call matches the one defined in this
command, this parameter specifies the specific method of number discrimination
implemented by the call processing software. The meanings of the available options
are as follows:
z
Reject call in: The call processing software rejects all calls from that caller number.
Caller number discrimination: The call processing software discriminates the

length of the caller number. If the length of the caller number in the incoming trunk
call is in the range defined by the minimum and maximum lengths in this command,
the call will be accepted; otherwise, the call will be rejected.
Modify caller attribute: The call processing software modifies the call source code,
charging source code, call barring group number, and caller category of the caller
number in the incoming trunk call. That is, the caller number uses the
above-mentioned attributes defined in the command for the call.
Caller number discrimination and modify caller attribute: Refer the above
description.
Judge caller type: The call processing software judges the type of the caller
number in the incoming trunk call. For example, the software judges whether the
caller is a WAC subscriber defined by the local office. If yes, the SoftX3000
connects the call according to the Centrex call processing procedure. If not, the
SoftX3000 connects the call according to the normal call processing procedure.
[One MGW prefer flag]

Suppose that the local office is a tandem office in the local network. For an incoming
trunk call originated by a TMG, suppose that the local office finds that it can select an
outgoing trunk circuit from two or more TMGs (including the TMG that originates the
call) after route analysis. The parameter specifies whether the SoftX3000 prefers the
outgoing trunk circuit of the TMG that originates the call.

14-15

When the networking contains the local office, two or more TMGs, and multiple end
offices, you can use the One MGW prefer flag in the caller discrimination group to
optimize the routing.
[Minimum length], [Maximum length]
They are available if the parameter function code contains the option caller number
discrimination, specifying the minimum and maximum lengths that the caller number in
the incoming trunk call must satisfy. The value 255 indicates not to discriminate the
minimum or maximum length.
[Call source code]
If the parameter function code contains the option modify caller attribute, this
parameter is available to re-define the call source code for the caller number in the
incoming trunk call after the caller number discrimination. That is, the default call
source code of the incoming trunk group is not used for the caller number in this call.
This parameter is defined in the ADD CALLSRC command and referenced here.
65535 indicates not to modify the call source code.
parameter is available to re-define the charging source code for the caller number in the
incoming trunk call after the caller number discrimination. That is, the default charging
source code of the incoming trunk group is not used for the caller number in this call.
This parameter is defined in the ADD CHGIDX or ADD CHGGRP command and
referenced here. The value 255 indicates not to modify the charging source code.
[Barring group number]
parameter is available to re-define the barring group number for the caller number in
the incoming trunk call after the caller number discrimination. That is, the default
barring group number of the incoming trunk group is not used for the caller number in
this call. Set this parameter by the following principles:
z
65535 indicates not to modify the barring group number.
To use black and white lists, three invariable barring group numbers preset by the
system are available directly, that is, 60001 for the black list, 60002 for the white
list, and 65534 for the ordinary barring group.
To use other barring group number, it must have been defined in the SET GRPAC
[Caller category]
parameter is available to re-define the caller category for the caller number in the

14-16

incoming trunk call after the caller number discrimination. That is, the default caller
category sent by the opposite office through an incoming office signaling message is
not used for the caller number in this call.
parameter is available to specify whether the system changes the caller number in the
incoming trunk call after the caller number discrimination. Set this parameter by the
z
If you set this parameter to 0, no number change will be carried out.
If you set this parameter to a value other than 0, number change will be carried
out. In this case, this parameter must have been defined in ADD DNC and then
referenced here.
[Codec list]
parameter is available to re-define the code list supported by the caller number in the
incoming trunk call after the caller number discrimination. That is, the default codec list
supported by the incoming trunk group is not used for the caller number in this call.
The priority sequence of the codec capabilities is decided by the configuration
sequence of codec list of the caller number in the caller number discrimination table.
That is, when you use the command LST CLRDSN to query the discrimination data of a
caller number, the sequence of the codec modes in the query result is the priority
sequence.
z
discrimination table or the called number analysis table, the SoftX3000 selects the
codec mode according to the caller first and subscriber first principle. For
codec modes, only the codec mode of the caller is valid. During a transit call, if the
incoming trunk group and the outgoing trunk group of the local office have different
preferred codec modes, only the codec mode of the incoming trunk group is valid.
14-17

During an incoming terminated call, if the incoming trunk group and the callee of
the local office have different preferred codec modes, only the codec mode of the
callee is valid.
[WAC group number]
It specifies in the data table of which WAC group the call processing software judges
the caller number in the incoming trunk call. It is available only when Function code
contains Judge caller type option. If the parameter is not specified, the call processing
software judges the caller number in the incoming trunk call in the data tables of all
WAC groups.
[User type]
It specifies the rule followed by the call processing software to judge the caller type. For
example, if you select WAC user for User type, the call processing software judges
whether the caller in the incoming trunk call is a WAC subscriber defined by the local
office. It is available only when Function code contains Judge caller type option.
14.2.4 Adding Trunk Discrimination Group

Related commands
Command
Function
ADD TGDSG
To add trunk discrimination group
RMV TGDSG
To remove trunk discrimination group
MOD TGDSG
To modify trunk discrimination group
LST TGDSG
To list trunk discrimination group
In the SoftX3000 (V300R001), you can set caller discrimination group number for
different trunk groups separately with ADD N7TG and ADD N1TG. In V300R002 or
later versions of the SoftX3000, you can only set caller discrimination group number for
all trunk groups with ADD TGDSG.

It specifies the group number of the trunk group for which caller discrimination group
number is to be set. It must have been defined in ADD N7TG and ADD N1TG before
being referenced here. The following is the configuration guideline:

14-18

z
The SIP trunk and H.323 trunk do not support caller discrimination group
temporarily.
The caller discrimination group only functions in the incoming trunk group or
bi-directional trunk group. Errors may occur to the system if an outgoing trunk
group number is inputted.
Before using the caller discrimination group, you should set the parameters [Can
request caller number] and [Whether request caller number] in the corresponding
trunk group as Yes with the commands MOD N7TG and MOD N1TG. Otherwise,
errors may occur.
[Caller category]
It specifies the category of the caller number to be discriminated. Its value ranges from
0 to 254. By default, it is set to 254, which is a wildcard character indicating all types.
Usually, the default value is used. If there is a special requirement, for example, it is
only necessary to discriminate the numbers of ordinary subscribers, please contact
Huawei technical support personnel.
When the call processing software discriminates a caller number, the option All types
enjoys the lowest priority if caller category of several pieces of caller number
discrimination data matches the current call. That is, the system matches the other
options as prior.
It specifies the caller discrimination group number when it is necessary to discriminate
the caller number in an incoming trunk call. It is available to incoming trunks only. Set
z
65535 indicates no discrimination.
Other values must have been defined in ADD CLRDSN before being referenced
here.
If you enter a value other than 65535, the trunk group will reference the specified
caller discrimination group and the one numbered 65534 at the same time. If two
discrimination groups have the same caller number record, the one in the
specified caller discrimination group will be referenced as prior.
14.2.5 Setting Inter-Group Call Barring Indication

I. Related commands
Command
Function
SET GRPAC
To set inter-group call barring indication
RMV GRPAC
To remove inter-group call barring indication
LST GRPAC
To list inter-group call barring indication

14-19


Inter-group call indication defines the call barring relationship between the caller and
callee barring groups. During the initialization process of the system, the system
presets six default pieces of call barring data pertaining to black and white lists, which
cannot be modified. If you want to define other call barring relationship, you must set
inter-group call indication using SET GRPAC.

[Source call barring group number]
This parameter specifies the caller barring group number in the inter-group barring
relationship. The value range is 0 to 65534. 65534 is a wildcard character.
The caller barring group number typed here can either be an undefined barring group
number or a barring group number that has been defined in the ADD CLRDSN
command (but without parameter referencing relationship).
[Destination call barring group number]
This parameter specifies the callee barring group number in the inter-group barring
relationship. The value range is 0 to 65534. 65534 is a wildcard character.
The callee barring group number typed here can either be an undefined barring group
number or a barring group number that has been defined in the ADD CLRDSN
command (but without parameter referencing relationship).
[Call indication]
This parameter specifies the relationship between the caller and callee barring groups:
allowed or barred.
14.2.6 Adding Called Number Barring Group

Related commands
Command
Function
ADD CLDGRP
To add called number barring group
RMV CLDGRP
To remove called number barring group
MOD CLDGRP
To modify called number barring group
LST CLDGRP
To list called number barring group
Notes of configuration

14-20

Called number barring is applicable to calls made from local office subscribers defined
in the caller barring group to an outgoing call prefix defined in the called barring group.
By default, when you add a call prefix using the ADD CNACLD command, the system
automatically defines the subscribers with that call prefix as the ordinary called barring
group (65534) subscribers. According to the black & white lists, the subscribers of the
ordinary caller barring group (65534) can dial this call prefix if they have the
corresponding call-out authority.
However, limited by the call-out authorities, the system cannot distinguish further
classified call prefixes. For example, if 500 call prefixes in an office are set with the
Local call authority, all subscribers with the Local call authority can dial all 500
prefixes if call barring is implemented according to call authority only. This cannot meet
the demand of carriers on controlling the call-out authority of a certain type of callers,
for example, public telephone subscribers.
If you want to further classify call prefixes, define the corresponding outgoing call prefix
in the black list, the white list, or other ordinary call barring groups with the ADD
CLDGRP command. However, in actual application, you need to set different call
barring policies in order to simplify call barring data configuration. For example,
suppose there are 500 call prefixes in an office are set with Local call authority.
For a certain type of subscribers in the caller barring group A, if the number of local
call prefixes that they can dial is less than that of the prohibited call prefixes, you
need to define the allowed call prefixes into a called barring group B, and then use
SET GRPAC to define call barring as follows:
Caller barring group number
Called barring group number
Call indication
Calls allowed
65534
Calls prohibited
For a certain type of subscribers in the caller barring group A, if the number of local
call prefixes that they can dial is more than that of the prohibited call prefixes, you
need to define the prohibited call prefixes into a called barring group B, and then
use SET GRPAC to define call barring as follows:
Caller barring group number
Called barring group number
Call indication
Calls prohibited
65534
Calls allowed
Parameter description
[Local DN set]

14-21

When it is necessary to define that the called subscribers with an outgoing call prefix
belong to a called number barring group, this parameter specifies the local DN set to
which the call prefix belongs. Its value ranges from 0 to 65534. 65534 is a wildcard
character and indicates that the call prefix can be used by any local DN set (but with the
lowest priority). To use other local DN set, it must have been defined in the ADD
[Called prefix]
When it is necessary to define that the called subscribers with an outgoing call prefix
belong to a called number barring group, this parameter specifies the call prefix.
Usually when a local office subscriber is called, its barring group number is callee
barring group number. Therefore, type the outgoing call prefix, instead of the local call
prefix, as the called number to be specified here.
[Group category]
This parameter specifies the category of the call barring group for the called number.
The options are
z
If you choose black list, the barring group number is 60001, which is preset by
the system automatically and cannot be modified.
If you choose white list, the barring group number is 60002, which is preset by
the system automatically and cannot be modified.
If you choose ordinary group, you must enter the customized barring group
number but cannot enter 65534.
[Called barring group number]

When ordinary group is chosen for group category, this parameter is available to
specify the specific called barring group number. The value range is 0 to 65535 except
60001, 60002, and 65534. It must be preset in SET GRPAC (non-source barring group
number); otherwise, it cannot be referenced. You can set several called numbers for
one called barring group. That is, when adding a called barring group, you can use one
called barring group number in multiple ADD CLDGRP commands.
[Called barring group name]
When ordinary group is chosen for group category, this parameter is available to
identify an ordinary barring group with a string of characters.
14.2.7 Adding Call Timingly Restriction Group

Related commands
Command
ADD LCGRP
Function
To add call timingly restriction group

14-22

Command
Function
RMV LCGRP
To remove call timingly restriction group
MOD LCGRP
To modify call timingly restriction group
LST LCGRP
To list call timingly restriction group
Notes of configuration
This command is designed to set the time-based call restriction function for Centrex
subscribers only, so that Centrex subscribers can be limited to particular call-in or
call-out authorities in specific time segments.
Parameter description
This parameter specifies the Centrex group using the time-based call restriction
function. The value range is 0 to 65534. 65534 is a wildcard character and indicates all
Centrex groups. If you want to type other Centrex group number, this parameter must
have been defined in the ADD CXGRP command before being referenced here.
This parameter uniquely identifies a call barring group using the time-based call
restriction function in the SoftX3000. Its value ranges from 0 to 65534. When you set
subscriber data with ADD VSBR, ADD MSBR, or ADD BRA, if the subscriber is a
Centrex subscriber and uses the time-based call restriction function, the barring group
number in the subscriber data will reference this parameter.
It should be noted that the call barring group number here can be configured with
multiple date categories. That is, when you add a call timingly restriction group, more
than one ADD LCGRP command can use the same barring group number.
[Date category]
This parameter specifies the date categories to which the call restriction function is
applicable. For information about date category, refer to Chapter 4, Configuring
Charging Data.
By default, the data category for Friday is category 1, not normal workday. Do NOT
treat Friday as a normal workday when using the ADD LCGRP command.
[Barring type]
This parameter specifies the specific processing mode used by the call processing
software to analyze time-based call restriction, that is, the specific constraints on the

14-23

calls of a Centrex subscriber using the call barring group in a particular time segment.
The meanings of the available options are as follows:
z
Call forwarding busy to console: In a particular time segment, when an out-group

subscriber calls a Centrex subscriber but the callee is busy, the system forwards
the call to the console.
Call forwarding unconditional to console: In a particular time segment, whenever

an out-group subscriber calls a Centrex subscriber, the system always forwards
the call to the console regardless of any cases.
Call forwarding no reply to console: In a particular time segment, when an

out-group subscriber calls a Centrex subscriber but no reply is made by the callee,
the system forwards the call to the console.
Do-Not-Disturb: In a particular time segment, a Centrex subscriber is enjoying the

do-not-disturb service and thus cannot be connected by others except the console
in the same Centrex group.
Call-out authority: In a particular time segment, the Centrex subscriber cannot use
certain call-out rights.
Call-in authority: In a particular time segment, the Centrex subscriber cannot use
certain call-in rights.
[Call-in authority]
When "call-in authority is chosen as the barring type, this parameter must be typed to
specify the Centrex subscribers call-in rights to be restricted by the system.
When "call-out authority is chosen as the barring type, this parameter must be typed to
specify the Centrex subscribers call-out rights to be restricted by the system.
[Start time 1], [End time 1]
These parameters specify the first time segment in which call restriction will be carried
out. The time is in the 24-hour indication format and the parameter in the HH&MM
format, in which HH represents hour and MM minute.
When you define multiple time segments for a call barring group in one day, there
should be no intersection between their start time points. Otherwise, errors may occur.
These parameters specify the second time segment in which call restriction will be
carried out. The time is in the 24-hour indication format and the parameter in the
HH&MM format, in which HH represents hour and MM minute.

14-24

These parameters specify the third time segment in which call restriction will be carried
out. The time is in the 24-hour indication format and the parameter in the HH&MM
format, in which HH represents hour and MM minute.
These parameters specify the fourth time segment in which call restriction will be
carried out. The time is in the 24-hour indication format and the parameter in the
HH&MM format, in which HH represents hour and MM minute.
[Start identifier]
This parameter specifies whether or not to start the call restriction function in the
preceding four time segments. If one is chosen, the call restriction function will be
started in that time segment. If not, the call restriction function will not be started in that
time segment even though the start and end time points of the segment have been
specified.

14-25

Table of Contents
15.5.6 Adding SHLR Service Configuration (Optional) ................................................ 15-56

15.6 Configuring SSAP Data ............................................................................................... 15-59
15.6.1 Overview ........................................................................................................... 15-59
15.6.2 Adding INAP over IP ......................................................................................... 15-60
15.6.3 Adding Module Dialog Number ......................................................................... 15-61
15.7 Configuring IN Announcement Data ............................................................................ 15-62
15.7.1 Overview ........................................................................................................... 15-62
15.7.2 Loading IN Voice Files to MRS ......................................................................... 15-64
15.7.3 Adding Language Kind (Optional) ..................................................................... 15-64
15.7.4 Adding Language Kind Index ............................................................................ 15-66
15.7.5 Adding Money Category (Optional)................................................................... 15-67
15.7.6 Adding Record Announcement Message ID Conversion (Optional)................. 15-68
15.7.7 Adding Mapping between Message ID and Tone ID (Optional) ....................... 15-69
15.8 Special Configuration Commands ............................................................................... 15-70
15.8.1 Adding IN Service Special Signaling................................................................. 15-70
15.8.2 Adding Caller Description of Local IN Call ........................................................ 15-71
15.8.3 Adding Network Access Code........................................................................... 15-72

ii

Chapter 15 Configuring IN Service Data

Intelligent Network (IN) service data defines related parameters for interconnection
between the SoftX3000 and the Service Control Point (SCP), including charging class,
Detection Point (DP) number, service key, and database number. To configure IN
service data, the office data, signaling data, and number analysis data must have been
Start
Equipment data
Trunk data
Office data
Number analysis
Charging data
Subscriber data
MG data
Centrex data
MRS data
Call barring data
Protocol data
IN service data
Signaling data
Other service data
Routing data
Other application
data
End

Because multiple commands are involved in the process of configuring IN service data,
the configuration process will be divided into the following sub-processes for easy
description and understanding purposes:
1)
Configuring IN charging data: Including charging discount and charging class.
2)
Configuring DP, SCP and SSP data: Including DP number, service key, SCP
physical address, and SSP physical address, used for interconnection between
the SoftX3000 and the SCP.
3)
Configuring SSAP data: Including INAP over IP data and module dialog number.

15-1

4)
Configuring IN announcement data: Including currency type and language type

related to IN announcements.

15.1.1 Architecture of Standard IN
A standard IN is structured with Service Switching Point (SSP), Service Control Point
(SCP), Service Data Point (SDP), Signaling Transfer Point (STP), Intelligent Peripheral
(IP), Service Management System (SMS), and Service Creation Environment Point
(SCEP). The architecture of the IN is illustrated in Figure 15-2.
SCEP
SMS
SCP
SDP
M3UA
No.7
IP network
No.7
M3UA
STP
SSP
IP
Metropolitan
Area Network
SIP
Phone
TMG
AMG
H.323
Phone
Figure 15-2 Architecture of standard IN
I. SSP
The SSP interfaces the IN with the Public Switched Telephone Network (PSTN), the
Integrated Services Digital Network (ISDN), and the Global System for Mobile
communications (GSM). The SSP provides functions for access to the set of IN
capabilities and implements the Service Switching Function (SSF) and the Call Control
Function (CCF). The SSP is responsible for detecting IN service requests,
communicating with the SCP, responding to received SCP requests, and allowing the
service logics in the SCP to affect the call processing.

15-2

The SoftX3000 supports the Intelligent Network Application Protocol (INAP) and can
act as an SSP in the standard IN. INAP signaling messages between the SoftX3000
and the SCP can be carried either by the No. 7 signaling network (MTP links), that is,
INAP/TCAP/SCCP/MTP, or by the IP signaling network (M3UA links), that is,
INAP/TCAP/SCCP/M3UA/SCTP/IP.
II. SCP
The SCP is usually integrated with the SDP as the core of the IN. The SCP
accommodates subscriber data and service logics. The functions of the SCP are to
receive query information from the SSP and query the database and then conduct a
variety of code translations. In addition, the SCP can start appropriate service logics
based on the call events reported by the SSP. According to the service logics, the SCP
sends call control instructions to the corresponding SSP for further actions, thus
achieving various intelligent calls. Control functions regarding all services provided by
the IN are built in the SCP. The SCP and the SSP communicate with each other through
the standard IN interface protocol (INAP).
III. STP
The STP is actually a component of the SS7. In the traditional IN, the STP is
responsible for implementing the function of transferring signaling messages between
the SSP and the SCP.
IV. IP
The IP provides specialized resources for assisting in implementing IN services,
including Dual Tone Multi-Frequencies (DTMF) digit collection, audio signal generation,
announcement signal transmission, and voice synthesis. The IP is responsible for the
allocation, control, and management of the various specialized resources. Along with
other entities in the network, the IP implements the Service Resource Function (SRF)
and maintains and manages the resources.
Either a Media Resource Server (MRS) embedded in the SoftX3000 or a physically
separate device MRS6000 interconnects with the SoftX3000 through the MGCP
protocol. Either can act as the IP in the architecture of the IN.
V. SMS
The SMS includes the Service Management Point (SMP) and its client Service
Management Access Point (SMAP). The SMAP provides an operation interface to the
SMP.
The SMP manages the life cycle of services, such as storing service data, loading
activated services, providing an interface for subscribing services. For example,
Huawei subscribes an 800 service, and an interface is available to specify the free
phone number, the inquiry password, and other related data. In addition, the SMP
provides network management functions (in terms of security, performance,
15-3

configuration, and account), as well as offering service related network management

on the IN. The SMP provides an interface to the settlement center to deliver bills
collected through the SCP from the SSPs, so that the settlement center can sort the
bills in a centralized way and share consumed fees among different service providers.
VI. SCEP
The SCEP is used to create data and logic procedures for a new service, including an
edit creator and an emulated test environment. The edit creator is a graphical editor
where procedure figures are drawn and service related database and voice are defined.
Those contents are created in a file and then loaded to the emulated test environment
for test simulation. After no errors are found during the test simulation process, the file
will be loaded to the real operating environment. The SCEP is relatively independent
and is not connected to other devices unless in case of a service transfer in which it is
connected to the SMP to transfer service files to the SMP.
15.1.2 Architecture of Local IN

Local IN is composed of Service Switching Access Point (SSAP), Service Management
Control Point (SMCP), Service Management Access Point (SMAP), and Service
Creation Environment Point (SCEP). See Figure 15-3 for the architecture.
SSCP
SMAP
SMCP
INAP/TCP/IP
SCEP
SSAP
Metropolitan
Area Network
SIP
Phone
AMG
TMG
H.323
Phone
Figure 15-3 Architecture of local IN

15-4

As shown in Figure 15-3, SSAP and SMCP are combinedly called Service Switching
Control Point (SSCP) sometimes. SSCP, as the core component in a local IN,
accomplishes such functions as service switching, control, and management.
When the SoftX3000 serves as an SSAP in a local IN, the IP signaling interfaces (that is,
the FE ports) for interconnection with the SMCP are provided by the HSCI instead of
the IFMI. In actual networking, the IP signaling interfaces for interconnecting with the
SMCP are led from 0#LAN Switch and 1#LAN Switch in the integrated configuration
cabinet, for the HSCI in each frame is connected to 0#LAN Switch and 1#LAN Switch
through internal Ethernet cables.
I. SSAP
SSAP is the connection point between PSTN/ISDN and SMCP, implementing Service
Switching Function (SSF), Call Control Function (CCF), and Signaling Access Function
(SAF). SSAP detects IN service requests, communicates with SMCP, responds to the
requests from SMCP, and allows the service logic in SMCP to affect call processing.
z
SSAP communicates with SMCP through TCP/IP, and adopts the standard INAP
for applications. It processes IN calls under the control of the service logic in
SMCP.
Compared with SSP in a standard IN, SSAP supports SAF besides all SSP
functions.
II. SMCP
SMCP offers all functions of SCP and SMP in a standard IN, implementing Service
Management Function (SMF), Service Control Function (SCF), and Service Data
Function (SDF).
1)
SMF includes Network Management Function (NMF), Service Management

Access Function (SMAF), and Service Management Sub-Function (SMSF) of IN.
NMF manages the physical network composed of IN functional entities, including

network resource configuration, equipment state monitoring, and fault removal
functions.
SMAF provides GUI for IN service administrator and IN service subscribers to

access SMSF/NMF.
SMSF manages the whole life cycle of IN services and that of IN service instances
applied by IN service subscribers.
2)
SCF invokes and implements service logic, accesses SSAP, and processes IN call
requests from SSF and the related events.
3)
SDF manages subscriber data and service data, such as charging data, service
state, performance management, configuration management, fault management,
accounting management, and security management.

15-5

III. SMAP
SMAP in a local IN has the same functions as that in a standard IN.
IV. SCEP
SCEP in a local IN has the same functions as that in a standard IN.
15.1.3 IN Charging Principles

Charging an IN call can be implemented either on the SSP side or on the SCP side. In
actual applications, charging is usually implemented on the SSP side.
I. Architecture of IN charging
A complete architecture of IN charging is illustrated in Figure 15-4. If service settlement
is not required in an IN service, the SCP unnecessarily delivers collected bills to the
SMP through which the bills will be transferred to the settlement center.
Settlement center
SMP
Charging
management
information
Bills
Settlement results
and non-local bills
SCP
Charge
details
Charge
reports
SSP
Bills
Billing center
Figure 15-4 Architecture of IN charging

In the architecture of IN charging, the purposes of the various functional entities are as
follows:
z
SSP: To generate charge reports and IN service bills, and then deliver the charge
reports to the SCP and the IN service bills to the local billing center.
SCP: To control the charging at the SSP according to the related intelligent service
logics.
SMP: To send charging management information to the SCP, and deliver

non-local bills to the settlement center for settlement processing.
Settlement center: To settle the consumed fees regarding both local and non-local
bills, sort the bills, and send them along with the settlement results to the related
billing center.

15-6

Billing center: To generate the final bills available for consumers with the various
call records into account including non IN-based call records, local IN-based
records, and settlement details (sent from the settlement center).
II. IN charging procedure

A typical IN charging procedure implemented, for example, on the SSP side is
illustrated in Figure 15-5.
SCP
SSP
Service logic
Start to charge
Obtain
charge result
Apply Charge
Apply Charge Report
Start to charge
Generate
charge report
Figure 15-5 Charging procedure between SCP and SSP

1)
After the SSP receives an IN-based call and completes the interaction with the
associated user under the control of the SCP, the SCP initiates an Apply Charge
operation and sends an apply charge INAP message to the SSP, requesting the
SSP to generate a call record. This INAP message carries a key charging element,
charging class, for the SSP.
2)
Upon receipt of the apply charge, the SSP looks up a matching record in the local
database according to the charging class parameter carried in the request, and
sets the corresponding tariff and discount information based on the charging class.
Subsequently the SSP starts a charging following the instructions in the apply
charge request. After the completion of the charging, the SSP provides an Apply
Charge Report operation for the SCP and sends the charge results to the SCP.
3)
Upon receipt of the apply charge report from the SSP, the SCP saves the charge
results in its database and generates bills according to the results. Subsequently
the SCP processes the charge results, for example, reduces consumed fee from
the associated account card.
15.1.4 Recorded Announcement Message ID

To play back a recorded announcement in an IN-based service, the SCP notifies the
SSP, through an INAP message, of the message ID which identifies the associated
announcement. The message ID is composed of three parts, namely service key,
language position, and recorded announcement serial number. Together they identify a

15-7

unique recorded announcement, to instruct the SSP to correctly operate the resources
of the recorded announcements that are stored on the IP and thus implement the
announcement playback function required by the IN service (that is, playing a
designated announcement in a specified language to the user).
Coding format for recorded announcement message IDs is as follows:
8 bits
8 bits
16 bits
Service key
Language position
Recorded announcement serial number
I. Service key
Different from other service keys you may see, the service key present in a recorded
announcement message ID is an 8-bit field, used to identify the type of the IN service
with which the recorded announcement in the message ID are associated. Taking an
SCP device of Huawei as an example, the correspondence between the service keys in
the recorded announcement message IDs and the IN services is shown in Table 15-1.
Table 15-1 Correspondence between service keys and IN services
Service key (hexadecimal
number)
Corresponding IN service
01
Account Card Calling (ACC)
02
Free PHone (FPH)
03
Virtual Private Network (VPN)
04
Universal Personal Telecommunication (UPT)
05
Televoting (VOT)
06
Pre-Paid Service (PPS)
07
Mass Calling (MAS)
08
Number Portability (NP)
09
ADvertisement (AD)
1A
Universal Card Service (UCS)
FC
Internet Personal Number (IPN)
II. Language position

The language position in a recorded announcement message ID constitutes an 8-bit
field, used to specify the language in which the recorded announcement in the
message ID will be played. Taking an SCP device of Huawei as an example, the
definitions of the language codes are shown in Table 15-2.

15-8

Table 15-2 Language code definitions

Code (hexadecimal number)
Language
00
Chinese
01
English
02
Chinese (Cantonese)
03
Czech
04
Danish
05
Dutch
06
Finnish
07
French
08
German
09
Greek
0A
Hungarian
0B
Icelandic
0C
Italian
0D
Japanese
0E
Korean
0F
Norwegian
10
Polish
11
Portuguese
12
Russian
13
Slovak
14
Spanish
15
Swedish
16
Turkish
17
Uzbekistan
18
Thailand
50
Siwihili
51
Arabian
52
India
53
Philippines

15-9

III. Recorded announcement serial number

The recorded announcement serial number in a recorded announcement message ID
is a 16-bit field, used to uniquely identify a recorded announcement. There is a fixed
correspondence between the recorded announcement serial numbers and the
recorded announcements. For example, in the 200 service (an ACC service), the serial
number 0001 (hexadecimal number) offers greetings to the user and "0002"
(hexadecimal number) directs the user to type an account number. Such a
correspondence is defined in the host software and you cannot modify it.
15.1.5 Naming Conventions for Intelligent Voice Files

It is helpful to learn the naming conventions for the intelligent voice files that are stored
in the hard disk of the BAM before you configure IN-based announcement playback
data.
I. When an embedded MRS in the SoftX3000 is used

When an embedded MRS in the SoftX3000 is used, the matching intelligent voice files
are stored in the D:\Data\voice in the hard disk of the BAM. The suffixes to the voice
files include .chi, .eng, and .may only, as in HW1A400001.eng, HWFC800001.chi,
and HW6100000.may. The naming conventions are shown in Figure 15-6.
HW XX XX XXXX . xxx
Suffix
Voice number
Language position
Service key
Fixed characters
Figure 15-6 Naming conventions for intelligent voice files (1)

z
Suffix: The suffix is made up of three English letters. The suffix only helps to
describe the type of the language of the voice, but it is not the basis for judging the
language when the MRS plays announcements back. .chi indicates Chinese,
.eng English, and .may Malay.
Voice number: The voice number is a 4-digit hexadecimal number, used to identify
the serial number of the voice. There is a direct one-to-one correspondence
between the voice numbers and the recorded announcement serial numbers in
the recorded announcement message IDs.
Language position: The language position constitutes a 2-digit hexadecimal

number, used to identify the language used for the voice. The language position
field is the basis for judging the language when the MRS plays announcements
back. Internal language codes of the SoftX3000 are used. There is no direct
15-10

one-to-one correspondence between them and the language position parameter

in the recorded announcement message IDs. Currently, 10 means Malay, 40
means English, and 80 means Chinese. To ensure the normal playback function,
you need to set the mapping between the language position parameter in the
recorded announcement message ID and that in the tone file with the
corresponding MML command.
z
Service key: The service key is a 1-digit or 2-digit hexadecimal number, used to
identify the IN service with which the voice is associated. The service key field is
the basis for judging the service when the MRS plays announcements back. There
is a direct one-to-one correspondence between the service keys and the service
keys in the recorded announcement message IDs. For example, 3 indicates VPN,
6 PPS, 1A UCS, and FC IPN.
Note:
When the service key in a voice file is one hexadecimal digit, the corresponding service
key in the recorded announcement message ID is 0+ one hexadecimal digit. For
example, if the service key in a voice file is 8, the corresponding service key in the
recorded announcement message ID is 08.
Fixed characters: These fixed characters represent that the voice files are
recorded by Huawei.
II. When a physically separate MRS6000 is used

When a physically separate MRS6000 is used, the matching intelligent voice files are
stored in the D:\Data\ voice\fin in the hard disk of the BAM. Moreover, all Chinese
voices are stored in the chi subfolder and all English voices in the eng subfolder. The
suffix to the various voice files is .wav only, as in 1A800001_pcm_g729c.wav and
FC40008A_pcm_g729c.wav. The naming conventions are shown in Figure 15-7.
XX XX XXXX _pcm_g729c . wav

Suffix
Fixed characters
Voice number
Language position
Service key
Figure 15-7 Naming conventions for intelligent voice files (2)

For the meanings of the fields, refer to the preceding section.

15-11

15.2 Configuring IN Charging Data

15.2.1 Overview
IN charging data defines IN charging related information used for interconnection
between the SoftX3000 and the SCP, such as charging discount, charging class, and
charging rounding. IN charging data is relatively independent and has no parameter
referencing relationship with other data.
II. Preparations
Before configuring IN charging data, make sure that all preparations are done as
SN
Item
Remark
Charging class

between the SoftX3000 and the SCP
Planning charging discount

index
Determining discount rules according to IN

charging policies

Table 15-4 lists the general steps for configuring IN charging data.
Step
Description
Command
Add holiday tariff discount (optional)
ADD HLDDIS
Add weekday tariff discount (optional)
ADD WEKDIS
Add normal tariff discount (optional)
ADD NRMDIS
Add conversation duration discount (optional)
ADD TIMEDIS
Add charging class
ADD CHGCLS
Add charging property (optional)
ADD CHGPRO
Add charging rounding (optional)
ADD CHGRND

you configure IN charging data.

15-12

ADD HLDDIS
[Discount index]
[Year]
[Month]
ADD WEKDIS
[Discount index]
[Week]
[Start time]
ADD CHGCLS
[Charge class]
ADD NRMDIS
[TA charge rate]
[Discount index]
(Optional)
[Start time
[End time]
[Discount index]
ADD CHGRND
[Service key]
ADD TIMEDIS
[Charge class]
[Discount index]
[Allowed PB
overdraft times]
[Conversation duration
15.2.2 Adding Holiday Tariff Discount (Optional)

I. Related commands
Command
Function
ADD HLDDIS
To add holiday tariff discount
RMV HLDDIS
To remove holiday tariff discount
MOD HLDDIS
To modify holiday tariff discount
LST HLDDIS
To list holiday tariff discount

data configuration.
If it is necessary to give a discount on IN-based calls to consumers on some special
days, for example, on the National Day or the Labor Day, you can add the holiday tariff
discount related to IN charging using the ADD HLDDIS command.
15-13


[Discount index]
It uniquely identifies an IN charging discount in the SoftX3000. The value range is 1 to
65534. The configuration principles of this parameter are as follows:
z
The same discount index can be configured for several discounts. That is, when
you add an IN charging discount by using the ADD HLDDIS, ADD WEKDIS, ADD
NRMDIS, or ADD TIMEDIS command, you can use the same tariff discount index
in multiple settings of one or several commands.
65534 is a wildcard and indicates that the discount index can be used by any
charging class (but with the lowest priority). That is, a charging class with a
non-65535 discount index can use the discount with index 65534, in addition to the
discount with the specified index number. In case that both the discount indexes
have a record regarding the same time segment, the record in the discount with
the specified index number is preferred.
[Year], [Month], [Day]

These parameters specify the specific holiday date on which the discount is used.
[Start time], [End time]
These parameters specify the specific time segment of the specified date during which
the discount is used. The time format is 24-hour indication system and the parameter
format is HH&MM&SS.
It should be noted that the end time point is excluded in the discount time segment. For
example, if you set these parameters to 00&00&00 and 21&00&00, the valid
discount time segment is from 00:00:00 to 20:59:59. Discount is no longer available at
21:00:00 and later.
[Basic charging discount style]
This parameter specifies in which way the basic tariff in conversation fees is discounted.
z
Discount by percent: The basic tariff is discounted by a percentage. The typed

discount value divided by 100 is the corresponding discount percentage. The
original basic tariff multiplied by that discount percentage is the new basic tariff
that customers actually enjoy.
Discount by sum: The new basic tariff that customers actually enjoy is typed
directly. That is, the new basic tariff is equal to the typed value.
Discount by conversation duration: The original basic tariff remains unchanged.

Discount is achieved by modifying the values of the metering TA and TB. The new
TA after discount is equal to the original TA multiplied by the discount value, and
the new TB after discount is equal to the original TB multiplied by the discount
value.

15-14

z
Discount by real time: The original basic tariff remains unchanged. Discount is
achieved by modifying the values of the metering TA and TB. The new TA after
discount is equal to the new TB after discount and also equal to the discount value.
Controlled by Bit 6 of the software parameter SSP internal parameter 1 (P77), the
default discount style may be discount by percent or discount by sum. Discount by
conversation duration and Discount by real time are invalid in normal cases. If you
modify the value of Bit 6 of SSP internal parameter 1 (P77) to 0, Discount by
conversation duration and Discount by real time become valid and the other two
styles are invalid.
[Basic charging discount]
This parameter specifies the discount value for the basic tariff in the discount time
segment. For different discount styles, the parameter meanings and corresponding
value ranges are different.
z
Discount by percent: The unit is %. The value range is 0 to 100. If you type 100, no
discount is provided for consumers. If you type 60, there is 40% off.
Discount by sum: The value range is 0 to 2147483647. If you type 0, the basic tariff
is provided free of charge. If you type 15, the new basic tariff is 0.15 dollars after
the discount. It should be noted that the new basic tariff after the discount cannot
be more than the original one. Otherwise, the system charges consumers based
on the original basic tariff as no discount is provided.
Discount by conversation duration: The value is an integer, ranging from 1 to 3. If

you type 1, no discount is provided for consumers. If you type 2, the original TA
and TB values are doubled after the discount. That is, the available conversation
duration for consumers doubles the original duration if the tariff keeps unchanged.
Discount by real time: Its value ranges from 0 to 1048575in unit of 10 milliseconds.
If you type 0, free of charge is provided. If you type 12000, the new TA and TB
values after the discount are both 120 seconds. Note that the new TA and TB
values after the discount cannot be smaller than the TA and TB values defined in
the charging category; otherwise, it is equivalent to no discount and the system will
charge calls according to the original basic tariff.
[Additional charging discount style]

This parameter specifies in which way the additional tariff in conversation fees is
discounted. The meanings of the available options are as follows:
z
Discount by percent: The additional tariff is discounted by a percentage. The typed

discount value divided by 100 is the corresponding discount percentage. The
original additional tariff multiplied by that discount percentage is the new additional
tariff that customers actually enjoy.
Discount by sum: The new additional tariff that customers actually enjoy is typed
directly. That is, the new additional tariff is equal to the typed value.

15-15

Depending on your charge policies, set information about additional fee. Usually the
additional tariff is discounted by a percentage.
[Additional charging discount]
This parameter specifies the discount value for the additional tariff in the discount time
segment. For different discount styles, the parameter meanings and corresponding
value ranges are different.
z
Discount by percent: The unit is %. The value range is 0 to 100. If you type 100, no
discount is provided for consumers. If you type 60, there is 40% off.
Discount by sum: The value range is 0 to 2147483647. If you type 0, the additional
tariff is provided free of charge. If you type 15, the new additional tariff is 0.15
dollars after the discount. It should be noted that the new additional tariff after the
discount cannot be more than the original one. Otherwise, the system charges
consumers based on the original additional tariff as no discount is provided.
15.2.3 Adding Weekday Tariff Discount (Optional)

I. Related commands
Command
Function
ADD WEKDIS
To add weekday tariff discount
RMV WEKDIS
To remove weekday tariff discount
MOD WEKDIS
To modify weekday tariff discount
LST WEKDIS
To list weekday tariff discount

data configuration.
If it is necessary to give a discount on IN calls to consumers on some special days in
every week, for example, on Saturdays or Sundays, you can add the weekday tariff
discount related to IN charging using the ADD WEKDIS command.
Note:
Most of the parameters in ADD WEKDIS are the same as those in ADD HLDDIS, so
this section only describes the dedicated parameters in ADD WEKDIS. For the other
parameters, refer to section 15.2.2 Adding Holiday Tariff Discount (Optional).

15-16

[Week]
This parameter specifies the week day on which the discount is used.
These parameters specify the specific time segment of the specified week day during
which the discount is used. The time format is 24-hour indication system and the
parameter format is HH&MM&SS.
15.2.4 Adding Normal Tariff Discount (Optional)

I. Related commands
Command
Function
ADD NRMDIS
To add normal tariff discount
RMV NRMDIS
To remove normal tariff discount
MOD NRMDIS
To modify normal tariff discount
LST NRMDIS
To list normal tariff discount

data configuration.
If it is necessary to give a discount on IN-based calls to consumers in a specific time
segment every day, for example, from 00:00 to 07:00, you can add the normal tariff
discount related to IN charging using the ADD NRMDIS command.
Note:
Most of the parameters in ADD NRMDIS are the same as those in ADD HLDDIS, so
this section only describes the dedicated parameters in ADD NRMDIS. For the other

These parameters specify the specific time segment every day during which the
discount is used. The time format is 24-hour indication system and the parameter
format is HH&MM&SS.
It should be noted that the end time point is excluded in the discount time segment. For
example, if you set these parameters to 00&00&00 and 21&00&00, the valid
15-17

discount time segment is from 00:00:00 to 20:59:59. Discount is no longer available at

21:00:00 and later.
15.2.5 Adding Conversation Duration Discount (Optional)

I. Related commands
Command
Function
ADD TIMEDIS
To add conversation duration discount
RMV TIMEDIS
To remove conversation duration discount
MOD TIMEDIS
To modify conversation duration discount
LST TIMEDIS
To list conversation duration discount

data configuration.
If some IN-based calls are kept so long that the duration exceeds a predefined
threshold and thus it is necessary to give a discount to consumers, you can add the
conversation duration discount related to IN charging using the ADD TIMEDIS
command.
Note:
Most of the parameters in ADD TIMEDIS are the same as those in ADD HLDDIS, so
this section only describes the dedicated parameters in ADD TIMEDIS. For the other
[Conversation duration]
This parameter specifies a duration threshold. If a call is kept so long that the duration
exceeds this threshold, the SSP will give discount to the call. The value range is 1 to
65534, and the unit is minute.

15-18

15.2.6 Adding Charging Class

I. Related commands
Command
Function
ADD CHGCLS
To add charging class
RMV CHGCLS
To remove charging class
MOD CHGCLS
To modify charging class
LST CHGCLS
To list charging class

[Charge class]
This is one of the interconnection parameters between the SoftX3000 and the SCP,
used to uniquely identify an IN charging mode. The value range is 1 to 1000. Whenever
there is an IN-based call originated at the SSP, the SCP delivers the charging class
parameter to the SSP through an INAP message, directing the SSP to charge the
IN-based call according to the charging mode (such as metering mode, basic tariff, and
discount style) defined by the charging class.
[TA charging rate]
This parameter specifies the consumed fee for every meter count during the initial
metering time interval. The value range is 0 to 2147483647.
[PB independent tariff]
This parameter specifies the consumed fee for every meter count during the metering
time interval. The value range is 0 to 2147483647.
[Initial metering time interval]
This parameter specifies the time interval for calculating conversation fee for the first
time. The value range is 0 to 1048575. The unit is 10 milliseconds.
[Initial metering pulse count]
This parameter specifies the metering count during the initial metering time interval.
[Metering time interval]
This parameter specifies the time interval for calculating conversation fee for the
second time and later. The value range is 0 to 1048575. The unit is 10 milliseconds.
[Metering pulse count]
This parameter specifies the metering count during the metering time interval. For
example, if the preceding four parameters are set to 18000/2/6000/1, it indicates that
the meter counts twice during the initial 180 seconds and then the meter counts once
every 60 seconds.
15-19

[Discount index]
This parameter specifies the discount index which is applicable to the charging class
when it is necessary to give a discount on IN-based calls. The configuration principles
of this parameter are as follows:
z
65535 indicates not to use the discount.
If you type another discount index, this parameter must have been defined in the
ADD HLDDIS, ADD WEKDIS, ADD NRMDIS, or ADD TIMEDIS command before
If the typed discount index is configured with several types of discounts, the system
complies with the following principles to reference a suitable discount.
z
For holiday, weekday, and normal tariff discounts, the start conversation time
(including date and time) is the only basis to trigger a discount. If the start
conversation time of a call satisfies more than one discount criterion, the system
will reference the piece of data with the lowest discount.
For conversation duration discount, the conversation duration is the only basis to
trigger a discount in essence. In addition, a conversation duration discount can be
used even though consumers are enjoying a holiday, weekday, or normal tariff
discount. If a call only satisfies the conversation duration discount criterion, the
final discount percentage that customers enjoy is equal to the conversation
duration discount percentage. If a call satisfies the duration discount criterion and
the start conversation time also satisfies a tariff discount criterion, the final
discount percentage that consumers enjoy is equal to the conversation duration
discount percentage multiplied by the tariff discount percentage.
[Minimum charging time]

This parameter specifies the shortest conversation duration for charging an IN-based
call. If an IN-based call does not last for the defined minimum charging time, the system
will not charge the call. The value range is 0 to 65534, and the unit is second.
[Zoom factor]
It defines the variation ratio of charging rate. It affects both TA charging rate and PB
independent tariff. It ranges from 1 to 2147483647. The default value is 1.
z
Actual TA charging rate = configured TA charging rate / zoom factor
Actual PB independent tariff = configured PB independent tariff / zoom factor
15.2.7 Adding Charging Property (Optional)

I. Related commands
Command
Function
ADD CHGPRO
To add charging property
RMV CHGPRO
To remove charging property

15-20

Command
Function
MOD CHGPRO
To modify charging property
LST CHGPRO
To list charging property

data configuration. If it is necessary to deploy one of the following applications, you can
add the charging property related to IN charging using the ADD CHGPRO command.
z
When the SoftX3000 acts as an SSP and functions as a transit office on the
network, for incoming IN-based calls, it is required for the local office to send
answer signal, no charge to the originating office (the calling side). By default,
answer signal, charge is sent.
For the PPS service, when a subscriber does not have enough balance in the PPS
card to maintain the on-going call, it is required to manually configure at the SSP
the start time to play an announcement to notify the subscriber of the
out-of-balance state before the call is terminated. By default, the SCP delivers the
start time value to the SSP through an INAP message.

[Local DN set]
This parameter specifies the local DN set to which the IN call prefix with the
to-be-added charging property belongs. This parameter is defined in the ADD LDNSET
[Callee prefix]
This parameter specifies the IN call prefix for which the charging property is to be
added. This parameter is defined in the ADD CNACLD command and referenced here.
[Charging-free flag]
This parameter specifies whether or not to send answer signal, no charge from the
local office to the originating office (the calling side) for incoming IN-based calls when
the SoftX3000 acts as an SSP and functions as a transit office on the network.
z
The default setting is No, indicating "answer signal, charge will be sent from the
local office to the originating office.
If you set it to Yes, "answer signal, no charge will be sent from the local office to
the originating office.
The setting of this parameter is applicable to both single-stage and dual-stage dialing
IN services.
[Duration of notify tone]

15-21

For the PPS service, when a subscriber does not have enough balance in the PPS card
to maintain the on-going call, it is required to manually configure at the SSP the start
time to play an announcement to notify the user of the out-of-balance state before the
call is terminated. This parameter is used to specify the announcement start time. The
value range is 0 to 254. The unit is second. Set this parameter by the following
principles:
z
If you type 0, it indicates that the setting of this parameter is invalid. The
associated time value is delivered by the SCP to the SSP through an INAP
message.
If you type a number rather than 0, it indicates that the setting of this parameter is
valid. The announcement start time value delivered by the SCP to the SSP
through an INAP message is invalid.
15.2.8 Adding Charging Rounding (Optional)

I. Related commands
Command
Function
ADD CHGRND
To add charging rounding
RMV CHGRND
To remove charging rounding
MOD CHGRND
To modify charging rounding
LST CHGRND
To list charging rounding

data configuration. If it is necessary to deploy one of the following applications, you can
add the charging rounding related to IN charging using the ADD CHGRND command.
z
There may be such cases that a subscriber does not have enough balance in the
PPS card to maintain the duration to the next TB. Therefore, it is necessary to
configure some overdraft policies so that user can continue the call until all the
balance is used up.
It is required for the SSP to round off the consumed calling fee during an IN
charging process. By default, the system does not perform any rounding
operation.

[Service key]
This parameter specifies the service key of the IN service for which the charging
rounding is to be added. This parameter is defined in the ADD TDPCFG command and
referenced here.
15-22

[Charging class]
This parameter specifies the class of the IN charging for which the charging rounding is
to be set. This parameter is defined in the ADD CHGCLS command and referenced
here.
[Allowed PB overdraft times]
If a subscriber does not have enough balance in the PPS card to maintain the duration
to the next TB, this parameter specifies the PB metering count allowed by the SSP to
continue the conversation. That is, the allowed pulse times to be overdrawn. The
default value is 0, indicating that overdraft is not permitted. If it is set to other values,
when the overdrawn conversation is terminated, the balance of the account of the user
should be a minus number.
[Maximum rounding fee]
This parameter specifies the maximum rounding fee during an IN charging process.
The value range is 0 to 100. Controlled by Bit 8 of the software parameter SSP internal
parameter 1 (P77), this parameter is invalid by default.
If you modify the value of Bit 8 of SSP internal parameter 1 (P77) to 0, the SSP will
perform a rounding operation on the total conversation cost to be reported. The part
which is less than the maximum rounding fee multiplied by 0.5 will be ignored. For
example, you define the maximum rounding fee to 10 (0.10 dollars). If the cost of a call
is 12.53 dollars exactly, the SSP will round the cost down to 12.50 dollars. If the cost of
a call is 12.56 dollars exactly, the SSP will round the cost up to 12.60 dollars.
15.3 Configuring DP Data

15.3.1 Overview
The DPdata defines information about INAP signaling for interconnection between the
SoftX3000 and the SCP, including access code, DP number, and service key. During
the process of IN service data configuration, some parameters defined when you
configure number analysis data will be referenced during the configuration of DP data.
parameter referencing relationship between DP, SCP and SSP data and other data,
see Table 15-5.

15-23

Table 15-5 Parameter referencing relationship between DP, SCP and SSP data and
other data
Input parameter
Name
Output parameter
Defined in
Number
data
IN service access code
Name
analysis
Referenced in
/
II. Preparations
Before configuring DP data, make sure that all preparations are done as specified in
Table 15-6.
SN
Item
Remark
Access code

the SoftX3000 and the SCP
DP number

Service key


Table 15-7 lists the general steps for configuring DP data.
Step
Description
Command
Set INAP protocol type
SET INAPTP
ADD CNACLD
Add access code
ADD ACCODE
Add TDP configuration
ADD TDPCFG
Set DP trigger configuration (optional)
SET DPTCFG
Add mapping between service key and event code
ADD SK2EC
Add IN service restriction (optional)
ADD SRVRST

15-24


you configure DP data.
ADD CNACLD
[Local DN set]
[Call prefix]
[Service category]
ADD ACCODE
[Access code]
[Database start position]
[Database field length]
ADD TDPCFG
[DP number]
[Access code]
[Service key]
ADD SRVRST
[Outer layer IN service
key]
[Inner layer IN service
key]
[Restriction relationship]
15.3.2 Setting INAP Protocol Type (Optional)

I. Related commands
Command
Function
SET INAPTP
To set INAP protocol type
LST INAPTP
To list INAP protocol type

15-25


data configuration.
By default, the SoftX3000 can interwork with C-INAP-based SCP only. To set the
SoftX3000 to interwork with SCPs of other INAP standards, such as R-INAP, you must
use SET INAPTP to set the INAP protocol type.

[INAP type]
It is one of the parameters used for the interworking between SoftX3000 and SCP. It
selects a country whose national INAP standard is to be complied with. This parameter
must be correctly configured, or the SoftX3000 will not work with the SCP properly.
[Application context]
It is one of the parameters used for the interworking between SoftX3000 and SCP. It
defines whether the SoftX3000 uses the application context defined in C-INAP. When
the SoftX3000 uses C-INAP, you must set the parameter to No; otherwise, set it to
Yes.
By default, if you have not used SET INAPTP to change the INAP protocol type, the
application context of C-INAP is used.

I. Related commands
Command
Function
ADD CNACLD
To add called number analysis data
RMV CNACLD
To remove called number analysis data
MOD CNACLD
To modify called number analysis data
LST CNACLD
To list called number analysis data

When using the ADD CNACLD command to add an IN call prefix, pay attention to the
following points:
1)
The service category parameter in the command is set according to the type of
the IN service.
If the IN service is an ordinary IN service, such as FPH, ACC, or NP, intelligent

service" is selected.
If the IN service is a specialized IN service, such as WAC, special access code is

selected.
15-26

2)
The service attribute parameter in the command is set according to the type of
the IN service.
If the IN service has a fixed-length called number, such as FPH, dual-stage dialing
IN card number service (for example, ACC), or NP incoming service (with an
access code 500), intelligent service is selected.
If the IN service has a variable-length called number, such as single-stage dialing

IN card number service (for example, APS), or NP outgoing service (with an
access code 501), special function number is selected to accelerate the
connection speed.
Note:
For the single-stage dialing IN service, both the preceding options are available with
the following differences.
z
Intelligent service is selected. Accordingly, when the length of the dialed called
number is equal to the maximum number length, the SSP immediately triggers the
IN service. When the length of the dialed called number is greater than the minimum
number length but less than the maximum number length, the SSP waits for five
seconds and then triggers the IN service. In this case, the connection speed is slow.
Special function number is selected. As long as the length of the dialed called
number is greater than or equal to the minimum number length, the SSP triggers the
IN service without any delay.
3)
The minimum number length and maximum number length parameters in the
command are set according to the type of the IN service.
If the IN service has a fixed-length called number, such as FPH, ACC, or NP

incoming service, minimum number length and maximum number length are
set to the same value.
If the IN service has a variable-length called number, such as single-stage dialing

IN card number service (for example, APS) or NP outgoing service, minimum
number length is set to the length of the access code and "maximum number
length is set to a number as great as possible, for example, 24. The purpose is to
meet the requirement for a diversity of called number lengths.

For more information, refer to Chapter 11, Configuring Number Analysis Data.

15-27

15.3.4 Adding Access Code

I. Related commands
Command
Function
ADD ACCODE
To add access code
RMV ACCODE
To remove access code
MOD ACCODE
To modify access code
LST ACCODE
To list access code

[Access code]
used to specify the call prefix to trigger the IN service at the SSP. This parameter is
defined in the ADD CNACLD command and referenced here.
This parameter specifies the start position to pick up the database number from the
called number dialed by the subscriber in an IN call. That is, the SSP picks up a
specified length of number, from the called number, with the value on this bit as the start
digit. (The specified length is defined by the following database field length parameter.)
What is picked up is a database number. According to that database number, the SCP
configuration table in the local database is queried to find the SCP that is responsible
for processing the call. The configuration principles of this parameter are as follows:
z
If you type 0, the database number is picked up from the first digit of the called
number. Other cases are deduced in the same way. For example, if you type 2, the
database number is picked up from the third digit of the called number.
If you type 255, it indicates not to pick up the database number from the called
number. In this case, the call will be processed by the default SCP, that is, SCP
numbered 1.
Whether or not to pick up the database number from the called number depends on the
specific requirements of the particular IN service. Usually, it is unnecessary to do that
and the value 255 is set for the database start position parameter.
When the database start position parameter is not set to 255, this parameter is
available to specify, in an IN call, the length of the database number to be picked up
from the called number dialed by the subscriber.
[Service type]

15-28

This parameter defines whether an access code is used for anonymous card service.
By default, it is IN service. If an access code is used for the anonymous card service,
you must set this parameter to Anonymous card service.
15.3.5 Adding TDP Configuration

I. Related commands
Command
Function
ADD TDPCFG
To add TDP configuration
MOD TDPCFG
To modify TDP configuration
RMV TDPCFG
To remove TDP configuration
LST TDPCFG
To list TDP configuration

[DP number]
used to specify a Trigger Detection Point (TDP) at the SSP for the corresponding
service key. It indicates that the SSP will trigger the IN service at this TDP or detect call
related events in the process of an IN call.
Defined in the ITU-T Q.1214 (CS-1R), the value range of the DP number is 1 to 18
except 11. Each DP number describes an originating or terminating call model in the IN
Capability Set 1R.
DP
DP name
DP trigger criteria
The local caller picks up.
DP1
Origination_Attempt_
Authorized
DP2
Collected_Info
The local caller or the incoming trunk dials the

minimum number length of the IN call prefix.
DP3
Analyzed_Info
The local caller or the incoming trunk dials the IN

call prefix.
DP4
Route_Select_Failure
The route selection fails in the outgoing call

initiated by the local caller or the incoming trunk,
and the failure reason is a specified reason.
DP5
O_Called_Party_Busy
The callee is busy in the outgoing call initiated by

the local caller or the incoming trunk, and the
failure reason is a specified reason.
DP6
O_No_Answer
The callee does not answer in the outgoing call

initiated by the local caller or the incoming trunk,
and the failure reason is a specified reason.
The incoming trunk starts a call.

15-29

DP
DP name
DP trigger criteria
DP7
O_Answer
The local caller or incoming trunk calls the callee

and the callee answers.
DP8
O_Mid_Call
The local caller or incoming trunk calls the callee

and the callee hears the ringing tone.
DP9
O_Disconnect
A specific caller-hang-up event has occurred

during the call initiated by the local caller or the
incoming trunk.
DP10
O_Abandon
A specific caller-hang-up event has occurred

when the callee rings during the call initiated by
the local caller or the incoming trunk.
DP12
Term_Attempt_Authori
zed
The system calls a local callee of a specific call

source code, and can send him the Alerting
signal.
DP13
T_Called_Party_Busy

source code when the latter is busy, and the
failure reason is a specific reason.
DP14
T_No_Answer

source code when the latter does not answer, and
the failure reason is a specific reason.
DP15
T_Answer

source code and the latter answer the call.
DP16
T_Mid_Call

source code and the phone of the latter rings.
DP17
T_Disconnect

source code. A callee-hang-up event of a specific
reason occurs after the conversation starts.
DP18
T_Abandon
For fixed intelligent network (FIN) services, the analyzed_info call model is usually
used at the SSP side, and accordingly the DP number is 3.
If you want to use other DP numbers to trigger IN services, you must use SET DPTCFG
to set DP trigger data.
[DP criteria number]
This parameter specifies the criteria for detecting the preceding DP number. The
SoftX3000 supports seven types of DP criteria in the IN CS-1R. The DP criteria are as
follows:
z
Feature code: A vertical service code, such as a # or a two-digit or three-digit

code preceded by * or 11.
Access code: Access code (for example 800KN1N2 and 300KN1N2) for customized
numbering plan, a string of digits in a customized numbering plan that matches
access codes.
15-30

z
Callee number: A string of digits that must match the called party number, which is
either a local, national, or international E.164 number.
Trigger assigned: An indicator of the armed/disarmed status of a TDP assigned on

a line/trunk, or office basis.
Specific digit strings: A string of digits that must match collected digit strings for
numbering plans in which a variable number of digits are to be collected. It could
be zero or more digits (for example, to trigger on off-hook delay).
Specific B-channel identifier: An identifier of the specific B-channel on an ISDN

interface from which a call attempt has originated or to which a call attempt is to be
terminated.
Feature
activation
indication:
In
local
exchange
only,
feature
activation/indication on an ISDN interface or that is detected at the Mid_Call DP

(for example, hook flash, #) for ISDN and non-ISDN lines that can be sent in
conjunction with or preceding other address/digit collection.
For FIN services, an access code is usually used as the detection criterion for the DP 3.
That is, the DP criterion is set to access code.
[Access code]
When access code" is set as the DP criterion, this parameter is available to specify the
call prefix for triggering IN-based services at the SSP. This parameter is defined in the
ADD ACCODE command and referenced here.
For some special IN-based services such as NP (with access code, for example, 500 or
501), the access code is one of the interconnection parameters between the SoftX3000
and the SCP. The access code at the SSP and that at the SCP must be the same.
[Service key]
used to uniquely identify an IN service in an INAP message. Service key is a kind of
number resources for which the telecom operator has to apply to the national
administration. The access code and service key have the following correspondence:
z
One access code must only respond to one service key, but one service key may
respond to more than one access code.
An access code and the corresponding service key may be the same or be
different.
The preceding correspondence can be illustrated in Table 15-8 in which 200, 300,
17908, and 17909 are all access codes of several ACC services.
Table 15-8 Correspondence between access codes and service keys
Access code
Service key
Remark
200
200
200 card number service
300
300
300 card number service

15-31

Access code
Service key
Remark
96338
203
Dual-stage dialing IP card number service
203
203
Single-stage dialing IP card number service
[Request/Notification flag]
This parameter specifies the TDP type, Trigger Detection Point Request (TDP-R) or
Trigger Detection Point Notification (TDP-N), to trigger an IN service by the
SoftX3000. The options are
z
Request: Request indicates the TDP-R type. When the SSP sends related
information to the SCP, the SSP will perform further processing under the control
of the SCP.
Notification: Notification indicates the TDP-N type. When the SSP sends related
information to the SCP, the SSP will perform further processing by itself, not
waiting for instructions from the SCP.
For FIN services, the TDP-R type is usually selected if it is not for a special purpose.
[Auxiliary flag]
used to specify whether or not the IN service corresponding to the service key uses the
specialized resources (such as DTMF digit collector and announcements) on the IP
controlled by the local SSP (that is, the SoftX3000). Set this parameter by the following
principles:
z
If this parameter is set to NO, the specialized resources required by the IN service
are provided by the IP that is controlled by the local SSP. In this case, the local
SSP will report the InitialDP operation to the SCP to trigger the IN service.
If this parameter is set to YES, the specialized resources required by the IN

service are provided by an IP controlled by other SSP rather than the local SSP. In
this case, the local SSP will report the Assist Request Instructions operation to
the SCP to trigger the IN service. This networking model is designed to implement
the service assist capability or the service hand-off function. In this model, the
local SSP is the initiating SSP and the other SSP is an assisting SSP. The
correspondence between the initiating and assisting SSPs is defined by the SCP
through data configuration.
In normal cases, this parameter is set to NO. If it is set to YES, you must add an SCP
numbering mapping correspondence between the initiating and assisting SSPs by
using the ADD SCPMAP command. Otherwise, the normal operation of the IN service
may be affected.
[Call source code]
It defines the DP trigger condition. When a caller of the call source code initiates an IN
call, or when the callee of a call is of the call source code, the SSP will trigger the IN
15-32

service at the TDP or detect call-related events during the IN call. Here are the
configuration guidelines of the parameter:
z
The parameter must first be defined by ADD CALLSRC before it can be

referenced here.
When the DP number is used in the call model of caller, set this parameter to the
call source code of the caller
When the DP number is used in the call model of callee, set this parameter to the
call source code of the callee
65534 stands for all call source codes.

It defines the start position of the database number retrieved from the dialed callee
number. The SSP obtains the database number by cutting a certain length of digits
(defined by database field length) in the callee number starting from the database start
position. Then the SSP queries the SCP configuration table in the local office database
using the database number, and decide which SCP shall process the call. Here are the
configuration guidelines of the parameter:
z
If it is set to 0, it means that the SSP starts cutting the database number from the
first digit; if it is set to 1, the SSP starts cutting from the second digit; and so on.
If it is set to 255, it means that the SSP shall not retrieve database number from
the callee number. The call will be processed by the default SCP (SCP 1).
This parameter is required by some IN services. Generally there is no such requirement,

and it is set to 255.
It defines the digits cut from the dialed callee number for database number in an IN call.
This parameter is valid only when the database start position' is not 255.
It restricts the DP trigger conditions. When the cause of failure of the call exactly
matches the specified failure cause code, the SSP will trigger IN service at the TDP or
detect call-related events during the IN call. This parameter is valid only when DP
number is DP4, DP5, DP6, DP9, DP10, DP13, DP14, DP17, or DP18.
15.3.6 Set DP Trigger Configuration (Optional)

I. Related commands
Command
Function
SET DPTCFG
To set DP trigger configuration
LST DPTCFG
To list DP trigger configuration

15-33


data configuration.
By default, the system uses DP3 to trigger IN services. To use other DP numbers to
trigger IN services, use SET DPTCFG to modify the DP trigger configuration.

[Detect point 1] to [Detect point 18]
They define whether a specific DP can be used to trigger IN services. By default, DP3 is
used to trigger IN services. Here are the configuration guidelines of the parameter:
Defined in the ITU-T Q.1214 (CS-1R), the value range of the DP number is 1 to 18
except 11. Each DP number describes an originating or terminating call model in the IN
Capability Set 1R.
z
DP 1 Origination_Attempt_Authorized
DP 2 Collected_Info
DP 3 Analyzed_Info
DP 4 Route_Select_Failure
DP 5 O_Called_Party_Busy
DP 6 O_No_Answer
DP 7 O_Answer
DP 8 O_Mid_Call
DP 9 O_Disconnect
DP 10 O_Abandon
DP 12 Term_Attempt_Authorized
DP 13 T_Called_Party_Busy
DP 14 T_No_Answer
DP 15 T_Answer
DP 16 T_Mid_Call
DP 17 T_Disconnect
DP 18 T_Abandon
15.3.7 Add Mapping Between Service Key and Event Code (Optional)
I. Related commands
Command
Function
ADD SK2EC
To add mapping between service key and event code
RMV SK2EC
To remove mapping between service key and event code
MOD SK2EC
To modify mapping between service key and event code
LST SK2EC
To list mapping between service key and event code

15-34


data configuration.
When a subscriber uses services involves second dialing, such as IN card number
services, he/she will follow the call procedure:
1)
Caller picks up.
2)
Dial access code.
3)
Select language.
4)
Enter card number.
5)
Enter password.
6)
Dial callee number.
When the two parties finish the conversation and the callee hangs up first, SCP will
inform the caller to continue dialing without having to hang up and repeat the above
procedure to start another call.
Generally, if the caller wants to start another call without repeating the above procedure
after the first call, he/she has to wait till the callee hangs up. To change this pattern, and
let the caller dial a certain prefix to release the call after conversation without having to
hang up or wait for callee hanging up, use ADD SK2EC to add a mapping between the
service key and the event code.

[Service key]
It specifies the service key used by the IN service (usually second-dial, card number
services). This parameter must first be defined by ADD TDPCFG before it can be
referenced here.
[Event code]
It allocates an event code for the service key. It includes a maximum nine characters of
digits from 0 to 9 and the pound and asterisk keys.
Assume that you set the event code to ## to a certain IN service, the caller can dial ##
any time after finishing dialing the access code to inform the SoftX300 that the call is
finished. The SoftX3000 shall inform the SCP through an INAP message. The SCP
shall decide, according to the service procedure, whether to release the call or to play
announcement to the caller to start another call.
15.3.8 Adding IN Service Restriction (Optional)

I. Related commands
Command
ADD SRVRST
Function
To add IN service restriction

15-35

Command
Function
MOD SRVRST
To modify IN service restriction
RMV SRVRST
To remove IN service restriction
LST SRVRST
To list IN service restriction

data configuration.
For any IN call, no matter whether the IN service is associated with single-stage dialing
or dual-stage dialing, the called number must be dialed to instruct the SSP to
implement the subsequent connection.
z
If the dialed called number is a subscriber number, national number, or

international number, the SSP will perform a normal call connection action to
connect the calling and called parties and at the termination disconnect and
charge the call.
If the dialed called number is another IN access code (for example, 500 or 501),
that is, "IN call nested dialing, the SSP has to look up the related configuration
flag in the database to determine whether or not nested dialing is allowed.
By default, IN call nested dialing is allowed in the SoftX3000. To prohibit it, you must
add an IN service restriction using the ADD SRVRST command.

[Outer layer IN service key]
This parameter specifies the first service key triggering an IN service. This parameter is
defined in the ADD TDPCFG command and referenced here.
[Inner layer IN service key]
This parameter specifies the second service key triggering an IN service. It implies that
the SSP triggers a different IN service when the SSP is triggering the first IN service.
This parameter is defined in the ADD TDPCFG command and referenced here.
[Restriction relationship]
This parameter specifies whether or not there is a restriction between the outer layer
service key and the inner layer service key, that is, whether or not the SSP allows
nested dialing in an IN call. By default, it is NO, indicating nested dialing is allowed. If
you set it to YES, nested dialing is not allowed and the outer layer IN service cannot
trigger the inner IN service.

15-36

15.4 Configuring SCP and SSP Data

15.4.1 Overview
The SCP and SSP data define the IN services on the specific SCP triggered by each
service key, a mapping between the IN services and the SCP. During the process of IN
service data configuration, some parameters defined when you configure office data
and signaling data will be referenced during the configuration of SCP and SSP data.
parameter referencing relationship between SCP and SSP data and other data, see
Table 15-9.
Table 15-9 Parameter referencing relationship between SCP and SSP data and other
data
Input parameter
Name
Output parameter
Defined in
Name
Referenced in
Local signaling point code
Office data
SCCP destination signaling point code
SCCP data
SCCP data
SCCP data
II. Preparations
Before configuring SCP and SSP data, make sure that all preparations are done as
SN
Item
Remark
Codes regarding SCP physical

address, including DPC and SSN

Codes regarding SSP physical

address, including DPC and SSN


Table 15-11 lists the general steps for configuring SCP and SSP data.

15-37


Step
Description
Command
Add SCP physical address description
ADD SCPADDR
Add SSP physical address description
ADD SSPADDR
Add SCP configuration
ADD SCPCFG
Add SSP service specialized resource capability

(optional)
ADD SSPSRC
Add SCP number mapping (optional)
ADD SCPMAP

you configure DP, SCP and SSP data.
ADD SCPADDR
ADD TDPCFG
[DP number]
[SCP number]
[Access code]
[DPC flag]
[Service key]
[SSN flag]
ADD SSPADDR
[SCP number]
[DPC flag]
[SSN flag]
ADD SCPCFG
[Service key]
[Database number]
[SCP0-SCP15]
ADD SSPSRC
[Service key]
ADD SCPMAP
[SCP external number]
[SCP number]

15-38

15.4.2 Adding SCP Physical Address Description

I. Related commands
Command
Function
ADD SCPADDR
To add SCP physical address description
RMV SCPADDR
To remove SCP physical address description
MOD SCPADDR
To modify SCP physical address description
LST SCPADDR
To list SCP physical address description

Comply with the following configuration principles when adding SCP physical address
description.
1)
When the SoftX3000 interconnects with an SCP, if the SCP physical address
employs the signaling point coding format, set the DPC flag and the SSN flag to
YES, GT type to NO, and routing flag to Addressing by DPC. In addition, you
must set other parameters such as DPC address and SSN.
2)
employs the global title coding format, set both the DPC flag and the SSN flag to
NO, GT type to GT type 4, and routing flag to Addressing by GT. In addition,
you must set the GT content parameter.

[SCP number]
The SCP number uniquely identifies an SCP interconnected with the SoftX3000. The
value range is 0 to 15. The SoftX3000 can interconnect with a maximum of 16 SCPs.
When configuring this parameter, pay attention to the following:
z
When the SoftX3000 interconnects with an embedded SCP, that is, it is required to
deploy the IPN service in the local office, the SCP number is 0 rather than any
other integer. Otherwise, the IPN service cannot be used normally.
When the SoftX3000 interconnects with a physically separate SCP, that is, it is
required to deploy other IN services expect the IPN service in the local office, the
SCP is numbered from 1 to 15.
[DPC flag]
This parameter specifies the coding format for the physical address of the SCP
interconnected with the SoftX3000. By default, it is YES, indicating to employ the
signaling point code coding format. If you set it to NO, the global title coding format is
employed.
[SSN flag]
15-39

This parameter specifies whether or not the SCCP subsystem number (SSN) is
contained in the SCP physical address.
z
If the SCP physical address employs the signaling point coding format, the SSN
flag must be set to YES.
If the SCP physical address employs the global title coding format, the SSN flag
must be set to NO.
[GT flag]
When the SCP physical address employs the global title coding format, this
parameter specifies the type of the global title. Usually, it is GT type 4.
[Route flag]
This parameter specifies the routing or addressing mode of SCCP messages at the
SCP.
z
If the SCP physical address employs the signaling point coding format, the route
flag must be set to Addressing by DPC.
If the SCP physical address employs the global title coding format, the route flag
must be set to Addressing by GT.
[DPC]
When the SCP physical address employs the signaling point coding format, this
parameter specifies the signaling point code of the SCP in the SS7 network (that is, the
SCCP destination signaling point code). Set this parameter by the following principles:
z
When the INAP signaling between the SoftX3000 and the SCP is transmitted
through SCCP links (that is, INAP/TCAP/SCCP), this parameter is defined in the
ADD SCCPDSP command and referenced here.
When the INAP signaling between the SoftX3000 and the SCP is transmitted
through TCP/IP links (that is, INAP/TCP/IP), this parameter is defined in the ADD
N7DSP command and referenced here.
When the SoftX3000 interconnects with the SMCP through INAP over IP, this
parameter is not set.
[Network indicator]
parameter specifies the signaling network in which the signaling point code of the SCP
is resident. Set this parameter according to the networking fact.
[SSN]
parameter specifies the SCCP subsystem number used at the SCP. The configuration
principles of this parameter are as follows:
z
If the interconnected SCP is provided by Huawei, the SSN is set to INAP. In this
case, SSN is equal to 0x0C.

15-40

z
If the interconnected SCP is provided by other vendor, the SSN is set to INAP or
INAP1 according to the actual situations. In the case of INAP1, the SSN is
equal to 0xFE.
The SSN defined here should have the corresponding SCCP subsystem (ADD
SCCPSSN) configured in the SCCP data; otherwise, the SoftX3000 may fail to
interconnect with the SCP.
[GT content]
When the SCP physical address employs the global title coding format, this
parameter specifies the content of the global title. According to the default configuration,
the global title of type 4 is composed of the country code, the long-distance area code,
and the subscriber number. For example, a global title is 8675528970132, in which 86
is the country code, 755 is the long-distance area code, and 28970132 is the subscriber
number.
The GT content defined here should have the corresponding SCCP global title (ADD
SCCPGT) configured in the SCCP data; otherwise, the SoftX3000 may fail to
[SCP connect type]
This parameter defines the networking mode of INAP signaling between the SoftX3000
and the SCP. The options are
z
Connect SAU: It indicates that the INAP signaling between the SoftX3000 and the
SCP is transmitted through SCCP links. Select this option when the SoftX3000
networks with the SCP through MTP, M2UA, or M3UA links.
Connect SCP: Select this option only when the SoftX3000 interconnects with the
built-in SCP.
Connect SMCP or SCP: It indicates that the INAP signaling between the
SoftX3000 and the SMCP or SCP is transmitted through TCP/IP links. Select this
option when the SoftX3000 networks with the SMCP or SCP through IP interface
directly. By default, the SoftX3000 connects with the SMCP directly. To enable the
SoftX3000 to connect with SCP, you need to modify Bit 10 of SSP internal
parameter 2 (P78) to 0. This parameter must be identical to that at the SCP side;
otherwise, IN services cannot be enabled.
15.4.3 Adding SSP Physical Address Description

I. Related commands
Command
Function
ADD SSPADDR
To add SSP physical address description
RMV SSPADDR
To remove SSP physical address description
MOD SSPADDR
To modify SSP physical address description

15-41

Command
Function
LST SSPADDR
To list SSP physical address description

Comply with the following configuration principles when adding SSP physical address
description.
1)
employs the signaling point coding format, the SSP (that is, the SoftX3000)
physical address must use the same format. Set both the DPC flag and the SSN
flag to Yes, GT type to NO, and routing flag to Addressing by DPC. In addition,
you must set other parameters such as DPC address and SSN.
2)
employs the global title coding format, the SSP (that is, the SoftX3000) physical
address must use the same format. Set both the DPC flag and the SSN flag to
No, GT type to GT type 4, and routing flag to Addressing by GT. In addition,
you must set the GT content parameter.

[SCP number]
This parameter specifies the SCP interconnected with the SoftX3000. The value range
is 0 to 15. The SoftX3000 can interconnect with a maximum of 16 SCPs. This
parameter is defined in the ADD SCPADDR command and referenced here.
If the SoftX3000 interconnects with more than one SCP, the SCPs may employ different
coding formats for respective physical addresses. Therefore, you must add the coding
format for the physical address of each SCP interconnected with the SoftX3000 one by
one using this command.
[DPC flag]
This parameter specifies the coding format for the physical address of the SSP (that is,
the SoftX3000) when the SoftX3000 interconnects with the SCP. By default, it is YES,
indicating to employ the signaling point code coding format. If you set it to NO, the
global title coding format is employed.
[SSN flag]
This parameter specifies whether or not the SCCP subsystem number (SSN) is
contained in the SSP physical address.
z
If the SSP physical address employs the signaling point coding format, the SSN
flag must be set to YES.
If the SSP physical address employs the global title coding format, the SSN flag
must be set to NO.

15-42

[GT type]
When the SSP physical address employs the global title coding format, this parameter
specifies the type of the global title. Usually, it is GT type 4.
[Route flag]
This parameter specifies the routing or addressing mode of SCCP messages at the
SSP.
z
If the SSP physical address employs the signaling point coding format, the route
flag must be set to Addressing by DPC.
If the SSP physical address employs the global title coding format, the route flag
must be set to Addressing by GT.
[DPC]
When the SSP (that is, the SoftX3000) physical address employs the signaling point
coding format, this parameter specifies the signaling point code of the SSP in the SS7
network (that is, the SCCP local signaling point code). This parameter is defined in the
SET OFI command and referenced here.
Although the SoftX3000 supports multiple signaling point codes, it is not recommended
to use the local signaling point code defined in the ADD OFI command in the SSP
physical address description data table.
[Network indicator]
When the SSP physical address employs the signaling point coding format, this
parameter specifies the signaling network in which the signaling point code of the SSP
is resident. This parameter should be configured according to the networking fact.
[SSN]
When the SSP physical address employs the signaling point coding format, this
parameter specifies the SCCP subsystem number used at the SSP. The configuration
principles of this parameter are as follows:
z
If the interconnected SSP is provided by Huawei, the SSN is set to INAP. In this
case, SSN is equal to 0x0C.
If the interconnected SSP is provided by other vendor, the SSN is set to INAP or
INAP1 according to the actual situations. In the case of INAP1, the SSN is
equal to 0xFE.
The SSN defined here should have the corresponding SCCP subsystem (ADD
SCCPSSN) configured in the SCCP data; otherwise, the SoftX3000 may fail to
[GT content]
When the SSP physical address employs the global title coding format, this parameter
specifies the content of the global title. According to the default configuration, the global
title of type 4 is composed of the country code, the long-distance area code, and the
subscriber number. For example, a global title is 8675528970132, in which 86 is the
15-43

country code, 755 is the long-distance area code, and 28970132 is the subscriber
number.
The GT content defined here should have the corresponding SCCP global title (ADD
SCCPGT) configured in the SCCP data; otherwise, the SoftX3000 may fail to
15.4.4 Adding SCP Configuration

I. Related commands
Command
Function
ADD SCPCFG
To add SCP configuration
MOD SCPCFG
To modify SCP configuration
RMV SCPCFG
To remove SCP configuration
LST SCPCFG
To list SCP configuration

[Service key]
This parameter specifies the service key corresponding to a particular IN service. The
IN service associated with this service key will be controlled by the SCP that is to be
specified in this command. This parameter is defined in the ADD TDPCFG command
[Database number]
This parameter specifies the database number to be used by the service key. The value
of this parameter depends on the access code description table in the database
(defined in the ADD ACCODE command).
z
If the database start position of the corresponding access code is set to 255, it
indicates to use the default database and the database number here must be set
to 65535.
If the database start position of the corresponding access code is not 255, it
indicates to pick up the required database number from the called number and the
database number here should be set according to the actual situations.
[SCP0] to [SCP15]
These parameters specify the SCP which controls the IN service associated with the
preceding service key. Valid SCP numbers entered here must have been defined in the
ADD SCPADDR or ADD SSPADDR command before being referenced here.
The SoftX3000 supports to interconnect with a maximum of 16 SCPs. If more than one
SCP flag are set to "Existing, when the SSP triggers the IN service, the SCPs are

15-44

selected in a cyclic way according to the SCP numbers until an SCP is brought into
service successfully.
[Service name]
It identifies the IN service related to the service key. It is designed for identification
purpose only.
15.4.5 Adding SSP Service Specialized Resource Capability (Optional)

I. Related commands
Command
Function
ADD SSPSRC
To add SSP service specialized resource capability
RMV SSPSRC
To remove SSP service specialized resource capability
LST SSPSRC
To list SSP service specialized resource capability

This configuration step is optional. Read carefully the following description before using
this command.
By default, the system automatically adds SSP service special resource capability
(sometimes called specialized resource functionality) for the corresponding service
key when you are adding SCP configuration using the ADD SCPCFG command. The
piece of data is used for IN traffic measurement purposes, and it does not influence IN
services.

[Service key]
This parameter specifies the service key for which the SSP service specialized
resource capability is to be added. This parameter is defined in the ADD TDPCFG
15.4.6 Adding SCP Number Mapping (Optional)

I. Related commands
Command
Function
ADD SCPMAP
To add SCP number mapping
RMV SCPMAP
To remove SCP number mapping
MOD SCPMAP
To modify SCP number mapping
LST SCPMAP
To list SCP number mapping

15-45


data configuration.
When the SoftX3000 acts as an assisting SSP in the IN networking, other SSP (that is,
the initiating SSP) can use the specialized resources on the IP that is controlled by the
assisting SSP. A typical networking model is illustrated in Figure 15-11.
SCP
INAP
INAP
ISUP
Initiating
SSP
Media stream
channel
MGCP
Assisting
SSP
IP
Media stream
channel
Figure 15-11 Networking model with assisting SSP application

In this networking model, when the IN service triggered by the initiating SSP needs to
use the specialized resources on the IP, the SCP always instructs the calling party to
connect to the assisting SSP to achieve the interaction between the calling party and
the IP. In this case, all INAP signaling traffic with which the SCP operates the IP is
transferred by the assisting SSP.
During the process of interaction between the calling party and the IP, ISUP signaling
(or SIP-T signaling) is required between the initiating and assisting SSPs to exchange
control related information. If the SCP number for the same SCP is not specified to the
same value, the ISUP signaling cannot interwork between the initiating and assisting
SSPs. The reason is that the Initial Address Message with Information (IAI) regarding
ISUP signaling carries the SCP number" parameter. To ensure the interworking of
ISUP signaling between the initiating and assisting SSPs, the SoftX3000 provides a
mechanism to translate SCP numbers by defining the mapping relationship from peer
SCP numbers to local SCP numbers in the ADD SCPMAP command.

[SCP external number]
This is one of the interconnection parameters between the SoftX3000 and the initiating
SSP, used to specify the SCP number carried in the IAI message sent by the initiating
SSP to the SoftX3000 (that is, the assisting SSP). This parameter should have been
negotiated with the initiating SSP before being configured. It must be the SCP number
carried in the IAI message, rather than the actual SCP number defined in the initiating
SSP (because the peer may also make some translation on the SCP number).

15-46

[SCP number]
This parameter specifies the SCP physical number that corresponds to the preceding
SCP external number and is defined in the SoftX3000 (that is, the assisting SSP). This
parameter is defined in the ADD SCPADDR command and referenced here.
15.5 Configuring SHLR Data

15.5.1 Overview
The SHLR data is signaling and service data used for the interworking between the
SoftX3000 and the SHLR, including the SHLR local address, the SHLR remote address,
the SHLR networking model, and the service procedures of the SHLR. When
configuring the SHLR data, you need to reference some office parameters and
signaling parameters as shown in Table 15-12.
Table 15-12 Parameter referencing relationship between SHLR data and other data
Input parameter
Name
Output parameter
Defined in
Name
Defined in
Local DN set
Office data
DPC
Signaling data
II. Preparations
Before configuring SHLR data, make sure that all preparations are done as specified in
Table 15-13.
SN
Item
Remark
DPC of SHLR
Service procedure of SHLR (standard or

extended)
Overlap service indicator
Parameters that the SoftX3000

uses to interwork with the
SHLR
Number type (sent by SoftX3000)
CUG service access code (optional)
MON service trigger access code (optional)
MON service release access code (optional)

15-47
Used only when CUG service

is required
Used only when MON service
is required

SN
8
Item
Remark
Used only when UC service is
required
UC service access code (optional)

Table 15-14 lists the general steps for configuring the SHLR data.
Step
Description
Command
Add SHLR local address
ADD SHLRLA
Add SHLR remote address
ADD SHLRRA
Add SHLR group
ADD SHLRGRP
Add SHLR configuration
ADD SHLRCFG
Add SHLR service configuration
ADD SHLRSRVC

There is no referencing relationship among the steps of configuring SHLR data.
15.5.2 Adding SHLR Local Address

I. Related commands
Command
Function
ADD SHLRLA
To add SHLR local address
RMV SHLRLA
To remove SHLR local address
MOD SHLRLA
To modify SHLR local address
LST SHLRLA
To list SHLR local address

[SHLR address index]
It identifies an SHLR address in a SoftX3000. It ranges from 0 to 254.
When the SoftX3000 is connecting with a SHLR, the SHLR address index used in the
command must be the same as the SHLR address index defined by ADD SHLRRA;
otherwise the SoftX3000 cannot successfully connect the SHLR.
[SHLR description]

15-48

It describes an SHLR in character strings.

[Route flag]
It indicates whether the signaling route between the SoftX3000 and the SHLR is
addressing by DPC or addressing by GT. By default, it is set to addressing by DPC.
[DPC flag]
It indicates whether DPC is used in the signaling routing between the SoftX3000 and
the SHLR. It is valid only when the route flag is by DPC. By default, it is set to
TRUE.
[SSN flag]
It indicates whether SSN is used in the signaling routing between the SoftX3000 and
the SHLR. It is valid only when the route flag is by SSN. By default, it is set to
TRUE.
[DPC]
It specifies the local signaling point code of the local office. It is one of the parameters
used for the interworking between the SoftX3000 and the SHLR, and is valid only when
the route flag is addressing by DPC. This parameter must first be defined by SET
OFI and configured by ADD SCCPDSP (need to configured OPC) before it can be used
here.
[Network indicator]
It indicates the signaling network in which the SHLR local signaling point locates. It can
be an international network, international reserved network, national network, and
national reserved network. This parameter is valid only when the route flag is
addressing by DPC. The parameter must be set the same as the network indicator
attribute of the SPC in the office information table.
[SSN]
It specifies the SSN in the DPC + SSN addressing model. This parameter is valid only
when the route flag is set to addressing by DPC. Here are the configuration
guidelines:
z
When it is used in ADD SHLRLA to configure SHLR local address, select

MSC (0x08).
When it is used in ADD SHLRRA to configure SHLR remote address, select

HLR (0x06).
[GT type]
It specifies the type of the new global title. It can be type 1, type 2, type 3, and
type 4. In SHLR networking, select type 4. This parameter is valid only when the
route flag is addressing by GT.
[Translation type]

15-49

It specifies the translation feature that the new GT uses. It is valid only when the route
flag is set to addressing by GT. Currently the parameter is not used. Set it to 00.
[Numbering plan]
It specifies the numbering plan that the new GT uses. Select ISDN/telephony
numbering plan in SHLR networking. This parameter is valid only when the route flag
is set to addressing by GT.
It specifies the address nature of the new GT. Select International number in SHLR
networking. This parameter is valid only when the route flag is set to addressing by
GT.
It specifies the new GT value (the specific address signal). This parameter is valid only
when the route flag is set to addressing by GT.
15.5.3 Adding SHLR Remote Address

I. Related commands
Command
Function
ADD SHLRRA
To add SHLR remote address
RMV SHLRRA
To remove SHLR remote address
MOD SHLRRA
To modify SHLR remote address
LST SHLRRA
To list SHLR remote address
Note:
Since most of the parameters in ADD SHLRRA are the same as ADD SHLRLA, only
the different ones are introduced here. For the rest, refer to section 15.5.2 Adding
SHLR.
[SHLR address index]

It identifies an SHLR address in a SoftX3000. It ranges from 0 to 254.
When the SoftX3000 is connecting with a SHLR, the SHLR address index used in the
command must be the same as the SHLR address index defined by ADD SHLRLA;
otherwise the SoftX3000 cannot successfully connect the SHLR.

15-50

[DPC]
It specifies the SHLR remote SPC (the SPC of the SHLR). It is one of the parameters
used for the interworking between the SoftX3000 and the SHLR, and is valid only when
the route flag is addressing by DPC. This parameter must first be defined by ADD
N7DSP or ADD M3DE and configured by ADD SCCPDSP (need to configure OPC)
before it can be used here.
15.5.4 Adding SHLR Group

I. Related commands
Command
Function
ADD SHLRGRP
To add SHLR group
RMV SHLRGRP
To remove SHLR group
MOD SHLRGRP
To modify SHLR group
LST SHLRGRP
To list SHLR group

[SHLR group number]
It uniquely defines an SHLR group number within the SoftX3000. It ranges from 0 to
254.
[Select mode]
It specifies the query mode selected when the SoftX3000 queries multiple SHLR in one
network. There are two select modes:
z
Active/Standby mode: It is also known as 1+1 backup mode. Generally, the

SoftX3000 only queries the active SHLR, and will not query the standby SHLR
unless the active one is faulty.
Load-sharing mode: The SoftX3000 will query the SHLRs in load-sharing style.
[SHLR index 1]
It specifies the address index of the first SHLR. It ranges from 0 to 254. This parameter
is mandatory, and must be defined by ADD SHLRLA and ADD SHLRRA before it can
be referenced here.
When you select active/standby mode for the selection mode, the SHLR index 1
stands for the active SHLR.
[SHLR index 2]
It specifies the address index of the first SHLR. It ranges from 0 to 255. This parameter
is optional, and must be defined by ADD SHLRLA and ADD SHLRRA before it can be
referenced here.
15-51

When you select active/standby mode for the selection mode, the SHLR index 2
stands for the standby SHLR.
[SHLR index 3] to [SHLR index 16]
These parameters are valid when you select load-sharing mode for select mode.
They range from 0 to 255. 255 means that the parameter is not functioning.
These parameters are optional, and must be defined by ADD SHLRLA and ADD
SHLRRA before they can be referenced here.
15.5.5 Adding SHLR Configuration

I. Related commands
Command
Function
ADD SHLRCFG
To add SHLR configuration
RMV SHLRCFG
To remove SHLR configuration
MOD SHLRCFG
To modify SHLR configuration
LST SHLRCFG
To list SHLR configuration

[SHLR select code]
It is uniquely defined in SoftX3000. It ranges from 0 to 65535. The parameter is one of
the indicators that the SoftX3000 uses to trigger SHLR. It is used to trigger SHLR when
the SoftX3000 is analyzing the called prefix. This parameter will be referenced in ADD
CNACLD. Here are the configuration guidelines:
z
One SHLR select code can be used by multiple configurations of ADD SHLRCFG.
65534 is the wildcard, and can be any call prefix (yet with lowest priority). When
the SHLR select code of a call prefix is any value other than 65535, it indexes the
SHLR data record of the specific SHLR select code as well as the 65534. If the two
records match a certain record, the specific one will be prioritized.
This parameter must be set to 65535 when the hook trigger mode is used (used in
color dial tone service). The SoftX3000 does not judge the SHLR select code of
the called prefix.
[SHLR select source code]

It specifies the call source (caller) that can trigger the SHLR group specified in the
command. The parameter is one of the indicators that the SoftX3000 uses to trigger
SHLR. It must be defined by ADD CALLSRC before it can be used here.
[Caller subscriber type]

15-52

It specifies the type of callers that can trigger the SHLR (SHLR group number specified
in the command). The parameter is one of the indicators that the SoftX3000 uses to
trigger SHLR. Generally it is set to all subscriber type. You can select other options
according to actual requirements.
When the call processing software triggers the SHLR during call analysis, and it finds
multiple caller subscriber type results matching the call, the all subscriber type
enjoys the lowest priority; the system will match other results first.
[Query SHLR flag]
It determines whether the system shall trigger the SHLR in a call based on the
combination of the above parameters; whether the SoftX3000 shall start an SRI action
to the SHLR through MAP. By default, it is set to TRUE.
You can set the parameter to FALSE in the following two cases:
z
To temporary stop some services related to an SHLR without (and not wishing to)
deleting the configured data.
To filter the alarms generated in the SoftX3000 of a faulty SHLR.
[Query SHLR type]

The parameter indicates the service procedure that the SoftX3000 adopts to trigger the
SHLR. By default, it is set to standard. Here are the descriptions of the options:
z
Standard: The SoftX3000 shall trigger the SHLR following the standard procedure.
You can only specify the SHLR group number through this command. For each
SRI action initiated by the SHLR to the SoftX3000, the former needs to query
sequentially the four value-added servicescaller NP service, caller IN
subscription , callee IN subscription, and callee NP.
Extend: The SoftX3000 shall trigger the SHLR following the extended procedure.
You can only use ADD SHLRSRVC to specify the SHLR group number. For each
SRI action initiated by the SHLR to the SoftX3000, the former shall first query
whether the called segment of the SRI request includes any access code of the
CUG, MON, and UC service. If so, the SHLR shall follow the extended procedure;
if not, the SHLR shall follow the standard procedure.
[Callee trigger again]

This parameter indicates whether the SoftX3000 shall again trigger the SHLR after
completing a procedure based on caller number and called number for a call initiated
by a local subscriber or incoming trunk. This parameter is valid only when the "query
SHLR type is "standard. By default, it is set to "FALSE
If you set it to TRUE, you must set the SHLR select source code to 65535; otherwise,
the system will prompt error. The "TRUE setting can only be used in the following
cases:
z
When you use the SoftX3000 in a network of multiple area codes or multiple
country codes, the SoftX3000 shall control the calls of multiple local networks.

15-53

According to the networking model of a smart network, a SoftX3000 needs to

interact with multiple SHLR, each of which manages the subscriber data of one
local network in the local office.
z
When a local subscriber starts a national toll or international toll call within the
office, the SoftX3000 shall trigger the SHLR based on the caller number and the
called number. After the completion of the first-round trigger procedure, the
system detects that the callee trigger again is set to TRUE and a second-round
trigger procedure. The SoftX3000 will not proceed with subsequent actions until it
receives the results of the two round trigger procedures.
[Hook trigger flag]

It indicates whether the SoftX3000 immediately triggers the SHLR on subscriber
offhook when the SHLR select source code, of the call source to which the subscriber
belongs, matches the parameter SHLR select source code". The parameter is valid
only when the "query SHLR type" is "extend". By default, it is set to "FALSE".
If you set it to "TRUE", you must set the "SHLR select code" to 65535, or the system will
prompt an error.
[SHLR configuration index]
It is uniquely defined in the SoftX3000. The parameter is valid only when the "query
SHLR type" is "extend". It ranges from 0 to 255. The parameter will be referenced by
ADD SHLRSRVC.
[Service trigger start length]
It indicates the number of digits (starting from the first digit) of the called number that
the SoftX3000 uses to query in SHLR. It ranges from 0 to 31. By default, it is set to 0.
Here are the configuration guidelines:
z
When it is set to 0, it means that the SoftX3000 will use the length of digits, which
the call processing software actually matches in the called number, to query the
SHLR.
When it is set to values other than 0, it means that the SoftX3000 will retrieve the
number of digits in the called number specified by the parameter to query the
SHLR. The start length of service triggering is set to greater than equal to the
minimum number length of any call prefix.
[Overlap flag]
It indicates whether SoftX3000 supports the overlap service procedure. The parameter
is one of the indicators that the SoftX3000 uses to trigger SHLR. By default, it is set to
"FALSE". Here are the configuration guidelines:
z
When the "service trigger start length" is set to 0, this parameter is generally set to
"FALSE".
When the "service trigger start length" is set to values other than 0, and the SHLR
dedicated to support caller IN subscription, set the parameter to "FALSE". This is
to reduce the interaction of invalid messages between the SoftX3000 and the
15-54

SHLR because the former need not query the latter for the information of called
number..
z
When the "service trigger start length" is set to values other than 0, and the SHLR
is used to support multiple value-added services, set the parameter to "TRUE".
Otherwise, the callee IN subscription and callee NP service will be unavailable.
When you set it to "TRUE", and the length of the dialed called number reaches the
"service trigger start length", the SoftX3000 shall trigger the SHLR:
1)
The SoftX3000 includes the "service trigger start length" and the dialed called
number in the MAP message, and sends it to the SHLR.
2)
The SHLR receives the SRI request, and detects whether the called number
segment includes the "service trigger start length". If so, the SHLR shall start
number length match analysis of the called number; if the number length falls short,
the SHLR shall send overlap service indicator to the SoftX3000.
3)
The SoftX3000 shall continue to receive the remaining digits dialed by the
subscriber, inserts an overlap service indicator before the called number, and
sends them digit by digit to the SHLR, until the SHLR returns a MAP message that
the number is complete..
[Overlap service indicator]

It identifies the overlap service, and is included in the MAP message sent by the
SoftX3000 to the SHLR. The parameter is one of the indicators that the SoftX3000 uses
to trigger SHLR. It is valid only when the "overlap flag" is "TRUE". It contains a
maximum eight characters.
When you enable the overlap feature, the SoftX3000 inserts the overlap service
indicator before the called number, and includes them in the MAP message to the
SHLR for number analysis. After the SHLR receives the SRI request, it analyzes the
overlap service indicator and triggers the relevant service procedure.
[Number type]
The parameter instructs the SoftX3000 to convert the caller and called number into a
certain type before starting the SRI request to the SHLR through MAP. The parameter
is one of the indicators that the SoftX3000 uses to trigger SHLR. It is valid only when
the "query SHLR type" is "standard" or the "overlap flag" is "TRUE". Here are the
options:
z
Original number (default): No change is made.
International number
National number
Subscriber number
[SHLR group number]

It defines the SHLR that the SoftX3000 queries when the latter triggers a VAS. This
parameter must first be defined by ADD SHLRGRP before it can be used here.

15-55

15.5.6 Adding SHLR Service Configuration (Optional)

I. Related commands
Command
Function
ADD SHLRSRVC
To add SHLR service configuration
RMV SHLRSRVC
To remove SHLR service configuration
MOD SHLRSRVC
To modify SHLR service configuration
LST SHLRSRVC
To list SHLR service configuration

data configuration.
This command is required only when the SoftX3000 triggers the SHLR following the
extended procedure.

[SHLR configuration index]
It is uniquely defined in the SoftX3000. The parameter is valid only when the "query
SHLR type" is "extend". It ranges from 0 to 255. The parameter will be referenced by
ADD SHLRSRVC.
It specifies the SHLR configuration index whose SHLR service data shall be configured.
It ranges from 0 to 255. The parameter must first be defined by ADD SHLRCFG before
it can be referenced here.
[Service type]
It specifies the type of value-added services whose service data shall be configured.
When the SoftX3000 triggers the SHLR following the extended procedure, you need to
configure some additional service data to meet the requirements of the extended
procedure. Here are the options:
Service type
Description
UC
Unified communication service
Caller NP or caller IN
Calller NP or caller IN subscription service
CUG
Closed user group service
MON
Multiple subscriber number service
Callee NP or callee IN
Calllee NP or callee IN subscription service
Overlap
Overlap number receiving service

15-56

[Number type]
The parameter instructs the SoftX3000 to convert the caller and called number into a
certain type before starting the SRI request to the SHLR through MAP. The parameter
is one of the indicators that the SoftX3000 uses to trigger SHLR. It is valid only when
the "query SHLR type" is "standard" or the "overlap flag" is "TRUE". Here are the
options:
z
Original number (default): No change is made.
International number
National number
Subscriber number
[Service access code]

It identifies the CUG, MON, or UC service in the MAP messages that the SoftX3000
sends to the SHLR. The parameter is one of the indicators that the SoftX3000 uses to
trigger SHLR. It is valid only when the "service type" is "CUG", "MON", or "UC". It
contains a maximum 32 characters. When the service type is MON, it is the trigger
access code of the MON service.
When the SoftX3000 requests the SHLR to analyze a CUG, MON, or UC service it
inserts the relevant service access code before the called number, includes them in the
MAP message, and sends it to the SHLR for number analysis. After the SHLR receives
the SRI request, it analyzes the service access code and triggers the relevant service
procedure.
[MON service release access code]
It specifies the release access code of the MON service. The parameter is one of the
indicators that the SoftX3000 uses to trigger SHLR. It is valid only when the "service
type" is "MON".
The MON service is used in a multi-area-code or multi-country-code NGN to allocate to
the subscriber the PSTN numbers of other local networks in the local office. When the
virtual number of the MON subscriber is used as a PBX pilot number, local subscribers
can dial the virtual number to call other PBX users. However, the system shall limit the
number of simultaneous calls. Here is the implementation mechanism:
z
When a local subscriber successfully starts a call to the virtual number of the MON
subscriber, the SHLR automatically adds one to the simultaneous call counter of
the MON subscriber (as callee). When the counter reaches a threshold, the SHLR
shall reject any calls from the SoftX3000 through MAP for called number analysis
(of the MON subscriber).
When the above-mentioned successful call is released, the SoftX3000 shall start
an SRI action to the SHLR. Prior to the SRI action, the SoftX300 inserts the "MON
service release access code" before the called number (virtual number of the
MON subscriber) in the MAP message, and sends it to the SHLR for number
analysis.
15-57

z
When SHLR receives the SRI request, it will automatically reduce the
simultaneous call counter of the MON subscriber by one according to the "MON
service release access code" and called number in the message.

It instructs the SoftX300 to fill in the caller number in the MAP message during the
triggering state of "callee NP/IN" service when the SoftX300 triggers the SHLR
following the extended procedure. The parameter is valid only when the "service type"
is callee NP/IN. It is an invalid number in the local network. Generally, use the default
value 00000000.
The parameter is valid only when the service type is "callee NP/IN" or "MON". Here are
the descriptions of the parameter::
z
For "Callee NP/IN" service: It instructs the SoftX300 to fill in the caller number in
the MAP message during the triggering state of "callee NP/IN" service when the
SoftX300 triggers the SHLR following the extended procedure. It is an invalid
number in the local network. Generally, use the default value 00000000.
For "MON" service: When a MON subscriber initiates a call, and the SHLR detects
that the virtual number of the caller and the callee number are in the same local
network, it returns the virtual number of the caller. By default, the callee's
telephone displays the "defualt caller number" rather than the virtual number of the
caller. To make the telephone display the virtual number of the caller, set the bit8
of the call internal parameter 13 (P169) to 0. If the SHLR detects that the virtual
number of the caller and the callee number are not in the same local network, this
parameter is invalid, and the SoftX3000 shall proceed with the call connection
following the normal procedure.
[Default callee number]

It instructs the SoftX300 to fill in the callee number in the MAP message during the
triggering state of "caller NP/IN" service when the SoftX300 triggers the SHLR following
the extended procedure. The parameter is valid only when the "service type" is callee
NP/IN. It is an invalid number in the local network. Generally, use the default value
00000000.
[SHLR group number]
It specifies the SHLR to which the SoftX3000 shall start the SRI action through MAP.
The parameter shall first be defined in ADD SHLRGRP before it can be referenced
here.

15-58

15.6 Configuring SSAP Data

15.6.1 Overview
SSAP data defines the related information of the SoftX3000 when it acts as an SSAP in
a local IN and interconnects with SMCP, including IP address of SSAP, IP address of
SMCP, TCP port number at SMCP side, and start dialog number. When setting SSAP
data, you need to reference some hardware parameters as shown in Table 15-15.
Table 15-15 Parameter referencing relationship between SSAP data and other data
Input parameter
Name
FCCU/FCSU
module number
Output parameter
Defined in
Equipment data
Name
FCCU/FCSU
module number
Referenced in
/
II. Preparations
Before configuring SSAP data, make sure that all preparations are done as specified in
Table 15-16.
SN
Item
Remark
IP address of SSAP
One of the parameters for the SoftX3000 to

interconnect with SMCP
IP address of SMCP

TCP port number at SMCP side

Start dialog number


Table 15-17 lists the general steps for configuring SSAP data.
Step
Description
Command
Add INAP over IP
ADD INAPOIP
Add module dialog number
ADD DLGNUM

15-59


There is no parameter referencing relationship between data tables for SSAP data
configuration.
15.6.2 Adding INAP over IP

I. Related commands
Command
Function
ADD INAPOIP
To add INAP over IP data
RMV INAPOIP
To remove INAP over IP data
MOD INAPOIP
To modify INAP over IP data
LST INAPOIP
To list INAP over IP data

When the SoftX3000 serves as an SSAP in a local IN, the IP signaling interfaces (that is,
the FE ports) for interconnection with the SMCP are provided by the HSCI instead of
the IFMI. In actual networking, the IP signaling interfaces for interconnecting with the
SMCP are led from 0#LAN Switch and 1#LAN Switch in the integrated configuration
cabinet, for the HSCI in each frame is connected to 0#LAN Switch and 1#LAN Switch
through internal Ethernet cables.
The INAP messages transmitted between the SoftX3000 and the SMCP occupy the
Ethernet communication channels between and in the frames of the SoftX3000. To
ensure the reliability of the Ethernet communication system in the SoftX3000, a virtual
IP address (not in 172.20.XXX.XXX and 172.30.XXX.XXX) is used by the FCCU/FCSU
that is responsible for transmitting and receiving INAP messages to and from the
SMCP.

It specifies the module number of the FCCU/FCSU responsible for processing INAP
messages at the SoftX3000 side when the SoftX3000 acts as SSAP in a local IN. The
value range is 22 to 101. It is defined in the ADD BRD command and referenced here.
The subscribers managed by an FCCU/FCSU can use the corresponding local IN
services only after you add INAP over IP configuration for this FCCU/FCSU. Those
managed by the FCCU/FCSU without INAP over IP configuration cannot use the
corresponding local IN services.
[Group number]
Reserved.
15-60

[Local IP address 0], [Local IP address 1]

They are among the parameters for the SoftX3000 to interconnect with SMCP (for
example, U-NICA of Huawei). They define the IP addresses of the virtual FE ports of
the FCCU/FCSU processing INAP messages at the SoftX3000 side. Set this parameter
by the following principles:
z
Local IP address 0 is mandatory. Local IP address 1 is not set generally.
For different FCCUs/FCSUs, their local IP address 0 cannot be the same.
To ensure the reliability of the Ethernet communication system in the SoftX3000,

local IP addresses cannot be within 172.20.XXX.XXX or 172.30.XXX.XXX.
[Remote IP address 0], [Remote IP address 1]

They are among the parameters for the SoftX3000 to interconnect with SMCP (for
example, U-NICA of Huawei). They define the IP addresses of SMCP. Set this
z
Local IP address 0 is mandatory. Local IP address 1 is not set generally.
If several SoftX3000s interconnect with one SMCP, Remote IP address 0 of the

SMCP for interconnecting with different FCCUs/FCSUs must be the same.
[Remote port number]

It is one of the parameters for the SoftX3000 to interconnect with SMCP, specifying the
TCP port number used by the SMCP for processing INAP messages. Because SMCP
works in Server mode on TCP links, the remote port numbers used by the TCP links of
the FCCUs/FCSUs can be identical, for example, 10100, if you add INAP over IP
configuration for different FCCUs/FCSUs.
[System number]
Reserved.
[Default gateway]
When the virtual FE ports of the FCCU/FCSU use the IP addresses in different network
segments from the IP address of SMCP, this parameter specifies the IP address of the
router connected to the virtual FE ports of the FCCU/FCSU. You must set it correctly;
otherwise, the FCCU/FCSU cannot interwork with SMCP.
[Mask]
It defines the sub-net mask of the virtual FE ports of the FCCU/FCSU. It is in dotted
decimal format, for example, 255.255.255.0.
15.6.3 Adding Module Dialog Number

I. Related commands
Command
ADD DLGNUM
Function
To add module dialog number

15-61

Command
Function
RMV DLGNUM
To remove module dialog number
LST DLGNUM
To list module dialog number

When the SoftX3000 serves as an SSAP in a local IN, you must add module dialog
number for an FCCU/FCSU using ADD DLGNUM after adding INAP over IP
configuration for the FCCU/ FCSU. Otherwise, the subscribers managed by the
FCCU/FCSU cannot use the corresponding local IN services.

It specifies the module number of the FCCU/FCSU whose module dialog number is to
be set. The value range is 22 to 101. It is defined in ADD BRD first and then in ADD
INAPOIP before being referenced here.
[Start dialog number]
As one of the parameters for the SoftX3000 to interconnect with the SMCP (for
example, U-NICA equipment of Huawei), it specifies the start dialog number for the
FCCU/FCSU to communicate with SMCP. Its value ranges from 0 to 4000. Set this
z
Dialog number is a kind of resources. At present, there are 6000 available dialog
numbers between the SoftX3000 and an SMCP fixedly and they are numbered
from 0 to 5999.
By default, after you set the start dialog number for an FCCU/FCSU, the system
defines the end dialog number for the FCCU/FCSU automatically, that is, end
dialog number=start dialog number+ 1999.
The dialog number range for different FCCUs/FCSUs cannot be intersected;

otherwise, call loss might occur.
Set the start dialog number to an even number, for example, 0, 2000, or 4000.
Only after you have set the dialog number for an FCCU/FCSU, the subscribers
managed by the FCCU/FCSU can use the corresponding local IN services.
15.7 Configuring IN Announcement Data

15.7.1 Overview
IN announcement data defines information about IN announcements of the SoftX3000,
including loading IN voice files, configuring language type, and configuring currency
15-62

type. IN announcement data is closely associated with MRS data. Before configuring IN
announcement data, be sure to know how to configure MRS data.
II. Preparations
Before configuring IN announcement data, make sure that all preparations are done as
SN
Item
Remark
Knowledge about service

types supported by voice files
in the hard disk of the BAM
Through naming conventions for voice files,

the definition of service code (that is, service
keys) in the SoftX3000 can be found. For
example, 03 represents the VPN, 06 the
PPS, 1A the UCS, and FC the IPN.
Knowledge about language

types supported by voice files
in the hard disk of the BAM
Through naming conventions for voice files,

the definition of language position in the
SoftX3000 can be found. For example, 40
represents English and 80 Chinese.

Table 15-19 lists the general steps for configuring IN announcement data.
Step
Description
Command
ADD MRC voice file
ADD MRCV (embedded MRS)
Add language kind (optional)
ADD LKND
Add language kind index
ADD LKNDIDX
Add money category (optional)
ADD MCAT
Add record announcement message ID

conversion
ADD MSGCVT
Add mapping between message ID and

tone ID (optional)
ADD MSGTONE

During the configuration of IN announcement data, there is parameter referencing
relationship between the ADD LKND and ADD LKNDIDX commands only, as shown
in Figure 15-12.

15-63

ADD LANGKIND
[Language category]
[Language position
transfer value]
[Language description]
ADD LANGKINDIDX
[Service key]
[Language position]
[Language kind number]
[Language kind n]
15.7.2 Loading IN Voice Files to MRS

Before enabling IN services, you must load necessary IN voice files to the MRS
(intelligent peripheral) to provide IN announcements. Otherwise, subscribers cannot
use IN services normally.
For more information about loading voice files to the MRS, refer to Chapter 6,
Configuring MRS Data, of this manual.
15.7.3 Adding Language Kind (Optional)

I. Related commands
Command
Function
ADD LKND
To add language kind
RMV LKND
To remove language kind
MOD LKND
To modify language kind
LST LKND
To list language kind

This configuration step is optional. Read carefully the following description before using
this command.
When an IN service needs announcement, the SCP sends a message ID identifying the
recorded announcement to the SSP through an INAP message. This message ID
consists of service key, language position, and recorded announcement ID. Language
position specifies the language for playing the announcement.

15-64

The SCP devices of different manufacturers might define the language position
differently. If the SSP directly uses the language position in the recorded
announcement message ID to operate and reference the IN voice file on an MRS, the
MRS must be loaded with a large number of voice files with same contents according to
the language position defined by different SCP manufacturers. This limits the
SoftX3000 to interconnect with different SCPs.
To solve the problem, define the language position parameter in IN voice files to be
loaded to the MRS based on the internal rule, and then define the mapping relationship
between the language position in the recorded announcement message ID and that in
IN voice files using ADD LKND and ADD LKNDIDX.

[Language category]
This parameter uniquely identifies a language in the SoftX3000. For example, ENG
represents English, CHI represents Chinese, and GER represents German.
The language category defined here is only a parameter transmitted inside the
SoftX3000 databases, and will be referenced in ADD LKNDIDX.
[Language position transfer value]
This parameter specifies an identifier for the language category parameter defined
above. It is valid only inside the SSP and must comply with the definition rules of the
language position parameter in the IN voice files in the SoftX3000. The default settings
in the SoftX3000 are as follows:
z
40:
English
80:
Chinese
21:
German
22:
French
23:
Italian
24:
Japanese
25:
Korean
26:
Russian
27:
Spanish
28:
Malay
61:
Vernacular
You can define the mapping relationship between the language position transfer value
and the language position parameter carried in a recorded announcement message ID
sent by the SCP using ADD LKNDIDX. This facilitates the conversion between the
language position parameter in the IN voice files and that carried in a recorded
announcement message ID and enhances the flexibility of the interconnection between
the SoftX3000 and various SCPs.

15-65

15.7.4 Adding Language Kind Index

I. Related commands
Command
Function
ADD LKNDIDX
To add language kind index
RMV LKNDIDX
To remove language kind index
MOD LKNDIDX
To modify language kind index
LST LKNDIDX
To list language kind index

[Service key]
This parameter specifies the corresponding service key of the IN service for which the
language kind index is to be set. This service key is different from the service key we
usually use. This service key is a 2-digit hexadecimal number, used to identify the IN
service to which the recorded announcement defined in the recorded announcement
message ID belongs.
Different versions of SCP might have different definitions for service key. The setting of
this parameter must match the version of the SCP. With SCP provided by Huawei as an
example, the correspondence between service keys and IN services is as follows:
z
01:
ACC
02:
FPH
03:
VPN
04:
UPT
05:
VOT
06:
PPS
07:
MAS
08:
NP
09:
AD
1A:
UCS
FC:
IPN
In addition, the system presets the language kind indexes of the commonly used
language positions for the service key FE during the initialization. The service key
FE is a wildcard character that can match the service key parameter in any recorded
announcement message ID (but with the lowest priority). That is, when analyzing the
service key in a recorded announcement message ID, the SoftX3000 first searches in
the language kind index table whether there is a service key field that matches the
service key in the recorded announcement message ID. If so, the SoftX3000 uses this

15-66

record for analysis. If not, the SoftX3000 uses the data related to the service key FE
for analysis.
[Language kind index]
used to specify the value of the language position parameter carried in the recorded
announcement message ID sent from the SCP to the SSP. The value of this parameter
is a 2-digit hexadecimal number and must comply with the definition rules of the
language codes described in Section 15.1.4 Recorded Announcement Message ID.
[Language kind number]
This parameter specifies the number of languages in which recorded announcements
are played for the corresponding IN service of the service key. The value range is 1 to 8.
Set this parameter by the following principles:
z
If you set this parameter to 1, it indicates that recorded announcements are

played only in one language which is defined by the parameter Language kind 1.
If you set this parameter to 2, it indicates that recorded announcements can be

played in two languages which are defined by the parameters Language kind 1
and Language kind 2 in sequence.
For other value of this parameter, its meaning can be deduced in the same way.
[Language kind 1] to [Language kind 8]

These parameters specify the languages and their sequence to play back recorded
announcements. If the language kind number parameter is set to 1, the language
kind 1 parameter is available. If the language kind number parameter is set to 2, the
language kind 1 and language kind 2 parameters are available. Other cases can be
deduced in the same way. The playback sequence for recorded announcements is
language kind 1, language kind 2...language kind 8. These parameters are defined
in the ADD LKND command and referenced here.
15.7.5 Adding Money Category (Optional)

I. Related commands
Command
Function
ADD MCAT
To add money category
RMV MCAT
To remove money category
MOD MCAT
To modify money category
LST MCAT
To list money category

15-67


data configuration.
In an IN announcement, the SCP sends price information to the SSP through an INAP
message. The price information related to the conversation fee or the balance of the
card is carried in a 32-bit field. In that field, the most significant four bits are used for
money category index and the remaining bits for price value. The coding format is as
follows:
4 bits
28 bits
Money category index
Price value
Each money category index corresponds to a record in the language kind index table in
the database of the host. That record defines the rules for playing the price information
corresponding to the money category index, for example, the sequence of playing price
value and price units. Usually, the preceding rules pre-defined by the system are able to
meet the requirements of playing a price information related announcement. If the
carriers have special requirements, you can use the ADD MCAT command to add a
new money category.

[Money category index]
used to specify the index of the money category carried in the Apply Charging
operation sent by the SCP to the SSP. Currently, this index is set to 1.
[Money category]
This parameter specifies the currency type that the money category index represents.
z
US dollar
Chinese RMB
Malaysian dollar
15.7.6 Adding Record Announcement Message ID Conversion (Optional)

I. Related commands
Command
Function
ADD MSGCVT
To add record announcement message ID conversion
RMV MSGCVT
To remove record announcement message ID conversion
MOD MSGCVT
To modify record announcement message ID conversion

15-68

Command
Function
LST MSGCVT
To list record announcement message ID conversion

data configuration.
When an announcement is to be played in an IN service, the SCP includes the
message ID, which identifies the record announcement, in the INAP, and sends it to the
SSP. The SSP will then retrieve the correct audio resources from the MRS and play the
announcement.
Because INAP has, among its different versions, different definitions of record
announcement message ID, the SoftX3000 will identify follow C-INAP to identify the
message ID and play announcement. Therefore, when the SoftX3000 is observing
other INAP standard versions, such as R-INAP, to interwork with the SCP, you have to
use ADD MSGCVT to convert the message ID of the record announcement before the
SoftX3000 can play the announcement as required by the IN service.

[Old message ID]
It is the message ID that the SCP sends in an INAP message to the SoftX3000 before
the conversion. It is a decimal value, and ranges from 0 to 255.
To enable the message ID conversion feature, you have to use MOD FSFP to set the
bit11 of the software parameter SSP internal parameter 2 (P78) to 0.
[New message ID]
It is the message ID that the SoftX3000 uses, in conformity with the C-INAP standard,
to identify the record announcements. The parameter consists of three partsservice
key, language position, and record announcement number. It is a hexadecimal numeral
in format of 0xSSLL****.
15.7.7 Adding Mapping between Message ID and Tone ID (Optional)

I. Related commands
Command
Function
ADD MSGTONE
To add mapping between message ID and tone ID
RMV MSGTONE
To remove mapping between message ID and tone ID
MOD MSGTONE
To modify mapping between message ID and tone ID
LST MSGTONE
To list mapping between message ID and tone ID

15-69


data configuration.
Usually, IN announcements for IN services are recorded and then loaded to the MRS.
IN announcements belong to a different mechanism from signal tones for basic
services. The two mechanisms cannot be shared with each other. If you really want to
replace some IN announcements with signal tones, for example, to save the memory of
the MRS, you can use the ADD MSGTONE command to add the mapping relationship
between IN announcements and signal tones.

[Message ID]
This parameter specifies the recorded announcement message ID which is sent by the
SCP to the SSP through an INAP message. The value range is 0 to 2147483647. It
should be noted that what is typed here is a decimal number while the corresponding
recorded announcement message ID is a hexadecimal number. Do convert the
expected number to the correct form. If the expected recorded announcement
message ID is, for example, 0x01A00010, what you type here should be 27262992.
[Tone ID]
This parameter specifies the signal tone code in the MGCP message sent by the
SoftX3000 to instruct the MRS for playing announcement. Usually, the signal tone code
typed here is used for basic services. The value range is 0 to 255. It should be noted
that what is typed here is a decimal number while the corresponding signal tone code is
a hexadecimal number. Do convert the expected number to the correct form. If the
expected signal tone code is, for example, TID_0x0013, what you type here should be
19.
15.8 Special Configuration Commands

15.8.1 Adding IN Service Special Signaling
I. Related commands
Command
Function
ADD SRVSIG
To add IN service special signaling
RMV SRVSIG
To remove IN service special signaling
MOD SRVSIG
To modify IN service special signaling
LST SRVSIG
To list IN service special signaling

15-70


data configuration.
When the SoftX3000 acts as an SSP and also functions as a transit office on the
network, if it is required to charge an incoming single-stage dialing IN call (for example,
NP incoming service or APS service) after the SCP sends a play-announcement (PA)
operation (for example, notifying the caller of called number changed or called
subscriber busy) to the SSP, that is, if it is required to send an Address Complete
Message (ACM) instead of the default answer signal from the local office to the
originating office (the calling side), you need to use the ADD SRVSIG command to add
a special signaling for the IN service. The purpose is to prevent the local office from
returning an answer signal to misguide the opposite to charge such a call.

[Service key]
This parameter specifies the service key of the IN service for which the special
signaling is to be added. This parameter is defined in the ADD TDPCFG command and
referenced here.
[Special signaling]
This parameter specifies whether or not the local office sends an answer signal to the
originating office (the calling side) after the SCP sends the PA operation to the SSP. By
default, an answer signal is sent. If you select PA send answer signal, it indicates to
send an ACM signal.
15.8.2 Adding Caller Description of Local IN Call

I. Related commands
Command
Function
ADD CLILOC
To add caller description of local IN call
RMV CLILOC
To remove caller description of local IN call
MOD CLILOC
To modify caller description of local IN call
LST CLILOC
To list caller description of local IN call

data configuration.
By default, the calling number in an IN call always is the original calling number of the
calling party. In this way, the exchange with the called party can obtain the exact calling
15-71

number of the calling party. If you want to mask the original calling number in the IN call,
you can use the ADD CLILOC command to add the caller description related to the IN
call.

[Service key]
This parameter specifies the service key of the IN service for which the caller
description is to be added. This parameter is defined in the ADD TDPCFG command
[Call prefix]
This parameter specifies the IN call prefix for which the caller description is to be added.
This parameter is defined in the ADD CNACLD command and referenced here.
[Select caller number to be sent]
This parameter specifies the policy used by the SSP to send the calling number. The
meanings of the available options are as follows:
z
Original caller number: If the caller is in the local office, the calling number is the
real number of the calling subscriber. If the caller is in other office, the calling
number is the calling number sent by the opposite office through an incoming
office signaling message.
Charging number: The calling number is the charging number specified in the
INAP charging message packet which is sent by the SCP to the SSP.
Assigned number: The calling number is a telephone number that you configured.
[Assigned number]
When the select caller number to be sent parameter is set to assigned number, this
parameter is available to configure the telephone number to be sent.
15.8.3 Adding Network Access Code

I. Related commands
Command
Function
ADD NACCODE
To add network access code
RMV NACCODE
To remove network access code
MOD NACCODE
To modify network access code
LST NACCODE
To list network access code

data configuration.
15-72

When the SoftX3000 acts as an SSP and also functions as a transit office on the
network, it may be required for the local SSP to transit the IN-based traffic transferred
by other telecom carriers. To identify the network to which the calling subscriber
belongs (that is, the telecom carrier to which the calling subscriber belongs) to
implement different charging and routing policies, you need to add the network access
code using the ADD NACCODE command.

[Network access code]
This parameter specifies the prefix of the calling subscriber number which is sent from
a network to the local SSP. Based on this code, the SSP identifies the telecom carrier to
which the calling subscriber in an IN call belongs.
[Network name]
This parameter specifically describes a network access code for identification purposes
with a string of characters.

15-73

Chapter 16 Configuring UC Service Data

16.1.1 Architecture of UC System
The Unified Communication (UC) system correlates communication networks with the
Internet. The U-SYS integration solution proposes that the UC system be physically
composed of the softswitching network and a group of UC servers. The architecture of
the UC system based on the Information Technology (IT) system of Microsoft is
illustrated in Figure 16-1.
UC Portal
Directory Server
IM Server
E-mail Server
Call Log Server
Fax Gateway
VM Server
UC Agent
UC server group
Softswitching network
SIP
SIP + MML
PRA trunk
SoftX3000
ISUP trunk
IP MAN
PRA trunk
PSTN
TMG
AMG
IAD
SIP
Phone
H.323
Phone
Figure 16-1 Architecture of UC system (an IT system based on Microsoft software)
I. Softswitching network
The softswitching network is composed of network control layer devices, core switching
layer devices, and edge access layer devices that are present in the NGN architecture.
The softswitching network provides a variety of NGN communication capabilities. The
core entity on the network is the SoftX3000.
The interconnection between the softswitching network and the UC server group
involves the following parts:
16-1

Interconnection between
Using
SoftX3000 and UC Agent
SIP and MML
SoftX3000 and Call Log Server
SIP
SoftX3000 and Fax Gateway through TMG
PRA trunk
SoftX3000 and Voice Mail (VM) Gateway through TMG
PRA trunk
II. UC server group

The UC server group is logically located at the service management layer of the NGN
architecture, used to provide various communication capabilities for the IT system.
According to the software functions, the UC server group is structured with eight
software modules and the core software module is UC Agent.
z
UC Agent: The UC Agent is the connection point between a communication

network and the Internet and is responsible for triggering UC services and
transferring MML messages between UC subscribers and the SoftX3000. The UC
Agent communicates with the SoftX3000 through SIP and MML.
Call Log Server: The Call Log Server is responsible for receiving call related
records of UC subscribers from the SoftX3000 and storing the records in a local or
remote SQL database. The Call Log Server communicates with the SoftX3000
through SIP.
UC Portal: The UC Portal provides Web pages for UC subscribers to access the
UC system, such as login page, operation page, and maintenance page.
Directory Server: The Directory Server employs Microsoft Active Directory (AD)
structure and implements, when UC subscribers log in to the UC system, the
authentication and management functions.
Instant Messaging (IM) Server: The IM Server adopts Microsoft Live

Communication server 2003 and provides instant messaging and online alerting
functions on intranet.
E-mail Server: The E-mail Server adopts Microsoft Exchange 2003, used to
provide mobile, remote, desktop access service functions to e-mail messages with
security and privacy.
Fax Gateway: The Fax Gateway implements fax transmission and reception
functions, and provides fax-to-e-mail and e-mail-to-fax conversion capabilities.
The Fax Gateway communicates with the Internet through TCP/IP. The Fax
Gateway must provide PRA trunk to TMG in the softswitching network.
VM Server: The VM Server records users voice messages in digital voice files and
stores the files on the hard disk of the server. (The UC Agent is responsible for
sending the files to the e-mail box of the destination UC subscriber.) The VM
Server communicates with the Internet through TCP/IP. The VM Server must
provide PRA trunk to TMG in the softswitching network.

16-2

According the UC subscriber capacity, you can configure the eight software modules
either in different servers or appropriately together. If you choose to configure the
software modules appropriately together, remember that:
z
At least two servers are required.
UC Agent and Call Log Server are configured in different servers.
Suppose a UC system supports a capacity of 20 000 subscribers, the configuration of

UC server group is shown in Table 16-1.
Table 16-1 Configuration of UC server group
Server
No.
Configured software
module
To provide
Server 1
UC Agent and Directory

Server
UC call management interfaces to the

SoftX3000 and authentication directory
(address book) services
Server 2
Call Log Server and E-mail

Server
E-mail server and call log management

services
Server 3
UC Portal and IM Server
Portal, Web pages, instant messaging,

and presence management services
Server 4
Fax Gateway
Server
Fax gateway and voice mail services
and
VM
16.1.2 UC Intelligent Calling Routing

According to caller number and UC subscribers state, Intelligent Calling Routing (ICR)
enables the subscribers call to be routed to either a pre-defined destination phone set
or a pre-determined voice mailbox or allows notifying the UC subscriber of the call by
means of instant messaging service.
I. ICR conditions
When a UC subscriber sets the ICR data in the SoftX3000, the SoftX3000 determines a
suitable dealing mode depending on the following conditions:
z
The caller group to which the calling subscriber belongs
The caller group refers to the classification of callers that make calls to the UC
subscriber. Depending on the calling number, the UC subscriber can select an
appropriate ICR dealing mode. For example, a UC subscriber defines the telephone
numbers of relatives in the caller group 0 and the telephone numbers of colleagues in
the caller group 1. In this way, the UC subscriber can customize different ICR dealing
modes respectively for incoming family calls and work-related calls.
z
The current state of the UC subscriber

16-3

The current state indicates the communication state of the UC subscriber at a specific
time point. In other words, the UC subscriber can customize different ICR dealing
modes depending on the state at specific time points. For example, a UC subscriber
defines the state during the on-duty time as online and the state during the off-duty
time as offline. In this way, the UC subscriber can customize different ICR dealing
modes for incoming calls during on-duty time and off-duty time based on the current
state.
II. ICR dealing modes

z
Rejecting incoming call: When the UC subscriber is called, the SoftX3000 rejects
the incoming call.
Sequence-based forwarding: When the UC subscriber is called, the SoftX3000

routes the call to the several destination called numbers pre-defined in the
database one by one based on their sequence until there is an answer or all
destination called numbers fail to be connected.
Parallel forwarding: When the UC subscriber is called, the SoftX3000 attempts to

connect the call to all destination called numbers pre-defined in the database until
there is an answer from a destination or all destination called numbers fail to be
connected.
Forwarding to voice mailbox: When the UC subscriber is called, the SoftX3000

routes the call to a voice mailbox that is specified by the subscriber.
Forwarding to text terminal: When the UC subscriber is called, the SoftX3000

notifies the subscriber of the call by means of instant messaging service.
Hybrid forwarding: When the UC subscriber is called, the SoftX3000 attempts to

forward the call to the pre-defined destination called numbers. If the forwarding
fails, the SoftX3000 routes the call to the specified voice mailbox or notifies the
subscriber of the call by means of instant messaging service.
III. ICR setting modes

ICR data can be set in two ways: UC subscriber can set through Web pages and
maintenance personnel can set through MML commands. In the first mode, the UC
subscriber must use UC Agent to operate the host database of the SoftX3000.
16.2 Configuring UC Service Data

16.2.1 Overview
UC service data defines the IP address of the UC Agent, the IP address of the Call Log
Server, UC subscribers, and ICR data. To configure UC service data, make sure that
local office data and subscriber data has been configured, as shown in Figure 16-2.

16-4

Start
Equipment data
Trunk data
Office data
Number analysis
Charging data
Subscriber data
MG data
Centrex data
MRS data
Call barring data
Protocol data
IN service data
Signaling data
Other service data
Routing data
Other application
data
End

During the process of configuring UC service data, some parameters defined when
configuring local office data and subscriber data will be referenced in the UC service
data. See Table 16-2.
Table 16-2 Parameter referencing relationship between UC service data and other
data
Input parameter
Name
Output parameter
Defined in
Name
Referenced in
Local DN set
Local office data
Call source code
Local office data
Subscriber number
Subscriber data
II. Preparations
Before configuring UC service data, make sure that all preparations are done as

16-5


SN
Item
IP address of UC Agent
IP address of Call Log Server
IP address of UC application server

Table 16-4 lists the general steps for configuring UC service data.
Step
Description
Command
Add UC agent server
ADD UCA
Add UC application server
ADD APS
Add UC subscriber
ADD USBR
Add workstation
ADD WS
Add UC caller group (optional)
ADD UCCG
Add UC date information (optional)
ADD UCDATE
Add UC presence status data (optional)
ADD UCPRE
Set UC presence status data (optional)
SET UCPRE
Add UC profile (optional)
ADD UCPFL
10
Set UC profile (optional)
SET UCPFL
11
Add UC intelligent calling routing (optional)
ADD UCICR

configuring UC service data.

16-6

ADD UCA
[UC group number]
[Call source code]
[UCA address]
ADD UCS
[Local DnSet]
[UC subscriber number]
[UC group number]
ADD UCCG
[Local DnSet]
[Caller group number]
ADD UCICR
[Local DnSet]
[Presence state]
16.2.2 Adding UC Agent Server

I. Related commands
Command
Function
ADD UCA
To add UC agent server
RMV UCA
To remove UC agent server
MOD UCA
To modify UC agent server
LST UCA
To list UC agent server

[Agent server group number]
16-7

This parameter identifies a UC agent server group uniquely in the SoftX3000. Its value
ranges from 0 to 65535.
[IFMI/MSGI module number]
This parameter specifies the module number of the IFMI or the MSGI that is
responsible for dispatching protocol messages of the UC agent server. This parameter
is defined in the ADD BRD command and referenced here.
[Agent server IP address]
This parameter specifies the IP address of the server running the UC agent software.
This is one of the interconnection parameters between the SoftX3000 and the UC
server group. This parameter must be defined correctly; otherwise, the UC service
cannot be used.
[Agent server port number]
It specifies the number of the UDP port through which the SoftX3000 communicates
with the UC agent server. By default it is 5060. This is one of the interconnection
parameters between the SoftX3000 and the UC agent server. This parameter must be
defined the same as the UDP port number of the UC agent server; otherwise, the UC
service cannot be used.
[Agent server domain]
It defines the domain name of the UC agent server used in the Internet. This is one of
the interconnection parameters between the SoftX3000 and the UC agent server.
[Call log IP address]
This parameter specifies the IP address of the server running the Call Log Server
software module. This is one of the interconnection parameters between the SoftX3000
and the UC server group.
If you do not specify this parameter, the system will set the Call Log Server software to
run on the UC agent server.
[Heartbeat test module number]
It specifies the module number of the UCSI board, the designated board in SoftX3000
that is used to send heartbeat test signals to the UC agent server (SIP-based). This
parameter must be defined by ADD BRD before it can be used here.
As the SoftX3000 interconnects the UC agent server through SIP trunks, the former
sends heartbeat test signals to the latter to prevent the suspension of SIP trunks during
network interruption.
[Heartbeat test time(s)]
It specifies the interval between which the SoftX3000 sends a heartbeat test signal to
the UC agent server. It ranges from 10 to 180, in unit of second. The default value is 60.

16-8

16.2.3 Adding UC Application Server

I. Related commands
Command
Function
ADD APS
To add UC application server
RMV APS
To remove UC application server
MOD APS
To modify UC application server
LST APS
To list UC application server

[Application server group number]
It uniquely identifies a UC application server group (for example, Huawei U-NICA) in
the SoftX3000. It ranges from 0 to 65535.
[The description of application server]
It describes a UC application server group in details. It is in character string.
[Server type]
It defines the value-added services supported by the UC application service, such as
ringback tone (RBT) service.
[Service access code]
It specifies the access code that triggers a UC service. The parameter must first be
defined by ADD CNACLD before it can be used here.
Different from normal IN services, such NGN value-added services as SIP-PPS and
ONLY are triggered by AS (for example, the U-NICA of Huawei) that controls their
service logics. You only need to enter the corresponding access code at SoftX3000
side and route the service to the corresponding SIP trunk.
16.2.4 Adding UC Subscriber

I. Related commands
Command
Function
ADD USBR
To add UC subscriber
RMV USBR
To remove UC subscriber
MOD USBR
To modify UC subscriber
LST USBR
To list UC subscriber

16-9


This parameter specifies the telephone number of the UC subscriber when you are
defining an ESL subscriber, multimedia subscriber, or ISDN subscriber of the local
office to be a UC subscriber. This parameter is defined in ADD VSBR, ADD MSBR, or
ADD BRA, and referenced here.
[Local DN set]
This parameter specifies the local DN set to which the UC subscriber belongs. This
[UCSI module number]
It specifies the module number of the UCSI board which processes the UC calls in the
SoftX3000. It ranges from 22 to 101. The parameter must first be defined by ADD BRD
before it can be used here.
[UC call-out authority]
It defines the call-out authorities of a UC subscriber. It can be intra-office, local, local
toll, national toll, international toll, intra-Centrex, outgoing Centrex, intra-office
national toll, and intra-office international toll. By default, the subscriber has All
(call-out authorities) except national and international toll, intra-office national and
international toll.
[UC call-in authority]
It defines the call-in authorities of a UC subscriber. It can be intra-office, local, local
toll, national toll, international toll, intra-Centrex, outgoing Centrex, intra-office
national toll, and intra-office international toll. By default, the subscriber has all call-in
authorities.
[UC operation authority]
It defines the service authorities of a UC subscriber. It can be click to dial (CTC), click
to conference (CTF), click to forwarding, click to transfer, call-in, call-out, and
intelligent call route. By default, the subscriber has all UC operation authorities.
[UC increment authority]
It defines the value-added service authorities of a UC subscriber. It can be RBT, call log,
instant bill, and so on. By default, the subscriber has all value-added service
authorities.
[Original binding number type]
It specifies that the original binding number of the UC subscriber is within the office or
out of the office.
[Original binding number]

16-10

It specifies the original number to be bound with the UC subscriber number. The
number can be a subscriber number, national valid number, or international valid
number.
[Temporary binding number]
This parameter specifies the telephone number to which the UC subscriber number is
bound temporarily. The telephone number can be a subscriber number, national
significant number, international significant number, or a mobile number. The
temporary binding number specified for the UC subscriber number is used for the
following purposes:
z
When the UC subscriber number is called, the SoftX3000 automatically and

unconditionally forwards the call to the temporary binding number.
When the UC subscriber uses the CTD service through a Web page, the
SoftX3000 first sends the ringing tone to the phone set with the temporary binding
number (that is, the caller). After the caller hooks off, the SoftX3000 sends the
ringing tone to the called party.
[Agent server group number]

This parameter specifies the number of the UC group to which the UC subscriber
belongs. This parameter is defined in the ADD UCA command and referenced here.
[UC trigger type]
It specifies the mode that the system adopts to trigger the UC service. Here are the
options:
z
Caller trigger: Triggered by the UC agent or the original binding terminal.
Callee trigger: Triggered when the UC subscriber is the callee.
Both side trigger: It is a combination of the above two options.
[Call source code]

It specifies the call source to which the UC subscriber belongs. The parameter must
first be defined by ADD CALLSRC before it can be used here.
It is one of the charging attributes of a subscriber. The parameter must first be defined
by ADD CHGGRP or ADD CHGIDX before it can be used here. Refer to chapter 4,
Configuring Charging Data for details.
It is one of the charging attributes of a subscriber. The parameter must first be defined
by ADD CHGCLD before it can be used here. The default value is 255, which means
that the system does not charge the callee. Refer to chapter 4, Configuring Charging
Data for details.

16-11

16.2.5 Adding Workstation

I. Related commands
Command
Function
ADD WS
To add workstation
RMV WS
To remove workstation
MOD WS
To modify workstation
LST WS
To list workstation

Because MML interface is provided between the UC Agent and the SoftX3000, the UC
Agent is logically equivalent to a workstation of the SoftX3000 terminal system.
Therefore, execute the ADD WS command to define the IP address of the UC Agent to
a workstation so that the UC Agent can normally transfer MML messages between UC
subscribers and the SoftX3000.

[Workstation name]
This parameter specifies the name of a workstation in the SoftX3000 terminal system
with a string of characters.
[IP address]
This parameter specifies the IP address of the workstation. Here, it is the IP address of
the UC Agent.
[Command group]
This parameter specifies the command group to which the workstation belongs. To
ensure the security of the SoftX3000 terminal system, restrict the authorities of the
command group to which the UC Agent belongs. It is recommended to define the UC
Agents command group to be G_20 (Unified communication agent class).
16.2.6 Adding UC Caller Group (Optional)

I. Related commands
Command
Function
ADD UCCG
To add UC caller group
RMV UCCG
To remove UC caller group
MOD UCCG
To modify UC caller group

16-12

Command
Function
LST UCCG
To list UC caller group

data configuration.
There are two ways to set ICR data:
z
UC subscribers can set it through Web pages.
You can set it through MML commands.
When using the second mode, first of all, you need to execute the ADD UCCG
command to add a caller group.

[Local DN set]
This parameter specifies the telephone number of the UC subscriber as the called party
in a caller group. This parameter is defined in the ADD UCS command and reference
here.
[Caller number]
This parameter specifies the prefix of the calling number in a caller group. In one caller
group, you can set multiple calling numbers for one UC subscriber number. The
SoftX3000 uses the maximum matching principle during the ICR analysis.
What is maximum matching? For a calling number, the system searches all calling
prefixes for the most similar one, based on which the system carries out the
corresponding processing. For example, a caller group is configured with three calling
numbers, 13, 139, and 1390. If the calling number sent by the opposite office is
13901234567, according to the maximum matching principle, the system finds the
most similar calling prefix 1390. Neither 13 nor 139 complies with the maximum
matching principle.
This parameter specifies the caller group number that uniquely identifies a UC caller
group inside the SoftX3000. The value range is 0 to 255. The configuration principles of
this parameter are as follows:
z
For the same UC subscriber, maintenance personnel can define the subscriber in
a maximum of 10 caller groups.

16-13

z
For the same UC subscriber, maintenance personnel can define a maximum of 20

calling numbers for the subscriber in all caller groups to which the subscriber
belongs.
16.2.7 Adding UC Date Information (Optional)

I. Related commands
Command
Function
ADD UCDATE
To add UC date information
MOD UCDATE
To modify UC date information
RMV UCDATE
To remove UC date information
LST UCDATE
To list UC date information

data configuration.
UC subscribers time state information can be set in two ways:
z
When using the second mode, you need to execute the ADD UCWEEK, ADD
UCDATE and ADD UCTIME commands.

[Local DN set]
This parameter specifies the telephone number of the UC subscriber to which the date
information is to be added. This parameter is defined in the ADD UCS command and
referenced here.
[Day]
This parameter specifies a specific date. What is typed in this parameter must be a
valid date in the format of MM&DD, in which MM represents a month in the range from
01 to 12 and DD represents a date in the range from 01 to 31.
[Date type]
This parameter specifies the date type of the specific day as defined in the previous
parameter day. The meanings of the parameter options are as follows:
16-14

Off duty: The subscriber is off duty on the day.
On duty: The subscriber is on duty on the day.
User-defined type 1 to User-defined type 18: The date type is defined by the
subscriber
16.2.8 Adding UC Presence Status Data (Optional)

I. Related commands
Command
Function
ADD UCPRE
To add UC presence status data
RMV UCPRE
To remove UC presence status data
MOD UCPRE
To modify UC presence status data
LST UCPRE
To list UC presence status data

data configuration.
A UC subscriber can set his/her status by using the client software WorkSpace (it is the
UC software of Huawei) to facilitate the SoftX3000 to implement the ICR feature. You
can define a maximum of 20 presence statuses for a UC subscriber. The names of
three statuses including offline, online, and departing are pre-defined by the
system and cannot be modified by the UC subscriber. The names of the other 17
statuses can be customized by the UC subscriber through Web pages or the command
ADD UCPRE.
You can use the command LST UCPRE to query, the command MOD UCPRE to
modify, and the command RMV UCPRE to remove customized status set through Web
pages by UC subscribers.

[Local DN set]
It specifies the local DN set to which the UC subscriber belongs. The parameter must
first be defined by ADD LDNSET before it can be used here.
It specifies the telephone number of the UC subscriber whose customized status data
is to be configured. The parameter must first be defined by ADD USBR before it can be
used here.
[Presence type]

16-15

It specifies the type of the presence status customized by the UC subscriber. You can
define a maximum of 17 types for a UC subscriber.
[Presence description]
It details the presence status customized by the UC subscriber (for example, the
communication status at a specific time point and even the mood of the UC subscriber.)
It contains a string of a maximum of 64 characters.
16.2.9 Setting UC Presence Status Data (Optional)

I. Related commands
Command
Function
SET UCPRE
To set UC presence status data
LST UCPRE
To list UC presence status data

data configuration.
The presence status of a UC subscriber indicates the SoftX3000 to implement the ICR
feature. It can be set in two ways:
z
When using the second mode, you need to execute the SET UCPRE command.

[Local DN set]
It specifies the telephone number of the UC subscriber whose presence status data is
to be configured. The parameter must first be defined by ADD USBR before it can be
used here.
[Presence type]
It specifies the type of the presence status of the UC subscriber.

16-16

16.2.10 Adding UC Profile (Optional)

I. Related commands
Command
Function
ADD UCPFL
To add UC profile
RMV UCPFL
To remove UC profile
MOD UCPFL
To modify UC profile
LST UCPFL
To list UC profile

data configuration.
UC profiles are used to implement ICR feature of UC subscribers. That is, UC
subscribers can configure related ICR data by using preset configuration profiles. UC
subscribers activate different configuration profiles in different time segments to
implement different ICR strategies.
The SoftX3000 allows each UC subscriber to define a maximum of 10 configuration
profiles to implement different ICR strategies. Profiles can be set in two ways:
z
You can set it through the MML command ADD UCPFL.
When using the first mode, you can execute the LST UCPFL command to query, the
MOD UCPFL command to modify, or the RMV UCPFL command to remove a profile.

[Local DN set]
It specifies the telephone number of the UC subscriber whose UC profile data is be
configured. The parameter must first be defined by ADD USBR before it can be used
here.
[Profile index]
It defines the profile index for the UC subscriber. It ranges from 1 to 10, which means
that ten profile indexes can be configured at maximum. The command is only for the
configuration of profile indexes. For configuring ICR data related to profile indexes,
execute the command ADD UCICR.
[Profile type]
16-17

It specifies whether the profile index is based on time or presence status.

[Profile name]
It describes a UC profile. It is in character strings.
16.2.11 Setting UC Profile (Optional)

I. Related commands
Command
Function
SET UCPFL
To set UC profile
LST UCPFL
To list UC profile

data configuration.
UC profiles are used to indicate the SoftX3000 to implement the ICR feature. Preset
profiles can be activated in two ways:
z
When using the second mode, you need to execute the SET UCPFL command.

[Local DN set]
It specifies the telephone number of the UC subscriber whose UC profile data is be
configured. The parameter must first be defined by ADD USBR before it can be used
here.
[Profile index]
It defines the index of the profile of the UC subscriber to be activated. It ranges from 1
to 10. The parameter must first be defined by ADD UCPFL before it can be used here.
16.2.12 Adding UC Intelligent Calling Routing (Optional)

I. Related commands
Command
ADD UCICR
Function
To add UC intelligent calling routing data
16-18

Command
Function
RMV UCICR
To remove UC intelligent calling routing data
MOD UCICR
To modify UC intelligent calling routing data
LST UCICR
To list UC intelligent calling routing data

data configuration.
There are two ways to set ICR data:
z
When using the second mode, you need to execute the ADD UCICR command to add
the ICR data.

[Local DN set]
This parameter specifies the telephone number of the UC subscriber whose ICR data is
to be configured. This parameter is defined in the ADD USBR command and
referenced here.
This parameter specifies the caller group to which the UC subscriber controlling the
ICR dealing mode belongs. This parameter is defined in the ADD UCCG command and
referenced here. 254 is a wildcard that represents all caller group numbers, but it has
the lowest priority.
[UC profile index]
It specifies the index of the UC profile corresponding to the ICR data. This parameter is
defined in the ADD UCPFL command and referenced here.
[Profile type]
It specifies the UC profile type used by the ICR. This parameter must be defined the
same as the UC profile index defined in ADD UCPFL; otherwise, the system will
generate a fault alarm.
[Date type]
It specifies the date type used by the ICR. It is valid only when the profile type' is time.

16-19

[Start time] and [End time]

The two parameters define the time segment during which the UC subscriber uses the
ICR mode. They are valid only when the profile type' is time
[Presence type]
This parameter specifies the presence status of the UC subscriber determining the ICR
dealing mode. You can define different ICR dealing modes for a maximum of 20
presence statuses for a UC subscriber. The names of three statuses including offline,
online, and departing displayed on a UC client are pre-defined by the system and
cannot be modified by the UC subscriber. The names of the other 17 statuses displayed
on UC client can be customized by the UC subscriber through Web pages.
The presence status specified here is one of the conditions for judging an appropriate
ICR dealing mode in the database of the SoftX3000. It is not the current status of the
UC subscriber.
[ICR dealing mode]
This parameter specifies the ICR dealing mode. The meanings of the parameter
options are as follows:
z
None: The UC subscriber does not use the ICR service.
Call rejected: The UC subscriber rejects an incoming call.
To voice mailbox: When the UC subscriber is called, the SoftX3000 routes the call
to a voice mailbox that is specified by the subscriber.
To text terminal: When the UC subscriber is called, the SoftX3000 notifies the
subscriber of the call by means of instant messaging service.
Sequent forwarding: When the UC subscriber is called, the SoftX3000 routes the
call to the several destination called numbers pre-defined in the database one by
one based on their sequence until there is an answer or all destination called
numbers fail to be connected.
Parallel forwarding: When the UC subscriber is called, the SoftX3000 attempts to

connect the call to all destination called numbers pre-defined in the database until
there is an answer from a destination or all destination called numbers fail to be
connected.
[Additional dealing mode]

When the ICR dealing mode is set to sequent forwarding or parallel forwarding, this
parameter specifies how to do next when the destination called numbers fail to be
connected. The meanings of the parameter options are as follows:
z
No dealing: The hybrid forwarding service is not started.
To voice mailbox: When the destination called numbers fail to be connected, the
SoftX3000 routes the call to a voice mailbox specified by the UC subscriber.
To text terminal: When the destination called numbers fail to be connected, the
SoftX3000 notifies the UC subscriber of the call by means of instant messaging
service.
16-20

[Voice mailbox or terminal]

This parameter specifies the number of the corresponding terminal. The configuration
principles of the parameter are as follows:
z
When the ICR dealing mode is set to to_voice_mailbox, the voice mailbox
number of the UC subscriber must be specified in this parameter.
When the ICR dealing mode is set to to_text_terminal, this parameter is not
specified.
When the ICR dealing mode is set to sequent forwarding or parallel forwarding
and the additional dealing mode is defined, this parameter specifies the
corresponding terminal number for the additional dealing mode.
[Call forwarding mode 1] to [Call forwarding mode 10]

The parameters specify whether the ICR dealing mode is sequence mode or parallel
mode. The sequence mode corresponds to the ICR dealing mode sequence
forwarding, and the parallel mode corresponds to the parallel forwarding.
[Call forwarding number 1] to [Call forwarding number 10]
The parameters specify the destination called numbers. They are valid only when the
ICR dealing mode is sequent forwarding or parallel forwarding.
[Trial calling time of sequent call forwarding 1] to [Trial calling time of sequent call
forwarding 5]
The parameters specify the ringing monitor duration of the destination called number
(forwarding number). It ranges from 0 to 60, in unit of second. The default value is 10.

16-21

Chapter 17 Configuring Network Management Data
Chapter 17 Configuring Network Management

Data
17.1 Background Knowledge
17.1.1 Overview to Network Management Instructions
To ensure the quality of service (QoS) of the telecommunications networks, carriers
need to design the network capacity and inter-node routes reasonably and manage the
nodes in the network efficiently. In this way, traffic can be restricted in the case of
overload to reduce call loss and guarantee the reliable and efficient operation of the
network.
Network Management (NM) is implemented by the Network Management Center (NMC)
to control, schedule, and measure the nodes, such as switching equipment and
transmission equipment, in the telecommunications network. Controlling outgoing calls
of nodes and scheduling routes is the core NM function.
To achieve NM, the nodes in the network should be able to receive and carry out the
instructions from the NMC. The SoftX3000 offers abundant NM instruction sets, which
facilitates the carriers to control and schedule the SoftX3000.
17.1.2 Purposes of Network Management Instructions

The NM instruction sets of the SoftX3000 include originating destination code control,
outgoing destination code control, call gap control, circuit orient control, circuit reject
control, direct route control, alternative route cancellation control, temporary alternative
route control, skip sub-route control, special record notification control, trunk reserved
control, and Hard To Reach (HTR) control.
The purposes of these NM instructions are described as follows.
I. Originating destination code control

It means that the switch prohibits the calls to designated destination codes from
designated incoming trunks or callers by a certain percentage.
z
Designated incoming trunks: Incoming trunk groups configured with a specific NM

source code.
Designated callers: Callers with specific caller category, country code, area code,
office number, or subscriber number.
Designated destination codes: Specific country code, area code, office number,
subscriber number, or special service number.

17-1

Generally, whether an outgoing call is barred depends on the caller category, and
whether an incoming or forwarded call is barred depends on the incoming circuit group
type. The system first prohibits the calls from some common callers or trunks. After all
common calls are barred, the system prohibits the calls from priority callers or trunks.
Hierarchical barring of common calls is adopted, and 25% of total common calls are
barred for each level. There is no hierarchical barring of priority calls.
II. Outgoing destination code control

It means that the switch prohibits the calls to designated destination codes from
occupying designated outgoing trunks by a certain percentage.
z
Designated outgoing trunks: Outgoing trunk groups configured with a specific NM

source code.
III. Call gap control

It means that the switch restricts the maximum number of call attempts to designated
destination codes from designated callers during a certain interval.
That is, if the call attempts of designated callers to designated destination codes during
the designated interval exceed the number of call attempts defined here, the system
automatically starts the call barring function to prohibit these callers from dialing the
destination codes. The call barring will not end until the system cancels it automatically
or you cancel it with DEA NM.
z
Designated callers: Callers with specific caller category.
IV. Circuit orient control

It means that the switch changes bi-directional trunk circuits to incoming trunk circuits
according to the designated quantity or by a certain percentage.
V. Circuit reject control

It means that the switch suspends bi-directional and/or unidirectional trunk circuits
according to the designated quantity or by a certain percentage.
VI. Direct route control

It means that the switch restricts the direct traffic of the designated sub-route by a
certain percentage. It has two control modes:
z
Incoming prohibited (DRT): The switch prohibits the direct traffic to the designated
sub-route by a certain percentage. The overflown traffic is routed to the other
sub-routes.

17-2

Overflow prohibited(DRF): The switch prohibits the direct traffic overflown from the
designated sub-route by a certain percentage. The overflown traffic is canceled

directly.
VII. Alternative route cancellation control

It means that the switch restricts the alternative traffic of the designated sub-route by a
certain percentage.
Incoming prohibited (ART): The switch prohibits the alternative traffic to the
designated sub-route by a certain percentage. The overflown traffic is routed to

the other sub-routes. For example, a local network is networked as shown in
Figure 17-1. For Office A, Sub-route A to B is an alternative sub-route for C to B, D
to B, and E to B. If the direct traffic on Sub-route A to B is too heavy during a period
of time, you can prohibit the alternative traffic of C to B, D to B, and E to B from
entering Sub-route A to B with this NM instruction in order to ensure the direct
traffic on A to B.
D
Figure 17-1 Restricting alternative traffic (ART)

z
Overflow prohibited (ARF): The switch prohibits the alternative traffic overflown
from the designated sub-route by a certain percentage. The overflown traffic is
canceled directly. For example, a local network is networked as shown in
Figure 17-2. For Office A, Sub-route A to B is an alternative sub-route for C to B. If
both the direct and alternative traffic on Sub-route A to B is too heavy during a
period of time, you can prohibit the overflown alternative traffic of C to B from
entering Sub-route A to B again with this NM instruction in order to ensure the
direct traffic on A to B.

17-3

Figure 17-2 Restricting alternative traffic overflow (ARF)
VIII. Temporary alternative route control

It means that the switch allows the calls from designated callers or incoming trunks to
designated destination codes to use the designated alternative sub-routes temporarily
by a certain percentage.
z

source code.
IX. Skip sub-route control

It means that the switch allows the calls from designated callers or incoming trunks to
designated destination codes to skip the designated sub-route by a certain percentage.
The designated sub-route to be skipped can carry either direct traffic or alternative
traffic.
For example, a local network is networked as shown in Figure 17-3. For Office A,
Sub-routes A to B and A to D are alternative sub-routes for C to E. In normal cases,
Office A first selects Sub-route A to B (direct sub-route) and selects Sub-route A to D
(alternative sub-route) in the case of traffic overflow when transferring the calls
originated by Office C to Office E. If the direct traffic from Office A on Sub-route A to B is
too heavy during a period of time, you can prohibit the direct transfer traffic from
entering Sub-route A to B with this NM instruction in order to ensure the direct outgoing
traffic on A to B. That is, Office A can skip Sub-route A to B and directly selects
Sub-route A to D when transferring the calls originated by Office C to Office E.

17-4

Figure 17-3 Skip sub-route control
X. Special record notification control

It means that the switch can play the special announcement for the calls from
designated callers or incoming trunks to designated destination codes to notify the
callers or operators of delaying the calls.
z

source code.
XI. Trunk reserved control

It means that the switch dynamically adjusts the traffic of outgoing trunks according to
the availability of the designated outgoing trunk group. This NM instruction needs the
cooperation of the parameters Idle circuits for weak call restriction and Idle circuits for
forced call restriction of trunk groups. The options are
z
No call restriction: If the actual number of idle circuits of the designated trunk
group = Idle circuits for weak call restriction, this NM instruction is invalid.
Weak call restriction: If Idle circuits for forced call restriction = the actual number
of idle circuits of the designated trunk group < Idle circuits for weak call restriction,
the system restricts the calls by Weak restriction percent.
Forced call restriction: If the actual number of idle circuits of the designated trunk
group < Idle circuits for forced call restriction, that is, the trunk group is to be
congested, the system restricts the calls by Forced restriction percent.
XII. HTR control

It means that the switch can automatically prohibit the calls from designated callers or
incoming trunks to designated destination codes by a certain percentage if these
17-5

destination codes are not reachable to some extent. When a destination code is judged
as reachable, the system cancels call restriction automatically.
z

source code.
For example, if an incoming trunk makes more then 100 call attempts to a prefix 369
within five minutes and the answer attempt ratio is less than 10%, it means that the
office 369 is unreachable, and the switch will automatically restrict the calls to the prefix
369 by a certain percentage.
17.2 Configuring NM Instructions

17.2.1 Adding Originating Destination Code Control
I. Related commands
Command
Function
ADD NMIDEST
To add originating destination code control
MOD NMIDEST
To modify originating destination code control
LST NMIDEST
To list originating destination code control
RMV NM
To remove NM instruction

[NM ID number]
It identifies an originating destination code control NM instruction uniquely in the
SoftX3000, ranging from 0 to 65535. Generally, it is not set but allocated by the system
automatically.
IDs of NM instructions of the same type must be different, but those of different NM
instructions can be the same.
[Local DN set]
It specifies the local DN set to which the prohibited destination code belongs. This
parameter must be defined in the ADD LDNSET command before being referenced
here.
[Destination code]

17-6

It specifies the destination code to be prohibited, which can be a country code, area
code, office number, subscriber number, or special service number. The value
EEEEEEEE is a wildcard character, indicating all destination codes.
[Restriction percentage]
It specifies the percentage based on which the system restricts the calls, ranging from 1
to 100 in unit of %.
[Execution mode]
It specifies the mode in which the system implements the NM instruction configured in
this command. By default, it is Immediate.
[Active state]
It specifies whether the system activates the NM instruction configured in this
command. By default, it is Active. In application, the NMC can set the IN instruction
data according to the NM control plan in advance. Once NM control is needed, you can
activate the corresponding NM instructions at the NMC using ACT NM.
[Call type]
It defines the type of calls to be prohibited by the system. Set this parameter by the
z
To prohibit calls (including terminated calls or transferred calls) originated by

incoming trunks, select Incoming/transferred call.
To prohibit outgoing calls originated by local subscribers, select Outgoing call.
[Incoming trunk NM source code]

It specifies the incoming trunk group whose calls are to be prohibited by the system. It
is available only when Call type is set to Incoming/transferred call. Its value ranges
from 0 to 65534. By default, it is 65534, which is the wildcard character and indicates
all incoming trunk groups.
[Caller number]
It specifies the telephone numbers of the callers whose calls are to be prohibited by the
system. It is available only when Call type is set to Outgoing call. It can be a country
code, area code, office number, or subscriber number.
[Caller category]
It specifies the category of the callers whose calls are to be prohibited by the system. It
can be either the caller category sent by an incoming trunk through a signaling
message or the caller category of a local subscriber.
It defines the first time segment during which the system implements the NM instruction
configured in this command. It is available only when Execution mode is set to
Timing. It is in the format of HH:MM and ranges from 00:00 to 23:59.
17-7

It defines the second time segment during which the system implements the NM
instruction configured in this command. It is available only when Execution mode is
set to Timing. It is in the format of HH:MM and ranges from 00:00 to 23:59.
It defines the third time segment during which the system implements the NM
set to Timing. It is in the format of HH:MM and ranges from 00:00 to 23:59.
[Start date]
It defines the date when the system starts to implement the NM instruction configured in
this command. It is available only when Execution mode is set to "Timing. Its format is
YYYY&MM& DD. YYYY stands for year, MM for month, and DD for day.
[Total days]
It defines the total number of days during which the system implements the NM
set to "Timing. Its value ranges from 1 to 1024 in unit of days.
[Periodic mode]
It defines the periodic mode in which the system implements the NM instruction
configured in this command. It is available only when Execution mode is set to
"Timing. If you set it to Daily, the system implements the NM instruction during the
specified time segment every day.
[Cyclic mode]
It defines the interval between which the system implements the NM instruction
configured in this command. It is available only when Periodic mode is set to "Weekly
or Monthly. If Periodic mode is set to Weekly, this parameter ranges from 0 to 6. If
Periodic mode is set to Monthly, this parameter ranges from 1 to 31.
17.2.2 Adding Outgoing Destination Code Control

I. Related commands
Command
Function
ADD NMODEST
To add outgoing destination code control
MOD NMODEST
To modify outgoing destination code control
LST NMODEST
To list outgoing destination code control
RMV NM

17-8

Note:
Most of the parameters in ADD NMODEST are the same as those in ADD NMIDEST,
so this section only describes the dedicated parameters in ADD NMODEST. For the
other parameters, refer to section 17.2.1, Adding Originating Destination Code
Control.
[NM ID number]
It identifies an outgoing destination code control NM instruction uniquely in the
automatically.
[Local DN set]
here.
[Destination code]
[Outgoing trunk NM source code]
It specifies the outgoing trunk group occupied by the to-be-prohibited calls to the
designated destination code. Its value ranges from 0 to 65534. By default, it is 65534,
which is the wildcard character and indicates all outgoing trunk groups.
17.2.3 Adding Call Gap Control

I. Related commands
Command
Function
ADD NMGAP
To add call gap control
MOD NMGAP
To modify call gap control
LST NMGAP
To list call gap control
RMV NM

17-9

Note:
Most of the parameters in ADD NMGAP are the same as those in ADD NMIDEST, so
this section only describes the dedicated parameters in ADD NMGAP. For the other
parameters, refer to section 17.2.1, Adding Originating Destination Code Control.
[NM ID number]
It identifies a call gap control NM instruction uniquely in the SoftX3000, ranging from 0
to 65535. Generally, it is not set but allocated by the system automatically.
It specifies the module number of the FCCU/FCSU managing incoming trunk groups or
local subscribers whose calls are to be prohibited. Its value ranges from 22 to 101. It
must be defined in ADD BRD before being referenced here.
[Caller category]
[Local DN set]
here.
[Destination code]
[Interval in seconds], [Call attempts]
They define the interval for activating call gap control and the maximum call restriction
times. Interval in seconds ranges from 0 to 65534.
These two parameters must be used cooperatively. That is, if the call attempts of
designated callers to designated destination codes during the designated interval
exceed the number of call attempts defined here, the system automatically starts the
call gap control function to prohibit these callers from dialing the destination codes. The
call barring will not end until the system cancels it automatically or you cancel it with
DEA NM.
17-10

17.2.4 Adding Circuit Orient Control

I. Related commands
Command
Function
ADD NMCICD
To add circuit orient control
MOD NMCICD
To modify circuit orient control
LST NMCICD
To list circuit orient control
RMV NM
Note:
Most of the parameters in ADD NMCICD are the same as those in ADD NMIDEST, so
this section only describes the dedicated parameters in ADD NMCICD. For the other
[NM ID number]
It identifies a circuit orient control NM instruction uniquely in the SoftX3000, ranging
from 0 to 65535. Generally, it is not set but allocated by the system automatically.
It specifies the number of the bi-directional trunk group for which circuit orient control is
needed. This parameter must be defined in ADD N7TG, ADD N1TG, and ADD PRATG
After you set this NM instruction and activate it, the system changes some or all the
circuits of the bi-directional trunk group defined here to incoming trunk circuits.
[Control type]
It specifies whether the system implements circuit orient control by a certain
percentage or number of circuits.
It specifies the percentage of the bi-directional trunk circuits to be changed to incoming
trunk circuits. It is available only when Control type is set to Percent. Its value ranges
from 0 to 100 in unit of %.
[Circuit number]

17-11

It specifies the number of bi-directional trunk circuits to be changed to incoming trunk

circuits. It is available only when Control type is set to Circuit number. Its value
ranges from 1 to 65535.
17.2.5 Adding Circuit Reject Control

I. Related commands
Command
Function
ADD NMCICR
To add circuit reject control
MOD NMCICR
To modify circuit reject control
LST NMCICR
To list circuit reject control
RMV NM
Note:
Most of the parameters in ADD NMCICR are the same as those in ADD NMIDEST, so
this section only describes the dedicated parameters in ADD NMCICR. For the other
[NM ID number]
It identifies a circuit reject control NM instruction uniquely in the SoftX3000, ranging
It specifies the number of the trunk group for which circuit reject control is needed. This
parameter must be defined in ADD N7TG, ADD N1TG, and ADD PRATG before being
referenced here.
After you set this NM instruction and activate it, the system suspends some or all the
circuits of the trunk group defined here.
[Control type]
It specifies whether the system implements circuit reject control by a certain percentage
or number of circuits.

17-12

It specifies the percentage of the trunk circuits to be suspended by the system. It is

available only when Control type is set to Percent. Its value ranges from 0 to 100 in
unit of %.
[Circuit number]
It specifies the quantity of the trunk circuits to be suspended by the system. It is
available only when Control type is set to Circuit number. Its value ranges from 1 to
65535.
17.2.6 Adding Direct Route Control

I. Related commands
Command
Function
ADD NMDRT
To add direct route control
MOD NMDRT
To modify direct route control
LST NMDRT
To list direct route control
RMV NM
Note:
Most of the parameters in ADD NMDRT are the same as those in ADD NMIDEST, so
this section only describes the dedicated parameters in ADD NMDRT. For the other
[NM ID number]
It identifies a direct route control NM instruction uniquely in the SoftX3000, ranging
[Sub-route number]
It specifies the sub-route on which the direct traffic is to be restricted by the system. It
must be defined in ADD SRT before being referenced here.
It specifies the percentage based on which the system restricts the direct traffic on the
designated sub-route. Its value ranges from 1 to 100 in unit of %.
[Active state]
17-13

It specifies whether the system activates the NM instruction configured in this

command. By default, it is Active. In application, the NMC can set the IN instruction
data according to the NM control plan in advance. Once NM control is needed, you can
activate the corresponding NM instructions at the NMC using ACT NM.
[Control type]
It specifies the control mode in which the system restricts the direct traffic on the
designated sub-route. The options are
z
Incoming prohibited (DRT): The switch prohibits the direct traffic to the designated
sub-route by a certain percentage. The overflown traffic is routed to the other
sub-routes.
Overflow prohibited (DRF): The switch prohibits the direct traffic overflown from
the designated sub-route by a certain percentage. The overflown traffic is
canceled directly.
17.2.7 Adding Alternative Route Cancellation Control

I. Related commands
Command
Function
ADD NMCRT
To add alternative route cancellation control
MOD NMCRT
To modify alternative route cancellation control
LST NMCRT
To list alternative route cancellation control
RMV NM
Note:
Most of the parameters in ADD NMCRT are the same as those in ADD NMIDEST, so
this section only describes the dedicated parameters in ADD NMCRT. For the other
[NM ID number]
It identifies an alternative route cancellation control NM instruction uniquely in the
automatically.
[Sub-route number]
17-14

It specifies the sub-route on which the alternative traffic is to be restricted by the system.
It must be defined in ADD SRT before being referenced here.
[Control type]
It specifies the control mode in which the system restricts the alternative traffic on the
designated sub-route. The options are
z
Incoming prohibited (ART): The switch prohibits the alternative traffic to the
designated sub-route by a certain percentage. The overflown traffic is routed to
the other sub-routes.
Overflow prohibited (ARF): The switch prohibits the alternative traffic overflown
from the designated sub-route by a certain percentage. The overflown traffic is
canceled directly.
It specifies the percentage based on which the system restricts the alternative traffic on
the designated sub-route. Its value ranges from 1 to 100 in unit of %.
17.2.8 Adding Temporary Alternative Route Control

I. Related commands
Command
Function
ADD NMTMP
To add temporary alternative route control
MOD NMTMP
To modify temporary alternative route control
LST NMTMP
To list temporary alternative route control
RMV NM
Note:
Most of the parameters in ADD NMTMP are the same as those in ADD NMIDEST, so
this section only describes the dedicated parameters in ADD NMTMP. For the other
[NM ID number]
It identifies a temporary alternative route control NM instruction uniquely in the
automatically.

17-15

[Local DN set]
It specifies the local DN set to which the destination code using a temporary alternative
route belongs. This parameter must be defined in the ADD LDNSET command before
[Destination code]
It specifies the destination code for which a temporary alternative route is needed,
which can be a country code, area code, office number, subscriber number, or special
service number. The value EEEEEEEE is a wildcard character, indicating all
destination codes.
[Sub-route number]
It specifies the sub-route that can act as a temporary alternative route. It must be
defined in ADD SRT before being referenced here.
It specifies the percentage of the calls to the designated destination codes that can use
a temporary alternative route. Its value ranges from 1 to 100 in unit of %.
[Call type]
It defines the type of calls that can use a temporary alternative route. Set this parameter
by the following principles:
z
To allow the calls (including terminated calls or transferred calls) originated by

incoming trunks to use a temporary alternative route, select Incoming/transferred
call.
To allow the outgoing calls originated by local subscribers to use a temporary

alternative route, select Outgoing call.

It specifies the incoming trunk whose calls can use a temporary alternative route. It is
available only when Call type is set to Incoming/transferred call. Its value ranges
[Caller number]
It specifying the telephone numbers of the callers whose outgoing calls can use a
temporary alternative route. It is available only when Call type is set to Outgoing call.
It can be a country code, area code, office number, or subscriber number.
[Caller category]
It specifies the category of the callers whose outgoing calls can use a temporary
alternative route. It can be either the caller category sent by an incoming trunk through
a signaling message or the caller category of a local subscriber.
17-16

[Temporary route priority]

It defines the priority of a temporary sub-route to a common sub-route in route selection.
A temporary sub-route can be set in the beginning, middle, or end of a route table.
When it is set in the beginning of a route table, the temporary sub-route is actually a
temporary direct sub-route.
17.2.9 Adding Skip Sub-Route Control

I. Related commands
Command
Function
ADD NMSRT
To add skip sub-route control
MOD NMSRT
To modify skip sub-route control
LST NMSRT
To list skip sub-route control
RMV NM
Note:
Most of the parameters in ADD NMSRT are the same as those in ADD NMIDEST, so
this section only describes the dedicated parameters in ADD NMSRT. For the other
[NM ID number]
It identifies a skip sub-route control NM instruction uniquely in the SoftX3000, ranging
[Sub-route number]
It specifies the sub-route to be skipped during call routing. It must be defined in ADD
SRT before being referenced here.
[Service type]
It specifies the type of the routing service for which skip sub-route control is needed.
The options are alternative service, direct service, and direct and alternative service.
[Skip percentage]
It specifies the traffic percentage for skipping a specific sub-route. If this parameter is
set to 60%, 60% of the calls from designated callers or incoming trunks to designated
17-17

destination codes need to skip the designated sub-route, and 40% of the calls are
routed normally.
It specifies the incoming trunk whose calls can use a temporary alternative route. It is
available only when Call type is set to Incoming/transferred call. Its value ranges
[Caller number]
It specifies the telephone numbers of the callers whose outgoing calls can use a
temporary alternative route. It is available only when Call type is set to Outgoing call.
It can be a country code, area code, office number, or subscriber number.
[Caller category]
It specifies the category of the callers whose outgoing calls can use a temporary
alternative route. It can be either the caller category sent by an incoming trunk through
a signaling message or the caller category of a local subscriber.
17.2.10 Adding Special Record Notification Control

I. Related commands
Command
Function
ADD NMTONE
To add special record notification control
MOD NMTONE
To modify special record notification control
LST NMTONE
To list special record notification control
RMV NM
Note:
Most of the parameters in ADD NMTONE are the same as those in ADD NMIDEST, so
this section only describes the dedicated parameters in ADD NMTONE. For the other
[NM ID number]
It identifies a special record notification control NM instruction uniquely in the
automatically.

17-18

[Local DN set]
It specifies the local DN set of the destination code for which the special record
notification control is needed. This parameter must be defined in the ADD LDNSET
[Destination code]
It specifies the destination code for which the special record notification control is
needed, which can be a country code, area code, office number, subscriber number, or
special service number. The value EEEEEEEE is a wildcard character, indicating all
destination codes.
To modify the type of the record notification played to callers or operators, execute the
command ADD CFPRO.
[Call type]
It defines the type of calls for which the special record notification control is started. Set
z
To start the special record notification control to the calls (including terminated
calls
or
transferred
calls)
originated
by
incoming
trunks,
select
Incoming/transferred call.
z
To start the special record notification control to the outgoing calls originated by
local subscribers, select Outgoing call.

It specifies the incoming trunk group for whose calls the special record notification
control is started. It is available only when Call type is set to Incoming/transferred
call. Its value ranges from 0 to 65534. By default, it is 65534, which is the wildcard
character and indicates all incoming trunk groups.
[Caller number]
It specifies the telephone numbers of the callers for whose calls the system starts the
special record notification control. It is available only when Call type is set to
Outgoing call. It can be a country code, area code, office number, or subscriber
number.
[Caller category]
It specifies the category of the callers for whose calls the system starts the special
record notification control. It can be either the caller category sent by an incoming trunk
through a signaling message or the caller category of a local subscriber.

17-19

17.2.11 Adding Trunk Reserved Control

I. Related commands
Command
Function
ADD NMRES
To add trunk reserved control
MOD NMRES
To modify trunk reserved control
LST NMRES
To list trunk reserved control
RMV NM
Note:
Most of the parameters in ADD NMRES are the same as those in ADD NMIDEST, so
this section only describes the dedicated parameters in ADD NMRES. For the other
[NM ID number]
It identifies a trunk reserved control NM instruction uniquely in the SoftX3000, ranging
[Weak restriction percent], [Forced restriction percent]
They define the call restriction percentage when the system starts the trunk reserved
control in order to dynamically adjust outgoing traffic. This NM instruction needs the
cooperation of the parameters Idle circuits for weak call restriction and Idle circuits for
forced call restriction of trunk groups. The options are
z
No call restriction: If the actual number of idle circuits of the designated trunk
group = Idle circuits for weak call restriction, this NM instruction is invalid.
Weak call restriction: When Idle circuits for forced call restriction = the actual
number of idle circuits of the designated trunk group < Idle circuits for weak call
restriction, the system restricts the calls by Weak restriction percent.
Forced call restriction: If the actual number of idle circuits of the designated trunk
group < Idle circuits for forced call restriction, that is, the trunk group is to be
congested, the system restricts the calls by Forced restriction percent.
[Call type]

17-20

It defines the type of calls to be restricted by the NMS. Set this parameter by the
z


[Caller category]
[Service type]
It specifies the type of the routing service for which call restriction is to be implemented.
The options are alternative service, direct service, and direct and alternative service.
[Outgoing trunk NM source code]
It specifies the outgoing trunk group occupied by the to-be-prohibited calls to the
designated destination code. Its value ranges from 0 to 65534. By default, it is 65534,
which is the wildcard character and indicates all outgoing trunk groups.
[Control type]
It specifies the control mode used by the system to prohibit the calls to the designated
destination codes to occupy the outgoing trunk groups. The options are
z
Cancel: The system prohibits the alternative traffic overflown from the designated
sub-route by a certain percentage. The overflown traffic is cancelled directly.
Skip: The system restricts the alternative traffic to the designated sub-route by a
certain percentage. The overflown traffic is routed to the other sub-routes.
17.3 HTR Control Instructions

17.3.1 Adding HTR Description
I. Related commands
Command
Function
ADD HTRDESC
To add HTR description
RMV HTRDESC
To remove HTR description
MOD HTRDESC
To modify HTR description

17-21

Command
Function
LST HTRDESC
To list HTR description

HTR control means that the switch can automatically prohibit the calls from designated
callers or incoming trunks to designated destination codes by a certain percentage if
these destination codes are not reachable to some extent. When a destination code is
judged as reachable, the system cancels call restriction automatically.
When you add HTR control description, the system creates automatically a traffic
measurement task of HTR control for analyzing the measurement results reported by
all FCCUs/FCSUs every five minutes.
z
If the measurement results meet the conditions for starting HTR control
automatically, that is, Call attempts to prohibited destination codes is equal to
Call attempts in HTR description table and Percentage of answered attempts to
prohibited destination codes is less than Percentage of answered attempts in
HTR description tablePercentage of delayed attempts, the BAM sends to the
host the originating destination code control instruction automatically.
If the measurement results meet the conditions for stopping HTR control
automatically, that is, Call attempts to prohibited destination codes is less than
Call attempts in HTR description table and Percentage of answered attempts to
prohibited destination codes is bigger than or equal to Percentage of answered
attempts in HTR description tablePercentage of delayed attempts, the BAM
stops HTR control and deletes the originating destination code control instruction
automatically.
After setting HTR description, use LST NM to query whether HTR control is started. If
the originating destination code control instruction is set due to HTR generation, it
indicates that HTR control has been started.

[Local DN set]
It specifies the local DN set of the destination code for which HTR control is needed.
This parameter must be defined in the ADD LDNSET command before being
referenced here.
[Destination code]
It specifies the destination code for which HTR control is needed, which can be a
country code, area code, office number, subscriber number, or special service number.
The system analyzes the destination code according to maximum matching principle.
[Call attempts in 5 minutes]

17-22

As one of the conditions for starting HTR control, this parameter specifies the number
of call attempts within five minutes in the HTR description table.
After you set the HTR description, the system starts to count the number of call
attempts within the next five minutes. Five minutes later, the system judges whether
HTR control needs be started. For example, if you set HTR description at 12:22 in a
certain day, the system starts traffic measurement at 12:25. At 12:30, the system
judges whether HTR control needs be started according to the traffic measurement
result within the five minutes.
[Percentage of answered attempts]
As one of the conditions for starting HTR control, this parameter specifies the ratio of
answer attempts to call attempts in the HTR description table. Its value ranges from 1 to
100 in unit of %.
[Percentage of delayed attempts]
As one of the conditions for starting HTR control, this parameter specifies the delay
percentage of automatically starting or stopping HTR control in the HTR description
table. Its value ranges from 1 to 100 in unit of %.
[Percentage of restricted calls]
It specifies the percentage based on which the system restricts the calls, ranging from 1
to 100 in unit of %.
[Call type]
It defines the type of calls to be restricted by the NMS. Set this parameter by the
z

[Network management code of incoming relay]

[Calling number]
It specifies the telephone numbers of the callers whose calls are to be prohibited by the
system. It is available only when Call type is set to Outgoing call. It can be a country
code, area code, office number, or subscriber number.
[Caller type]

17-23

17.3.2 Setting HTR Switch

I. Related commands
Command
Function
SET HTRSW
To set HTR switch
LST HTRSW
To list HTR switch

When you add HTR description, the system automatically creates and starts a traffic
measurement task of HTR control by default. To suspend the traffic measurement task,
use SET HTRSW to set the HTR switch to OFF.

[HTR switch]
When HTR control is started, this parameter is used to control the system to start or
stop a traffic measurement task of HTR control. By default, it is On.
17.3.3 Removing HTR Control Table Content

I. Related commands
Command
Function
RMV HTRCTRL
To remove HTR control table content
LST HTRCTRL
To list HTR control table content

During HTR analysis, the system analyzes a destination code according to the
maximum matching principle. To remove a destination code in the HTR control table,
execute the command RMV HTRCTRL.

[Local DN set]
It specifies the local DN set of the destination code to be deleted. This parameter must
be defined in the ADD LDNSET command before being referenced here.
[Destination code]
It specifies the destination code to be deleted.

17-24

Chapter 18 Configuring Other Data

18.1.1 Dual-homing
Dual-homing is a disaster recovery mechanism preventing a softswitch from disaster or
paralysis by supplying emergency communication to outside. When starting the
dual-homing control mechanism in extremely abnormal cases, the system can recover
its communication capability by 80 to 90 percent.
I. Basic concepts
1)
Mutual assistance function: The system is configured with softswitches A and B.

When the softswitch B becomes faulty, the softswitch A can take over part or all of
services of the softswitch B. In this case, it is considered that the softswitch A has
the mutual assistance function.
2)
Mutual assistance active state: The softswitch A has the mutual assistance
function and takes over services of the softswitch B. In this case, it is considered
that the softswitch A operates in the mutual assistance active state.
3)
Mutual assistance inactive state: The softswitch A has the mutual assistance
function but does not take over services of the softswitch B. In this case, it is
considered that the softswitch A operates in the mutual assistance inactive state.
II. Dual-homing solution

Proposed in the U-SYS solution of Huawei, the dual-homing control mechanism of
SoftX3000 is composed of gateway control dual-homing mechanism and service
control dual-homing mechanism, as shown in Figure 18-1

18-1

Service
manageme nt layer
NMS
SCP
MRS
Heartbeat link
Primary signaling link
SoftX3000
(office A)
Se condary sig naling l ink
SoftX3000
(office B)
IP-ba sed
packet network
PSTN
TMG
IAD
AMG
UMG
Packet
ter mi na l
IAD
Access to offi ce A
AMG
UMG
Pa cket
ter mi nal
Access to offi ce B
Figure 18-1 Dual-homing solution

The dual-homing solution provided by Huawei has the following characteristics:
1)
Two SoftX3000s with mutual assistance function can be located in different

geographical areas. They are two independent exchange offices in terms of
networking. They operate in the mutual assistance relationship, not in the
active/standby mode. In other words, the other SoftX3000 will take the
responsibility of gateway control and service control functions of both offices only
when one SoftX3000 becomes faulty.
2)
Between the SoftX3000, a heartbeat link (through a private protocol) mutually

detects whether the opposite SoftX3000 is operating normally.
3)
Gateway control dual-homing mechanism: Each SoftX3000 is configured with

data of both primary (master) gateways and secondary (salve) gateways under its
control. Each gateway (including IAD, AMG, UMT, and TMG) or each
packet-based terminal (such as H.323 phone and OpenEye) is configured with
information of both a primary homed softswitch and a secondary homed softswitch.
In this way, when a softswitch becomes faulty or performs a dual-homing
switchover, the primary gateways under its control can automatically re-register to
or be forced to re-register to the secondary homed softswitch.
4)
Service control dual-homing mechanism: Universally plan office data and

subscriber data between two mutually assistant SoftX3000s, such as local DN set,
call source code, charging source code, subscriber number segment, route
number, route selection code, trunk group number, and call prefix. In this way,
either softswitch can take over some or all services of the other softswitch when
performing a dual-homing switchover without influencing subscriber attributes
such as call related attributes and charge related attributes.

18-2

5)
The same Network Management System (NMS) is networked to manage network

elements to keep consistency or coordination of office data and subscriber data
between the SoftX3000s.
6)
When the system adopts the dual-homing control mechanism, the number of
gateways or the number of subscribers under the control of a single softswitch is
not recommended to be greater than 50 percent of the maximum capacity of
SoftX3000.
III. Switch mode

A softswitch in the mutual assistance working mode transits its mutual assistance state
from the inactive state to the active state or from the active state to the inactive state,
which is called a switchover. The switchover happens manually or automatically.
1)
Manual switchover: A softswitch in the mutual assistance working mode transits its
mutual assistance state when a maintenance operator executes a switchover
command through the terminal system or the network management system.
2)
Automatic switchover: A softswitch in the mutual assistance working mode transits

its mutual assistance state, depending on its detection of the state of the heartbeat
link between the softswitch and its assistant softswitch.
IV. Heartbeat signal between softswitches and handshake signal between

softswitch and GW
Heatbeat signals exist between two assistant softswitches, used by a local softswitch to
check the state of the opposite softswitch. If the local softswitch receives no heartbeat
signals from the opposite within the specified period of time, the local softswitch
regards that the opposite softswitch is faulty. If the automatic switch mode is set at the
local softswitch, the local softswitch will change the assistance state from deactivated
to activated.
Handshake signals between a softswitch and a GW are used by the GW to judge the
state of the softswitch. If the GW receives no handshake signals from its homed
softswitch within the specified period of time, the GW regards that the homed softswitch
is faulty. At this time, the GW sends a registration request to the secondarily homed
softswtich.
Generally, the timer detecting the heartbeat signals at the softswitch side (one to five
minutes) should be shorter than that of sending handshake signals (five minutes). That
is, the local softswitch can process the registration requests sent by its secondarily
controlled GW only after it detects that the heartbeat signals sent by the opposite
softswtich time out. If the local softswitch receives a registration request from the
secondarily controlled GW before it detects that the heartbeat signals sent by the
opposite softswitch time out, it refuses the request.

18-3

18.1.2 PBX Service

Private Branch Exchange (PBX) is a kind of dedicated exchange for internal telephone
switching within enterprise, company, bank, community or school. SoftX3000 provides
PBX services for two purposes: one is to provide analog subscriber line to interworks
with PBX and the other is to support Call Center function of enterprise users.
I. Providing analog subscriber line

Figure 18-2 shows a typical networking model of SoftX3000 providing analog
subscriber line to interwork with PBX.
SoftX3000
IP core network
PSTN
TMG/UMG
IAD/AMG
Analog subscriber line
interface
Loop trunk cable
interface
PBX
Figure 18-2 Typical networking model for SoftX3000 providing analog subscriber line
to PBX
As shown in Figure 18-2, the PBX is required only to provide loop trunk cable to
connect with the analog subscribe line of Integrated Access Device (IAD)/Access
Media Gateway (AMG). From SoftX3000 side, each trunk cable from PBX is equivalent
to an ordinary subscriber line (that is, a subscriber).
To facilitate incoming calls from out-PBX subscribers, you need to assign a pilot
number at the SoftX3000 side for the PBX. The pilot number serves as the console
number of the PBX. When an out-PBX subscriber dials the pilot number, the call
processing software of the SoftX3000 shall select an idle subscriber line to play ringing
tone according to the preset PBX line hunting mode in the database. When the loop
trunk circuit of the PBX receives the ringing current, it shall start corresponding
connection actions, or provide second-stage dialing tone to the calling subscriber, or
connect the call to the PBX console.

18-4

II. Call Center function of enterprise user

The SoftX3000 supports multiple types of terminals, such as ESL terminal, V5 terminal,
SIP terminal, H.323 terminal and SoftPhone. According to specific demands, you can
add those terminals into a PBX subscriber group and assign the group with a pilot
number. When other subscribers dial this pilot number, the call processing software of
the SoftX3000 shall select an idle terminal according to the preset PBX line hunting
mode in the database, or provide queuing function when all terminals are busy, thus
implementing Call Center function.
The Call Center function is mainly applied to customer service hotline of enterprise
users, such as enterprise, company and bank, or to special service consoles for fire
alarm and burglar alarm. For example, there are 20 operators in the customer service
center of a company, and each operator has an individual phone number. If Call Center
function is enabled, the company can provide only one hotline number (91234 for
instance) externally, instead of all of the 20 phone numbers. When an out-PBX
subscriber calls 91234, the system will automatically select an idle console to get the
call through. If all operators are busy, the system will queue the call (playing
announcement or music to let the caller hold the call). Once an operator becomes idle,
the system will get through the earliest calling subscriber in the queue.
18.1.3 Videoconferencing Service

SoftX3000 supports point-to-point (P2P) multimedia service and multimedia
videoconferencing service. Actually, the P2P multimedia service, which does not
require special system networking, is the combination of ordinary call and video
communication. However, the videoconferencing service, adopting the architecture of
legacy H.323 videoconferencing system, requires not only that SoftX3000 can serve as
GateKeeper (GK), but also that Multipoint Control Unit (MCU), Service Management
Center (SMC) and OpenEye (iDo conference console) are configured in the network.
Figure 18-3 illustrates the typical networking.

18-5

RADIUS Server
SMC
MCU
Legacy H.323
videoconferencing network
SoftX3000(GK )
IP packet
switched network
iDo conference console
H.323
videophone
H.323
videophone
SIP
videophone
SIP
videophone
Figure 18-3 IP based videoconferencing system

The components shown in Figure 18-3 are described as follows:
z
Serving as GK, SoftX3000 implements address translation, call control, bandwidth

control, node management and Local Area Network (LAN) access control for the
endpoints, such as video terminal, MCU and SMC, of H.323 videoconferencing
system.
Multipoint Control Unit (MCU) is one of the core components of H.323

videoconferencing system, used to implement mixing and switching of audio,
video and data from video terminals. In actual networking, if the video conference
traffic is heavy, several MCUs can be configured.
Service Management Center (SMC) is the intelligent control center of H.323

videoconferencing system. It receives service requests from videoconferencing
subscribers and implements MCU resource dispatch, conference control
(including convening a conference), and centralized management to subscribers
and conference site.
RADIUS server implements charging for video conference.
OpenEye (iDo conference console) is a PC installed with Huawei iDo private

protocol. It provides conference convening function, including defining and
modifying conference and originating multipoint call to video terminals. Through
iDo and conference control extended function, you can also add or remove video
terminal and apply for or release chair authorities.
H.323 and SIP video terminals access the SoftX3000 through the standard H.323
and SIP. By dialing unique telephone numbers allocated in the NGN on H.323 and

18-6

SIP video terminals, you can achieve such multimedia services as voice,
point-to-point video, and data cooperation.
18.1.4 NP Service (Hong Kong)

I. Basic concept
Registered with the Number Portability (NP) service, service subscribers need not
change their original numbers (NP numbers) if they move or travel to other places.
Other subscribers can call NP service subscribers by dialing their original numbers.
However, service subscribers can select to display their NP numbers or new numbers
(actual telephone numbers) to the callees when they make outgoing calls.
The Hong Kong NP service is implemented by SoftX3000+NP server. The NP server
is used to store the mapping data between NP numbers and Network Numbers (NN).
The meanings of various numbers are as follows:
z
NP: portable number (original number), that is, the telephone number initially
applied by a service subscriber.
TN: telephone number (new number), that is, the actual number used by a service
subscriber currently.
NN: network number, that is, the network number defined by the carrier in the NP
server for a service subscriber.
Usually, NN is equivalent to TN, which can be directly used to control the SoftX3000 for
call connection. However, in the case of digit expansion and number segment change,
NN cannot be used to control the SoftX3000 for call connection if you do not re-define
the NNs in the NP server. To lessen the workload of modifying NNs in the NP server,
you can set the mapping between NNs and TNs in the SoftX3000 using ADD NN2TN.
II. Service analysis procedure

The NP service can be achieved because the SoftX3000 can quickly match NP
numbers with TNs when analyzing the NP numbers dialed by callers. The basic
analysis procedure is as follows:
1)
After the SoftX3000 determines that it is necessary to start the NP service analysis
procedure for an NP number dialed by a caller, it sends a number query command
to the NP server, requesting the NP server to return the corresponding NN.
2)
Upon receiving the number query request from the SoftX3000, the NP server
searches the corresponding NN in the local database. If the corresponding NN is
found, the NP server reports it to the SoftX3000.
3)
After receiving the NN, the SoftX3000 searches in the host database whether
there is a mapping record matching this NN. If so, the SoftX3000 changes the NN
according to the mapping relationship and regards the new number as the TN. If
not, the SoftX3000 regards this NN as the TN.

18-7

4)
The SoftX3000 re-analyzes the TN in the number analysis table for connecting the
call.
18.2 Configuring Dual-homing Data

18.2.1 Overview
In configuration of dual-homing data, it is vital to configure a pair of mutually assistant
SoftX3000s to keep consistent or coordinative in the aspect of assistant data. In other
words, the data of the primarily homed SoftX3000 must be consistent or coordinative
with that of the secondarily homed SoftX3000, such as gateway registration information,
signaling interworking information, trunk interworking information, route selection plan,
dialing plan, charging plan, number allocation plan, subscriber attributes, and so on. In
this way, one SoftX3000 can take over part or all of services of the other SoftX3000
when a dual-homing switch occurs.
Before the configuration of dual-homing data, therefore, telecom carriers must plan
routing arrangement, number allocation, dialing scheme, and charging scheme of both
mutually assistant softswitches according to the dual-homing solution. For examples,
refer to U-SYS SoftX3000 SoftSwitch System Operation Manual-Configuration
Example.
II. Data classification

To help you master the procedure of configuring dual-homing data, this manual
classifies the configuration data into three categories as shown in Table 18-1.

18-8

Table 18-1 Classification of configuration data

Category
Definition
It is required to add in the

database the related data
that is identified by a
master/slave type flag.
Category 1
Category 2
Category 3
Primary homing data

(master) is always valid.
Secondary homing data
(slave) is valid only when the
local office is operating in the
mutual assistance active
state.
Basically same data or

exactly same data between
the primary homed
SoftX3000 and the
secondary homed
SoftX3000.
Completely independent data

between the primary homed
SoftX3000 and the
secondary homed
SoftX3000.
Scope
Command
Local
signaling
point code
ADD OFI
Number segment
ADD
DNSEG
Media gateway data
ADD MGW
Multimedia
data
ADD MMTE
device
MCU data
ADD
MCUCNF
IP console data
ADD
CXCON
M2UA data
ADD M2LNK
M3UA data
ADD M3LNK
V5UA data
ADD
V5UALNK
IUA data
ADD
IUALNK
MTP data
ADD N7LNK
Local office data
Charging data
Routing data
Number
data
analysis
Call barring data
Centrex data
Service data
Equipment data
Protocol data
Subscriber
data,
signaling data, or
trunk data, without
using
the
dual-homing
service.
When you configure subscriber data, No. 7 trunk data, R2 trunk data, V5 trunk data, V5
interface data, PRA trunk data, and PRA link data, you have to specify the equipment
18-9

ID of the corresponding media gateway. The data of that media gateway, however, has
a master/slave type flag. Therefore, this part of data also belongs to the category 1
and you need not set the master/slave type parameter for it.

Configuration of dual-homing data involves the whole data configuration procedure of
the SoftX3000. This chapter only describes two basic configuration commands as
shown in Table 18-2.
Step
Description
Command
Set dual-homing work mode
SET DHWM
Add dual-homing heartbeat link
ADD DHHCFG
18.2.2 Setting Dual-homing Work Mode

I. Related commands
Command
Function
SET DHWM
To set dual-homing work mode
LST DHWM
To list dual-homing work mode
DSP DHSTA
To display dual-homing state

To start the dual-homing control mechanism between the local SoftX3000 and another
SoftX3000, you must set the dual-homing work mode of both SoftX3000s correctly
using the SET DHWM command. Otherwise, the dual-homing control mechanism of
the system cannot work normally.

[Work mode]
This parameter specifies the working mode of the local SoftX3000 in the network. By
default, it is Standalone. The meanings of the parameter options are as follows:
z
Standalone: The local SoftX3000 does not support the mutual assistance function.
Assistant: The local SoftX3000 supports the mutual assistance function.
[Switch mode]

18-10

When the work mode of the local SoftX3000 is set to Assistant, this parameter is
available to specify switch mode of the local SoftX3000. By default, it is Manual. The
z
Manual: When the local SoftX3000 is working in the assistant mode, the local
SoftX3000 transits its assistance state at and only at receiving a switchover
command (SET DHWM) from the terminal system or the network management
system.
Automatic: When the local SoftX3000 is working in the assistant mode, the local
SoftX3000 transits its assistance state depending on the detection of the state of
the heartbeat link to the assistant SoftX3000.
If you want to set the switch mode of the local SoftX3000 to Automatic, proceed as
follows:
1)
Execute the SET DHWM command to set the work mode of the local SoftX3000 to
Assistant and the switch mode to Manual.
2)
Execute the ADD DHHCFG command to add a dual-homing heartbeat link.
3)
Execute the SET DHWM command to set the work mode of the local SoftX3000 to
Assistant and the switch mode to Automatic.
[Manual assistant state or auto takeover mode]

When the switch mode of the local SoftX3000 is set to Automatic, this parameter
specifies the takeover mode of the local SoftX3000 when it is performing an automatic
switchover. By default, it is All. The meanings of the parameter options are as follows:
z
Deactivated -> activated: When performing an automatic switchover, the local

SoftX3000 transits its assistance state from the inactive state to the active state.
Activated -> deactivated: When performing an automatic switchover, the local

SoftX3000 transits its assistance state from the active state to the inactive state.
It is recommended to set the takeover mode to Deactivated -> activated to ensure

system reliability. In this way, the local SoftX3000 automatically takes over the service
control of the assistant SoftX3000 in the event of a failure and, when the system is
recovered, manual intervention is required to switch the assistance state of the local
SoftX3000 from the active state to the inactive state.
[Force State]
When the switch mode is set to Manual", this parameter is available to manually
specify the assistance state of the local SoftX3000. By default, it is Deactivated state.
The meanings of the parameter options are as follows:
z
Deactivated state: Force the local SoftX3000 to work in the assistance inactive
state.
Activated state: Force the local SoftX3000 to work in the assistance active state.
[Local Softswitch State]

18-11

When the force state is set to active, this parameter is available to manually control
the serving state of the local SoftX3000 in the network. By default, it is Active. The
z
Active: Force the local SoftX3000 to start the dual-homing control mechanism. In
this case, the local SoftX3000 takes over the service control of the assistant
SoftX3000.
Standby: Force the local SoftX3000 to exit from network services. In this case, all
IFMIs of the local SoftX3000 stop sending and receiving message packets.
[Handshake timeout(*10s)]
When the work mode parameter is set to Assistant, this parameter is available to
specify the maximum duration for the local SoftX3000 waiting for a handshake signal
after sending a heartbeat signal to the assistant SoftX3000.
The heartbeat signal is defined by ADD SIPTG. It is generally one to five minutes.
If the local SoftX3000 receives no handshake signal from the assistant SoftX3000
within the specified duration, the local SoftX3000 considers the assistant SoftX3000
faulty. Dual-homing switchover depends on the switch mode of the local SoftX3000.
The unit for this parameter is 10 seconds. The default value is 30 x 10, that is, 300
seconds.
18.2.3 Adding Dual-homing Heartbeat Configuration

I. Related commands
Command
Function
ADD DHHCFG
To add dual-homing heartbeat configuration
RMV DHHCFG
To remove dual-homing heartbeat configuration
MOD DHHCFG
To modify dual-homing heartbeat configuration
LST DHHCFG
To list dual-homing heartbeat configuration

If the automatic switch mode is adopted between the local SoftX3000 and the assistant
SoftX3000, you must add heartbeat links between them using the ADD DHHCFG
command. To ensure the reliability of heartbeat signals, you need to add two heartbeat
links between the mutually assistant SoftX3000s.


18-12

This parameter specifies the module number of the IFMI that provides FE port to send
heartbeat signals to the assistant SoftX3000. This parameter is defined in the ADD
To ensure the reliability of heartbeat signals, you must add two heartbeat links between
the mutually assistant SoftX3000s if the system is configured with two pairs of IFMIs or
more.
[Peer IP address]
This is one of the interconnection parameters between the local SoftX3000 and the
assistant SoftX3000. This parameter specifies the IP address at the assistant
SoftX3000 for receiving heartbeat signals.
[Local UDP port number]
assistant SoftX3000. This parameter specifies the UDP port number at the local
SoftX3000 for sending heartbeat signals. The value range is 0 to 65535. The default
value is 1000.
[Peer UDP port number]
assistant SoftX3000. This parameter specifies the UDP port number at the assistant
SoftX3000 for sending heartbeat signals. The value range is 0 to 65535. The default
value is 1000.
[Encryption method]
assistant SoftX3000. This parameter specifies whether to encrypt heartbeat signals
between the mutually assistant SoftX3000s, as well as the encryption mode. The
default setting is MD5, indicating that protocol messages are encrypted in the
Message Digest 5 (MD5) mode.
[Key]
assistant SoftX3000. This parameter specifies the key used in the MD5 algorithm for
encrypting heartbeat signals between the mutually assistant SoftX3000s.
18.3 Configuring PBX Service Data

18.3.1 Overview
If a PBX uses loop trunk cable to interwork with the SoftX3000, or an enterprise user
wants to enable Call Center function, you need to configure PBX service data at the
SoftX3000 side, including PBX pilot number, line hunting mode and queuing function.

18-13

To configure PBX service data, make sure that the local office data and MG data has
been configured.
During the configuration, some parameters defined in the local office data will be
referenced in the PBX service data. Besides, some parameters defined in the PBX
service data will be referenced when subscriber data and IP control data is configured.
Table 18-3 Parameter referencing relationships between PBX service data and other
data
Input parameter
Name
Local DN set
Output parameter
Defined in
Local office data
Name
Referenced in
Subscriber data, IP
console data
PBX pilot number
II. Preparations
Before configuring PBX service data, make sure that all preparations are done as
SN
Item
Remark
PBX pilot number
For planning access code of PBX or Call Center for

external incoming call
PBX
group
subscriber number
For planning subscriber number for interworking

with PBX, or subscriber number of Call Center

Table 18-5 lists the general steps for configuring PBX service data.
Step
1
Description
Add PBX group
Command
ADD PBX
ADD VSBR
Add PBX subscriber
ADD MSBR
ADD CXCON

18-14


the PBX service data is configured.
ADD PBX
[PBX indicating number]
[Local DnSet]
[Console flag]
ADD VSBR /
ADD MSBR /
ADD CXCON
[Subscriber number]
[Local DnSet]
[PBX indicating number]
18.3.2 Adding PBX Group

I. Related commands
Command
Function
ADD PBX
To add PBX group
RMV PBX
To remove PBX group
MOD PBX
To modify PBX group
LST PBX
To list PBX group

[PBX pilot number]
It specifies the access code of PBX or Call Center for incoming calls. When an out-PBX
subscriber dials the PBX pilot number, the call processing software of the SoftX3000
will select an idle line among the PBX subscriber group according to a specific line
hunting mode, or queue the call when no service is triggered or all PBX subscribers are
busy. A PBX pilot number is a number occupying number resource, and it must be
within the number segment defined in the ADD DNSEG command.
[Local DN set]
It specifies the local DN set to which the PBX pilot number belongs. This parameter
must be defined in the ADD LDNSET command before being referenced here.
18-15

[Queue flag]
It specifies whether the PBX subscriber group supports the queue function. If you set it
to Yes, the SoftX3000 will queue the calls from out-PBX subscribers when all
subscribers in the PBX subscriber group are busy. As soon as PBX subscribers are
available, the SoftX3000 will connect the calls based on the first in, first out principle.
The queue function can be achieved only when all subscribers in the PBX group are
controlled by the same FCCU/FCSU.
[Console flag]
It indicates whether the subscribers composing the PBX subscriber group must be IP
consoles. Set this parameter by the following principles:
z
If the option is No, it indicates that the subscribers composing the PBX
subscriber group can be of any category, including ESL, V5, SIP and H.323 (it is
recommended that the subscribers not be IP consoles). When an out-PBX
subscriber calls this PBX pilot number, the system will select idle line throughout
the PBX subscriber group according to the preset line hunting mode.
If the option is Yes, it indicates that the subscribers composing the PBX
subscriber group must be IP consoles. When an out-PBX subscriber calls the PBX
pilot number, the system will play ringing tone to all IP consoles at the same time.
In this case, the preset line hunting mode is invalid.
[Line hunting mode]

It specifies the mode the system selects PBX intra-group subscribers when an out-PBX
subscriber calls the PBX pilot number. Set this parameter by the following principles:
z
From small to large: In this mode, the system always selects the subscriber with
the minimum equipment ID. This mode can realize the preferred selection from
PBX subscribers.
From large to small: In this mode, the system always selects the subscriber with
the maximum equipment ID. This mode can realize the preferred selection from
PBX subscribers.
Cyclic: When a subscriber calls the PBX pilot number the first time, the system
selects the PBX subscriber from small to large according to their record numbers.
That is, you may configure the sequence of the PBX subscribers with the
command ADD/MOD VSBR. And for each PBX subscriber in the PBX group, the
system will rearrange to form a queue in sequence of release, which is followed
when the system selects the PBX subscriber later. That is, the PBX subscriber
released prior to others is preferred.
The default mode is From small to large, and you can select other mode according to
the actual conditions.
[Simultaneous ring]

18-16

It indicates whether the system provides the simultaneous ringing feature to the PBX
pilot number. When another subscriber dials the PBX pilot number, all idle phones in
the PBX will ring. By default, this feature is not provided.
[Virtual flag]
It specifies whether the system provides the simultaneous ringing feature through the
intelligent network, implementing the so-called intelligent simultaneous ringing
feature. This parameter is valid only when the Simultaneous ring is set to Yes. If you
set the parameter to Yes, you have to use ADD VPSBR to add PBX virtual
subscribers.
[PBX hunt mode]
It is reserved.
18.3.3 Adding PBX Subscriber

I. Related commands
Command
Function
ADD VSBR
To add a voice subscriber
ADD MSBR
To add a multimedia subscriber
ADD CXCON
To add Centrex console

In the actual applications, PBX subscriber can be voice subscriber, multimedia
subscriber or IP console. For different networking and application demands, you need
to use different configuration commands to add PBX subscriber.
1)
When PBX is connected to the SoftX3000 through loop trunk cable, that is, when
the SoftX3000 provides analog subscriber line to interwork with PBX, the PBX
subscribers can only be voice subscribers. In this case, to add PBX subscriber,
you must use the ADD VSBR command.
2)
When PBX subscriber group is used for the Call Center function of enterprise
users, the PBX subscribers can be of any category. In this case, to add PBX
subscribe, you need to use ADD VSBR, ADD MSBR or ADD CXCON according
to the actual networking demand.

18-17

Note:
This section only describes the parameters in the commands ADD VSBR, ADD MSBR
and ADD CXCON that are closely related to PBX subscriber. For detailed information
about other parameters, see Chapter 12, Configuring Subscriber Data, and Chapter
13, Configuring Centrex Data, in this manual.
[Subscriber number]
It specifies the phone number assigned to the subscriber. The specified number must in
the number segment defined in the ADD DNSEG command. This parameter must be
specified for the subscribers except those PBX subscribers not occupying number
resources.
[Local DN set]
called numbers dialed by the subscriber. This parameter must have been defined in the
ADD LDNSET command before being referenced here.
[Additional status]
It indicates whether the subscriber is a PBX subscriber. By default, it is Ordinary. The
options are
z
Ordinary: The subscriber is not a PBX subscriber.
PBX non-pilot number occupying number: The subscriber is a PBX subscriber.

You need to enter the subscribers phone number in the Subscriber number field.
PBX non-pilot number: The subscriber is a PBX subscriber. You need not specify
the subscribers phone number in the Subscriber number field. The PBX
subscribers occupying no number resource cannot be Centrex subscribers at the
same time.
[PBX pilot number]

It defines the pilot number of a PBX subscriber group to which the PBX subscriber
belongs. This parameter must be defined in the ADD PBX command before being
referenced here.
18.3.4 Adding PBX Virtual Subscribers

I. Related commands
Command
Function
ADD VPSBR
To add PBX virtual subscribers
DSP PBX
To display PBX status

18-18


Here is the basic service procedure when the SoftX3000, working as SSP, provides
intelligent simultaneous ringing in coordination with the SCP:
1)
The SCP all the communication numbers of a subscriber using his virtual personal
number (VPN).
2)
When another subscriber dials the VPN, the SCP sends multiple connected
number to the SoftX3000 in the extension parameters of an INAP
messageConnect.
3)
After the SoftX3000 receives the INAP message, its call processing software will
initiate a call, with the PBX virtual subscriber as the caller, and all the connected
number as the callee.
4)
When the call is initiated, all idle phones will ring simultaneously. When one of the
phones is picked up, all the others stop ringing, and the relevant resources are
released. The caller and called starts conversation.
The SoftX3000 implements the intelligent simultaneous ringing feature through PBX
virtual subscribers. You have to use ADD VPSBR to add a PBX virtual subscriber.
However, the number displayed on the callees phone is still the caller's not the PBX
virtual subscribers.

[Local DN set]
It specifies the local DN set to which the PBX virtual subscriber belongs. It specifies the
number analysis table in which all calls initiated by the PBX virtual subscriber shall be
analyzed by the call processing software. This parameter must first be defined by ADD
LDNSET before it can be used here.
The PBX virtual subscriber is a public resource, which is used to simulate as a caller to
initiate a call. Therefore, you can only configure one PBX virtual subscriber for each
local DN set.
It specifies the module number of the FCCU/FCSU board which processes the calls of
the PBX virtual subscribers. It ranges from 22 to 101. This parameter must first be
defined by ADD BRD before it can be used here.
[Start equipment number] [End equipment number]
The two parameters specify the range of the equipment number allocated to the PBX
virtual subscriber. It ranges from 0 to 59999. Here are the configuration principles of the
parameters:
z
The equipment numbers used by the PBX virtual subscriber cannot be the ones
already in use by other voice subscribers in the same FCCU/FCSU board. Before
configuration, you can use LST USER to list the range of allocated equipment
numbers.
18-19

z
A PBX virtual subscriber can occupy a range of 6000 equipment numbers at

maximum. This range specifies the percentage of resources that the subscriber
occupies in the FCCU/FCSU board. For instance, a FCCU/FCSU board can
process 60000 calls, the subscriber occupies a range of 6000 equipment numbers
and 10% of call processing resources in the FCCU/FCSU board.

It is a charging attribute of the subscriber. The parameter must be first defined by ADD
CHGGRP or ADD CHGIDX before it can be used here.
The parameter is used here by the call processing software for authentication. The
system does not generate bills for calls initiated by the PBX virtual subscriber
[Call source code]
It specifies the call source to which the PBX virtual subscriber belongs. The parameter
must first defined by ADD CALLSRC before it can be used here.
[PBX pilot number]
It defines the pilot number of the PBX to which the PBX virtual subscriber belongs . The
parameter must first be defined by ADD PBX before it can be used here.
18.4 Configuring Videoconferencing Service Data

18.4.1 Overview
Videoconferencing service data is used to configure SoftX3000 data for interworking
with MCU, iDo conference console and SMC in the legacy H.323 videoconferencing
network. The data includes MCU IP address, iDo port number, and SMC IP address. To
configure videoconferencing service data, make sure that the equipment data, local
office data, and H.323 data has been configured.
During the configuration, some parameters defined in the equipment data and local
office data will be referenced in the videoconferencing service data. Table 18-6 shows
the details.
Table 18-6 Parameter referencing relationships between videoconferencing service
data and other data
Input parameter
Name
Module
number
FCCU/FCSU
Output parameter
Defined in
of
Name
referenced in
Equipment data
Module number of MSGI
Equipment data
Call source code
Local office data

18-20

II. Preparations
Before configuring the videoconferencing service data, make sure that all preparations
are done as specified in Table 18-7.
SN
Item
Remark
IP address of MCU signaling

port
For interworking with the MCU
Originating call listen port
For interworking with the iDo conference

console
iDo port number
For interworking with the iDo conference

console
SMC IP address
For interworking with the SMC
SMC port number
Special service code of

videoconferencing service

Table 18-8 lists the general steps for configuring videoconferencing service data.
Step
Description
Command
Add MCU configuration
ADD MCUCNF
Add iDo and SMC
ADD IDOSMC
ADD CNACLD

mutually.
18.4.2 Adding MCU Configuration

I. Related commands
Command
Function
ADD MCUCNF
To add MCU configuration
RMV MCUCNF
To remove MCU configuration

18-21

Command
Function
MOD MCUCNF
To modify MCU configuration
LST MCUCNF
To list MCU configuration

If it is required to enable videoconferencing service in the local office, the SoftX3000 will
serve as a GK. Before using the ADD MCUCNF command to add configuration
information of MCU, you must configure H.323 protocol data. Otherwise, the MCU
cannot interwork with the SoftX3000.

[MCU Index]
It uniquely identifies an MCU in the SoftX3000. Its value ranges from 0 to 31, indicating
that the SoftX3000 can be connected to 32 MCUs.
[Equipment ID]
It uniquely identifies a multimedia device (control device) within the SoftX3000. The ID
cannot be repeated with the IDs of other media gateways or of multimedia devices. It is
recommended to define it the same as the alias at the MCU side.
It specifies the module number of the FCCU or FCSU processing the call messages
sent by the MCU. Its value ranges from 22 to 101. This parameter must be defined in
the ADD BRD command before being referenced here.
[MCU IP address]
It is one of the interconnection parameters between the SoftX3000 and the MCU, used
to specify the IP address of the MCU signaling port instead of that of the media port.
This parameter must be correctly configured; otherwise, the MCU cannot register with
the SoftX3000 successfully.
[Call source code]
It specifies the call attributes of the MCU as calling subscriber. This parameter must be
defined in the ADD CALLSRC command before being referenced here. In
videoconferencing service, MCU needs to send call message to the SoftX3000 to
request the SoftX3000 to connect the called subscriber to the conference. In this case,
MCU is a calling subscriber for the SoftX3000.
[Master/Slave type]
follows:

18-22

the local office. When you want to configure dual-homing data for the assistant office,
18.4.3 Adding iDo and SMC

I. Related commands
Command
Function
ADD IDOSMC
To add iDo and SMC
RMV IDOSMC
To remove iDo and SMC
MOD IDOSMC
To modify iDo and SMC
LST IDOSMC
To list iDo and SMC

If it is required to enable videoconferencing service in the local office, the SoftX3000 will
serve as a GK. Before using the ADD IDOSMC command to add configuration
information of iDo and SMC, you must configure H.323 protocol data. When you are
using the ADD H323APP command to add configuration information of H.323 protocol
application layer, you must configure the RAS protocol dispatch abilities for an MSGI. In
other words, you must set the MSG module type to either RAS application or RAS &
CALL application. Otherwise, videoconferencing service will not operate normally.

It specifies the module number of the MSGI processing RAS messages. Before this
parameter is referenced here, it must be defined in the ADD BRD command and the
RAS dispatch capability must be configured by the ADD H323APP command.
[Originating call listen port]
This is one of the parameters for the SoftX3000 to interconnect with the iDo conference
console. It sets the TCP port through which the SoftX3000 monitors and receives call
messages originated by an iDo terminal. Its value ranges from 1 to 65535, and the
[iDo port]
As one of the parameters used for interworking with iDo conference console (that is,
iDo terminal), it sets the number of the UDP port used by iDo protocol. Its value must be
18-23

consistent with that at iDo terminal side. Through this port, iDo terminal sends UDP
request message to request for the IP address of MCU to the SoftX3000, and the
SoftX3000 sends UDP response message to tell the IP address of MCU to iDo terminal,
so that iDo terminal can control the conference through the MCU. Its value ranges from
1 to 65535, and the default value is 10000.
[SMC IP address]
One of the parameters used for interworking with SMC. It specifies the IP address of
the SMC.
[SMC port]
One of the parameters used for interworking with SMC. It specifies the TCP port
through which the SMC listens to and receives the call message (originated by iDo
terminal) forwarded by the SoftX3000. Its value ranges from 1 to 65535, and the default
value is 7000.
[TCP port connected to SMC]
It specifies the TCP port used by the SoftX3000 to establish communication
connections with the SMC. The port number can be only specified at the SoftX3000
side and the value range is 1 to 65535. However, you cannot set it to well-known port
numbers of protocols and allocated port numbers in the database. For example, you
can set it to 65500.
[Special service code]
It is one of the parameters used by the SoftX3000 to interwork with the SMC. It
specifies the special service code that the H.323 terminal needs to dial to participate in
a conference. The default code is 168 and you can assign other code according to the
actual condition. It must be consistent with that at the SMC side.
A video terminal can send a request to the MCU to participate in a conference after the
conference is started. However, the video terminal may not know to which MCU it
needs to send the request. In this case, the caller can dial the special service code to
query the IP address of the MCU through the SoftX3000, and then the video terminal
sends the request directly to the MCU.

I. Adding outgoing call prefix
If a local multimedia subscriber is absent when a video conference is convened, the
local multimedia subscriber can dial a special service call prefix, for example, 168, to
apply to attend the conference through the SMC. To achieve this, you can use the ADD
CNACLD command to add an outgoing call prefix for the videoconferencing service.
Pay attention to the following:
1)
The service category parameter is set to basic service.
2)
The service attribute parameter is set to MCU.

18-24

3)
The minimum number length and maximum number length parameters are set
to the length of the access code to the videoconferencing service, for example, 3
digits. The access code is defined in the ADD IDOSMC command.
4)
The charging selection code parameter is used for charging usage.
II. Adding incoming call prefix

When a video conference is convened through the SMC, if a multimedia subscriber
belongs to the local office, the SMC sends to the SoftX3000 the called number of the
multimedia subscriber through signaling. The number is sent in the form of a national
significant number, that is, national toll area code + subscriber number. Consequently,
the SoftX3000 has to conduct a number initial processing (sometimes called prefix
processing) on the national toll area code of the local office during the analysis of the
called number.
Supposing the national toll area code of the local office is 0755 and there is a
subscriber segment 878XXXX, the related configuration script is as follows:
ADD CNACLD: PFX=K'878, MINL=7, MAXL=7, CHSC=65535;
ADD CNACLD: PFX=K'0755, MINL=4, MAXL=4, CHSC=65535;
ADD DNC: DCX=10, DCT=DEL, DCL=4;
ADD PFXPRO: CSC=0, PFX="0755", CCF=YES, DDCX=10, ISREANA=YES;
For more information, refer to Chapter 11, Configuring Number Analysis Data.
18.5 Configuring NP Service Data (Hong Kong)

18.5.1 Overview
The NP service (Hong Kong) data includes the IP address of the NP server,
communication links, and mapping between NNs and TNs. You can set NP service data
only after setting hardware data.
During the configuration, some hardware parameters as listed in Table 18-9 will be
referenced in the NP service data.
Table 18-9 Parameter referencing relationships between NP service data and other
data
Input parameter
Output parameter
Name
Defined in
FCCU/FCSU module number
Hardware data

18-25
Name
/
Defined in
/

II. Preparations
Before configuring NP service data, make sure that all preparations are done as
SN
Item
Remark
IP address of NP
server
It is one of the parameters for the SoftX3000 to

interconnect with the NP server.
Mapping between
NNs and TNs
In the case of digit expansion and number segment

change, if you do not re-define the NNs in the NP
server, you must set the mapping between NNs and
TNs in the SoftX3000.

Table 18-11lists the general steps for configuring NP service data.
Step
Description
Command
Add NP server
ADD NP
Add connection to NP server
ADD NPCON
Add mapping between network number and

telephone number (Optional)
ADD NN2TN

the NP service data is configured.

18-26

ADD NP
[NP server index]
[NP server name]
[Link 1 IP address]
ADD NPCON
[Index of first NP server]
[Index of second NP server]
18.5.2 Adding NP Server

I. Related commands
Command
Function
ADD NP
To add NP server
RMV NP
To remove NP server
MOD NP
To modify NP server
LST NP
To list NP server

[NP server index]
It identifies an NP server uniquely in the SoftX3000. Its value ranges from 0 to 9,
indicating that the SoftX3000 can interconnect with a maximum of 10 NP servers.
[NP server name]
It describes an NP server with a string of characters.
[Link 1 IP address]
It is one of the parameters for the SoftX3000 to interconnect with the NP server,
specifying the IP address of network adapter 1 of the NP server. In actual networking,
the NP server must interconnect with the SoftX3000 through the internal Ethernet
communication system of the SoftX3000, so the IP address defined here must be within
172.20.XXX.XXX and cannot be the same as the internal IP address of any board.

18-27

When the NP server functions are implemented by the NP server software installed on
the BAM, you can set this parameter to 172.20.200.0 only.
[Link 2 IP address]
It is one of the parameters for the SoftX3000 to interconnect with the NP server,
specifying the IP address of network adapter 2 of the NP server. In actual networking,
the NP server must interconnect with the SoftX3000 through the internal Ethernet
communication system of the SoftX3000, so the IP address defined here must be within
172.30.XXX.XXX and cannot be the same as the internal IP address of any board.
When the NP server functions are implemented by the NP server software installed on
the BAM, you can set this parameter to 172.30.200.0 only.
18.5.3 Adding Connection to NP Server

I. Related commands
Command
Function
ADD NPCON
To add connection to NP server
RMV NPCON
To remove connection to NP server
MOD NPCON
To modify connection to NP server
LST NPCON
To list connection to NP server

It specifies the module number of the FCCU or FCSU for which the links to the NP
server are to be added. Its value ranges from 22 to 101. This parameter must be
defined in the ADD BRD command before being referenced here.
The subscribers managed by an FCCU/FCSU can call NP service subscribers only
after you have added links between this FCCU/FCSU and the NP server. In actual
deployment, you should add links to the NP server for all the FCCUs/FCSUs in the local
office.
[Index of first NP server]
It defines the NP server to which the active links are established with the FCCU/FCSU.
It is mandatory and must be defined in ADD NP before being referenced here.
[Index of second NP server]
It defines the NP server to which the standby links are established with the
FCCU/FCSU. It must be defined in ADD NP before being referenced here.

18-28

18.5.4 Adding Mapping between Network Number and Telephone Number

(Optional)
I. Related commands
Command
Function
ADD NN2TN
To add mapping between network number and telephone

number
RMV NN2TN
To remove mapping between network number and telephone

number
MOD NN2TN
To modify mapping between network number and telephone

number
LST NN2TN
To list mapping between network number and telephone number

data configuration.
The NP server stores the mapping data between NP numbers and NNs. When the
SoftX3000 sends a number query request to the NP server, the NP server reports the
NN corresponding to a specified NP number to the SoftX3000.
Usually, NN is equivalent to TN, which can be directly used to control the SoftX3000 for
call connection. However, in the case of digit expansion and number segment change,
NN cannot be used to control the SoftX3000 for call connection if you do not re-define
the NNs in the NP server. To lessen the workload of modifying NNs in the NP server,
you can set the mapping between NNs and TNs in the SoftX3000 using ADD NN2TN.

[Network number]
It specifies the NN to be converted to TN. It is the NN returned by the NP server to the
SoftX3000 in response of the number query request. Usually, set it to a prefix (an
incomplete-length number).
[Telephone number]
It specifies the TN converted from an NN. It is the real TN used by an NP subscriber
currently. Usually, set it to a prefix (an incomplete-length number).

18-29

18.6 Configuring RACF Card Number

18.6.1 Overview
I. Congiuration description
RACF card numbers are offered by the SoftX3000 in IN mode through the embedded
SCP function. Therefore, RACF card number data is composed of two parts actually:
data at the SSP side for defining DP number, service key, physical addresses of SCP
and SSP, and data at the embedded SCP side for defining information related to the
CSP service and RACF card numbers.

Table 18-12 lists the general steps for configuring RACF card number data.
Step
Description
Command
Add IN call prefix
ADD CNACLD
Add access code
ADD ACCODE
Add TDP configuration
ADD TDPCFG
Add SCP physical address description
ADD SCPADDR
Add SSP physical address description
ADD SSPADDR
Add SCP configuration
ADD SCPCFG
Add CSP service configuration
ADD CSPSRVC
Add CSP service logic file
ADD CSPSRVF
Activate CSP service logic file
ACT CSPSRVF
10
Add CSP service module configuration
ADD CSPSRVM
11
Add RACF number segment
ADD RACFSEG
12
Add RACF number
ADD RACF
18.6.2 Configuring DP, SCP, and SSP Data

DP, SCP, and SSP data are used to set INAP information when the SoftX3000
interconnects with the embedded SCP, including DP number, service key, SCP physical
address, and SSP physical address. Refer to Chapter 15, Configuring IN Service
Data for details.

18-30

18.6.3 Add CSP Service Configuration

I. Related commands
Command
Function
ADD CSPSRVC
To add CSP service configuration
RMV CSPSRVC
To remove CSP service configuration
MOD CSPSRVC
To modify CSP service configuration
LST CSPSRVC
To list CSP service configuration

[Service key]
As one of the parameters for interconnection between the embedded SCP and the SSP,
it is used to specify the service key for the CSP service. This parameter must be set to
the same value as that defined for the service key of the CSP service in the ADD
TDPCFG command. Otherwise, the CSP service cannot be used normally.
[Access code]
it is used to specify the access code for the CSP service. This parameter must be set to
the same value as that defined for the access code of the CSP service in the ADD
TDPCFG command. Otherwise, the CSP service cannot be used normally.
[Service type]
This parameter specifies the type of the CSP service triggered by the preceding service
key. The meanings of the available options are as follows:
z
IPN calling service: The service key will trigger an IPN service according to the
IPN calling service procedure. If the charging type for that service is prepaid, the
card number database used by that service is located in SoftX3000.
IPN called service: The service key will trigger an IPN service according to the IPN
called service procedure. If the charging type for that service is prepaid, the card
number database used by that service is located in SoftX3000.
RADIUS card service: The service key will trigger a card service according to the
Remote Authentication Dial In User Service (RADIUS) card service procedure. If
the charging typeory for that service is pre-payment, the card number database
used by that service is located in an independent RADIUS server.
RACF service: The service key will trigger a card service. Generally, select
Period for the charging type of the service.
Super Do-Not-Disturb service: The service key will trigger a super do-not-disturb
service.
[Black statistics flag]

18-31

This parameter specifies whether or not to blacklist a card number when a user types
incorrect card passwords several times consecutively. By default, it is Yes.
Once a card number is blacklisted, it cannot be used any more. The card owner must
apply to cancel the blacklisted status before the card number is used again.
[Max black times]
When the black statistics flag parameter is set to Yes, this parameter is available to
specify the maximum number of consecutive attempts for a user to type incorrect card
passwords in a single call, not accumulated attempts in more than one call. The value
range is 1 to 255. The default value is 5 and indicates that a user is allowed to type
incorrect passwords at most five times consecutively in a single call. When the user
types incorrect passwords more than five times, the card number is blacklisted.
[Service serial no]
it is used to specify the "service key carried in a recorded announcement message ID
that is sent from the embedded SCP to the SSP through an INAP message. This
service key is used to instruct the SSP to correctly operate the recorded
announcements on the MRS. The meaning of this service key is different from what
we say usually. This service key is an 8-bit hexadecimal number. For the CSP
services, this parameter is set to FC.
For information about the relationship between service keys and voice files, refer to
Chapter 15, Configuring IN Service Data.
[First digit timeout]
In the card service, the system commonly prompts a user to type a string of digits, such
as card number, password, and called number. This parameter specifies the valid time
for the user to type the first digit after the related announcement is played. The value
range is 1 to 255. The unit is second.
The default value is 10 and indicates that the user has to type the first digit within 10
seconds after the related announcement is played. If no digit is typed within 10 seconds,
the embedded SCP will perform different processing according to the actual situations.
z
The default digit is brought into service to continue the service procedure. For
example, the system prompts a user to select an expected language, but no digit
is typed within 10 seconds. Subsequently, the SCP uses the default language, for
example, English, to continue the service procedure.
The related announcement is played again to prompt a user to type digits until the
call is released due to timeout. For example, the system prompts the user to type a
card number, but no digit is typed within 10 seconds. Subsequently, the system
repeats that related announcement to prompt the user to type a card number.
Usually, the SCP will release the call if the announcement is played three times to
prompt the user to type a card number but no digit is typed yet.
[Inter digit timeout]

18-32

This parameter specifies the maximum time interval between typed digits in the card
service. The value range is 1 to 255. The unit is second. The default value is 10 and
indicates that a digit, if any, must be typed within 10 seconds after the previous digit is
typed. Otherwise, the system will automatically terminate the current input.
[No answer time]
Only when the service type is IPN called service, this parameter is available to specify
the maximum monitoring time for the system to attempt to connect the several
destination numbers during a sequence-based selection. The value range is 1 to 255.
The unit is second. The default value is 20 and indicates that the system sends the
ringing tone to a destination number and waits for a maximum of 20 seconds for an
answer from the destination number. When the IPN number is called, the system sends
the ringing tone to the first destination number, waiting for an answer. If no answer is
received from the first destination number within 20 seconds, the system changes to
send the ringing tone to the second destination number, waiting for an answer. If no
answer is received from the second destination number within 20 seconds yet, the
system turns to a third destination number, waiting for an answer for a maximum of 20
seconds. The remaining destination numbers are operated in the same way.
[Charging type]
This parameter specifies how to charge the preceding CSP service. The meanings of
the available options are as follows:
z
Prepaid: The CSP service is charged based on card number.
Period: The charge of the CSP service is paid regularly.
18.6.4 Adding CSP Service Logic File

I. Related commands
Command
Function
ADD CSPSRVF
To add CSP service logic file
RMV CSPSRVF
To remove CSP service logic file
LST CSPSRVF
To list CSP service logic file

[Service name]
This parameter specifies the name of the CSP service that is to be loaded to the
SoftX3000. This name must be the same as the service name defined in the CSP
service logic file. Otherwise, the loading check will fail and the CSP service cannot be
used normally. For example, for the RACF service, type RACF.
[Service file name]

18-33

This parameter specifies the name of the CSP service logic file that is to be loaded to
the SoftX3000. The file is provided by Huawei and stored in D:\data on the hard disk of
the BAM. For example, for the RACF service, type racf.bin.
18.6.5 Activating CSP Service Logic File

I. Related commands
Command
Function
ACT CSPSRVF
To activate CSP service logic file (for all FCCUs/FCSUs)
DEA CSPSRVF
To deactivate CSP service logic file (for all FCCUs/FCSUs)
ULD CSPSRVF
To load CSP service logic file (for an FCCU/FCSU)
UPD CSPSRVF
To update CSP service logic file (for an FCCU/FCSU)
DSP CSPSRVF
To display the state of CSP service logic file

This parameter specifies the module number of the FCCU/FCSU whose CSP service
logic file is to be activated. Before activating the CSP service logic files, use the DSP
CSPSRVF command to check which files are deactivated.
[Service name]
This parameter specifies the name of the CSP service to be activated. This parameter
is defined in the ADD CSPSRVF command and referenced here.
18.6.6 Adding CSP Service Module Configuration

I. Related commands
Command
Function
ADD CSPSRVM
To add CSP service module configuration
RMV CSPSRVM
To remove CSP service module configuration
MOD CSPSRVM
To modify CSP service module configuration
LST CSPSRVM
To list CSP service module configuration

[Service key]

18-34

This parameter specifies the service key of the CSP service. It must be the same as the
Service key of the CSP service defined in ADD CSPSRVC; otherwise, the CSP
service cannot be used.
[Module1] to [Module5]
These parameters specify the FCCU/FCSU or CDBI that processes the designated
CSP service. It must be defined in ADD BRD before being referenced here. Module 1
is mandatory, and the others are optional.
[Load balance mode]
When the CSP service with the specified service key is processed by several modules,
this parameter indicates how the system selects the modules. The meaning of the
options is as follows:
z
Lowest CPU usage: For an CSP call, the system selects the module with the
lowest CPU usage to process the call.
Polling: For an CSP call, the system selects the module in turn by module number
to process the call.
18.6.7 Adding RACF Number Segment

I. Related commands
Command
Function
ADD RACFSEG
To add RACF number segment
RMV RACFSEG
To remove RACF number segment
LST RACFSEG
To list RACF number segment

When using the RACF service, a user can set the forwarded-to numbers in two ways:
by dialing the prefix *571* on any phone set of the local office; or by dialing the access
code on any phone set in the network, and then setting forwarded-to numbers in IN
card service mode. If the latter method is used, you must use ADD RACFSEG and
ADD RACF to set related card number segment, card number, and password.

[Start RACF number], [End RACF number]
These parameters specify the range of the RACF number segment. The system
supports a maximum of 10000 RACF numbers.
[Start number index]
This parameter specifies the index of the start RACF number in the RACF data index
table. The indexes of the other RACF numbers in the same segment are incremented
18-35

one by one. It is not set generally. The system sets it automatically after calculating
such parameters as configuration sequence and related number segment in ADD
RACFSEG.
18.6.8 Adding RACF Number

I. Related commands
Command
Function
ADD RACF
To add RACF number
RMV RACF
To remove RACF number
MOD RACF
To modify RACF number
LST RACF
To list RACF number
ADB RACF
To add a batch of RACF numbers
RVB RACF
To remove a batch of RACF numbers

When using the RACF service, a user can set the forwarded-to numbers in two ways:
by dialing the prefix *571* on any phone set of the local office; or by dialing the access
code on any phone set in the network, and then setting forwarded-to numbers in IN
card service mode. If the latter method is used, you must use ADD RACFSEG and
ADD RACF to set related card number segment, card number, and password.

[RACF number]
This parameter specifies an RACF number uniquely in the SoftX3000. It must be within
the RACF number segment defined in ADD RACFSEG.
[Password]
This parameter specifies the password for an RACF number.
18.7 Configuring Supplementary Service Data

18.7.1 Modifying Special Tone Configuration
I. Related commands
Command
Function
ADD SPTONE
To add special tone configuration
RMV SPTONE
To remove special tone configuration

18-36

Command
Function
MOD SPTONE
To modify special tone configuration
LST SPTONE
To list special tone configuration

If a subscriber has registered a supplementary service (for example, the call forwarding
service), the SoftX3000 sends the special dial tone to the subscriber for a maximum of
16 seconds if the subscriber picks up the phone and carries out no operations. After 16
seconds, the SoftX3000 releases the call.
To modify the timer duration of the special dial tone, use MOD SPTONE to modify the
supplementary service tone.

It defines the supplementary service whose special dial tone duration is to be modified.
[Tone length]
It defines the duration of the special dial tone, ranging from 0 to 65535 in unit of second.
18.7.2 Adding Service Processing Configuration

I. Related commands
Command
Function
ADD SRVPROC
To add service processing configuration
RMV SRVPROC
To remove service processing configuration
MOD SRVPROC
To modify service processing configuration
LST SRVPROC
To list service processing configuration

When a subscriber uses such supplementary services as inquiry (for Brazail), call
forwarding, three-party service, and call waiting, the system needs to define the
corresponding call processing modes for various operations of the service subscribers
(including callers and callees) according to the service logics. Because carriers define
the service logics of the above-mentioned services differently, you can add the specific
processing mode of a supplementary service based on the service logic using ADD
SRVPROC.

18-37


It specifies the supplementary service for which the call processing mode is to be set.
The options are inquiry (for Brazail), call transfer, three-party, and call waiting.
[Hooking then dial 0 processing code] to [Hooking then dial 9 processing code]
It specifies the call processing operations to be implemented by the system when a
service subscriber presses the hook and then dials a digit.
Here are the descriptions of options:
z
Release hold party: Assume that the hook and dial 0 is for release hold party.
Service subscriber A is talking to subscriber B, and subscriber C (held party) is
listening to announcement. If A hooks and dials 0, C will be released and will hear
busy tone; A and B will continue with their conversation.
Connect hold party and release active party: Assume that the hook and dial 1 is
for connect hold party and release active party. Service subscriber A is talking to
subscriber B, and subscriber C (held party) is listening to announcement. If A
hooks and dials 1, B will be released and will hear busy tone; A and C will start
conversation.
Connect hold party and hold active party: Assume that the hook and dial 2 is for
connect hold party and hold active party. Service subscriber A is talking to
subscriber B, and subscriber C (held party) is listening to announcement. If A
hooks and dials 2, B will be held and will hear busy tone; A and C will start
conversation.
Three-party: Assume that the hook and dial 3 is for three-party. Service
subscriber A (with three-party authority) is talking to subscriber B, and subscriber
C (held party) is listening to announcement. If A hooks and dials 3, A, B, and C will
start a three-party call.
Connect other party and release self: This mode is used for call transfer service.
Assume that the hook and dial 4 is for connect other party and release self.
Service subscriber A is talking to subscriber B. If A hooks and dials C, A and C will
start conversation. If A hooks again and dials 4, A will be released and hear busy
tone; B and C will start conversation.
Return: The system does not make any changes and returns to the original state.
For the three-party scenario in Hongkong version,, the subscriber does not need to
dial after the hookflash. For example, if subscriber A (with three-party authority) is
talking with subscriber B on the phone, and the former hooks and dials C. If A hooks
again, A will enter start a three-party conversation with B and C.
[Off-hooking processing code]
It specifies the call processing operation to be implemented by the system when a
service subscriber hooks off again after on-hook.
[Doulbe-hooking processing code]
18-38


service subscriber presses the hook two times consecutively.
[Tri-hooking processing code]
service subscriber presses the hook three times consecutively.
[Hook connection flag]
It specifies whether the system holds a call when a service subscriber presses the hook.
That is, whether the system allows a service subscriber to press the hook. It is set to
Yes by default.
[Ring back flag]
When subscriber A (either as a caller or callee) talks with subscriber B on the phone, if
subscriber A hangs up after pressing the hook and then dialing the number of the
subscriber C, this parameter specifies whether the system sends the ringback tone to
subscriber B. It is set to Yes by default.
[Ring back type]
It is available only when Ring back flag is set to Yes. It specifies the type of the
ringback tone sent by the system.
18.7.3 Modifying Supplementary Service Analysis

I. Related commands
Command
Function
MOD SYNANA
To modify supplementary service analysis
LST SYNANA
To list supplementary service analysis

The call processing software analyzes the supplementary service from two aspects:
call prefix and grammar analysis string.
The call prefix of a supplementary service is configured by the command ADD
CNACLD, and the basic format is service prefix + service code + the first delimiter.
Generally, the service prefix is * or #, the delimiter is *, and the service code is a
number or numbers from 0 to 9. For example, if the call prefix of a supplementary
service is #57, # is the service prefix, 57 is the service code, and * is the first
delimiter.
The grammar analysis string of a supplementary service is the part without the call
prefix. It is preset by the system, but can be modified by the command MOD SYNANA.
The basic format is the first supplementary information + the second delimiter + the
second supplementary information + + the last supplementary information.
18-39

Generally, the delimiter is *, and each supplementary information comprises a service

keyword and a length description word followed it. The service keyword and length
descriptive word are both single character. For example, A2 represents an
abbreviated number with two digits, *1 represents a *, N? represents a telephone
number, ? represents the variant length, and L2 represents a location in the range
from 0 to 99.
By default, the grammar analysis strings relevant to supplementary services are
defined when the system is initialized, so you do not need to configure them. If carriers
want to give a special definition to a supplementary service, you can modify the
analysis configuration of the supplementary service with the command MOD SYNANA
under the guidance of the technicians of Huawei. Do not modify the configuration as
you like in case of unexpected results. The default configuration of the grammar
analysis string of each supplementary service is as shown in Table 18-13
The default configuration of the grammar analysis string of each supplementary servie
Table 18-13 Property of supplementary service
Format
description
-1 1
Format
descripti
on -2
Format
descriptio
n -3
Activate abbreviated dialing by DTMF
A2*1N?
<null>
<null>
Cancel abbreviated dialing by DTMF
A2
<null>
<null>
Cancel all abbreviated dialing by DTMF
<null>
<null>
<null>
Use abbreviated dialing by DTMF
A2
<null>
<null>
Activate abbreviated dialing by pulse
A2N?
<null>
<null>
Cancel abbreviated dialing by pulse
A2
<null>
<null>
Cancel all abbreviated dialing by pulse
<null>
<null>
<null>
Use abbreviated dialing by pulse
A2
<null>
<null>
Verify abbreviated dialing by DTMF
A2*1N?
<null>
<null>
Activate outgoing call barring by DTMF
P6
P6K1
<null>
Cancel outgoing call barring by DTMF
P6
P6K1
<null>
Verify outgoing call barring by DTMF
<null>
<null>
<null>
Activate outgoing call barring by pulse
P6
P6K1
<null>
Cancel outgoing call barring by pulse
P6
P6K1
<null>
Modify password by DTMF
O?*1F?*1F?
<null>
<null>
<null>
T4*1T4
<null>
<null>
<null>
<null>
Property of supplementary service
Activate
DTMF
Do-Not-Disturb
service
by
Cancel Do-Not-Disturb service by DTMF

18-40

Format
description
-1 1
Format
descripti
on -2
Format
descriptio
n -3
Activate Do-Not-Disturb by pulse
<null>
T4T4
<null>
Cancel Do-Not-Disturb by pulse
<null>
<null>
<null>
Activate multi-wakeup by DTMF
T4
T4D2
<null>
Cancel multi-wakeup by DTMF
<null>
T4
<null>
Verify multi-wakeup by DTMF
<null>
T4
<null>
Activate multi-wakeup by pulse
T4
T4D2
<null>
Cancel multi-wakeup by pulse
<null>
T4
<null>
Activate conference list by DTMF
L1*1N?
<null>
<null>
Activate conference list by pulse
L1N?
<null>
<null>
Cancel single conference list by DTMF
L1*1N?
<null>
<null>
Cancel all conference list by DTMF
L1
<null>
<null>
Cancel single conference list by pulse
L1N?
<null>
<null>
Use conference list by DTMF
L1
<null>
<null>
Use conference list by pulse
L1
<null>
<null>
Activate dialed number call barring by

DTMF
P6N?
<null>
<null>
Cancel dialed number call barring by

DTMF
P6N?
<null>
<null>
Verify dialed number call barring by

DTMF
P6N?
<null>
<null>
Cancel all dialed number call barring by

DTMF
P6
<null>
<null>
Activate call forwarding table by DTMF
P6
<null>
<null>
Cancel call forwarding table by DTMF
P6
<null>
<null>
Verify call forwarding table by DTMF
P6
<null>
<null>
Remotely activate call

unconditional by DTMF
forwarding
P6*1N?*1N?
<null>
<null>
Remotely
cancel
call
unconditional by DTMF
forwarding
P6*1N?
<null>
<null>
Remotely activate call forwarding busy

by DTMF
P6*1N?*1N?
<null>
<null>
Remotely cancel call forwarding busy by

DTMF
P6*1N?
<null>
<null>
Remotely activate call forwarding no

reply by DTMF
P6*1N?*1N?
<null>
<null>

18-41

Format
description
-1 1
Format
descripti
on -2
Format
descriptio
n -3
Remotely cancel call forwarding no reply

by DTMF
P6*1N?
<null>
<null>
Password call by DTMF
P6*1N?
P6N?
<null>
Password call by pulse
P6N?
<null>
<null>
Cancel ALL Supplementary Service by

DTMF
P6
<null>
<null>
Cancel ALL Supplementary Service by

pulse
P6
<null>
<null>
Active callout allowed by DTMF
P6
<null>
<null>
Cancel callout allowed by DTMF
P6
<null>
<null>
Activate dialed number call barring by

DTMF
P6
<null>
<null>
Cancel dialed number call barring by

DTMF
P6
<null>
<null>
Activate dialed number call allowed by

DTMF
P6
<null>
<null>
Cancel dialed number call allowed by

DTMF
P6
<null>
<null>
Cancel all dialed number call allowed by

DTMF
P6
<null>
<null>
Modify super password by DTMF
O6*1F6*1F6
<null>
<null>
Activate wakeup by DTMF
T4
<null>
<null>
Activate wakeup by pulse
T4
<null>
<null>
Set CFS CLID by DTMF
Y2N?
<null>
<null>
Activate call forwarding selective by time

of day by DTMF
Y2*1T4*1T4
<null>
<null>
Activate call forwarding selective by day

of week by DTMF
Y2*1W7
<null>
<null>
Activate call forwarding selective by

DTMF
Y2*1N?
Y2
N?
Cancel call forwarding selective by caller

number by DTMF
Y2
<null>
<null>
Cancel call forwarding selective by time

of day by DTMF
Y2
<null>
<null>
Cancel call forwarding selective by day

of week by DTMF
Y2
<null>
<null>

18-42

Format
description
-1 1
Format
descripti
on -2
Format
descriptio
n -3
Cancel call forwarding selective entry by

DTMF
<null>
Y2
<null>
Deactivate call forwarding selective by

DTMF
<null>
Y2
<null>
Query call forwarding selective general

local information
Y2
<null>
<null>
Activate selective call acceptance by

caller number by DTMF
Y2N?
<null>
<null>

time of day by DTMF
Y2*1T4*1T4
<null>
<null>
Activate selective call acceptance by day

of week by DTMF
Y2*1W7
<null>
<null>

DTMF
<null>
Y2
<null>
Cancel selective call acceptance by

caller number by DTMF
Y2
<null>
<null>
Cancel selective call acceptance by time

of day by DTMF
Y2
<null>
<null>
Cancel selective call acceptance by day

of week by DTMF
Y2
<null>
<null>
Cancel selective call acceptance entry

by DTMF
<null>
Y2
<null>
Deactivate selective call acceptance by

DTMF
<null>
Y2
<null>
Query selective call acceptance general

local information
Y2
<null>
<null>
Activate selective call rejection by caller

number by DTMF
Y2N?
<null>
<null>
Activate selective call rejection by time of

day by DTMF
Y2*1T4*1T4
<null>
<null>
Activate selective call rejection by day of

week by DTMF
Y2*1W7
<null>
<null>
Activate selective call rejection by DTMF
<null>
Y2
<null>
Cancel selective call rejection by caller

number by DTMF
Y2
<null>
<null>
Cancel selective call rejection by time of

day by DTMF
Y2
<null>
<null>
Cancel DTMF selective call rejection by

day of week
Y2
<null>
<null>

18-43

Format
description
-1 1
Format
descripti
on -2
Format
descriptio
n -3
Cancel selective call rejection entry by

DTMF
<null>
Y2
<null>
Deactivate selective call rejection by

DTMF
<null>
Y2
<null>
Query selective call rejection general

local information
Y2
<null>
<null>
Activate international operator call-in

barring by DTMF
P6
<null>
<null>
Cancel international
barring by DTMF
P6
<null>
<null>
Verify Do-Not-Disturb by DTMF
<null>
T4*1T4
<null>
Activate PWCB by DTMF
P?
<null>
<null>
Deactivate PWCB by DTMF
P?
<null>
<null>
Once set PWCB by DTMF
P?*1N?
<null>
<null>
Remotely activate PWCB by DTMF
P?*1N?
<null>
<null>
Remotely deactivate PWCB by DTMF
P?*1N?
<null>
<null>
Set once authentication mode by DTMF
P?*1N?
<null>
<null>
Set manual authentication mode by

DTMF
P?*1N?
<null>
<null>
Cancel manual authentication mode by

DTMF
P?*1N?
<null>
<null>
Set selective call waiting by DTMF
Y2N?
<null>
<null>
Activate selective call waiting by DTMF
Y2
<null>
<null>
Set distinctive ringing with CLID by

DTMF
Y2N?
<null>
<null>
Activate distinctive ringing entry by

DTMF
Y2Z2
<null>
<null>
Deactivate distinctive ringing entry by

DTMF
Y2
<null>
<null>
Cancel distinctive ringing entry by DTMF
Y2
<null>
<null>
Test distinctive ringing by DTMF
Z2
<null>
<null>
Activate customized duration of ringing

by DTMF
V1S2
<null>
<null>
Activate customized duration of ringing

by pulse
V1S2
<null>
<null>
operator
call-in

18-44

Format
description
-1 1
Format
descripti
on -2
Format
descriptio
n -3
Registrer collective call screening by

pulse
P?
<null>
<null>
Register collective call screening by

DTMF
P?
<null>
<null>
Cancel collective call screening by

DTMF
P?
<null>
<null>
Cancel collective call screening by pulse
P?
<null>
<null>
Activate malicious call tracing
R1
<null>
<null>
Set call park appplication by DTMF
N?
<null>
<null>
Cancel selective call waiting
Y2
<null>
<null>
Deactivate selective call waiting entry
Y2
<null>
<null>
MRS test
N5*1N5
<null>
<null>

[Service]
It specifies of which category of supplementary service the grammar analysis string
needs modifying.
[Format description -1], [Format description -2], [Format description -3]
They define the grammar analysis string of the supplementary service. You can define
at most three format descriptions for each supplementary service. In other words, you
can operate a supplementary service in three different ways. The longest grammar
format string contains 15 characters.
The basic format of the format description is the first supplementary information + the
second delimiter + the second supplementary information + ... + the last supplementary
information. Generally, the delimiter is * or #. The supplementary information
comprises a service keyword and a length description word followed it, and they are
both single character. For examplem, A2 represents an abbreviated number with two
digits, *1 represents a *, N? represents a telephone number, ? represents the
variant length, L2 represents a location in the range from 0 to 99. The definition of
each character in the service keyword and length description word is as follows:
z
variant length
abbreviated number
CIC circuit number
duration
new password

18-45

The K value of the call restriction level
location
module number
telephone number
old password
the duration of customized ringing
start time or end time
the type of customized ringing
the entrance number of selective service
ring type
password
Phase
date
Generally, the supplementary service ends with a # (timeout or maximum number

length) by default, so you do not need to configure it.
18.7.4 Modifying Supplementary Service Collision Configuration

I. Related commands
Command
Function
MOD COMPTB
To modify supplementary service collision configuration
LST COMPTB
To list supplementary service collision configuration

The SoftX3000 provides tens of supplementary services, but some conflict with each
other. In other words, they cannot be registered simultaneously. For example, if you
registered the absent subscriber service, you cannot register the non-disturb service.
However, it does not mean that the collision is a bi-directional collision. That is to say, if
you register service A first, you cannot register service B, but if you register service B
first, you can still register service A.
You can configure the collision of the supplementary service by the command MML.
Generally, use the default configuration. If carriers have special requirements, you can
modify the collision configuration of the supplementary service with the command MOD
COMPTB under the guidance of the technicians of Huawei. Do not modify the
configuration as you like in case of unexpected results.

[Service]

18-46

It specifies of which category of supplementary service the collision configuration

needs modifying. In other words, if you register the supplementary service specified
here, you cannot register the supplementary services 1 to 7 specified in this command.
[Service 1] to [Service 7]
They specify the supplementary services conflicting with the supplementary service
above. If BUTT is selected, it means canceling the relevant collision configuration.
18.7.5 Modifying Supplementary Service Priority Configuration

I. Related commands
Command
Function
MOD PRIOR
To modify supplementary service priority configuration
LST PRIOR
To list supplementary service priority configuration

Although you can register these supplementary services simultaneously, they are not
all valid. That is to say, only the supplementary service with the highest priority is valid.
For example, by default, the call forwarding busy service has the higher priority than the
call forwarding no reply service. If you register the two services, only the call forwarding
busy service takes effect.
You can configure the priority of the supplementary services by the command MML.
Generally, use the default configuration. If carries have special requirements, you can
modify the priority configuration of the supplementary services with the command MOD
PRIOR under the guidance of the technicians of Huawei. Do not modify the
configuration as you like in case of unexpected results.

[Priority]
It numbers the priority. If multiple supplementary services are registered, the one with
the highest priority takes effect. The value range of the parameter is 014. 0 represents
the highest priority, 1 represents the next highest priority, and so on.
[Service]
It specifies a supplementary service corresponding to the priority above.

18-47

18.7.6 Adding Call Forwarding Restriction

I. Related commands
Command
Function
ADD CFBAR
To add call forwarding restriction
RMV CFBAR
To remove call forwarding restriction
MOD CFBAR
To modify call forwarding restriction
LST CFBAR
To list call forwarding restriction

By default, in call forwarding services, when a service subscriber (either as a caller or
callee) sets a forwarded-to number, the system admits this number no matter whether it
is a local number or an outgoing prefix if only the service subscriber has the
corresponding call-out authority.
To prohibit a service subscriber from using a certain prefix as the forwarded-to number,
that is, to enable the system to reject the called numbers with a certain prefix, you can
add the call forwarding restriction data accordingly using ADD CFBAR.

It defines the supplementary service for which the call forwarding restriction data is to
be set. The options are call transferring, call forwarding unconditional, call forwarding
busy, call forwarding no reply, call forwarding offline, inquiry, call forwarding no reply
when call waiting, secretary service, and selective call forwarding.
[Local DN set]
It specifies the local DN set of the callers for whom the call forwarding restriction data is
to be set. This parameter must be defined in the ADD LDNSET command before being
referenced here.
[Call source code]
It specifies the call source code of the callers for whom the call forwarding restriction
data is to be set. This parameter must be defined in the ADD CALLSRC command
[Barring group number]
It defines a barring group number uniquely in the SoftX3000, ranging from 0 to 65535
except 60001, 60002, and 65534. To prohibit a service subscriber from using a certain
prefix as the forwarded-to number, you need to set the barred call prefix as the barring

18-48

group number defined here using ADD CLDGRP. When a service subscriber sets this
prefix as the forwarded-to number, the system rejects the call.
18.7.7 Adding Call Forwarding Data

I. Related commands
Command
Function
ADD CFDATA
To add call forwarding data
RMV CFDATA
To remove call forwarding data
LST CFDATA
To list call forwarding data

Generally, a service subscriber can set a forwarded-to number on a phone set when
using the call forwarding unconditional, call forwarding busy, and call forwarding no
reply services. To facilitate managing call forwarding services, you can add or remove a
forwarded-to number for a service subscriber using ADD CFDATA or RMV CFDATA.

[Local DN set]
It specifies the local DN set of the callers for whom the call forwarding data is to be set.
This parameter must be defined in the ADD LDNSET command before being
referenced here.
[Subscriber number]
It specifies the number of the subscriber for whom the call forwarding data is to be set.
This parameter must be defined in the ADD VSBR, ADD MSBR, or ADD BRA
The subscriber number defined here must have the corresponding call forwarding
service authority and it cannot be a to-be-changed number, a suspended number, or a
PBX number occupying no number resource.
[Call forwarding cause]
It defines the type of the call forwarding service. The options are call forwarding
unconditional, call forwarding busy, and call forwarding no reply.
[CF number]
It defines the forwarded-to number. Set this parameter by the following principles:
z
You can register a maximum of five forwarded-to numbers for a service subscriber.
For the call forwarding busy service and the call forwarding no reply service, you
can register them three times at most respectively for a service subscriber. For the
call forwarding unconditional service, you can only register it once.
18-49

z
If the call forwarding busy service and the call forwarding no reply service are both
registered, the system will forward a call to the next number if the transfer to the
first forwarded-to number fails.
After registering the call forwarding unconditional service for a service subscriber,
you cannot register the other forwarding services for this service subscriber any
more, and all call forwarding services registered before become invalid.
18.7.8 Setting MWN Service Configuration

I. Related commands
Command
Function
SET MWNSRV
To set MWN service configuration
LST MWNSRV
To list MWN service configuration

For the Message Waiting Notification (MWN) service, if a service subscribers phone
set supports MDMF, the system not only turns on the message waiting indicator on the
phone set, but also sends a message waiting notification to the phone set through
DTMF or FSK signal when a voice message is received in the mailbox. To enable this
function, you must set the MWN service data using SET MWNSRV.

[Played tone type]
In the MWN service, it indicates the MWN tone type for which the MWN service data is
to be set. That is, when there is a voice message, a service subscriber can hear the
corresponding voice prompt after offhook.
[Message content]
It specifies the content of a message waiting notification sent by the SoftX3000 to a
phone set. It is a string of 1 to 20 characters.
[Light flag]
When a voice message is received, this parameter indicates whether the system turns
on the message waiting indicator of a phone set. It is set to Yes by default.
[Work way]
When the SoftX3000 needs to send a message waiting notification to a phone set that
supports MDMF, this parameter specifies whether the SoftX3000 adopts DTMF or FSK
to modulate the notification. The default mode is DTMF.

18-50

Appendix A Configuring SNTP Client

A.1 Overview
Simple Network Time Protocol (SNTP) Client is a service process of the BAM server
software U-SYS SoftX3000 Server. The purpose of configuring SNTP Client is to
enable the BAM to synchronize its time with that of the network time server (that is, the
NTP server).
I. Basic concept of time synchronization

Time synchronization is to limit the deviation of the time of communication equipment or
computers in the network from Universal Coordinated Time (UTC) to a small range (for
example, 100 ms).
In the NGN, time synchronization is necessary for charging, alarms, and logs.
z
In view of charging, because different carriers have different charging policies and
time-based tariff policy is widely used, conflicts always occur in inter-network
settlement due to different charging start time points. For example, suppose that
the network of carrier A interworks with that of carrier B through a gateway office,
the system time of office A is 30 seconds earlier than UTC, the system time of
office B is 30 seconds later than UTC, and half charge is set from 21:00 of the
current day to 08:00 of the next day. For the inter-network calls generated at about
21:00, it might happen that the calls are half-charged at office A but full-charged at
office B.
In view of network management, the NMS needs to accurately record the time
when alarms and events of each node are generated for troubleshooting and
performance analysis. If the system time of all nodes in the network is not
synchronized, system logs will be inaccurate and they cannot be used for
troubleshooting.
II. UTC transmission mode

There are two modes for transmitting UTC: wireless mode (through high- or
low-frequency radio signal), and wired mode (through DCN, PSTN, or DDN). Generally,
telecommunications networks adopt the second mode.
With the development of the computer networks, Network Time Protocol (NTP)
becomes one member of the TCP/IP family. At present, the time server installed with
the NTP software on Internet provides time reference for clients. Almost all high-level
time servers obtain the absolute time information of UTC from a Global Positioning
System (GPS) receiver through the RS-232 interface; while low-level time servers

A-1

obtain UTC from the upper-level servers in the TCP/IP-based DCN. All clients
(computers) receive UTC from a specified time server through the NTP client software.
III. Time synchronization of SoftX3000

The SoftX3000 supports SNTP. With the NTP server in networking, the SoftX3000 uses
the master/slave synchronization mode. That is, the BAM time is synchronized with the
host time, and the NTP server time is synchronized with the BAM time. Refer to
Figure A-1.
Host
S3526
Internal
protocols
SNTP
MAN
BAM
NTP Server
SoftX3000
Figure A-1 Time synchronization relationship of the SoftX3000
Figure A-1 is illustrated as follows:
1)
The BAM time is synchronized with the host time through internal protocols. That
is, the BAM broadcasts the time information periodically to the SMUI in each frame
of the host through the internal Ethernet. After receiving the time message, the
SMUI broadcasts it to the service boards in each frame through the internal
Ethernet. Based on the time information, the service boards adjust the local time.
2)
The NTP server time is synchronized with the BAM time through SNTP. The NTP
server is the SNTP Server, and the BAM is the SNTP Client. The BAM sends a
time adjustment request to the NTP server periodically. Upon receiving the
request, the NTP server returns a result. Receiving the result message, the BAM
calculates the transmission delay according to the time stamp of the message,
and then calculates the deviation between the time of the local clock and that of
the time server to adjust the local time.
If the SoftX3000 uses the synchronization mode as shown in Figure A-1, you must set
the data for interconnection between the BAM and the NTP server (that is, the SNTP
Client).

A-2

A.2 Guide to Data Configuration

I. Overview
When the U-SYS SoftX3000 Server module of the BAM server software is integrated
with the SNTP Client process as shown in Figure A-2, you only need to set the IP
address of the SNTP Server in the BAM configuration file STXBAM.ini to achieve the
interconnection between the BAM and the NTP server.
Figure A-2 [U-SYS SoftX3000 Server] window

1)
In the directory D:\SoftX3000 of the BAM hard disk, open the file STXBAM.ini
with a file editor, for example, notepad, and then drag the scroll bar of the window
to find [System] as shown in Figure A-3.

A-3

Figure A-3 Configuration window of STXBAM.ini

2)
In the configuration window as shown in Figure A-3, find the options related to
NTP, including NTPSyncPeriod, NTPServerList, NTPInterIPCount, NTPInterIP0,
and NTPInterIP1. Generally, you only need to set the IP address of the NTP server.
That is, set the NTPServerList as needed. For example, set NTPServerList to
10.70.3.173. If the BAM interconnects with several NTP servers, you can use a
semicolon to separate the IP addresses. For example, set "NTPServerList to
10.70.3.173;10.70.3.88. See Table A-1 for the meaning of the options.

A-4

Table A-1 Meaning of the NTP related options

NTPSyncPeriod
Meaning: NTP synchronization period, in unit of minute.
Value type: Integer
Value range: 11440
Default value: 1
NTPServerList
Meaning: IP address list of the NTP server
Value type: Character string
Value range: Multiple IP addresses are separated by semicolon. It is

recommended that the list contains no more than 12 addresses.
Default value: 127.0.0.1
NTPInterIPCount, NTPInterIP0, NTPInterIP1
Meaning: The number of the IP addresses of the NTP server and the IP
addresses
Value type: Character string
Value range: Valid IP address
3)
Default value: NTPInterIPCount = 2, NTPInterIP0 = 172.20.200.0, NTPInterIP1

= 172.30.300.0
Note: The above IP addresses are actually internal IP addresses for the BAM to
communicate with the host. In normal cases, the above three options are not
set. The purpose of keeping these options is to prevent the BAM from using its
internal IP address when sending NTP packets, so as to ensure that the NTP
server can return NTP response packets to the BAM correctly.
Finishing the configuration, restart the SNTP Client to validate the setting.

A-5

Appendix B Basic Principles of CRG Charging

B.1 Overview
B.1.1 Basic Concepts
I. CRG charging
CRG charging is based on charging signaling messages. In CRG charging, charging
signaling messages such as charging information message (CRG), charging band
message (CHB), charging information message (CHG), tariff change message (TAC),
charging unit message (CHU), and charging pulse message (CHP) are transferred in
inter-office ISUP signaling for charging. Different from independent charging, CRG
charging requires that all offices in the network cooperate in charging signaling.
II. Charging office

Charging office indicates the office that generates bills for a call. Normally, it is the office
that originates the call.When centralized charging or inter-network fee settlement is
required, the charging office may be a tandem office, a gateway office, or a toll office.
III. Charging controlling office

Charging controlling office indicates the office that sends the charging signaling
message to the charging office in an incoming call. Normally, it is the terminating office.
Suppose that there is a charging controlling office in a call (If there are multiple charging
controlling offices, choose the first one). The charging controlling office determines the
charging signaling process (signaling process 1, 2, or 3). The charging signaling
process of other offices such as tandem offices and the originating office must be
consistent with that of the charging controlling office.The charging controlling office and
other tandem offices can charge according to charging signaling messages, although
charging signaling messages need to be sent to the originating office or gateway office.
That is, any office can be a charging office.
IV. Detailed charging information

Detailed charging information indicates the charging data of the charged office directly
used to calculate meter pulse. It is transferred through CHG or TAC message. It is
equivalent to parameters such as TA, PA, TB, and PB in the charging system.For
example, set the above four parameters to 180/2/60/1, which means to record twice in
the first 180 seconds of the conversation and then once every 60 seconds.

B-1

V. Charging band number

Charging band number cites the detailed charging information. It is transferred through
CHB or CRG message. It is equivalent to the charging system index. It needs to be
uniformly numbered in the whole network.
VI. Charging pulse

Charging pulse directly instructs the charging office to charge a call with meter counts.
It is transferred through CRG, CHU, or CHP message. It is equivalent to the final
charging result.
B.1.2 Charging Mode and Charging Process

I. CRG charging mode
1)
Charging mode 1:There is detailed charging information in the charging office. But
it cannot determine the charging information to be used. The charging controlling
office notifies the charging office of the charging information to be used through
CRG or CHB message.The parameter Charging band number contained in CRG
or CHB message is used by the charging office to determine the detailed charging
information to be used for charging.
2)
Charging mode 2:There is no detailed charging information in the charging office.

The charging office can be notified of the detailed charging information only
through CHG or TAC message sent by the charging controlling office.The
charging office charges according to the charging information such as Packet
charging, Tariff indicator and Time indicator contained in the CHG or TAC
message.
3)
Charging mode 3:There is no detailed charging information in the originating office.

The originating office can charge a call only through receiving CHU or CHP
charging pulse message from the charging controlling office.
II. Signaling process of CRG charging

1)
Charging signaling process 1:The detailed charging information is transferred

through CHG and TAC-charging acknowledge (CHA) messages. Or the charging
pulse information is transferred through CHU-CHA messages.TAC-CHA indicates
that a CHA message must be sent for confirmation after a TAC message is sent.
CHU-CHA indicates that a CHA message must be sent for confirmation after a
CHU message is sent.
2)
Charging signaling process 2:CHB message is used to transfer charging band

number information. Or CHP message is used to transfer charging pulse
information.
3)
Charging signaling process 3:CRG message is used to transfer the charging band
number information or the charging pulse information.A CRG message cannot

B-2

concurrently transfer the charging band number information and the charging
pulse information.
The relationship between the CRG charging modes and charging signaling processes
is listed in Table B-1.
Table B-1 Relationship between the CRG charging modes and charging signaling
processes
Charging
signaling
process 1
Charging mode 1
Charging mode 2
Charging mode 3
Charging
signaling
process 2
Charging
signaling
process 3
X in the table indicates a charging signaling process possibly used by a CRG charging
mode.
B.2 CRG Charging Process

B.2.1 Charging Process of the First Class (CHG/TAC)
I. Transmission of the charging data during call set-up phase
In this process, the charging data is obtained during call set-up phase, as shown in
Figure B-1.

B-3

originating exchange with
charging process
intermediate
exachange
IAM

intermediate exchange with
charging data determination
function
IAM
IAM
intermediate
exachange
destination
exachange
IAM
ACM
ACM
ACM
ACM
CHG
ANM
ANM
CHG
ANM
ANM
TAC
TAC
CHA
CHA
TAC
TAC
CHA
CHA
REL
REL
RLC
RLC
REL
RLC
REL
RLC
Figure B-1 Transmission of the charging data during call set-up phase
The call set-up phase makes use of the CHG message, which contains the charging
information of the current time band and that of the next time band. This message is
sent from the charging controlling office to the originating office during call set-up.
1)
When the CHG message is received before the address complete message
(ACM), the relevant ACM timers (generally it is T7) should be reinitiated after the
receipt of the CHG message; and the sending and reception of the CHG message
must be completed before the sending of answer message (ANM) and connect
message (CON).
2)
If the charging case attribute of the originating office is set as Receiving CHG
message and the message is not received before ANM and CON messages, the
call will be released then (with cause 111).
3)
If the given call is charge-free (possibly in the following circumstances: a. the

calling party is a free call user; b. the Charging Indicator in Backward Call
B-4

Indicators of ACM, ANM, CPG and CON messages is Free), the charging will
not be performed even if the CHG message with charging information is received
before ANM or CON.
4)
For the intermediate office (e.g. tandem office) that transparently transmits the
CHG message, the CHG charging message should be inspected in the following
way:whether the CHG message is transmitted before ANM or CON backward
messages. The same inspection should also be carried out in the charging office.
5)
If it is possible that the tariff change occurs between the reception of CHG and that
of ANM/CON, the tariff change should be specified by the Next Charging
Information parameter of the CHG message.
II. Tariff-change during conversation phase

In a call, if the charging message CHG has been received while the tariff change occurs
during the conversation (for example, different tariffs for different time bands of a day),
the charging controlling office will send the charging message through which the
changed tariff will be transmitted. Refer to Figure B-1 for more details.
1)
The first tariff change may be specified by the charging message CHG.
2)
The subsequent tariff changes are specified by the TAC message sent by the
charging controlling office.
3)
The TAC message should be sent within fifteen minutes ahead of the tariff change
point.In the actual application, the fifteen minutes may be shortened to three to five
minutes.
4)
When the charging office receives the TAC message, the CHA message should
be sent to acknowledge the reception of TAC.The charging office updates the
charging data based on the tariff change information contained in TAC to facilitate
the change at the tariff change point specified by TAC.
5)
If the charging controlling office sending TAC does not receive a CHA message
within timer T40 (normally 25 seconds), it shall resend a TAC message with the
same number and start timer T41 (normally 60 seconds).
6)
If the charging controlling office can not receive the CHA message within timer
T41, the call will be released.
III. Charging process description relevant to CHU/CHA

For a given call, if it is charged by performing the reception and sending of the charging
pulse, the charging controlling office should send the CHU message to the originating
exchange immediately after the call set-up.Contents of the CHU message are as
follows: the number of the charging pulses and message number that starts from 1 and
is increased by 1 each time.
When the charging office receives the CHU message, it should record the number of
charging pulses on the charging meter and send forwards a CHA message to
acknowledge the reception of CHU, as shown in Figure B-2.

B-5

originating exchange with
charging process
intermediate
exachange
IAM

function
IAM
intermediate
exachange
IAM
destination
exachange
IAM
ACM
ACM
ACM
ACM
ANM
ANM
ANM
ANM
CHU
CHU
CHA
CHA
CHU
CHU
CHA
CHA
REL
REL
RLC
RLC
REL
RLC
REL
RLC
Figure B-2 Charging process description relevant to CHU/CHA

If the charging office receives a first CHU whose number is not 1 or receives two CHU
messages who have the same number, the call will be released (with cause 111).
If the charging controlling office sends the CHU message and receives no CHA
message within timer T42, it shall resend a CHU message with the same number and
start timer T43.If no CHA is received within timer T43, the call will be released.
B.2.2 Charging Process of the Second Class (CHB/CHP)

For this class of the charging process, the charging information transmitted among the
offices is the charge band number or the charging pulse.
I. CHB Charging Process

The CHB charging process is as shown in Figure B-3.

B-6

originating exchange
with charging process
intermediate
exachange
IAM

function
IAM
IAM
CHB/CRG
CHB/CRG
intermediate
exachange
destination
exachange
IAM
ACM
ACM
ACM
ACM
ANM
ANM
ANM
ANM
REL
REL
RLC
RLC
REL
RLC
REL
RLC
Figure B-3 CHB charging process

1)
First of all, a valid CHB message should be transmitted during call set-up phase
and various tandem and originating offices should restart the ACM timer after the
reception of the CHB message.
2)
The CHB message contains the charge band number parameter.The so-called
charge band number is the number of the charging band that is divided based on
the destination address or some special services.If multiple CHB messages are
transmitted during call set-up phase, the only acceptable band number is that
contained in the last message.
3)
For the originating office, when the CHB charging mode is enabled, if it receives
no CHB message before the reception of the ANM or CON message, the call will
be released.
4)
Generally, if the call is stated as charge-free by the backward call indicators

parameter contained in backward messages such as CPG, ACM, ANM, and CON,
the charging will not be performed even though the CHB message is received.
II. CHP charging process

The CHB charging process is as shown in Figure B-4.

B-7

originating exchange
with charging process

function
destination
exachange
intermediate
exachange
IAM
IAM
IAM
ACM
ACM
ANM
ACM
ANM
ANM
CRG/CHP
CRG/CHP
CRG/CHP
.
.
.
REL
CRG/CHP
REL
REL
Callee
hooks on
RLC
RLC
RLC
Figure B-4 CHP charging process

1)
The charging office will perform the charging analysis during call set-up phase and
enable the specified charging process. It will select CHP if it charges through
transmitting charging pulses.
2)
CHP is transmitted after the call set-up, that is, it is transmitted during
conversation phase.It should be noted that the CHP charging process is usually
determined by the following special requirements:Large-capacity charging and
charging requirements of the subscriber line.
3)
In the CHP message, the charging pulse number is an optional parameter. If

there is no such parameter in the message, the charging pulse number is taken as
1 by the charging office.
4)
Generally, if the call is stated as charge-free by the backward call indicators

parameter contained in backward messages such as CPG, ACM, ANM, and CON,
the charging will not be performed even though the CHP message is received.

B-8

B.2.3 Charging Process of the Third Class (CRG)

There is only one charging message in this class: CRG, however, the message is
divided into two types according to its charging parameters:CRG_BAND and
CRG_UNIT
I. CRG_BAND charging process

The so-called CRG_BAND charging means that the CRG message contains the
charging band number parameter.If the charging process is set as CRG_BAND, the
received CRG message that only contains the charging pulse number parameter will be
taken as an invalid CRG_BAND.For detailed analysis, refer to Table B-2.
Table B-2 CRG message analysis in the CRG_BAND charging process
CRG message
Analysis result
Charging band number
Charging pulse number
Not present
Not present
Wrong CRG message
Not present
Present
Invalid CRG message
Present
Not present
Correct CRG message
Present
Present
Wrong CRG message
As shown in the above table, the CRG message that only contains the charging band
number parameter is taken as the correct charging message in the CRG_BAND
charging process.The CRG_BAND charging process is the same as the CHB charging
process. For details, refer to Figure B-3.
II. CRG_UNIT charging process

The so-called CRG_UNIT charging process is based on the CRG message that
contains the charging pulse number parameter. If the charging mode is set as
CRG_UNIT, the received CRG message that only contains the charging band number
parameter will be taken as an invalid CRG_BAND.For detailed analysis, refer to
Table B-3.
Table B-3 CRG message analysis in the CRG_UNIT charging process
CRG message
Analysis result
Charging band number
Charging pulse number
Not present
Not present
Wrong CRG message
Not present
Present
Correct CRG message
Present
Not present
Invalid CRG message
Present
Present
Wrong CRG message

B-9

As shown in the above table, the CRG message that only contains the charging pulse
number parameter is taken as the correct charging message in the CRG_UNIT
charging process.The CRG_UNIT charging process is the same as the CHP charging
process. For details, refer to Figure B-4.
B.2.4 Special Cases of the CHP/CRG Charging Modes

I. In the calling party controlling release mode, the called party hooks on and
then the calling party hooks on
In such circumstance, the SUS message is sent to the charging controlling office after
the called party hooks on. The charging controlling office will not forward the SUS
message but start timer T6. Within timer T6, if the calling party hooks on, the call will be
released.However, the duration before a call is released (including that after callee
onhook) is charged.That is, during this period, the charging controlling office keeps
sending CHP/CRG messages to the originating office.The charging signaling process
is as shown in Figure B-5..
originating exchange with intermediate exchange with
charging process
function
intermediate
exachange
destination
exachange
IAM
IAM
SAM
SAM
IAM
SAM
ACM
ACM
ACM
ANM
ANM
Callee
answers
SUS
Callee
hooks on
ANM
CRG/CHP
CRG/CHP
CRG/CHP
SUS
start T6
.
.
.
CRG/CHP
REL
stop T6
REL
RLC
REL
RLC
RLC
REL
Figure B-5 In the calling party controlling release mode, the called party hooks on and
then the calling party hooks on
B-10

II. In the calling party controlling release mode, the called party hooks on and
then hooks off and re-answers
In such circumstance, if the interval between the on-hook and the next off-hook does
not exceed the time specified by T6 timer, the interval is charged.The charging
signaling process is as shown in Figure B-6.
charging process
function
destination
exachange
intermediate
exachange
IAM
IAM
SAM
SAM
IAM
SAM
ACM
ACM
ACM
ANM
ANM
Callee
answers
ANM
CRG/CHP
CRG/CHP
SUS
CRG/CHP
start T6
.
.
.
CRG/CHP
stop T6
RES
SUS
Callee
hooks on
RES
Callee
answers again
CRG/CHP
REL
REL
RLC
REL
RLC
RLC
REL
then hooks off and re-answers
III. In the calling party controlling release mode, the called party hooks on and
the call is released due to the timer expiry
In such circumstance, if no off-hook occurs within timer T6, the call will be released due
to the timer expiry.The charging signaling process is as shown in Figure B-7.

B-11


charging process
function
destination
exachange
intermediate
exachange
IAM
IAM
SAM
SAM
IAM
SAM
ACM
ACM
ACM
ANM
ANM
Callee
answers
SUS
Callee
hooks on
ANM
CRG/CHP
CRG/CHP
CRG/CHP
SUS
start T6
.
.
.
CRG/CHP
REL
expiry T6
REL
REL
RLC
RLC
RLC
REL
the call is released due to the timer expiry

B-12

Appendix C Tone ID
Appendix C Tone ID
TID
Parameter value
Tone name
TID_0X0001
Time announcement
TID_0X0003
Malicious call tracing failure tone
TID_0X0004
Wakeup tone
TID_0X0005
Conference gathering tone
TID_0X0006
Network congestion tone
TID_0X0007
Call back tone
TID_0X0008
Incoming toll call tone
TID_0X0009
Supplementary service cancellation tone
TID_0X000A
10
Call forwarding notification tone
TID_0X000B
11
Wrong number tone
TID_0X000C
12
Vacant number tone
TID_0X000D
13
Do-Not-Disturb tone
TID_0X002E
46
Absent subscriber tone
TID_0X002F
47
Absent subscriber tone for (SS)
TID_0X0030
48
Supplementary service registration success

tone
TID_0X0031
49
Supplementary service registration failure tone
TID_0X0032
50
Billing tone
TID_0X0033
51
Call restriction tone
TID_0X0034
52
Malicious call tracing success tone
TID_0X0035
53
Music
TID_0X0036
54
Call waiting tone
TID_0x0038
56
Call waiting tone A
TID_0x0039
57
Call waiting tone B
TID_0x003A
58
Call waiting tone C
TID_0x003B
59
Call waiting tone D
TID_0x003C
60
Call block tone
TID_0x003D
61
Query caller number tone for selective call
TID_0x003E
62
Unallocated number tone

C-1

TID
Appendix C Tone ID
Parameter value
Tone name
TID_0x003F
63
Confirmation tone
TID_0x0040
64
Collect call caller tone
TID_0x0041
65
Collect call callee tone
TID_0x0042
66
Callee logout tone
TID_0x0043
67
Temp billing tone
TID_0x0044
68
Out billing tone
TID_0x0045
69
Outin billing tone
TID_0x0046
70
180 service tone 0
TID_0x0047
71
180 service tone 1
TID_0x0048
72
180 service tone 2
TID_0x0049
73
180 service tone 3
TID_0x004A
74
180 service tone 4
TID_0x004B
75
180 service tone 5
TID_0x004C
76
180 service tone 6
TID_0x004D
77
Meter tone
TID_0x0100
256
Weather report announcement
TID_0x0101
257
No area code tone
TID_0x0103
259
Mute tone
TID_0x0104
260
Test code
TID_0x0105
261
Test tone
TID_0x0106
262
Charging service request failure tone
TID_0x0107
263
Card fund insufficient tone
TID_0X0108
264
Reserved_5 (congestion tone)
TID_0X010A
266
Reserved_6
TID_0X010B
267
Recorded_0 (temporarily unreachable tone)
TID_0X010C
268
Recorded_1 (test end tone)
TID_0X010D
269
Recorded_2
TID_0X010E
270
Recorded_3
TID_0X010F
271
Recorded_4
TID_0X0110
272
Recorded_5
TID_0X0111
273
Recorded_6 (message retrieved tone)
TID_0X0112
274
Recorded_7 (invalid password tone)

C-2

TID
Appendix C Tone ID
Parameter value
Tone name
TID_0X0113
275
Recorded_8 (card fund insufficient tone)
TID_0X0114
276
Recorded_9 (unallocated number tone)
TID_0X0115
277
Recorded_10 (number expansion tone)
TID_0X0116
278
Recorded_11
TID_0X0117
279
Recorded_14 (forward indication tone)
TID_0X0118
280
Recorded_18 (multiparty tone)
TID_0X0119
281
Recorded_19 (hang up prompt tone)
TID_0X011A
282
Recorded_20 (toll call tone)
TID_0X011B
283
Recorded_21 (emergency call tone)
TID_0X011C
284
Recorded_22 (silence tone)
TID_0X011D
285
Recorded_23 (incoming call restriction tone)
TID_0X011E
286
Recorded_24 (outgoing call restriction tone)
TID_0X011F
287
Recorded_25 (busy tone)
TID_0X0120
288
Recorded_26 (power off tone)
TID_0X0121
289
Recorded_27 (service not applied tone)
TID_0X0122
290
Recorded_28 (add zero tone)
TID_0X0123
291
Recorded_31
TID_0X0124
292
Special channel test tone
TID_0X0125
293
IP operation failure tone
TID_0X0126
294
IP choice notification tone
TID_0X0127
295
IP route busy tone
TID_0X0128
296
No reply tone
TID_0X0129
297
IP registered tone
TID_0X012A
298
IP not registered tone
TID_0X012B
299
IP operation success tone
TID_0X012C
300
Number changed tone
TID_0X012D
301
Second dial tone
TID_0X012E
302
Special ring back tone
TID_0X012F
303
Call forwarding restriction tone
TID_0X0130
304
SIP ring back tone
TID_0X0200
512
Callee billing tone
TID_0X0201
513
Call-in restriction tone

C-3

TID
Appendix C Tone ID
Parameter value
Tone name
TID_0X0202
514
Callee not active tone
TID_0X0203
515
Callee busy tone
TID_0X0204
516
Detection test tone
TID_0X0205
517
Bad TS31 tone
TID_0X0206
518
Mobile callee not reachable tone
TID_0X0207
519
Test finish tone
TID_0X0209
521
Invalid password tone
TID_0X020A
522
Computer on duty tone
TID_0X020C
524
Callee unreachable tone
TID_0X020D
525
Callee out of service tone
TID_0X020E
526
Service not provided tone
TID_0X020F
527
TWC warning tone (2kHz)
TID_0X0211
529
Mobile call-in restriction tone
TID_0X0212
530
Mobile call-out restriction tone
TID_0X0213
531
Mobile callee busy tone
TID_0X0214
532
Mobile callee power off tone
TID_0X0216
534
Mobile incoming toll call tone
TID_0X0217
535
Special queue ring back tone
TID_0X0218
536
No CB02SIG button board tone
TID_0X021A
538
Offhook tone
TID_0X021B
539
Caller not active tone
TID_0X021C
540
International incoming toll call tone
TID_0X021D
541
Local incoming call tone
TID_0X021E
542
Local incoming toll call tone
TID_0X021F
543
Change number tone
TID_0X0220
544
Recorded_0
TID_0X0223
547
Reserved_0
TID_0X0224
548
Reserved_1
TID_0X0225
549
Reserved_2
TID_0X0226
550
Release tone
TID_0X0228
552
PIN locked day tone
TID_0X0229
553
PIN locked permanent tone

C-4

TID
Appendix C Tone ID
Parameter value
Tone name
TID_0X022A
554
PIN not changed tone
TID_0X022B
555
Verify call forwarding failure tone

C-5

Appendix D Acronyms and Abbreviations

Abbreviation
Full name
A
AC
Access Code
ACC
Account Card Calling
ACK
Acknowledgement
ACM
Address Complete Message
ADI
Address Incomplete signal
ADPCM
Adaptive Differential Pulse Code Modulation
ALUI
Alarm Unit
AMG
Access Media Gateway
AMI
Alternate Mark Inversion code
AMR
Adaptive Multi-Rate
AN
Access Network
ANI
Automatic Number Identification
ANSI
American National Standard Institute
AS
Application Server
ASN.1
Abstract Syntax Notation One
ASP
Application Server Process
AT
Analog Trunk
ATM
Asynchronous Transfer Mode
B
BAM
Back Administration Module
BFII
Back insert FE Interface Unit
BITS
Building Integrated Timing Supply
BNC
Bayonet-niell-concelman
BRA
Basic Rate Access
BRI
Basic Rate Interface
BSGI
Broadband Signaling Gateway
C
CAS
Channel Associated Signaling

D-1

Abbreviation
Full name
CCB
Call Control Block
CCF
Call Control Function
CCITT
International Telegraph and Telephone Consultative Committee
CDBI
Central Database Board
CF
Call Forwarding services
CFB
Call Forwarding Busy
CFNR
Call Forwarding No Reply
CFU
Call Forwarding Unconditional
CHG
Charging message
CIC
Circuit Identification Code
CKII
Clock Interface Unit
CLI
Calling Line Identification
CLIP
Calling Line Identification Presentation
CLIR
Calling Line Identification Restriction
CN
Core Network
CON
Conference Calling
COT
Continuity Signal
CODEC
Coder-decoder
CPC
Central Processing Board
CPU
Center Processing Unit
CRC
Cyclic Redundancy Check
CS-1R
Capability Set
CSC
Customer Service Center
CTD
Click To Dial
CVT
Circuit Validation Test
D
DB
Data Base
DCL
Digital Channel Link
DCN
Data Communication Network
DDI
Direct-Dialing-In
DDN
Digital Data Network
DN
Directory Number
DOD2
Direct Outward Dialing-2

D-2

Abbreviation
Full name
DP
Detection Point
DPC
Destination Point Code
DSP
Digital Signal Processor
DSS1
Digital Subscriber Signaling No.1
DTMF
Dual-Tone Multi-frequency
E
EC
Echo Cancellation
EID
Equipment Identification
ENUM
E.164 Number URI Mapping
EPII
E1_Pool Interface Unit
ESL
Ethernet Subscriber Line
F
FCCU
Fixed Calling Control Unit
FCSU
Fixed Calling Control Unit and Signaling process Unit
FE
Fast Ethernet
FIFO
First In First Out
FPH
Free Phone
FSK
Frequency Shift Keying
G
GAP
Call Gapping
GK
Gatekeeper
GPS
Global Positioning System
GRS
Circuit Group Reset message
GSM
Global System for Mobile Communications
GT
Global Title translation
GUI
Graphic User Interface
GW
Gate Way
H
HSCI
Hot-Swap and Control unit
I
IAD
Integrated Access Device
IAI
Initial Address Message with Information
IAM
Initial Address Message

D-3

Abbreviation
Full name
ID
Identification
IEC
International Electrotechnical Commission
IEEE
Institute of Electrical and Electronics Engineers
IETF
Internet Engineering Task Force
IFMI
IP Forward Module
iGWB
iGateway Bill
IN
Intelligent Network
INAP
Intelligent Network Application Protocol
INtess
Intelligent Service System
IP
Intelligent Peripherals; Internet Protocol
IPN
Internet Personal Number
ISDN
Integrated Services Digital Network
ISO
International Standard Organization
ISUP
Integrated Services Digital Network User Part
ITU-T
International Telecommunication Union - Telecommunication

Standardization Sector
IUA
ISDN Q.921-User Adaptation Layer
IVR
Interactive Voice Response
K
KB
Kilobyte
L
LAN
Local Area Network
LE
Local Exchange
M
M2PA
MTP2-User Peer-to-Peer Adaptation Layer
M2UA
Message Transfer Part 2 (MTP2) -User Adaptation Layer
M3UA
Message Transfer Part 3 (MTP3) -User Adaptation Layer
MAC
Media Access Control
MAP
Mobile Application Part
MAS
Mass calling
MFC
Multiple Frequency Control
MG
Media Gateway
MGC
Media Gateway Controller

D-4

Abbreviation
Full name
MGCP
Media Gateway Control Protocol
MGW
Media Gateway
MID
Message Identification
MIDCOM
Middle-box Communications
MML
Man Machine Language
MODEM
Modulator-Demodulator
MRCA
Media Resource Control Unit
MRIA
Media Resource Interface Unit
MRS
Media Resource Server
MSGI
Multimedia Signaling Gateway Unit
MSN
Multiple Subscriber Number
MTA
Multifunctional Terminal Adapter
MTP
Message Transfer Part
MTP2
Message Transfer Part Layer 2
MTP3
Message Transfer Part Layer 3
MuxPDU
Multiplex Sub-layer Protocol Data Unit
MWN
Message Waiting Notification
N
NAS
Network Access Server
NAT
Network Address Translation
NGN
Next Generation Network
NM
Network Management
NMC
Network Management Center
NMF
Network Management Function
NN
Network Node
NP
Number Portability
NT
Network Terminal
NTP
Network Time Protocol
O
OPC
Originating Point Code
OpenEye
OSI
Open System(s) Interconnection
P
D-5

Abbreviation
Full name
PABX
Private Automatic Branch Exchange
PBX
Private Branch Exchange
PCM
Pulse Code Modulation
PDB
Power Distribution Box
PDU
Protocol Data Unit; Protocol Data Unit
PID
Process Identification
PPS
Pre-Paid Service
PRA
Primary Rate Access
PRI
Primary Rate Interface
PSTN
Public Switched Telephone Network
PTS
Portal Service
Q
QCIF
Quarter Common Intermediate Format
QoS
Quality of Service
R
RACF
Remote Activated Call Forwarding
RADIUS
Remote Authentication Dial in User Service
RAS
Registration, Admission and Status
RM
Resource Management
RTCP
Real-time Transport Control Protocol
RTP
Real-time Transport Protocol
S
SAM
Subsequent Address Message
SAO
Subsequent Address Message with One signal
SAU
Signaling Access Unit
SCCP
Signaling Connection and Control Part
SCEP
Service Creation Environment Point
SCF
Service Control Function
SCMG
SCCP Management
SCN
Switched Circuit Network
SCP
Service Control Point
SCTP
Signaling Control Transmission Protocol
SDF
Service Data Function

D-6

Abbreviation
Full name
SDP
Service Data Point
SDU
Service Data Unit
SG
Signaling Gateway
SIGTRAN
Signaling Transport
SIP
Session Initiation Protocol
SIUI
System Interface Unit
SLC
Signaling Link Code
SLS
Signaling Link Selection Code
SMAF
Service Management Access (Agent) Function
SMAP
Service Management Access Point
SMC
Service Management Center
SMCP
Service Management Control Point
SMF
Service Management Function
SMP
Service Management Point
SMSF
Service Management Sub-Function
SMUI
System Management Unit
SNTP
Simple Network Time Protocol
SP
Signaling Point
SPC
Board; Signaling Point Code
SQL
Structured Query Language
SRF
Service Resource Function
SS
Supplementary Service
SS7
Signaling System Number 7
SSAP
Service Switching Access Point
SSCP
Service Switching and Control Point
SSF
Service Switching Function
SSN
Sub-System Number
SSP
Service Switching Point
STP
Signaling Transfer Point
STUN
Simple Traversal of UDP Through Network Address Translators
T
TA
Terminal Adapter
TCAP
Transaction Capabilities Application Part

D-7

Abbreviation
Full name
TCP
Transport Control Protocol
TDM
Time Division Multiplex(ing)
TDP
Trigger Detection Point
TID
Termination Identification
TMG
Trunk Media Gateway
TOS
Type of Service
TP
Terminal Portability
TRIP
Telephone Route Information Protocol
TUP
Telephone User Part
U
UC
Unified Communication
UCS
Universal Card Service
UDP
User Datagram Protocol
UMG
Universal Media Gateway
U-NICA
Universal Network Intelligent Core Architecture
U-Path
UPT
Universal Personal Telecommunication
UPWR
Universal Power
URL
Universal Resource Locator
U-SYS
You Design Your System
UTC
Universal Time Coordinated
V
V5UA
V5.2-User Adaptation Layer
VIG
Video Interworking Gateway
VM
Voice Mailbox
VoIP
Voice Over IP
VOT
Televoting
VPN
Virtual Private Network
W
WAC
Wide Area Centrex;
WAN
Wide Area Network
WS
Work Station
WWW
World Wide Web

D-8

Abbreviation
Full name
X
xDSL
x Digital Subscriber Line
XML
Extensible Markup Language

D-9

SoftX3000 Operation Manual-Configuration Guide

Загружено:

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

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

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

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

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

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

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

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

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

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

SoftX3000 Operation Manual-Configuration Guide

Загружено:

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

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

Chapter 1 Overview of Configuration Guide .................................................

1.1 General Configuration Procedure ...........................................................

Chapter 2 Configuring Equipment Information ............................................

2.1 Related Concepts ...................................................................................

2.3.5 Setting CKII Clock Configuration ...................................................

Chapter 3 Configuring Office Data .................................................................

3.1 Related Concepts ...................................................................................

Chapter 4 Configuring Charging Data ...........................................................

4.1 Related Concepts ...................................................................................

4.4.1 Overview ........................................................................................

Chapter 5 Configuring MG Data .....................................................................

5.1 Related Concepts ...................................................................................

Chapter 6 Configuring MRS Data ...................................................................

6.1 Related Concepts ...................................................................................

6.1.2 MRS Networking Mode ..................................................................

Chapter 7 Configuring Protocol Data ............................................................

7.1 Related Concepts ...................................................................................

Chapter 8 Configuring Signaling Data ...........................................................

8.1 Related Concepts ...................................................................................

8.8 Configuring V5 Interface Data ................................................................

Chapter 9 Configuring Routing Data .............................................................

9.1 Related Concepts ...................................................................................

Chapter 10 Configuring Trunk Data ...............................................................

10.1 Related Concepts .................................................................................

10.3.2 Adding Virtual IP List (Optional) ................................................... 10-21

Chapter 11 Configuring Number Analysis Data ............................................

11.1 Related Concepts .................................................................................

Chapter 12 Configuring Subscriber Data ......................................................

12.1 Related Concepts .................................................................................

12.3.5 Adding a PRA Subscriber ............................................................

Chapter 13 Configuring Centrex Data............................................................

13.1 Related Concepts .................................................................................

Chapter 14 Configuring Call Barring Data .....................................................

14.1 Related Concepts .................................................................................

Chapter 15 Configuring IN Service Data ........................................................

15.1 Related Concepts .................................................................................

15.6.1 Overview ......................................................................................

Chapter 16 Configuring UC Service Data ......................................................

16.1 Related Concepts .................................................................................

Chapter 17 Configuring Network Management Data ....................................

17.1 Background Knowledge .......................................................................

17.2.3 Adding Call Gap Control ..............................................................

Chapter 18 Configuring Other Data ...............................................................

18.1 Related Concepts .................................................................................

18.6.1 Overview ......................................................................................

Appendix A Configuring SNTP Client ............................................................

A.1 Overview ................................................................................................

Appendix B Basic Principles of CRG Charging ............................................

B.1 Overview ................................................................................................

Appendix C Tone ID .........................................................................................

Appendix D Acronyms and Abbreviations ....................................................

U-SYS SoftX3000 SoftSwitch System

Huawei Technologies Proprietary

U-SYS SoftX3000 SoftSwitch System

Huawei Technologies Co., Ltd.

Huawei Technologies Proprietary

Copyright 2005 Huawei Technologies Co., Ltd.

All Rights Reserved

, HUAWEI, C&C08, EAST8000, HONET,

, ViewPoint, INtess, ETS, DMC,

TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium,

Huawei Technologies Proprietary

About This Manual

U-SYS SoftX3000 SoftSwitch