UA5000 Configuration Guide PVM CLI V100R017 08 PDF

UA5000 Universal Access Unit
V100R017
Configuration Guide-PVM CLI
Issue 08
Date 2011-11-15
HUAWEI TECHNOLOGIES CO., LTD.

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

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

Copyright © Huawei Technologies Co., Ltd.
Configuration Guide-PVM CLI About This Document
About This Document
Purpose
This document describes how to execute commands to configure the services supported by
theUA5000: VoIP service, ISDN service, FoIP service, and MoIP service. It provides the
networking, service configuration flow, service application example, and related operations of
the services supported by UA5000.
This document is intended for service configuration. It can also be used as a reference by system
maintenance engineers to learn and improve technical knowledge.
Related Versions
The following table lists the product versions related to this document.
Product Name Version
UA5000 V100R017
N2000 BMS V200R011
Intended Audience
The intended audience of this document are:
l Installation and commissioning engineer

l System maintenance engineer
l Data configuration engineer
Organization
This document describes the configuration of the UA5000. Each chapter provides an overview
of the configuration first, and then describes the configuration flow and provides configuration
examples (only some chapters provide configuration examples), and then describes the basic
operations in detail.
Issue 08 (2011-11-15) Huawei Proprietary and Confidential ii

For the readers who are familiar with the product, it is recommended that you read the
configuration example directly. For the readers who are not familiar with the product, it is
recommended that you read the basic operations first.
The following table describes the contents of this document.
Chapter… Describes…
1 Managing the License The license feature and the procedure for configuring the
license.
2 Configuring the The mode and procedure for configuring the maintenance
Maintenance Terminal terminal.
3 CLI Operation Basics The CLI operation features of the UA5000 and the basic
operation that can be performed on theUA5000 through the
CLI.
4 Configuring the NMS The mode for connecting the UA5000 to the network
management workstation and the procedure for the
configuration on the UA5000 side.
5 User Management The classification of users and how to add, modify, delete, or
disconnect a user.
6 Device Management How to manage the shelf and the board of the UA5000.
7 Configuring the System The functions of the DSP channel and the method for
DSP Channels maintaining the system DSP resources.
8 Configuring the Clock The method for realizing the clock synchronization and the
operation for configuring the clock of the UA5000.
9 Configuring the MG How to configure an MG interface.

Interface
10 Configuring the VoIP How to configure the VoIP service through the PVMB control
Service board and the A32 service board.
11 Configuring the VAG The example for configuring the VAG service of
Service theUA5000.
12 Configuring the ISDN How to configure the ISDN service through the PVMB
Service control board, DSLD service board, and EDTB interface
board.
13 Configuring the FoIP How to realize the FoIP function through the fax service.
Service
14 Configuring the MoIP How to realize the MoIP function through the modem service.
Service
15 Configuring the R2 How to configure the R2 access.

Access Service
16 Configuring the V5 How to configure the V5 voice service.

Voice Service
Issue 08 (2011-11-15) Huawei Proprietary and Confidential iii

Chapter… Describes…
17 Configuring the SPC How to configure the SPC.
18 Configuring the DDI How to configure the DDI service.

Service
19 Configuring the SDL How to configure the SDL service.

Service
20 Configuring the MTA How to configure the MTA service.

Service
21 Configuring the VFB How to configure the VFB service.

Service
22 Configuring the ATI How to configure the ATI service.

Service
23 Configuring the CDI How to configure the CDI service.

Service
24 Configuring the EPON This topic describes the Ethernet passive optical network
Upstream Transmission (EPON) technology and how to configure the EPON
upstream transmission on the UA5000 MiniMSAN.
25 Configuring the GPON This topic describes the gigabit-capable passive optical
Upstream Transmission network (GPON) technology and describes how to configure
the GPON upstream transmission on the UA5000
MiniMSAN.
26 Configuring the Remote How to configure the remote subtending.

Subtending
27 Configuring the QoS of How to configure the QoS of the voice service.
the Voice Service
28 Configuring the Security How to configure the security of the voice service.
of the Voice Service
29 Configuring the Configuring the Reliability of the Voice Service.

Reliability of the Voice
Service
30 Configuring the Link How to configure the link detection on the UA5000 to ensure
Detection the quick detection and the quick switch of the link.
31 Configuring the This topic provides an overview of the environment

Environment Monitoring monitoring and describes how to configure the environment
monitoring on the UA5000.
32 Configuring the The related operation for configuring the integrated data and
Integrated Data and Voice voice networking of the UA5000.
Networking
Acronym and Abbreviation Acronyms and abbreviations used in the document.
Issue 08 (2011-11-15) Huawei Proprietary and Confidential iv

Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates a hazard with a high level of risk, which if not

avoided, could result in death or serious injury.
DANGER
Indicates a hazard with a medium or low level of risk, which

if not avoided, could result in minor or moderate injury.
WARNING
Indicates a potentially hazardous situation, which if not

avoided, could cause equipment damage, data loss,
CAUTION
performance degradation, or unexpected results.
TIP Indicates a tip that may help you solve a problem or save time.
NOTE Provides additional information to emphasize or supplement

important points of the main text.
General Conventions
Convention Description
Times New Roman Normal paragraphs are in Times New Roman.
Boldface Names of files, directories, folders, and users are in boldface.

For example, log in as user root.
Italic Book titles are in italics.

Courier New Terminal display is in Courier New.
Command Conventions
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 item can be selected.
Issue 08 (2011-11-15) Huawei Proprietary and Confidential v

[ x | y | ... ] Optional alternative items are grouped in square brackets and

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

vertical bars. A minimum of one or a maximum of all items can
be selected.
GUI Conventions
Boldface Buttons, menus, parameters, tabs, window, and dialog titles are
in Boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.
Keyboard Operation
Format Description
Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt
+A means the three keys should be pressed concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means the
two keys should be pressed in turn.
Mouse Operation
Action Description
Click Select and release the primary mouse button without moving
the pointer.
Double-click Press the primary mouse button twice continuously and quickly
without moving the pointer.
Drag Press and hold the primary mouse button and move the pointer
to a certain position.
Issue 08 (2011-11-15) Huawei Proprietary and Confidential vi

Update History
Updates between document versions are cumulative. Therefore, the latest document version
contains all updates made to previous versions.
Updates in Issue 08 (2011-11-15)

Based on issue 07 (2010-10-30), the document is updated as follows:
The following information is modified:
l 9.1 Introduction to the MG Interface
l 9.3 Configuration Example of the MG Interface (the MGCP Protocol)
l 9.4 Adding an MG Interface
l 10.2 Configuration Example of the VoIP Service
l 10.3 Configuration Example of the VoIP Service (in Integrated Upstream Mode)

l 32 Configuring the Integrated Data and Voice Networking

The structure and content of the document are optimized comprehensively so that the document
can better cater to user preferences and guide users.

l 9 Configuring the MG Interface
l 10 Configuring the VoIP Service
l 11 Configuring the VAG Service
l 12 Configuring the ISDN Service
l 13 Configuring the FoIP Service
l 14 Configuring the MoIP Service
l 15 Configuring the R2 Access Service

The following information is added:
10.3 Configuration Example of the VoIP Service (in Integrated Upstream Mode)
Issue 08 (2011-11-15) Huawei Proprietary and Confidential vii


l 24 Configuring the EPON Upstream Transmission
l 25 Configuring the GPON Upstream Transmission
l 31 Configuring the Environment Monitoring

l 9.13 Configuring the Overload Control of the MGC
l 9.14 Configuring the Overload Control of the MG

This is the first release.
Issue 08 (2011-11-15) Huawei Proprietary and Confidential viii

Configuration Guide-PVM CLI Contents
Contents
About This Document.....................................................................................................................ii

1 Managing the License...................................................................................................................1
1.1 Introduction to the License.................................................................................................................................2
1.2 License Principle................................................................................................................................................3
1.3 Configuration Example of the License Application...........................................................................................3
1.4 Configuring the ESN..........................................................................................................................................6
1.5 Configuring the License Server..........................................................................................................................7
2 Configuring the Maintenance Terminal...................................................................................9

2.1 Introduction to the Maintenance Terminal.......................................................................................................10
2.2 Configuring the Terminal Through the Local Serial Port................................................................................11
2.3 Configuring the Terminal Through the Remote Serial Port.............................................................................14
2.4 Configuring the Outband Management Interface.............................................................................................19
2.5 Configuring the Inband Management Interface................................................................................................22
3 CLI Operation Basics..................................................................................................................26

3.1 Introduction to the CLI.....................................................................................................................................27
3.2 CLI Features.....................................................................................................................................................27
3.2.1 Introduction to the Command Mode.......................................................................................................27
3.2.2 Intelligent Matching................................................................................................................................28
3.2.3 Edit Characteristics..................................................................................................................................29
3.2.4 Interaction Characteristics.......................................................................................................................30
3.2.5 Parameter Prompt....................................................................................................................................30
3.2.6 Display Characteristics............................................................................................................................31
3.2.7 Saving and Querying the History Commands.........................................................................................32
3.2.8 CLI Error Prompt.....................................................................................................................................33
3.3 Basic Operation Through CLI..........................................................................................................................33
3.3.1 Obtaining the Online Help Information...................................................................................................33
3.3.2 Switching the Terminal Language...........................................................................................................35
3.3.3 Configuring the System Time..................................................................................................................36
3.3.4 Setting the System Name.........................................................................................................................36
3.3.5 Setting the Terminal Type.......................................................................................................................37
3.3.6 Setting the Timeout Exit Time................................................................................................................37
3.3.7 Locking the Terminal..............................................................................................................................38
Issue 08 (2011-11-15) Huawei Proprietary and Confidential ix

3.3.8 Clearing the Terminal Screen..................................................................................................................39

3.3.9 Querying the Version Information..........................................................................................................39
3.3.10 Querying the CPU Usage of a Board.....................................................................................................40
3.3.11 Testing the Network Status....................................................................................................................40
4 Configuring the NMS.................................................................................................................42

4.1 Introduction to the NMS...................................................................................................................................43
4.2 Configuration Example of an Outband NMS...................................................................................................43
4.3 Configuration Example of an Inband NMS......................................................................................................45
4.4 Configuring the SNMP Agent..........................................................................................................................48
4.4.1 Configuring the Community Name and Read-Write Authority..............................................................48
4.4.2 Enabling Sending the Trap Packet...........................................................................................................49
4.4.3 Configuring the IP Address of the Target Host for the Trap Packet.......................................................49
4.4.4 Configuring the Administrator ID of the Device.....................................................................................50
4.4.5 Configuring the Location of the Device..................................................................................................51
5 User Management........................................................................................................................53
5.1 Introduction to the Operation User...................................................................................................................54
5.2 Adding a User...................................................................................................................................................54
5.3 Modifying the User Attributes..........................................................................................................................56
5.3.1 Changing a User Level............................................................................................................................56
5.3.2 Changing the User Password...................................................................................................................57
5.3.3 Changing the Number of Re-logins.........................................................................................................58
5.3.4 Modifying the Supplementary Information About a User.......................................................................59
5.4 Disconnecting an Online User..........................................................................................................................60
5.5 Deleting a User.................................................................................................................................................61
6 Device Management...................................................................................................................63
6.1 Introduction to the Device................................................................................................................................65
6.2 Adding the Connection Between the Shelves...................................................................................................66
6.3 Setting the Description of a Shelf.....................................................................................................................67
6.4 Resetting a Control Board................................................................................................................................68
6.5 Adding a Service Board....................................................................................................................................69
6.6 Deleting a Service Board..................................................................................................................................70
6.7 Resetting a Service Board.................................................................................................................................71
6.8 Prohibiting a Service Board..............................................................................................................................71
7 Configuring the System DSP Channels..................................................................................74

7.1 Introduction to the System DSP Channels.......................................................................................................75
7.2 Configuring the Attributes of the DSP Channel...............................................................................................75
7.3 Configuring the Number of the Globally Shared DSP Channels.....................................................................77
7.4 Configuring the Number of DSP Channels in the DSP Resources Reserved for the VAG.............................79
7.5 Prohibiting the DSP Channel............................................................................................................................80
8 Configuring the Clock................................................................................................................83
Issue 08 (2011-11-15) Huawei Proprietary and Confidential x

8.1 Introduction to the Clock..................................................................................................................................84

8.2 Configuration Example of a Clock Source.......................................................................................................85
8.3 Configuring the Reference Clock Source.........................................................................................................87
8.4 Setting the Clock Source Priority.....................................................................................................................88
9 Configuring the MG Interface..................................................................................................90

9.1 Introduction to the MG Interface......................................................................................................................92
9.2 Configuration Example of the MG Interface (the H.248 Protocol)..................................................................92
9.3 Configuration Example of the MG Interface (the MGCP Protocol)................................................................95
9.4 Adding an MG Interface...................................................................................................................................97
9.5 Configuring the IP Address Pool....................................................................................................................102
9.6 Configuring the Attributes of the MG Interface (the H.248 Protocol)...........................................................103
9.7 Configuring the Attributes of the MG Interface (the MGCP Protocol)..........................................................109
9.8 Configuring the Software Parameters of an MG Interface (the H.248 Protocol)...........................................112
9.9 Configuring the Software Parameters of an MG Interface (the MGCP Protocol).........................................114
9.10 Configuring the Ringing Mode of an MG Interface.....................................................................................115
9.11 Configuring Digitmaps of the MG Interface (the H.248 Protocol)..............................................................117
9.12 Configuring Digitmaps of the MG Interface (the MGCP Protocol).............................................................119
9.13 Configuring the Overload Control of the MGC...........................................................................................121
9.14 Configuring the Overload Control of the MG..............................................................................................122
9.15 Enabling an MG Interface............................................................................................................................124
10 Configuring the VoIP Service...............................................................................................126

10.1 Introduction to the VoIP Service..................................................................................................................128
10.2 Configuration Example of the VoIP Service................................................................................................128
10.3 Configuration Example of the VoIP Service (in Integrated Upstream Mode).............................................135
10.4 Configuring the Standalone Service.............................................................................................................142
10.5 Configuring the System Parameters.............................................................................................................144
10.6 Configuring the POTS Subscriber Data and Port Attributes........................................................................145
10.7 Configuring the QoS IP Precedence.............................................................................................................149
10.8 Configuring the QoS VLAN Priority...........................................................................................................152
10.9 Separating the Signaling IP Address from the Media IP Address................................................................153
10.10 Enabling the Voice Quality Enhanced Function........................................................................................154
11 Configuring the VAG Service...............................................................................................157

11.1 Introduction to the VAG Service..................................................................................................................158
11.2 Configuration Example of the VAG Service................................................................................................158
11.3 Configuring the TID Profile of the VAG.....................................................................................................163
12 Configuring the ISDN Service..............................................................................................167

12.1 Introduction to the ISDN Service.................................................................................................................168
12.2 Configuration Example of the P2P ISDN BRA Service..............................................................................169
12.3 Configuration Example of the P2MP ISDN BRA Service...........................................................................174
12.4 Configuration Example of the ISDN PRA Service (When the EDTB Service Board Is Used)...................179
12.5 Configuring the SIGTRAN Protocol Stack..................................................................................................183
Issue 08 (2011-11-15) Huawei Proprietary and Confidential xi

13 Configuring the FoIP Service................................................................................................187

13.1 Introduction to the FoIP Service...................................................................................................................189
13.2 Configuring the V2 Transparent Transmission Flow...................................................................................190
13.3 Configuring the Selfswitch Transparent Transmission Flow.......................................................................192
13.4 Configuring the V2 T.38 Flow.....................................................................................................................194
13.5 Configuring the Selfswitch T.38 Flow.........................................................................................................196
13.6 Configuring the V3 Flow..............................................................................................................................198
13.7 Configuring the V5 Flow..............................................................................................................................199
13.8 Configuring the High-Speed Fax..................................................................................................................201
13.9 Configuring the High-Low Speed Selfswitch Fax.......................................................................................203
13.10 Configuring the Fax Transmission Parameters..........................................................................................205
13.11 Configuring the Fax Training Parameters..................................................................................................206
14 Configuring the MoIP Service..............................................................................................208

14.1 Introduction to the MoIP Service.................................................................................................................209
14.2 Configuring the MoIP Service......................................................................................................................209
14.3 Configuring the Modem Transmission Parameters......................................................................................210
15 Configuring the R2 Access Service......................................................................................212

15.1 Introduction to the R2 Access Service.........................................................................................................213
15.2 Configuration Example of the R2 Access Service.......................................................................................214
15.3 Adding an R2 Profile....................................................................................................................................219
15.4 Configuring the Adaptation Data of the R2 Profile .....................................................................................220
15.4.1 Configuring the R2 Address Receiving Attributes..............................................................................220
15.4.2 Configuring the R2 Address Sending Attributes.................................................................................221
15.4.3 Configuring the R2 Profile Attributes.................................................................................................222
15.4.4 Configuring the R2 Line Signaling Attributes....................................................................................222
15.4.5 Configuring the R2 Register Signaling Attributes..............................................................................223
15.5 Loading an R2 Signaling Configuration File...............................................................................................224
16 Configuring the V5 Voice Service........................................................................................226

16.1 Introduction to the V5 Voice Service...........................................................................................................227
16.2 Configuration Example of the V5 Voice Service.........................................................................................228
16.3 Configuring a PSTN Subscriber...................................................................................................................233
16.4 Configuring an ISDN Subscriber.................................................................................................................234
16.5 Blocking a V5 Service Port..........................................................................................................................236
16.6 Configuring the Loopback for a V5 Service Port.........................................................................................236
17 Configuring the SPC...............................................................................................................238

17.1 Introduction to the SPC................................................................................................................................239
17.2 Configuration Example of the Common SPC..............................................................................................240
17.3 Configuration Example of the U Interface Transparent Transmission.........................................................242
18 Configuring the DDI Service................................................................................................246

18.1 Introduction to the DDI Service...................................................................................................................247
Issue 08 (2011-11-15) Huawei Proprietary and Confidential xii

18.2 Configuration Example of the DDI Service.................................................................................................248
19 Configuring the SDL Service................................................................................................252

19.1 Introduction to the SDL Service...................................................................................................................253
19.2 Configuration Example of the Normal SDL Service....................................................................................253
20 Configuring the MTA Service...............................................................................................258

20.1 Introduction to the MTA Service..................................................................................................................259
20.2 Configuration Example of the MTA Service...............................................................................................259
21 Configuring the VFB Service................................................................................................263

21.1 Introduction to the VFB Service...................................................................................................................264
21.2 Configuration Example of the VFB Service.................................................................................................264
22 Configuring the ATI Service.................................................................................................268

22.1 Introduction to the ATI Service....................................................................................................................269
22.2 Configuration Example of the 2-Wire/4-Wire VF and E&M Trunk Service Transparent Transmission
..............................................................................................................................................................................269
22.3 Configuration Example of the Hotline Service on the E&M Trunk Interface.............................................272
23 Configuring the CDI Service.................................................................................................275

23.1 Introduction to the CDI Service....................................................................................................................276
23.2 Configuration Example of the Z Interface Extension Service......................................................................276
23.3 Configuration Example of the PBX-Bothway Service.................................................................................279
24 Configuring the EPON Upstream Transmission..............................................................282

24.1 Introduction to the EPON Upstream Transmission......................................................................................283
24.2 Configuration Example of the EPON Upstream Transmission....................................................................283
24.3 Querying the Attributes of the Ports on the EP1A Board.............................................................................290
24.4 Querying the Statistics of the Ports on the EP1A Board..............................................................................291
25 Configuring the GPON Upstream Transmission..............................................................292

25.1 Introduction to the GPON Upstream Transmission.....................................................................................293
25.2 Configuration Example of the GPON Upstream Transmission...................................................................293
25.3 Querying the Attributes of the Ports on the GP1A Board............................................................................300
25.4 Querying the Statistics of the Port on the GP1A Board...............................................................................301
26 Configuring the Remote Subtending..................................................................................304

26.1 Introduction to the Remote Subtending........................................................................................................305
26.2 Configuration Example of the E1 Subtending..............................................................................................305
27 Configuring the QoS of the Voice Service.........................................................................311

27.1 Introduction to the Voice Service QoS.........................................................................................................312
27.2 Configuration Example of the QoS Test Task..............................................................................................312
28 Configuring the Security of the Voice Service..................................................................314

28.1 Introduction to the Voice Service Security...................................................................................................315
28.1.1 Registration Process When the H.248 Protocol Is Used.....................................................................315
28.1.2 Registration Process When the MGCP Protocol Is Used....................................................................316
Issue 08 (2011-11-15) Huawei Proprietary and Confidential xiii

28.2 Configuring the Device Authentication........................................................................................................318

28.2.1 Configuring the Device Authentication (the H.248 Protocol).............................................................318
28.2.2 Configuring the Device Authentication (the MGCP Protocol)...........................................................320
29 Configuring the Reliability of the Voice Service..............................................................323

29.1 Introduction to the Voice Service Reliability...............................................................................................324
29.2 Configuring the Dual Homing......................................................................................................................325
29.2.1 Configuring the Dual Homing (the H.248 Protocol)...........................................................................325
29.2.2 Configuring the Dual Homing (the MGCP Protocol).........................................................................326
29.3 Configuring the Standalone Service.............................................................................................................327
29.4 Configuring an Emergency Channel............................................................................................................328
29.5 Configuring the Separation Between the Signaling Stream and the Media Stream.....................................329
30 Configuring the Link Detection...........................................................................................331

30.1 Introduction to the Link Detection...............................................................................................................332
30.2 Configuration Example of the ARP Link Detection....................................................................................332
30.3 Configuration Example of the BFD Link Detection....................................................................................335
30.4 Configuration Example of the ETH_OAM Layer 2 Link Detection............................................................339
31 Configuring the Environment Monitoring.........................................................................344

31.1 Introduction to the Environment Monitoring...............................................................................................346
31.2 Configuration Example of the ESC..............................................................................................................347
31.3 Configuration Example of the Fan Monitoring............................................................................................351
31.4 Configuration Example of the Power Monitoring........................................................................................353
31.5 Configuration Example of the Universal Power Monitoring.......................................................................356
31.6 Adding an EMU............................................................................................................................................358
31.7 Setting the ESC Analog Parameters.............................................................................................................359
31.8 Setting the ESC Digital Parameters..............................................................................................................361
31.9 Configuring the Fan Alarm Reporting..........................................................................................................362
31.10 Setting the Fan Speed Adjustment Mode...................................................................................................363
31.11 Setting the Fan Speed.................................................................................................................................364
31.12 Setting the Power Supply Parameters.........................................................................................................365
32 Configuring the Integrated Data and Voice Networking................................................371

32.1 Networking...................................................................................................................................................373
32.2 Prerequisites..................................................................................................................................................373
32.3 Data Plan (IPM)............................................................................................................................................374
32.4 Data Plan (PVM)..........................................................................................................................................375
32.5 Configuration Procedure (IPM)....................................................................................................................376
32.6 Configuration Procedure (PVM)..................................................................................................................380
32.7 Verification...................................................................................................................................................382
A Acronyms and Abbreviations................................................................................................383
Issue 08 (2011-11-15) Huawei Proprietary and Confidential xiv

Configuration Guide-PVM CLI 1 Managing the License
1 Managing the License
About This Chapter
The license function can control the function entries and resource entries of the UA5000. To
ensure that the required service on theUA5000 can be activated and accessed, you must
implement the management of the license functions.
1.1 Introduction to the License
The license function can control the function entries and resource entries of the UA5000. The
prerequisite for using the license function normally is specifying the functions of and relations
between the license server, license file, function entries, and resource entries.
1.2 License Principle
The UA5000 adopts the network license scheme to manage and control the license.
1.3 Configuration Example of the License Application
Configure the license equipment serial number (ESN) and specify the license server for the
UA5000 so that the UA5000 and license server can communicate normally, and theUA5000
supports the controlled features normally.
1.4 Configuring the ESN
The ESN uniquely identifies a device on the license server. Only after the UA5000 is configured
with an ESN, the license server can identify the device.
1.5 Configuring the License Server
Each UA5000 corresponds to a license file. This license file is saved on the license server which
manages the license functions. Configure the IP address of the license server of the UA5000 and
the TCP port number used for the communication between the UA5000 and the license server.
Thus, the UA5000 and the license server can communicate with each other.
Issue 08 (2011-11-15) Huawei Proprietary and Confidential 1

1.1 Introduction to the License

The license function can control the function entries and resource entries of the UA5000. The
prerequisite for using the license function normally is specifying the functions of and relations
between the license server, license file, function entries, and resource entries.
Service Description
With the license function enabled, the license server performs license control on the function
entries and the resource entries supported by the UA5000 to provide individualized services for
users.
Service Specifications
The controlled features are the features that are controlled through the license. These features
are unavailable without authorization. Such controlled features include function entries and
resource entries.
l A function entry refers to the entry whose license is controlled based on the function.
l A resource entry refers to the entry whose license is controlled based on the number.
The controllable function entries and resource entries of the UA5000 include the following:
l Calling feature
– Number of PSTN subscribers
– Number of BRA subscribers
– Number of PRA subscribers
l SPC service
– Number of SPCs
l Interface feature
– Number of V5 interfaces
– Number of H248 interfaces
– Number of MGCP interfaces
– Number of R2 subscribers
l EMM control power
– Number of EMM control power supplies
l MG property
– T38 coding and decoding function
– G723 and G729 coding and decoding function
– 2198 redundancy function
– Dual homing function of the H248 interface
– Standalone function of the H248 interface
– Dual homing function of the MGCP interface
– Dual homing function of L2UA

NOTE
l If you need to use the license function supported by the UA5000, consider the installation of the license
server in network planning.
l It is recommended that you install the software of the license server on the same computer with the
software of the network management system (NMS) server. If the NMS server does not exist, install
one license server in the network.
1.2 License Principle

The UA5000 adopts the network license scheme to manage and control the license.
License Function Principle

l When the license server is deployed in a network, the license server can be installed on the
same computer with the NMS server, but the two servers are different. The license server
can also be installed on a separate server. Each multi-service access node (MSAN) device
functions as a license client. The license server manages the licenses of all the clients in a
centralized manner.
l In the management range of each license server, each product has one license file.
Generally, a management range can be a district or a city. The license file is stored on the
license server. The license file defines the product resources controlled by the license. One
license server can manage multiple products. Hence, multiple license files can be stored
on one license server.
License Implementation Principle

l In the system initialization process of the UA5000, each service module must register their
controlled resource entries and function entries. After the system runs in the normal state,
based on the registration information, the management module of a license client obtains
the authorization information about the license controlling entries of the device from the
license server.
l When you configure a service module through the command line or the NMS, the device
checks whether the resource entries of the service module are overloaded or the function
entries of the service module are authorized.
– For license-controlled resource entries, if the resource entries are overloaded, the system
terminates the service configuration and prompts that the license resources are
insufficient.
– For license-controlled function entries, if the function entries are not authorized, the
system prompts you that the functions are unauthorized.
– If the resource entries are not overloaded or the function entries are authorized, the
system allows you to continue the service configuration.
– For a license-controlled resources entry, the license resources applied for the service
module are released when the service configuration is deleted.
1.3 Configuration Example of the License Application

Configure the license equipment serial number (ESN) and specify the license server for the
UA5000 so that the UA5000 and license server can communicate normally, and theUA5000
supports the controlled features normally.

Prerequisite
l The network devices and the lines must be normal.
l All boards of the UA5000 must be normal.
l The license function must be enabled.
Networking
Figure 1-1 shows the example network for configuring the license application.
The license function is enabled on the UA5000. The license server is installed on the same
computer as the NMS server (N2000 BMS). The license management tool installed on the N2000
client configures and manages the license file. UA5000_A communicates with the license server
through port 0/5/0. The TCP port number is 10010.
Figure 1-1 Example network for configuring the license application

N2000 BMS&License Server
100.100.100.1/24
N2000 Client
60.60.60.2/24 Router
60.60.60.1/24
......
UA5000_A UA5000_B UA5000_N
Data Plan
Table 1-1 provides the data plan for configuring the license application.
Table 1-1 Data plan for configuring the license application
Item Data
License server IP address: 100.100.100.1/24

Item Data
TCP port number: 10010
UA5000_A IP address of the layer 3 interface: 60.60.60.1/24
Router IP address of the port connected to UA5000_A: 60.60.60.2/24
NOTE
l The configuration at the UA5000 side is the same. This section uses the configuration of UA5000_A
as an example.
l This topic describes only the configuration at the device side. For details on how to configure the license
server, see the related configuration manual of the license server.
Configuration Flowchart
Figure 1-2 shows the flowchart for configuring the license application.
Figure 1-2 Flowchart for configuring the license application
Start
Configure the ESN
Specify the license server
Save the data
End
Procedure
Step 1 Configure the equipment serial number (ESN).
NOTE
At the license server side, you need to add the ESN of the device to the license server, and add the function
entries and resource entries for the device.
huawei(config)#license esn 60.60.60.1
Step 2 Specify the license server.

huawei(config)#license server ipaddress 100.100.100.1 tcpport 10010
Step 3 Save the data.

huawei(config)#save
----End
Result
After the configuration, run the display license info command to check whether the
communication between the device and the license server is normal. UA5000_A is initialized,
and each service module can register the controlled resource entries or function entries.
NOTE
The license does not take effect immediately after it is configured.

By default, the license takes effect 15-20 minutes after it is configured successfully. After configuring the
license, if you run the save command to save the configuration, and then run the reset command to reset
the device, the license takes effect immediately after the system resets.
1.4 Configuring the ESN

The ESN uniquely identifies a device on the license server. Only after the UA5000 is configured
with an ESN, the license server can identify the device.
Context
l The ESN of the UA5000 must be an existing IP address in the IP address pool. You can
run the ip address command to add the IP address to the IP address pool.
l After adding the ESN for the UA5000, you need to add the ESN of the device to the license
server, and add the function entries and resource entries for the device.
Procedure
Step 1 Run the license esn command to configure the ESN for the device.
Step 2 Run the display license info command to query the basic information about the license.
----End
Example
To configure the ESN, do as follows:
huawei(config)#license esn 60.60.60.1
huawei(config)#display license info
License switch: enable
ESN: 60.60.60.1
IP address of the first server: 100.100.100.1
IP address of the second server: 200.200.200.1
Communication status: abnormal
License status: unregistered

NOTE
l When the upper layer device is disconnected, the communication status of the license client is abnormal.
The license status of the license client is unregistered. In this case, the controlled resources cannot be
configured and the controlled function cannot be enabled.
l When the related configuration is complete in the network, the communication status of the license client
is normal. The license status of the license client is registered. In this case, new controlled resources can be
configured and controlled functions can be enabled within the management range of the license.
Related Operation
Table 1-2 lists the related operation for configuring the ESN for the device.
Table 1-2 Related operation for configuring the ESN for the device
To… Run the Command...
Configure the license server license server
1.5 Configuring the License Server

Each UA5000 corresponds to a license file. This license file is saved on the license server which
manages the license functions. Configure the IP address of the license server of the UA5000 and
the TCP port number used for the communication between the UA5000 and the license server.
Thus, the UA5000 and the license server can communicate with each other.
Context
l The IP address of the license server and the TCP port number must be the same as the data
in the actual network plan.
l When the IP address of the license server and the TCP port number change, you need to
re-configure the device.
l Two IP addresses of the license server can be configured at the device side. The two IP
addresses must be different from each other. Only one TCP port number can be configured
at the device side.
Procedure
Step 1 Run the license server command to configure the license server.
Step 2 Run the display license info command to query the basic information about the license.
----End
Example
To configure the IP address of license server 1 as 10.10.10.1, the IP address of license server 2
as 20.20.20.1, and TCP port number as 1024, do as follows:
huawei(config)#license server ipaddress 10.10.10.1 20.20.20.1 tcpport 1024
huawei(config)#display license info
Special license switch: disable
Basic license switch:
enable

ESN: 10.71.55.192
IP address of the first server: 10.10.10.1
IP address of the second server: 20.20.20.1
Communication status: normal
License status: registered
NOTE
l When the upper layer device is not connected, the communication status of the license client is abnormal.
The license status of the license client is unregistered. In this case, the controlled resources cannot be
configured and the controlled function cannot be enabled.
l When the related configuration is complete in the network, the communication status of the license client
is normal. The license status of the license client is registered. In this case, new controlled resources can be
configured and controlled functions can be enabled within the management range of the license.
Related Operation
Table 1-3 lists the related operation for configuring the license server.
Table 1-3 Related operation for configuring the license server

To... Run the Command...
Configure the ESN license esn

Configuration Guide-PVM CLI 2 Configuring the Maintenance Terminal
2 Configuring the Maintenance Terminal
About This Chapter
This topic describes the different maintenance modes of theUA5000 through the maintenance
terminal.
2.1 Introduction to the Maintenance Terminal

Introduction to the maintenance terminal includes the different maintenance modes of the
UA5000 through a maintenance terminal and the features of different maintenance modes.
2.2 Configuring the Terminal Through the Local Serial Port
Connect the serial port on the PC to the UA5000 directly. Then, log in to the UA5000 CLI system
through the HyperTerminal of the Widows OS to maintain and manage the device locally.
2.3 Configuring the Terminal Through the Remote Serial Port
Connect the serial port on the PC to the UA5000 remotely. Then, log in to the UA5000 CLI
system through the HyperTerminal of the Windows OS to maintain the device remotely.
2.4 Configuring the Outband Management Interface
After the outband management interface is configured successfully, you can use the PC to log
in to the UA5000 through the outband management interface of the UA5000 for maintenance
and management.
2.5 Configuring the Inband Management Interface
This topic describes how to log in to the UA5000 through the inband management interface of
the UA5000 for maintenance and management. This example considers the PVMB control board
as an example. The configuration of the PVMD control board is the same as the configuration
of the PVMB control board. Therefore, the configuration of the PVMD control is not described
here.

2.1 Introduction to the Maintenance Terminal

Introduction to the maintenance terminal includes the different maintenance modes of the
UA5000 through a maintenance terminal and the features of different maintenance modes.
You can maintain the UA5000 Universal Access Unit (the UA5000) through the maintenance
terminal in the command line interface (CLI) mode. The configuration of the maintenance
terminal includes the following modes:
l 2.2 Configuring the Terminal Through the Local Serial Port
l 2.3 Configuring the Terminal Through the Remote Serial Port
l 2.4 Configuring the Outband Management Interface
l 2.5 Configuring the Inband Management Interface
Table 2-1 lists the features of different maintenance modes.
Table 2-1 Features of different maintenance modes

Maintenance Description Feature
Mode
Local serial port Uses the embedded The network management software is not
HyperTerminal of the required for the CLI maintenance. Generally,
operating system (OS) to user interface is provided by the software
complete the networking embedded in the OS or by the commercial
for managing and software.
maintaining network
devices.
Remote serial Uses the HyperTerminal In the case of the maintenance through the
port of the OS to complete the remote serial port, you need to connect a
networking for modem to the UA5000 and another modem to
managing and the maintenance terminal, and then connect the
maintaining network maintenance terminal to the UA5000 through
devices. the modem dial-up.
Inband Uses the service channel l Advantages: It uses flexible networking,

management of the UA5000 to and does not require additional networking
interface complete the networking devices, thus saving the networking cost.
for managing and l Disadvantages: The maintenance cannot be
maintaining networking performed if the service channel fails.
devices.
Outband Uses the maintenance l Advantages: It provides reliable device

management network port (ETH) on management channel. The fault can be
interface the control board of the located in time even if the managed device
UA5000 to complete the fails.
networking for l Disadvantages: Additional devices are
managing and required to provide the maintenance
maintaining network channel that is independent of the service
devices. channel.

2.2 Configuring the Terminal Through the Local Serial Port

Connect the serial port on the PC to the UA5000 directly. Then, log in to the UA5000 CLI system
through the HyperTerminal of the Widows OS to maintain and manage the device locally.
Networking
Figure 2-1 shows the example network for configuring the terminal through the local serial port.
Figure 2-1 Example network for configuring the terminal through the local serial port
PVMB
ETH0
ETH1
COM
Local maintenance
serial port cable
UA5000
Figure 2-2 shows the flowchart for configuring the terminal through the local serial port.

Figure 2-2 Flowchart for configuring the terminal through the local serial port
Start
Connect the serial port cable
Start the HyperTerminal
Set the parameters of the

terminal
Set the terminal emulation type
Set the line delay and the

character delay
Log in to the system
End
Procedure
Step 1 Connect the serial port cable.
Use a local maintenance serial port cable to connect the serial port of a PC to the maintenance
serial port (COM) on the control board of the UA5000, as shown in Figure 2-1.
Step 2 Start the HyperTerminal.

1. Set up a connection.
On a PC, choose Start > Programs > Accessories > Communication >
HyperTerminal to display the Connection Description dialog box. Enter the connection
name, and click OK.
NOTE
When you use the HyperTerminal for the first time, the system displays the dialog box of the default
telnet program.
2. Configure the serial port.
Select the standard character terminal or PC terminal serial port that is actually connected
to the UA5000. Assume that it is COM2. Click OK.
Step 3 Set the parameters of the terminal.
In the dialog box that is displayed, set the parameters as follows:

l Baud rate: 9600 bit/s

l Data bits: 8
l Parity: None
l Stop bits: 1
l Data flow control: None
NOTE
l When setting the baud rate, make sure that the baud rate of the HyperTerminal is the same as the baud
rate of the serial port in the system. By default, the baud rate of the serial port is 9600 bit/s.
l The illegible characters may exist in the input information after you log in to the system. This is due
to baud rate inconsistency between the HyperTerminal and the system. In this case, use a different baud
rate to log in to the system. The system supports the baud rates of 9600 bit/s, 19200 bit/s, 38400 bit/s,
57600 bit/s, and 115200 bit/s.
Click OK to display the interface of the HyperTerminal.

Step 4 Set the terminal emulation type.
Choose File > Properties on the HyperTerminal interface. Click the Settings tab in the dialog
box that is displayed. Select VT100 or Auto Detect as the type of terminal emulation, as shown
in Figure 2-3.
Figure 2-3 Type of terminal emulation
Step 5 Set the line delay and the character delay.

Click ASCII Setup. Set the line delay and the character delay for transmitting ASCII to 200 ms.

NOTE
When you paste text to the HyperTerminal, the character delay controls the character transmission speed,
and the line delay controls the interval of transmitting each line. A very short delay may lead to the loss of
characters. If the pasted text is not displayed properly, you can modify the settings.
----End
Result
On the HyperTerminal interface, press Enter. The system displays a message, prompting you
to enter the user name. Enter the user name and the password for user registration (By default,
the super user name is root and password is admin). When the registration is completed
successfully, the prompt of the command line is displayed (such as huawei>), as shown in the
following figure.
If the login fails, click the Hang-up icon and then click the Dial icon. If the login fails again,
check and ensure that the parameter settings and physical connections are correct, and then log
in to the system again.
2.3 Configuring the Terminal Through the Remote Serial

Port
Connect the serial port on the PC to the UA5000 remotely. Then, log in to the UA5000 CLI
system through the HyperTerminal of the Windows OS to maintain the device remotely.
Prerequisite
Connect the public switched telephone network (PSTN) modem on the UA5000 side and the
PC side, before using the serial port for remote maintenance. In this way, you can set up a remote
connection between the PC and the UA5000 through modem dial-up.

The PSTN modem on the UA5000 side is referred to as the called modem. The modem on the
PC side is referred to as the calling modem. The modems must meet the following requirements:
l Both the calling and called modems must comply with the related standards, and support
AT command set.
l The called modem must be an external modem.
l The calling modem can be either a built-in modem or an external modem. For better
compatibility and to facilitate status monitoring, it is recommended that you use an external
modem made by the vendor of the called modem.
Precautions
l After the dial-up and before the connection is set up, pressing any key on the keyboard ends
the call.
l Stop the connection after the remote maintenance. Do not close the HyperTerminal.
Otherwise, certain types of remote modems are always online and the next dial-up fails.
l The following configuration is based on modems of the same type. In actual applications,
you can configure the modems by referring to the related AT command set.
Networking
Figure 2-4 shows the example network for configuring the terminal through the remote serial
port.
Figure 2-4 Example network for configuring the terminal through the remote serial port
Local
maintenance
serial port ETH0
ETH1
cable
COM
Telephone line
The called PVM UA5000
modem
Telephone line
Local
The calling maintenance
modem serial port PC
cable
Figure 2-5 shows the flowchart for configuring the terminal through the remote serial port.

Figure 2-5 Flowchart for configuring the terminal through the remote serial port
Start
Set the parameters of the called modem
Set the parameters of the calling modem
Set up the configuration environment
Start the HyperTerminal
Set the parameters of the terminal
Dial up on the HyperTerminal
End
Procedure
Step 1 Set the parameters of the called modem.
Only three signal lines, namely SD, RD and SG, are used for connecting the UA5000 and the
modem. Therefore, before connecting the modem to the terminal, shield the handshake signals
and flow control signals of the modem.
The configuration of a modem requires an intelligent terminal. The following modem
configuration is based on the HyperTerminal on Windows platform.
1. Connect the serial port of the modem to the port of the maintenance terminal by using the
dedicated cable for the modem, and then power on the system. A driver is not required at
this step.
2. Assume that the modem is connected to the COM2 port. Start the HyperTerminal. Select
Direct to COM2 in the column of Connect using in the dialog box that is displayed. Set
the parameters of the serial port as follows: 9600 bit/s for baud rate, 8 for data bits, 1 for
stop bits, none for parity, and none for flow control.

NOTE
l After the connection, the terminal may not display anything. This is because the display function
of the modem is disabled during the previous configuration. To enable the terminal to display
the latest input and output information, run the AT&F command to restore the default settings
and press Enter.
l Due to the rate limitation of the modem, you can set the baud rate of the maintenance port of the
UA5000 to 9600 bit/s or 19200 bit/s.
3. Check whether the modem works in the normal state.
In the HyperTerminal, run the AT&F command to restore the default settings of the modem.
Check if an OK message is displayed on the screen. If an OK message is displayed, the
modem works in the normal state.
4. In the HyperTerminal, run the following commands:
ATS0=1 //Enable the auto replay function (ringing sound).
AT&D //Ignore the DTR signals.
AT&K0 //Disable the flow control function.
AT&R1 //Ignore the RTS signals.
AT&S0 //Set DSR as high level.

ATEQ1&W
//Disable the modem’s response to the command when executing
the command and saving the configurations.
NOTE
l After executing the previous command, run the AT command to disable the echo function of the
terminal and prohibit it from displaying the execution results.
l You can run the baudrate command to modify the baud rate of the maintenance serial port of
the UA5000. To prevent an extremely high bit rate on the line between the two modems, you can
set AT$MB=9600 (or another value) before running the ATEQ1&W command.
Step 2 Set the parameters of the calling modem.

After power-on, the calling modem can function in the normal state without any configuration.
If a non-standard cable is used to connect the maintenance terminal to the modem, shield the
handshake signals and the flow control signals of the modem before the connection. For details
on this operation, see the settings of the parameters on the called modem.
Step 3 Set up the configuration environment.
Figure 2-4 shows the configuration environment.
1. Connect the called modem.
Insert the telephone line into the LINE port of the called modem. Connect the serial port
of the called modem to the maintenance port COM of the PVM board by using the dedicated
serial port cable for the UA5000. Power on the modem.
2. Connect the calling modem.
In the case of an external modem, insert the telephone line into the LINE port of the calling
modem. Connect the serial port of the calling modem to the serial port of the maintenance
terminal by using the dedicated cable for the modem. Power on the modem.
In the case of a built-in modem, you only need to plug the telephone line into the LINE
port of the calling modem.
Step 4 Start the HyperTerminal.

1. Set up a connection.
Choose Start > Programs > Accessories > Communication > HyperTerminal to display
the Connection Description dialog box. Enter the connection name, and click OK.
2. Configure the serial port.
Select the standard character terminal or PC terminal serial port that is actually connected
to the UA5000. Assume it to be serial COM2. Click OK.
Step 5 Set the parameters of the terminal.
In the dialog box that is displayed, set the parameters as follows:
l Baud rate: 9600 bit/s
l Data bits: 8
l Parity: None
l Stop bits: 1
l Flow control: None
NOTE
l When setting the baud rate, make sure that the baud rate of the HyperTerminal is the same as the baud
rate of the serial port in the system. By default, the baud rate of the serial port is 9600 bit/s.
l There may be illegible characters in the input information after you log in to the system. This is usually
due to baud rate inconsistency between the HyperTerminal and the system. In this case, use a different
baud rate to log in to the system. The system supports the baud rates of 9600 bit/s, 19200 bit/s, 38400
bit/s, 57600 bit/s, and 115200 bit/s.
Click OK to display the interface of the HyperTerminal.

Step 6 Dial up on the HyperTerminal.
l External modem:
To set up a connection with an external modem, select a serial port, and not a modem, from
the Connect Using drop-down list in the HyperTerminal.
On the HyperTerminal interface, run the AT command for dial-up, for example,
ATDTXXXXXXXX. Press Enter. XXXXXXXX represents the telephone number of the
remote modem connected to the host.
For details on the dial-up commands, see the AT command set. For example, ATDT0 W
020XXXXXXXX means to dial "0" for connection with the external line. Wait for the dialing
tone from the exchange, and then dial the telephone number 020XXXXXXXX.
l Built-in modem:
Run the HyperTerminal. Set the called number on the Hyperterminal. Select the modem from
the Connect Using drop-down list. Click Configure in the properties > connect to dialog
box to display the modem properties setting interface. Select Bring up terminal window
after dialing on the Options tab of the properties setting interface. Click OK to confirm the
settings. You need not execute any ATDT commands for dialing.
----End
Result
After the dial-up, the "OH" and "RI" LEDs on the modem connected to the PC are on. The
modem generates a sound, which indicates the progress of the connection. After the connection
is set up, the "CD" LEDs (for carrier detection) on the two modems are on, and the

HyperTerminal interface displays "CONNECT9600 (or 19200)". This indicates that the inter-
modem connection is set up successfully.
If "NO CARRIER" is displayed, the connection fails. Check the hardware connections and the
telephone line. Press Enter, and the command line interface for login is displayed.
After the operation on the remote terminal, run the hang-up command of the HyperTerminal to
disrupt the connection.
2.4 Configuring the Outband Management Interface

After the outband management interface is configured successfully, you can use the PC to log
in to the UA5000 through the outband management interface of the UA5000 for maintenance
and management.
Networking — LAN
Figure 2-6 shows the example network for outband management through the local area network
(LAN) in the Telnet mode.
Figure 2-6 Example network for the outband management through the LAN in the Telnet mode
ETH0
ETH1
COM
PVMB UA5000
LAN
PC PC PC
The UA5000 uses a straight through cable to connect to the LAN. Make sure that the IP address
of the maintenance port on the UA5000 and the IP address of the maintenance terminal are in
the same network segment.
NOTE
You can connect the network port of the maintenance terminal (refers to PC in this example) to the
maintenance port on the control board of the UA5000 to perform the outband management of the device.
In this case, you need to use a crossover cable.
Data Plan — LAN

Table 2-2 provides the data plan for outband management through the LAN in the Telnet mode.

Table 2-2 Data plan for outband management through the LAN in the Telnet mode
Item Data
Maintenance port of the UA5000 IP address: 0.10.20.2/24
Maintenance terminal IP address: 10.10.20.1/24
Networking — WAN
Figure 2-7 shows the example network for outband management through the wide area network
(WAN) in the Telnet mode.
Figure 2-7 Example network for outband management through the WAN in the Telnet mode
PC
LAN
ETH0
ETH1
COM
Router
PVMB UA5000
PC PC
Data Plan — WAN

Table 2-3 provides the data plan for outband management through the WAN in the Telnet mode.
Table 2-3 Data plan for outband management through WAN in the Telnet mode
Item Data
Maintenance port of the UA5000 IP address: 10.10.20.1/24
Figure 2-8 shows the flowchart for configuring the device through the outband management
interface.

Figure 2-8 Flowchart for configuring the device through the outband management interface
Start
Set up the configuration

enviroment
Set the NMS working mode
Set the IP address of the

maintenance network port
Run the Telnet program
End
Procedure
Set up the configuration environment based on actual conditions, as shown in Figure 2-6 or
Figure 2-7.
Step 2 Set the NMS working mode to the outband mode.
huawei(config)#sysman mode outband
Step 3 Set the IP address (namely, the outband IP address) of the maintenance network port.
NOTE
The system supports only one outband IP address. If the outband IP address is already configured by running
the display ip address command, you need to delete the original IP address before adding an IP address
or run the ip modify command to change the outband IP address.
huawei(config)#interface outband
huawei(interface-outband)#ip address 10.10.20.1 255.255.255.0 10.10.20.0
huawei(interface-outband)#display ip address
OutBand:
IPAddress............: 10.10.20.1
SubMask..............: 255.255.255.0
GateWay..............: 10.10.20.0
MacIndex.............: 1
MacAddress...........: 00-E0-FC-EE-DD-05
VlanID...............: --
Step 4 Run the Telnet program.

Choose Start > Run on the maintenance terminal. Enter the command telnet followed by the
IP address of the maintenance port on the UA5000 in the Open address bar. Click OK to run
Telnet (consider the Windows XP OS as an example), as shown in Figure 2-9.

Figure 2-9 Running Telnet
Step 5 Log in to the system.

Users can log in to the system. By default, the super user uses root and admin as the user name
and password respectively. In this case, the system returns the following prompt:
Huawei UA5000 Multi-service Access Module.
Copyright(C) 1998-2007 by Huawei Technologies Co., Ltd.
>>User name:root
>>User password:
----End
Result
After logging in to the system, you can perform the related operations.
2.5 Configuring the Inband Management Interface

This topic describes how to log in to the UA5000 through the inband management interface of
the UA5000 for maintenance and management. This example considers the PVMB control board
as an example. The configuration of the PVMD control board is the same as the configuration
of the PVMB control board. Therefore, the configuration of the PVMD control is not described
here.
Networking — LAN
Figure 2-10 shows the example network for inband management through the local area network
(LAN) in the Telnet mode.

Figure 2-10 Example network for inband management through the LAN in the Telnet mode
LAN
PC1
PC2
ETH0
ETH1
COM PC3
PVMB UA5000
Data Plan—LAN
Table 2-4 provides the data plan for inband management through the LAN in the Telnet mode.
Table 2-4 Data plan for inband management through the LAN in the Telnet mode
Item Data
Inband management interface of the UA5000 IP address: 10.10.20.1/24
Networking—WAN
Figure 2-11 shows the example network for inband management through the wide area network
(WAN) in the Telnet mode.
Figure 2-11 Example network for inband management through the WAN in the Telnet mode
Router PC
ETH0
ETH1
COM
PVMB UA5000

Data Plan—WAN
Table 2-5 provides the data plan for inband management through the WAN in the Telnet mode.
Table 2-5 Data plan for inband management through the WAN in the Telnet mode
Item Data
Inband management interface of IP address: 10.10.20.1/24

the UA5000
Figure 2-12 shows the flowchart for configuring the device through the inband interface in the
Telnet mode.
Figure 2-12 Flowchart for configuring the device through the inband interface in the Telnet
mode
Start
Set up the configuration

environment
Run the Telnet program
End
Procedure
Set up the configuration environment based on actual conditions, as shown in Figure 2-10 or
Figure 2-11.
Step 2 Run the Telnet program.

Choose Start > Run on the maintenance terminal. Enter the telnet command followed by the
IP address of the maintenance network port on the UA5000 in the Open address bar. Click
OK to run Telnet (consider the Windows XP OS as an example), as shown in Figure 2-13.
Figure 2-13 Running Telnet
Step 3 Log in to the system.

Log in to the system. By default, the super user uses root and admin as the user name and
password. In this case, the system displays the following prompt:
>>User name:root
>>User password:
----End
Result
After logging in to the system, you can perform the related operations.

Configuration Guide-PVM CLI 3 CLI Operation Basics
3 CLI Operation Basics
About This Chapter
This topic describes the basic operation on the UA5000 through CLI.
3.1 Introduction to the CLI

Two maintenance modes of the UA5000 are the NMS and the CLI.
3.2 CLI Features
This topic describes the features of the UA5000 CLI mode.
3.3 Basic Operation Through CLI
This topic describes how to maintain and manage the UA5000 through CLI.

3.1 Introduction to the CLI

Two maintenance modes of the UA5000 are the NMS and the CLI.
Service Description
The differences of the two maintenance modes of the UA5000 are as follows:
l The NMS provides a graphical user interface (GUI), and the command line interface (CLI)
provides the maintenance interface for users.
l The networking for maintaining the UA5000 in the CLI mode is simple. You can run the
HyperTerminal or the telnet program of the maintenance terminal to log in to the
UA5000 to maintain it through the CLI.
3.2 CLI Features

This topic describes the features of the UA5000 CLI mode.
3.2.1 Introduction to the Command Mode

This topic describes the classification and features of the CLI, and the switching relation between
the command modes.
Command Mode Classification

The UA5000 supports multiple command modes to implement the hierarchical protection and
to prevent attacks from unauthorized users.
The UA5000 supports the following command modes:
l User mode
l Privilege mode
l Global config mode
Command Mode Features

l Downward compatibility
All the commands that work in the user mode are available in the privilege mode. All the
commands that work in the user mode and the privilege mode are all available in the global
config mode.
l Hierarchical protection
This helps prevent attacks from unauthorized users. The users at different levels can enter
different command modes. Even if users at different levels enter the same command mode,
the executable commands vary.
Command Mode Switching

Figure 3-1 shows how to switch the command modes.

Figure 3-1 Command mode switching
interface pvm frame/slot PVM mode

quit huawei(config-if-pvm-0/5)#
narrow user Narrow user mode

quit huawei(config-narrow-user)#
interface h248 mgid H248 mode

quit huawei(config-if-h248-...)#
interface emu emuid EMU mode

quit huawei(config-if-h302esc-0)#
quit User mode enable Privilege mode config Global config mode
huawei> disable huawei# quit huawei(config)#
test Test mode

quit huawei(config-test)#
esl user
ESL user mode
quit huawei(config-esl-user)#
narrow resource Narrow resource mode

huawei(config-narrow-
quit resource)#
r2 profile profileid R2 mode

huawei(config-r2-0)#
quit
return
3.2.2 Intelligent Matching

The intelligent matching means when you enter an incomplete keyword and press the space bar,
the matching keyword is displayed.
Function
The UA5000 facilitates the operation by supporting the function, where the matching keyword
is displayed when you input an incomplete keyword and press the space bar. For example, for
the enable command, input en or ena (in the common user mode) and press the space bar.
Precaution
If the system does not return the commands after you press the space bar, it indicates the
following:
l An incorrect command is entered. In this case, check the command and enter the correct
command.
For example, when you enter display incorrectly in the privilege mode, you cannot enter
a space.
huawei#dip
l The input keyword conflicts with other keywords.

For example, when you enter dis in the privilege mode, the system cannot find a matching
keyword for it. This is because there are two commands that start with dis: disable and
display.
huawei#dis
3.2.3 Edit Characteristics

You can press the corresponding keys to enter the parameters of command lines and the
keywords.
Function
The CLI provides basic command edit functions. It allows multi-line editing, with a maximum
of 255 bytes for each command.
Specifications
Table 3-1 lists the edit functions.
Table 3-1 Edit functions
Key Function
Common key If the edit buffer is not full, press one of these keys to move the
cursor to the right from its current position.
BackSpace When you press this key, the character before the cursor is
deleted and the cursor moves to the left. The cursor stops when
it reaches the beginning of the command.
Left arrow key ← or Ctrl When you press the key(s), the cursor moves one character to
+A the left.
Right arrow key → or Ctrl When you press the key(s), the cursor moves one character to
+D the right.
Up/Down arrow key ↑↓ When you press one of the keys, the history commands are
displayed. In the case of certain terminals that do not support the
up/down arrow keys, you can press Ctrl+P to select the previous
history command.
Ctrl+U When you press the keys, the characters before the current cursor
are deleted and the cursor moves to the beginning of the line.
Ctrl+K When you press the keys, the characters after the current cursor
are deleted and the cursor moves to the end of the line.
Ctrl+F When you press the keys, a string is searched.
Ctrl+B When you press the keys, the cursor moves to the end of the line.
ESC When you press this key twice, the current entered information
is cancelled.

NOTE
Common keys refer to letter keys, number keys, and punctuation keys.
3.2.4 Interaction Characteristics

When you enter an incomplete command, namely, when you press Enter after the entered
keyword or parameter, the CLI system prompts the subsequent keywords that can be entered
and prompts the parameter type of the keyword.
Function
The UA5000 provides the interaction function of the CLI. In the interactive mode, if you enter
an incomplete command and press Enter, the system prompts the subsequent keyword that can
be input and the parameter type of the keyword. When you input ?, the system prompts the help
information of the command.
Example
To use the CLI interaction mode to run the load program command, do as follows:
huawei#load program
{ xmodem<K>|tftp<K>|ftp<K>|sftp<K> }:
To run the load program command after the interaction mode is disabled, do as follows:
huawei#undo smart
huawei#load program tftp
^
% Incomplete command, and error detected at '^'
After the interaction mode is disabled, enter the command and press Enter. The system directly
runs the command. If the entered command is incomplete, the system prompts an error.
To display the help information provided by the command, enter the keyword switch and
press ?.
huawei#switch ?
---------------------------------------------
Command of user Mode:
---------------------------------------------
language-mode Set language parameter
3.2.5 Parameter Prompt

In the interactive mode, the system prompts the type of the parameter that is to be configured
on the CLI.
Function
In interactive mode, the CLI characters such as <K> and are used to express the parameter
type of a keyword.
Specifications
Table 3-2 lists the meaning of the CLI characters supported by the UA5000.

Table 3-2 Meaning of the CLI characters

Character Meaning
<K> Keyword
<E> Enumeration. Items that follow this character are the available
options.
 ULONG. Information that follows this character is the range of the
value to be entered.
<L> LONG. Information that follows this character is the range of the
value to be entered.
<S> Character string. Information that follows this character is the length
of the character string to be entered.
 IP address
<M> MASK, such as the mask of an IP address.
 MAC address
<H> Hexadecimal number. The system supports the input of "0x". By

default, the system supports decimal numbers.
<D><yyyy-mm-dd> Date
<T><hh:mm:ss> Time
NOTE
The CLI supports the input of hexadecimal numbers; however, if you do not enter "0x" when entering a
hexadecimal number, the system considers the entered number as a decimal number.
3.2.6 Display Characteristics

The CLI system supports the function of pausing the displayed information when there is a lot
of information to be displayed.
Function
When you query information, sometimes the CLI fails to display the information on one screen
because there is a lot of information to be displayed. In this case, you can use the pause function
to view the information displayed on multiple screens.
NOTE
l One screen here refers to one screen displayed by the HyperTerminal software of a PC. One screen contains
24 lines.
l The system supports the function where the screen scrolls upward automatically, that is, the displayed
information cannot be paused. Run the scroll command to enable the auto-scroll function, and run the undo
scroll command to disable the auto-scroll function. By default, the auto-scroll function is disabled.

Specifications
Table 3-3 lists three options for viewing the information when the display is paused.
Table 3-3 Display characteristics

Key Function
Press Q or Ctrl+C when the Suspend the display and execution of the commands.
display is paused.
Press the space bar when the Continue to display the information on the next screen.
display is paused.
Press Enter when the display is Continue to display the information on the next line.
paused.
3.2.7 Saving and Querying the History Commands

The CLI system automatically saves history commands that you enter. You can obtain history
commands saved in the CLI at any time and execute them repeatedly.
Context
By default, a maximum of 10 history commands can be saved for every user in the CLI, and a
maximum of 10 history commands can be queried.
The queried history commands are valid only for the current user. After the user re-logs in, the
history commands are cleared.
Procedure
Step 1 Run the history-command max-size command to set the number of history commands that can
be saved in the command buffer.
Step 2 Run the display history-command command to query history commands.
----End
Example
To set the number of history commands that can be saved in the command buffer to 12, do as
follows:
huawei(config)#history-command max-size 12
huawei(config)#display history-command
--------------------------------------------------
No. Command
--------------------------------------------------
12 display history-command
11 history-command max-size 20
10 display traffic table from-index 0
9 traffic table atm srvcategory cbr tdtype noClpNoScr clp01Pcr 160
priority 6 priority-policy tag-In-Package
8 modify rate table row 128 160

7 display rate table row

6 config
5 quit
4 quit
3 display power environment info
2 emu
1 display power run info
--------------------------------------------------
3.2.8 CLI Error Prompt

When you enter an incorrect command, which cannot be executed by the system, the system
prompts an error.
Function
The system checks the syntax of each command that is entered, and executes the command if it
passes the check. If the command fails to pass the check, the system prompts an error.
Specifications
Table 3-4 lists the common CLI error prompts.
Table 3-4 Common CLI error prompts
Error Prompt Cause
Unknown command This command and keyword cannot be found. The parameter type
is incorrect. The parameter value exceeds the threshold.
Incomplete command The entered command is incomplete.
Too many parameters There are too many entered parameters.
Ambiguous command The entered command is ambiguous.
Parameter error The parameter is wrong and the cursor location indicates where
the error exists.
3.3 Basic Operation Through CLI

This topic describes how to maintain and manage the UA5000 through CLI.
3.3.1 Obtaining the Online Help Information

When you need to query the help information about the current command or commands in the
current mode, you can enter "?" after the command prompt or command keyword. If the matching
information is not found, it indicates that the help list is empty.
Context
The CLI provides the following methods to obtain online help:
l Full help

When you enter ? following the prompt, you can obtain help information about the
current commands that are available.
When you enter ? following a complete keyword, you can obtain help information about
all the commands matching the keyword and the parameters used by the commands.
l Partial help
When you enter ? following an incomplete keyword, you can obtain help information
about the commands matching the incomplete keyword.
Example
To display the help information about all the available commands in global config mode, do as
follows:
huawei(config)#?
---------------------------------------------
Command of config Mode:
---------------------------------------------
ati Enter into ATI command mode
aulaw Set A/u law
board <Group> board command group
cdi Enter into CDI command mode
clock <Group> clock command group
config System config
dns Configure DNS
dsl Enter the dsl mode
dsp <Group> dsp command group
dtmf DTMF parameter configure
e2etrace End to end signalling trace
emu Emu command group
esl Enter ESL(Ethernet Subscriber Line) user command mode
fax FAX parameter configure
fe Config FE Parameter
frame <Group> frame command group
gtcstatistics <Group>gtcstatistics command group
h248statistics H248 message statistic
hwcport HWC port group
info-center <Group> info-center command group
---- More ( Press 'Q' to break ) ----
To display the help information about the commands matching the keyword display, do as
follows:
huawei(config)#display ?
---------------------------------------------
Command of privilege Mode:
---------------------------------------------
alarm Display alarm related information
arp-detect ARP link detect
auth Authentication parameters
backup-server Display backup server configuration
board Command Keyword:
c-channel C-channel
clock Display information about clock source
config System config
current-configuration Current configuration
data Display data synchronization status
detect-group Detect link group
digitmap Digitmap configure
digitmap-timer DMM T timer configure
dns Display DNS information
e2etrace End to end signalling trace
emu Display environment monitor unit(s)
esl The online user information

ETH0-ETH1 Display ETH0-ETH1 port state

To display the help information about the commands matching the keyword d, do as follows:
huawei(config)#d?
---------------------------------------------
Command of config Mode:
---------------------------------------------
dns Configure DNS
dsl Enter the dsl mode
---------------------------------------------
Command of privilege Mode:
---------------------------------------------
debugging Enable system debugging functions
diagnose Change into diagnose mode
disable Turn off privileged mode commands
display Display information
duplicate <Group> duplicate command group
---------------------------------------------
Command of user Mode:
---------------------------------------------
display Display information
Related Operation
Table 3-5 lists the related operation for obtaining online help information.
Table 3-5 Related operation for obtaining online help information
Obtain system help information help
3.3.2 Switching the Terminal Language

The UA5000 system supports two languages by default, which are the local language and general
language. You can select a preferred language as the terminal display language.
Context
The UA5000 supports English and Chinese. English is the default language.
Procedure
Step 1 Run the switch language-mode command to switch from one language to another.
----End
Example
To run the switch language-mode command to switch from one language to another, do as
follows:
huawei(config)#switch language-mode
The current language has been switched to general language

Related Operation
Table 3-6 lists the related operation for switching the terminal language.
Table 3-6 Related operation for switching the terminal language
To... Run the Command... Remarks
Display the terminal language display language This command is

not available for
common users.
3.3.3 Configuring the System Time

The system time of the device can be configured in the following format: hh:mm:ss yyyy-mm-
dd, namely, hour:minute:second year-month-date.
Context
l The system time takes effect immediately after the configuration.
l When you configure the system time, the system checks the time for its validity strictly.
Invalid settings are prohibited. Exercise caution when configuring the leap year and leap
month.
Procedure
Step 1 Run the time command to configure the system time.
Step 2 Run the display time command to query the system time.
----End
Example
To configure the current system time, do as follows:
huawei#time 09:00:00 2007-02-28
huawei#display time
{ <cr>|dst<K>|time-stamp<K> }:
command:
display time
2007-02-28 09:00:06+08:00
3.3.4 Setting the System Name

Set the system name to differentiate various UA5000s.
Context
l By default, the device name is UA5000.
l The new system name takes effect immediately after it is set.

l After the system name is changed, the command line prompt changes to the new name
accordingly.
Procedure
Step 1 Run the sysname command to set the system name.
----End
Example
To name the first UA5000 in the New York office in the USA, do as follows:
huawei(config)#sysname NY_UA5000_A
NY_UA5000_A(config)#
3.3.5 Setting the Terminal Type

Different terminals feature different edit characteristics. The system divides terminals into two
types, namely, standard terminals (ANSI) and VT series terminals so that it is compatible with
most terminals.
Context
l The default terminal type is ANSI.
l Certain terminal tools, such as HyperTerminal, telnet, and neterm, allow you to set the
terminal types. You can use the associated menu to set the terminal emulation type so that
the type of terminal tool is the same as the type of terminal in the system.
Procedure
Step 1 Run the terminal type command to set the terminal type.
Step 2 Run the display terminal type command to query the terminal type that is set.
----End
Example
To set the terminal type as VT100, do as follows:
huawei#terminal type vt100
huawei#display terminal type
The terminal type: VT100
3.3.6 Setting the Timeout Exit Time

Set the timeout exit time. During this time, if the information is not entered on the terminal, the
system allows the terminal to exit the system automatically.
Context
By default, the system allows the terminal to exit the system if the information is not entered on
the terminal for 5 minutes.

Procedure
Step 1 Run the idle-timeout command to set the timeout exit time.
Step 2 Run the display idle-timeout command to query the preset timeout exit time.
----End
Example
To set the timeout exit time to 255 minutes, do as follows:
huawei>idle-timeout 255
huawei>display idle-timeout
The timeout value is set to 255 minutes currently. If there is no input from
terminal during this time, the user will be disconnected
Related Operation
Table 3-7 lists the related operation for setting the timeout exit time.
Table 3-7 Related operation for setting the timeout exit time
Set the timeout exit time to the undo idle-timeout

default value, that is, 120 minutes
3.3.7 Locking the Terminal

Lock the terminal to prevent other users from accessing the terminal by using the name of the
online user.
Context
After a terminal is locked, if you press any button on the terminal, the system prompts you to
enter the password. After entering the correct password, you can operate the terminal.
Procedure
Step 1 Run the terminal hold command to lock the terminal.
----End
Example
To lock the current CLI terminal and then to unlock it, do as follows:
huawei(config)#terminal hold
Hold Password(<=15 chars):
Confirm Password(<=15 chars):
The user terminal has been held
Hold Password(<=15 chars)://Press any key and the system prompts you to enter the
unlocking password.

huawei(config)# //Input the correct password and the system unlocks the
terminal.
Related Operation
Table 3-8 lists the related operation for locking the terminal.
Table 3-8 Related operation for locking the terminal

Unlock the terminal undo terminal hold
3.3.8 Clearing the Terminal Screen

When you need to highlight certain input or output information, you can clear the current display
on the terminal screen. Then, the prompt is displayed on the upper left corner of the screen.
Context
Running the cls command clears only the information that is displayed on the screen, and does
not clear the information in the buffer.
Procedure
Step 1 Run the cls command to clear the terminal screen.
----End
Example
To clear the screen output, do as follows:
huawei>cls
3.3.9 Querying the Version Information

Query the information about the software version of the current system or board.
Context
By running the display version command, you can obtain the version of normal boards only.
You cannot obtain the version of a faulty board by running this command.
Procedure
Step 1 Run the display version command to query the version information.
----End
Example
To query the system version, do as follows:

huawei(config)#display version
UA5000PVMV100R017 RELEASE SOFTWARE

Copyright (c) 1998-2007 by Huawei Technologies Co., Ltd
Uptime is 0 day(s), 15 hour(s), 30 minute(s), 11 second(s)
3.3.10 Querying the CPU Usage of a Board

Query the CPU usage of a board to check whether it exceeds the threshold. When the CPU usage
of the board exceeds the threshold, the system reports an alarm. Attach importance to the alarm.
Procedure
Step 1 Run the display cpu command to query the CPU usage of a board.
----End
Example
To query the CPU usage of the control board, do as follows:
huawei>display cpu 0/5
CPU occupancy: 17%
3.3.11 Testing the Network Status

Check the network connectivity and whether the host is reachable, how to test all the gateways
through which the data packets sent from a host to the destination pass, and how to locate network
faults.
Context
The commands used to test network status include ping and tracert.
l ping is used to check the network connectivity and whether the host is reachable.
l tracert is used to test the gateways through which data packets sent from a host to the
destination pass. tracert can also be used to check the connectivity of a network and locate
faults in the network. The process of running the tracert command is as follows:
– The host sends a packet with the time to live (TTL) of 1 to the destination.
– The gateway returns an Internet Control Message Protocol (ICMP) packet to indicate
the failure in sending the packet due to TTL timeout.
– The host sends a packet with the TTL of 2.
– The gateway also returns a packet indicating TTL timeout in the second hop.
The process repeats until the packet reaches the destination.
In this way, the system records the source address of each ICMP TTL timeout message,
and provides a path along which an IP packet passes to the destination.
Procedure
Step 1 Run the ping command to test the network status.
Step 2 Run the tracert command to test the network status.
----End

Example
To test the network status by running the ping command, do as follows:
huawei(config)#ping 10.11.52.240
PING 10.11.52.240: 56 data bytes, press CTRL_C to break
Reply from 10.11.52.240: bytes=56 Sequence=0 ttl=64 time = 10 ms
--- 10.11.52.240 Ping statistics ---
5 packets transmitted
5 packets received
0.00% packet loss
round-trip min/avg/max = 10/10/13 ms
To test the network status by running the tracert command, do as follows:

huawei#tracert 10.11.106.133
traceroute to 10.11.106.133 max hops 30 ,packet 40 bytes
press CTRL_C to break
1 253 ms 476 ms 508 ms 10.11.120.62
2 * * * Request timed out.
3 * * * Request timed out.
4 4 ms 4 ms 5 ms 10.11.106.133

Configuration Guide-PVM CLI 4 Configuring the NMS
4 Configuring the NMS
About This Chapter
This topic describes the examples and related operations for configuring the N2000 BMS so that
you can manage the UA5000 through the N2000 BMS.
4.1 Introduction to the NMS

Introduction to the NMS includes the NMS protocols and NMS maintenance mode supported
by the UA5000.
4.2 Configuration Example of an Outband NMS
The UA5000 is connected to the iManager N2000 NMS workstation through outband
maintenance network port ETH0 on the PVM board. Thus, you can maintain and manage the
UA5000 on the iManager N2000 NMS workstation.
4.3 Configuration Example of an Inband NMS
The UA5000 is connected to the iManager N2000 NMS workstation through inband
4.4 Configuring the SNMP Agent
Configuring the SNMP agent means configuring the community name and read-write authority,
enabling sending the trap packet, and configuring the IP address of the target host for the trap
packet, administrator ID of the device, and location of device.

4.1 Introduction to the NMS

Introduction to the NMS includes the NMS protocols and NMS maintenance mode supported
by the UA5000.
Service Description
The UA5000 provides the NMS interface, and uses the Simple Network Management Protocol
(SNMP) to communicate with the NMS. The UA5000 supports the iManager N2000 Broadband
Management System (N2000 BMS).
The N2000 BMS manages the UA5000 through the NMS interface of the UA5000. The
UA5000 provides the status information for the N2000 BMS by sending the trap packet, thus
reporting certain emergency events.
The UA5000 supports two NMS modes: inband NMS mode and outband NMS mode.
The UA5000 supports the following protocol: SNMPv1, SNMPv2c, SNMPv3.
4.2 Configuration Example of an Outband NMS

The UA5000 is connected to the iManager N2000 NMS workstation through outband
Networking
Figure 4-1 shows the example network for configuring the outband NMS.
Figure 4-1 Example network for configuring the outband NMS

PVMB/PVMD
Router
ETH0
ETH1
NMS workstation
COM
IP address: 10.10.21.1/24
UA5000
IP address: 10.10.20.1/24
Data Plan
Table 4-1 provides the data plan for configuring the outband NMS.

Table 4-1 Data plan for configuring the outband NMS
Item Data
UA5000 maintenance network port (ETH0) IP address: 10.10.20.1/24
NMS (network management system) IP address: 10.10.21.1/24
Figure 4-2 shows the flowchart for configuring the outband NMS.
Figure 4-2 Flowchart for configuring the outband NMS

Start

maintenance network port
Set the SNMP parameters
Enable trap sending
Set the IP address of the target

host for traps
Set the source address for trap

sending
Save the data
End
Procedure
Step 1 Set the IP address of the maintenance network port.
huawei(config)#interface outband
huawei(config-outband)#ip address 10.10.20.1 255.255.255.0 10.10.20.0
{ <cr>|vlan_tag<K> }:
Command:
ip address 10.10.20.1 255.255.255.0 10.10.20.0
Considering the reliability of network, suggest to config vlan for outband IP
. Continue?(y/n)[n]: y

huawei(config-outband)#quit
huawei(config)#
Step 2 Set the NMS working mode to the outband mode.

huawei(config)#sysman mode outband
Step 3 Set the simple network management protocol (SNMP) parameters.

l Set the community name.
huawei(config)#snmp-agent community read public
huawei(config)#snmp-agent community write private
l Set the administrator ID and the contact method.

huawei(config)#snmp-agent sys-info contact HW-075528780808
l Set the device location.

huawei(config)#snmp-agent sys-info location Shenzhen
l Set the SNMP version.

huawei(config)#snmp-agent sys-info version v1
Step 4 Enable the transmission of trap packets.

huawei(config)#snmp-agent trap enable standard
Step 5 Set the IP address of the target host for trap packets.
huawei(config)#snmp-agent target-host trap address 10.10.21.1
securityname private

huawei(config)#save
NOTE
This topic describes the data plan only on the UA5000. To communicate with the network, configure the related
data on the router.
----End
Result
After the configuration, you should be able to manage the UA5000 through the N2000 BMS.
4.3 Configuration Example of an Inband NMS

The UA5000 is connected to the iManager N2000 NMS workstation through inband
Networking
Figure 4-3 shows the example network for configuring the inband NMS.
Figure 4-3 Example network for configuring the inband NMS

PVMB/PVMD
Router Router
ETH0
ETH1
COM
NMS workstation
IP address: 10.10.21.1/24 UA5000
IP address: 10.10.20.1/16

Data Plan
Table 4-2 provides the data plan for configuring the inband NMS.
Table 4-2 Data plan for configuring the inband NMS

Item Data
UA5000 maintenance port (ETH1) IP address: 10.10.20.1/16 (directly use the

primary service IP address)
Default gateway: 10.10.1.1
NMS IP address: 10.10.21.1/24
Default gateway: 10.10.1.10
Figure 4-4 shows the flowchart for configuring the inband NMS.
Figure 4-4 Flowchart for configuring the inband NMS
Start
Query the IP address

of the NMS port
Set the community name

and the access authority
Enable the transmission

of Trap packets

target host for Trap packets
Save the data
End

Procedure
Step 1 Set the NMS working mode as inband.
huawei(config)#sysman mode inband
Step 2 Query the IP address of the NMS port.

huawei(config)#display ip address
OutBand:
IPAddress............: 10.144.78.92
SubMask..............: 255.255.254.0
GateWay..............: 10.144.78.1
MacIndex.............: 1
MacAddress...........: 00-E0-FC-8B-77-78
VlanID...............: --
Eth:
IPAddress............: 10.10.20.1//The first service IP address that is displayed
is the primary service IP address.
SubMask..............: 255.255.0.0
GateWay..............: 10.10.1.1
MacIndex.............: 0
MacAddress...........: 00-E0-FC-8B-77-77
VlanID...............: --
IPAddress............: 10.10.10.2
SubMask..............: 255.255.255.0
GateWay..............: 10.10.10.1
MacIndex.............: 0
MacAddress...........: 00-E0-FC-8B-77-77
VlanID...............: --
NOTE
In inband NMS mode, the primary service IP address is used as the management IP address.
Step 3 Set the community name and the access authority.

Step 4 Enable the transmission of trap packets.

Step 5 Set the IP address of the target host for trap packets.
huawei(config)#snmp-agent target-host trap address 10.10.21.1 securityname private

huawei(config)#save
NOTE
This topic describes the data plan only on the UA5000. To communicate with the network, configure the related
data on the router.
----End
Result
After the configuration, you should be able to manage the UA5000 through the N2000 BMS.

4.4 Configuring the SNMP Agent

Configuring the SNMP agent means configuring the community name and read-write authority,
enabling sending the trap packet, and configuring the IP address of the target host for the trap
packet, administrator ID of the device, and location of device.
4.4.1 Configuring the Community Name and Read-Write Authority

The SNMP community is a collection of one SNMP agent and a group of SNMP managers
whose identities and access control are defined. Each community is identified by a community
name consisting of a character string of eight characters, namely, the password. An SNMP agent
generally provides two communities. One community is read-only, and is called the read
community. The other community is readable and writable. This community can be created and
deleted, which is called the write community.
Context
l In the N2000 BMS, the default name of the read-only community is public, and the default
name of the write community is private.
l The UA5000 supports a maximum of 10 community names.
l The name of the write community in the host should be the same as the name of the write
community in the BMS workstation.
Procedure
Step 1 Run the snmp-agent community command to configure the community name and read-write
authority.
Step 2 Run the display snmp-agent community command to query the information about the
community name.
----End
Example
To add a community with the name of public, which is read-only, do as follows:
huawei(config)#display snmp-agent community read Community name:public Storage
type: nonVolatile View name:ViewDefault
Total number is 1
Related Operation
Table 4-3 lists the related operation for configuring the community name and read-write
authority.

Table 4-3 Related operation for configuring the community name and read-write authority
Delete the existing community name undo snmp-agent community
4.4.2 Enabling Sending the Trap Packet

Enable sending the trap packet. When the device is faulty, or the important data of the device is
modified by the user or other managers, the SNMP agent sends the trap packet to inform the
SNMP manager.
Context
By default, sending the trap packet from the device to the BMS is disabled.
Procedure
Step 1 Run the snmp-agent trap enable standard command to enable sending the trap packet.
Step 2 Run the display snmp-agent trap enable command to query whether sending the trap packet
from the device is enabled.
----End
Example
To enable sending the trap packet from the device to the BMS, do as follows:
huawei(config)#display snmp-agent trap enable Trap is enabled
Related Operation
Table 4-4 lists the related operation for enabling sending the trap packet.
Table 4-4 Related operation for enabling sending the trap packet
Disable sending the trap packet undo snmp-agent trap enable standard
from the device
4.4.3 Configuring the IP Address of the Target Host for the Trap
Packet
After enabling sending the trap packet, you must configure the IP address of the target host for
the trap packet correctly. Thus, the BMS can receive the trap packet.

Context
You can configure a maximum of 20 target hosts for the system.
Procedure
Step 1 Run the snmp-agent target-host trap command to configure the IP address of the target host
for the trap packet.
Step 2 Run the display snmp-agent target-host command to query the target host of the trap packet.
----End
Example
To configure the IP address of the target host for the trap packet to 10.71.53.108, by using
community name private, do as follows:
huawei(config)#snmp-agent target-host trap address 10.71.53.108 securityname
private v3 authentication
huawei(config)#display snmp-agent target-host Traphost list: Traphost address:
10.71.53.108 Traphost portnumber: 162 Traphost securityname: private Traphost
trapversion: v3 Traphost securityLevel: authentication
Total number is 1
Related Operation
Table 4-5 lists the related operation for configuring the IP address of the target host for the trap
packet.
Table 4-5 Related operation for configuring the IP address of the target host for the trap packet
Delete the IP address of the target host undo snmp-agent target-host

for the trap packet
4.4.4 Configuring the Administrator ID of the Device

This topic describes how to re-configure the administrator ID of the device according to the
contact method of the actual device administrator.
Context
By default, the administrator ID is "R&D Shenzhen, Huawei Technologies Co., Ltd.".
Procedure
Step 1 Run the snmp-agent sys-info contact command to configure the administrator ID of the device.
Step 2 Run the display snmp-agent sys-info contact command to query the administrator ID of the
device.
----End

Example
To configure the administrator ID of the device to HW-075528780808, do as follows:
huawei(config)#snmp-agent sys-info contact HW-075528780808
huawei(config)#display snmp-agent sys-info contact
The contact person for this managed node:
HW-075528780808
Related Operation
Table 4-6 lists the related operation for configuring the administrator ID of the device.
Table 4-6 Related operation for configuring the administrator ID of the device
Restore the default configuration of the undo snmp-agent sys-info contact

administrator ID of the device
4.4.5 Configuring the Location of the Device

Re-configure the location of the device according to the city and region of the actual device.
Thus, you can distinguish the devices of different locations in the BMS.
Context
By default, the location of the device is "Shenzhen China".
Procedure
Step 1 Run the snmp-agent sys-info location command to configure the location of the device.
Step 2 Run the display snmp-agent sys-info location command to query the location of the device.
----End
Example
To configure the location of the device to Shanghai China, do as follows:
huawei(config)#snmp-agent sys-info location Shanghai China
huawei(config)#display snmp-agent sys-info location
The physical location of this node:
Shanghai China
Related Operation
Table 4-7 lists the related operation for configuring the location of the device.

Table 4-7 Related operation for configuring the location of the device
Restore the default configuration undo snmp-agent sys-info location

of the location of the device

Configuration Guide-PVM CLI 5 User Management
5 User Management
About This Chapter
Managing the user includes the classification of users supported by the UA5000 and how to add,
modify, disconnect, or delete a user.
5.1 Introduction to the Operation User

The operation user is the user who can perform the configuration and maintenance operations
on the device through the CLI terminal. The operation users at different levels obtain different
authorities.
5.2 Adding a User
After a user is added, the user can access the device and perform the configuration and
management operations on the device.
5.3 Modifying the User Attributes
You can modify the attributes of existing users, such as authority, password, times of re-logins,
and appended information.
5.4 Disconnecting an Online User
Disconnect an online user forcibly to prevent the user from logging in to the device.
5.5 Deleting a User
Only the user at the super user level can delete users at lower levels. The deleted user is not
permitted to log in to the device and implement configuration and management operations on
the device.

5.1 Introduction to the Operation User

The operation user is the user who can perform the configuration and maintenance operations
on the device through the CLI terminal. The operation users at different levels obtain different
authorities.
In terms of authority, UA5000 users are divided into four levels: common user, operator,
administrator and super user. Users at all levels can add a user only at a level that is lower than
theirs. Table 5-1 lists the authority for users at all levels.
Table 5-1 Authority for users at all levels
Level Authority
Common user Common users can perform basic system operations and simple query
operations.
Operator Operators can configure the device and services.
Administrator l Administrators can perform all operations.

l Administrator can maintain the device, user accounts and user
authority.
l Multiple administrators can exist in the system.
Super user l The super user can perform all operations.

l The super user can maintain the device, user accounts and user
authority.
l The super user is of the highest level in the system. Only one super
user exists in the system.
5.2 Adding a User

After a user is added, the user can access the device and perform the configuration and
management operations on the device.
Context
l The super user and administrators can add a user at a level that is lower than their level.
That is:
– The super user can add the administrators, operators, and common users.
– The administrators can add only the operators and common users.
l A user name must be unique. It cannot be all or online.
l Multiple users can be successively added. In one system, a maximum of 127 operating
users can be added. That is, including user root, a total of 128 users can be added to one
system.

When adding a user, you need to configure the user attributes, including the user account,
password, authority, number of re-logins and supplementary information. Table 5-2 lists the
user attributes.
Table 5-2 User attributes

User Attributes Description
Account It is also called user name. It consists of 1–15 printable characters. It

must not be less than six characters in length. The account must be
unique. No space is allowed in the user name. The user name is not case
sensitive.
Password It consists of 0–15 characters. It must not be less than eight characters
in length. It must contain at least one letter and a number. The password
is case sensitive.
Authority In terms of authority, users can be classified into common users,

operators, and administrators.
Times of re-logins Whether a user can log in to the device from multiple terminals depends
on the number of re-logins of the user. The range of the number of re-
logins is 0–4. In normal case, it is set to 1.
Supplementary It is a kind of optional and supplementary information. It is a string of

information characters. It can be null. It can contain a maximum of 30 characters. It
can be the telephone number or address of the user.
Procedure
Step 1 Run the terminal user name command to add a user.
Step 2 Run the display terminal user command to query user information.
----End
Example
Assume the following:
l The user name is huawei.
l The password is huawei123.
l The level is common user.
l The number of re-logins is 3.
l The supplementary information is "user".
To add the user, do as follows:
huawei(config)#terminal user name
User profile name(<=15 chars)[root]:
User Name(<=15 chars):huawei
User Password(<=15 chars):huawei123//This is not displayed.
Confirm Password(<=15 chars):huawei123//This is not displayed.
User profile name(<=15 chars)[root]:
User's Level:

1. Common User 2. Operator 3. Administrator:3

Permitted Reenter Number(0--4):3
User's Appended Info(<=30 chars):user
Adding user succeeds
Repeat this operation? (y/n)[n]:n
huawei(config)#display terminal user all
----------------------------------------------------------------------------
Name Level Status Reenter Profile Append
Num Info
----------------------------------------------------------------------------
huawei1 Admin Online 4 root -----
huawei User Offline 3 root user
----------------------------------------------------------------------------
Total record(s) number: 2
Related Operation
Table 5-3 lists the related operation for adding a user.
Table 5-3 Related operation for adding a user
Delete a user undo terminal user name l Only the super user and
administrators can delete the
users who have lower authority.
l Users cannot delete
themselves.
l User root cannot be deleted.
l An online user cannot be
deleted. To delete the online
user, you need to disconnect the
user first.
l Multiple users can be deleted at
a time.
5.3 Modifying the User Attributes

You can modify the attributes of existing users, such as authority, password, times of re-logins,
and appended information.
5.3.1 Changing a User Level

Only the super user and the administrator have the right to change the level of a user at a lower
level. In addition, the super user and the administrator can only change the user level to a level
lower than their own levels.
Context
l The super user can change the level of a user to the level of a common user, an operator,
or an administrator.
l Administrators can change the level of a user to the level of a common user or an operator.

Procedure
Step 1 Run the terminal user level command to change a user level.
Step 2 Run the display terminal user command to query a user level.
----End
Example
To change a common user huawei to an operator, do as follows:
huawei(config)#terminal user level
1. Common User 2. Operator 3.Administrator:2
User's Level:2
Confirm Level: 2
Information will take effect when this user logs on next time
---------------------------------------------------------------------------
Name Level Status ReenterNum AppendInfo
---------------------------------------------------------------------------
root Super Online 1 none
huawei Operator Offline 3 user
---------------------------------------------------------------------------
Related Operation
Table 5-4 lists the related operations for changing a user level.
Table 5-4 Related operations for changing a user level
Change the user terminal user password

password
Modify the number of terminal user reenter

re-logins
Modify appended terminal user apdinfo

information
5.3.2 Changing the User Password

Change the user password regularly to ensure the device security. Only user root has the right
to change the passwords of other users.
Context
l The super user and administrators can change the passwords of users at lower levels
(including themselves). When changing the passwords of users at lower levels, the super
user and administrators need not enter the old passwords.

l The common users and operators can change only their own passwords, and need to enter
the old passwords.
Procedure
Step 1 Run the terminal user password command to change a user password.
Step 2 Log in to the device with the old user name and new password.
----End
Example
To change the password of common user huawei, do as follows:
huawei(config)#terminal user password
User name (<=15 chars):huawei
New password(<=15 chars):huawei123 //This is not displayed.
Confirm Password(<=15 chars):huawei123 //This is not displayed.
Information takes effect
Related Operation
Table 5-5 lists the related operations for changing a user password.
Table 5-5 Related operations for changing a user password
Modify a user level terminal user level
Modify the number of re-logins terminal user reenter
Modify appended information terminal user apdinfo
5.3.3 Changing the Number of Re-logins

Change the number of re-logins from multiple terminals of a user to ensure the user authority
of re-logging in to the device.
Context
l The super user and administrators can modify the permitted number of re-logins of users
at lower levels.
l It is not allowed to modify the permitted number of re-logins of the super user.
Procedure
Step 1 Run the terminal user reenter command to modify the permitted number of re-logins of a user.
Step 2 Run the display terminal user command to query the permitted number of re-logins of a user.
----End

Example
To change the permitted number of re-logins of common user huawei to 4, do as follows:
huawei(config)#terminal user reenter
Permitted Reenter Number(0--4):4
Confirm Reenter Number(0--4):4
Information will take effect when this user logs on next time
----------------------------------------------------------------------------
Num Info
----------------------------------------------------------------------------
root Super Online 1 root -----
huawei Operator Online 4 root user
----------------------------------------------------------------------------
Related Operation
Table 5-6 lists the related operations for modifying the permitted number of re-logins of a user.
Table 5-6 Related operations for modifying the permitted number of re-logins of a user
Modify a user password terminal user password
Modify appended information terminal user apdinfo
5.3.4 Modifying the Supplementary Information About a User

Modify the supplementary information about a user regularly to update the user information in
time.
Context
l The super user and administrators can modify their own supplementary information and
the supplementary information of users at lower levels.
l Common users and operators can modify their own supplementary information.
Procedure
Step 1 Run the terminal user apdinfo command to modify the supplementary information about a
user.
Step 2 Run the display terminal user command to query the supplementary information about a user.
----End
Example
To modify the supplementary information of common user huawei, do as follows:

huawei(config)#terminal user apdinfo

User name (<=15 chars):huawei
User's Appended Info(<=30 chars):support@huawei.com
Information takes effect
----------------------------------------------------------------------------
Num Info
----------------------------------------------------------------------------
huawei Operator Online 4 root support@huawei.com
----------------------------------------------------------------------------
Related Operation
Table 5-7 lists the related operations for modifying the supplementary information about a user.
Table 5-7 Related operations for modifying the supplementary information about a user
Modify a user password terminal user password
Modify the number of re-logins terminal user reenter
5.4 Disconnecting an Online User

Disconnect an online user forcibly to prevent the user from logging in to the device.
Context
Only the super user and administrators can disconnect an online user at lower levels.
Procedure
Step 1 Run the client kickoff command to disconnect a user.
NOTE
Run the display client command to query the clientid.
Step 2 Run the display terminal user command to query the current users who have logged in.
----End
Example
To disconnect user 3, and confirm that the user is not in the list of the online users, do as follows:
huawei(config)#display terminal user online
---------------------------------------------------------------------------
Num Info
---------------------------------------------------------------------------
huawei Admin Online 4 root -----

ww User Online 4 root user

----------------------------------------------------------------------------
huawei(config)#display client
-----------------------------------------------------------------------------
ID Client name Domain name IP Address Login Time
-----------------------------------------------------------------------------
2 huawei -- 10.144.68.158 2007-10-22 11:17:5
3 ww -- 10.144.68.158 2007-10-22 11:18:1
-----------------------------------------------------------------------------
huawei(config)#client kickoff 3
Are you sure to kick the user off?(y/n)[n]:y
The user has been kicked off successfully
huawei(config)#display terminal user online
---------------------------------------------------------------------------
Num Info
---------------------------------------------------------------------------
huawei Admin Online 4 root -----
----------------------------------------------------------------------------
Related Operation
Table 5-8 lists the related operation for disconnecting an online user.
Table 5-8 Related operation for disconnecting an online user
To… Run the Command...
Delete a user undo terminal user name
5.5 Deleting a User

Only the user at the super user level can delete users at lower levels. The deleted user is not
permitted to log in to the device and implement configuration and management operations on
the device.
Context
l Users cannot delete themselves.
l User root cannot be deleted.
l An online user cannot be deleted. To delete an online user, you need to disconnect the user
first.
l Multiple users can be deleted at a time.
Procedure
Step 1 Run the undo terminal user name command to delete a user.
Step 2 Run the display terminal user command to verify that a user is deleted successfully.
----End

Example
To delete user huawei, do as follows:
huawei(config)#undo terminal user name
Are you sure to delete the user?(y/n)[n]:y
Deleting user succeeds
----------------------------------------------------------------------------
Num Info
----------------------------------------------------------------------------
----------------------------------------------------------------------------
Related Operation
Table 5-9 lists the related operations for deleting a user.
Table 5-9 Related operations for deleting a user

Disconnect an online user client kickoff
Add a user terminal user name

Configuration Guide-PVM CLI 6 Device Management
6 Device Management
About This Chapter
This topic describes how to manage the UA5000. Device management includes shelf
management and board management.
6.1 Introduction to the Device

Introduction to the device includes the management of the device and the types and status of the
control board and service board supported by UA5000.
6.2 Adding the Connection Between the Shelves
The connection between shelves need not be added when only the master shelf exists. When the
master shelf and slave shelf are required, you must add a slave shelf and a connection between
the master shelf and slave shelf.
6.3 Setting the Description of a Shelf
Set and change regularly the number of a test group or the description of a shelf to update the
shelf information in time.
6.4 Resetting a Control Board
Reset a control board to run the newly loaded program and database. If there is no standby control
board, the resetting operation causes the resetting of all the service boards. Exercise caution
when performing this operation.
6.5 Adding a Service Board
Adding a service board is to provide you the data configuration when the service board is offline,
namely, an operation when the actual service board is not inserted. The system checks the
configured data in details. After the service board is added successfully and the service board is
inserted, it runs according to the configuration.
6.6 Deleting a Service Board
When the service board in a certain slot is faulty or not required because of the system capacity
reduction, you can delete the service board. When the service board is deleted successfully, you
can add a new service board in the idle slot.
6.7 Resetting a Service Board
You can reset a service board when the service board does not work properly. The system
generates a fault alarm after the reset operation. The system generates a recovery alarm after the
board recovers.

6.8 Prohibiting a Service Board

When a service board does not work normally, or a certain port on a service board is faulty, you
must prohibit the service board first. When you prohibit a service board, you prohibit not only
the normal services on the board but also any other operation till the service board is unprohibited
(enabled).

6.1 Introduction to the Device

Introduction to the device includes the management of the device and the types and status of the
control board and service board supported by UA5000.
Service Description
l Shelf management includes the following: adding a shelf, adding a link between two
shelves, deleting a shelf, deleting a link between two shelves, configuring the attributes of
a shelf, querying shelf information, and querying a link between two shelves.
l Control board management includes the following: resetting a control board and querying
control board information.
l Service board management includes the following: adding a service board offline,
confirming a service board, deleting a service board, resetting a service board, prohibiting
a service board, unprohibiting a service board, and querying the service board information.
You can use the HABD or HABL shelf as the master shelf and use the HABF as the slave shelf
for the UA5000. Thus, the connection between shelves is supported.
When you use the HABM shelf as the master shelf for the UA5000 MiniMSAN, the connection
between shelves is not supported.
Introduction to Board Types

Table 6-1 lists the boards supported by the UA5000.
Table 6-1 Boards supported by the UA5000
Board Type Board Name
Control board PVMB, PVMD, and PVME
Service board A32, CSR, CSM, CDI, DSL, DSLE, DSLD, EDTB, SDL, SDLE, ATI,
RSP, RSU, and HSL
Interface board EP1A, GP1A
Monitoring board ESC, FCBB/FCBA, PWMA, and FCBD
Secondary power PWX

supply board
Rear access transfer E1TB, EFTB, HWCB, HWTB, RATB, and SAPB
board
Front access E1TF, EFTF, HLAF, HLEF, HWCF, HWTF, PSTF, RATF, SLTF,
transfer board SAPF, and WATF
Introduction to Board Status

Table 6-2 lists the service board status.

Table 6-2 Service board status

Status Remarks
Normal It indicates that the board is running in the normal state.
Failed It indicates that the board is faulty.
Config It indicates that the board is being configured.
Auto_find It indicates that the board is inserted, but not confirmed.
Prohibited It indicates that the board is prohibited.
6.2 Adding the Connection Between the Shelves

The connection between shelves need not be added when only the master shelf exists. When the
master shelf and slave shelf are required, you must add a slave shelf and a connection between
the master shelf and slave shelf.
Context
l The master shelf and the PVM control board are in the normal state after the master shelf
is added.
l The slave shelf is in the faulty state after it is added. The slave shelf is normal after the
connection is added between shelves.
Procedure
Step 1 Run the frame add command to add a shelf.
Step 2 Run the frame connect command to add a connection between shelves.
Step 3 Run the display frame info command to query the connection between shelves.
----End
Example
To add a connection between the master and slave shelves, do as follows:
huawei(config)#frame add 0
FrameType:
0 : MAIN_HABM_30(HABA) 1 : MAIN_HAFM_30(HABD)
2 : MAIN_HAFM_6(HABL) 3 : MAIN_H602HABD(HABD)
4 : MAIN_H601HABC(HABC) 5 : MAIN_H601HABO(HABO)
6 : MAIN_H601HABM(HABM) 7 : SLAVE_HAFS_32(HABE)
8 : SLAVE_HABS_32(HABB) 9 : SLAVE_HABS_30(HABA)
10 : SLAVE_HAFS_30(HABD) 11 : SLAVE_H602HABD(HABD)
12 : SLAVE_H602HABE(HABE) 13 : RSU_HAFS_30(HABD)
14 : RSU_HABS_30(HABA) 15 : RSU_HAFS_12(HABC)
16 : RSU_HAFS_6(HABL) 17 : RSUG_ONU60A(HUBO)
18 : RSUG_ONU04A 19 : RSUG_ONU08A
20 : RSP_19(HCB) 21 : RSP_15(HDB)
22 : RSP_14(HIB) 23 : RSP_12(HFB)
24 : RSP_10(HGB) 25 : RSP_6A(HMB)
26 : RSP_6B(HLB) 27 : UAM_R (HUBM)
28 : UAS_R (HUBS) 29 : UAFM_R(HUBE)

30 : UAFS_R(HUBF) 31 : UAMB_R(HUBB)
32 : ONU60A_R(HUBO) 33 : ONUF01D100_R(HUBL)
34 : VRSP_12(HABA) 35 : VRSP_18(HABA)
36 : HWTA(HIB_1) 37 : HWTA(HIB_2)
38 : HWTA(HIB_3)
Please select frame type (0 ~ 38):1
Frame add successfully
huawei(config)#frame connect
{ upframeid<0,97> }:0
{ downframeid<0,97> }:1
Command:
frame connect 0 1
Add the frame connection successfully
huawei(config)#display frame connect
---------------------------------------------
Record Upper-frame Lower-frame
---------------------------------------------
0 0 1
---------------------------------------------
Related Operation
Table 6-3 lists the related operation for configuring the connection between shelves.
Table 6-3 Related operation for configuring the connection between shelves
Delete the connection between shelves undo frame connect
6.3 Setting the Description of a Shelf

Set and change regularly the number of a test group or the description of a shelf to update the
shelf information in time.
Precaution
l Set the information of the test group of a shelf before setting the number of the test group.
l The number of the test group and the description of the shelf cannot be modified at the
same time.
Procedure
Step 1 Run the frame set command to set the description of a shelf.
Step 2 Run the display frame info command to query the description of a shelf.
----End
Example
To set the description of shelf 0 to huawei, do as follows:
huawei(config)#frame set 0 desc huawei
huawei(config)#display frame info 0
----------------------------------------------------------------------------
Type : MAIN_F(H612HABD)

State: Normal
Desc : huawei
TestGroup: 0
EMU 0 ID: 5 Subnode:12 State:Communications failed
EMU 2 ID: 2 Subnode:1 State:Communications normal
----------------------------------------------------------------------------
6.4 Resetting a Control Board

Reset a control board to run the newly loaded program and database. If there is no standby control
board, the resetting operation causes the resetting of all the service boards. Exercise caution
when performing this operation.
Context
The control boards include active control board and standby control board.
Resetting an active control board results in the following:
l In the case of an active/standby configuration, the resetting operation does not affect the
ongoing services.
l If there is no standby control board, the resetting operation causes the resetting of all the
service boards. In other words, this operation causes the resetting of the system.
Precaution
l The resetting of a control board may discard unsaved data. Therefore, before the operation,
run the save command to save the system data.
l The board reset command cannot be used to reset a control board.
NOTE
Reset the system only when required. Otherwise, the services may be affected. In general, the system
is reset after a new application or database is loaded.
Procedure
Step 1 Run the reboot command to reset the control board.
----End
Example
To reset the active control board, do as follows:
huawei#reboot active
Please check whether data has saved, the unsaved data may lose if reboot active
board, are you sure
to reboot active board? (y/n)[n]:y
Reboot active will cause system forced switchover, are you sure to rebootactive
board?
(y/n)[n]:y
To reset the standby control board, do as follows:

huawei#reboot standby
Please check whether data has saved, are you sure to reboot standby board? (y/n)
[n]:y

6.5 Adding a Service Board

Adding a service board is to provide you the data configuration when the service board is offline,
namely, an operation when the actual service board is not inserted. The system checks the
configured data in details. After the service board is added successfully and the service board is
inserted, it runs according to the configuration.
Precaution
l After a service board is added offline, the status of the service board is faulty. The status
changes to normal only when the slot is inserted with a service board of the same type. If
a service board of different type is inserted, the service board cannot be started because the
slot and the service board do not match.
l You can add a service board only in an idle slot.
Procedure
Step 1 Run the board add command to add a service board offline.
Step 2 Insert the service board of the same type manually into the service shelf
Step 3 Run the board confirm command to confirm a service board.
Step 4 Run the display board command to query the status of a service board.
----End
Example
To insert an A32 board in slot 0/10, do as follows:
huawei(config)#board add 0/10 a32
huawei(config)#board confirm 0/10
huawei(config)#display board 0/10
--------------------------------------------------------
Board Name : A32
Board state : Normal
Online state : -
Board has ports : 32
0 port type : PSTN_PORT Licensed


A/u Law : A law
Port Impedance : Bureau machine in China(200+680|| 100nf)
Port Current : 25mA steady current
Work Environment : -
Work Mode : -
Ring Voltage : -
--------------------------------------------------------
Related Operation
Table 6-4 lists the related operation for adding a service board.
Table 6-4 Related operation for adding a service board
Delete a board delete Before deleting a service board,

service delete the data on it first. Otherwise,
board deleting the service board fails.
6.6 Deleting a Service Board

When the service board in a certain slot is faulty or not required because of the system capacity
reduction, you can delete the service board. When the service board is deleted successfully, you
can add a new service board in the idle slot.
Precaution
l Before deleting a service board, delete the data on it first. Otherwise, deleting the service
board fails.
l A control board in the auto-find state cannot be deleted; however, the faulty standby PVM
board can be deleted.
Procedure
Step 1 Run the board delete command to delete a service board.
Step 2 Run the display board command to query the status of a board.
----End
Example
To delete the faulty service board in slot 0/12, do as follows:

huawei(config)#board delete 0/12

Are you sure to delete this board? (y/n)[n]: y
0 frame 12 slot board delete successfully
Failure: Board does not exist
Related Operation
Table 6-5 lists the related operation for deleting a service board.
Table 6-5 Related operation for deleting a service board

Add a service board board add
6.7 Resetting a Service Board

You can reset a service board when the service board does not work properly. The system
generates a fault alarm after the reset operation. The system generates a recovery alarm after the
board recovers.
Precaution
l When the service board starts successfully after resetting, it reports the registration
information to the control board. The control board configures the data of the service board
to restore the services.
l Do not reset the power board.
Procedure
Step 1 Run the board reset command to reset a service board.
----End
Example
To reset the service board in slot 0/12, do as follows:
huawei(config)#board reset 0/12
Are you sure to reset board? (y/n)[n]:y
0 frame 2 slot reset board message sent successfully...
6.8 Prohibiting a Service Board

When a service board does not work normally, or a certain port on a service board is faulty, you
must prohibit the service board first. When you prohibit a service board, you prohibit not only
the normal services on the board but also any other operation till the service board is unprohibited
(enabled).
Context
You need to prohibit service boards in the following cases:

l The services of a board are suspended but not deleted.

l The dynamic resources are released.
Precaution
l The control board cannot be prohibited.
l The service board that is in the auto-find state and is unconfirmed cannot be prohibited.
l Prohibiting a service board interrupts the services of the board.
l It is not allowed to prohibit the power board.
Procedure
Step 1 Run the board prohibit command to prohibit a service board.
Step 2 Run the display board command to query the status of a service board.
----End
Example
To prohibit the service board in slot 0/12, do as follows:
huawei(config)#board prohibit 0/12
Prohibiting board will interrupt all services on this board, are you
sure to prohibit board? (y/n)[n]:y
Prohibit board successfully
--------------------------------------------------------
Board Name : A32
Board state : Prohibited
Online state : Unmanageable
Board has ports : 32


A/u Law : A law
Port Impedance : Bureau machine in China(200+680|| 100nf)
Port Current : 25mA steady current
Work Environment : EMSAN
Work Mode : COMBO
Ring Voltage : -
--------------------------------------------------------

Configuration Guide-PVM CLI 7 Configuring the System DSP Channels
7 Configuring the System DSP Channels
About This Chapter
The number of digital signal processor (DSP) channels specifies the processing capability of a
DSP chip. Configuring the system DSP channels includes configuring the attributes of the DSP
channels and configuring the number of DSP channels for subscribers with different priorities.
7.1 Introduction to the System DSP Channels

Through the DSP channels, the analog signals accessed by the UA5000 can be digitized. Thus,
the voice service can be transmitted over the IP network.
7.2 Configuring the Attributes of the DSP Channel
The attributes of the DSP channel include the parameters such as the maximum rate of the fax
training, fax training mode, input gain of the DSP chip, output gain of the DSP chip, and default
interval for the DSP to packetize RTP packets. By configuring the parameters of the attributes
of the DSP channel, you can ensure the voice quality during the analog-digit and digit-analog
conversion.
7.3 Configuring the Number of the Globally Shared DSP Channels
The number of the globally shared DSP channels refer to the number of the system DSP channels
minus the number of the channels reserved for the VAG. By configuring the number of the
globally shared DSP channels, you can allocate different numbers of the DSP channels for
subscribers with different priorities.
7.4 Configuring the Number of DSP Channels in the DSP Resources Reserved for the VAG
The number of DSP channels reserved for the VAG refers to the number of private DSP channels
reserved for the specified VAG. Subscribers in the VAG can use only the reserved DSP channels.
Through the reservation of DSP channels for the VAG, subscribers of different priorities in the
VAG can be allocated with different numbers of DSP channels.
7.5 Prohibiting the DSP Channel
When one or more DSP channels on a subboard are faulty, you can prohibit the faulty DSP
channel so that the service is not affected.

7.1 Introduction to the System DSP Channels

Through the DSP channels, the analog signals accessed by the UA5000 can be digitized. Thus,
the voice service can be transmitted over the IP network.
Service Description
DSP is a type of chip used to process the digital signals. The PVM board uses DSP to packetize
the PCM signals to the voice packets, and then sends the voice packets into the IP network. In
this way, the VoIP function is realized.
DSP channel: The processing capability of the DSP chip is further quantified and can be reflected
by the number of channels.
Each DSP channel processes the information in one 64 K PCM voice channel.
Only after you insert a DSP subboard in the PVM control board, the PVM control board supports
the DSP channels. The number of total DSP channels varies according to different subboard.
7.2 Configuring the Attributes of the DSP Channel

The attributes of the DSP channel include the parameters such as the maximum rate of the fax
training, fax training mode, input gain of the DSP chip, output gain of the DSP chip, and default
interval for the DSP to packetize RTP packets. By configuring the parameters of the attributes
of the DSP channel, you can ensure the voice quality during the analog-digit and digit-analog
conversion.
Context
l The UA5000 supports two fax training modes: end-to-end training and local training.
l The network transmission delay, the device processing delay, and the serial link delay exist
in the VoIP service. The occurrence of the delay causes the voice jitter and decreases the
call quality. JitterBuffer is used to eliminate the delay, and improve the voice quality with
the lost-packet compensation function.
l For details of the attributes of the DSP channel, see the parameter description of the dsp
attribute command.
Procedure
Step 1 Run the dsp attribute command to configure the attributes of the DSP channel.
Step 2 Run the display dsp attribute command to query the DSP parameters.
----End
Example

l The maximum rate of the fax training is V29.

l The fax training mode is local training.
l The initial adaptive JitterBuffer of the DSP channel is 50.
l The maximum adaptive JitterBuffer of the DSP channel is 100.
l The maximum fixed JitterBuffer of the DSP channel is 90.
l The minimum adaptive JitterBuffer of the DSP channel is 20.
l The minimum fixed JitterBuffer of the DSP channel is 40.
l The initial fixed JitterBuffer of the DSP channel is 60.
l The input gain of the DSP chip is 2 dB.
l The output gain of the DSP chip is 2 dB.
l The default coding mode of the DSP channel is G.729.
l The interval of transmitting the RTCP packet of the DSP channel is 500 ms.
l The default value of severe packet loss second threshold is 500.
l The VQM function is enabled.
l The default RTP packetization interval of the DSP channel is 30 ms.
l The default echo suppression function of the DSP channel is enabled.
l The default silence compression function of the DSP channel is enabled.
l The PLC algorithm function of the DSP channel is enabled.
l The value of the clearmode payload of the DSP channel is 100.
To configure the DSP attributes, do as follows:
huawei(config)#dsp attribute train-rate 1 train-mode 1 init-adapt-jb 50 max-adapt-
jb 100 max-fixed-jb 90 min-adapt-jb 20 min-fixed-jb 40 nominal-fixed-jb 60 input-
gain 2 output-gain 2 code 3 rtcp-interval 500 sev-degradethreshold 500 bvqm 1 rtp-
interval 30 echoflag 1
huawei(config)#dsp attribute clearmode-payload 100 silenceflag 1 statisticsflag 1
plc 1
huawei(config)#display dsp attribute
-----------------------------------------------------------------------------
Fax Max Train Rate :V29
Fax Train Mode :Local Train
DSP chip maximum adaptive JitterBuffer(ms) :100
DSP chip minimum adaptive JitterBuffer(ms) :20
DSP chip initial adaptive JitterBuffer(ms) :50
DSP chip maximum fixed JitterBuffer(ms) :90
DSP chip minimum fixed JitterBuffer(ms) :40
DSP chip nominal fixed JitterBuffer(ms) :60
DSP input gain(PCM->IP)(db) :-8
DSP output gain(IP->PCM)(db) :-8
DSP code type :G.729
RTCP package send interval time(ms) :500
Severe Degrade Threshold(periods) :500
Support VQM :Enable
DSP Rtp Packet Interval(ms) :30
DSP echo check :Open
DSP silence reduce :Open
DSP need statistics or not :Yes
DSP Packet Lose Compensate :Open
DSP clearmode payload value :100
Support RTCP XR :Disable
T30 redundancy parameter value of T38 Fax :3
T4 redundancy parameter value of T38 Fax :3
Fax V8 Negotiate :Enable
DSP VBD payload value :102
DSP G.726-16k payload value :103


DSP 2198 payload value :96
DSP 2833 payload value :97
-----------------------------------------------------------------------------
Related Operation
Table 7-1 lists the related operations for configuring the attributes of the DSP channel.
Table 7-1 Related operation for configuring the attributes of the DSP channel
Prohibit the DSP channel dsp prohibit Prohibit the DSP channel that
cannot be used any more.
Unprohibit the DSP channel undo dsp prohibit When the DSP channel
recovers, unprohibit the DSP
channel to reuse it.
Query the status of the DSP display dsp state -

channel
Query the DSP status of the display dsp statistic Query the configuration and the
VAG usage of the DSP resources on
a specified VAG.
7.3 Configuring the Number of the Globally Shared DSP

Channels
The number of the globally shared DSP channels refer to the number of the system DSP channels
minus the number of the channels reserved for the VAG. By configuring the number of the
globally shared DSP channels, you can allocate different numbers of the DSP channels for
subscribers with different priorities.
Context
l The subscribers are classified into the following three categories:
– Cat1: category 1 government subscribers
– Cat3: common subscribers.
The priorities of three-category subscribers are as follows: cat1 > cat2 > cat3.
l The DSP resources are configured for subscribers according to the following principles:
– For category 1 government subscribers, the resources reserved for them are configured
first. When the resources are insufficient, the resources reserved for category 2
government subscribers are configured. When the resources are insufficient again, the
resources reserved for common subscribers are configured.

first. When the resources are insufficient, the resource reserved for common subscribers
are configured.
– For common subscribers, the remaining globally shared DSP resources are configured.
Precaution
The reserved DSP channels must be configured for subscribers according to the number of
subscribers with the priorities of cat1 and cat2.
Procedure
Step 1 Run the dsp reserve share command to configure the number of DSP channels in globally
shared DSP resources.
Step 2 Run the display dsp statistic share command to query the allocation and the usage of globally
----End
Example
To reserve 150 DSP channels for category 1 government subscribers and 200 DSP channels for
category 2 government subscribers in globally shared DSP resources, do as follows:
huawei(config)#dsp reserve share cat1 150 cat2 200
huawei(config)#display dsp statistic share
-----------------------------------------------------------------------------
Config Used
Cat1 DSP Channels: 150 0
Common DSP Channels: 226 0
-----------------------------------------------------------------------------
Global Share DSP Channels Total: 576
DSP Channels Used: 0
Cat1 User Used: 0
Cat2 User Used: 0
Common User Used: 0
-----------------------------------------------------------------------------
Related Operation
Table 7-2 lists the related operations for configuring the number of DSP channels in globally
Table 7-2 Related operations for configuring the number of DSP channels in globally shared
DSP resources
To... Run the command... Remarks
Configure the attributes of the dsp attribute -

DSP channel
Configure the number of DSP dsp reserve -

channels in the DSP resources
reserved for the VAG

Query the attributes of the DSP display dsp attribute -

channel
Query the DSP channel status display dsp statistic Query the DSP resource
of the VAG configuration and the usage of a
specified VAG.
7.4 Configuring the Number of DSP Channels in the DSP

Resources Reserved for the VAG
The number of DSP channels reserved for the VAG refers to the number of private DSP channels
reserved for the specified VAG. Subscribers in the VAG can use only the reserved DSP channels.
Through the reservation of DSP channels for the VAG, subscribers of different priorities in the
VAG can be allocated with different numbers of DSP channels.
Context
l Subscribers in the VAG can only use DSP channels in the reserved DSP resources.
l Subscribers are classified into the following three categories:
– Cat3: common subscribers.
The priorities of three category subscribers are as follows: cat1 > cat2 > cat3.
l The DSP resources are configured for subscribers according to the following principles:
first. When the resources are insufficient, the resources reserved for category 2
government subscribers are configured. When the resources are insufficient again, the
resources reserved for common subscribers are configured.
first. When the resources are insufficient, the resource reserved for common subscribers
are configured.
– For common subscribers, the remaining DSP resources are configured.
l For the related information about the VAG, see "11 Configuring the VAG Service."
Precaution
The reserved DSP channels must be configured for subscribers according to the number of
subscribers with the priorities of cat1 and cat2.
Procedure
Step 1 Run the interface h248 or interface mgcp command to enter the MG interface mode to be
configured.

Step 2 Run the dsp reserve command to configure the number of DSP channels in the DSP resources
reserved for the VAG.
Step 3 Run the display dsp statistic command to query the allocation and the usage of DSP resources
in a specified VAG.
----End
Example
To configure 100 DSP channels for VAG 0, 25 DSP channels for category 1 government
subscribers, and 25 DSP channels for category 2 government subscribers, do as follows:
huawei(config)#interface h248 0
huawei(config-if-h248-0)#dsp reserve total 100 cat1 25 cat2 25
huawei(config-if-h248-0)#display dsp statistic
-----------------------------------------------------------------------------
Config Used
DSP Channels Total: 100 0
Common DSP Channels: 50 0
-----------------------------------------------------------------------------
Cat1 User Used: 0
Cat2 User Used: 0
Common User Used: 0
-----------------------------------------------------------------------------
Related Operation
Table 7-3 lists the related operations for configuring the number of DSP channels in the reserved
DSP resources for the VAG.
Table 7-3 Related operations for configuring the number of DSP channels in the reserved DSP
resources for the VAG

DSP channel
Configuring the number of dsp reserve share -

DSP channels in globally
shared DSP resources

channel
Query the status of globally display dsp statistic Query the configuration and the
shared DSP channels share usage of the globally shared
DSP resources.
7.5 Prohibiting the DSP Channel

When one or more DSP channels on a subboard are faulty, you can prohibit the faulty DSP
channel so that the service is not affected.

Precaution
A DSP channel that is processing the voice service cannot be prohibited.
Procedure
Step 1 Run the dsp prohibit command to prohibit the DSP channel.
Step 2 Run the display dsp state command to query the status of the DSP channel.
----End
Example
To prohibit two consecutive DSP channels on subboard 0/5/0, with the start DSP channel number
3, do as follows:
huawei(config-narrow-resource)#display dsp state 0/5/0 3 2
------------------------------------------------------------------------------
Channel NO. DSP Channel State 0-idle $-G.711 busy A-All busy W-Wastage X-fault
@-IP loopback *-PCM loopback #-prohibited
------------------------------------------------------------------------------
0000-0049 ---00
------------------------------------------------------------------------------
Total: 2 DSP channel
2 idle, 0 G.711 Busy, 0 All Busy, 0 Wastage, 0 Fault, 0 IP loopback, 0 PCM
loopback, 0 prohibited
------------------------------------------------------------------------------
huawei(config-narrow-resource)#dsp prohibit 0/5/0 3 2
huawei(config-narrow-resource)#display dsp state 0/5/0 3 2
------------------------------------------------------------------------------
Channel NO. DSP Channel State 0-idle $-G.711 busy A-All busy W-Wastage X-fault
@-IP loopback *-PCM loopback #-prohibited
------------------------------------------------------------------------------
0000-0049 ---##
------------------------------------------------------------------------------
Total: 2 DSP channel
0 idle, 0 G.711 Busy, 0 All Busy, 0 Wastage, 0 Fault, 0 IP loopback, 0 PCM
loopback, 2 prohibited
------------------------------------------------------------------------------
Related Operation
Table 7-4 lists the related operations for prohibiting the DSP channel.
Table 7-4 Related operations for prohibiting the DSP channel

DSP channel

channel
Unprohibit the DSP channel undo dsp prohibit When the DSP channel
recovers, unprohibit the DSP
channel to use it again.

Query the DSP channel status display dsp statistic Query the configuration and the
of the VAG usage of the DSP resources on
a specified VAG.

Configuration Guide-PVM CLI 8 Configuring the Clock
8 Configuring the Clock
About This Chapter
In the digital network consisting of the UA5000 and other devices, the primary problem to be
solved is clock synchronization. The UA5000 adopts the master-slave mode to synchronize the
clock with the clocks of the devices in the network.
8.1 Introduction to the Clock

The purpose of clock synchronization is to restrict the clock frequency and the phase of each
node in a network within the predefined tolerance scope. This prevents the transmission
performance degradation due to poor timings at the transmit (Tx) and receive (Rx) ends.
8.2 Configuration Example of a Clock Source
This topic describes how to implement the clock synchronization of the UA5000 by extracting
the clock signals from ports 0/4/0 and 0/5/0 on the UA5000.
8.3 Configuring the Reference Clock Source
Configure the reference clock source for the port on the PVM board to synchronize the clock of
the UA5000 with the clock of the upper-layer device.
8.4 Setting the Clock Source Priority
Set the clock source priority for each clock source on the PVM board. The UA5000 uses the
clock source with the highest priority for the clock synchronization. When the link of the clock
source with the highest priority is faulty, the UA5000 uses the clock source with the second
highest priority for the clock synchronization. This rule applies to the rest clock sources.

8.1 Introduction to the Clock

The purpose of clock synchronization is to restrict the clock frequency and the phase of each
node in a network within the predefined tolerance scope. This prevents the transmission
performance degradation due to poor timings at the transmit (Tx) and receive (Rx) ends.
Service Description
There are two methods of achieving clock synchronization in a digital network: pseudo
synchronization and master-slave synchronization. Table 8-1 shows the details of the two clock
synchronization modes.
Table 8-1 Clock synchronization description
Synchronization Description
Mode
Pseudo In a digital network using pseudo synchronization, all digital

synchronization exchanges are independent in terms of the clock. The clock of each
digital exchange is of high precision and stability. Usually, the cesium
clock is used. Because these clocks are independent from each other,
their frequencies and phases are not totally synchronized, but the
difference can be ignored because these clocks are precise. Hence,
this clock synchronization is called pseudo synchronization.
It is applied in international digital networks.
Master-slave In a network that uses the master-slave synchronization, there is a

synchronization master exchange with a high-precision clock. The other exchanges in
the network are controlled by the master exchange, that is, the clocks
of other exchanges in the network are synchronized with the clock of
this master exchange. The clock of the lower layer exchange is
synchronized with the clock of the upper layer exchange until the
clock of the end exchange is synchronized.
The reference clock source of the system includes Bits clock, E1 line clock, and GPON line
clock. A maximum of 10 clock sources can be configured when you run the clock source
command to add the reference clock.
Service Implementation
The UA5000 often uses the master-slave synchronization mode. The working procedure is as
follows:
1. The UA5000 extracts the clock signals sent from the upper-layer device at the line side as
the clock source of the system. The clock source, with the highest priority and in the normal
state, is used as the system clock.
2. The UA5000 sends the clock signals to all the service boards through the backplane.

3. The service boards send the clock signals to a lower-layer network element.
NOTE
The control boards can also send the clock signals to a lower-layer network element.
8.2 Configuration Example of a Clock Source

This topic describes how to implement the clock synchronization of the UA5000 by extracting
the clock signals from ports 0/4/0 and 0/5/0 on the UA5000.
Prerequisite
The UA5000 must be connected properly according to the networking.
Precaution
l You can configure a maximum of 10 clock sources.
l The added clock module must be set with a priority before use.
l After the priority of the clock module is set, it takes effect immediately. This operation may
result in clock switch.
l When running the undo clock source command to delete the clock source that is being
used by the system, it can result in clock switch.
Networking
Figure 8-1 shows the networking of the clock configuration.
Figure 8-1 Networking of the clock configuration
E1/V5
SDH
E1/V5
P P A A
V V 3 3
M M 2 2
UA5000
Data Plan
l By running the clock source command, you can configure a maximum of 10 clock sources.
The following section uses the configuration of two clock sources as an example.

l By running the clock priority command, you can configure a maximum of 10 priority
levels. The following section uses the configuration of the priority level of the two clock
sources as an example.
Table 8-2 provides the data plan for configuring the UA5000 clock.
Table 8-2 Data plan for configuring the clock
Item Data
srcindex System reference clock source 0: 0

System reference clock source 1: 1
Port number System reference clock source 0: 0/4/0

System reference clock source 1: 0/4/1
priority System reference clock source 0: High

System reference clock source 1: Low
Figure 8-2 shows the flowchart for configuring the clock.
Figure 8-2 Flowchart for configuring the clock
Start
Configure the system

reference clock source
Set the priority of the

system clock source
Query the clock source

status
End
Procedure
Step 1 Configure the reference clock source.
l Clock source 0 extracts clock signals from port 0/4/0.
l Clock source 1 extracts clock signals from port 0/4/1.
huawei(config)#clock source 0 E1 0/4/0
huawei(config)#clock source 1 E1 0/4/1

Step 2 Set the priority of the clock source.

l Set the clock source 0 with the highest priority.
l Set the clock source 1 with the second highest priority.
huawei(config)#clock priority 0/1
Step 3 Query the status of the clock source.

huawei(config)#display clock source
--------------------------------------------------------
Index Config Source Priority State Output
--------------------------------------------------------
0 E1 0/4/0 0 OK Yes
1 E1 0/4/1 1 OK No
--------------------------------------------------------
----End
Result
The UA5000 selects clock source 0 as the system clock and delivers the clock signals to each
service board.
8.3 Configuring the Reference Clock Source

Configure the reference clock source for the port on the PVM board to synchronize the clock of
the UA5000 with the clock of the upper-layer device.
Context
The system supports a maximum of 10 reference clock sources.
Procedure
Step 1 Run the clock source command to add the reference clock source.
Step 2 Run the display clock source command to query the reference clock source.
----End
Example
To add an E1 clock source with index 0 to port 0/4/0, do as follows:
huawei(config)#clock source 0 e1 0/4/0
Clock source set succeeded

--------------------------------------------------------
--------------------------------------------------------
0 E1 0/4/0 0 OK Yes
--------------------------------------------------------
To delete the clock source with index 0, do as follows:

huawei(config)#undo clock source 0
Clock source deletion succeeded

The current system clock source is local

Failure: User not config any clock source
Related Operation
Table 8-3 lists the related operation for configuring the reference clock source of the system.
Table 8-3 Related operation for configuring the reference clock source of the system
Set the clock priority clock priority After the priority of the clock
module is set, it takes effect
immediately. This operation
may result in clock switch.
8.4 Setting the Clock Source Priority

Set the clock source priority for each clock source on the PVM board. The UA5000 uses the
clock source with the highest priority for the clock synchronization. When the link of the clock
source with the highest priority is faulty, the UA5000 uses the clock source with the second
highest priority for the clock synchronization. This rule applies to the rest clock sources.
Precaution
After the priority is set, the priority of the clock module takes effect immediately. This operation
may result in clock switch.
Procedure
Step 1 Run the clock priority command to set the clock priority of the reference clock source.
Step 2 Run the display clock source command to query the reference clock source.
----End
Example
To set the priority level of the clock source with index 1 as high, and the priority level of clock
source with index 0 as low, do as follows:
huawei(config)#clock
{ priority<K>|source<K> }:priority
{ p0/p1/p2/p3/p4/p5/p6/p7/p8/p9<S><1,19> }:1/0
Command:
clock priority 1/0
Clock source priority set succeeded

--------------------------------------------------------
--------------------------------------------------------
0 E1 0/4/0 1 OK Yes
1 E1 0/5/0 0 OK No
--------------------------------------------------------

Related Operation
Table 8-4 lists the related operations for setting the clock source priority.
Table 8-4 Related operations for setting the clock source priority
Set the reference clock source clock source The added clock source must
be set with a priority before
being used.
Query the reference clock source display clock source -

Configuration Guide-PVM CLI 9 Configuring the MG Interface
9 Configuring the MG Interface
About This Chapter
When configuring the IP services such as voice over IP (VoIP) and integrated services digital
network (ISDN), configure the media gateway (MG) first. One MG corresponds to a unique MG
IP address and MG port number, which are the only ways for the UA5000 to communicate with
the MGC.
9.1 Introduction to the MG Interface

In the application of the next generation network (NGN), the UA5000 communicates with the
upper-layer MGC through the MG interface (the MG IP address and MG port number of the
MG interface). Each MG interface corresponds to one virtual access gateway (VAG).
9.2 Configuration Example of the MG Interface (the H.248 Protocol)
Configuring the MG interface means configuring the attributes of the MG interface, software
parameters, ringing mode, and digitmap. After configuring the MG interface, you can configure
the IP services such as VoIP and ISDN through the MG interface.
9.3 Configuration Example of the MG Interface (the MGCP Protocol)
9.4 Adding an MG Interface
Add an MG interface to the UA5000 so that the UA5000 and the MGC can communicate with
each other through the MG interface.
9.5 Configuring the IP Address Pool
The IP address can be used for configuring the service only after the IP address is added to the
IP address pool successfully. By configuring the IP address pool, you can add the planned IP
address to the IP address pool.
9.6 Configuring the Attributes of the MG Interface (the H.248 Protocol)
The attributes of the MG interface include the IP address, domain name, and port number
required for setting up the communication between the MG interface and the MGC, and also
include the 2833 encryption and heartbeat duration. The MG interface and the MGC can
communicate with each other normally only when the parameters of the MG interface attributes
are the same as the parameters of the MG interface attributes configured on the MGC.

9.7 Configuring the Attributes of the MG Interface (the MGCP Protocol)

9.8 Configuring the Software Parameters of an MG Interface (the H.248 Protocol)
The software parameters of an MG interface include parameters such as whether the MG
interface supports authentication during registration and whether the MG interface supports
standalone. After the configuration, the software parameters of the MG interface take effect on
the subscriber service processes on the MG interface.
9.9 Configuring the Software Parameters of an MG Interface (the MGCP Protocol)
The software parameters of an MG interface include parameters such as whether to maintain the
ongoing call if the MG interface and the MGC are disconnected and whether the MG interface
supports the dual-homing function. After the configuration, the software parameters of the MG
interface take effect on the subscriber service processes on the MG interface.
9.10 Configuring the Ringing Mode of an MG Interface
Configuring the ringing mode includes configuring the cadence ringing type and initial ringing
type. Configure the ringing mode of the MG interface to meet different requirements for the
ringing of different subscribers.
9.11 Configuring Digitmaps of the MG Interface (the H.248 Protocol)
The format of a digitmap is strictly defined by the H.248 protocol. A digitmap consists of strings
of characters with certain meanings. Configuring the digitmaps of the MG interface includes
configuring the inner telephone digitmap, emergency channel digitmap, automatic re-dial
digitmap, and overload emergency call digitmap of the MG interface.
9.12 Configuring Digitmaps of the MG Interface (the MGCP Protocol)
The format of a digitmap is strictly defined by MGCP. A digitmap consists of strings of
characters with certain meanings. Configuring the digitmaps of the MG interface includes
configuring the automatic re-dial digitmap and overload emergency call digitmap of the MG
interface.
9.13 Configuring the Overload Control of the MGC
The MGC processes the calls reported by multiple AGs that the MGC controls. If the traffic
volumes of multiple AGs increase, the MGC may be overloaded. When the MGC is overloaded,
the UA5000 can control the calls to ensure that the calls of subscribers with priority or emergency
are processed. Thus, the stability and the availability of the system are improved.
9.14 Configuring the Overload Control of the MG
If the traffic volume of the MG increases suddenly, the MG may be overloaded. When the MG
is overloaded, the UA5000 can control the calls to ensure that the calls of subscribers with priority
or emergency are processed. Thus, the stability and the availability of the system are improved.
9.15 Enabling an MG Interface
Enable an MG interface so that the MG interface negotiates with the MGC through the specified
media gateway control protocol and implements the registration on the MGC. Resetting the
interface enables the MG interface to register again on the MGC.

9.1 Introduction to the MG Interface

In the application of the next generation network (NGN), the UA5000 communicates with the
upper-layer MGC through the MG interface (the MG IP address and MG port number of the
MG interface). Each MG interface corresponds to one virtual access gateway (VAG).
Service Description
In the next generation network (NGN), the MG and media gateway controller (MGC) are
completely separated from each other. The MG converts the media format provided in one type
of network to the media format required in another type of network. The MGC controls the status
of a call related to the connection control for media channels in an MG.
In the NGN solutions of Huawei, the UA5000 functions as an MG and the softswitch functions
as an MGC. The MG interface data describes the interface and connection information between
the UA5000 and the MGC.
l You can configure a maximum of eight MG interfaces, namely, eight virtual access
gateways (VAGs), on one UA5000.
l The UA5000 supports the H.248 protocol and the media gateway control protocol (MGCP).
One UA5000 can use only one of the two protocols at the same time.
9.2 Configuration Example of the MG Interface (the H.248

Protocol)
Prerequisite
l The UA5000 must use the H.248 protocol.
l The IP address to be used in the example must already be configured in the IP address pool
through the ip address command.
l The data on the MGC side (corresponding to the data on the MG side) must be configured
correctly.
Precaution
l You can add a maximum of eight MG interfaces for one UA5000. If the UA5000 has eight
MG interfaces, adding the MG interface fails, and an error prompt is displayed.
l The UA5000 supports either the H.248 protocol or the MGCP protocol. If one UA5000
uses one protocol, all the MG interfaces on the UA5000 must also use this protocol. The
default protocol is H.248.
Data Plan
Table 9-1 provides the data plan for configuring the MG interface.

Table 9-1 Data plan for configuring the MG interface

Data Type Item Data
MG interface mgid 0
data
code text
transfer udp
protocol H.248
port MG: 2944

MGC: 2944
domainname UA5000.com
Standalone digitmap 1234xxxx
Emergency channel digitmap 110|119|999
IP addresses Media IP address of MG interface 0 on the UA5000 10.10.10.2/24
Signaling IP address of MG interface 0 on the 10.10.10.4/24

UA5000
The IP address of the MGC 10.10.20.1/24
Figure 9-1 shows the flowchart for configuring the MG interface.
Figure 9-1 Flowchart for configuring the MG interface

Start
Add an MG interface
(Optiona) (Optiona)
Configure Configure Configure
the MG the ring digitmaps of
interface mode of the the MG
attributes MG interface interface
Enable the MG interface
End

Procedure
Step 1 Add an MG interface.
Are you sure to add MG interface? (y/n)[n]:y
Step 2 Configure the MG interface attributes.

huawei(config-if-h248-0)#if-h248 attribute mgip 10.10.10.2 mgport 2944 code text
transfer udp domainName UA5000.com mgcip_1 10.10.20.1 mgcport_1 2944
mg-media-ip 10.10.10.4
huawei(config-if-h248-0)#display if-h248 attribute
---------------------------------------------------------------------
MGID 0
MG Description -
MG DomainName UA5000.com
Protocol H248
H248version Negotiated Originally 1
Profile Negotiation Para disable
Profile 0:NoProfile("")
2833Encrypt -
Codetype Text
Transmode UDP
HeartBeatTimer(s) 60
HeartBeatRetransTimes 3
HeartBeatRetransTimer(s) 60
MG signalling IP 10.10.10.2
MG signalling Port 2944
MG media IP 10.10.10.4
MIDType IP4_ADDR
DeviceName -
Active MGC MGC Port :2944 MGC IP:10.10.20.1

Active MGC MGC Domain Name:-
Standby MGC MGC Port :- MGC IP:-
Standby MGC MGC Domain Name:-
---------------------------------------------------------------------
Step 3 Configure the MG interface digitmap.

huawei(config-if-h248-0)#digitmap set inner 1234xxxx emergency
110|119|999
Step 4 Reset MG interface.

huawei(config-if-h248-0)#reset coldstart
Are you sure to reset MG interface?(y/n)[n]:y
huawei(config-if-h248-0)#
Reset MG interface 0 success!
Step 5 Query the status of MG interface.

huawei(config-if-h248-0)#quit
huawei(config)#display if-h248 all
-------------------------------------------------------------------------
MGID TransMode State MgPort MGIP/DomainName MgcPort MGCIP/DomainName
-------------------------------------------------------------------------
0 UDP Normal 2944 10.10.10. 2 2944 10.10.20.1
-------------------------------------------------------------------------
----End

Result
After the MG interface is configured successfully, it should be able to communicate with MGC
in the normal state.
9.3 Configuration Example of the MG Interface (the MGCP

Protocol)
Prerequisite
l The UA5000 must use the MGCP protocol.
l The IP addresses must be configured in the IP address pool.
l The data on the MGC side must be configured correctly.
Data Plan
Table 9-2 provides the data plan for configuring the MG interface.
Table 9-2 Data plan for configuring the MG interface

Data Type Item Data
MG interface data mgid 0
protocol MGCP
port MG: 2427

MGC: 2727
IP addresses The IP address of MG 10.10.10.2/24

interface 0 on the UA5000
Context
The different between the H.248-based MG interface and the MGCP-based MG interface is that
the MGCP-based MG interface does not support the isolation of the media stream and signaling
stream. Hence, the IP address of the media stream must be the same as the IP address of the
signaling stream (the same as the IP address of the MG interface), and the IP address of the
signaling stream must be added to the IP address pool in the system.
Figure 9-2 shows the flowchart for configuring the MG interface.

Figure 9-2 Flowchart for configuring the MG interface

Start
Add an MG interface
(Optiona) (Optiona)
Configure Configure Configure
the MG the ring digitmaps of
interface mode of the the MG
attributes MG interface interface
End
Procedure
huawei(config)#interface mgcp 0
Step 2 Configure the attributes of the MG interface.

huawei(config-if-mgcp-0)#if-mgcp attribute mgip 10.10.10.2 mgport 2427 domainName
UA5000.com mgcip_1 10.10.20.1 mgcport_1 2727
Step 3 Query the attributes of the MG interface.

huawei(config-if-mgcp-0)#display if-mgcp attribute
---------------------------------------------------------------------
MGID 0
Protocol MGCP
2833Encrypt -
Codetype Text
Transmode UDP
IP 10.10.10.2
Port 2427
HeartBeat Timer(s) 60
MGC[1] MGC PORT :2727 MGC IP:10.10.20. 1

MGC[1] MGC Domain Name:
MGC[2] MGC PORT :- MGC IP:-
MGC[2] MGC Domain Name:-
---------------------------------------------------------------------
Step 4 Reset the MG interface.

huawei(config-if-mgcp-0)#reset
Step 5 Query the status of the MG interface.

huawei(config)#display if-mgcp all
--------------------------------------------------------------------------
MGID State MGPort MGIP MGCPort MGCIP/DomainName
--------------------------------------------------------------------------
0 Normal 2427 10.10.10.2 2727 10.10.20.1
--------------------------------------------------------------------------
----End
Result
After the MG interface is configured successfully, it should be able to communicate with the
MGC in the normal state.
9.4 Adding an MG Interface

Add an MG interface to the UA5000 so that the UA5000 and the MGC can communicate with
each other through the MG interface.
Precaution
l You can add a maximum of eight MG interfaces for one UA5000. If the UA5000 has eight
MG interfaces, adding the MG interface fails, and an error prompt is displayed.
l The UA5000 supports either the H.248 protocol or the MGCP protocol. If one UA5000
uses one protocol, all the MG interfaces on the UA5000 must also use this protocol. The
default protocol is H.248.
l If the MG interface that supports the current system protocol exists, you cannot modify the
protocol. You can modify the protocol only after deleting the MG interface.
Procedure
Step 1 Run the display protocol support command to query the protocol used by the system.
Step 2 Configure the system protocol.

l If the protocol is different from the planned protocol, do as follows:
1. Run the undo interface h248 or undo interface mgcp command to delete the original
MG interface.
2. Run the protocol support command to set the protocol for the system.
l If the protocol is the same as the planned protocol, go to step 4.
Step 3 Run the reboot command to reboot the system and validate the protocol settings.

l When the H.248 protocol is used, run the interface h248 command to add an MG interface.
l When the MGCP protocol is used, run the interface mgcp command to add an MG interface.
----End

Example
To add an MG interface with MG ID 0 when the H.248 protocol is used, do as follows:
huawei(config)#display protocol support
System support H248 protocol
To add an MG interface with MG ID 0 when the MGCP protocol is used, do as follows:

huawei(config)#display protocol support
System support H248 protocol
huawei(config)#undo interface h248 0
huawei(config)#protocol support mgcp
Configure Protocol need save the data, then reboot the system. Are you sure to
change the protocol? (y/n)[n]:y
huawei(config)#save
huawei(config)#reboot system
Data is not saved, the unsaved data will lose if reboot system, are you sure
to reboot system? (y/n)[n]:y
huawei(config-if-mgcp-0)#
Related Operation
Table 9-3 lists the related operations for adding an MG interface.
Table 9-3 Related operations for adding an MG interface

Shut down an MG interface shutdown The shutdown type can be

graceful or force.
l graceful: If the active
calls exist on the MG
interface, the calls are
held. When the active
calls end or occur after the
set time, the MGC and the
MG are disconnected.
l The option force
indicates that all the calls
are released after the
MGC and the MG are
disconnected.
Restart an MG interface shutdown Run this command to restart

an MG interface that is shut
down.

Start an MG interface reset When an MG interface is

normal, run this command to
reset it. After modifying the
MG interface parameters,
reset the MG interface so that
it registers again with the
MGC.
Delete an MG interface undo interface h248 You cannot delete an MG

undo interface mgcp interface that is configured
with the subscriber data, or
an MG interface that
functions normally. That is,
you can delete only an MG
interface that is in the close
state or in the not start state.
Query the information about display if-h248 all Run this command to query
all the MG interfaces display if-mgcp all the configurations and the
current states of all the MG
interfaces in the global
config mode.
Query the MG interface display if-h248 attribute Run this command to query
attributes display if-mgcp attribute the configuration of an MG
interface in the MG interface
mode.
Query the status of an MG display if-h248 state Run this command to query
interface display if-mgcp state the current status of an MG
mode.

Add a ring mapping entry mg-ringmode add When the MGC interacts
with the UA5000, the ring
mode is negotiated. The ring
mapping involves mapping
the ring mode parameters
provided by the MGC and the
ring tones provided by the
UA5000.
The data packet sent to the
UA5000 by the MGC
contains the parameters of
the ring mode, which has the
same value as the value of
mgcpara.
The UA5000 searches the
ring mapping table for the
matching mgcpara to obtain
the cadence and initial ring
tones.
Modify a ring mapping entry mg-ringmode modify -
Delete a ring mapping entry mg-ringmode delete As the system supports only
16 ring mapping entries, you
can delete unnecessary
entries if required.
Query a ring mapping entry display mg-ringmode -

attribute

Configure digitmap timers digitmap-timer The H.248 protocol defines

three digitmap timers: long
timer (L), short timer (S), and
initial timer (T). Run the
digitmap-timer command to
set the timers to comply with
the standards in your country
or area.
l Long timer (L): If the MG
confirms that at least one
more digit needs to be
received to match a
dialing scheme in the
digitmap, the timer
between the digits is set as
the long timer.
l Short timer (S): If the
number string matches
with one dialing scheme
in the digitmap, but more
numbers may be received
and they match with other
dialing schemes, the
matching status should
not be reported
immediately. The MG
must use the short timer to
wait for receiving more
numbers.
l Initial timer (T): It is used
before any dialed
number. It is the duration
before the first digit is
received after offhook. If
the initial timer is set to 0
(namely, T = 0), the timer
fails. In this case, the MG
waits for other digits.
Switch the MGC forcibly mgc switch Use this command to forcibly
register the MG interface
with the new MGC.
Before the switchover, make
sure that the IP address and
port number of the secondary
MGC are configured in the
MG interface data.

9.5 Configuring the IP Address Pool

The IP address can be used for configuring the service only after the IP address is added to the
IP address pool successfully. By configuring the IP address pool, you can add the planned IP
address to the IP address pool.
Context
It is recommended that you plan the NMS configuration mode of the device before configuring
the IP address pool. Otherwise, changing the NMS configuration mode of the device
subsequently may interrupt the service.
Procedure
Step 1 Run the ip address command to add the IP address to the IP address pool.
Step 2 Run the display ip address command to query the information about the IP address pool in the
system.
----End
Example
To add the IP address 10.144.68.158 with the subnet mask of 255.255.255.0 and the gateway IP
address of 10.144.68.1 to the IP address pool, do as follows:
huawei(interface-eth)#ip address 10.144.68.158 255.255.255.0 10.144.68.1
huawei(interface-eth)#display ip address
Eth:
IPAddress............: 10.11.11.20
SubMask..............: 255.255.0.0
GateWay..............: 10.11.1.1
MacIndex.............: 0
MacAddress...........: 00-E0-FC-8B-77-77
VlanID...............: --
IPAddress............: 10.10.10.10
SubMask..............: 255.255.255.0
GateWay..............: 10.10.10.1
MacIndex.............: 0
MacAddress...........: 00-E0-FC-8B-77-77
VlanID...............: --
IPAddress............: 10.144.68.158
SubMask..............: 255.255.255.0
GateWay..............: 10.144.68.1
MacIndex.............: 0
MacAddress...........: 00-E0-FC-8B-77-77
VlanID...............: --
Related Operation
Table 9-4 lists the related operation for configuring the IP address pool.

Table 9-4 Related operation for configuring the IP address pool
Delete the IP address undo ip address -
9.6 Configuring the Attributes of the MG Interface (the H.

248 Protocol)
Prerequisite
l An MG interface must be added successfully. For details on how to configure an MG
interface, see "9.4 Adding an MG Interface."
l The required IP addresses must be configured in the IP address pool. For details on how to
configure an IP address, see "9.5 Configuring the IP Address Pool."
Context
l One UA5000 can be configured with a maximum of eight MG interfaces.
l The MG interface attributes configured on the UA5000 must be the same as the MG
interface attributes configured on the MGC.
l You can configure the following MG interface attributes as required:
– 2833 encryption key
– Coding mode
– MG interface description
– MG device name
– MG domain name
– Heartbeat duration
– Heartbeat retransmission interval
– Heartbeat retransmission times
– Media IP address
– Active and standby MGC domain name
– Active and standby MGC IP address
– Active and standby MGC port number
– Signaling IP address
– Signaling port number
– H.248 profile

– Profile negotiation identifier

– Transmission type
– Negotiation function of H.248 profile
Procedure
Step 1 In the global config mode, run the interface h248 command to enter the MG interface mode.
Step 2 Run the if-h248 attribute command to configure the MG interface attributes.
Step 3 Run the display if-h248 attribute command to query the MG interface attributes.
NOTE
The MG interface parameters are valid only for a specified MG interface.
----End
Example
The following example shows how to configure an MG interface. Table 9-5 provides the data
plan for configuring the MG interface attributes.
Table 9-5 Data plan for configuring the MG interface attributes

Parameter Value Parameter Value
mgid 0 mgip 10.10.10.2
mgport 2944 code text
transfer UDP domainName UA5000.com
mgcip_1 10.10.20.1 mgcport_1 2944
mgcip_2 10.11.10.1 mgcport_2 2944
mg-media-ip 10.10.10.4 protocol H.248
H248 profile Name: voice Profile negotiation disable

Index: 1 parameters
huawei(config)#load profile tftp 10.11.117.55 voice.fes

Whether to start loading? (y/n)[n]:y
Load(backup,duplicate,...) begins, please wait and notice the rate of progress
Any operation such as reboot or switchover will cause failure
and unpredictable result
! EVENT MAJOR 2007-11-25 12:33:18 ALARM NAME :Load start
PARAMETERS :FrameID: 0, SlotID: 5, Load type: Profile file
huawei(config)#
! EVENT MAJOR 2007-11-25 12:33:24 ALARM NAME :Load complete
PARAMETERS :FrameID: 0, SlotID: 5, Load type: Profile file
huawei(config-if-h248-0)#if-h248 attribute mgip 10.10.10.2 mgport 2944
code text transfer udp domainName UA5000.com mgcip_1 10.10.20.1 mgcport_1 2944
mgcip_2 10.11.10.1 mgcport_2 2944 mg-media-ip 10.10.10.4 profile-index 1
profile-negotiation disable


---------------------------------------------------------------------
MGID 0
MG Description -
Protocol H248
Profile 1:Resv1("")
2833Encrypt -
Codetype Text
Transmode UDP
MIDType IP4_ADDR
DeviceName -

Standby MGC MGC Port :2944 MGC IP:10.11.10.1
---------------------------------------------------------------------
NOTE
l The coding mode can be text or binary. H.248 supports only the text coding mode.
l The transmission mode supports only the user datagram protocol (UDP). The transmission control protocol
(TCP) is not supported.
l The MGC information includes the MGC IP address, port number at the transport layer on the MGC side,
and MGC domain name. In the case of the MGC IP address and the MGC domain name, you must specify
one of them. To implement the MGC domain name resolution, you must run the dns command in the global
config mode to start a domain name system (DNS) client on the UA5000.
Related Operation
Table 9-6 lists the related operations for configuring the MG interface attributes.

Table 9-6 Related operations for configuring MG interface attributes


graceful or force.
l The option graceful
indicates that the active
calls are held after the
MGC and the MG are
disconnected. After the
set time, the MG and the
MGC are disconnected.
l The option force
MGC and the MG are
disconnected.
Enable an MG interface reset When an MG interface is

MGC.
Delete an MG interface undo interface h248 You cannot delete an MG

interface that is configured
with subscriber data or an
MG interface that is in use.
Query the information about display if-h248 all Run this command to query
all the MG interfaces the configurations and the
config mode.
Query the attributes of an display if-h248 attribute Run this command to query
MG interface the configuration of an MG
mode.
Query the status of an MG display if-h248 state Run this command to query
interface the current status of an MG
mode.

UA5000.
UA5000 by the MGC
contains a ring mode, which
has the same value as the
value of mgcpara.
tones.

attribute


timer (L), short timer (S) and
or area.
digit is to be received to
match a dialing scheme in
the digitmap, the MG
waits for the digits with
the long timer.
not be reported
immediately. The MG
numbers.
before any dialed
number. It is the duration
before the first digit is
received after offhook. If
the initial timer is set as 0
(namely, T = 0), the timer
fails. In this case, the MG
waits for other digits
indefinitely.
Switch the MGC forcibly mgc switch Run this command to force
the MG interface to register
with the new MGC.
MG interface data.

9.7 Configuring the Attributes of the MG Interface (the

MGCP Protocol)
Prerequisite
l The system must use the MGCP protocol.
l An MG interface must be added successfully. For details on how to configure an MG
interface, see "9.4 Adding an MG Interface."
l The IP addresses must be configured in the IP address pool. For details on how to configure
an IP address, see "9.5 Configuring the IP Address Pool."
Context
l One UA5000 can be configured with a maximum of eight MG interfaces.
l The MG interface attributes configured on the UA5000 must be the same as the MG
interface attributes configured on the MGC.
l You can configure the following MG interface attributes as required:
– 2833 encryption key
– MG domain name
– Heartbeat interval
– MG interface name
– MGC IP address
– MGC domain name
– MGC port number
– IP address of the MG interface
– Port number of the MG interface
Procedure
Step 1 In the global config mode, run the interface mgcp command to enter the MG interface mode.
Step 2 Run the if-mgcp attribute command to configure the MG interface attributes.
Step 3 Run the display if-mgcp attribute command to query the MG interface attributes.
NOTE
The MG interface parameters are valid only for the current MG interface.
----End

Example
The following example shows how to configure an MG interface. Table 9-7 provides the data
plan for configuring an MG interface.
Table 9-7 Data plan for configuring an MG interface

mgid 0 mgip 10.10.10.2
mgport 2944 domainName UA5000.com
mgcip_1 10.10.20.1 mgcport_1 2727
mgcip_2 10.11.10.1 mgcport_2 2727
protocol MGCP description aaln
huawei(config-if-mgcp-0)#if-mgcp attribute mgip 10.10.10.2 mgport 2427
domainName UA5000.com desc aaln mgcip_1
10.10.20.1 mgcport_1 2727 mgcip_2 10.11.10.1 mgcport_2 2727
huawei(config-if-mgcp-0)#display if-mgcp attribute
------------------------------------------------------------
MGID 0
MG description aaln
Protocol MGCP
2833Encrypt -
Codetype Text
Transmode UDP
IP 10.10.10.2
Port 2427
HeartBeat Timer(s) 60
MGC[1] MGC PORT :2727 MGC IP:10.10.20.1
MGC[2] MGC PORT :2727 MGC IP:10.11.10.1
------------------------------------------------------------
Related Operation
Table 9-8 lists the related operations for configuring the MG interface attributes.

Table 9-8 Related operations for configuring MG interface attributes


graceful or force.
l The option graceful
indicates that the active
calls are held after the
MGC and the MG are
disconnected. After the
set time, the MG and the
MGC are disconnected.
l The option force
MGC and the MG are
disconnected.
Enable an MG interface reset When an MG interface is

MGC.
Delete an MG interface undo interface mgcp You cannot delete an MG

interface that is configured
with the subscriber data or an
MG interface that is in use.
Query the information about display if-mgcp all Run this command to query
all the MG interfaces the configurations and the
config mode.
Query the MG interface display if-mgcp attribute Run this command to query
attributes the configuration of an MG
mode.
Query the status of an MG display if-mgcp state Run this command to query
interface the current status of an MG
interface in MG interface
mode.

UA5000.
UA5000 by the MGC
contains a ring mode, which
has the same value as the
value of mgcpara.
tones.

attribute
Configure digitmap timers digitmap-timer The T timer is used to match

a timer expiry.
Switch the MGC forcibly mgc switch Run this command to force
the MG interface to register
with the new MGC.
MG interface data.
9.8 Configuring the Software Parameters of an MG Interface

(the H.248 Protocol)
The software parameters of an MG interface include parameters such as whether the MG
interface supports authentication during registration and whether the MG interface supports
standalone. After the configuration, the software parameters of the MG interface take effect on
the subscriber service processes on the MG interface.

Prerequisite
l The system must use the H.248 protocol.
l The MG interface must be added successfully.
Context
With different software parameters of the MG interface, you can select whether to perform the
following operations:
l Configure the MG interface to support the dual homing.

l Configure the MG interface to register with the MGC with a wildcard.
l Configure the MG interface to support authentication.
l Configure the MG interface to support the authentication header.
l Configure the MG interface to support the standalone service.
l Configure the filter switch of the media stream source port.
l Configure the filter timer length of the media stream source port.
l Configure the parameter for reporting the P2P fault.
l Configure the parameter for reporting the P2MP fault.
l Configure the type of the prompt tone after the MG and the MGC are disconnected.
Procedure
Step 2 Run the mg-software parameter command to configure the software parameters of the MG
interface.
Step 3 Run the display mg-software parameter command to query the software parameters of the
MG interface.
NOTE
The software parameters are valid only for the current MG interface.
----End
Example
To configure the software parameters of the MG interface so that the MG interface supports the
dual homing and does not support the standalone service, do as follows:
huawei(config-if-h248-0)#mg-software parameter 2 1
huawei(config-if-h248-0)#display mg-software parameter 2
---------------------------------------------------------------------
Interface Id:1 para index:2 value:1
---------------------------------------------------------------------
APPENDIX:
---------------------------------------------------------------------
Interface software parameter name:
2: The selections of the MG interface dual-homing
0: Do not support the dual-homing
1: Support the dual-homing, but do not support the auto switchover
2: Support the dual-homing and auto switchover

9.9 Configuring the Software Parameters of an MG Interface

(the MGCP Protocol)
The software parameters of an MG interface include parameters such as whether to maintain the
ongoing call if the MG interface and the MGC are disconnected and whether the MG interface
supports the dual-homing function. After the configuration, the software parameters of the MG
interface take effect on the subscriber service processes on the MG interface.
Prerequisite
l The system must use the MGCP protocol.
Context
With different software parameters of the MG interface, you can select whether to perform the
following operations:
l Configure the MG to hold the active calls when the MG is disconnected from the MGC.
l Configure the MG interface to support the dual homing.
l Configure the MG interface to shut down the heartbeat.
l Configure the MG interface to register with the MGC with a wildcard.
l Configure the MGC type for the MG interface.
l Configure the heartbeat-no-reply threshold.
l Configure the MG interface to report heartbeat notification with the MG as the endpoint
name.
l Configure the parameter for reporting the P2P fault
l Configure the parameter for reporting the P2MP fault
Procedure
Step 2 Run the mg-software parameter command to configure the software parameters of the MG
interface.
Step 3 Run the display mg-software parameter command to query the software parameters of the
MG interface.
NOTE
The software parameters are valid only for the current MG interface.
----End
Example
To configure the software parameters of an MG interface so that the active calls are held after
the MGC and MG are disconnected, do as follows:
huawei(config-if-mgcp-0)#mg-software parameter 1 1

huawei(config-if-mgcp-0)#display mg-software parameter 1

-------------------------------------------------
-------------------------------------------------
APPENDIX:
-------------------------------------------------
Interface soft parameter name:
1: Whether MG hold the existent call when connection between MGC and MG is
broken
0 : Hold the existent call
1 : Disconnect all call and release resource
9.10 Configuring the Ringing Mode of an MG Interface

Configuring the ringing mode includes configuring the cadence ringing type and initial ringing
type. Configure the ringing mode of the MG interface to meet different requirements for the
ringing of different subscribers.
Prerequisite
The MG interface must be added successfully.
Context
l If the system defined ring modes can meet the subscriber requirements, you can select the
required ring modes and configure the ring mapping.
l If the system defined ring modes cannot meet the subscriber requirements, you can
customize ring modes and configure the ring mapping.
Precaution
The mgcpara parameter on the MG must be the same as the mgcpara parameter configured on
the MGC.
Procedure
Step 1 Run the system parameters command to configure the stop initial ringing flag.
NOTE
l If the initial ringing and the cadence ringing are in different cadence ratios, perform step 1. If they are
in the same cadence ratio, skip step 1.
l To use user defined ring modes, perform steps 2-3. To use system defined ring modes, perform step 4.
Step 2 Run the user defined-ring modify command to configure a user defined ring.
Step 3 Run the display user defined-ring command to display the user defined ring modes.
Step 4 Enter the MG interface mode.

1. When the H.248 protocol is used, run the interface h248 command to enter the MG
interface mode.
2. When the MGCP protocol is used, run the interface mgcp command to enter the MG
interface mode.
Step 5 Run the mg-ringmode add command to add a ring mapping entry.

Step 6 Run the display mg-ringmode attribute command to query a ring mapping entry.
----End
Example
To configure the ring for an MG interface, do as follows:
l MG ID: 0
l MGC peer parameter ID: 0
l Cadence ring: 1:4
l Initial ring: 1:2
huawei(config)#system parameters 3 1
huawei(config-if-h248-0)#mg-ringmode add 0 0 17
huawei(config-if-h248-0)#display mg-ringmode attribute
-------------------------------------------------------
MGID PeerParameter CadenceRinging InitialRinging
-------------------------------------------------------
0 0 0 17
-------------------------------------------------------
To configure a ring mode for an MG interface, do as follows:

l MG ID: 0
l Peer parameter ID: 0
l User-defined ring 0: 0.4s On, 0.2s Off, 0.4s On, 2.0s Off
l Initial ring: user-defined ring 0
l Cadence ring: user-defined ring 0
huawei(config)#user defined-ring modify 0 para1 400 para2 200 para3 400 para4 2000
huawei(config)#display user defined-ring
--------------------------------------------------
RingType Para1 Para2 Para3 Para4 Para5 Para6
--------------------------------------------------
0 400 200 400 2000 0 0
1 0 0 0 0 0 0
2 0 0 0 0 0 0
3 0 0 0 0 0 0
4 0 0 0 0 0 0
5 0 0 0 0 0 0
6 0 0 0 0 0 0
7 0 0 0 0 0 0
8 0 0 0 0 0 0
9 0 0 0 0 0 0
10 0 0 0 0 0 0
11 0 0 0 0 0 0
12 0 0 0 0 0 0
13 0 0 0 0 0 0
14 0 0 0 0 0 0
15 0 0 0 0 0 0
--------------------------------------------------
huawei(config-if-h248-0)#mg-ringmode add 1 128 144
huawei(config-if-h248-0)#display mg-ringmode attribute
-------------------------------------------------------
MGID PeerParameter CadenceRinging InitialRinging

-------------------------------------------------------
0 1 128 144
-------------------------------------------------------
NOTE
The user defined ring mode 0–15 corresponds with cadence ring modes 128–143 and initial ring modes
144–159. For example, to use the user defined ring mode 0 as the cadence ring mode, select 128. To use
the user defined ring mode 0 as the initial ring mode, select 144.
9.11 Configuring Digitmaps of the MG Interface (the H.248

Protocol)
The format of a digitmap is strictly defined by the H.248 protocol. A digitmap consists of strings
of characters with certain meanings. Configuring the digitmaps of the MG interface includes
configuring the inner telephone digitmap, emergency channel digitmap, automatic re-dial
digitmap, and overload emergency call digitmap of the MG interface.
Prerequisite
Specifications
Table 9-9 shows the valid characters in the strings and their meanings in the H.248 protocol.
Table 9-9 Description of the characters in H.248 digitmap
Character Meaning
0-9 -
A-D -
E It stands for * in the DTMF mode.
F It stands for # in the DTMF mode.
X It stands for a wildcard, indicating any digit from 0 to 9.
T It stands for a start timer used before any dialed number.
S Short timer. If the dialed number string matches with one dialing scheme in
the digitmap, but more numbers may be received and they match with other
dialing schemes, the matching status should not be reported immediately. The
MG must use the short timer to wait for receiving more numbers.
L Long timer. If the MG ensures that at least one more number is required to
match with any dialing scheme in the digitmap, the timer value between the
numerals should be set as long timer.
Z Duration modifier. It indicates a dialing event of a long duration. It precedes

the event character with a fixed location. When the event duration exceeds
the threshold, the dialing event fills the location.
. It indicates that there can be zero or many characters before it.

Character Meaning
| It is used to divide a string into several strings, and each string is a dialing
scheme.
[] It indicates that one digit or string can be selected among the options.
NOTE
l When you configure the re-dial digitmap for the card service when the MG interface uses the H.248
protocol, E stands for * and F stands for #. For example, to set the re-dial digitmap for the card service
to ##, you need to set the dualdialdigitmap to FF.
l The time length of the start timer on the UA5000 must be consistent with the configuration on the
SoftSwitch.
Procedure
Step 2 Run the digitmap set command to configure digitmaps for the services.
Step 3 Run the display digitmap command to query the settings of the digitmaps.
----End
Example
To configure the digitmap for internal calls as 1234xxxx, and the digitmap for emergency
channel as 110|119|999, do as follows:
huawei(config-if-h248-0)#digitmap set inner 1234xxxx emergency 110|119|999
huawei(config-if-h248-0)#display digitmap
-----------------------------------------------------------------------------
Inner digitmap : 1234xxxx
Emergency digitmap : 110|119|999
Urgent digitmap (for overload or bandwidth restrict) : -
Dualdial digitmap for card service : -
-----------------------------------------------------------------------------
Related Operation
Table 9-10 lists the related operations for configuring the digitmaps.
Table 9-10 Related operations for configuring the digitmaps (based on H.248)
Clear a digitmap digitmap clear -


timer (L), short timer (S) and
or area.
digit is to be received to
match with a dialing
scheme in the digitmap,
the MG waits for the digits
with the long timer.
not be reported
immediately. The MG
numbers.
before any dialed number.
It is the duration before
the first digit is received
after offhook. If the initial
timer is set as 0 (T = 0), the
timer fails. In this case, the
MG waits for other digits
indefinitely.
9.12 Configuring Digitmaps of the MG Interface (the MGCP

Protocol)
The format of a digitmap is strictly defined by MGCP. A digitmap consists of strings of
characters with certain meanings. Configuring the digitmaps of the MG interface includes
configuring the automatic re-dial digitmap and overload emergency call digitmap of the MG
interface.

Prerequisite
An MG interface must be added successfully.
Specifications
Table 9-11 shows the valid characters in the strings and their meanings in the MGCP protocol.
Table 9-11 Description of the characters in MGCP digitmaps
Character Meaning
0-9 -
A-D -
X It stands for a wildcard, indicating any digit from 0 to 9.
T It indicates that the timer timeout is detected. That is, if there is still a number
after the dialing scheme is matched with, the system reports the number digit
by digit.
* It stands for * in DTMF mode.
# It stands for # in DTMF mode.
. It indicates that there can be zero or many characters before it.
| It is used to divide a string into several strings, and each string is a dialing
scheme.
[] It indicates that one digit or string can be selected among the options.
NOTE
The time length of the start timer on the UA5000 must be consistent with the configuration on the
SoftSwitch.
Procedure
Step 2 Run the digitmap set command to configure digitmaps for services.
Step 3 Run the display digitmap command to query the settings of the digitmap.
----End
Example
To configure the automatic re-dial digitmap for the card service to ##, do as follows:
huawei(config-if-mgcp-0)#digitmap set dualdial ##
huawei(config-if-mgcp-0)#display digitmap
-----------------------------------------------------------------------------
Dualdial digitmap for card service : ##

System urgent digitmap (for overload or bandwidth restrict) : -

-----------------------------------------------------------------------------
Related Operation
Table 9-12 lists the related operations for configuring the digitmap.
Table 9-12 Related operations for configuring the digitmap (based on MGCP)
Clear a digitmap digitmap clear -
Configure digitmap timers digitmap-timer The T timer is used to match

with a timer expiry.
9.13 Configuring the Overload Control of the MGC

The MGC processes the calls reported by multiple AGs that the MGC controls. If the traffic
volumes of multiple AGs increase, the MGC may be overloaded. When the MGC is overloaded,
the UA5000 can control the calls to ensure that the calls of subscribers with priority or emergency
are processed. Thus, the stability and the availability of the system are improved.
Prerequisite
l The data on the MGC side must be configured successfully.
l An MG interface must be added successfully.
Context
The MGC overload means that when the MGC has a large number of tasks to process, the CPU
usage of the MGC increases, and the MGC cannot ensure normal calls. In this case, to solve this
problem, the UA5000 limits the calls through different levels of priorities.
In a network, the MGC or the MG may be overloaded. That is, either the MGC or the MG is
overloaded, or both are overloaded. When either device is overloaded, the remote device should
support and work with the other device.
The user levels corresponding to the parameters for controlling the MGC overload are as follows:
l t3: The customized user at the highest level, that is, the user of urgent calls
l t2: The customized user at the second highest level, that is, the user of cat1 and cat2 calls
l t1: The customized user at the common level, that is, the user of cat3 calls
NOTE
Cat1, cat2, and cat3 are the priority levels of the user terminal. Cat1 has the highest priority, and cat3 has
the lowest priority.
Precaution
The MGC overload control cannot be disabled.

Procedure
Step 1 Run the mgc-overload-control parameters set command to configure the maximum call
throughput of the calls at different levels for the MG interface.
Step 2 Run the display mgc-overload-control parameters command to query the maximum call
throughput of the calls at different levels for the MG interface.
----End
Example
To configure the parameters for the MGC overload control to meet the following requirements,
l The user-defined call throughput threshold at the highest level is 20 offhook/s.

l The user-defined call throughput threshold at the second highest level is 15 offhook/s.
l The user-defined call throughput threshold at the common level is 10 offhook/s.
l The leaky bucket throughput is 25 offhook/s.
l The network busy tone after the call is intercepted by the bucket is an announcement.
do as follows:
huawei(config-if-h248-0)#mgc-overload-control parameters set t3 20 t2 15 t1 10
maxAdmitRate 25 throttlingCallTreat 2
huawei(config-if-h248-0)#display mgc-overload-control parameters
-----------------------------------------------------------------------------
Threshold for the calling channel at the highest level :20
Threshold for the calling channel at the less-higher level:15
Threshold for the calling channel at the ordinary level :10
The maximum pass rate of the leaky bucket :25.00
When the calling is rejected by the leaky bucket, the system prompts busy tone
of the user network: 2
-----------------------------------------------------------------------------
APPENDIX:
-----------------------------------------------------------------------------
When the calling is rejected by the leaky bucket, the system prompts busy tone
of the user network:
1:EET
2:Announcement
-----------------------------------------------------------------------------
9.14 Configuring the Overload Control of the MG

If the traffic volume of the MG increases suddenly, the MG may be overloaded. When the MG
is overloaded, the UA5000 can control the calls to ensure that the calls of subscribers with priority
or emergency are processed. Thus, the stability and the availability of the system are improved.
Prerequisite
An MG interface must be added successfully.
Context
The MG overload means that when the MG has a large number of tasks to process, the CPU
usage of the MG increases, and the MG cannot ensure normal calls. In this case, to solve this
problem, the UA5000 limits calls to control the traffic when the CPU of the MG is overloaded.

In a network, the MGC or the MG may be overloaded. When either is overloaded, or both are
overloaded, the cooperation and the support of the remote device are required.
Precaution
l The MG overload control takes effect only for PSTN subscribers and ISDN subscribers
(including ISDN PRA subscribers, ISDN BRA subscribers, DPNSS subscribers, and
DASS2 subscribers).
l The UA5000 does not implement the overload processing for the onhook of ISDN
subscribers.
Procedure
Step 1 Configure the MG overload control parameters.
l Run the mg-overload-control originating-call command to set the offhook overload control
parameters for the system.
l Run the mg-overload-control call-clear command to set the onhook overload control
l Run the mg-overload-control terminating-call command to set the callee overload control
NOTE
In general, use the system defaults to set the MG overload control parameters.
Step 2 Run the display mg-overload-control command to query the MG overload control parameters.
Step 3 Run the mg-overload-control set command to enable the function of offhook overload control
and callee overload control, and configure the corresponding minimum CPU usage for the
restriction level overload.
NOTE
Use the default value 70 to set the corresponding minimum CPU usage for the restriction level overload.
Run the power-dialer-control set command to set the detection, detection cycle, number of detection
events in each cycle and the recovery time for malicious subscribers.
----End
Example
Table 9-13 provides the data plan for configuring the MG overload control parameters. The
values of other parameters are the system default values.
Table 9-13 Data plan for configuring the MG overload control parameters
Type Pararemeter Value
originating-call threshold1 25
threshold2 30
initleakrate 6
call-clear threshold 30

Type Pararemeter Value
initleakrate 10
terminating-call threshold 30
initleakrate 10
huawei(config)#mg-overload-control originating-call threshold1

25 threshold2 30 initleakrate 6
huawei(config)#mg-overload-control call-clear threshold 30 initleakrate
10
huawei(config)#mg-overload-control terminating-call threshold 30
initleakrate 10
huawei(config)#display mg-overload-control all
------------------------------------------------------------
Originating Call threshold1 25
Originating Call threshold2 30
Originating Call initleakrate 6
Originating Call adjustfactor 20
Originating Call resume time length 30(s)
------------------------------------------------------------
Terminating Call threshold 30
Terminating Call initleakrate 10
Terminating Call adjustfactor 20
Terminating Call resume time length 30(s)
------------------------------------------------------------
Mass Call Clear threshold 30
Mass Call Clear initleakrate 10
Mass Call Clear adjustfactor 20
Mass Call Clear resume time length 30(s)
------------------------------------------------------------
huawei(config)#mg-overload-control set originating-call-switch enable
call-clear-switch enable
9.15 Enabling an MG Interface

Enable an MG interface so that the MG interface negotiates with the MGC through the specified
media gateway control protocol and implements the registration on the MGC. Resetting the
interface enables the MG interface to register again on the MGC.
Prerequisite
l An MG interface must be added successfully.
l The data on the MG and the data on the MGC must be configured properly.
Precaution
l After adding an MG interface or modifying the MG interface parameters, you need to reset
the MG interface to validate the parameter configuration.
l Enabling an MG interface interrupts the ongoing services on the interface. Therefore,
exercise caution when enabling an MG interface.
Procedure
Step 1 Enter the MG interface mode

1. When the H.248 protocol is used, run the interface h248 command to enter the MG
interface mode.
2. When the MGCP protocol is used, run the interface mgcp command to enter the MG
interface mode.
Step 2 Run the reset command to reset the MG interface to enable it.
----End
Example
To reset the MG interface with MG ID 0 when the UA5000 uses the H.248 protocol, do as
follows:

Configuration Guide-PVM CLI 10 Configuring the VoIP Service
10 Configuring the VoIP Service
About This Chapter
Configuring the VoIP service includes the application of the VoIP technology and the related
process for configuring the VoIP service of the UA5000.
10.1 Introduction to the VoIP Service

The voice over IP (VoIP) service uses the voice compression technology and transmits the voice
service over the IP network.
10.2 Configuration Example of the VoIP Service
This topic describes how to configure the VoIP service by accessing the voice service through
the A32 service board and accessing the IP network through the PVMB control board.
10.3 Configuration Example of the VoIP Service (in Integrated Upstream Mode)
the A32 service board and accessing the IP network through the IPM control board.
10.4 Configuring the Standalone Service
Configure the standalone service of the UA5000. Thus, when the UA5000 is disconnected from
the MGC, the subscribers connected to a same VAG can still communicate with each other.
10.5 Configuring the System Parameters
Configure the parameters such as the sending howler tone flag, overseas flag, and consistency
test flag of the UA5000 by configuring the global system parameters. Thus, the use of the
subscriber terminal complies with the local standard.
10.6 Configuring the POTS Subscriber Data and Port Attributes
After configuring the MG interface successful, you can add POTS subscribers on the MG
interface by configuring the POTS subscriber data and port attributes. Thus, the function of the
communication between POTS subscribers can be implemented.
10.7 Configuring the QoS IP Precedence
Configuring the QoS IP precedence means configuring the different QoS IP precedences for the
signaling, media, and maintenance packets to meet different requirements for the delay and jitter
of different services.
10.8 Configuring the QoS VLAN Priority

Configuring the QoS VLAN priorities means configuring the different QoS VLAN priorities for
the signaling, media, and maintenance packets. Thus, the QoS priorities of the service traffic
streams can be controlled according to the VLAN priorities.
10.9 Separating the Signaling IP Address from the Media IP Address
Separating the signaling IP address from the media IP address means configuring two different
IP addresses as the media IP address and signaling IP address. Thus, the media stream and
signaling stream are transmitted through different paths in the network.
10.10 Enabling the Voice Quality Enhanced Function
Enabling the voice quality enhanced function includes enabling the automatic gain adjustment
and background noise suppression functions so that the voice service is of better quality when
there is noise.

10.1 Introduction to the VoIP Service

The voice over IP (VoIP) service uses the voice compression technology and transmits the voice
service over the IP network.
Service Description
The VoIP service uses the IP packet switched network for transmission after the analog voice
signals are specially processed, such as compressed and packetized. In this manner, the voice
signals can be transmitted through the connectionless User Datagram Protocol (UDP).
Currently, the VoIP has the following three types:
l PC to PC: The subscribers are mainly teenagers.

l PC to phone: The subscribers are mainly young people (such as oversea students). These
subscribers are sensitive to the communication price.
l Phone to phone: The subscribers use the traditional telephones. The carrier provides the
voice service over the NGN softswitch network.
The UA5000 provides the voice service through the voice service boards. Table 10-1 shows the
number of ports provided by each type of service boards.
Table 10-1 Number of ports provided by each type of service boards
Board Type Number of Ports Remarks
ASL 16 16-port POTS service board
A32 32 32-port POTS service board
10.2 Configuration Example of the VoIP Service

the A32 service board and accessing the IP network through the PVMB control board.
Prerequisite
l The master shelf must be added successfully. In this example, the H601HABD functions
as the master shelf.
l The network management port must be configured properly, and you can telnet to the
PVMB control board. For the procedure for configuring the network management port, see
"4 Configuring the NMS."
l The IP addresses used in this example must be configured in the IP address pool. The media
IP address and the signaling IP address are different.
l The data on the MGC (namely, the data corresponding to the data configured on the MG)
must be configured properly.

l The data on the MG interface must be configured properly. For detailed operations, see
"9 Configuring the MG Interface."
Networking
Figure 10-1 shows the example network of the VoIP service.
NOTE
This example considers the PVMB control board as an example. The configuration of the PVMD control board
is the same as the configuration of the PVMB control board. Therefore, the configuration of the PVMD control
is not described here.
Figure 10-1 Example network of the VoIP service
MGC
10.10.20.1/24
Router
10.10.10.1/24
H.248
0/11
P P A
UA5000
V V 3
10.10.10.2/24
M M
2
B B
Phone1 Phone32
Data Plan
Table 10-2 provides the data plan for configuring the VoIP service on the PVMB control board.
Table 10-2 Data plan for configuring the VoIP service on the PVMB control board
Data Type Item Data
code text
protocol H.248

Data Type Item Data
tranfer UDP
port MG: 2944

MGC: 2944
start-negotiate-version 2
NOTE
The parameter value must be the
same as the H.248 version on the
MGC.
IP addresses Signaling IP address of MG 10.10.10.2/24

Media IP address of MG 10.10.10.4/24

Default gateway of MG 10.10.10.1/24

IP address of the MGC 10.10.20.1/24
Telephone numbers Phone 1-phone 32 Shelf ID/Slot ID: 0/11

Telephone numbers:
12340001-12340032
terminal id 0-31, where terminals 0-31

correspond to telephone numbers
12340001-12340032.
ToS (type of service) IP priority and ToS priority System default value
strategy
Voice enhancing function The automatic gain control Supported

(AGC) function of the PSTN
port
The AGC level of the PSTN 15 (-24 dBm0)

port
The spectral noise Supported

suppression (SNS) function
of the PSTN port
The SNS level of the PSTN 20 (20 dB)

port
Context
l The MG interface parameters must be the same as the parameters configured on the MGC.
l Use the cadence ring tone and initial ring tone defined in the local standard.

Figure 10-2 shows the flowchart for configuring the VoIP service.
Figure 10-2 Flowchart for configuring the VoIP service

Start
Add shelves
Add boards Configure

hardware data
Confirm boards
Configure IP
Configure IP addresses addresses
Add MG interfaces
Configure an MG interface Configure MG interface

data
Configure Configure software

protocol data Configure POTS subsciber data parameters
(Optional) (Optional)
Configure Configure Configure (Optional)
Configure Configure (Optional)
POTS common software Configure
MGCP H.248 Configure
subscriber attributes parameters of system
protocol protocol SPCs
data of the PORT the MG parameters
parameters parameters
subscribers interface
End
Procedure
l Procedure (for IPMB)
NOTE
In this example, the system uses the independent upstream mode. The A32 service board provides
the interface for accessing the voice service. The voice signals are transmitted directly to the upper-
layer network after being processed by the PVMB control board. Therefore, you need not configure
the IPMB board.
l Procedure (for PVMB)
1. Configure the IP address of the service network port.
huawei(config)#interface eth
huawei(interface-eth)#ip modify 10.10.10.10 ip_address 10.10.10.2 gateway
10.10.10.1 submask 255.255.255.0 vlan_tag 1001
/When the device is configured with the IP address of the service network
port, whereas the IP address, subnet mask, gateway, or vlantag of the
current
service network port on the device is inconsistent with the requirement of
the actual data plan, run this command to modify the parameters./
/If no IP address is added to the current IP address pool of the device,
run the ip address command to add the media IP address and signaling IP
address to the IP address pool./

vlan_tag 1001
Eth:
IPAddress ..........: 10.10.10.2
SubMask.............: 255.255.255.0
GateWay.............: 10.10.10.1
MacIndex............: 0
MacAddress..........: 00-E0-FC-44-16-57
VlanID .............: 1001
IPAddress ..........: 10.10.10.4

SubMask.............: 255.255.255.0
GateWay.............: 10.10.10.1
MacIndex............: 0
MacAddress..........: 00-E0-FC-44-16-57
VlanID .............: --
2. Configure the QoS (quality of service) IP strategy.

huawei(interface-eth)#quit
huawei(config)#qos ip 10.10.10.2 strategy none
3. Configure the working mode of the PVMB board as alone.

In this networking mode, the PVM control board provides services independently, and
the voice service is transmitted upstream through the ETH port on the PVM board.
huawei(config)#working mode alone
4. Add A32 service board to the shelf and confirm the board.
huawei(config)#display board 0
-------------------------------------------------------------------------
SlotID BoardName Status Sub0 Sub1 Online/Offline
-------------------------------------------------------------------------
0 PWX2 Normal
1 PWX2 Normal
2
3
4 H601PVMB Standby_normal H602ETCA
5 H601PVMB Active_normal H602ETCA H602ETCM
......
11 A32 Normal
......
35
-------------------------------------------------------------------------
5. Configure the MG interface attributes.

code text transfer udp domainName UA5000.com mgcip_1 10.10.20.1
mgcport_1 2944 mg-media-ip 10.10.10.4 start-negotiate-version 2
---------------------------------------------------------------------
MGID 0
MG Description -
Protocol H248
Profile Negotiation Para enable
Profile 1:Resv1("")
2833Encrypt -
Codetype Text
Transmode UDP

MIDType IP4_ADDR
DeviceName -

---------------------------------------------------------------------
6. Configure H.248 protocol parameters (enable the three-way handshake signal switch
of the H.248 protocol stack.)
huawei(config-if-h248-0)#h248stack tr responseackctrl true
huawei(config-if-h248-0)#display h248stack tr
---------------------------------------------------------------------
three way handshake : true
longtimer(units: ms) : 30000
provtimer(units: ms) : 8000
retransfailoption : max retransfer times
maxretranstimes : 7
retransmode : auto
maxretranstimerval(units: ms) : 4000
minretranstimerval(units: ms) : 1000
---------------------------------------------------------------------
7. Enable the MG interface again.
8. Query whether the state of the MG interface is normal.
-------------------------------------------------------------------------
-------------------------------------------------------------------------
0 UDP Normal 2944 10.10.10.2 2944 10.10.20.1
-------------------------------------------------------------------------
9. Configure the telephone numbers of the subscribers.
huawei(config)#esl user
huawei(config-esl-user)#mgpstnuser batadd 0/11/0 0/11/31 0 terminalid 0
telno 12340001
huawei(config-esl-user)#display mgpstnuser 0/11
--------------------------------------------------------
Frame/Slot/Port MGID TelNo Priority TID
--------------------------------------------------------
0 / 11 / 0 0 12340001 Cat3 A0
0 / 11 / 1 0 12340002 Cat3 A1
0 / 11 / 2 0 12340003 Cat3 A2
0 / 11 / 3 0 12340004 Cat3 A3
0 / 11 / 4 0 12340005 Cat3 A4
0 / 11 / 5 0 12340006 Cat3 A5
0 / 11 / 6 0 12340007 Cat3 A6
0 / 11 / 7 0 12340008 Cat3 A7
0 / 11 / 8 0 12340009 Cat3 A8
0 / 11 / 9 0 12340010 Cat3 A9
0 / 11 / 10 0 12340011 Cat3 A10
0 / 11 / 11 0 12340012 Cat3 A11
0 / 11 / 12 0 12340013 Cat3 A12
0 / 11 / 13 0 12340014 Cat3 A13
0 / 11 / 14 0 12340015 Cat3 A14
0 / 11 / 15 0 12340016 Cat3 A15

0 / 11 / 16 0 12340017 Cat3 A16

0 / 11 / 17 0 12340018 Cat3 A17
0 / 11 / 18 0 12340019 Cat3 A18
0 / 11 / 19 0 12340020 Cat3 A19
0 / 11 / 20 0 12340021 Cat3 A20
0 / 11 / 21 0 12340022 Cat3 A21
0 / 11 / 22 0 12340023 Cat3 A22
0 / 11 / 23 0 12340024 Cat3 A23
0 / 11 / 24 0 12340025 Cat3 A24
0 / 11 / 25 0 12340026 Cat3 A25
0 / 11 / 26 0 12340027 Cat3 A26
0 / 11 / 27 0 12340028 Cat3 A27
0 / 11 / 28 0 12340029 Cat3 A28
0 / 11 / 29 0 12340030 Cat3 A29
0 / 11 / 30 0 12340031 Cat3 A30
0 / 11 / 31 0 12340032 Cat3 A31
--------------------------------------------------------
Command processing completed. 32 port(s) are configured MG PSTN user data
10. Enable the voice enhancing function.

huawei(config-esl-user)#pstnport vqe batset 0/11/0 0/11/31 agc enable agc-
Level 15 sns enable sns-Level 20
Command processing completed. 32 user data modified successfully
huawei(config-esl-user)#display pstnport vqe 0/11
-------------------------------------------------------------------------
Frame/Slot/Port AGC enable AGC value (dbm0) SNS enable SNS value(db)
-------------------------------------------------------------------------
0 / 11 / 0 enable -24 enable 20
0 / 11 / 1 enable -24 enable 20
0 / 11 / 2 enable -24 enable 20
0 / 11 / 3 enable -24 enable 20
0 / 11 / 4 enable -24 enable 20
0 / 11 / 5 enable -24 enable 20
0 / 11 / 6 enable -24 enable 20
0 / 11 / 7 enable -24 enable 20
0 / 11 / 8 enable -24 enable 20
0 / 11 / 9 enable -24 enable 20
0 / 11 / 10 enable -24 enable 20
0 / 11 / 11 enable -24 enable 20
0 / 11 / 12 enable -24 enable 20
0 / 11 / 13 enable -24 enable 20
0 / 11 / 14 enable -24 enable 20
0 / 11 / 15 enable -24 enable 20
0 / 11 / 16 enable -24 enable 20
0 / 11 / 17 enable -24 enable 20
0 / 11 / 18 enable -24 enable 20
0 / 11 / 19 enable -24 enable 20
11. Save the data.

huawei(config-esl-user)#quit
huawei(config)#save
----End
Result
After the configuration is complete, phone 1 to phone 32 can communicate with each other.

10.3 Configuration Example of the VoIP Service (in

Integrated Upstream Mode)
the A32 service board and accessing the IP network through the IPM control board.
Prerequisite
l The master shelf must be added successfully. In this example, the H601HABD functions
as the master shelf.
l The network management port must be configured properly, and you can telnet to the
PVMB control board. For the procedure for configuring the network management port, see
"4 Configuring the NMS."
l The IP addresses used in this example must be configured in the IP address pool. The media
IP address and the signaling IP address are different.
l The data on the MGC (namely, the data corresponding to the data configured on the MG)
must be configured properly.
l The data on the MG interface must be configured properly. For detailed operations, see
"9 Configuring the MG Interface."
Networking
Figure 10-3 shows the example network for configuring the VoIP service.
Figure 10-3 Example network for configuring the VoIP service
MGC
10.10.20.1/24
Router
10.10.10.1/24
H.248
0/11
I I P P A
UA5000
P P V V 3
10.10.10.2/24
M M M M
2
B B B B
Phone1 Phone32

Data Plan
l Table 10-3 provides the data plan for configuring the VoIP service on the IPMB control
board.
l The PVMB control board uses its FE ports Inner_FE0 and Inner_FE1 to communicate with
FE ports 6 and 7 on the IPMB control board. In this case, the PVMB control board uses the
IPMB control board for upstream.
l Table 10-4 provides the data plan for configuring the VoIP service on the PVMB control
board.
Table 10-3 Data plan for configuring the VoIP service (on the IPMB control board)
Shelf ID/Slot ID/Port ID Corresponding Remarks
VLAN
0/2/0 1001 The PVMB control board uses

port 0 on the IPMB control board
0/2/6 for uplink. The PVMB control
0/2/7 board uses its FE ports Inner_FE0
and Inner_FE1 to communicate
with FE ports 6 and 7 on the IPMB
control board. Group FE ports 0,
6, and 7 on the IPMB control
board into a VLAN.
Table 10-4 Data plan for configuring the VoIP service (on the PVMB control board)
Type Item Data
code text
protocol H.248
tranfer UDP
port MG: 2944

MGC: 2944
NOTE
The parameter must be consistent
with the H.248 version of the MGC.
IP address Signaling IP address of MG 10.10.10.2/24


Type Item Data


Telephone number phone 1-phone 32 Shelf ID/slot ID: 0/11

allocation Telephone number:
12340001-12340032
terminal id 0-31. Terminals 0-31 correspond

to numbers 12340001-12340032.
TOS strategy IP priority and TOS priority System default value
Voice enhanced function Automatic gain control Support

(AGC) of the PSTN port
Parameter value of the AGC 15 (-24 dBm0)

of the PSTN port
Spectral noise suppression Support

(SNS) of the PSTN port
Parameter value of the SNS 20 (20 dB)

of the PSTN port
Context
l The parameters configured on the MG interface and on the MGC interface must be
consistent.
l The cadence ringing tone and initial ringing tone must use the local standards.
Figure 10-4 shows the flowchart for configuring the VoIP service.

Figure 10-4 Flowchart for configuring the VoIP service

Start
Add shelves
Add boards Configure

hardware data
Confirm boards
Configure IP
Configure IP addresses addresses
Add MG interfaces
Configure an MG interface Configure MG interface

data
Configure Configure software

protocol data Configure POTS subsciber data parameters
Configure Configure Configure (Optional)
Configure Configure (Optional)
POTS common software Configure
MGCP H.248 Configure
subscriber attributes parameters of system
protocol protocol SPCs
data of the PORT the MG parameters
parameters parameters
subscribers interface
End
Procedure
l Configuration steps (for the IPMB control board)
1. Add a common VLAN and group FE ports 6 and 7 and IP uplink port 0 into the
common VLAN.
huawei(config)#vlan 1001 standard
huawei(config)#port vlan 1001 0/2 0
2. Specify the IP address for the VLAN interface.

huawei(config)#interface vlanif 1001
huawei(config-if-vlanif1001)#ip address 10.10.10.1 255.255.255.0
3. Add a common VLAN and group FE ports 6 and 7 and IP uplink port 0 into the
common VLAN as the uplink channel of the NMS packets.
4. Specify the IP address for the VLAN interface

huawei(config-if-vlanif1002)#ip address 10.10.20.1 255.255.255.0
5. Save the data.

huawei(config)#save
l Configuration steps (for the PVMB control board)

1. Configure the IP address of the service network port.

10.10.10.1 submask 255.255.255.0 vlan_tag 1002
/When the device is configured with the IP address of the service network
port, run this command to change the configuration if the IP address,
subnet mask, gateway, or the vlantag does not meet the data plan
requirements./
/If no IP address is added to the current IP address pool, run the ip
address command to add the media IP address and signaling IP address to
the IP address pool.//
vlan_tag 1001
Eth:
IPAddress ..........: 10.10.10.2
SubMask.............: 255.255.255.0
GateWay.............: 10.10.10.1
MacIndex............: 0
MacAddress..........: 00-E0-FC-44-16-57
VlanID .............: 1001
IPAddress ..........: 10.10.10.4

SubMask.............: 255.255.255.0
GateWay.............: 10.10.10.1
MacIndex............: 0
MacAddress..........: 00-E0-FC-44-16-57
VlanID .............: --
2. Configure the QoS IP strategy.

huawei(config)#qos ip 10.10.10.2 strategy tos
3. Configure the working mode of the PVMB control board to the independent
networking mode.
In this networking mode, the voice service is transmitted upstream through the ETH
port on the IPM board.
huawei(config)#working mode integrated
If switch working mode from alone to integrated,ETH0 will be service port
and
ETH1 will be outband port,Are you sure?(y/n)[n]:y
4. Add the A32 service board and confirm the board.

-------------------------------------------------------------------------
-------------------------------------------------------------------------
0 PWX2 Normal
1 PWX2 Normal
2
3
......
11 A32 Normal
......
35
-------------------------------------------------------------------------
5. Configure the attributes of the MG interface.

---------------------------------------------------------------------
MGID 0
MG Description frf_add
Protocol H248
2833Encrypt -
Codetype Text
Transmode UDP
MIDType IP4_ADDR
DeviceName -

---------------------------------------------------------------------
6. Configure the parameters of the H.248 protocol (enable the three-way handshake
signal function of the H.248 protocol stack).
---------------------------------------------------------------------
maxretranstimes : 7
retransmode : auto
---------------------------------------------------------------------
7. Restart the MG interface.
8. Query whether the MG interface is in the normal state.
-------------------------------------------------------------------------
-------------------------------------------------------------------------
0 UDP Normal 2944 10.10.10. 2 2944 10.10.20.1
-------------------------------------------------------------------------
9. Configure the user telephone number.
telno 12340001
--------------------------------------------------------


--------------------------------------------------------
0 / 11 / 0 0 12340001 Cat3 A0
0 / 11 / 1 0 12340002 Cat3 A1
0 / 11 / 2 0 12340003 Cat3 A2
0 / 11 / 3 0 12340004 Cat3 A3
0 / 11 / 4 0 12340005 Cat3 A4
0 / 11 / 5 0 12340006 Cat3 A5
0 / 11 / 6 0 12340007 Cat3 A6
0 / 11 / 7 0 12340008 Cat3 A7
0 / 11 / 8 0 12340009 Cat3 A8
0 / 11 / 9 0 12340010 Cat3 A9
0 / 11 / 10 0 12340011 Cat3 A10
0 / 11 / 11 0 12340012 Cat3 A11
0 / 11 / 12 0 12340013 Cat3 A12
0 / 11 / 13 0 12340014 Cat3 A13
0 / 11 / 14 0 12340015 Cat3 A14
0 / 11 / 15 0 12340016 Cat3 A15
0 / 11 / 16 0 12340017 Cat3 A16
0 / 11 / 17 0 12340018 Cat3 A17
0 / 11 / 18 0 12340019 Cat3 A18
0 / 11 / 19 0 12340020 Cat3 A19
0 / 11 / 20 0 12340021 Cat3 A20
0 / 11 / 21 0 12340022 Cat3 A21
0 / 11 / 22 0 12340023 Cat3 A22
0 / 11 / 23 0 12340024 Cat3 A23
0 / 11 / 24 0 12340025 Cat3 A24
0 / 11 / 25 0 12340026 Cat3 A25
0 / 11 / 26 0 12340027 Cat3 A26
0 / 11 / 27 0 12340028 Cat3 A27
0 / 11 / 28 0 12340029 Cat3 A28
0 / 11 / 29 0 12340030 Cat3 A29
0 / 11 / 30 0 12340031 Cat3 A30
0 / 11 / 31 0 12340032 Cat3 A31
--------------------------------------------------------
10. Enable the voice enhanced function.

huawei(config-esl-user)#pstnport vqe batset 0/11/0 0/11/31 agc enable
agc-Level 15 sns enable sns-Level 20
-------------------------------------------------------------------------
-------------------------------------------------------------------------
0 / 11 / 0 enable 15 enable 20
0 / 11 / 10 enable 15 enable 20
0 / 11 / 11 enable 15 enable 20
0 / 11 / 12 enable 15 enable 20
0 / 11 / 13 enable 15 enable 20
0 / 11 / 14 enable 15 enable 20
0 / 11 / 15 enable 15 enable 20
0 / 11 / 16 enable 15 enable 20
0 / 11 / 17 enable 15 enable 20
0 / 11 / 18 enable 15 enable 20
0 / 11 / 19 enable 15 enable 20
11. Save the data.

huawei(config)#save
----End
Result
After the configuration is complete, phone 1 to phone 32 can communicate with each other.

Configure the standalone service of the UA5000. Thus, when the UA5000 is disconnected from
the MGC, the subscribers connected to a same VAG can still communicate with each other.
Prerequisite
l The subscribers of the voice services must be configured on the MG interface.
l The subscribers must be able to call each other.
For the procedure for configuring the subscribers, see "10.2 Configuration Example of the
VoIP Service."
Context
l Internal call standalone: When the UA5000 is disconnected from the MGC, the subscribers
on the same MG interface can call each other. The MG interface is supported by the
UA5000 instead of the MGC.
l Emergency channel: When the UA5000 is disconnected from the MGC, the subscribers of
the UA5000 can dial the external phone numbers that are in the digitmap for emergency
calls. For example, when the UA5000 is disconnected from the MGC, in the case of a fire,
you can dial the fire emergency call.
Precaution
The UA5000 cannot detect repeated telephone numbers. When configuring telephone numbers
for the standalone service, ensure that the telephone numbers are unique. Otherwise, the
standalone service fails.
Procedure
Step 1 Run the mg-software parameter command to configure the service type of the VAG standalone
service.
Step 2 Run the display mg-software parameter command to query the service type of the VAG
standalone service.
Step 3 Run the standalone parameters command to configure the parameters of the VAG standalone
timers.
Step 4 Run the display standalone parameters command to query the parameters of the VAG
standalone timers.
Step 5 Run the digitmap set command to configure the digitmap for internal calls.

Step 6 Run the display digitmap command to query the digitmap for internal calls.
----End
Example
The following example shows how to configure the 32 POTS subscribers on the board in slot
12 of shelf 0, and configure the VAG to support the standalone service. Table 10-5 provides the
data plan for configuring the standalone service.
Table 10-5 Data plan for configuring the standalone service
Data Type Item Data
MG interface mgid 1
Standalone para index 11: The device supports internal calls between the
parameters subscribers connected to the device and the
emergency channels.
dialtoneval 15
ringval 60
busytoneval 50
Phone digitmap 1234xxxx
Emergency call 110|119|999

digitmap
-------------------------------------------------
-------------------------------------------------
APPENDIX:
-------------------------------------------------
Interface soft parameter name:
11: Stand alone support
0 : None
1 : Inner
2 : Emergency
3 : Both
huawei(config-if-h248-1)#standalone parameters dialtone 15 ring 60 busytone 50
huawei(config-if-h248-1)#display standalone parameters
--------------------------------------------------------------------------
System stand alone para of timer for dial tone :15 (s)
System stand alone para of timer for busy tone :50 (s)
System stand alone para of timer for ring :60 (s)
--------------------------------------------------------------------------
huawei(config-if-h248-1)#digitmap set inner 1234xxxx emergency 110|119|999
huawei(config-if-h248-1)#display digitmap
---------------------------------------------------------------------------
Inner digitmap : 1234xxxx
Emergency digitmap : 110|119|999
Urgent digitmap (for overload or bandwidth restrict) : -
Dualdial digitmap for card service : -
---------------------------------------------------------------------------

10.5 Configuring the System Parameters

Configure the parameters such as the sending howler tone flag, overseas flag, and consistency
test flag of the UA5000 by configuring the global system parameters. Thus, the use of the
subscriber terminal complies with the local standard.
Prerequisite
l The UA5000 must work in the normal state.
l The user must log in to the UA5000 through the maintenance terminal and must maintain
the UA5000 in the normal state.
Context
The system parameters can be used to configure the following:
l Sending howler tone flag

l Overseas version flag
l Consistency test flag
l Stop initial ringing flag
l System self check flag
l CPU over load call restriction flag
l Call-waiting tone flag
l Voicemail mode
l RTP 2833 Payload Type
l Inconsistency of the numbers of the peer UDP transmit and receive ports
l Transfer mode of media stream in a device
l Howler tone source
l TEI check cycle
l POTS GTC performance statistics function
Procedure
Step 1 Run the system parameters command to configure the system parameters.
Step 2 Run the display system parameters command to query the system parameters.
----End
Example
To set the overseas version flag as ETSI, do as follows:
huawei(config)#display system parameters 1
-----------------------------------------------------------------------------
Parameter name index: 1 Parameter value: 8
Mean: Overseas version flag, 0:China, 1:HongKong, 2:Brazil, 3:Egypt,
4:Singapore, 5:Thailand, 6:France, 7:Britain MSFUK, 8:Britain ETSI, 9:Bulgaria,

10:Aleutian
-----------------------------------------------------------------------------
10.6 Configuring the POTS Subscriber Data and Port

Attributes
After configuring the MG interface successful, you can add POTS subscribers on the MG
interface by configuring the POTS subscriber data and port attributes. Thus, the function of the
communication between POTS subscribers can be implemented.
Prerequisite
l The UA5000 must communicate properly with the MGC.
l The subscriber data on the MGC must be configured properly.
Context
l Perform this operation to configure POTS subscriber data, such as the following:
– Terminal priority
– Telephone number
– Terminal ID
l Perform this operation to configure the attributes of a POTS port, such as the following:
– Subscriber attributes
– Attributes of the calling number format
– Impedance and attributes of the current
– 16KC/12KC attributes
– Polarity reversed pulse attributes
– Power-off duration attributes
Procedure
Step 1 In the global config mode, run the esl user command to enter the ESL mode.
Step 2 Run the mgpstnuser add or mgpstnuser batadd command to add POTS subscribers.
Step 3 Run the display mgpstnuser command to query the information about the POTS subscribers.
Step 4 Run the pstnport attribute set or pstnport attribute batset command to set the attributes of
the PSTN port.
Step 5 Run the display pstnport attribute command to query the attributes of the PSTN port.
----End
Example
The following example shows how to add 32 POTS subscribers to shelf 0/slot 11. In this example,
the mgid is 0, and all the subscribers support polarity reversed charging.
huawei(config-esl-user)#mgpstnuser batadd 0/11/0 0/11/31 0 step 1 terminalid 100

This operation will take several minutes, please wait...

huawei(config-esl-user)#
Command processing completed. 32 user data added successfully
huawei(config-esl-user)#display mgpstnuser 0/11/0 0/11/31
--------------------------------------------------------
--------------------------------------------------------
0 / 11 / 0 0 - Cat3 A100
0 / 11 / 1 0 - Cat3 A101
0 / 11 / 2 0 - Cat3 A102
0 / 11 / 3 0 - Cat3 A103
0 / 11 / 4 0 - Cat3 A104
0 / 11 / 5 0 - Cat3 A105
0 / 11 / 6 0 - Cat3 A106
0 / 11 / 7 0 - Cat3 A107
0 / 11 / 8 0 - Cat3 A108
0 / 11 / 9 0 - Cat3 A109
0 / 11 / 10 0 - Cat3 A110
0 / 11 / 11 0 - Cat3 A111
0 / 11 / 12 0 - Cat3 A112
0 / 11 / 13 0 - Cat3 A113
0 / 11 / 14 0 - Cat3 A114
0 / 11 / 15 0 - Cat3 A115
0 / 11 / 16 0 - Cat3 A116
0 / 11 / 17 0 - Cat3 A117
0 / 11 / 18 0 - Cat3 A118
0 / 11 / 19 0 - Cat3 A119
0 / 11 / 20 0 - Cat3 A120
0 / 11 / 21 0 - Cat3 A121
0 / 11 / 22 0 - Cat3 A122
0 / 11 / 23 0 - Cat3 A123
0 / 11 / 24 0 - Cat3 A124
0 / 11 / 25 0 - Cat3 A125
0 / 11 / 26 0 - Cat3 A126
0 / 11 / 27 0 - Cat3 A127
0 / 11 / 28 0 - Cat3 A128
0 / 11 / 29 0 - Cat3 A129
0 / 11 / 30 0 - Cat3 A130
0 / 11 / 31 0 - Cat3 A131
--------------------------------------------------------
huawei(config-esl-user)#pstnport attribute batset 0/11/0 0/11/31 polarity-reverse
support
huawei(config-esl-user)#display pstnport attribute 0/11
-------------------------------------------------------------------------
Frame/Slot/Port Gain(db) Dial-Mode Polarity-Reverse User-Type
-------------------------------------------------------------------------
0 / 11 / 0 High gain DTMF-Pulse-Both Supported DEL


-------------------------------------------------------------------------
huawei(config)#board reset 0/11
Are you sure to reset board? (y/n)[n]:y
NOTE
At the start and end of a call, the UA5000 shows the start time and the end time based on the polarity
reversal of the subscriber line. The billing terminal that has the polarity reversal charging function, such
as a charging telephone set, implements the polarity reversal charging function according to the start time
and the end time of the call.
Related Operation
Table 10-6 lists the related operations for configuring the POTS subscriber data.
Table 10-6 Related operations for configuring the POTS subscriber data
Delete a POTS subscriber or mgpstnuser del/mgpstnuser -

delete POTS subscribers in batdel
batches
Modify POTS subscriber mgpstnuser modify -

data
Query the information about display mgpstnuser Query information, such as

a POTS port to which the port ID, MG ID, terminal
subscriber is connected ID, and telephone number
corresponding to the
subscriber.
Query the type and status of a display port state Query information, such as
POTS port and the service the type, status, and service
types on it type of the port.
Terminate/Reset the POTS endservice/undo endservice Terminating/Resetting the

port service POTS port service affects
the ongoing call. Run this
command with caution.
Terminating the POTS port
service may fail when the
system is busy.
Configure the attributes of a pstnport attribute set/ -

POTS port or configure the pstnport attribute batset
attributes of POTS service
ports in batches

Query the attributes of a display pstnport attribute -

POTS port
Configure the caller number pstnport clip set/pstnport -

format on a POTS service clip batset
port or configure the caller
number format on the POTS
service ports in batches
Display the caller number display pstnport clip -

format on a POTS service
port
Configure the impedance and pstnport electric set/ -

the attributes of the current on pstnport electric batset
a POTS service port or
configure the impedance and
the attributes of the current on
POTS service ports in batches
Query the impedance and the display pstnport electric -

attributes of the current on a
POTS service port
Configure the KC attributes pstnport kc set/pstnport kc After configuring the KC

of a POTS port or configure batset attributes, reset the board to
the KC attributes of POTS validate the settings.
ports in batches
Query the KC attributes of a display pstnport kc -

POTS service port
Configure the polarity pstnport reversepole_pulse After configuring the

reversal attributes for a POTS set/pstnport polarity reversal attributes,
port or configure the polarity reversepole_pulse batset reset the board to validate
reversal attributes for POTS the settings.
ports in batches
Query the polarity reversal display pstnport -

attributes of POTS ports reversepole_pulse
Configure the power-off pstnport timer set/pstnport -

duration of a POTS timer batset
subscriber or configure the
power-off duration of POTS
subscribers in batches
Query the power-off duration display pstnport timer -

of a POTS subscriber

10.7 Configuring the QoS IP Precedence

Configuring the QoS IP precedence means configuring the different QoS IP precedences for the
signaling, media, and maintenance packets to meet different requirements for the delay and jitter
of different services.
Prerequisite
l The ToS/DSCP strategy on the UA5000 must be the same as the ToS/DSCP strategy
configured on the router at the upper layer.
l The IP addresses must be configured in the IP address pool.
Related Concept
l Precedence tagging: It is a strategy to re-tag the precedence of a packet that matches the
access control list. The tagged precedence is located in the related precedence fields.
l ToS (type of service) precedence: It is the ToS sub-field (bits 4 to 7 of the ToS field) carried
by the ToS field in the IP header.
Figure 10-5 shows the ToS field in the IP header. The fields are described as follows:
1. Precedence: 3 bits. It indicates the IP precedence.

2. Delay (D): 1 bit. It indicates the minimum delay. When the ToS value is set to 8 (in decimal
notation) or 1000 (in binary notation), the delay is the minimum.
3. Throughput (T): 1 bit. It indicates the maximum throughput. When the ToS value is set to
4 (in decimal notation) or 0100 (in binary notation), the throughput is the maximum.
4. Reliability (R): 1 bit. It indicates the maximum reliability. When the ToS value is set to 2
(in decimal notation) or 0010 (in binary notation), the reliability is the maximum.
5. Cost (C): 1 bit. It indicates the minimum cost, that is, the router of the lower cost should
be selected. When the ToS value is set to 1 (in decimal notation) or 0001 (in binary notation),
the cost is the minimum.
Figure 10-5 ToS field of the IP header

0 1 2 3 4 5 6 7
Not used
Precedence D T R C
bit 0 4 8 16 31
Version IHL ToS Total length
NOTE
If the ToS value of an IP packet is set to 0 (in decimal notation) or 0000 (in binary notation), the packet is
for common service.
l Differentiated services code point (DSCP) precedence: It is defined by the differentiated
services (DS) field of the IP header. The DS field uses the ToS octet in the IP header. Six

bits of the ToS octet is used and the other two bits are reserved and must be set as 0. Figure
10-6 shows the DS field of the IP header.
Figure 10-6 DS field of the IP header
0 1 2 3 4 5 6 7
Not used
DSCP
bit 0 4 8 16 31
Version IHL DS Total length
Context
l The traditional IP network uses the best effort (BE) mode in the transmission of the packets
carrying various services. The BE mode can meet the requirements of the non-realtime
services such as file transfer, web page browsing and e-mail transfer. The realtime services,
however, demand low delay and jitter. The BE mode cannot meet the increasing demand
of the subscribers. To solve the problem, you must distinguish the priorities for signaling,
media, and maintenance packets, and set different QoS IP priorities for the signaling, media,
and maintenance packets.
l Before changing the QoS IP strategy, run the qos ip command to set the ToS or DSCP value
as none. Otherwise, changing the QoS IP strategy is not allowed, and the system displays
an error prompt.
l To modify a QoS IP strategy, the interface corresponding to the IP address must be in the
closed or not-started state.
l After configuring the IP addresses, you can configure the ToS/DSCP tag. If the MG
interface is configured, you must disable the MG interface to configure the ToS/DSCP tag.
Otherwise, configuring the ToS/DSCP tag is not allowed, and the system displays an error
prompt.
Procedure
l Procedure (TOS)
1. Run the qos ip ip_address strategy tos command to set the QoS IP strategy to TOS.
2. Run the qos ip ip_address tos command to configure the ToS precedence for different
service types.
3. Run the display qos ip command to query the QoS IP strategy.
l Procedure (DSCP)
1. Run the qos ip ip_address strategy dscp command to set the QoS IP strategy to
DSCP.
2. Run the qos ip ip_address dscp command to configure the DSCP precedence for
different service types.
3. Run the display qos ip command to query the QoS IP strategy.
----End

Example
The following example shows how to configure the QoS IP strategy as tos for the UA5000.
Table 10-7 provides the data plan for configuring the QoS IP strategy.
Table 10-7 Data plan for configuring the QoS IP strategy-1

ip_address 10.10.10.2 strategy tos
media_precedence 2 media_tos 3
signalling_precedence 3 signalling_tos 5
maintain_precedence 2 maintain_tos 5
huawei(config)#display qos ip
{ <cr>|ip_address<X.X.X.X> }:
Command:
display qos ip
Eth:
IPAddress............: 10.10.10.2
QOSIP Strategy.......: NONE
Command:
display qos ip
Eth:
IPAddress............: 10.10.10.2
QOSIP Strategy.......: ToS
Media Precedence.....: 6
Media ToS............: 8
Signaling Precedence.: 7
Signaling ToS........: 2
Maintain Precedence..: 7
Maintain ToS.........: 2
huawei(config)#qos ip 10.10.10.2 tos media 2 3 signaling 3 5 maintain 2 5
Command:
display qos ip
Eth:
IPAddress............: 10.10.10.2
Media ToS............: 3
The following example shows how to configure the QoS IP strategy as dscp for the UA5000.
Table 10-8 provides the data plan for configuring the QoS IP strategy.

Table 10-8 Data plan for configuring the QoS IP strategy-2

ip_address 10.10.10.2 strategy dscp
media_dscp 34 signalling_dscp 56
maintain_dscp 56 - -
Command:
display qos ip
Eth:
IPAddress............: 10.10.10.2
Media ToS............: 3
huawei(config)#qos ip 10.10.10.2 strategy dscp
Command:
display qos ip
IPAddress............: 10.10.10.2
QOSIP Strategy.......: DSCP
Media DSCP...........: 46
Signaling DSCP.......: 26
Maintain DSCP........: 26
huawei(config)#qos ip 10.10.10.2 dscp media 34 signaling 56 maintain 56
Command:
display qos ip
IPAddress............: 10.10.10.2
QOSIP Strategy.......: DSCP
Media DSCP...........: 34
Signaling DSCP.......: 56
Maintain DSCP........: 56
10.8 Configuring the QoS VLAN Priority

Configuring the QoS VLAN priorities means configuring the different QoS VLAN priorities for
the signaling, media, and maintenance packets. Thus, the QoS priorities of the service traffic
streams can be controlled according to the VLAN priorities.
Prerequisite
The IP addresses must be configured in the IP address pool.

Context
You can configure different VLAN priorities for signaling, media, and maintenance packets
when configuring an IP address.
NOTE
An IP address is bound only with the VLAN ID instead of the VLAN priority. That is, different types of
packets from one IP address can have different VLAN priorities.
Procedure
Step 1 Run the qos vlan ip_address priority command to set VLAN priorities for different service
types.
Step 2 Run the display qos vlan command to query the QOS VLAN settings.
----End
Example
To set the QoS VLAN priority of the IP address 10.10.10.4 to the default value, do as follows:
huawei(config)#qos vlan 10.10.10.4 priority default
huawei(config)#display qos vlan 10.10.10.4
IPAddress............: 10.10.10.4
VlanID...............: 1001
Media Priority.......: 6
Signaling Priority...: 3
Maintain Priority....: 5
10.9 Separating the Signaling IP Address from the Media IP

Address
Separating the signaling IP address from the media IP address means configuring two different
IP addresses as the media IP address and signaling IP address. Thus, the media stream and
signaling stream are transmitted through different paths in the network.
Prerequisite
The IP addresses must be configured in the IP address pool.
Context
You need to configure different IP addresses for signaling stream and media stream to distinguish
the paths for signaling stream and media stream. This helps to use different QoS strategy.
Precaution
l The signaling IP address and media IP address can be separated only when the UA5000
uses the H.248 protocol.
l After modifying the configuration of MG interface, reset the MG interface to validate the
modification.

Procedure
Step 2 Run the if-h248 attribute mg-media-ip command to add a media IP address for the MG
interface.
Step 3 Run the display if-h248 attribute command to query the attributes of the MG interface. Then,
check whether the media IP address is correct.
----End
Example
To set the media IP address of MG interface 0 as 10.10.10.4, do as follows:
huawei(config-if-h248-0)#if-h248 attribute mg-media-ip 10.10.10.4
---------------------------------------------------------------------
MGID 0
MG Description -
MG DomainName -
Protocol H248
Profile Negotiation Para enable
Profile 1:Resv1("")
2833Encrypt -
Codetype Text
Transmode UDP
MIDType IP4_ADDR
DeviceName -

---------------------------------------------------------------------
10.10 Enabling the Voice Quality Enhanced Function

Enabling the voice quality enhanced function includes enabling the automatic gain adjustment
and background noise suppression functions so that the voice service is of better quality when
there is noise.
Prerequisite
l The UA5000 must work in the normal state.
l The maintenance terminal must be logged in to the UA5000 successfully and the
UA5000 must be maintained normally.

Context
The voice quality enhancements (VQE) include two functions: automatic gain adjustment and
background noise suppression.
l Automatic gain adjustment: During the VoIP call, this function helps to prevent the call
quality from be affected by the sudden change of the noise energy. When the noise energy
changes suddenly, the gain is adjusted automatically so that noise energy is adjusted
smoothly. This prevents the discomfort of the listener caused by the sudden change of the
noise energy.
l Background noise suppression: During the VoIP call, the noise energy can be reduced to
improve the comfort and the clarity of the call.
Procedure
Step 1 Run the pstnport vqe set command or the pstnport vqe batset command to configure the VQE
attributes of the PSTN port.
NOTE
l pstnport vqe set is to configure the VQE of a single PSTN port.

l pstnport vqe batsetis to configure the VQE of PSTN ports in batch.
Step 2 Run the display pstnport vqe command to query the VQE attributes of the PSTN port.
----End
Example
To enable the automatic gain adjustment, set the automatic gain adjustment parameter as 15 (that
is -24dBm0), enable the background noise suppression, and set the background noise suppression
parameter as 20 dB for PSTN port 0/6/0, do as follows:
huawei(config-esl-user)#pstnport vqe set 0/6/0 agc enable agc-Level 15 sns enable
sns-level 20
PSTN port set completed
huawei(config-esl-user)#display pstnport vqe 0/6/0
------------------------------------------------------------------------------
Frame/Slot/Port AGC enable AGC value (dbm0) SNS enable SNS value (db)
------------------------------------------------------------------------------
0 / 6 / 0 enable -24 enable 20
-----------------------------------------------------------------------------

l The automatic gain adjustment is enabled.
l The automatic gain adjustment parameter is set as 15 (that is -24dBm0).
l The background noise suppression is enabled.
l The background noise suppression parameter is set as 20 dB.
To configure the VQE attributes for PSTN ports 0/6/0 to 0/6/4 in batches, do as follows:
huawei(config-esl-user)#pstnport vqe batset 0/6/0 0/6/4 agc enable agc-Level 15 sns
enable sns-Level 20
------------------------------------------------------------------------------
Frame/Slot/Port AGC enable AGC value (dbm0) SNS enable SNS value (db)

------------------------------------------------------------------------------
0 / 6 / 5 enable NULL enable NULL
-----------------------------------------------------------------------------

Configuration Guide-PVM CLI 11 Configuring the VAG Service
11 Configuring the VAG Service
About This Chapter
Configuring the VAG service includes the application of the VAG service and the process for
configuring the VAG on the UA5000.
11.1 Introduction to the VAG Service

Virtual access gateway (VAG) means that a physical AG is simulated as multiple virtual AGs.
11.2 Configuration Example of the VAG Service
This topic describes how to configure and verify the VAG service by creating two MG interfaces
on the UA5000 and then configuring PSTN subscribers on the two MG interfaces.
11.3 Configuring the TID Profile of the VAG
This topic describes how to configure the mode of generating terminal IDs (TIDs) of users of
all the types of the VAG, including the terminal prefix and TID profile. The TID profile defines
the mode of generating the ID of the terminal except the terminal prefix. The ID of a user terminal
is a combination of the terminal prefix and the character string generated by the TID profile.

11.1 Introduction to the VAG Service

Virtual access gateway (VAG) means that a physical AG is simulated as multiple virtual AGs.
Service Description
An AG supports different IP interfaces and each interface is used independently to realize the
VAG feature.
In the VAG service, an AG can be used by several carriers to improve the device utilization, to
facilitate the management and charging, and thus to meet the requirements of the carrier.
For more information about the features of VAG, see "VAG" in the Feature Description.
An AG supports a maximum of 8 VAGs.
11.2 Configuration Example of the VAG Service

This topic describes how to configure and verify the VAG service by creating two MG interfaces
on the UA5000 and then configuring PSTN subscribers on the two MG interfaces.
Prerequisite
l The IP address of the service network port and the subscribers must be configured
successfully. The subscribers must be able to call each other. For the procedure for
configuring the subscribers, see "10.2 Configuration Example of the VoIP Service."
l System parameters must be configured according to "10.2 Configuration Example of the
VoIP Service."
Networking
Figure 11-1 shows the example network of the VAG service.
NOTE

Figure 11-1 Example network of the VAG service
MGC
Router 10.10.20.1/24
10.10.10.1/24
H.248
0/11 0/12
P P A A
V V 3 3
UA5000
M M 2 2
10.10.10.2/24
B B
Phone 1 Phone 32 Phone 33 Phone 64
VAG1 VAG2
Data Plan
l Table 11-1 provides the data plan for configuring the VAG 2 on the PVMB control board.
For the data plan for configuring VAG 1, see "10.2 Configuration Example of the VoIP
Service."
l In the preceding figure, MG 1 stands for VAG 1, and MG 2 stands for VAG 2.
Table 11-1 Data plan for configuring the VAG on PVMB

Data Type Item Data
code text
protocol H.248
transfer UDP
port MG: 2944

MGC: 2944

Data Type Item Data
Whether the MG holds Yes

ongoing calls when the
connection between MGC and
MG is broken
NOTE
same as the H.248 version on
the MGC.
IP addresses Signaling IP address of MG 10.10.10.3/24



MGC 10.10.20.1/24
Telephone numbers Phone 33-phone 64 MG interface: 1

Shelf ID/slot ID: 0/12
Telephone numbers:
12340033-12340064
Context
Virtual Access Gateway (VAG) is a feature that enables a physical AG to support multiple
VAGs. The physical AG supports multiple IP interfaces, and assigns the IP interfaces for
dedicated use to realize the VAG feature.
Precaution
l The MG interface parameters configured on the UA5000 must be the same as the parameters
configured on the MGC.
l The cadence ring tone and initial ring tone must meet the local standard.
Procedure
l For the procedure for configuring the data of VAG 1, see "10.2 Configuration Example
of the VoIP Service."
l To configure the data of VAG 2, do as follows.
1. Add a service board.
-------------------------------------------------------------------------

-------------------------------------------------------------------------
0 PWX2 Normal
1 PWX2 Normal
2
3
......
12 A32 Normal
......
35
-------------------------------------------------------------------------
2. Configure the attributes for the MG interface of VAG 2.

Are you sure to add MG interface?(y/n)[n]:y
huawei(config-if-h248-1)#if-h248 attribute mgip 10.10.10.3 mgport
2944 code text transfer udp domainName UA50001.com mgcip_1 10.10.20.1

---------------------------------------------------------------------
MGID 1
MG Description -
Protocol H248
2833Encrypt -
Codetype Text
Transmode UDP
MIDType IP4_ADDR
DeviceName -

---------------------------------------------------------------------
3. Configure the digitmap for internal calls on the MG interface.

huawei(config-if-h248-1)#digitmap set inner 1234xxxx
4. Enable the MG interface.

5. Query whether the MG interface is in the normal state.

-------------------------------------------------------------------------
-------------------------------------------------------------------------
1 UDP Normal 2944 10.10.10.3 2944 10.10.20.1
-------------------------------------------------------------------------
6. Configure the telephone numbers of the subscribers.

telno 12340033
--------------------------------------------------------
--------------------------------------------------------
0 / 12 / 0 0 - Cat3 A32
0 / 12 / 1 0 - Cat3 A33
0 / 12 / 2 0 - Cat3 A34
0 / 12 / 3 0 - Cat3 A35
0 / 12 / 4 0 - Cat3 A36
0 / 12 / 5 0 - Cat3 A37
0 / 12 / 6 0 - Cat3 A38
0 / 12 / 7 0 - Cat3 A39
0 / 12 / 8 0 - Cat3 A40
0 / 12 / 9 0 - Cat3 A41
0 / 12 / 10 0 - Cat3 A42
0 / 12 / 11 0 - Cat3 A43
0 / 12 / 12 0 - Cat3 A44
0 / 12 / 13 0 - Cat3 A45
0 / 12 / 14 0 - Cat3 A46
0 / 12 / 15 0 - Cat3 A47
0 / 12 / 16 0 - Cat3 A48
0 / 12 / 17 0 - Cat3 A49
0 / 12 / 18 0 - Cat3 A50
0 / 12 / 19 0 - Cat3 A51
0 / 12 / 20 0 - Cat3 A52
0 / 12 / 21 0 - Cat3 A53
0 / 12 / 22 0 - Cat3 A54
0 / 12 / 23 0 - Cat3 A55
0 / 12 / 24 0 - Cat3 A56
0 / 12 / 25 0 - Cat3 A57
0 / 12 / 26 0 - Cat3 A58
0 / 12 / 27 0 - Cat3 A59
0 / 12 / 28 0 - Cat3 A60
0 / 12 / 29 0 - Cat3 A61
0 / 12 / 30 0 - Cat3 A62
0 / 12 / 31 0 - Cat3 A63
--------------------------------------------------------
7. Save the data.

huawei(config)#save
----End
Result
1. When MG interface 1 communicates properly with the MGC, subscribers of phone 1-phone
32 should be able to call each other.
2. When MG interface 2 communicates properly with the MGC, subscribers of phone 33-
phone 64 should be able to call each other.
3. When MG interfaces 1 and 2 communicate properly with the MGC, subscribers of phone
1-phone 64 should be able to call each other.
4. After disabling MG interface 1 by running the shutdown graceful command, the results
should be as follows:
l Subscribers of phone 1-phone 32 should not be able to call each other.
l Subscribers of phone 33-phone 64 should be able to call each other.
l Subscribers of phone 1-phone 32 and phone 33-phone 64 should not be able to call each
other.

This indicates that the configuration of each VAG is independent, and the configuration is
valid only to the subscribers of the VAG.
11.3 Configuring the TID Profile of the VAG

This topic describes how to configure the mode of generating terminal IDs (TIDs) of users of
all the types of the VAG, including the terminal prefix and TID profile. The TID profile defines
the mode of generating the ID of the terminal except the terminal prefix. The ID of a user terminal
is a combination of the terminal prefix and the character string generated by the TID profile.
Prerequisite
Context
l The system has 18 common TID profiles with the TID indexes of 0-17. When the default
TID profiles in the system cannot meet the current requirement, you can add the user-
defined TID profile manually as required.
l The TID profile format string should consist of at least one fixed format "%u" or one unfixed
format "%0nu". "n" represents the numeral that ranges from 0 to 10. "%u" means that the
length of the parameter to be printed is unlimited, and "%0nu" means that the length of the
parameter to be printed is n. The format allows the security character string at the beginning
and the end.
l The parameter list consists of at least one keyword. The keywords are separated by "," and
support the addition algorithm. The deviation of addition ranges from 0 to 0x40000000.
The keywords include the following:
– F: Indicates the shelf ID.
– S: Indicates the slot ID.
– P: Indicates the port ID.
– B: Indicates the B channel.
– G: Indicates the general permanent TID.
– R: Indicates the RTP virtual TID.
l When a PSTN subscriber, an ISDN PRA subscriber or an ISDN BRA subscriber is added,
the TID matching each type of the subscriber is output based on the format and the terminal
prefix of the matching TID profile.
For example, if the matching TID profile format of the PSTN subscriber is %02u/%02u/
%02u, the terminal prefix of the TID profile is aln, and the location of the PSTN subscriber
is 0/11/0, the TID of the PSTN subscriber is aln00/11/00
.
l You can run the display tid-format command to query the TID profile bound to users of
all the types on the current MG interface, and then run the display tid-template command
to query the format of the TID profile.
Precaution
l The format of the TID profile of the VAG and the format of the TID profile of the SoftSwitch
must be consistent.

l The index and name of the added profile must be different from the index and name of the
existing profiles in the system.
l If terminals of a type exist on an interface and the interface is not disabled, the prefix of
terminals of this type cannot be modified.
l If terminals of a type exist on an interface, the index of the TID profile corresponding to
the terminals of this type cannot be modified.
l The system supports 64 TID profiles. The TID profiles with indexes from 0 to 31 are
reserved for the system, and the TID profiles with indexes from 32 to 63 can be customized.
Procedure
Step 1 Run the display tid-template command to query the TID profile of the system.
Step 2 When the default TID profile in the system cannot meet the requirements, run the tid-template
add command to add the required TID profile. When the default TID profile in the system can
meet the requirements, go to Step 3.
Step 3 Enter MG interface mode.

l If the system protocol is H.248, run the interface h248 command to enter H248 mode.
l If the system protocol is MGCP, run the interface mgcp command to enter MGCP mode.
Step 4 Configure the TID profiles and terminal prefixes of subscribers of all the types of the current
VAG.
l In H248 mode, run the tid-format pstn command to configure the TID profile and terminal
prefix of the PSTN subscriber.
l In H248 mode, run the tid-format bra command to configure the TID profile and terminal
prefix of the ISDN BRA subscriber.
l In H248 mode, run the tid-format pracommand to configure the TID profile and terminal
prefix of the ISDN PRA subscriber.
l In H248 mode, run the tid-format rtp command to configure the TID profile and terminal
prefix of the RTP terminal.
l In H248 mode, run the tid-format r2 command to configure the TID profile and terminal
prefix of the R2 subscriber.
l In MGCP mode, run the tid-format pstn command to configure the TID profile and terminal
prefix of the ISDN subscriber.
l In MGCP mode, run the tid-format pra command to configure the TID profile and terminal
prefix of the ISDN PRA subscriber.
l In MGCP mode, run the tid-format bra command to configure the TID profile and terminal
prefix of the ISDN BRA subscriber.
----End
Example
l The index of the TID profile is 36.

l The length of the printing parameter is not limited.
l The parameter list is shelf ID + 1, slot ID +1, and port ID + 1.

l The name of the TID profile is CustomTemplate.

l The terminal prefix is A.
To configure the TID profile in H248 mode for PSTN subscriber on port 0/15/0, do as follows:
huawei(config)#display tid-template all
---------------------------------------------------------
Index Name
---------------------------------------------------------
0 Rtp_Delamination
1 Rtp_No_Delamination
2 General_No_Delamination
3 Aln_Not_Fixed_1
4 Aln_Fixed_1
5 Aln_Not_Fixed_0
6 Aln_Fixed_0
7 Aln_BT
8 Bra_Not_Fixed_1
9 Bra_Fixed_1
10 Bra_Not_Fixed_0
11 Bra_Fixed_0
12 Bra_BT
13 Trunk_Not_Fixed_1
14 Trunk_Fixed_1
15 Trunk_Not_Fixed_0
16 Trunk_Fixed_0
17 Trunk_BT
18 Rtp_Fixed_5u
-------------------------------------------------
huawei(config)#tid-template add 36 format %u/%u/%u parameterlist
f+1,s+1,p+1 name CustomTemplate
huawei(config-if-h248-0)#tid-format pstn template 36 prefix A
huawei(config-if-h248-0)#display tid-format
--------------------------------
user-type template-index prefix
--------------------------------
rtp 1 A
pstn 36 A
bra 2 A
pra 2 A
r2 2 A
--------------------------------
huawei(config-esl-user)#mgpstnuser add 0/10/0 0
huawei(config-esl-user)#display mgpstnuser 0/10/0
--------------------------------------------------------
--------------------------------------------------------
0 / 10 / 0 0 - Cat3 A1/11/1
--------------------------------------------------------
Related Operation
Table 11-2 lists the related operations for configuring the TID profile of the VAG interface.
Table 11-2 Related operations for configuring the TID profile of the VAG interface
Delete the user-defined TID tid-template delete -

profile

Modify the user-defined TID tid-template_modify -

profile
Modify the prefix of the user H248: Run this command to modify
terminal tid-format the terminal prefix of the user
MGCP: terminal. If terminals of a
tid-format certain type exist on an
interface and the interface is
not disabled, the prefix of
terminals of this type cannot
be modified.

Configuration Guide-PVM CLI 12 Configuring the ISDN Service
12 Configuring the ISDN Service
About This Chapter
Configuring the ISDN service includes the application of the ISDN technology and the related
process for configuring the ISDN service of the UA5000.
12.1 Introduction to the ISDN Service

The integrated services digital network (ISDN) is a digital communication network developed
by integrating the digital network and the data communication network. The ISDN is the
digitized stage of the telephone network, which permits voice, data, text, graphics, music, and
video to be transmitted over existing telephone wires.
12.2 Configuration Example of the P2P ISDN BRA Service
This topic describes how to configure the point-to-point (P2P) ISDN BRA service through the
DSL service board. Thus, after the configuration, ISDN BRA subscribers can call each other,
and ISDN BRA subscribers and POTS subscribers can call each other.
12.3 Configuration Example of the P2MP ISDN BRA Service
This topic describes how to configure the point-to-multipoint (P2MP) ISDN BRA service
through the DSL service board. After the configuration, ISDN BRA subscribers can call each
other, and ISDN BRA subscribers and POTS subscribers can call each other.
12.4 Configuration Example of the ISDN PRA Service (When the EDTB Service Board Is Used)
This topic describes how to configure the ISDN PRA service through the EDTB service board.
After the configuration, ISDN PRA subscribers can call each other, and ISDN PRA subscribers
and POTS subscribers can call each other.
12.5 Configuring the SIGTRAN Protocol Stack
The signaling transport (SIGTRAN) protocol supports the transmission of traditional switched
circuit network (SCN) signaling over the IP network through protocol adaptation and
transmission.

12.1 Introduction to the ISDN Service

The integrated services digital network (ISDN) is a digital communication network developed
by integrating the digital network and the data communication network. The ISDN is the
digitized stage of the telephone network, which permits voice, data, text, graphics, music, and
video to be transmitted over existing telephone wires.
Service Description
Definition of ISDN by the International Telegraph and Telephone Consultative Committee
(CCITT): Integrated services digital network (ISDN) is a communication network evolved from
integrated digital network (IDN) and provides the E2E digital connection to support multiple
telecommunication services involving the voice and non-voice services. Subscribers can access
the network through a group of network interfaces.
ISDN provides the following two types of services:
l Basic rate interface (BRI): It provides a rate of 144 kbit/s, and provides two B channels
and one D channel.
l Primary rate interface (PRI): In North America, it provides a rate of 1.544 Mbit/s, and
provides 23 B channels and one D channel. In other areas, it provides a rate of 2 Mbit/s,
and provides 30 B channels and one D channel.
The B channels are used for bearing the service and the D channel is used for transmitting the
call control signaling and the operation, administration and maintenance (OAM) signaling.
The UA5000 provides the ISDN BRA service to the subscribers through the DSL, DSLE/
DSLD board, and provides the ISDN PRA service to the subscribers through the PVMB, PVMD,
SDLE, or EDTB board.
Table 12-1 shows the number of ISDN BRA ports provided by each board.
Table 12-1 Number of ISDN BRA ports provided by each board

Board Ports
DSL 8 ISDN BRA ports
DSLD 16 ISDN BRA ports
Table 12-2 shows the number of ISDN PRA ports provided by each board.
Table 12-2 Number of ISDN PRA ports provided by each board

Board Ports
PVMB 4 E1 ports, namely, 4 ISDN PRA ports
PVMD 4 E1 ports, namely, 4 ISDN PRA ports

Board Ports
EDTB 16 E1 ports, namely, 16 ISDN PRA ports
SDLE 8 E1 ports, namely, 8 ISDN PRA ports
12.2 Configuration Example of the P2P ISDN BRA Service

This topic describes how to configure the point-to-point (P2P) ISDN BRA service through the
DSL service board. Thus, after the configuration, ISDN BRA subscribers can call each other,
and ISDN BRA subscribers and POTS subscribers can call each other.
Prerequisite
l The local IP address must be configured in the IP address pool.
l The system parameters and the MG interface attributes must be configured successfully.
The PSTN subscriber data on the MG interface must be configured successfully and the
PSTN subscribers must be able to call each other. For the operation procedure, see "10
Configuring the VoIP Service."
l The data on the MGC must be configured properly.
Networking
Figure 12-1 shows the example network of the P2P ISDN BRA service.
NOTE

Figure 12-1 Example network of the P2P ISDN BRA service
MGC
10.10.20.1/24
Router
10.10.10.1/24
H.248
0/8 0/11
I I P P
D D A
UA5000 P P V V
S S 3
10.10.10.2/24 M M M M
L L 2
B B B B
PBX PBX
ISDN phone A ISDN phone B Phone A
Data Plan
Table 12-3 provides the data plan for configuring the P2P ISDN BRA service.
Table 12-3 Data plan for configuring the P2P ISDN BRA service
Data Type Item Data
code text
protocol H.248
port MG: 2944

MGC: 2944
Whether the termination ID Not supported

on the MG interface supports
the layer configuration
terminalID 0, 2

Data Type Item Data
IP addresses The IP address of MG 0 on 10.10.10.2/24

the UA5000
Default gateway of MG 0 on 10.10.10.1/24

the UA5000
IUA link parameters IUA link number 15
IUA link set number 1
Local port number 1401
Peer port number 1400
IUA interface ID 8
DSL boards Shelf ID/slot ID 0/8, 0/11
ISDN BRA ports Shelf ID/slot ID/port ID 0/8/0, 0/11/0
Working mode P2P
Context
l One port can be connected to only one terminal.
l The terminal equipment identifiers (TEIs) of the ISDN digital phones must be 0.
l If the ISDN digital telephone is not provided with local power, the braport attribute batset
frameid/slotid/portid endframeid/slotid/portid rpower yes and braport attribute set
frameid/slotid/portid rpower yes commands must be executed on the UA5000 to enable
the remote power.
l The MG interface parameters configured on the UA5000 must be the same as the MG
interface parameters configured on the MGC.
Figure 12-2 shows the flowchart for configuring the ISDN service.

Figure 12-2 Flowchart for configuring the ISDN service
Start
Add service boards
Configure the working

mode of ISDN BRA port
Configure an IUA link

set and an IUA link
Configure the
SIGTRAN protocol
(Optional) Configure
SCTP parameters
Configure ISDN
subscriber data
Save the configuration

data
End
Procedure
Step 1 Add a DSL board.
huawei(config)#board add 0/8 dsl
0 frame 8 slot board has been confirmed
0 frame 11 slot board has been confirmed
Step 2 (Optional) Query the attributes of the ISDN BRA ports.

huawei(config-esl-user)#display braport attribute 0/8
------------------------------------------------------------------------------
F /S /P Remote-power Work-mode BAD BADDelay(s) Keep_L1_Active
------------------------------------------------------------------------------
0/8/0 No p2mp disable 30 enable
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------

F /S /P Remote-power Work-mode Bad BADDelay(s) Keep_L1_Active

-----------------------------------------------------------------------------
--------------------------------------------------------------------------------
Step 3 Configure the working modes of the ports.

huawei(config-esl-user)#braport attribute set 0/8/0 work-mode p2p
The board(s) may be reset before the configuration works , are you sure to
reset the board(s) when executing this command?(y/n)[n]:y
huawei(config-esl-user)#braport attribute set 0/11/0 work-mode p2p
The board(s) may be reset before the configuration works , are you sure to
reset the board(s) when executing this command?(y/n)[n]:y
Step 4 Add a link set and a link, query the configuration information of the link set and the link.
huawei(config)#sigtran
huawei(config-sigtran)#iua-linkset add 1
huawei(config-sigtran)#iua-link add 15 1 1401 10.10.10.2 1400 10.10.20.1
huawei(config-sigtran)#display iua-link attribute
----------------------------------------------------------------------
LinkNo : 15
LinksetNo : 1
Local prot : 1401
Local IP address : 10.10.10.2
Remote port : 1400
Remote IP address 1 : 10.10.20.1
Remote IP address 2 : -
InStreamNum : 33
OutStreamNum : 33
----------------------------------------------------------------------
huawei(config-sigtran)#display iua-link state

-------------------------------------------------------------------------
LinkNo LinkState LockFlag CongestFlag ListenId SctpAssocId
-------------------------------------------------------------------------
15 active unlock uncongest 1 3
-------------------------------------------------------------------------
Step 5 Add an ISDN BRA subscriber and configure the data.

huawei(config-sigtran)#quit
huawei(config-esl-user)#mgbrauser add 0/8/0 0 1 8 terminalid 0
huawei(config-esl-user)#mgbrauser add 0/11/0 0 1 10 terminalid 2
huawei(config-esl-user)#display mgbrauser 0/8/0
------------------------------------------------------------------------------
F /S /P MGID LinkSetNo UserIFID R.POWER TelNo Priority TID
------------------------------------------------------------------------------
0/ 8/ 0 0 1 8 No - Cat3 A0
------------------------------------------------------------------------------
huawei(config-esl-user)#display mgbrauser 0/11/0
------------------------------------------------------------------------------
------------------------------------------------------------------------------
0/ 11/ 0 0 1 8 No - Cat3 A2
------------------------------------------------------------------------------

huawei(config)#save
----End

Result
1. The ISDN BRA ports should be in the active state.
huawei(config-esl-user)#display port state 0/8/0
------------------------------------------------------------------------------
F/ S/ P Type SubType PortState SvcState SvcType UserType MgID ProtocolID
------------------------------------------------------------------------------
0/ 8/0 BRA 2B+D Active AutoBlk InstSvc MG 0 A0
-----------------------------------------------------------------------------
------------------------------------------------------------------------------
------------------------------------------------------------------------------
0/ 11/0 BRA 2B+D Active AutoBlk InstSvc MG 0 A2
-----------------------------------------------------------------------------
2. The working mode of the ISDN BRA ports should be P2P.

huawei(config-esl-user)#display braport attribute 0/8/0
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
0/ 8/0 No p2p disable 30 enable
-----------------------------------------------------------------------------
huawei(config-esl-user)#display braport attribute 0/11/0
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
0/11/0 No p2p disable 30 enable
-----------------------------------------------------------------------------
3. P2P ISDN BRA subscribers ISDN phone A and ISDN phone B should be able to call each
other. P2P ISDN BRA subscribers and POTS subscriber Phone A should be able to call
each other. The status of the ports with the P2P ISDN BRA service should always be in the
active state.
12.3 Configuration Example of the P2MP ISDN BRA Service

This topic describes how to configure the point-to-multipoint (P2MP) ISDN BRA service
through the DSL service board. After the configuration, ISDN BRA subscribers can call each
other, and ISDN BRA subscribers and POTS subscribers can call each other.
Prerequisite
l The local IP address must be configured in the IP address pool.
l The system parameters and the MG interface attributes must be configured successfully.
The PSTN subscriber data on the MG interface must be configured successfully and the
PSTN subscribers must be able to call each other. For the operation procedure, see "10
l One NT1 with power supply and two ISDN digital phones must be available. In addition,
the ISDN digital phones must be connected properly.

Networking
Figure 12-3 shows the example network of the P2MP ISDN BRA service.
NOTE
Figure 12-3 Example network of the P2MP ISDN BRA service
MGC
10.10.20.1/24
Router
10.10.10.1/24
H.248
0/15
I I P P
A D
UA5000 P P V V
3 S
10.10.10.2/24 M M M M
2 L
B B B B
NT1
Phone A ISDN phone ISDN phone
Data Plan
Table 12-4 provides the data plan for configuring the P2MP ISDN BRA service.
Table 12-4 Data plan for configuring the P2MP ISDN BRA service
Data Type Item Data
code text
protocol H.248

Data Type Item Data
port MG: 2944

MGC: 2944
terminalID 0, 1
IP addresses MG interface 0 on the 10.10.10.2/24

UA5000

IUA link parameters IUA link set number 1
IUA link number 15
ISDN BRA Port port ID 0/15/0, 0/15/1
interfaceid 8
Context
The MG interface parameters configured on the UA5000 must be the same as the MG interface
parameters configured on the MGC.
Figure 12-4 shows the flowchart for configuring the ISDN service.

Figure 12-4 Flowchart for configuring the ISDN service
Start
Add a DSL board
configure the working

mode of ISDN BRA port

set and an IUA link
Configure the
(Optional) Configure SIGTRAN protocol
SCTP parameters
Add an ISDN BRA

subscriber and
configure the data

data
End
Procedure
Step 1 Add a DSL board.
0 frame 15 slot board confirms successfully
--------------------------------------------------------
--------------------------------------------------------
0 H602PWX0 Normal
1 H602PWX0 Normal
2
3
4 H601PVMB Active_normal H601ETCB H601ETCB
5 H601PVMB Standby_normal H601ETCB H601ETCB
......
15 DSL Normal
......
35
--------------------------------------------------------
Step 2 Add an IUA link set and an IUA link.


----------------------------------------------------------------------
LinkNo : 15
LinksetNo : 1
Local prot : 9900
Remote port : 1400
InStreamNum : 33
OutStreamNum : 33
----------------------------------------------------------------------
--------------------------------------------------------------
--------------------------------------------------------------
--------------------------------------------------------------
Step 3 Add an ISDN BRA subscriber and configure the data.

huawei(config-esl-user)#mgbrauser batadd 0/15/0 0/15/1 0 1 8 terminalid 0
huawei(config-esl-user)#display port state 0/15
------------------------------------------------------------------------------
------------------------------------------------------------------------------
0/15/0 BRA 2B+D Deactive StartSvc InstSvc MG 0 A0
0/15/1 BRA 2B+D Deactive StartSvc InstSvc MG 0 A2
huawei(config-esl-user)#display mgbrauser 0/15
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
0/15/ 0 0 1 8 No - Cat3 A0
0/15/ 1 0 1 9 No - Cat3 A2
-----------------------------------------------------------------------------
Command:
display braport attribute 0/15
--------------------------------------------------------------------------
F /S /P Remote-power Work-mode BAD BADDelay(s) Keep-L1-active
--------------------------------------------------------------------------
----------------------------------------------------------------------------

huawei(config)#save
----End
Result
ISDN BRA subscribers should be able to call each other, and ISDN BRA subscribers and POTS
subscriber Phone A should be able to call each other.

12.4 Configuration Example of the ISDN PRA Service

(When the EDTB Service Board Is Used)
This topic describes how to configure the ISDN PRA service through the EDTB service board.
After the configuration, ISDN PRA subscribers can call each other, and ISDN PRA subscribers
and POTS subscribers can call each other.
Prerequisite
l The system parameters, the MG interface attributes, and the PSTN subscribers must be
configured successfully. For the operation procedure, see "10 Configuring the VoIP
Service."
l Several PBX subscribers must be configured.
Context
The MG interface parameters configured on the UA5000 must be the same as the parameters
Networking
Figure 12-5 shows the example network of the ISDN PRA service.
NOTE

Figure 12-5 Example network of the ISDN PRA service
MGC
10.10.20.1/24
Router
10.10.10.1/24 Router
FE/GE 0/13
I I P P E
UA5000 P P V V D
10.10.10.2/24 M M M M UA5000
T
B B B B B
PBX
Phone A Phone N Phone N+1
Data Plan
Table 12-5 provides the data plan for configuring the ISDN PRA service.
Table 12-5 Data plan for configuring the ISDN PRA service
Data Type Item Data
code text
protocol H.248
port MG: 2945

MGC: 2944
terminalid 0, 1
IP addresses MG interface 0 on the 10.10.10.2/24

UA5000

Data Type Item Data
Default gateway of the MG 10.10.10.1/24

IUA link parameters IUA link set number 2
IUA link number 1
Figure 12-6 shows the flowchart for configuring the ISDN PRA service.
Figure 12-6 Flowchart for configuring the ISDN PRA service
Start
Add an EDTB
board
Set the working mode

of the EDTB board
Add a link set and a

link
Configure the
SIGTRAN protocol
SCTP parameters
Add an ISDN PRA

subscriber and
configure the data

data
End

Procedure
Step 1 Add an EDTB board.
huawei(config)#board add 0/13 h601edtb
0 frame 13 slot board add successfully
0 frame 13 slot board confirms successfully
----------------------------------------------------------------------------------
----------------------------------------------------------------------------------
0 H602PWX0 Normal
1 H602PWX0 Normal
2
3
4 H601PVMB Active_normal H601ETCB H601ETCB
5 H601PVMB Standby_normal H601ETCB H601ETCB
......
13 H601EDTB Normal
......
35
----------------------------------------------------------------------------------
Step 2 Set the working mode of the EDTB board.

huawei(config)#interface edt 0/13
huawei(config-if-edt-0/13)#runmode indep
huawei(config-if-edt-0/13)#quit
Step 3 Add a link set and a link.

------------------------------------------------------------------
LinkNo : 1
LinksetNo : 2
Local port : 1402
Remote port : 1404
InStreamNum : 33
OutStreamNum : 33
------------------------------------------------------------------
-----------------------------------------------------------------
-----------------------------------------------------------------
-----------------------------------------------------------------
Step 4 Add an ISDN PRA subscriber and configure the data.

huawei(config-esl-user)#mgprauser add 0/13/0 0 2 10 terminalid 0
--------------------------------------------------------------------------
Frame/Slot/Port PortType PortState ServiceType SvcState
--------------------------------------------------------------------------
0 / 13 / 0 E1 Failed VOIP_PRA -
--------------------------------------------------------------------------
huawei(config-esl-user)#display mgprauser 0/13
----------------------------------------------------------
MGID 0
F/S/P 0/13/0
TerminalID A0
LinkSetNo 2

InterfaceID 10
Uni-report 1(0-enable 1-disable)
Auto-return-to-service-limit 20
Active-mask 255:255:255:255
User Priority is cat3
----------------------------------------------------------
Command processing completed. 1 port(s) are configured MG PRA user data

huawei(config)#save
----End
Result
ISDN PRA subscribers should be able to call subscribers who do not belong to the same PBX,
and subscribers who belong to one PBX should be able to call each other.
12.5 Configuring the SIGTRAN Protocol Stack

The signaling transport (SIGTRAN) protocol supports the transmission of traditional switched
circuit network (SCN) signaling over the IP network through protocol adaptation and
transmission.
l The SIGTRAN protocol, which is applied to the ISDN services of the UA5000, contains
the MAC, IP, SCTP and IUA protocols.
l Generally, you need not configure the SCTP protocol parameters.
l Parameters localipaddr, remoteipaddr, localport, and remoteport are used to set up an
IUA link between the UA5000 and the MGC. localport on the UA5000 must be the same
as remoteport on the MGC. remoteport on the UA5000 must be the same as localport
on the MGC.
Related Concept
l SIGTRAN protocol stack: The SIGTRAN protocol stack includes two layers of protocols:
transmission and adaptation. The transmission protocol is SCTP/IP and the adaptation
protocol can be M2UA (for MTP2 subscribers) or IUA (for Q. 921 subscribers). Figure
12-7 shows the model of the SIGTRAN protocol.

Figure 12-7 Model of the SIGTRAN protocol
M3UA M2UA IUA M2PA V5UA SUA

adaptation adaptation adaptation adaptation adaptation adaptation ......
layer layer layer layer layer layer
SCTP
IP
MAC
M3UA: MTP3 User Adaptation Layer IP: Internet Protocol

M2PA: MTP2 Peer Adaptation Layer IUA: ISDN Q. 921 User Adaptation Layer
SCTP: Stream Control Transmission Protocol SUA: SCCP User Adaptation Layer
M2UA: MTP2 User Adaptation Layer MAC: Media Access Control
V5UA: V5 User Adaptation Layer
l SCTP: The SCTP protocol is a connection-oriented protocol. The basic function of SCTP
is to provide reliable transmission for the messages between the UA5000 and the MGC.
SCTP functions based on the association between the two terminals of SCTP. SCTP can
be regarded as a transmission layer whose upper layer is the SCTP subscriber and the lower
layer is the IP network.
Figure 12-8 shows the flowchart for configuring the SIGTRAN protocol stack.
Figure 12-8 Flowchart for configuring the SIGTRAN protocol stack
Start
Configure an IUA link set
(Optional) Configure SCTP

parameters
End

Procedure
Step 1 In global config mode, run the sigtran command to enter the sigtran mode.
Step 2 Run the iua-linkset add command to add an IUA link set.
Step 3 Run the display iua-linkset state command to query the state of the IUA link set. Run the
display iua-linkset attribute command to query the attributes of the IUA link set.
Step 4 Run the iua-link add command to add an IUA link to the IUA link set.
Step 5 Run the display iua-link state command to query the state of the IUA link. Run the display
iua-link attribute command to query the attributes of the IUA link.
Step 6 (Optional) Run the sctp protocol command to configure the parameters of the SCTP protocol.
Step 7 (Optional) Run the display sctp protocol command to query the parameters of the SCTP
protocol.
----End
Example
To configure the SIGTRAN protocol stack, do as follows:
huawei(config-sigtran)#iua-linkset add 8 mgid 0
huawei(config-sigtran)#display iua-linkset state
-----------------------------------------
LinksetNo LinkNum LinksetState
-----------------------------------------
8 0 down
-----------------------------------------
huawei(config-sigtran)#display iua-linkset attribute
----------------------------------------------------------------------------
LinksetNo MgId Pendingtime TrafficMode Client/Server UseTxtIf
----------------------------------------------------------------------------
8 0 4 override server integer
----------------------------------------------------------------------------
NOTE
l In the SIGTRAN protocol, localipaddr, localport, remoteipaddr, and remoteport can uniquely identify
an SCTP association.
l A UA5000 can be configured with a maximum of eight links and eight link sets.
--------------------------------------------------------
--------------------------------------------------------
--------------------------------------------------------
huawei(config-sigtran)#display iua-link attribute 1
----------------------------------------------------------------------
LinkNo : 1
LinksetNo : 8
Local port : 1401
Remote port : 1400
InStreamNum : 33

OutStreamNum : 33
----------------------------------------------------------------------

Configuration Guide-PVM CLI 13 Configuring the FoIP Service
13 Configuring the FoIP Service
About This Chapter
Configuring the FoIP service includes the application of the FoIP technology and the related
process for configuring the FoIP service of the UA5000.
13.1 Introduction to the FoIP Service

Fax over Internet Protocol (FoIP) is a method of providing the fax service over the IP network
or between the IP network and the traditional PSTN network.
13.2 Configuring the V2 Transparent Transmission Flow
In the V2 transparent transmission flow, the voice port functions as the fax port, and the fax
signals are encoded in the G.711 encoding mode, in which the voice signals are encoded.
13.3 Configuring the Selfswitch Transparent Transmission Flow
In the selfswitch transparent transmission flow, the UA5000 determines whether to add 2 to the
voice port number to set the fax port.
13.4 Configuring the V2 T.38 Flow
When the V2 T.38 flow is used, the UA5000 must determine whether to add 2 to the voice port
ID to set the fax port based on the requirement of the MGC. The fax settings for the receiver
should be the same as the fax settings for the sender.
13.5 Configuring the Selfswitch T.38 Flow
When the selfswitch T.38 flow is used, the UA5000 need not be controlled by the MGC for the
fax service.
13.6 Configuring the V3 Flow
In the V3 flow, you can use either the transparent transmission mode or the T.38 mode on the
UA5000, which is determined by the mode configured on the MGC. If the MGC uses the T.38
mode, the fax port ID can be negotiated.
The V5 flow is compatible with the V2 flow and the V3 flow. When the peer fax machine uses
the V2 or V3 flow, the local fax machine that uses the V5 flow can communicate with the peer
fax machine properly.
13.8 Configuring the High-Speed Fax

If the network communication is of a high quality and the fax machines support the high-speed
fax service, you can configure a high-speed fax mode to transmit the signals. In the high-speed
mode, the signals are transmitted in the modem mode.
13.9 Configuring the High-Low Speed Selfswitch Fax
fax service, the data can be transmitted in the high-speed fax mode. In the high-speed fax mode,
the signals are transmitted in the modem mode. When the quality of the network communication
deteriorates, and the high-speed negotiation fails, the UA5000 automatically switches to the low
speed fax mode. In the low-speed fax mode, the signals are transmitted in the fax mode.
13.10 Configuring the Fax Transmission Parameters
The fax transmission parameters for the MG include the transmission mode, 10 ms packetization
function, and RFC 2198 intelligent start function. You can configure the fax transmission
parameters according to the actual application environment to ensure the quality of the fax
service.
13.11 Configuring the Fax Training Parameters
Configuring the fax training parameters includes configuring the fax training mode and the
maximum rate of fax training. The fax training mode takes effect only in the T.38 flow. The
maximum rate of fax training takes effect only in the T.38 local training flow.

13.1 Introduction to the FoIP Service

Fax over Internet Protocol (FoIP) is a method of providing the fax service over the IP network
or between the IP network and the traditional PSTN network.
Service Description
The fax service is widely used in the PSTN. The fax machine in the POTS service is supported
in the NGN network, that is the FoIP. The FoIP is a type of service that provides the transmission
of FoIP over the IP network or between the IP network and the PSTN network.
l The UA5000 provides the fax service and the voice service through the voice service
boards. Table 13-1 shows the number of ports provided by each type of service boards.
Table 13-1 Number of ports provided by each voice service boards

Board Type Number of Ports Description
CSRB 32 32-port POTS and ADSL/

ADSL2+ combo service board
l Table 13-2 shows the fax flows supported by the UA5000.
Table 13-2 Fax flow list

Fax Flow Remarks
Transparent V2 transparent transmission The transparent transmission

transmission fax flow flow supports high-low speed
flow selfswitch fax.
Selfswitch transparent
transmission flow
V3 flow
V5 flow
T.38 fax flow V2 T.38 flow The T.38 flow does not support
high-speed fax or high-low
Selfswitch T.38 flow speed selfswitch fax.
V3 flow
V5 flow
l The following part describes each fax flow mode and the principles of using each fax flow
mode:

– According to whether the MGC is involved, the fax mode can be V2 fax or selfswitch
fax. According to the coding mode, the fax mode can be transparent transmission fax
(G.711 coding) or T.38 fax (T.38 coding).
– If the SoftSwitch does not support the fax service and the UA5000 functions as the
transmit and receive gateway, either the selfswitch transparent transmission mode or
the selfswitch T.38 mode can be used.
– To enhance the intelligence of the fax service (the support from the SoftSwitch and the
peer gateway is required), use the V3 flow.
– If the SoftSwitch supports the V5 flow, but the peer gateway supports only the V2 flow,
V3 flow, or V5 flow, use the V5 flow.
– In the V3 T.38 or V5 T.38 flow, the fax mode is controlled by the MGC. For example,
if the flow on the UA5000 is V3, and the flow on the MGC is V3 T.38, the UA5000
uses the V3 T.38 flow.
– The transparent transmission flow and the T.38 flow support low-speed fax. In the low-
speed fax, data is transmitted in the fax mode. The transparent transmission flow
supports high-speed fax and high-low speed selfswitch fax. In the high-speed fax, data
is transmitted in the modem mode.
13.2 Configuring the V2 Transparent Transmission Flow

In the V2 transparent transmission flow, the voice port functions as the fax port, and the fax
signals are encoded in the G.711 encoding mode, in which the voice signals are encoded.
Prerequisite
l The data on the MGC must be accurate.
l The FoIP service is implemented based on the voice service. Before you configure the FoIP
service, the voice service data must be configured properly and the subscribers must be
able to call each other successfully. For the configuration of the voice service, see "10
Context
The fax mode for the UA5000 and the MGC must be the transparent transmission mode.
Figure 13-1 shows the flowchart for configuring the V2 transparent transmission flow.

Figure 13-1 Flowchart for configuring the V2 transparent transmission flow
Start
Set the fax

transmission mode
Query the fax

transmission mode
(Optional) Set the fax

training mode
(Optional) Query the fax

training mode
End
Procedure
Step 1 Run the fax parameters tranmode command to set the fax transmission mode as the transparent
transmission mode.
NOTE
You can select not to set the fax training mode in the V2 transparent transmission flow. If you need to set
the fax training mode, set the same mode on the MG and on the MGC.
Step 2 Run the display fax parameters command to query the fax parameters.
Step 3 (Optional) Run the dsp attribute train-mode command to set the fax training mode.
Step 4 (Optional) Run the display dsp attribute command to query the dsp channel mode.
----End
Example
To configure the V2 transparent transmission flow on the UA5000, do as follows:
huawei(config)#fax parameters tranmode 0
huawei(config)#display fax parameters
-----------------------------------------------------------------------------
Fax transfers mode :V2 thoroughly
T38 Fax Port :RTP port
Fix the package interval as 10ms :disable
RFC2198 intelligent startup :enable
-----------------------------------------------------------------------------
huawei(config)#dsp attribute train-mode 0


-----------------------------------------------------------------------------
Fax Train Mode :Remote Train
DSP input gain(PCM->IP)(db) :0
DSP output gain(IP->PCM)(db) :0
DSP code type :G711A
Support VQM :Disable
DSP silence reduce :Close
DSP need statistics or not :No
DSP Packet Lose Compensate :Close
-----------------------------------------------------------------------------
13.3 Configuring the Selfswitch Transparent Transmission

Flow
In the selfswitch transparent transmission flow, the UA5000 determines whether to add 2 to the
voice port number to set the fax port.
Prerequisite
l The FoIP service is implemented based on the voice service. Hence, before the FoIP service
is configured, the voice service data must be configured properly and the subscribers must
be able to call each other successfully. For the configuration of the voice service, see "10
Context
l The fax transmission mode must be configured only on the UA5000.
l To ensure that the fax service is implemented, the fax training modes on the two
UA5000s must be the same, that is, the mode must be either the end-to-end training mode
or the local training mode. The end-to-end training mode is recommended.
Figure 13-2 shows the flowchart for configuring the selfswitch transparent transmission.

Figure 13-2 Flowchart for configuring the selfswitch transparent transmission
Start
Set the fax

transmission mode
Query the fax

transmission mode

training mode

training mode
End
Procedure
Step 1 Run the fax parameters tranmode command to set the fax transmission mode as the transparent
transmission mode.
Step 4 (Optional) Run the display dsp attribute command to query the DSP channel mode.
----End
Example
To configure the V2 transparent transmission flow on the UA5000, do as follows:
-----------------------------------------------------------------------------
Fax transfers mode :Self switch thoroughly
RFC2198 intelligent startup :disable
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------


-----------------------------------------------------------------------------
13.4 Configuring the V2 T.38 Flow

When the V2 T.38 flow is used, the UA5000 must determine whether to add 2 to the voice port
ID to set the fax port based on the requirement of the MGC. The fax settings for the receiver
should be the same as the fax settings for the sender.
Prerequisite
Context
l If the fax machines are connected to the same MG, the T.38 fax port ID can be configured
at random. If they are connected to different MGs, the configurations of adding 2 to the fax
port ID must be the same. That is, 2 is added to both or none of the fax port IDs.
l To ensure that the fax service is implemented successfully, the fax training modes at both
ends of the MG must be the same, that is, the mode must be either the end-to-end training
mode or the local training mode. The end-to-end training mode is recommended.
Figure 13-3 shows the flowchart for configuring the V2 T.38 fax service.

Figure 13-3 Flowchart for configuring the V2 T.38 fax service
Start
Set the fax transmission

mode
Set the T.38 fax port
Query the fax

transmission mode

training mode
(Optional) Query the

attributes of the DSP channel
End
Procedure
Step 1 Run the fax parameters tranmode command to set the V2 T.38 mode as the fax transmission
mode.
Step 2 Run the fax parameters is-port+2 command to set the T.38 fax port.
Step 5 (Optional) Run the display dsp attribute command to query the attributes of the DSP channel.
----End
Example
To configure the V2 T.38 flow, do as follows:
huawei(config)#fax parameters is-port+2 0
-----------------------------------------------------------------------------
Fax transfers mode :V2 T38
-----------------------------------------------------------------------------


-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
13.5 Configuring the Selfswitch T.38 Flow

When the selfswitch T.38 flow is used, the UA5000 need not be controlled by the MGC for the
fax service.
Prerequisite
Figure 13-4 shows the flowchart for configuring the selfswitch T.38.

Figure 13-4 Flowchart for configuring the selfswitch T.38
Start
Set the fax

transmission mode
Query the fax

transmission mode

training mode

training mode
End
Procedure
Step 1 Run the fax parameters tranmode command to set the selfswitch T.38 mode as the fax
transmission mode.
Step 4 (Optional) Run the display dsp attribute command to query the attributes of the DSP.
----End
Example
To set the selfswitch T.38 mode on the UA5000, do as follows:
-----------------------------------------------------------------------------
Fax transfers mode :Self switch T38
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------


-----------------------------------------------------------------------------

In the V3 flow, you can use either the transparent transmission mode or the T.38 mode on the
UA5000, which is determined by the mode configured on the MGC. If the MGC uses the T.38
mode, the fax port ID can be negotiated.
Prerequisite
Context
In the T.38 mode, the fax port ID is negotiated. In the V3 flow, you can set one fax port ID as
the voice port ID and the other fax port ID as the voice port ID plus 2. The settings result in the
fax service failure in the V2 flow. The fax process in the V3 flow on the UA5000 is controlled
by the MGC. For example, the training mode, coding mode, and port ID are issued by the MGC.
Figure 13-5 shows the flowchart for configuring the V3 flow service.

Figure 13-5 Flowchart for configuring the V3 flow service
Start

mode
Query the fax

transmission mode
End
Procedure
Step 1 Run the fax parameters tranmode command to set the fax transmission mode as the V3 mode.
NOTE
In the V3 flow, the MGC issues the fax training mode. Hence, you need not configure the fax training mode
on the UA5000.
----End
Example
To configure the V3 flow, do as follows:
-----------------------------------------------------------------------------
Fax transfers mode :V3 flow
-----------------------------------------------------------------------------

The V5 flow is compatible with the V2 flow and the V3 flow. When the peer fax machine uses
the V2 or V3 flow, the local fax machine that uses the V5 flow can communicate with the peer
fax machine properly.
Prerequisite

Context
In the V5 flow, you can use either the transparent transmission mode or the T.38 mode, which
is determined by the mode configured on the MGC.
Figure 13-6 shows the flowchart for configuring the V5 flow.
Figure 13-6 Flowchart for configuring the V5 flow
Start
Set the fax

transmission mode
Query the fax

transmission mode

training mode

training mode
End
Procedure
Step 1 Run the fax parameters tranmode command to set the V5 mode as the fax transmission mode.
Step 4 (Optional) Run the display dsp attribute command to query the attributes of the DSP channel.
----End
Example
To configure the V5 flow on the UA5000, do as follows:


-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
13.8 Configuring the High-Speed Fax

fax service, you can configure a high-speed fax mode to transmit the signals. In the high-speed
mode, the signals are transmitted in the modem mode.
Prerequisite
Context
To implement the high-speed fax service, the following requirements must be met:
l Both the UA5000 and the MGC must support the high-speed fax service, and the fax
transmission mode must not be the selfswitch T.38 mode or the selfswitch transparent
transmission mode.
l The fax machines must support the high-speed fax service.
Figure 13-7 shows the flowchart for configuring the high-speed fax.

Figure 13-7 Flowchart for configuring the high-speed fax
Start
Query the fax transmission

mode
No
Selfswitch thoroughly
or Selfswitch T38
mode?
Yes
mode
Query the modem

transmission mode
End
Procedure
Step 1 Run the display fax parameters command to query the fax transmission mode.
Step 2 If the fax transmission mode is the selfswitch T.38 mode or the selfswitch transparent
transmission mode, run the fax parameters tranmode command to change the fax transmission
mode to the fax transmission mode that can be configured. If the fax transmission mode is not
the selfswitch T.38 mode or the selfswitch transparent transmission mode, skip this step.
Step 3 Run the display modem parameters command to query modem parameters.
Step 4 If the modem transmission mode is the transparent transmission mode, the configuration is not
required.
----End
Example
To configure the UA5000 with the transparent transmission flow so that the UA5000 supports
the high-speed fax, do as follows:
-----------------------------------------------------------------------------
Fax transfers mode :Self switch T38

-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
huawei(config)#display modem parameters
-----------------------------------------------------------------------------
Modem transfers mode :Thoroughly
Modem event mode :Direct
-----------------------------------------------------------------------------
13.9 Configuring the High-Low Speed Selfswitch Fax

fax service, the data can be transmitted in the high-speed fax mode. In the high-speed fax mode,
the signals are transmitted in the modem mode. When the quality of the network communication
deteriorates, and the high-speed negotiation fails, the UA5000 automatically switches to the low
speed fax mode. In the low-speed fax mode, the signals are transmitted in the fax mode.
Prerequisite
Context
l To implement the high-low speed selfswitch fax service, both the UA5000 and the MGC
must support the high-speed fax service, and the UA5000 must use the direct report mode
as the modem event report mode.
l To implement the high-speed fax service, the fax machines must support the high-speed
fax service.
l To configure the high-low speed selfswitch fax service, the fax mode cannot be the
selfswitch mode.
Figure 13-8 shows the flowchart for configuring the high-low speed selfswitch fax.

Figure 13-8 Flowchart for configuring the high-low speed selfswitch fax
Start
Set the modem event report mode
Set the modem transmission mode
Query the modem parameters
Set the Fax transmission mode
Query the Fax parameters
End
Procedure
Step 1 Run the modem parameters eventmode command to set the direct report mode as the modem
event report mode.
Step 2 Run the modem parameters tranmode command to set the transparent transmission mode as
the modem transmission mode.
Step 3 Run the display modem parameters command to query the modem parameters.
----End
Example
To configure the UA5000 with the transparent transmission flow so that the UA5000 supports
the high-low speed selfswitch fax, do as follows:
huawei(config)#modem parameters eventmode 1
huawei(config)#modem parameters tranmode 0
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------

//The mode cannot be set to the selfswitch mode (namely, 3: Selfswitch thoroughly
or 5: Selfswitch T38).
-----------------------------------------------------------------------------
Fax transfers mode :V2 thoroughly
-----------------------------------------------------------------------------
13.10 Configuring the Fax Transmission Parameters

The fax transmission parameters for the MG include the transmission mode, 10 ms packetization
function, and RFC 2198 intelligent start function. You can configure the fax transmission
parameters according to the actual application environment to ensure the quality of the fax
service.
Context
The fax transmission parameters of the UA5000 include the following:
l Transmission mode: the transmission mode supported by the fax service. The UA5000
supports the selection of different transmission modes according to the actual coding
scheme and the participating degree of the MGC. The transmission mode can be the
following:
– Transparent transmission mode
– Auto-negotiation T.38 mode
– V3 flow
– Selfswitch transparent transmission mode
– V5 flow
– Selfswitch T.38 mode
l 10 ms packetization function: Based on the 20 ms G711 transparent transmission, the 10
ms G711 transmission function is supported. This reduces the delay in the transmission and
improves the performance of the transparent transmission.
l RFC 2198 intelligent start function: RFC 2198 uses the redundancy transmission mode to
improve the reliability of the data transmission, and to ensure the service quality when the
network quality is poor.
NOTE
When the protocol supported by the system is MGCP, parameter tranmode cannot be set to 4.
Procedure
Step 1 Run the fax parameters command to set the fax transmission parameters.
Step 2 Run the display fax parameters command to query the fax transmission parameters.
----End
Example

l The fax transmission mode is auto-negotiation T.38.

l The T.38 port ID is equal to the voice port ID.
l The 10 ms packetization function is enabled for the enhanced function of the transparent
transmission.
l The RFC 2198 intelligent startup function is enabled.
To configure the fax parameters, do as follows:
huawei(config)#fax parameters tranmode 1 is-port+2 0 packet-interval-10ms 1
rfc2198 1
Parameter 10ms packing and modification for rfc2198 intelligent startup is
effecitive to both fax and modem
13.11 Configuring the Fax Training Parameters

Configuring the fax training parameters includes configuring the fax training mode and the
maximum rate of fax training. The fax training mode takes effect only in the T.38 flow. The
maximum rate of fax training takes effect only in the T.38 local training flow.
Context
In the T.38 flow, the fax training mode on both UA5000s must be the same. That is, the mode
must be either the end-to-end training mode or the local training mode. The end-to-end training
mode is recommended.
When the quality of the network communication deteriorates, decrease the rate of the fax training
accordingly, if the rate of the fax machine can be decreased.
Procedure
Step 1 Run the dsp attribute train-mode command to set the fax training parameters.
Step 2 Run the dsp attribute train-rate command to set the maximum training rate.
Step 3 Run the display dsp attribute command to query the attributes of the DSP .
----End
Example
To set the fax training mode of the UA5000 as the end-to-end training mode and the maximum
training rate as V29, do as follows:
huawei(config)#dsp attribute train-mode 0 train-rate 1
-----------------------------------------------------------------------------
DSP input gain(PCM->IP)(db) :-8
DSP code type :G729


DSP silence reduce :Open
DSP Packet Lose Compensate :Open
-----------------------------------------------------------------------------

Configuration Guide-PVM CLI 14 Configuring the MoIP Service
14 Configuring the MoIP Service
About This Chapter
Configuring the MoIP service includes the application of the MoIP technology and the related
process for configuring the MoIP service of the UA5000.
14.1 Introduction to the MoIP Service

Modem over IP (MoIP) provides the modem service over the IP network or between the IP
network and the PSTN network.
14.2 Configuring the MoIP Service
Configure the MoIP service so that the traditional modem data service can be transmitted over
the IP network.
14.3 Configuring the Modem Transmission Parameters
Configure the modem transmission parameters for the MG. The modem transmission parameters
for the MG includes the transmission mode, 10 ms package function, RFC 2198 intelligent start
function, and modem event reporting mode.

14.1 Introduction to the MoIP Service

Modem over IP (MoIP) provides the modem service over the IP network or between the IP
network and the PSTN network.
Service Description
The MoIP means the service of connecting modems to the terminals of the traditional POTS
subscribers to implement the MoIP functions. The modem service is widely used in the PSTN
network. The NGN networking supports the modem device of the traditional PSTN service,
namely, the MoIP.
In the modem service and the voice service, the subscriber access ports are provided by the voice
service boards. Table 14-1 lists the number of ports provided by each type of service boards.
Table 14-1 Number of ports provided by each type of service boards
Board Type Number of Ports Description
CSRB 32 32-port POTS and ADSL/ADSL2+

combo service board
14.2 Configuring the MoIP Service

Configure the MoIP service so that the traditional modem data service can be transmitted over
the IP network.
Prerequisite
l The MoIP service is implemented based on the voice service. Before you configure the
MoIP service, the voice service data must be configured properly and the subscribers must
be able to call each other successfully. For the configuration of the voice service, see "10
Context
The UA5000 supports only the modem service that is in the transparent transmission mode. That
is, the UA5000 processes the modem signals as the common RTP data by using the G.711 codec.
The transparent transmission mode is used depending on the bearer network. Therefore, when
the connection breaks, or a low access rate or an instability occurs, you can check the packet
loss rate and the delay jitter index of the bearer network.

Procedure
Step 1 Run the modem parameters tranmode command to set the modem transmission mode.
----End
Example
To set the modem transmission mode as the transparent transmission mode, do as follows:
-----------------------------------------------------------------------------
RFC2198 intelligent startup :enable
-----------------------------------------------------------------------------
NOTE
Only the modem service in transparent transmission mode is supported, and the modem service in relay
mode is not supported.
14.3 Configuring the Modem Transmission Parameters

Configure the modem transmission parameters for the MG. The modem transmission parameters
for the MG includes the transmission mode, 10 ms package function, RFC 2198 intelligent start
function, and modem event reporting mode.
Prerequisite
l The data on the MGC side must be configured correctly.
l The MoIP service is provided on the basis of the voice service. Before you configure the
MoIP service, the voice service must be configured correctly and the call between
subscribers must be normal. For the configuration of the voice service, see "10 Configuring
the VoIP Service."
Context
The transmission parameters of the UA5000 include:
l Transmission mode: The UA5000 supports only the modem service in transparent
transmission mode. The modem signal is processed as the common RTP data by using the
G.711 codec. The transparent transmission mode is used depending on the bearer network.
Therefore, when the connection breaks, or a low access rate or an instability occurs, you
can check the packet loss rate and delay jitter index of the bearer network.
l 10 ms packetization function: Based on the 20 ms G711 transparent transmission, the
UA5000 supports the 10 ms G711 transmission function. This reduces the delay, improves
the performance of the transparent transmission, and reduces the impact of the network
packet loss on the modem transmission.
l RFC 2198 intelligent start function: The RFC 2198 uses the redundancy transmission mode
to improve the reliability of the data transmission, and to ensure the service quality when
the packet loss occurs in the network.

l Modem event reporting mode:

– In direct reporting mode, after the UA5000 receives a modem event, it reports the event
to the softswitch.
– In delay reporting mode, after the UA5000 receives a modem event, it does not report
the event immediately, but waits until the event times out. Then, if no V21 flag (the fax
even) is reported, the host reports the modem event. In this way, when the high-speed
fax machine fails in the high-speed transmission (by modem) negotiation, it can transmit
data in low-speed transmission (by fax) mode.
Procedure
Step 1 Run the modem parameters tranmode command to configure the modem transmission
parameters.
----End
Example
To configure the modem transmission mode of the UA5000 as the transparent transmission
mode, to configure the modem event reporting mode as the delay reporting mode, and to enable
the RFC 2198 intelligent start function and the 10 ms package function, do as follows:
huawei(config)#modem parameters eventmode 1 packet-interval-10ms 1 rfc2198 1
{ <cr>|tranmode<K> }:
Command:
modem parameters eventmode 1 packet-interval-10ms 1 rfc2198 1
Parameter 10ms packing and modification for rfc2198 intelligent startup is
effecitive to both fax and modem
NOTE
Only the modem service in transparent transmission mode is supported, and the modem service in relay
mode is not supported.

Configuration Guide-PVM CLI 15 Configuring the R2 Access Service
15 Configuring the R2 Access Service
About This Chapter
Configuring the R2 access service includes the application of the R2 technology and the process
for configuring the R2 access service on the UA5000.
15.1 Introduction to the R2 Access Service

A signaling system (SS) is an important part of the communication network. It is a tool for the
nodes in the communication network to exchange information. The inter-office signaling
includes the channel associated signaling (CAS) and common channel signaling (CCS). The R2
signaling is a common CAS.
15.2 Configuration Example of the R2 Access Service
This topic describes how to configure the R2 access service on the UA5000-1 through the
signaling mode and the basic parameters of R2 profile of the E1 port on the EDTB board of the
UA5000-1.
15.3 Adding an R2 Profile
You can define an R2 signaling with certain characteristics as an R2 profile. The R2 profile
index can be referenced by the MG R2 subscribers. That is, the R2 profile is valid for the MG
R2 subscribers who reference this profile.
15.4 Configuring the Adaptation Data of the R2 Profile
Configure the R2 profile data, including the R2 address receiving attributes, R2 address sending
attributes, R2 profile attributes, R2 line signaling attributes, and register signaling attributes.
15.5 Loading an R2 Signaling Configuration File
You can integrate the R2 signaling conversion tables into a script file. Then, configure the R2
signaling conversion table of the UA5000 by loading the script file.

15.1 Introduction to the R2 Access Service

A signaling system (SS) is an important part of the communication network. It is a tool for the
nodes in the communication network to exchange information. The inter-office signaling
includes the channel associated signaling (CAS) and common channel signaling (CCS). The R2
signaling is a common CAS.
Service Description
To unify the inter-office signaling, the ITU-T makes recommendations for signaling and finally
forms the signaling systems 1 to 7, R1 signaling, and R2 signaling in succession. Among them,
SS1 to SS5, R1, and R2 are CAS. R2 is a common CAS. Generally, different countries define
their own national standard for CAS according to the ITU-T recommendations. For example,
China defines Signaling No. 1, which is different from the standard R2 to a certain extent.
The description of each signaling is as follows:
l CAS
The signaling information is transmitted within the voice channel. The inter-office
signaling of the CAS signaling consists of line signaling (supervisory signals) and register
signaling (with control function).
l R2 signaling
It is a type of CAS. The R2 signaling can be used in international and national networks.
Signaling No. 1, used in China, is a subset of the R2 signaling. The R2 signaling consists
of line signaling and register signaling.
l Line signaling
It controls the transmission path between switches or the transmission path inside a switch.
During a call, the line signaling is used to set up, maintain, release, and monitor the selected
route. The line signaling can be forward or backward and is categorized into analog line
signaling and digital line signaling. Currently, only the digital R2 line signaling is provided
for the switching and wireless overseas products. The digital line signaling is fixedly
transmitted through timeslot 16 of each 30/32-channel pulse code modulation (PCM).
l Register signaling
It provides the address and other information required for call routing and related call
processing. The register signaling is used to send and request for the caller and called
numbers, as well as sending caller subscriber type, called subscriber state, and call service
type. The register signaling complies with the multiple frequency control (MFC) principle.
It is transmitted in the voice channel and it occupies the voice channel resources. It is
transmitted before the call is set up, but it cannot be transmitted during a call session.
l Forward signaling and backward signaling
– Forward signaling is sent from the calling office to the called office.
– Backward signaling is sent from the called office to the calling office.
The UA5000 provides the R2 access service through the EDTB board. Table 15-1 lists the
number of ports provided by the EDTB board.

Table 15-1 Number of ports provided by the EDTB board

Board Type Number of Ports Remarks
EDTB 16 16-port E1 service board
15.2 Configuration Example of the R2 Access Service

This topic describes how to configure the R2 access service on the UA5000-1 through the
signaling mode and the basic parameters of R2 profile of the E1 port on the EDTB board of the
UA5000-1.
Prerequisite
l The UA5000-1 must support the R2 CAS and the PBX user must be configured on
UA5000-1.
l The data of phone D must be configured properly on the UA5000-2.
l The PBX must support the R2 CAS. The PBX must be configured properly. Phones A, B
and C must communicate with each other properly.
l The physical connection between the PBX and the UA5000-1 must be correct.
Context
In the R2 CAS configuration, a large amount of data is configured through the script file provided
by Huawei according to the signaling standard of a specific country (such as CAS conversion
table). Therefore, you need not configure this part of the data. This section provides a simplified
configuration example to make you familiar with the flowchart for configuring the R2 access
service.
Networking
Figure 15-1 shows the example network of the R2 access service.

Figure 15-1 Example network of the R2 access service
MGC
H.248 H.248
UA5000-1 UA5000-2
R2 E1
PBX
Phone A Phone B Phone C Phone D
NOTE
The UA5000 converts the R2 CAS into the H.248 messages, and then reports the messages to the MGC.
At the same time, the UA5000 receives the H.248 messages and converts them into the R2 CAS. In this
way, the MGC that uses H.248 and the PBXs or the switches that use the R2 CAS can communicate with
each other.
Data Plan
Table 15-2 provides the data plan for configuring the R2 access service.
Table 15-2 Data plan for configuring the R2 access service
Item Data Item Data
R2 profile index 0 R2 profile name Argentina
R2 signaling type Argentina R2 Shelf ID/slot ID/port 0/7/2

signaling ID of the MG R2
subscribers
mgid 0 start-terminalid 0
Figure 15-2 shows the flowchart for configuring the R2 access service.

Figure 15-2 Flowchart for configuring the R2 access service
Start
Add an EDTB board
Set the working mode

of the EDTB board
Set the signaling

mode of the E1 port
Add an R2 profile
Configure the R2
profile data
Configure the Configure the Configure the Configure the

Configure the
R2 address R2 address R2 line R2 interregister
R2 profile
receiving sending signaling signaling
attributes
attributes attributes attributes attributes
Add an R2 subscriber
End
Procedure
Step 1 Add and confirm an EDTB board.
Step 2 Set the working mode of the EDTB board.

Step 3 Set the signaling mode of the E1 port.

huawei(config-if-edt-0/7)#e1port signal 2 cas
huawei(config-if-edt-0/7)#display port mode
------------------------------------------------------------------------------
Port Signalling CRC4 Impedance Service flag-interval-index
----------------------------------------------------------------------------

0 CCS Disable 75 - -
2 CAS Disable 75 - -
-----------------------------------------------------------------------------
Step 4 Query the version and type of the R2 signaling.

huawei(config)#display r2 signaling-type
---------------------------------------------------------
R2 signaling-type
---------------------------------------------------------
file version: 100
signaling-type: 0 - Standard_R2
1 - Brazil_R2
2 - Argentina_R2
3-15: Extend_R2
---------------------------------------------------------
Step 5 Add an R2 profile.

huawei(config)#r2 profile 0
Are you sure to add r2 profile?(y/n)[n]:y
huawei(config-r2-0)#
Step 6 Configure the R2 profile.

huawei(config-r2-0)#profile attribute name brazil signaling-type 2
Step 7 Query the details of the R2 profile.

huawei(config-r2-0)#display profile detail
---------------------------------------------------------
R2 signaling profile
---------------------------------------------------------
index: 0
name: brazil
signaling-type: 2
---------------------------------------------------------
R2 line-signaling attribute
---------------------------------------------------------
type(0:L1B,1:L2B,2:L3B,3:PULSE): 1
wait-seize-ack-time(ms): 5000
wait-answer-time(s): 300
wait-clear-forward-time(ms): 200
wait-protect-time(ms): 200
---------------------------------------------------------
R2 register-signaling attribute
---------------------------------------------------------
type(0:MFC,1:PULSE,2:DTMF,3:MFP,4:DPMFP):0
signal-send-voltage(dBm): 13
back-pulse-time(ms): 150
dtmf-send-time(ms): 68
dtmf-send-interval(ms): 68
no-cid-permit(yes/no): yes
number-max-interval(s): 50
signal-keep-max-time(s): 15
receive-number-max-interval(s): 50
signal-stop-permit-time(s): 15

wait-caller-category-time(s): 50
wait-Bsignal-time(s): 50
number-send-mode(0:immediate,1:delay): 1
calling-number-max-length: 12
compelling-sequence-keepalive-time(ms): 40000
send-pulse-signal(yes/no): no
---------------------------------------------------------
R2 address-receive attribute
---------------------------------------------------------
DI: yes
SI: yes
SC: yes
ES: no
CC: no
DISC: no
NAC: no
SP: no
RCPS: 1
RCCP: 1
---------------------------------------------------------
R2 address-send attribute
---------------------------------------------------------
DI: yes
SI: yes
SC: yes
ES: no
CC: no
DISC: no
NAC: no
SP: no
---------------------------------------------------------
Step 8 Add a media gateway (MG) R2 subscriber.

huawei(config-r2-0)#quit
huawei(config-esl-user)#mgr2user add 0/7/2 0 0 start-terminalid 0
huawei(config-esl-user)#display mgr2user state 0/7/2
----------------------------------------------
F / S/ P/ TS ServiceState TerminalID
----------------------------------------------
0/ 7/ 2/ 0 Fault 0
0/ 7/ 2/ 1 Fault 1
0/ 7/ 2/ 2 Fault 2
0/ 7/ 2/ 3 Fault 3
0/ 7/ 2/ 4 Fault 4
0/ 7/ 2/ 5 Fault 5
0/ 7/ 2/ 6 Fault 6
0/ 7/ 2/ 7 Fault 7
0/ 7/ 2/ 8 Fault 8
0/ 7/ 2/ 9 Fault 9
0/ 7/ 2/ 10 Fault 10
0/ 7/ 2/ 11 Fault 11
0/ 7/ 2/ 12 Fault 12
0/ 7/ 2/ 13 Fault 13
0/ 7/ 2/ 14 Fault 14
0/ 7/ 2/ 15 Fault 15
0/ 7/ 2/ 16 Fault 16
0/ 7/ 2/ 17 Fault 17
0/ 7/ 2/ 18 Fault 18
0/ 7/ 2/ 19 Fault 19
0/ 7/ 2/ 20 Fault 20
0/ 7/ 2/ 21 Fault 21
0/ 7/ 2/ 22 Fault 22
0/ 7/ 2/ 23 Fault 23
0/ 7/ 2/ 24 Fault 24
0/ 7/ 2/ 25 Fault 25
0/ 7/ 2/ 26 Fault 26
0/ 7/ 2/ 27 Fault 27
0/ 7/ 2/ 28 Fault 28

0/ 7/ 2/ 29 Fault 29
0/ 7/ 2/ 30 Fault 30
0/ 7/ 2/ 31 Fault 31
----------------------------------------------
--------------------------------------------------------
Frame/Slot/Port PortType PortState ServiceType
--------------------------------------------------------
0 / 7 / 2 E1 Normal MGR2
---------------------------------------------------------
----End
Result
Any one phone among phones A, B, and C should be able to communicate with phone D.
15.3 Adding an R2 Profile

You can define an R2 signaling with certain characteristics as an R2 profile. The R2 profile
index can be referenced by the MG R2 subscribers. That is, the R2 profile is valid for the MG
R2 subscribers who reference this profile.
Context
You can add a maximum of 16 R2 profiles with the signaling type that ranges from 0 to 15. The
signaling types are defined as follows:
l 0: Standard_R2
l 1: Brazil_R2
l 2: Argentina_R2
l 3–15: Subscriber self-defined R2
NOTE
By default, in the case of the R2 profiles that range from 0 to 15, the values of the following four tables
are default values. The four tables are register signaling attribute table, line signaling attribute table, address
sending attribute table, and address receiving attribute table.
Procedure
Step 1 Run the r2 profile command to add an R2 profile.
Step 2 Run the display r2 profile command to query the attributes of the R2 profile.
----End
Example
To add an R2 profile with index 2, do as follows:
Are you sure to add r2 profile?(y/n)[n]: y
huawei(config-r2-2)#display r2 profile
---------------------------------------------------------
R2 signalling profile
---------------------------------------------------------
index: 2
name: standard r2

signalling-type: 0
---------------------------------------------------------
Related Operation
Table 15-3 lists the related operations for adding an R2 profile.
Table 15-3 Related operations for adding an R2 profile
To... Run the Command... In...
Delete an R2 profile undo r2 profile Global config mode
Modify the attributes of an profile attribute R2 mode

R2 profile
Query the basic information display r2 profile all Global config mode
about all R2 profiles that
have been configured
Query the general attributes display profile detail R2 mode

of an R2 profile
15.4 Configuring the Adaptation Data of the R2 Profile

Configure the R2 profile data, including the R2 address receiving attributes, R2 address sending
attributes, R2 profile attributes, R2 line signaling attributes, and register signaling attributes.
NOTE
When you configure the adaptation data of the R2 profile, if a parameter in the signaling standard of a
country is the same as the default parameter defined by the UA5000, the parameter need not be changed.
If a parameter in the signaling standard of a country is different from the default parameter defined by the
UA5000, the parameter need be changed accordingly.
15.4.1 Configuring the R2 Address Receiving Attributes

Configuring the R2 address receiving attributes means configuring the address receiving
attributes in the adaptation data of the specified R2 profile.
Context
The UA5000 provides default values for the R2 address receiving attributes. Perform the
following operation to configure the attributes if the default values do not meet the requirement.
Procedure
Step 1 In global config mode, run the r2 profile command to enter the R2 mode.
Step 2 Run the address-receive attribute command to configure the R2 address receiving attributes.
Step 3 Run the display address-receive command to query the R2 address receiving attributes.
----End

Example
To set ES to yes in the address receiving table of the R2 profile with index 2, do as follows:
huawei(config-r2-2)#address-receive attribute ES yes
huawei(config-r2-2)#display address-receive
---------------------------------------------------------------------------
R2 address-receive attribute
---------------------------------------------------------------------------
index: 2
DI: yes
SI: yes
SC: yes
ES: yes
CC: no
DISC: no
NAC: no
SP: no
RCPS: 1
RCCP: 1
---------------------------------------------------------
15.4.2 Configuring the R2 Address Sending Attributes

Configuring the R2 address sending attributes means configuring the address sending attributes
in the adaptation data of the specified R2 profile.
Context
The UA5000 provides default values for the attributes. Perform the following operation to
configure the attributes if the default values do not meet the requirement.
Procedure
Step 2 Run the address-send attribute command to configure the R2 address sending table.
Step 3 Run the display address-send command to query the R2 address sending attributes.
----End
Example
To set SI as no in the address sending table of the R2 profile with index 2, do as follows:
huawei(config-r2-2)#address-send attribute si no
huawei(config-r2-2)#display address-send
---------------------------------------------------------------------------
R2 address-send attribute
---------------------------------------------------------------------------
index: 2
DI: yes
SI: no
SC: yes
ES: no
CC: no
DISC: no
NAC: no
SP: no
---------------------------------------------------------------------------

15.4.3 Configuring the R2 Profile Attributes

Configure or modify the basic information about the R2 profile so that the parameters in the R2
profile meet the requirements of the subscribers.
Context
The UA5000 provides default values for the R2 profile attributes. Perform the following
operation to configure the attributes if the default values do not meet the requirement.
Procedure
Step 1 In the global config mode, run the r2 profile command to enter the R2 mode.
Step 2 Run the profile attribute command to configure the attributes of the R2 profile.
Step 3 Run the display r2 profile command to query the attributes of the R2 profile.
----End
Example
To modify the R2 profile with index 2 so that the name of the profile is Argentina and the
signaling type is 2, do as follows:
huawei(config-r2-2)#profile attribute name Argentina signalling-type 2
huawei(config-r2-2)#display r2 profile
---------------------------------------------------------------------------
R2 signaling profile
---------------------------------------------------------------------------
index: 2
name: Argentina
signalling-type: 2
---------------------------------------------------------------------------
15.4.4 Configuring the R2 Line Signaling Attributes

Configuring the R2 line signaling attributes means configuring the line signaling attributes in
the adaptation data of the specified R2 profile.
Context
The UA5000 provides default values for the R2 line signaling attributes. Perform the following
operation to configure the attributes if the default values do not meet your requirement.
Procedure
Step 2 In global config mode, run the line-signaling attribute command to configure the R2 line
signaling attributes.
Step 3 In the global config mode, run the display line-signaling attribute command to query the R2
line signaling attributes.
----End

Example
l type: L2B
l wait-seize-ack-time: 3500 ms
l wait-answer-time: 260s
l wait-clear-forward-time: 1000 ms
l wait-protect-time: 1000 ms
To modify the line signaling attributes of the R2 profile with index 2, do as follows:
huawei(config-r2-2)#line-signaling attribute type 1 wait-seize-ack-time 3500
wait-answer-time 260 wait-clear-forward-time 1000 wait-protect-time 1000
huawei(config-r2-2)#display line-signaling attribute
---------------------------------------------------------
R2 line-signaling attribute
---------------------------------------------------------
index: 2
type(0:L1B,1:L2B,2:L3B,3:PULSE): 1
wait-seize-ack-time(ms): 3500
wait-answer-time(s): 260
wait-clear-forward-time(ms): 1000
wait-protect-time(ms): 1000
---------------------------------------------------------
15.4.5 Configuring the R2 Register Signaling Attributes

Configuring the R2 register signaling attributes means configuring the register signaling
attributes in the adaptation data of the R2 profile.
Context
The UA5000 provides default values for the R2 register signaling attributes. Perform the
following operation to configure the attributes if the default values do not meet the requirement.
Procedure
Step 2 Run the register-signaling attribute command to configure the attributes of the R2 register
signaling.
Step 3 Run the display register-signaling attribute command to query the attributes of the R2 register
signaling.
----End
Example
l type: 0
l signal-send-voltage: 20 dBm
l back-pulse-time: 150 ms
To modify the line signaling attributes of the R2 profile with index 2, do as follows:
huawei(config-r2-2)#register-signaling attribute type 0 signal-send-voltage 20

back-pulse-time 150
huawei(config-r2-2)#display register-signaling attribute
---------------------------------------------------------
R2 register-signaling attribute
---------------------------------------------------------
index: 2
type(0:MFC,1:PULSE,2:DTMF,3:MFP,4:DPMFP):0
signal-send-voltage(dBm): 20
back-pulse-time(ms): 150
dtmf-send-time(ms): 68
dtmf-send-interval(ms): 68
no-cid-permit(yes/no): yes
number-max-interval(s): 50
signal-keep-max-time(s): 15
receive-number-max-interval(s): 50
signal-stop-permit-time(s): 15
wait-caller-category-time(s): 50
wait-Bsignal-time(s): 50
number-send-mode(0:immediate,1:delay): 1
calling-number-max-length: 12
compelling-sequence-keepalive-time(ms): 40000
send-pulse-signal(yes/no): no
---------------------------------------------------------
15.5 Loading an R2 Signaling Configuration File

You can integrate the R2 signaling conversion tables into a script file. Then, configure the R2
signaling conversion table of the UA5000 by loading the script file.
Context
To convert R2 signaling to adapt to the standards of different countries, you must configure the
mapping table between the physical signals and the logical signals. This mapping table is named
the R2 signaling conversion table, which consists of the following four subtables:
l Line signaling report conversion table
l Line signaling delivery conversion table
l Line signaling delivery conversion table
l Register signaling delivery conversion table
Huawei produces a script file by collecting all man machine language (MML) commands used
for configuring the R2 signaling conversion table according to the signaling standard of your
country. You can load the script file to complete the configuration of the R2 signaling conversion
table on site.
l You can select only one loading mode among Xmodem, TFTP, SFTP, and FTP.
l During the loading, running information and other prompts are displayed, indicating the
loading progress, loading result, and failure cause in the case of a failure.
Procedure
Step 1 Run the load r2-signaling-file command to load the R2 signaling configuration file.
----End
Example
To load an R2 signaling configuration file through TFTP, do as follows:

huawei#load r2-signaling-file tftp 10.11.117.170 r2signalingtype.efs

During the file load, the R2 signaling adaptation data will be modified and
all the being services will be interrupted
Please ensure the file is correct,and please save it after load complete
Are you sure to load this file? (y/n)[n]:y
Load(backup,duplicate,...) begins, please wait and notice the rate of progress
Any operation such as reboot or switchover will cause failure
and unpredictable result

Configuration Guide-PVM CLI 16 Configuring the V5 Voice Service
16 Configuring the V5 Voice Service
About This Chapter
Configuring the V5 voice service includes the application of the V5 technology and the process
for configuring the V5 voice service on the UA5000.
16.1 Introduction to the V5 Voice Service

The V5 interface is designed for the access network (AN) development and is located between
the local exchange (LE) and the AN. The interface changes the analog connection between the
exchange and the access device to a standard digital connection.
16.2 Configuration Example of the V5 Voice Service
This topic describes how to configure a V5 interface and the V5 voice subscriber data on the
UA5000. In this way, the voice service is transmitted upstream to the exchange for processing
so that the voice subscribers can call each other.
16.3 Configuring a PSTN Subscriber
After configuring the v5 interface, configure the public switched telephone network (PSTN)
subscriber data on the V5 interface so that the PSTN subscribers can call each other.
16.4 Configuring an ISDN Subscriber
After configuring the V5 interface, configure the ISDN subscriber data on the V5 interface so
that the UA5000 can support the ISDN BRA and ISDN PRA access services.
16.5 Blocking a V5 Service Port
You can block a V5 service port by blocking the shelf number/slot number/port number, V5
interface ID + L3 address, or V5 interface ID + EF address.
16.6 Configuring the Loopback for a V5 Service Port
You can configure the loopback for a V5 service port and locate the subscriber line faults or
network transmission faults based on the voice quality.

16.1 Introduction to the V5 Voice Service

The V5 interface is designed for the access network (AN) development and is located between
the local exchange (LE) and the AN. The interface changes the analog connection between the
exchange and the access device to a standard digital connection.
Service Description
When the PVMB or PVMD board functions as the narrowband control board, the UA5000
supports the V5 interface and is compatible with the optical line terminal (OLT). The OLT is a
narrowband access device. The UA5000 provides the V5 voice service by connecting to the
PSTN switch through the V5 interface.
The V5 interface is a standard interface between the access network (AN) and the local exchange
(LE). The V5 interface includes the V5.1 and V5.2 interfaces.
l A V5.1 interface manages only one 2048 kbit/s link, and it does not have the line
concentration capability.
l When the V5.1 protocol is used for configuring the narrowband subscriber, a maximum of
30 narrowband subscribers can be added. TS16 and the timeslots that are configured as C-
channels are skipped when the V5.1 timeslots increase. When you add the PSTN
subscribers in batches, the system automatically searches for the PSTN ports within a
specified range and adds the PSTN subscribers one by one. The layer 3 addresses and
telephone numbers of the added PSTN subscribers increase by the set step value. The
default step is 1.
l A V5.2 interface manages 1-16 2048 kbit/s links, and it has the line concentration capability.
l For configuring the narrowband subscribers, the link timeslot is allocated as follows:
– When the 5.1 protocol is used, one narrowband subscriber constantly occupies one
timeslot.
– When the 5.2 protocol is used, no link timeslot is occupied. The V5.2 timeslot is
allocated dynamically after the subscriber picks up the phone.
The ring modes of the PSTN subscriber are controlled by the LE, whereas the ring tones are
configured on the UA5000. Therefore, a ring mapping must be created between the ring modes
and the ring tones. One mapping is applied to one V5 interface. If you do not create a ring
mapping, the default ring tones are used.
If the C&C08 switch functions as the LE, you need not set the ring mapping, because the ring
modes set on the C&C08 switch are the same as the ring tones set on the UA5000.
Currently, the following three types of ring-stop modes are supported:
l a:b
– a: ring duration
– b: stop duration
l a:b:c:d

– c: ring duration
– d: stop duration
l a:b:c:d:e:f
– c: ring duration
– d: stop duration
– e: ring duration
– f: stop duration
16.2 Configuration Example of the V5 Voice Service

This topic describes how to configure a V5 interface and the V5 voice subscriber data on the
UA5000. In this way, the voice service is transmitted upstream to the exchange for processing
so that the voice subscribers can call each other.
Context
The V5 parameters must be the same on the AN and the LE.
NOTE
For the cascaded interfaces, the AN_V5 interface is the upper-level interface of the LE_V5. Therefore, the
parameter upperv5id of the LE_V5 must be configured. The AN_V5 interface does not have an upper-
level V5 interface, and it is not required to configure this parameter.
Networking
Figure 16-1 shows the example network of the V5 voice service.
NOTE

Figure 16-1 Example network of the V5 voice service
LE
V5 link1 V5 link2
0/13
P P
A
V V
UA5000 3
M M
2
B B
Phone A Phone B
Data Plan
Table 16-1 provides the data plan for configuring the V5 voice service.
Table 16-1 Data for configuring the V5 voice service
Data Type Item Data
V5 interface Interface ID 0
Protocol version V5.2
Interface type AN_V5
Interface variable 0
ID of the PSTN C channel 0
ID of the logical C channel 0/4/0: 0

0/5/0: It need not be
specified.
Number of the timeslot 0/4/0: 16

occupied by the physical C 0/5/0: 16
channel
Protection group type 0/4/0: protection group I

active
0/5/0: protection group I
standby
Narrowband service board Slot of A32 board 0/13
Subscriber PSTN subscribers L3 address: 8, 9

Data Type Item Data
Telephone numbers:
12340000-12340001
User-defined ring Ring duration: 0 ms
Ring Peer parameter 0
Cadence ring mode 0: normal ring
Figure 16-2 shows the flowchart for configuring the V5 voice service.
Figure 16-2 Flowchart for configuring the V5 voice service
Query the status of

Start
the V5 interface
(Optional) Set E1
Add a slave shelf
port CRC4
(Optional Set E1 Add an inter-shelf

port impedance link
Add a V5 interface Confirm the boards
Set the V5 interface Load softwares to

attributes the boards
Query the status of

Add 2M V5 links
the boards
Configure logic C Add narrowband

channels service boards
Reset the V5 Configure subscriber

interface data
End

NOTE
The steps in dashed line frames are for adding a slave shelf. If there is no slave shelf on the UA5000, skip the
steps.
Procedure
Step 1 (Optional) Configure CRC4 for the E1 port.
NOTE
The configuration must be same as the configuration on the LE side. Otherwise, the CRC4 may fail.
huawei(config)#interface pvm 0/4
huawei(config-if-pvm-0/4)#crc4 0
Step 2 (Optional) Configure the impedance attributes of the E1 port.

huawei(config-if-pvm-0/4)#quit
huawei(config-esl-user)#pstnport electric set 0/13/0 impedance 2 current 6
Step 3 Add a V5 interface.

huawei(config)#interface v5 0
Are you sure to add V5 interface? (y/n)[n]:y
huawei(config-if-v5-0)#
Step 4 Configure the V5 interface attributes.

huawei(config-if-v5-0)#if-v5 attribute an_v5 v52 0 0
--------------------------------------------------------------------------
IF ID IF type Superior IF ID IF Desc
0 AN_V5 -1 -
Protocol Version Variable Code PSTN C-channel ID
V5.2 0 0
Start link identification:

Timed starting In restarting In re-provisioning In link restoration
no no no no
--------------------------------------------------------------------------
Step 5 Add links.

huawei(config-if-v5-0)#link add 0/4/0 1
huawei(config-if-v5-0)#link add 0/5/0 2
Step 6 Configure physical C channels.

huawei(config-if-v5-0)#c-channel add 0/4/0 tsno 16 1:protc1_act 0
huawei(config-if-v5-0)#c-channel add 0/5/0 tsno 16 2:protc1_std
Step 7 Reset the V5 interface.

huawei(config-if-v5-0)#reset
Are you sure to reset V5 interface?(y/n)[n]:y
This operation will take some time,please wait ......
Step 8 Configure the ringing mode.

huawei(config-if-v5-0)#ringmode add 0 128
Step 9 Configure a user-defined ringing mode.

NOTE
You can change the 16 user-defined ringing modes to the required ringing modes, but you cannot add a
ringing mode.
In the global config mode, run the user defined-ring modify command to change a user-defined ringing
mode.
huawei(config-if-v5-0)#quit
huawei(config)#user defined-ring modify 0 para1 0
Step 10 Add a A32 board and confirm it.

Step 11 Configure the subscriber data.

huawei(config)#narrow user
huawei(config-narrow-user)#pstnuser add 0/13/0 0 8 telno 12340000

huawei(config-narrow-user)#quit
huawei(config)#save
----End
Result
1. Verify whether the V5 interface attributes are configured successfully.
huawei(config)#interface v5 0
huawei(config-if-v5-0)#display if-v5 state
--------------------------------------------------------------------------
V5 interface state: Interface
normal
V5 interface ID V5 interface type Current variable

value
0 AN_V5
0
Primary link ID Secondary link ID V5 Interface link
number
1 2
2
Starting link
identification:
Interface timed starting : no start in interface starting :
no
Start after re-provisioning: no Start after link restoration:
no
States of protocol data links under V5

protocol
PSTN protocol data link state : Data link
normal
Control protocol data link state : Data link
normal
BCC protocol data link state : Data link
normal
Link control protocol data link state : Data link
normal
Protection protocol data link 1 state : Data link
normal
Protection protocol data link 2 state : Data link
unusable
Logic C-

channel:
C-channel frame/slot/port/TS Protection group
type
0 0 /4 /0 /16 GROUP1-
ACT
Bearer
protocol:
C-channel PSTN CTRL BCC PROTECT LINKCTRL ISDN_Ds ISDN_P
ISDN_F
0 1 1 1 1 1 0 0
0
Standby physical C-
channel:
Serial No. frame/slot/port/TS Protection group
type
0 0 /5 /0 /16 GROUP1-
STD
--------------------------------------------------------------------------
2. Verify whether the E1 link is normal.

huawei(config-if-v5-0)#display link state
--------------------------------------------------------------------------
ID. CRC4 Link FSM Local LID state
--------------------------------------------------------------------------
1 yes Link fault Link ID not requested
2 no Link fault Link ID not requested
--------------------------------------------------------------------------
16.3 Configuring a PSTN Subscriber

After configuring the v5 interface, configure the public switched telephone network (PSTN)
subscriber data on the V5 interface so that the PSTN subscribers can call each other.
Prerequisite
The V5 interface must be configured properly. For details, see "16.2 Configuration Example
of the V5 Voice Service."
Procedure
Step 1 Run the narrow user command to enter the narrow user mode.
Step 2 Run the pstnuser add command to add a PSTN subscriber or run the pstnuser batadd command
to add the PSTN subscribers in batches.
Step 3 Run the display user data command to query the PSTN subscriber data.
Step 4 Run the pstnport attribute set command to set the PSTN port attributes.
Step 5 Run the display pstnport attribute command to query the PSTN port attributes.
----End
Example
The following example describes how to configure a PSTN subscriber. Table 16-2 provides the
data plan for configuring a PSTN subscriber.

Table 16-2 Data plan for configuring a PSTN subscriber
Data Type Item Data
A32 board Shelf ID/slot ID/port ID 0/13/0
V5 interface V5 interface ID 0
PSTN subscriber L3 address 8
Telephone number 12340000
PSTN port Supports polarity reversal Support
huawei(config-narrow-user)#display user data 0/13/0
------------------------------------------------------------------
Frame/Slot/Port V5ID L3_Addr V5.1 Ts Telephone Number
------------------------------------------------------------------
0 / 13 / 0 0 8 - 12340000
------------------------------------------------------------------
huawei(config-narrow-user)#pstnport attribute set 0/13/0 polarity-reverse support
huawei(config-narrow-user)#display pstnport attribute 0/13/0
-------------------------------------------------------------------------
Frame/Slot/Port Gain(db) Dial-Mode Polarity-Reverse User-Type
-------------------------------------------------------------------------
-------------------------------------------------------------------------
16.4 Configuring an ISDN Subscriber

After configuring the V5 interface, configure the ISDN subscriber data on the V5 interface so
that the UA5000 can support the ISDN BRA and ISDN PRA access services.
Prerequisite
l The V5 interface parameters must be configured properly. For details, see "16.2
Configuration Example of the V5 Voice Service."
l The ISDN port group number must be added. To add the ISDN port group number, run the
isdn-channel add command.
Procedure
l The procedure for configuring an ISDN BRA subscriber is as follows:
1. Run the narrow user command to enter the narrow user mode.
2. Run the brauser add command to add an ISDN BRA subscriber or run the brauser
batadd command to add the ISDN BRA subscribers in batches.
3. Run the display user data command to query the ISDN BRA subscriber data.
l The procedure for configuring an ISDN PRA subscriber is as follows:
1. Run the narrow user command to enter the narrow user mode.
2. Run the prauser add command to add an ISDN PRA subscriber.

3. Run the display user data command to query the ISDN PRA subscriber data.
----End
Example
The following example describes how to configure an ISDN BRA subscriber. Table 16-3
provides the data plan configuring an ISDN BRA subscriber.
Table 16-3 Data plan for configuring an ISDN BRA subscriber

Data Type Item Data
DSL board Shelf ID/slot ID 0/15
ISDN BRA subscriber EF address 0
ISDN port group number 0
Telephone number 12345678
huawei(config-narrow-user)#brauser add 0/15/0 0 0 0 telno 12345678
----------------------------------------------------------------------------
Frame/Slot/Port V5ID EF_Addr PortGrpNo R.Pwr V51Ts1/2 Telephone Number
----------------------------------------------------------------------------
0 / 15 / 0 0 0 0 No - 12345678
----------------------------------------------------------------------------
The following example describes how to configure an ISDN PRA subscriber. Table 16-4
provides the data plan for configuring an ISDN PRA subscriber.
Table 16-4 Data plan for configuring an ISDN PRA subscriber

Data Type Item Data
EDTB board Shelf ID/slot ID 0/5
ISDN PRA subscriber EF address 0
ISDN port group number 0
E1 port Shelf ID/slot ID/port ID 0/5/2
huawei(config-narrow-user)#prauser add 0/5/2 0 0 0
------------------------------------------------------------------
Frame/Slot/Port V5ID EFAddr PortGrpNo ServiceType
------------------------------------------------------------------
0 / 5 / 2 0 0 0 PRA
------------------------------------------------------------------

16.5 Blocking a V5 Service Port

You can block a V5 service port by blocking the shelf number/slot number/port number, V5
interface ID + L3 address, or V5 interface ID + EF address.
Precaution
If any subscriber is already added to a V5 service port, performing such an operation may
interrupt the ongoing call on that port.
Procedure
Step 1 Run the narrow user command to enter the Narrow user mode.
Step 2 Run the block command to block the V5 service port.
----End
Example
To block the V5 port with the v5id of 1 and the L3 address (namely, the available protocol
address on the V5 port) of 11234, do as follows:
huawei(config-narrow-user)#block delay 1 l3 1234
Related Operation
Unblock the V5 port undo block
Loop back the V5 port loop
16.6 Configuring the Loopback for a V5 Service Port

You can configure the loopback for a V5 service port and locate the subscriber line faults or
network transmission faults based on the voice quality.
Prerequisite
The parameters related to the V5 interface must be configured. For details, see "16.2
Configuration Example of the V5 Voice Service."
Context
l The local loopback can be performed on the V5 service port after the offhook. That is, the
subscribers of the port can hear only their own voice after they take the phone off the hook.
The subscribers can check the line status based on the voice quality.

l The remote loopback can be performed on the V5 service port after the conversation starts.
That is, the subscriber of the port cannot hear any voice, and the subscribers of the peer
end hear their own voice. The subscriber of the peer end can check the network transmission
status based on the voice quality.
l The loopback tag is removed when the V5 service port is faulty, recovered, and reset.
l During the loopback, the subscriber data cannot be changed or deleted.
l A conversation does not affect the loopback tag of the V5 service port.
Precaution
The loopback cannot be performed when the V5 service port is faulty or the timeslot is not
occupied.
Procedure
Step 1 Run the narrow user command to enter the narrow user mode.
Step 2 Run the loop command to perform the loopback on the V5 service port.
----End
Example
To perform the remote loopback on the V5 service port with the ID 1 and the 13 address (namely,
the available protocol address on the V5 port) 1234, do as follows:
huawei(config-narrow-user)#loop remote 1 l3 1234
Related Operation
Block the V5 port block

Configuration Guide-PVM CLI 17 Configuring the SPC
17 Configuring the SPC
About This Chapter
This topic describes the application of the SPC technology and provides examples for
configuring the common SPC service and U port transparent transmission service.
17.1 Introduction to the SPC

The semi-permanent connection (SPC) is used to connect, release, check, and protect one or
more 64 KB communication channels between the ports of different boards or between different
ports of a same board.
17.2 Configuration Example of the Common SPC
This topic describes how to set up a common SPC between port 0/13/0/0 and port 0/15/0/0 on
the UA5000 (in this example, the SPC type is private.) Thus, when outer-group subscriber A
calls intra-group subscriber B, subscriber A does not need the two-stage dialing or the assistance
of the operator.
17.3 Configuration Example of the U Interface Transparent Transmission
In this example, the UA5000 is configured with two DSL boards. One DSL board is connected
to the DDN node machine through the U interface. The services on the U interface are transmitted
transparently to the terminal that is connected to the other DSL board through the SPC. Thus,
the transmission distance of the DDN node machine can be extended.

17.1 Introduction to the SPC

The semi-permanent connection (SPC) is used to connect, release, check, and protect one or
more 64 KB communication channels between the ports of different boards or between different
ports of a same board.
Service Description
The SPC occupies dedicated voice channels to meet the requirements of special and important
access users and ensure the quality of the service.
The UA5000 supports a common SPC between the narrowband service ports. The common SPCs
include internal SPC (an-spc), private SPC (an-private), V5-SPC (v5-spc), and V5-pre SPC (v5-
pre). U interface transparent transmission is a type of internal SPC.
Table 17-1 lists the mapping between the SPC application type and the SPC type.
Table 17-1 Mapping between the SPC application type and the SPC type
Service Type SPC Application Type SPC Type
Hotline telephone hotline private
SPC for connecting the subscriber normal V5-spc or V5-pre

on the LE side
Narrowband data service, normal an-spc

including U interface transparent
transmission and V.35 connection
Voice frequency telephone service normal an-spc
Z interface extension Z-extension private
PBX bi-directional interconnection PBX-bothway private
Transparent transmission for E&M normal an-spc

trunk service
Hotline telephone for the E&M EM-signal private

trunk interface
Table 17-2 lists the mapping between the SPC type and the port type.
Table 17-2 Mapping between the SPC type and the port type
SPC Type Port Type
an-spc PSTN, 2B+D, E1, V5TK, G.SHDSL, VFB

SPC Type Port Type
private PSTN, E1, V5TK, CDI
V5-spc PSTN, 2B+D
V5-pre PSTN
A port can be configured with both common access service and SPC service; however, a port
can be configured with only one service at a time.
To set up an SPC, pay attention to the following restrictions on the channel ID.
l If the start or the end port of the SPC is a PSTN port, the channel ID at the PSTN port is
0.
l If the start or the end port of the SPC is a V5TK port, the channel ID at the V5TK port
cannot be 0 or the ID of channel C.
l If the start or the end port of the SPC is an E1 port, the channel ID at the E1 port cannot be
0.
17.2 Configuration Example of the Common SPC

This topic describes how to set up a common SPC between port 0/13/0/0 and port 0/15/0/0 on
the UA5000 (in this example, the SPC type is private.) Thus, when outer-group subscriber A
calls intra-group subscriber B, subscriber A does not need the two-stage dialing or the assistance
of the operator.
Context
Subscribers A and B must be configured on different ports of one board or on different ports of
different boards.
Networking
Figure 17-1 shows the example network of the common SPC.
Figure 17-1 Example network of the common SPC

0/13 0/15
P P
A A
UA5000 V V
3 3
M M
2 2
B B
Phone A Phone B

Data Plan
Table 17-3 provides the data plan for configuring an SPC between subscriber A and subscriber
B.
Table 17-3 Data Plan for configuring an SPC

Item Data
Application type normal
SPC type private
Start port of the SPC 0/13/0/0
End port of the SPC 0/15/0/0
Total number of channels for the SPC 1
Figure 17-2 shows the flowchart for configuring a common SPC.
Figure 17-2 Flowchart for configuring a common SPC
Start
Add boards
Confirm the boards
Configure an SPC
End
Procedure
Step 1 Add A32 boards.
Step 2 Confirm the A32 boards.


Step 3 Configure an SPC between subscriber A and subscriber B.

huawei(config)#spc add private start 0/13/0/0 end 0/15/0/0 1 normal

huawei(config)#save
----End
Result
After the SPC between subscriber A and subscriber B is set up, subscriber B should hear the
ring tone when subscriber A picks up the phone.
17.3 Configuration Example of the U Interface Transparent

Transmission
In this example, the UA5000 is configured with two DSL boards. One DSL board is connected
to the DDN node machine through the U interface. The services on the U interface are transmitted
transparently to the terminal that is connected to the other DSL board through the SPC. Thus,
the transmission distance of the DDN node machine can be extended.
Context
l Only the PVMD supports U interface transparent transmission, whereas the PVMB does
not support U interface transparent transmission.
l The port on the DSL board that is connected to the network must work in the MNT mode,
whereas the port on the DSL board that is connected to the subscriber must work in the
MLT mode.
Networking
Figure 17-3 shows the example network for configuring the U interface transparent
transmission.

Figure 17-3 Example network for configuring the U interface transparent transmission
DDN node
U interface
0/8 0/11
P P A D D A A
UA5000 V V S S S S S
M M
L L L L L
D D
U interface
Customer A
Data Plan
Table 17-4 provides the data plan for configuring the U interface transparent transmission.
Table 17-4 Data plan for configuring the U interface transparent transmission
Port or Device Item Data
DSL board connected to the Shelf ID/slot ID 0/8

network
DSL board connected to the Shelf ID/slot ID 0/11

subscriber
SPC Application type normal
SPC type an-spc
Start shelf ID/slot ID/port 0/8/0/0

ID/channel ID
End shelf ID/slot ID/port ID/ 0/11/0/0

channel ID
Total number of channels 2

Port or Device Item Data
Subtype of the start port MNT
Subtype of the end port MLT
Figure 17-4 shows the flowchart for configuring the U interface transparent transmission.
Figure 17-4 Flowchart for configuring the U interface transparent transmission
Start
Add boards
Confirm the boards
Configure an SPC
End
Procedure
Step 1 Add two DSL boards.
Step 2 Confirm the DSL boards.

Step 3 Configure an SPC.

huawei(config)#spc add an-spc start 0/8/0/0 end 0/11/0/0 2 normal startportsubtype
mnt endportsubtype mlt

huawei(config)#save
----End

Result
The DSL board helps to extend the transmission distance of the U interface of the DDN node
machine. This ensures that the coverage of the services is extended.

Configuration Guide-PVM CLI 18 Configuring the DDI Service
18 Configuring the DDI Service
About This Chapter
Configuring the direct dialing in (DDI) service includes the application of the DDI technology
and the process for configuring the DDI service on the UA5000.
18.1 Introduction to the DDI Service

In the DDI service, the call can be connected to the extension directly without the two-stage
dialing and the assistance of an operator.
18.2 Configuration Example of the DDI Service
This topic describes how to configure the DDI service by adding a CDI board to the UA5000
and then configuring the DDI subscribers on the MG interface. The DDI subscriber to which
each port corresponds is an intra-group subscriber. Thus, outer-group subscriber A can call intra-
group subscriber B without the two-stage dialing.

18.1 Introduction to the DDI Service

In the DDI service, the call can be connected to the extension directly without the two-stage
dialing and the assistance of an operator.
Service Description
You can connect the UA5000 to an enterprise PBX through an analog trunk interface provided
by a CDI board, as shown in Figure 18-1. In this way, the UA5000 realizes the DDI service.
An outer-group subscriber can dial the access code of the enterprise (PBX pilot number) + PBX
extension number to call an intra-group subscriber through DDI. Hence, no two-stage dialing
or operator assistance is involved in this process.
The UA5000 provides a channel for directly calling the PBX through the CDI board. The
UA5000 also provides an emergency channel. The UA5000 VoIP subscribers can call the PSTN
subscribers through the emergency channels provided by the CDI board in the case of network
failure (such as physical line failure or disconnection from the MGC), as shown in Figure
18-1.
Figure 18-1 DDI service application

MGC
Appserver
NMS
Enterprise 2
UA5000
UA5000 PBX
Enterprise 1
The UA5000 supports the DDI service only when it uses the H. 248 protocol.

18.2 Configuration Example of the DDI Service

This topic describes how to configure the DDI service by adding a CDI board to the UA5000
and then configuring the DDI subscribers on the MG interface. The DDI subscriber to which
each port corresponds is an intra-group subscriber. Thus, outer-group subscriber A can call intra-
group subscriber B without the two-stage dialing.
Prerequisite
The data on the MGC must be configured.
Precaution
You can set certain ports on the CDI board as DDI channels and other ports as emergency
channels. You cannot, however, set a port as a DDI channel and an emergency channel at the
same time.
Networking
The UA5000 provides voice services through the voice access ports on the ASL boards. The
voice signals are processed by the PVMB board, and then transmitted to the upper layer network.
Figure 18-2 shows the example network of the DDI service.
NOTE
Figure 18-2 Example network of the DDI service

MGC
P P A P P C A
UA5000 UA5000
V V V V
S D S
M M M M
L I L
B B B B
PBX
Phone A
Phone B

Data Plan
Table 18-1 provides the data plan for configuring the DDI service.
Table 18-1 Data plan for configuring the DDI service

Item Data Remarks
UA5000 10.10.10.2/24 Uplink FE port (fast Ethernet

port)
Gateway of the UA5000 10.10.10.1/24 The default gateway for

service upstream
MGC 10.10.20.1/24 -
MGC port: 2944 -
MG MG ID: 0 -
Domain name: UA5000.com -
Code: text -
Protocol: H.248 -
Transfer: udp -
MG port: 2944 -
NOTE
same as the H.248 version on the
MGC.
Context
l The terminal ID of the DDI user must be the same as the ID configured on the MGC.
l If the MG interface does not support the terminal layer configuration, the terminal IDs of
the DDI users must be numbered within the MG interface.
l If the MG interface supports the terminal layer configuration, you need not set a terminal
ID because the system generates a protocol address automatically.
Figure 18-3 shows the flowchart for configuring the DDI service.

Figure 18-3 Flowchart for configuring the DDI service
Start
Add a CDI board
Configure the attributes

of the CDI port
Configure the DDI

subscriber data
Save the data
End
Procedure
Step 1 Add a CDI board.
huawei(config)#board add 0/11 cdi
Step 2 Add and configure the MG interface data.

NOTE
For the procedure for configuring an MG interface, see "9 Configuring the MG Interface".
Are you sure to add MG interface?(y/n)[n]:y
huawei(config-if-h248-0)#if-h248 attribute mgip 10.10.10.2 mgport 2944 code
text transfer udp domainName UA5000.com mgcip_1 10.10.20.1 mgcport_1 2944
mg-media-ip 10.10.10.4 start-negotiate-version 2
Step 3 (Optional) Query the status of the MG interface.

---------------------------------------------------------------------
MGID 0
MG Description -
Protocol H248
Profile 1:Resv1("")
2833Encrypt -
Codetype Text
Transmode UDP


MIDType IP4_ADDR
DeviceName -

---------------------------------------------------------------------
Step 4 Quit the MG interface mode and enter the ESL user mode.
huawei(config-esl-user)#
Step 5 Add and configure the DDI subscriber data.

huawei(config-esl-user)#mgddiuser add 0/11/0 0 151
--------------------------------------------------------------------------
F / S/ P Type State SvcState SvcType UserType MgID ProtocolID
--------------------------------------------------------------------------
0/11/0 CDI Idle StartService InstSvc MG 0 151
--------------------------------------------------------------------------
Step 6 (Optional) Configure the attributes of the DDI port.

huawei(config)#cdi
huawei(config-cdi)#port attribute set 0/11/0 dialmode PULSE
huawei(config-cdi)#quit

huawei(config)#save
----End
Result
The DDI service configuration of subscriber A and subscriber B is complete. Subscriber A should
be able to call subscriber B by dialing the access code (PBX pilot number) of the company +
PBX extension number of subscriber B.

Configuration Guide-PVM CLI 19 Configuring the SDL Service
19 Configuring the SDL Service
About This Chapter
Configuring the SDL service includes the application of the SDL board and the process for
configuring the SDL service through the SDL board on the UA5000.
19.1 Introduction to the SDL Service

The UA5000 provides different SDL services, including the N x 64 k (N ranges from 1 to 32)
data service and E1 access service through the SDL/SDLE board.
19.2 Configuration Example of the Normal SDL Service
This topic describes how to configure the two routers connected to the two SDL boards through
the SHDSL terminals so that the routers can communicate with each other.

19.1 Introduction to the SDL Service

The UA5000 provides different SDL services, including the N x 64 k (N ranges from 1 to 32)
data service and E1 access service through the SDL/SDLE board.
Service Description
The UA5000 provides the N x 64 k (N ranges from 1 to 32) data services and E1 services through
the SDL/SDLE board. The service data is sent through SPCs, which are set up between G.SHDSL
ports on the SDL/SDLE board and other service ports.
The SDL/SDLE board supports two types of SPCs: intra-board SPCs and inter-board SPCs.
l An intra-board SPC is set up between G.SHDSL ports, E1 ports, or a G.SHDSL port and
an E1 port on one SDL/SDLE board.
l An inter-board SPC is set up between a port on one SDL/SDLE board and a G.SHDSL port
on the other SDL/SDLE board, or between a port on one SDL/SDLE board and an E1 port
on the PVMB or PVMD board.
The SDL/SDLE board can work in the normal mode or the transmission mode.
l The SDL board provides four G.SHDSL ports and four E1 ports.
l The SDLE board provides eight G.SHDSL ports and eight E1 ports.
The G.SHDSL ports provided by the SDL/SDLE board work in the FE1 or V.35 mode to extend
the transmission distance of the E1 or V.35 services.
19.2 Configuration Example of the Normal SDL Service

This topic describes how to configure the two routers connected to the two SDL boards through
the SHDSL terminals so that the routers can communicate with each other.
Networking
Figure 19-1 shows the example network of the SDL normal service.
NOTE

Figure 19-1 Example network of the SDL normal service
LE
DDN
E1/V5
0/8 0/9
PP SS
VV D D
MM
L L
BB
SHDSL terminal SHDSL terminal
V.35/E1
Router Router
Data Plan
Table 19-1 provides the data plan for configuring the SDL normal service.
Table 19-1 Data plan for configuring the SDL normal service
Interface or Item Data Remarks
Device
SDL board Shelf/Slot 0/8 and 0/9 -
Running mode normal Normal mode
Clock source system system clock
SHDSL port Clock mode E1 mode -
SPC Service type normal Normal application
Connection type an-spc Internal SPC
Start shelf number/ 0/8/4/1 -

slot number/port
number/channel
number
End shelf number/ 0/9/4/1 -

slot number/port
number/channel
number
Channel number 10 -

Context
When you configure the application of the SDL normal service, the running mode of the SDL
board must be normal.
The SPC on the SDL board has the following limitations based on the service mode.
l The intra-board SPC of the SDL board supports a maximum of 32 timeslots. The minimum
timeslot number is occupied first for both the start and the end timeslots of the SPC.
l The intra-board SPC from SDL to SDL supports a maximum of 30 timeslots. The minimum
timeslot number is occupied first for both the start and the end timeslots of the SPC.
l If the SDL board is configured with the inter-board SPC service, use the system clock.
l When the transport mode is configured for the SDL board, do not select the SHDSL port
as the clock source.
l When you create the inter-board SPC from PVM/EDTB to SDL, the following situations
occur:
– The SPC from E1 port to V.35 port supports a maximum of 30 timeslots. At the start
of the SPC, timeslot 3 of the port is occupied first. At the end, timeslot 0 is occupied
first.
– The SPC from E1 port to FE1 port supports a maximum of 30 timeslots. At the start of
the SPC, timeslot 1 of the port is occupied first. At the end, timeslot 1 is occupied first.
Figure 19-2 shows the flowchart for configuring the SDL service.
Figure 19-2 Flowchart for configuring the SDL service
Start
Add SDL boards
Confirm the SDL boards
Configure the running

mode of the boards
Configure the clock

source for the boards
Configure an SHDSL port
Set up an SPC
End

Precaution
When you are configuring the timeslot range for the SPC by running the spc addan-spc
command, note that the timeslot of the SPC must be within the range of the G.SHDSL port rate.
For example, if the port rate is 10, the timeslot range of the SPC must be 0–9.
Procedure
Step 1 Add SDL boards.
huawei(config)#board add 0/8 sdl
huawei(config)#board add 0/9 sdl
Step 2 Confirm the SDL boards.

Step 3 Configure the running mode of the boards.

huawei(config)#interface sdl 0/8
huawei(config-if-sdl-0/8)#runmode normal clock line 0
Step 4 Configure the clock source of the board.

huawei(config-if-sdl-0/8)#clock source line 0
huawei(config-if-sdl-0/8)#display clock config
------------------------------------------------
Board's clock source: FE1 line 0 clock
------------------------------------------------
Step 5 Configure an SHDSL port.

l Query the configuration of the SHDSL port. If the running mode is the E1 mode, you need
not change it.
huawei(config-if-sdl-0/8)#display port config
--------------------------
Port Frame Username
--------------------------
0 PCM31 -
1 PCM31 -
2 PCM31 -
3 PCM31 -
----------------------------------
Port Workmode Active Username
----------------------------------
4 E1 Allow -
5 E1 Allow -
6 E1 Allow -
7 E1 Allow -
----------------------------------
l Query the configuration of the SHDSL port. If the running mode is the V.35 mode, change
it to the E1 mode.
huawei(config-if-sdl-0/8)#display port config
--------------------------
Port Frame Username
--------------------------
0 PCM31 -
1 PCM31 -
2 PCM31 -
3 PCM31 -
----------------------------------
Port Workmode Active Username
----------------------------------
4 V35 Allow user1

5 E1 Allow -
6 E1 Allow -
7 E1 Allow -
----------------------------------
huawei(config-if-sdl-0/8)#shdslport modify 4 runmode fe1
Step 6 Query the timeslot occupancy of the port (before creating the SPC, the timeslot is not occupied).
huawei(config-if-sdl-0/8)#display timeslot
----------------------------------------------------------
| 0--7 | 8--15 | 16--23 | 24--31 |
----------------------------------------------------------
FE1 line 0 | 00000000 | 00000000 | 00000000 | 00000000 |
FE1 line 1 | 00000000 | 00000000 | 00000000 | 00000000 |
FE1 line 2 | 00000000 | 00000000 | 00000000 | 00000000 |
FE1 line 3 | 00000000 | 00000000 | 00000000 | 00000000 |
SHDSL line 0 | 00000000 | 00000000 | 00000000 | 00000000 |
SHDSL line 1 | 00000000 | 00000000 | 00000000 | 00000000 |
SHDSL line 2 | 00000000 | 00000000 | 00000000 | 00000000 |
SHDSL line 3 | 00000000 | 00000000 | 00000000 | 00000000 |
----------------------------------------------------------
'0'-Not used; '1'-Used
----------------------------------------------------------
Step 7 Repeat Steps 3–6 to configure the SDL board on shelf 0/slot 9.
Step 8 Set up an SPC.
huawei(config)#spc add an-spc start 0/8/4/1 end 0/9/4/1 10 normal
huawei(config-if-sdl-0/8)#display timeslot
----------------------------------------------------------
| 0--7 | 8--15 | 16--23 | 24--31 |
----------------------------------------------------------
FE1 line 0 | 00000000 | 00000000 | 00000000 | 00000000 |
FE1 line 1 | 00000000 | 00000000 | 00000000 | 00000000 |
FE1 line 2 | 00000000 | 00000000 | 00000000 | 00000000 |
FE1 line 3 | 00000000 | 00000000 | 00000000 | 00000000 |
SHDSL line 0 | 01111111 | 11100000 | 00000000 | 00000000 |
SHDSL line 1 | 00000000 | 00000000 | 00000000 | 00000000 |
SHDSL line 2 | 00000000 | 00000000 | 00000000 | 00000000 |
SHDSL line 3 | 00000000 | 00000000 | 00000000 | 00000000 |
----------------------------------------------------------
'0'-Not used; '1'-Used
----------------------------------------------------------
----End
Result
The routers connected to the two SDL boards should be able to communicate with each other.

Configuration Guide-PVM CLI 20 Configuring the MTA Service
20 Configuring the MTA Service
About This Chapter
Configuring the multifunctional terminal adapter (MTA) service includes the application of the
MTA technology and the process for configuring the MTA service on the UA5000.
20.1 Introduction to the MTA Service

The UA5000 supports accessing the subscriber data service through the multifunctional terminal
adapter (MTA).
20.2 Configuration Example of the MTA Service
This topic describes how to add the MTA on port 0/8/0 and port 0/11/0 on the UA5000 so that
subscribers connected to port 0/8/0 and port 0/11/0 can exchange data.

20.1 Introduction to the MTA Service

The UA5000 supports accessing the subscriber data service through the multifunctional terminal
adapter (MTA).
Service Description
The UA5000 provides the following ports through the MTA:
l 64 kbit/s and 128 kbit/s rate synchronous ports

l 2.4 kbit/s, 4.8 kbit/s, 9.6 kbit/s, and 19.2 kbit/s sub-rate synchronous or asynchronous ports
In this way, the UA5000 provides the data terminal subscribers with the physical communication
channels between the data terminal subscribers and the DDN network or other data terminal
subscribers.
The MTA is connected to the DSL board through the 2B1Q interface. On the subscriber side,
the MTA provides one V.35/V.24 compatible port and two V.24 ports. The three ports can work
only in the DCE mode.
l V.35/V.24 compatible port (port 0): It is a DB25 socket, which directly provides the V.24
port (or the DCE-DTE cross over cable can be used). The port supports the synchronous
rate of 64 kbit/s, and the synchronous/asynchronous rates of 19.2 kbit/s, 9.6 kbit/s, 4.8 kbit/
s, and 2.4 kbit/s. The port functions as a V.35 port through the V.35 transit cable, and
supports the rates of 128 kbit/s and 64 kbit/s.
l V.24 ports (ports 1 and 2) are RJ45 socket (8-pin RJ-45 socket). The ports function as the
V.24 ports through the RJ45-DB25 transit cable. The ports support the synchronous rate
of 64 kbit/s, and the synchronous/asynchronous rates of 19.2 kbit/s, 9.6 kbit/s, 4.8 kbit/s,
and 2.4 kbit/s. The rate of 19.2 kbit/s is not recommended for port 2 (refer to the X.50
protocol).
The data devices that are connected directly to the MTA must have the standard V.24/RS-232
serial ports, or the V.35 serial ports. The devices include the following:
l Router
l PC
l Front end processor
l Other data terminal equipment (DTE)
20.2 Configuration Example of the MTA Service

This topic describes how to add the MTA on port 0/8/0 and port 0/11/0 on the UA5000 so that
subscribers connected to port 0/8/0 and port 0/11/0 can exchange data.
Prerequisite
Bit 2 of the DIP switch on the MTA must be set to ON so that port 0 on the MTA works in the
V.24 mode.

Precaution
l Before connecting a DTE, make sure that the port type, the DIP switches, and the cable are
correct. Otherwise, the ports on the UA5000 and the DTE may be damaged.
l The power of the MTA must map the MTA.
Networking
Figure 20-1 shows the example network of the MTA service.
Figure 20-1 Example network of the MTA service
LE
E1/V5 0/8 0/11
P P D D A A
UA5000
V V S S S S
M M
L L L L
B B
MTA MTA
Computer A Computer B
Data Plan
Table 20-1 provides the data plan for configuring the MTA service.
Table 20-1 Data plan for configuring the MTA service
Data Type Item Data
DSL board Shelf ID/slot ID 0/8, 0/11
MTA port Shelf ID/slot ID/port ID 0/8/0, 0/11/0
DSL board Channel number 0
Rate of channel 0 19200 bit/s

Data Type Item Data
Asynchronous word length of 10

channel 0
Synchronous or asynchronous asyn

selection of the channel
SPC Application type Common application
SPC type Internal SPC
Start shelf ID/slot ID/port ID/ 0/8/0/0

channel ID
End shelf ID/slot ID/port ID/ 0/11/0/0

channel ID
Total number of channels 1
Figure 20-2 shows the flowchart for configuring the MTA service.
Figure 20-2 Flowchart for configuring the MTA service
Start
Add an MTA
Modify the attributes

of the MTA
Query the settings

of the MTA channels
Set up an SPC
End
Procedure
Step 1 Add an MTA.
huawei(config)#mta add 0/8/0
huawei(config)#display mta
---------------------------------------------------------------------------

Frame/Slot/Port status Channel 0 Channel 1 Channel 2

0 /8/0 Normal Syn 4.8K Unavail Unavail
-------------------------------------------------------------------------
Total: 1 MTA, 1 normal, 0 fault, 0 unknown
------------------------------------------------------------------
Step 2 Modify the attributes of the MTA.

huawei(config)#mta modify 0/8/0 channelNo 0 asyn_len 10 mode asyn rate 19200
Step 3 Query the settings of the MTA channels.

huawei(config)#display mta 0/8/0
------------------------------------------------------------------
Frame/Slot/Port mmunication status protocol
0 /8 /0 Normal X.50 S bit loop
Channel 0:
Mode:Asyn Rate:19.2K Port type:DCE Clock type:Internal mode
Signal phase: Data receive In-phase Data send In-phase Clock receive In-
phase Clock send In-phase
Data length:10 B channel: B1 Involve phase:Sequence phase
Channel 1: Unavailable
Channel 2: Unavailable
Step 4 Repeat steps 1 to 3 to configure the other MTA on port 0/11/0.

----End
Result
Connect the two MTAs to two computers, and set the baud rate of the HyperTerminal to 19200
bit/s and do not set any flow control. The computers can send data to the MTAs and receive data
from the MTAs through the serial ports.

Configuration Guide-PVM CLI 21 Configuring the VFB Service
21 Configuring the VFB Service
About This Chapter
Configuring the VFB service includes the application of the VFB technology and the process
for configuring the VFB service on the UA5000.
21.1 Introduction to the VFB Service

The UA5000 supports the audio telephone service through the VFB board.
21.2 Configuration Example of the VFB Service
This topic describes how to configure two VFB boards on the UA5000 to set up an SPC between
port 0/8/0 and port 0/12/0. Thus, subscribers connected to port 0/8/0 and port 0/12/0 are
connected through a private line.

21.1 Introduction to the VFB Service

The UA5000 supports the audio telephone service through the VFB board.
Service Description
The UA5000 transmits voice or data services over the voice frequency (VF) channel in a private
network.
The UA5000 provides point-to-point VF channels. You can connect a VF phone or modem to
each end of the channel to implement the private line interconnection of the voice or data
services.
21.2 Configuration Example of the VFB Service

This topic describes how to configure two VFB boards on the UA5000 to set up an SPC between
port 0/8/0 and port 0/12/0. Thus, subscribers connected to port 0/8/0 and port 0/12/0 are
connected through a private line.
Networking
Figure 21-1 shows the example network of the VFB service.
NOTE
Figure 21-1 Example network of the VFB service
0/8 0/12
UA5000 P P V V
V V F F
M M
B B
B B
VF VF
telephone telephone

Data Plan
Table 21-1 provides the data plan for configuring the VFB service.
Table 21-1 Data plan for configuring the VFB service

Data Type Item Data Remarks
VFB board Shelf ID/slot ID/port ID 0/8/0, 0/12/0 -
VFB port Working mode 2-wire 2-wire
Rx gain -6 dB -
Tx gain +5 dB -
SPC Application type normal Common

application
SPC type an-spc Internal SPC
Start shelf ID/slot ID/ 0/8/0/0 -

port ID/channel ID
End shelf ID/slot ID/ 0/12/0/0 -

port ID/channel ID
Total number of 1 -
channels
Context
l When modifying the working mode of the VFB port, you must delete the SPC that is set
up on the port.
l When modifying other attributes on the VFB port, you need not delete the SPC that is set
up on the port.
Figure 21-2 shows the flowchart for configuring the VFB service.

Figure 21-2 Flowchart for configuring the VFB service
Start
Add VFB boards
Confirm the VFB

boards
Configure the VFB

port attributes
Set up an SPC
No Modify the VFB

QoS qualified?
port attributes
Yes
End
Procedure
Step 1 Add two VFB boards.
huawei(config)#board add 0/8 VFB
huawei(config)#board add 0/12 VFB
Step 2 Confirm the two VFB boards.

Step 3 Configure the VFB port attributes.

huawei(config)#vfb
huawei(config-vfb)#port attribute set 0/8/0 mode 2line receivegain 5 transmitgain
9
huawei(config-vfb)#display port attribute 0/8/0
------------------------------------------
Port Mode Resistance Receive Transmit
------------------------------------------
0 Two line 600 -6dB +5dB
------------------------------------------
huawei(config-vfb)#port attribute set 0/12/0 mode 2line receivegain 5 transmitgain
9
------------------------------------------
Port Mode Resistance Receive Transmit

------------------------------------------
0 Two line 600 -6dB +5dB
------------------------------------------
huawei(config-vfb)#quit

Step 5 (Optional) Modify the VFB port attributes.

After the SPC is set up, the subscribers that are connected to the two ports can call each other.
1. If the voice of the peer end is very low, increase the Rx gain of the local end or the Tx gain
of the peer end.
huawei(config)#vfb
huawei(config-vfb)#port attribute set 0/8/0 receivegain 6
--------------------------------------------------------
Port Mode Resistance Receive Transmit Name
--------------------------------------------------------
0 Two line 600 -5dB +5dB -
--------------------------------------------------------
2. If the voice of the peer end is very high and is distorted, decrease the Rx gain of the local
end or the Tx gain of the peer end.
huawei(config-vfb)#port attribute set 0/8/0 receivegain 4
-------------------------------------------------------
Port Mode Resistance Receive Transmit Name
--------------------------------------------------------
0 Two line 600 -7dB +5dB -
--------------------------------------------------------
----End
Result
Subscribers connected to the two VFB boards should be able to call each other.

Configuration Guide-PVM CLI 22 Configuring the ATI Service
22 Configuring the ATI Service
About This Chapter
Configuring the ATI service includes the application of the ATI and the process for configuring
the ATI service on the UA5000.
22.1 Introduction to the ATI Service

The UA5000 supports the transparent transmission of the E&M signalings and the 2-wire/4-wire
VF signals through the ATI board.
22.2 Configuration Example of the 2-Wire/4-Wire VF and E&M Trunk Service Transparent
Transmission
This topic describes how to configure two ATI boards on the UA5000, configure the subscriber
line mode of ATI ports 0/7/0 and 0/13/0 to 2wire, and set up an SPC between the two ports. The
SPC type is normal. Thus, the private line service of subscribers connected to port 0/7/0 and port
0/13/0 is implemented.
22.3 Configuration Example of the Hotline Service on the E&M Trunk Interface
This topic describes how to configure two ATI boards on the UA5000, and set up an SPC between
port 0/7/0 and port 0/13/0. The SPC type is the private line. Thus, subscribers connected to port
0/7/0 and port 0/13/0 can communicate with each other after taking the phones off the hook.

22.1 Introduction to the ATI Service

The UA5000 supports the transparent transmission of the E&M signalings and the 2-wire/4-wire
VF signals through the ATI board.
Service Description
The signaling channel and voice channel of the E&M trunk interface are separate. Therefore,
when the E&M trunk interface is supported, a port includes the signaling line (E line and M line)
and the voice frequency (VF) line. Where,
l The signaling line can be configured to support the Bell IV-type or V-type interface through
DIP switch settings.
l The VF line can be configured to support the 4-wire or 2-wire interface through the DIP
switch settings.
The ATI board provides six 2-wire/4-wire E&M trunk interfaces. Each interface of an ATI board
provides the 2-wire/4-wire VF line or the 1E1M signaling line. When the E&M signaling line
is not used, the 2-wire/4-wire VF line can be used separately for transmitting VF signals.
22.2 Configuration Example of the 2-Wire/4-Wire VF and

E&M Trunk Service Transparent Transmission
This topic describes how to configure two ATI boards on the UA5000, configure the subscriber
line mode of ATI ports 0/7/0 and 0/13/0 to 2wire, and set up an SPC between the two ports. The
SPC type is normal. Thus, the private line service of subscribers connected to port 0/7/0 and port
0/13/0 is implemented.
Networking
Figure 22-1 shows the example network of the 2-wire/4-wire VF and E&M trunk service
transparent transmission.
Figure 22-1 Example network of the 2-wire/4-wire VF and E&M trunk service transparent
transmission
0/7 0/13
P P A A
UA5000 V V T T
M M
I I
B B
E&M interface E&M interface
Modem A Modem B

Data Plan
Table 22-1 provides the data plan for configuring the 2-wire/4-wire VF and E&M trunk service
transparent transmission.
Table 22-1 Data plan for configuring the 2-wire/4-wire VF and E&M trunk service transparent
transmission
ATI board Shelf ID/slot ID of the board to 0/7 -

which modem A is connected
Shelf ID/slot ID of the board to 0/13 -

which modem B is connected
E&M interface Subscriber line mode 2-wire 2-wire
EM working mode 1E1M -
Rx gain -6 dB -
Tx gain -2.5 dB -
SPC Application type normal Common

application
SPC type an-spc Internal SPC
Start shelf ID/slot ID/port ID/ 0/7/0/0 -

channel ID
End shelf ID/slot ID/port ID/ 0/13/0/0 -

channel ID
Total number of channels 1 -
Context
l Currently, the ATI board supports only the 1E1M mode.
l After modifying the EM mode and the subscriber line mode, adjust the DIP switches on
the board.
Figure 22-2 shows the flowchart for configuring the ATI service.

Figure 22-2 Flowchart for configuring the ATI service
Start
Add ATI boards
Confirm ATI boards
Configure the ATI port

attributes
Set up an SPC
No Modify the ATI port

QoS qualified?
attributes
Yes
End
Procedure
Step 1 Add ATI boards.
huawei(config)#board add 0/7 ati
Step 2 Confirm the ATI boards.

Step 3 Configure the attributes of the ATI port to which subscriber A is connected.
huawei(config)#ati
huawei(config-ati)#port attribute set 0/7/0 recvgain 28 transgain 9 workmode 1E1M
userline 2Wire
Step 4 Configure the attributes of the ATI port to which subscriber B is connected.
huawei(config-ati)#port attribute set 0/13/0 recvgain 28 transgain 9 workmode
1E1M userline 2Wire
Step 5 Set up an SPC

----End
Result
Subscribers of the two terminals that are connected to the two modems should be able to call
each other.

22.3 Configuration Example of the Hotline Service on the

E&M Trunk Interface
This topic describes how to configure two ATI boards on the UA5000, and set up an SPC between
port 0/7/0 and port 0/13/0. The SPC type is the private line. Thus, subscribers connected to port
0/7/0 and port 0/13/0 can communicate with each other after taking the phones off the hook.
Networking
Figure 22-3 shows the example network of the hotline service on the E&M trunk interface.
NOTE
Figure 22-3 Example network of the hotline service on the E&M trunk interface
0/7 0/13
P P A A
V V
UA5000 T T
M M
I I
B B
PCM-MUX/PBX
Telephone A Telephone B
Data Plan
Table 22-2 provides the data plan for configuring the hotline service on the E&M trunk service.
Table 22-2 Data plan for configuring the hotline service on the E&M trunk service
ATI board Shelf ID/slot ID/port ID 0/7, 0/13 -
E&M interface Subscriber line mode 4-wire 4-wire
Rx gain -10 dB -

Tx gain +5 dB -
E&M working mode 1E1M -
SPC Application type em-signal EM signalling

application
SPC type private Private line
Start shelf ID/slot ID/port ID 0/7/0 -
End shelf ID/slot ID/port ID 0/13/0 -
Total number of channels 1 -
Figure 22-4 shows the flowchart for configuring the ATI service.
Figure 22-4 Flowchart for configuring the ATI service
Start
Add ATI boards
Confirm ATI boards
Configure the ATI port

attributes
Set up an SPC
No Modify the ATI port

QoS qualified?
attributes
Yes
End
Procedure
Step 1 Add ATI boards.


Step 2 Confirm the ATI boards.

Step 3 Configure the attributes of the ATI port to which subscriber A is connected.
huawei(config)#ati
huawei(config-ati)#port attribute set 0/7/0 recvgain 20 transgain 24 userline
4Wire workmode 1E1M
Step 4 Configure the attributes of the ATI port to which subscriber B is connected.
huawei(config-ati)#port attribute set 0/13/0 recvgain 20 transgain 24 userline
4Wire workmode 1E1M

huawei(config)#spc add private start 0/7/0/0 end 0/13/0/0 1 em-signal
----End
Result
l After subscriber A takes the phone off the hook, subscriber B hears the ringing tone and
subscriber A hears the ring back tone.
l After subscriber B takes the phone off the hook, subscriber A and subscriber B can talk
with each other over the phone.
l After one subscriber disconnects the call, the other subscriber hears the busy tone.
l When the service bearer channel between the two subscribers becomes faulty, the
subscriber who takes the phone off the hook hears the busy tone.

Configuration Guide-PVM CLI 23 Configuring the CDI Service
23 Configuring the CDI Service
About This Chapter
Configuring the CDI service includes the function application of the CDI board and the process
for configuring the CDI service through the CDI board on the UA5000.
23.1 Introduction to the CDI Service

The UA5000 supports the transparent transmission between the analog subscriber ports through
the CDI board.
23.2 Configuration Example of the Z Interface Extension Service
This topic describes how to configure the CDI board and ASL board on the UA5000, and set up
an SPC between the CDI board and the ASL board. The SPC type is Z-extension. Thus, the
subscriber connected to the ASL board can be connected to a port on the CDI board through the
SPC.
23.3 Configuration Example of the PBX-Bothway Service
This topic describes how to configure the PBX-Bothway service to set up a private SPC between
the ports on two CDI boards. Thus, the bothway service of the PBX-1 and PBX-2 subscribers
is implemented.

23.1 Introduction to the CDI Service

The UA5000 supports the transparent transmission between the analog subscriber ports through
the CDI board.
Service Description
The CDI board implements the transparent extension of the POTS port (Z interface) of the
connected LE between the CDI port and the ASL port through the following ways:
l Digital/Analog conversion
l Transparent transmission
l Host signaling processing
Z interface is an analog phone interface. In the access network, Z interface extension service is
applicable to the following two scenarios:
l The V5 interface is not enabled for interconnection with the LE in the network. There is a
certain market demand for the analog phone service.
l The analog phone of one LE is connected to another LE through the Z interface extension
without changing the charging mode. This can save the toll charge.
l The CDI board is connected to the analog line. The CDI port functions as an analog phone.
l The CDI board supports the following services:
– Z interface extension
– PBX-bothway
– E1-direct dialing in (E1-DDI)
l The Rx gain of the CDI board ranges from -22.5 dB to -3 dB. The Tx gain ranges from -8.5
dB to +13 dB. The adjustment step is 0.5 dB.
23.2 Configuration Example of the Z Interface Extension

Service
This topic describes how to configure the CDI board and ASL board on the UA5000, and set up
an SPC between the CDI board and the ASL board. The SPC type is Z-extension. Thus, the
subscriber connected to the ASL board can be connected to a port on the CDI board through the
SPC.
Networking
The CDI board is connected to subscriber B of the PBX through the Z interface. Subscriber A
is connected to a port on the CDI board through a private SPC. In this way, the Z interface
extension function is realized. Figure 23-1 shows the example network of the Z interface
extension.

Figure 23-1 Example network of the Z interface extension
LE
0/8 0/11
P P C A A
UA5000 V V
D S S
M M
I L L
B B
Z interface
PBX
Phone B Phone A Phone C
Data Plan
Table 23-1 provides the data plan for configuring the Z interface extension.
Table 23-1 Data plan for configuring the Z interface extension
CDI board Shelf ID/slot ID 0/8 -
ASL board Shelf ID/slot ID 0/11 -
CDI port Shelf ID/slot ID/port 0/8/0 -

ID
Rx gain -7 dB -
Tx gain -5 dB -
Dial-up mode DTMF Dual tone
Supports delayed no Not supported

dialing
Working mode DDI -
Ringing Normal -
SPC Application type Z-extension Z interface extension
SPC type private Only private line can

be supported


port ID/channel ID
End shelf ID/slot ID/ 0/11/0/0 -

port ID/channel ID
Total number of 1 Only one B channel

channels can be occupied.
Context
The CDI port supports only the private SPC.
Figure 23-2 shows the flowchart for configuring the Z interface extension.
Figure 23-2 Flowchart for configuring the Z interface extension
Start
Add CDI boards
Confirm CDI boards

of the CDI port
Set up an SPC
No Modify the attributes

QoS qualified?
of the CDI port
Yes
End
Procedure
Step 1 Add a CDI board and an ASL board.


huawei(config)#board add 0/11 asl
Step 2 Confirm the CDI board and the ASL board.

Step 3 Modify the attributes of the CDI port.

huawei(config)#cdi
huawei(config-cdi)#port attribute set 0/8/0 recvgain 31 transgain 7 dialmode DTMF
delaydial no workmode DDI ringmode 4

huawei(config)#spc add private start 0/8/0/0 end 0/11/0/0 1 z-extension
----End
Result
When subscriber C dials the number of subscriber A, the phone of subscriber B should ring.
That is, the phone of subscriber B functions as the phone of subscriber A.
23.3 Configuration Example of the PBX-Bothway Service

This topic describes how to configure the PBX-Bothway service to set up a private SPC between
the ports on two CDI boards. Thus, the bothway service of the PBX-1 and PBX-2 subscribers
is implemented.
Networking
One CDI board (in slot 0/8) is connected to PBX-1 through a twisted pair (Z interface). The
other CDI board (in slot 0/11) is connected to PBX-2 through a twisted pair (Z interface). Figure
23-3 shows the example network for configuring the PBX-bothway service.
NOTE
Figure 23-3 Example network for configuring the PBX-bothway service
0/8 0/11
P P A C C A A
UA5000
V V S D D S S
M M
L I I L L
B B
Z interface Z interface
PBX-1 PBX-2

Data Plan
Table 23-2 provides the data plan for configuring the PBX-bothway service.
Table 23-2 Data plan for configuring the PBX-bothway service

CDI board Shelf ID/slot ID 0/8, 0/11 -
SPC Application type PBX-bothway PBX-bothway

connection
SPC type private Private line type

port ID/channel ID
End Shelf ID/slot ID/ 0/11/0/0 -

port ID/channel ID
Total number of 1 Only one B channel

channels is occupied.
Figure 23-4 shows the flowchart for configuring the CDI service.
Figure 23-4 Flowchart for configuring the CDI service
Start
Add CDI boards
Confirm CDI boards

of the CDI port
Set up an SPC
No Modify the attributes

QoS qualified?
of the CDI port
Yes
End

Procedure
Step 1 Add a CDI board.
Step 2 Confirm the CDI board.


huawei(config)#spc add private start 0/8/0/0 end 0/11/0/0 1 PBX-bothway
Step 4 If the service quality cannot meet the requirement, you need to change port attributes.
----End
Result
A private SPC is set up between the ports on the two CDI boards. PBXs should be able to initiate
calls between each other. In this way, the PBX-bothway service of the PBX-1 and PBX-2
subscribers is implemented. In addition, the service quality can meet the requirement.

Configuration Guide-PVM CLI 24 Configuring the EPON Upstream Transmission
24 Configuring the EPON Upstream

Transmission
About This Chapter
This topic describes the Ethernet passive optical network (EPON) technology and how to
configure the EPON upstream transmission on the UA5000 MiniMSAN.
24.1 Introduction to the EPON Upstream Transmission
EPON can transmit the converged data, video, and voice over the optical fiber.
24.2 Configuration Example of the EPON Upstream Transmission
This topic describes how to implement the EPON upstream transmission of the UA5000
MiniMSAN by configuring the EP1A board on the UA5000 MiniMSAN. Thus, the UA5000
MiniMSAN and OLT form an EPON.
24.3 Querying the Attributes of the Ports on the EP1A Board
The EP1A provides one EPON uplink port and one FE/GE adaptive electrical port. By querying
the attributes of the ports on the EP1A board, you can obtain the type, adaptive mode, rate,
working mode, activation status, and current status of each port on the EP1A board.
24.4 Querying the Statistics of the Ports on the EP1A Board
By querying the statistics of the ports on the EP1A board, you can obtain the transmitted frames,
received frames, and error frames. Thus, this helps you to detect and locate the faults of the ports
on the EP1A board in time.

24.1 Introduction to the EPON Upstream Transmission

EPON can transmit the converged data, video, and voice over the optical fiber.
Service Description
Passive optical network (PON) is a point-to-multipoint (P2MP) network, consisting of the optical
line terminal (OLT), optical network unit (ONU), and passive optical splitter (POS).
EPON, a type of the PON technology, has the common features, such as the high bandwidth,
wide coverage, flexible networking, and passive network nodes. EPON overcomes the
disadvantages of the Ethernet which lacks operations, administration, and maintenance (OAM)
measures. EPON can improve the network bandwidth and performance, and save the
maintenance cost.
The UA5000 MiniMSAN supports the EPON upstream transmission. The UA5000
MiniMSAN that works as an ONU can use the wide coverage, flexible networking, and low
maintenance cost provided by the EPON network. The UA5000 MiniMSAN works with the
OLT to provide high-bandwidth access for subscribers. At the same time, it helps increase the
density of subscribers at the OLT end.
The UA5000 MiniMSAN provides the EPON upstream transmission through the EP1A board.
The detailed specifications are as follows:
l Supports one EPON uplink port with the upstream and downstream rates 1.25 Gbit/s.
l Supports the transmission distance of a maximum of 20 km.
24.2 Configuration Example of the EPON Upstream

Transmission
This topic describes how to implement the EPON upstream transmission of the UA5000
MiniMSAN by configuring the EP1A board on the UA5000 MiniMSAN. Thus, the UA5000
MiniMSAN and OLT form an EPON.
Prerequisite
l The network devices and the lines must be in the normal state.
l When the PVM board adopts the independent upstream transmission mode, the ETH1 port
on the PVM board and the FE port on the EP1A board must be connected through a network
cable.
Networking
Figure 24-1 shows the example network of the EPON upstream transmission service.
Connect the EPON port on the EP1A board in slot 0/3 of the UA5000 MiniMSAN to the splitter
through an optical fiber. Thus, the connection between the UA5000 MiniMSAN and OLT is set
up.

Figure 24-1 Example network of the EPON upstream transmission service
Router
OLT
Optical
0/3 EPON 0/7
spllitter
I P E AA
P V P 3 3
Optical 1
EPON MMA 2 2
spllitter
HABM shelf
EPON
UA5000 MiniMSAN_B
UA5000 MiniMSAN_A
PBX NT1
ISDN BRA ISDN BRA

Phone Phone Phone Phone
Phone Phone
Data Plan
Table 24-1 provides the data plan for configuring the EPON upstream transmission service.
NOTE
The following table provides only the data plan of the VoIP service of the EP1A board. For the data plans
of services such as P2P ISDN BRA and P2MP ISDN BRA, see "12.2 Configuration Example of the P2P
ISDN BRA Service" and "12.3 Configuration Example of the P2MP ISDN BRA Service" respectively.
Table 24-1 Data plan for configuring the EPON upstream transmission service
Category Item Data
UA5000 The EP1A board: provides the EPON port to Shelf ID/Slot ID: 0/3
MiniMSAN_A interconnect to the upper-layer OLT
code text
protocol H.248

Category Item Data
tranfer UDP
port MG: 2944

MGC: 2944
NOTE
The parameter value
must be the same as the
H.248 version on the
MGC.
IP address The signaling IP address of MG 0 of the 10.10.10.2/24

UA5000
The media IP address of MG 0 of the UA5000 10.10.10.4/24
The default gateway of MG 0 of the UA5000 10.10.10.1/24
Telephone number Phone1–Phone32 Shelf ID/Slot ID: 0/7

configuration Telephone number:
12340001–12340032
terminal id 0–31. Terminals 0–31

correspond with
telephone numbers
12340001–12340032.
ToS strategy IP priority and ToS priority The default system

value
Voice enhancing The function of automatic gain adjustment of Supported

function the PSTN port
The parameter value of automatic gain 15 (-24 dbm0)

adjustment of the PSTN port
The function of the spectral noise suppression Supported

(SNS) of the PSTN port
The parameter value of the SNS of the PSTN 20 (20 dB)

port
Context
l You need to add the EP1A board if the UA5000 MiniMSAN needs the EPON upstream
transmission. After the EP1A board is added successfully, the UA5000 MiniMSAN can
implement the EPON upstream transmission through the EPON uplink port on the EP1A
board.

l When the UA5000 MiniMSAN implements the upstream transmission through the EP1A
board, the UA5000 MiniMSAN supports only the IP services, such as VoIP, FoIP, MoIP,
and ISDN.
l This document describes only the configuration on the UA5000 MiniMSAN. For the
configuration on the OLT, see the related guide. For example, if the OLT is the MA5680T
of Huawei, see the MA5680T Configuration Guide.
l The configurations on the UA5000 MiniMSAN_B and UA5000 MiniMSAN_A are the
same. This topic considers the configuration on the UA5000 MiniMSAN_A as an example.
Figure 24-2 shows the flowchart for configuring the EPON upstream transmission service.
Figure 24-2 Flowchart for configuring the EPON upstream transmission service
Start
Add an EP1A board
Confirm the EP1A

board
Configure the
service
Save the data
End
Procedure
Step 1 Add an EP1A board.
You can add the EP1A board offline on the CLI, and then insert the EP1A board. You can also
insert the EP1A board into the shelf, and then add the EP1A board on the CLI.
huawei(config)#board add 0/3 h601ep1a
Step 2 Confirm the EP1A board.

After the EP1A board is added successfully, the UA5000 MiniMSAN can implement the EPON
upstream transmission through the EPON uplink port on the EP1A board.
Step 3 Configure the service.

NOTE
l For the configuration of the ISDN service, see "12 Configuring the ISDN Service."
l For the configuration of the FoIP and MoIP services, see "13 Configuring the FoIP Service" and "14
Configuring the MoIP Service."
The slot positions for the PVM and service boards on the UA5000 MiniMSAN are different from the slot
positions described in the topics for reference. Configure the UA5000 MiniMSAN according to the
parameters that are actually used.
The following configuration procedure considers configuring the VoIP service as an example.
1. Set the IP address of the service network port.
10.10.10.1 submask 255.255.255.0
/When the device is configured with the IP address of the service network port,
whereas the IP address, subnet mask, and gateway of the current service network
port on
the device are inconsistent with the requirement of the actual data plan, run
this command to modify
the configuration./
/If no IP address is added to the current IP address pool of the device, run
the ip address command to add the media IP address and signaling IP address to
the IP address pool./
Eth:
IPAddress ..........: 10.10.10.2
SubMask.............: 255.255.255.0
GateWay.............: 10.10.10.1
MacIndex............: 0
MacAddress..........: 00-E0-FC-44-16-57
VlanID .............: --
IPAddress ..........: 10.10.10.4

SubMask.............: 255.255.255.0
GateWay.............: 10.10.10.1
MacIndex............: 0
MacAddress..........: 00-E0-FC-44-16-57
VlanID .............: --

3. Configure the working mode of the PVM board to the independent networking mode.
In the independent networking mode, the PVM control board provides services
independently.
4. Add an A32 service board and confirm the board.

-------------------------------------------------------------------------
-------------------------------------------------------------------------
0 PWX2 Normal
1
3 H601EP1A Normal
4
5
6
7 A32 Normal

8
-------------------------------------------------------------------------

---------------------------------------------------------------------
MGID 0
MG Description -
Protocol H248
2833Encrypt -
Codetype Text
Transmode UDP
MIDType IP4_ADDR
DeviceName -

---------------------------------------------------------------------
6. Set the H.248 protocol parameter. (Enable the three-way handshake signal switch of the H.
248 protocol stack.)
---------------------------------------------------------------------
maxretranstimes : 7
retransmode : auto
---------------------------------------------------------------------
7. Reset the MG interface.

8. Query whether the MG interface is normal.

-------------------------------------------------------------------------
-------------------------------------------------------------------------
0 UDP Normal 2944 10.10.10. 2 2944 10.10.20.1
-------------------------------------------------------------------------
9. Configure subscriber telephone numbers.

telno 12340001
--------------------------------------------------------
--------------------------------------------------------
0 / 7 / 0 0 12340001 Cat3 A0
0 / 7 / 1 0 12340002 Cat3 A1
0 / 7 / 2 0 12340003 Cat3 A2
0 / 7 / 3 0 12340004 Cat3 A3
0 / 7 / 4 0 12340005 Cat3 A4
0 / 7 / 5 0 12340006 Cat3 A5
0 / 7 / 6 0 12340007 Cat3 A6
0 / 7 / 7 0 12340008 Cat3 A7
0 / 7 / 8 0 12340009 Cat3 A8
0 / 7 / 9 0 12340010 Cat3 A9
0 / 7 / 10 0 12340011 Cat3 A10
0 / 7 / 11 0 12340012 Cat3 A11
0 / 7 / 12 0 12340013 Cat3 A12
0 / 7 / 13 0 12340014 Cat3 A13
0 / 7 / 14 0 12340015 Cat3 A14
0 / 7 / 15 0 12340016 Cat3 A15
0 / 7 / 16 0 12340017 Cat3 A16
0 / 7 / 17 0 12340018 Cat3 A17
0 / 7 / 18 0 12340019 Cat3 A18
0 / 7 / 19 0 12340020 Cat3 A19
0 / 7 / 20 0 12340021 Cat3 A20
0 / 7 / 21 0 12340022 Cat3 A21
0 / 7 / 22 0 12340023 Cat3 A22
0 / 7 / 23 0 12340024 Cat3 A23
0 / 7 / 24 0 12340025 Cat3 A24
0 / 7 / 25 0 12340026 Cat3 A25
0 / 7 / 26 0 12340027 Cat3 A26
0 / 7 / 27 0 12340028 Cat3 A27
0 / 7 / 28 0 12340029 Cat3 A28
0 / 7 / 29 0 12340030 Cat3 A29
0 / 7 / 30 0 12340031 Cat3 A30
0 / 7 / 31 0 12340032 Cat3 A31
--------------------------------------------------------

-------------------------------------------------------------------------
-------------------------------------------------------------------------
0 / 7 / 10 enable -24 enable 20
0 / 7 / 11 enable -24 enable 20
0 / 7 / 12 enable -24 enable 20
0 / 7 / 13 enable -24 enable 20
0 / 7 / 14 enable -24 enable 20
0 / 7 / 15 enable -24 enable 20
0 / 7 / 16 enable -24 enable 20
0 / 7 / 17 enable -24 enable 20
0 / 7 / 18 enable -24 enable 20
0 / 7 / 19 enable -24 enable 20



huawei(config)#save
----End
Result
After the configuration, the UA5000 MiniMSAN can implement the following functions:
l The UA5000 MiniMSAN and OLT can exchange data in the EPON mode.
l The subscribers configured on the UA5000 MiniMSAN service boards can call each other.
24.3 Querying the Attributes of the Ports on the EP1A Board

The EP1A provides one EPON uplink port and one FE/GE adaptive electrical port. By querying
the attributes of the ports on the EP1A board, you can obtain the type, adaptive mode, rate,
working mode, activation status, and current status of each port on the EP1A board.
Context
When you query the attributes of the ports on the EP1A board, the system displays "-" for the
status of the item that the port does not support.
l The PON port does not support the port impedance, MDI, port rate, and port mode. The
system displays "-" for the status of these items.
l The GE/FE adaptive electrical port does not support the port impedance. The system
displays "-" for the status of this item.
Precaution
The EP1A board supports two ports: the EPON uplink port and FE/GE adaptive electrical port.
The EPON uplink port corresponds to the logical number 0, and the FE/GE adaptive electrical
port corresponds to the logical number 1. When you query the attributes of the ports on the EP1A
board and enter a logical number that is greater than 1, the system prompts an error.
Procedure
Step 1 Run the interface epon command to enter the EPON mode.
Step 2 Run the display port state command to query the attributes of the ports on the EP1A board.
----End
Example
To query the attributes of the ports on the EP1A board of the UA5000 MiniMSAN, do as follows:
huawei(config)#interface epon 0/3
huawei(config-if-epon-0/3)#display port state all
-----------------------------------------------------------------------
Port PortType Impedance MDI Speed(Mbps) Duplex Active Link
-----------------------------------------------------------------------

0 EPON - - - - ACTIVE UP
1 GE ELC - AUTO 100 FULL ACTIVE UP
-----------------------------------------------------------------------
24.4 Querying the Statistics of the Ports on the EP1A Board

By querying the statistics of the ports on the EP1A board, you can obtain the transmitted frames,
received frames, and error frames. Thus, this helps you to detect and locate the faults of the ports
on the EP1A board in time.
Context
The EP1A board supports two ports: the EPON uplink port and FE/GE adaptive electrical port.
If the result of the queried statistical item is 0x00, it indicates that the port does not receive
frames of this type, or the port does not carry any traffic currently.
Procedure
Step 1 Run the interface epon command to enter the EPON mode.
Step 2 Run the display port statistic command to query the statistics of the EPON port.
----End
Example
To query the statistics of the port on the EP1A board of the UA5000 MiniMSAN, do as follows:
huawei(config)#interface epon 0/3
huawei(config-if-epon-0/3)#display port statistic all
Number of transmitted frames of PON port =0x0cef7d90
Number of received frames of PON port =0x0b913fed
Number of received FEC error frames of PON port =0x00
Number of received HEC error frames of PON port =0x00
Number of discard frames of PON port in send direction =0x00
Number of discard frames of UNI port in send direction =0x00
Number of transmitted frames of UNI port =0x039
Number of received frames of UNI port =0x01228f6d
Number of received error frames of UNI port =0x00
Related Operation
Table 24-2 lists the related operation for querying the statistics about the port on the EP1A
board.
Table 24-2 Related operation for querying the statistics about the port on the EP1A board
Clear the statistics of the ports on the EP1A reset port statistic
board

Configuration Guide-PVM CLI 25 Configuring the GPON Upstream Transmission
25 Configuring the GPON Upstream

Transmission
About This Chapter
This topic describes the gigabit-capable passive optical network (GPON) technology and
describes how to configure the GPON upstream transmission on the UA5000 MiniMSAN.
25.1 Introduction to the GPON Upstream Transmission
GPON is a point-to-multipoint (P2MP) broadband optical transmission system. It can transmit
data of any type.
25.2 Configuration Example of the GPON Upstream Transmission
This topic describes how to implement the GPON upstream transmission of the UA5000
MiniMSAN by configuring the GP1A board on the UA5000 MiniMSAN. Thus, the UA5000
MiniMSAN and OLT form a GPON.
25.3 Querying the Attributes of the Ports on the GP1A Board
The GP1A board provides one GPON uplink port, one FE/GE auto-sensing electrical port, one
100M electrical port, two 100M optical ports, and four E1 ports. By querying the attributes of
the port on the GP1A board, you can learn the type, impedance, auto-sensing mode, rate, working
mode, activation status, and current status of each port on the GP1A board.
25.4 Querying the Statistics of the Port on the GP1A Board
By querying the statistics of the port on the GP1A board, you can learn the information about
each port on the board. This helps you to detect and locate the faults of the port on the GP1A
board in time.

25.1 Introduction to the GPON Upstream Transmission

GPON is a point-to-multipoint (P2MP) broadband optical transmission system. It can transmit
data of any type.
Service Description
Passive optical network (PON) is a P2MP network, consisting of the optical line terminal (OLT),
optical network unit (ONU), and passive optical splitter (POS).
GPON is defined in the ITU-T Recommendations G.984.x. It supports downstream rates of 1.2
Gbit/s and 2.4 Gbit/s, and upstream rates of 155 Mbit/s, 622 Mbit/s, 1.2 Gbit/s, and 2.4 Gbit/s.
To meet the requirements of the users for the multiple networking modes, the UA5000
MiniMSAN provides the GPON uplink port to form a GPON network with the OLT. The
UA5000 MiniMSAN that works as an ONU can use the wide coverage, flexible networking,
and low maintenance cost provided by the GPON network. The UA5000 MiniMSAN works
with the OLT to provide high-bandwidth access for subscribers. At the same time, it helps
increase the density of subscribers at the OLT end.
For details about the GPON upstream transmission, see "GPON Upstream Transmission" in
"Feature Description".
The UA5000 MiniMSAN provides the GPON upstream transmission through the GP1A board.
The detailed specifications are as follows:
l The UA5000 MiniMSAN supports one GPON uplink port with a downstream rate of 2.488
Gbit/s and an upstream rate of 1.244 Gbit/s.
l The UA5000 MiniMSAN supports eight transmission containers (T-CONTs) with 32 GEM
ports.
l The OLT manages and configures the services on the PON board of the UA5000
MiniMSAN through the optical network termination management and control interface
(OMCI). That is, the OLT manages the UA5000 MiniMSAN as an ONT. The OLT does
not manage the existing services of the UA5000.
25.2 Configuration Example of the GPON Upstream

Transmission
This topic describes how to implement the GPON upstream transmission of the UA5000
MiniMSAN by configuring the GP1A board on the UA5000 MiniMSAN. Thus, the UA5000
MiniMSAN and OLT form a GPON.
Prerequisite
l The network devices and the lines must be in the normal state.
l When the PVM board adopts the independent upstream transmission mode, the ETH1 port
on the PVM board and the FE port on the GP1A board must be connected through a network
cable.

Networking
Figure 25-1 shows the example network of the GPON upstream transmission service.
Use the optical fiber to connect the GPON port on the GP1A board in slot 0/3 of the UA5000
MiniMSAN to the optical splitter to set up the connection with the OLT.
Figure 25-1 Example network of the GPON upstream transmission service
DDN
MGC
OLT
Optical
0/3 GPON 0/7
Splitter
I P G AA
P V P 3 3
1
GPON Optical MMA 2 2
Splitter
HABM Shelf
UA5000 GPON
MiniMSAN_B
UA5000
MiniMSAN_A
PBX NT1
Phone Phone ISDN BRA ISDN BRA Phone Phone

Phone Phone
Data Plan
Table 25-1 provides the data plan for configuring the GPON upstream transmission service.
NOTE
The following table provides only the data plan of the VoIP service. For the data plans of other services
such as the P2P ISDN BRA and P2MP ISDN BRA, see "12.2 Configuration Example of the P2P ISDN
BRA Service" and "12.3 Configuration Example of the P2MP ISDN BRA Service" respectively.
In the case of the HABM shelf, the GP1A board can be inserted in slot 3. In the case of other high-density
shelves, the GP1A board can be inserted in slot 6.

Table 25-1 Data plan for configuring the GPON upstream transmission service
Category Item Data
UA5000 The GP1A board: provides the GPON port to Shelf ID/Slot ID: 0/3
MiniMSAN_A interconnect with the upper-layer OLT
code text
protocol H.248
tranfer UDP
port MG: 2944

MGC: 2944
NOTE
The parameter value
must be the same as the
H.248 version on the
MGC.
IP Address The signaling IP address of MG 0 of the 10.10.10.2/24

UA5000
The media IP address of MG 0 of the UA5000 10.10.10.4/24
The default gateway of MG 0 of the UA5000 10.10.10.1/24
Telephone number Phone1-Phone32 Shelf ID/Slot ID: 0/7

configuration Telephone number:
12340001-12340032
terminal id 0-31. Terminals 0-31

correspond with
telephone numbers
12340001-12340032
ToS strategy IP priority and ToS priority The default system

value
Voice enhancing The function of automatic gain adjustment of Supported

function the PSTN port
The value of automatic gain adjustment of the 15 (-24 dbm0)

PSTN port
The SNS function of the PSTN port Supported
The SNS value of the PSTN port 20 (20 db)

Context
l You need to add the GP1A board if the UA5000 MiniMSAN needs the GPON upstream
transmission. After the GP1A board is added successfully, the UA5000 MiniMSAN can
implement the GPON upstream transmission through the GPON uplink port on the GP1A
board.
l When the UA5000 MiniMSAN implements the upstream transmission through the GP1A
board, it supports not only the IP services, such as VoIP, FoIP, MoIP, and ISDN, but also
the POTS such as V5.
l This document describes only the configuration on the UA5000 MiniMSAN. For the
configuration on the OLT, see the related guide. For example, if the OLT is the MA5680T
of Huawei, see the MA5680T Configuration Guide.
l The configurations on the UA5000 MiniMSAN_B and UA5000 MiniMSAN_A are the
same. This topic considers the configuration on the UA5000 MiniMSAN_A as an example.
l The ONT (that is, the UA5000 MiniMSAN) must register on the OLT before the
configuration.
Figure 25-2 shows the flowchart for configuring the GPON upstream transmission service.
Figure 25-2 Flowchart for configuring the GPON upstream transmission service
Procedure
Step 1 Add a GP1A board.
You can add the GP1A board offline on the CLI, and then insert the GP1A board. You can also
insert the GP1A board into the shelf, and then add the GP1A board on the CLI.

huawei(config)#board add 0/3 h601gp1a
Step 2 Confirm the GP1A board.

After the GP1A board is added successfully, the UA5000 MiniMSAN can implement the GPON
upstream transmission through the GPON uplink port on the GP1A board.
Step 3 Configure the service.
NOTE
l For the configuration of the ISDN service, see "12 Configuring the ISDN Service."
l For the configurations of the FoIP and MoIP services, see "13 Configuring the FoIP Service" and
"14 Configuring the MoIP Service."
The slot positions for the PVM and service boards on the UA5000 MiniMSAN are different from the slot
positions described in the topics for reference. Configure the UA5000 MiniMSAN according to the
parameters that are actually used.
The following configuration procedure considers configuring the VoIP service as an example.
1. Set the IP address of service network port.
10.10.10.1 submask 255.255.255.0
/When the device is configured with the IP address of the service network port,
whereas the IP address, subnet mask, and gateway are inconsistent with the
requirement of the actual data plan, run this command to modify the
configuration./
/If no IP address is added to the current IP address pool of the device, run
the ip address command to add the media IP address and signaling IP address to
the IP address pool./
Eth:
IPAddress ..........: 10.10.10.2
SubMask.............: 255.255.255.0
GateWay.............: 10.10.10.1
MacIndex............: 0
MacAddress..........: 00-E0-FC-44-16-57
VlanID .............: --
IPAddress ..........: 10.10.10.4

SubMask.............: 255.255.255.0
GateWay.............: 10.10.10.1
MacIndex............: 0
MacAddress..........: 00-E0-FC-44-16-57
VlanID .............: --

3. Configure the working mode of the PVM board as alone.

In this independent networking mode, the PVM control board provides services
independently.
4. Add an A32 service board, and confirm the board.

-------------------------------------------------------------------------

-------------------------------------------------------------------------
0 PWX2 Normal
1
3 H601GP1A Normal
4
5
6
7 A32 Normal
8
-------------------------------------------------------------------------

---------------------------------------------------------------------
MGID 0
MG Description -
Protocol H248
2833Encrypt -
Codetype Text
Transmode UDP
MIDType IP4_ADDR
DeviceName -

---------------------------------------------------------------------
6. Set the H.248 protocol parameter. (Enable the three-way handshake signal switch of the H.
248 protocol stack.)
---------------------------------------------------------------------
maxretranstimes : 7
retransmode : auto
---------------------------------------------------------------------
7. Reset the MG interface.

8. Query whether the MG interface is normal.

-------------------------------------------------------------------------
-------------------------------------------------------------------------
0 UDP Normal 2944 10.10.10. 2 2944 10.10.20.1
-------------------------------------------------------------------------
9. Configure the subscriber telephone numbers.

telno 12340001
--------------------------------------------------------
--------------------------------------------------------
0 / 7 / 0 0 12340001 Cat3 A0
0 / 7 / 1 0 12340002 Cat3 A1
0 / 7 / 2 0 12340003 Cat3 A2
0 / 7 / 3 0 12340004 Cat3 A3
0 / 7 / 4 0 12340005 Cat3 A4
0 / 7 / 5 0 12340006 Cat3 A5
0 / 7 / 6 0 12340007 Cat3 A6
0 / 7 / 7 0 12340008 Cat3 A7
0 / 7 / 8 0 12340009 Cat3 A8
0 / 7 / 9 0 12340010 Cat3 A9
0 / 7 / 10 0 12340011 Cat3 A10
0 / 7 / 11 0 12340012 Cat3 A11
0 / 7 / 12 0 12340013 Cat3 A12
0 / 7 / 13 0 12340014 Cat3 A13
0 / 7 / 14 0 12340015 Cat3 A14
0 / 7 / 15 0 12340016 Cat3 A15
0 / 7 / 16 0 12340017 Cat3 A16
0 / 7 / 17 0 12340018 Cat3 A17
0 / 7 / 18 0 12340019 Cat3 A18
0 / 7 / 19 0 12340020 Cat3 A19
0 / 7 / 20 0 12340021 Cat3 A20
0 / 7 / 21 0 12340022 Cat3 A21
0 / 7 / 22 0 12340023 Cat3 A22
0 / 7 / 23 0 12340024 Cat3 A23
0 / 7 / 24 0 12340025 Cat3 A24
0 / 7 / 25 0 12340026 Cat3 A25
0 / 7 / 26 0 12340027 Cat3 A26
0 / 7 / 27 0 12340028 Cat3 A27
0 / 7 / 28 0 12340029 Cat3 A28
0 / 7 / 29 0 12340030 Cat3 A29
0 / 7 / 30 0 12340031 Cat3 A30
0 / 7 / 31 0 12340032 Cat3 A31
--------------------------------------------------------

-------------------------------------------------------------------------
-------------------------------------------------------------------------
0 / 7 / 10 enable -24 enable 20

0 / 7 / 11 enable -24 enable 20

0 / 7 / 12 enable -24 enable 20
0 / 7 / 13 enable -24 enable 20
0 / 7 / 14 enable -24 enable 20
0 / 7 / 15 enable -24 enable 20
0 / 7 / 16 enable -24 enable 20
0 / 7 / 17 enable -24 enable 20
0 / 7 / 18 enable -24 enable 20
0 / 7 / 19 enable -24 enable 20

huawei(config)#save
----End
Result
After the configuration, the UA5000 MiniMSAN can perform the following functions:
l The UA5000 MiniMSAN and OLT can transmit data in the GPON mode.
l The subscribers configured on the service boards of the UA5000 MiniMSAN can call each
other.
25.3 Querying the Attributes of the Ports on the GP1A Board

The GP1A board provides one GPON uplink port, one FE/GE auto-sensing electrical port, one
100M electrical port, two 100M optical ports, and four E1 ports. By querying the attributes of
the port on the GP1A board, you can learn the type, impedance, auto-sensing mode, rate, working
mode, activation status, and current status of each port on the GP1A board.
Context
When you query the attributes of the port on the GP1A board, the system displays "-" for the
item that the port does not support.
l The PON port does not support the port impedance, MDI, port rate, and port mode. The
system displays "-" for these items.
l The 100M electrical port does not support the port impedance. The system displays "-"for
this item.
l The GE/FE auto-sensing electrical port and 100M optical port does not support the port
impedance and MDI. The system displays "-" for the two items.
l The E1 port does not support the MDI, port rate, and port mode. The system displays "-"
for these items.
Table 25-2 lists the port types corresponding to the IDs of the ports on the GP1A board.
Table 25-2 Port types corresponding to IDs of the ports on the GP1A board
Port Description Port ID
PON port 0
GE/FE auto-sensing electrical port 1

Port Description Port ID
100M electrical port 2
100M optical port 3-4
E1 port 5-8
Precaution
The GP1A board supports nine ports. When you query the attributes of the port on the GP1A
board, the system displays an error, if you enter a logical number greater than 8.
Procedure
Step 1 Run the interface gpon command to enter the GPON mode.
Step 2 Run the display port state command to query the attributes of the port on the GP1A board.
----End
Example
To query the port attributes of the GP1A board on the UA5000 MiniMSAN, do as follows:
huawei(config)#interface gpon 0/3
huawei(config-if-gpon-0/3)#display port state all
-----------------------------------------------------------------------
Port PortType Impedance MDI Speed(Mbps) Duplex Active Link
-----------------------------------------------------------------------
0 GPON - - - - ACTIVE UP
1 GE - - AUTO HALF ACTIVE UP
2 FE ELC - AUTO AUTO HALF ACTIVE UP
3 FE OPT - - 100 FULL ACTIVE UP
4 FE OPT - - 100 FULL ACTIVE UP
5 E1 75 - - - ACTIVE UP
6 E1 75 - - - ACTIVE UP
7 E1 75 - - - ACTIVE UP
8 E1 75 - - - ACTIVE UP
-----------------------------------------------------------------------
25.4 Querying the Statistics of the Port on the GP1A Board

By querying the statistics of the port on the GP1A board, you can learn the information about
each port on the board. This helps you to detect and locate the faults of the port on the GP1A
board in time.
Context
The GP1A board supports nine ports. They are one GPON uplink port, one FE/GE auto-sensing
electrical port, one 100M electrical port, two 100M optical ports, and four E1 ports.
If the result of the queried statistical item is 0x0, it indicates that the port does not receive frames
of this type, or the port does not carry any traffic currently.

Procedure
Step 1 Run the interface gpon command to enter the GPON mode.
Step 2 Run the display port statistic command to query the statistics of the GPON port.
----End
Example
To query the statistics of the E1 port group on the GP1A board of the UA5000 MiniMSAN, do
as follows:
huawei(config-if-gpon-0/3)#display port statistic e1port-group
port5:
Number of GEM frames of E1 port =0x0
Number of E1 channels from TGMAC =0x0
Number of E1 channels to TGMAC =0xb278
port6:
Number of E1 channels to TGMAC =0xdf7a
port7:
Number of E1 channels to TGMAC =0x117d
port8:
Number of E1 channels to TGMAC =0xab7f
To query the statistics of the Ethernet port group on the GP1A board of the UA5000
MiniMSAN, do as follows:
huawei(config-if-gpon-0/3)#display port statistic ethport-group
port0:
Number of transmitted frames of PON port =0x0
Number of received frames of PON port =0x0
Number of discard frames of PON port in send direction =0x0
port1:
Number of transmitted frames of UNI port =0x0
Number of received frames of UNI port =0x0
Number of discard frames of UNI port in send direction =0x0
port2:
Number of transmitted frames of FE port =0x0
Number of received frames of FE port =0x0
Number of discard frames of FE port in send direction =0x0
port3:
Number of transmitted frames of FE optics port =0x0
Number of received frames of FE optics port =0x0
Number of discard frames of FE optics port in send direction =0x0
port4:
Number of transmitted frames of FE optics port =0x0
Number of received frames of FE optics port =0x0
Number of discard frames of FE optics port in send direction =0x0
Related Operation
Table 25-3 lists the related operation for querying the statistics of the port on the GP1A board.

Table 25-3 Related operation for querying the statistics of the port on the GP1A board
Clear the statistics of the port on the GP1A reset port statistic
board

Configuration Guide-PVM CLI 26 Configuring the Remote Subtending
26 Configuring the Remote Subtending
About This Chapter
Configuring the remote subtending includes the description of the remote subtending networking
and the process for configuring the remote subtending through different boards on the
UA5000.
26.1 Introduction to the Remote Subtending

The remote subtending facilitates the flexible networking of the UA5000, and the expansion of
capacity of the UA5000.
26.2 Configuration Example of the E1 Subtending
This topic describes how to subtend a remote RSU to the UA5000 through the EDTB board.
Thus, the two subtended devices are connected through an E1 cable to extend the service
transmission distance and to expand the access capacity of the UA5000.

26.1 Introduction to the Remote Subtending

The remote subtending facilitates the flexible networking of the UA5000, and the expansion of
capacity of the UA5000.
Service Description
The UA5000 enables you to subtend the remote service shelves to the master shelf through the
E1 ports on the PVMB or PVMD board, or through the E1 ports on the EDTB board, thus to
expand the capacity of the UA5000. The remote service shelf uses the RSU4 or RSU8 board as
the control board. The local office and the remote office are connected by the E1 cables over
the multi-service transport platform (MSTP) or the synchronous digital hierarchy (SDH).
The remote service shelves access the modem services and the voice services through the ports
of the voice service boards. Table 26-1 shows the number of ports provided by the service boards
in the remote service shelves.
Table 26-1 Specification of the remote service shelf
Shelf Type Service Board Maximum Number of

Ports
RSU_HAFS_30(HABD) A32 1920
RSU_HABS_30(HABA) A32 1920
26.2 Configuration Example of the E1 Subtending

This topic describes how to subtend a remote RSU to the UA5000 through the EDTB board.
Thus, the two subtended devices are connected through an E1 cable to extend the service
transmission distance and to expand the access capacity of the UA5000.
Prerequisite
l The E1 cable must be connected correctly.
l The MG interface must be configured properly. (For details about the procedure, see "9
Configuring the MG Interface.")
l The RSU boards and the A32 boards must be added to the remote service shelf.
Context
The EDTB board can be installed in slots 6-17 of the HABA or HABD shelf, slots 12-17 of the
HABC shelf, or slots 6-11 of the HABL shelf. A maximum of six EDTB boards can be installed
in the adjacent slots of a shelf.

Networking
Figure 26-1 shows the example network of the E1 subtending.
Figure 26-1 Example network of the E1 subtending
MGC
H.248
E1
LAN Switch SDH
FE/GE
E1
P P E E
UA5000 A A
V V D D
3 3
M MT T
2 2
B B B B
E1
MSTP
E1 E1
R R
A A A A
S S
3 3 3 3
U U
2 2 2 2
8 8
Phone 1 Phone 128
Data Plan
Table 26-2 provides the data plan for configuring the E1 subtending.

Table 26-2 Data plan for configuring the E1 subtending

Data Type Item Data
IP address IP address/subnet mask of UA5000 10.10.10.2/255.255.255.0

MG 0
Default IP address/subnet mask of 10.10.10.1/255.255.255.0

UA5000 MG 0
IP address/subnet mask of the MGC 10.10.20.1/255.255.255.0
Parameters of the MG ID 0
MG interface
Code text
Protocol UDP
MG Port 2944
MGC Port 2944
Terminal layer configuration No, terminalid: 0-127
Telephone numbers Phone 1-phone 128 Shelf ID/slot ID/port ID:

1/9/0-1/12/31
Telephone number:
12340001-12340128
EDTB boards Shelf ID/slot ID 0/6 and 0/7
Remote service Shelf ID 1

shelf
Shelf type RSU_HAFS_30(HABD)
RSU board Shelf ID/slot ID 1/4 and 1/5
Context
l The MG interface parameters must be the same as the MG interface parameters configured
on the MGC.
l The EDTB board must work in the independent mode and the default value is independent.
Figure 26-2 shows the flowchart for configuring the E1 subtending.

Figure 26-2 Flowchart for configuring the E1 subtending
Start
Add EDTB boards
Confirm the EDTB boards
Add remote service shelf
Add inter-shelf links
Add subscribers to
slave service shelf
End
Procedure
Step 1 Add EDTB boards.
huawei(config)#board batadd 0/6 0/7 h601EDTB
Step 2 Confirm the EDTB boards.

Step 3 Add the remote service shelves.

huawei(config)#frame add 1
FrameType:
0 : MAIN_HABM_30(HABA) 1 : MAIN_HAFM_30(HABD)
2 : MAIN_HAFM_6(HABL) 3 : MAIN_H602HABD(HABD)
4 : MAIN_H601HABC(HABC) 5 : MAIN_H601HABO(HABO)
6 : MAIN_H601HABM(HABM) 7 : SLAVE_HAFS_32(HABE)
8 : SLAVE_HABS_32(HABB) 9 : SLAVE_HABS_30(HABA)
10 : SLAVE_HAFS_30(HABD) 11 : SLAVE_H602HABD(HABD)
12 : SLAVE_H602HABE(HABE) 13 : RSU_HAFS_30(HABD)
14 : RSU_HABS_30(HABA) 15 : RSU_HAFS_12(HABC)
16 : RSU_HAFS_6(HABL) 17 : RSUG_ONU60A(HUBO)
18 : RSUG_ONU04A 19 : RSUG_ONU08A
20 : RSP_19(HCB) 21 : RSP_15(HDB)
22 : RSP_14(HIB) 23 : RSP_12(HFB)

24 : RSP_10(HGB) 25 : RSP_6A(HMB)
26 : RSP_6B(HLB) 27 : UAM_R (HUBM)
28 : UAS_R (HUBS) 29 : UAFM_R(HUBE)
30 : UAFS_R(HUBF) 31 : UAMB_R(HUBB)
32 : ONU60A_R(HUBO) 33 : ONUF01D100_R(HUBL)
34 : VRSP_12(HABA) 35 : VRSP_18(HABA)
36 : HWTA(HIB_1) 37 : HWTA(HIB_2)
38 : HWTA(HIB_3)
Please select frame type (0 ~ 38):12
Frame add successfully
Step 4 Add the inter-shelf links.

huawei(config)#frame link start 0/6/0 end 1/4/0
Step 5 Query the inter-shelf links.

huawei(config)#display frame link
--------------------------------------------------------
Record UpBoardName Frame/Slot/Port DownBoardName Frame/Slot/Port
--------------------------------------------------------
1 H601EDTB 0 /6/0 RSU8 1 /4 /0
2 H601EDTB 0 /6/1 RSU8 1 /4 /1
3 H601EDTB 0 /6/2 RSU8 1 /4 /2
4 H601EDTB 0 /6/3 RSU8 1 /4 /3
5 H601EDTB 0 /6/4 RSU8 1 /4 /4
6 H601EDTB 0 /6/5 RSU8 1 /4 /5
7 H601EDTB 0 /6/6 RSU8 1 /4 /6
8 H601EDTB 0 /6/7 RSU8 1 /4 /7
9 H601EDTB 0 /6/8 RSU8 1 /5 /0
10 H601EDTB 0 /6/9 RSU8 1 /5 /1
11 H601EDTB 0 /6/10 RSU8 1 /5 /2
12 H601EDTB 0 /6/11 RSU8 1 /5 /3
13 H601EDTB 0 /6/12 RSU8 1 /5 /4
14 H601EDTB 0 /6/13 RSU8 1 /5 /5
15 H601EDTB 0 /6/14 RSU8 1 /5 /6
16 H601EDTB 0 /6/15 RSU8 1 /5 /7
--------------------------------------------------------
Step 6 Query the port status of the boards subtended between shelves.
huawei(config)#display port state 0/6
--------------------------------------------------------------------------
--------------------------------------------------------------------------
0 / 6 / 0 E1 Normal RSU -
0 / 6 / 10 E1 Normal RSU -
0 / 6 / 11 E1 Normal RSU -

0 / 6 / 12 E1 Normal RSU -
0 / 6 / 13 E1 Normal RSU -
0 / 6 / 14 E1 Normal RSU -
0 / 6 / 15 E1 Normal RSU -
--------------------------------------------------------------------------
--------------------------------------------------------------------------
--------------------------------------------------------------------------
--------------------------------------------------------------------------
--------------------------------------------------------------------------
--------------------------------------------------------------------------
--------------------------------------------------------------------------
Step 7 Add and confirm service boards in the slave shelf.

huawei(config)#board batadd 0/9 0/12 a32
Step 8 Add remote subscribers.

huawei(config-esl-user)#mgpstnuser batadd 1/9/0 1/12/31 0 terminalid 0 telno
12340001
----End
Result
After the E1 subtending is configured, subscribers with phone numbers 12340001–12340128
should be able to call each other.

Configuration Guide-PVM CLI 27 Configuring the QoS of the Voice Service
27 Configuring the QoS of the Voice Service
About This Chapter
Configuring the QoS of the voice service includes the application of the QoS technology and
the process for configuring the QoS test of the voice service on the UA5000.
27.1 Introduction to the Voice Service QoS

The quality of service (QoS) provides subscriber services with end-to-end quality assurance by
a set of measurement indexes, such as service availability, throughput, time delay, jitter, and
loss rate.
27.2 Configuration Example of the QoS Test Task
This topic describes how to start a passive QoS test task on the UA5000 to monitor the actual
service.

27.1 Introduction to the Voice Service QoS

The quality of service (QoS) provides subscriber services with end-to-end quality assurance by
a set of measurement indexes, such as service availability, throughput, time delay, jitter, and
loss rate.
Service Description
The UA5000 provides the function of the QoS test. The UA5000 can work with the EMS to test
the quality of the IP network, or start the QoS test by itself. The UA5000 can add an 802.1Q/
802.1p or a type of service (ToS) label to the upstream packet. The upper layer device in the IP
network can take proper measures according to the label to ensure the QoS of the voice service.
l Passive QoS test: After receiving the test command from the EMS or the host, the
UA5000 collects all QoS messages of appropriate sessions. The messages are reported to
the EMS through a test port at the scheduled time.
l The differences between the active and passive tests are as follows:
– In the active test, the call is set up automatically and the QoS information is recorded.
– In the passive test, the QoS information is recorded only when there are calls that meet
the requirements.
l In the QoS passive test, the UA5000 command line and the EMS are independent of each
other. The EMS can start the test task without running the UA5000 command line. The
UA5000 command line can, however, forcibly stop the test task started by the EMS.
l The UA5000 supports the active and passive QoS tests.
l The UA5000 supports a maximum of 16 passive QoS tests concurrently.
27.2 Configuration Example of the QoS Test Task

This topic describes how to start a passive QoS test task on the UA5000 to monitor the actual
service.
Prerequisite
Before a QoS test is started, the following parameters must be set:
l IP address of the peer device used in the test

l Start time of the test
l Interval for reporting the test result to the EMS
Data Plan
Table 27-1 provides the data plan for starting a QoS test at the local end.

Table 27-1 Data plan for starting a QoS test at the local end
Item Data
Loop delay 200 ms
Jitter 20 ms
Packet loss ratio 1%
IP address of the peer device 10.10.20.20
Index of the task 1
Context
To start a QoS test task on the UA5000, run the qos-rtptest command. The test result is not
reported to the EMS.
Procedure
Step 1 Set the QoS alarm threshold parameters.
huawei(config)#qos threshold loopdelay 200 jitter 20 packetlost 1
Step 2 Start the QoS test task on the UA5000.

huawei(config)#qos-rtptest 1 10.10.20.20
----End
Result
The QoS test task for 10.10.20.20 is started. When the QoS parameters exceed the thresholds,
the QoS alarms are generated. To verify the configuration of the QoS test task, do as follows:
huawei(config)#display qos-rtptest all
Task Index : 1
Task Execution Time (sec) : 0
Peer Address : 10.10.20.20
Duration (sec) :3600
Tick (sec) : 60
TaskMode : COMMAND
InPkts : 0
OutPkts : 0
InOctets : 0
OutOctets : 0
InDropPkts : 0
MaxDropRate (percent) : 0, Port :-/-/-
MinDropRate (percent) : 0, Port :-/-/-
MaxJitter (millisec) : 0, Port :-/-/-
MinJitter (millisec) : 0, Port :-/-/-
MaxLoopDelay (millisec) : 0, Port :-/-/-
MinLoopDelay (millisec) : 0, Port :-/-/-

Configuration Guide-PVM CLI 28 Configuring the Security of the Voice Service
28 Configuring the Security of the Voice

Service
About This Chapter
Configuring the security of the voice service includes the registration process of the device and
the configuration process of the UA5000 device authentication.
28.1 Introduction to the Voice Service Security

This topic describes how the UA5000 as an MG requests registration on the MGC and the
registration process of the device when the H.248 or MGCP protocol is used.
28.2 Configuring the Device Authentication
This topic describes how to configure the authentication parameters of the MG interface on the
UA5000 to implement the device authentication function when the H.248 or HGCP protocol is
used.

28.1 Introduction to the Voice Service Security

This topic describes how the UA5000 as an MG requests registration on the MGC and the
registration process of the device when the H.248 or MGCP protocol is used.
28.1.1 Registration Process When the H.248 Protocol Is Used

This topic describes the process that the UA5000 registers on the MGC as an MG and the MGC
verifies the validity of the MG identity when the H.248 protocol is used.
Service Description
Figure 28-1 shows the process for registering the MG with the MGC when the H.248 protocol
is used.
Figure 28-1 Process for registering the MG with the MGC (through the H.248 protocol)
MG MGC
(1) ServiceChange
Start
(2) Reply
(3) Modify
(4) Reply
(5) Modify
(6) Reply
Table 28-1 describes the registration process.
Table 28-1 Process for registering the MG with the MGC (through the H.248 protocol)
Number Description
(1) The MG sends a ServiceChange message to the MGC for registration. In

the ServiceChange message, TerminationID is Root, Method is Restart,
ServiceChangeReason is mandatory and the version is optional. The
message contains the MG timestamp (determined by the time of the MG)
and the MG ID. The values of the MG timestamp and the MG ID are
encrypted through MD5 by the static cipher key, which is set by both the
MG and the MGC.
(2) The MGC sends the Reply message to the MG.

Number Description
(3) The MGC sends the Modify message to the MG. The MGC produces a key
according to the MG timestamp, MG ID, and MGC ID. The MGC then sends
the Modify message that contains the key to the MG. The KEY is encrypted
through the MD5 by the static cipher key, which is set by both the MG and
the MGC.
(4) The MG sends the Reply message to the MGC.
(5) The MGC sends the Modify message, which contains the MGC timestamp
encrypted by the key.
(6) The MG receives the Modify message and obtains the MGC timestamp. The
MG sends the Reply message to the MGC. The message contains the MG
ID and the MGC timestamp encrypted by the key for authentication.
NOTE
After the registration is completed successfully, the MG sends the heartbeat detection messages for security
authentication. When the heartbeat detection message fails in the security authentication, the MGC forces
the MG to exit the service. The heartbeat detection messages are contained in the Modify message, and the
message sending interval is three minutes.
28.1.2 Registration Process When the MGCP Protocol Is Used

This topic describes the process that the UA5000 registers on the MGC as an MG and the MGC
verifies the validity of the MG identity when the MGCP protocol is used.
Service Description
In the MGCP protocol, the MG can register with the MGC in either of the following ways:
wildcard registration and single endpoint registration.
Wildcard registration
If there are a large number of subscribers under an MG interface, the registration process takes
a long time and a large number of messages are generated. In this case, wildcard registration is
recommended. Figure 28-2 shows the wildcard registration process.

Figure 28-2 Wildcard registration process (through the MGCP protocol)
MG MGC
(1) RSIP
Start
(2) ACK
(3) RQNT
(4) ACK
(5) RQNT
(6) ACK
(7) NTFY
(8) ACK
Table 28-2 describes the wildcard registration process when the MGCP protocol is used.
Table 28-2 Wildcard registration process (through the MGCP protocol)

Number Description
(1) The MG sends a registration request message to the MGC.
(2) The MGC sends a reply message to the MGC.
(3) The MGC sends the random number and algorithm ID for generating the
shared cipher key to the MG.
(4) The MG sends a reply message to the MGC.
(5) The MGC initiates the authentication of the MG.
(6) The MG sends a reply message to the MGC.
(7) The MG sends an authentication response message to the MGC.
(8) The MGC sends a reply message to the MG.
Single endpoint registration

To register a single MG, use the single endpoint registration process. Figure 28-3 shows the
single endpoint registration process.

Figure 28-3 Single endpoint registration process (through the MGCP protocol)
MG MGC
(1) RSIP
(2) ACK
(3) RQNT
(4) ACK
Table 28-3 describes the single endpoint registration process when the MGCP protocol is used.
Table 28-3 Single endpoint registration process (through the MGCP prtocol)
Number Description
1 The MG sends a registration message to the MGC.
2 The MGC sends a reply message to the MG.
3 The MGC sends a RQNT message to the MG.
4 The MG sends a reply message to the MGC.
28.2 Configuring the Device Authentication

This topic describes how to configure the authentication parameters of the MG interface on the
UA5000 to implement the device authentication function when the H.248 or HGCP protocol is
used.
28.2.1 Configuring the Device Authentication (the H.248 Protocol)

When the H.248 protocol is used, you can configure the UA5000 device authentication by
configuring the registration mode of the MG interface, the MG interface to support the device
authentication, authentication initial key, and authentication gateway ID of the MG interface.
Prerequisite
l The encryption type, initial key, and DH authentication MG ID must be configured on the
MGC. The parameters configured on the UA5000 must be the same as the parameters
Context
When the MGC is the SoftX3000 of Huawei, the authentication MG ID must be a string with
more than eight digits, and the initial key must be a string with more than eight and less than 16
digits.

Procedure
Step 2 Run the display mg-software parameter 4 command to query the registration mode used by
the MG interface.
l To register all the subscribers under the MG interface, use the wildcard registration mode.
l To register a single subscriber under the MG interface, use the single endpoint registration
mode.
Step 3 If the query result is different from the planned registration mode, run the mg-software
parameter 4 command to set the registration mode of the MG interface. If the query result is
the same as the planned registration mode, proceed to Step 4.
Step 4 Run the mg-software parameter 6 0 command to set the MG interface to support the device
authentication.
Step 5 Run the auth command to set the authentication MG ID and initial key.
Step 6 Run the display auth command to query the device authentication parameters.
Step 7 Run the reset command to reset the MG interface.
----End
Example
The following example describes how to configure the authentication for the UA5000. Table
28-4 provides the data plan for configuring the device authentication parameters.
Table 28-4 Data plan for configuring the device authentication parameters (through the H.248
protocol)
Item Data Item Data
MG interface ID 0 Whether to use the Yes

wildcard for
registration
Authentication MG UA5000 Initial key 0123456789ABCDE

ID F
-------------------------------------------------
-------------------------------------------------
APPENDIX:
-------------------------------------------------
Interface software parameter name:
4: Whether MG register to MGC with wildcard
0: Yes
1: No
huawei(config-if-h248-0)#auth auth_mgid ua5000 initial_key 0123456789ABCDEF
huawei(config-if-h248-0)#display auth
[AUTH_PARA config]

Initial Key : 0123456789ABCDEF

Auth MGid : UA5000
Algorithm : MD5
28.2.2 Configuring the Device Authentication (the MGCP Protocol)

When the MGCP protocol is used, you can configure the UA5000 device authentication by
configuring the registration mode of the MG interface, authentication initial key, and
authentication gateway ID of the MG interface.
Prerequisite
l The encryption type, initial key, and DH authentication MG ID must be configured on the
MGC. The parameters configured on the UA5000 must be the same as the parameters
Context
l When the MGC is the SoftX3000 of Huawei, the authentication MG ID must be a string
with more than eight digits, and the initial key must be a string with more than eight and
less than 16 digits.
l In the case of single endpoint registration, the UA5000 supports only the passive
authentication mode and does not support the active authentication mode.
Procedure
l Active authentication mode
NOTE
When the UA5000 uses the MGCP protocol and the MGC need not authenticate the subscribers of
the UA5000, select the passive authentication mode.
1. In the global config mode, run the interface mgcp command to enter the MG interface
mode.
2. Run the mg-software parameter 4 0 command to select the wildcard registration
mode.
3. Run the auth command to set the active authentication mode, and set the
authentication MG ID and initial key.
4. Run the display auth command to query the device authentication parameters.
5. Run the reset command to reset the MG interface.
l Passive authentication mode
1. In the global config mode, run the interface mgcp command to enter the MG interface
mode.
2. To register all the subscribers under the MG interface, run the mg-software
parameter 4 0 command to select the wildcard registration mode. To register a single
subscriber, proceed to Step 3.
3. Run the auth command to set the passive authentication mode, and set the
authentication key.

4. Run the display auth command to query the device authentication parameters.
5. Run the reset command to reset the MG interface.
----End
Example
The following example describes how to configure the active authentication mode for the
UA5000. Table 28-5 provides the data plan for configuring the active authentication mode.
Table 28-5 Data plan for configuring the active authentication mode (through the MGCP
protocol)
Item Data Item Data

wildcard for registration
Authentication MG UA5000 Initial key 0123456789ABCDEF

ID
huawei(config-if-mgcp-0)#auth mode2 auth_mgid
UA5000 initial_key 0123456789ABCDEF
huawei(config-if-mgcp-0)#display auth
active request authentication mode config:
Initial Key : 123456789ABCDEF
Auth MGid : UA5000
Algorithm : MD5
The following example describes how to configure the passive authentication mode for
theUA5000. Table 28-6 provides the data plan for configuring the passive authentication mode.
Table 28-6 Data plan for configuring the passive authentication mode (through the MGCP
protocol)
Item Data Item Data

wildcard for
registration
Initial key 0123456789ABCDEF - -
huawei(config-if-mgcp-0)#auth mode1 key 0123456789ABCDEF
huawei(config-if-mgcp-0)#display auth
passive respond authentication mode config:

Auth Key : 123456789ABCDEF

Algorithm : MD5

Configuration Guide-PVM CLI 29 Configuring the Reliability of the Voice Service
29 Configuring the Reliability of the Voice

Service
About This Chapter
UA5000 provides the assurance function of the reliable voice service. Configuring the reliability
of the voice service includes the application of the technology of the voice service reliability
and the process for configuring the voice service reliability of the UA5000.
29.1 Introduction to the Voice Service Reliability

The reliability of the UA5000 voice service is implemented through features such as dual
homing, standalone, emergency channel, and separation of the signaling stream and the media
stream.
29.2 Configuring the Dual Homing
Dual-homing is a disaster recovery mechanism to provide communication during emergency
situations when the softswitch device is down or an unexpected disaster occurs (such as fire in
the equipment room, disconnection of cables connected to the equipment room, and abnormal
power supply).
Configure the standalone service of the UA5000. When the UA5000 is disconnected from the
MGC, the UA5000 processes the services of the internal subscribers on the same MG interface
so that they can call each other without the support of the MGC.
29.4 Configuring an Emergency Channel
Configure an emergency channel of the UA5000. When the UA5000 is disconnected from the
MGC, the subscribers of the UA5000 can dial the external phone numbers that matches the
emergency digitmap.
29.5 Configuring the Separation Between the Signaling Stream and the Media Stream
This topic describes how to configure the signaling IP address and the media IP address for the
VAG to separate the signaling stream from the media stream.

29.1 Introduction to the Voice Service Reliability

The reliability of the UA5000 voice service is implemented through features such as dual
homing, standalone, emergency channel, and separation of the signaling stream and the media
stream.
Service Description
The details about the reliability of the UA5000 voice service are as follows:
l Dual homing
In dual homing, one UA5000 can register with two MGCs when the H.248 protocol is used
or one UA5000 can register with three MGCs when the MGCP protocol is used. When the
primary MGC is faulty and cannot communicate with the UA5000, the services are
switched to a secondary MGC.
The dual homing of the UA5000 is carried out by the heartbeat detection. Figure 29-1
shows the heartbeat detection and the switchover process.
Figure 29-1 Heartbeat detection and switchover process
UA5000 MGC1 MGC2
(1) Notify (it/ito)
Heatbeat lost (2) ServiceChange

(Method=Failover, Reason=909)
(3) Reply
Registration on MGC2 succeeds (4) ServiceChange

Registration on MGC2 fails (Method=Disconnected, Reason=909)
(5) Reply
Table 29-1 describes the heartbeat detection and the switchover process.
Table 29-1 Description of the heartbeat detection and the switchover process
No. Description
(1) The UA5000 sends several consecutive heartbeat detection messages

(Notify) and does not receive any response. This indicates that the
primary MGC (MGC1) is faulty.
(2) The UA5000 sends a registration request message ServiceChange

(Method = Failover, Reason = 909) to the MGC2 according to the
preset order in the MGC list.

No. Description
(3) If the UA5000 receives a response Reply from the MGC2, it indicates
that the registration on the MGC2 is successful and the process is
complete. If the UA5000 does not receive a response from the MGC2
after sending the several consecutive ServiceChange messages, it
indicates that the registration on the MGC2 has failed.
(4) If there is another MGC in the secondary MGC list, the UA5000 repeats
step 2 and step 3 for the next MGC. If there is no other secondary MGC,
the UA5000 sends the registration message ServiceChange (Method =
Disconnected, Reason = 909 (neighboring MGC fault)) to the original
primary MGC (MGC 1) based on the avalanche mechanism for
preventing the reset after a random delay.
(5) If the UA5000 receives the response Reply from the MGC1, the
communication between the UA5000 and the MGC1 is restored and
the process is complete. If the UA5000 does not receive a response
after sending several consecutive ServiceChange requests to the
MGC1, the registration on the MGC1 fails and the UA5000 proceeds
with step 2.
l Internal call standalone

When the UA5000 is disconnected from the MGC, the subscribers on the same MG
interface can call each other. The MG interface is supported by the UA5000 instead of the
MGC.
l Emergency channel
When the UA5000 is disconnected from the MGC, the subscribers of the UA5000 can dial
the external phone numbers that are listed in the digitmap as emergency call phone numbers.
For example, in the case of a fire, you can dial the fire emergency number, such as 911 in
the United States.
l Separation of the signaling stream and the media stream
Each VAG can be configured with independent signaling IP address and media stream IP
address, and can be configured in different VLANs. You can separate the control and the
transmission by separating the signaling stream from the media stream to enhance the
reliability of the voice service. The H.248 protocol supports this feature and the MGCP
protocol does not support this feature.
29.2 Configuring the Dual Homing

Dual-homing is a disaster recovery mechanism to provide communication during emergency
situations when the softswitch device is down or an unexpected disaster occurs (such as fire in
the equipment room, disconnection of cables connected to the equipment room, and abnormal
power supply).
29.2.1 Configuring the Dual Homing (the H.248 Protocol)

Configuring the dual homing means registering one UA5000 with two MGCs. When one MGC
is faulty and cannot support the communication, the UA5000 automatically switches to the other
MGC.

Prerequisite
l In the MG interface attributes, MGC1 and MGC2 must be configured.
l On the MGCs, the data for interconnecting to the UA5000 must be configured.
Procedure
Step 2 Run the mg-software parameter command to configure the MG interface to support dual
homing.
----End
Example
To configure the MG interface (with ID 0) on the UA5000 to support dual homing through the
heartbeat detection, do as follows:
29.2.2 Configuring the Dual Homing (the MGCP Protocol)

Configuring the dual homing means registering one UA5000 with two MGCs. When one MGC
is faulty and cannot communicate with the MG, the UA5000 automatically switches to the other
MGC.
Prerequisite
Procedure
Step 2 Run the mg-software parameter command to enable the function of the heartbeat message.
Step 3 Run the mg-software parameter command to configure the MG interface to support dual
homing.
----End
Example
To configure the MG interface (with ID 0) on the UA5000 to support dual homing through
heartbeat detection, do as follows:


Configure the standalone service of the UA5000. When the UA5000 is disconnected from the
MGC, the UA5000 processes the services of the internal subscribers on the same MG interface
so that they can call each other without the support of the MGC.
l Currently, the telephone numbers configured for the standalone service cannot be checked
for repetition. When configuring the telephone numbers for the standalone service, make
sure that the telephone numbers are unique. Otherwise, the standalone service cannot be
implemented.
l The telephone numbers configured on the UA5000 must be the same as the telephone
numbers configured on the MGC.
l The UA5000 supports the standalone service only when it uses the H.248 protocol.
Figure 29-2 shows the flowchart for configuring the standalone service.
Figure 29-2 Flowchart for configuring the standalone service
Start
Configure voice subscriber

data
Configure service types in

standalone
standalone timers
Configure the digitmap for

internal calls
End
NOTE
For details about how to configure the voice subscriber data, see "10 Configuring the VoIP Service."

29.4 Configuring an Emergency Channel

Configure an emergency channel of the UA5000. When the UA5000 is disconnected from the
MGC, the subscribers of the UA5000 can dial the external phone numbers that matches the
emergency digitmap.
Context
The UA5000 supports the emergency channel function only when it uses the H.248 protocol.
Service Description
Emergency call applies when the network to which the caller is connected fails. The caller is
configured with ports for emergency calls on the CDI board, and the ports are connected to the
ports for outgoing calls. These ports serve as the agent for setting up external calls. As the
resources on the ports are limited, only important and emergency numbers are configured in the
digitmap for emergency calls to ensure the connectivity of these calls.
Figure 29-3 shows the flowchart for configuring the emergency channels.
Figure 29-3 Flowchart for configuring the emergency channels
Start
Configure voice subscriber

data
Add a CDI board
Configure attributes
for the CDI ports
Configure emergency
channels
standalone timers
Configure digitmap for

emergency calls
End

Procedure
Step 1 Run the board add command to add the CDI board.
Step 2 Run the board confirm command to confirm the CDI board.
Step 3 Run the cdi command to enter the CDI mode.
Step 4 Run the port attribute set command to configure the attributes for the CDI ports.
Step 5 Run the quit command to exit the CDI mode.
Step 6 Run the esl user command to enter the ESL user mode.
Step 7 Run the mgddiuser add frameid/slotid/portid emergency command to configure the port as
the port for an emergency channel.
Step 8 Run the quit command to exit the ESL user mode.
Step 9 Run the interface h248 command to enter the MG interface mode.
Step 10 Run the digitmap set emergency command to set the digitmap for emergency calls.
----End
Example
The following example describes how to set port 0 on the CDI board at frame 0/slot 10 as the
port of the emergency channel, and set the digitmap for emergency calls as 119|110|168xxxxx.
huawei(config)#cdi
huawei(config-cdi)#port attribute set 0/10/0 workmode ddi
huawei(config-esl-user)#mgddiuser add 0/10/0 emergency
huawei(config-h248-0)#digitmap set emergency 119|110|168xxxxx
29.5 Configuring the Separation Between the Signaling

Stream and the Media Stream
This topic describes how to configure the signaling IP address and the media IP address for the
VAG to separate the signaling stream from the media stream.
Prerequisite
l The system must be configured to support the H.248 protocol.
l The IP address to be used in the example must be configured in the IP address pool. For
details of adding the IP address, see the ip address command.

Context
The signaling IP address and the media IP address of the VAG are two optional parameters in
the attributes of the MG interface. For information about the other parameters of the MG interface
attributes, see "9.6 Configuring the Attributes of the MG Interface (the H.248 Protocol)."
Procedure
Step 1 In global config mode, run the interface h248 command to enter the MG interface mode.
Step 2 Run the if-h248 attribute command to configure the signaling IP address and the media IP
address so that they are different from each other.
Step 3 Run the display if-h248 attribute command to query the configuration of the signaling IP
address and the media IP address.
----End
Example
To configure the signaling IP address as 10.10.10.2 and the media IP address as 192.168.10.2
for MG interface 0 of the UA5000, do as follows:
huawei(config-if-h248-1)#if-h248 attribute mgip 10.10.10.2 mgport 2944 mgcip_1
10.10.10.4 mgcport_1 9800 code text transfer udp mg-media-ip 10.144.78.138
---------------------------------------------------------------------
MGID 1
MG Description -
MG DomainName -
Protocol H248
2833Encrypt -
Codetype Text
Transmode UDP
MG media IP 10.144.78.138
MIDType IP4_ADDR
DeviceName -

---------------------------------------------------------------------

Configuration Guide-PVM CLI 30 Configuring the Link Detection
30 Configuring the Link Detection
About This Chapter
The UA5000 provides the function of the layer 2 link detection. Configuring the link detection
includes the application of the UA5000 link detection technology and the process for configuring
the link detection.
30.1 Introduction to the Link Detection

The link detection that the UA5000 supports includes the ARP link detection, BFD link
detection, and ETH_OAM link detection.
30.2 Configuration Example of the ARP Link Detection
This topic describes how to configure the ARP link detection on the UA5000. When the ARP
link detection on the UA5000 is enabled, the UA5000 can monitor the link status. When the link
is faulty, the UA5000 switches the links to avoid the long-time service interruption (the
interruption lasts for several seconds).
30.3 Configuration Example of the BFD Link Detection
This topic describes how to configure the BFD link detection on the UA5000. When the BFD
interruption lasts for a few hundred milliseconds).
30.4 Configuration Example of the ETH_OAM Layer 2 Link Detection
This topic describes how to configure the ETH_OAM link detection on the UA5000. When the
ETH_OAM link detection on the UA5000 is enabled, the UA5000 can monitor the link status.
When the link is faulty, the UA5000 switches the links to avoid the long-time service interruption
(the interruption lasts for a few hundred milliseconds).

30.1 Introduction to the Link Detection

The link detection that the UA5000 supports includes the ARP link detection, BFD link
detection, and ETH_OAM link detection.
Service Description
l An increasingly important feature of the network device is: The UA5000 is required to
quickly detect the fault in the communication between the adjacent systems or in the end-
to-end communication. When the device is faulty, the UA5000 can set up the alternative
channel or switch the service to other links in less time.
l The UA5000 can use the mechanism of active/standby switchover to ensure the service
stability. Functions of the link protection on the UA5000 include the following:
– ARP link detection: After the ARP link detection is enabled, the UA5000 sends the
ARP packet to the gateway that matches the primary service IP address to detect the
link. After the UA5000 detects that the link is faulty, it performs the active/standby
switchover between the two uplink network ports. In this case, the service is switched
to the standby link to ensure the normal transmission of the service.
– BFD link detection: BFD can detect the fault in any type of channel between systems.
BFD focuses on quickly detecting the fault of the link, and ensures better QoS for
transmitting the voice, video, and VoD services. It provides subscribers with the services
featuring high reliability and high applicability, such as VoIP services and other real-
time services.
– ETH_OAM link detection: ETH_OAM performs the link detection and the link
switchover protection as quickly as BFD.
Service specifications of the ARP, BFD, and ETH_OAM link detections are as follows:
l ARP link detection: It supports the detection of a single link only. The control boards that
support this feature are PVMB, and PVMD.
l BFD link detection: It supports the detection of a single link and double links. The control
board that supports this feature is PVMD.
l ETH_OAM link detection: It supports the detection of double links only. The control board
that supports this feature is PVMD.
30.2 Configuration Example of the ARP Link Detection

This topic describes how to configure the ARP link detection on the UA5000. When the ARP
interruption lasts for several seconds).
Prerequisite
l The networking of the UA5000 must support the ARP link detection. The networking
modes that support the ARP link detection are as follows:

– Independent uplink networking through the active service port with the configuration
of two PVM control boards
The UA5000 is configured with two PVM control boards. The UA5000 uses the
independent uplink mode and transmits the service packets upstream to the upper layer
device through the active network port on the PVM control board.
– Uplink networking with the configuration of one PVM control board
The UA5000 is configured with one PVM control board. The UA5000 transmits the
service packets upstream to the upper layer device through the network port on the PVM
control board.
NOTE
In the mode of the uplink networking with the configuration of one PVM control board, when
the link is faulty, the UA5000 reports only the status of the link to you and does not perform the
active/standby switchover for the uplink network port.
The integrated networking of IPMB or PVM does not support the ARP link detection.
l The UA5000 uses PVMB, or PVMDas its control boards.
Networking
Figure 30-1 shows the example network for configuring the ARP link detection.
Use network cables to connect network ports of slot 0/4 and slot 0/5 of the UA5000 to the router.
Set up an ARP link between slot 0/4 of the UA5000 and the router.
Figure 30-1 Example network for configuring the ARP link detection
MGC
Router
ARP link
FE FE 0/11
P P A
V V 3
UA5000
M M
2
B B
0/4 0/5
phone1 phone32

Data Plan
Table 30-1 provides the data plan for configuring the ARP link detection.
Table 30-1 Data plan for configuring the ARP link detection
Type Item Data
Detection link Name of the detection link group group1

group
Detection mode of the link group single-detect
NOTE
The ARP link detection supports
only the single-link detection.
Detection protocol of the link group arp-detect
ARP detection link Name of the ARP detection link Adetect
Figure 30-2 shows the flowchart for configuring the ARP link detection.
Figure 30-2 Flowchart for configuring the ARP link detection
Start
Add a detection link group
Add an ARP detection link
Activate the detection link group
Query the status and the

configuration of the detection link
End
CAUTION
Add a detection link group before setting up an ARP detection link.

Procedure
Step 1 Add a detection link group.
huawei(interface-eth)#detect-group add group1 mode single-detect
protocol arp-detect
Step 2 Add an ARP detection link.

huawei(interface-eth)#arp-detect add Adetect detect-group group1
Step 3 Activate the detection link group.

huawei(interface-eth)#detect-group enable group1
Step 4 Query the status and the configuration of the detection link.
huawei(interface-eth)#display arp-detect state
-----------------------------------------------------------------------
LinkName State F/S M/S GroupName
-----------------------------------------------------------------------
Adetect Up 0/4 master group1
-----------------------------------------------------------------------
huawei(interface-eth)#display arp-detect configuration
-----------------------------------------------------------------------
LinkName Tx_interval(ms) Rx_interval(ms) Multiplier GroupName
-----------------------------------------------------------------------
Adetect 2000 2000 3 group1
-----------------------------------------------------------------------
----End
Result
l Run the display arp-detect state command to query the status of the detection link.
l Run the display arp-detect configuration command to query the configuration of the
detection link.
l When the link is faulty, the UA5000 can detect the faulty link and can automatically perform
the switchover. This shortens the duration of the service interruption (the interruption lasts
for only several seconds) on the UA5000.
30.3 Configuration Example of the BFD Link Detection

This topic describes how to configure the BFD link detection on the UA5000. When the BFD
interruption lasts for a few hundred milliseconds).
Prerequisite
l The networking of the UA5000 must support the BFD link detection. The networking
modes that support the BFD link detection are as follows:
– Independent uplink networking through the active service port with the configuration
of two PVM control boards
The UA5000 is configured with two PVM control boards. The UA5000 uses the
independent uplink mode and transmits the service packets upstream to the upper layer
device through the active network port on the PVM control board. In this case, you can
configure the BFD single-link detection or the BFD double-link detection.

– Uplink networking with the configuration of one PVM control board

The UA5000 is configured with one PVM control board. The UA5000 transmits the
service packets upstream to the upper layer device through the network port on the PVM
control board. In this case, you can configure the BFD single-link detection.
NOTE
In the mode of the uplink networking with the configuration of one PVM control board, when
the link is faulty, the UA5000 reports only the status of the link to you and does not perform the
active/standby switchover for the uplink network port.
The integrated networking of IPMB or PVM does not support the BFD link detection.
l The UA5000 uses PVMD as its control board.
Networking
Figure 30-3 shows the example network for configuring the BFD link detection.
Connect network ports of slot 0/4 and slot 0/5 of the UA5000 to the router by using network
cables. Set up a BFD link between slot 0/4 of the UA5000 and the router and a link between slot
0/5 and the router.
NOTE
The following network uses the detection of double BFD links as an example. The networking and the
configuration for the detection of a single BFD link is similar to the networking and configuration for the
ARP detection. See "30.2 Configuration Example of the ARP Link Detection."
Figure 30-3 Example network for configuring the BFD link detection
MGC
Router Router
10.10.10.90 10.10.10.94
Link 1 Link 2
FE/GE 10.10.10.70 10.10.10.78 FE/GE
P P A
V V 3
UA5000
M M
2
D D
0/4 0/5 0/11
phone1 phone32

Data Plan
Table 30-2 provides the data plan for configuring the BFD link detection.
Table 30-2 Data plan for configuring the BFD link detection
Type Item Data

group
Detection mode of the link group double-detect
NOTE
The BFD link detection
supports the single-link
detection or the double-
link detection. The
following uses the
double-link detection
as an example.
Detection protocol of the link group bfd
BFD detection link Name of the BFD detection link Bdetect1

Bdetect2
peerip 10.10.10.94
10.10.10.90
localip 10.10.10.78
10.10.10.70
NOTE
When you configure
the BFD double-link
detection, localip must
be configured with
different IP addresses.
Figure 30-4 shows the flowchart for configuring the BFD link detection.

Figure 30-4 Flowchart for configuring the BFD link detection
Start
Enable the uplink port of

the standby control board
Add a BFD detection link

End
CAUTION
l Add a detection link group before setting up a BFD detection link.
l Run the uplink tps on command to enable the uplink port of the standby control board before
setting up the detection for double BFD links. Otherwise, when the active link is faulty, the
services cannot be switched to the standby link.
l When you set up the detection for a single BFD link, you need not enable the port on the
standby control board.
Procedure
Step 1 Enable the uplink port of the standby control board.
huawei(config)#uplink tps on

huawei(interface-eth)#detect-group add group1 mode double-detect
protocol bfd
Step 3 Add a BFD detection link.

huawei(interface-eth)#bfd add Bdetect1 detect-group group1 peerip 10.10.10.94
interface 0/4 discriminator 2 localip 10.10.10.78 rx-interval 50 tx-interval 50
echo on multiplier 5

huawei(interface-eth)#bfd add Bdetect2 detect-group group1 peerip 10.10.10.90

interface 0/5 discriminator 3 localip 10.10.10.70 rx-interval 50 tx-interval 50
echo on multiplier 5

huawei(interface-eth)#display bfd state
-----------------------------------------------------------------------
-----------------------------------------------------------------------
Bdetect1 Up 0/4 master group1
Bdetect2 Up 0/5 slave group1
-----------------------------------------------------------------------
huawei(interface-eth)#display bfd configuration
-----------------------------------------------------------------------
LinkName : Bdetect1
Peer IP : 10.10.10.94
Interface : 0/4
Descriminator : 2
Local IP : 10.10.10.78
RX-interval(ms) : 50
TX-interval(ms) : 50
AcRXinterval(ms): 300
AcTXinterval(ms): 300
Multiplier : 5
Echo : On
GroupName : group1
-----------------------------------------------------------------------
LinkName : Bdetect2
Peer IP : 10.10.10.90
Interface : 0/5
Descriminator : 3
Local IP : 10.10.10.70
Multiplier : 5
Echo : On
GroupName : group1
-----------------------------------------------------------------------
----End
Result
l Run the display bfd state command to query the status of the detection link.
l Run the display bfd configuration command to query the configuration of the detection
link.
the switchover. This ensures that the service lasts for only a few hundred milliseconds.
30.4 Configuration Example of the ETH_OAM Layer 2 Link

Detection
This topic describes how to configure the ETH_OAM link detection on the UA5000. When the
ETH_OAM link detection on the UA5000 is enabled, the UA5000 can monitor the link status.
When the link is faulty, the UA5000 switches the links to avoid the long-time service interruption
(the interruption lasts for a few hundred milliseconds).

Prerequisite
l The networking of the UA5000 must support the ETH_OAM layer 2 link detection. The
networking modes that support the ETH_OAM link detection are as follows:
Independent uplink networking through the active service port with the configuration of
two PVM control boards. The UA5000 is configured with two PVM control boards. The
UA5000 uses the independent uplink mode and transmits the service packets upstream to
the upper layer device through the active network port on the PVM control board.
NOTE
The integrated networking of IPMB or PVM does not support the ETH_OAM link detection.
l The UA5000 uses PVMD as its control board.
Networking
Figure 30-5 shows the example network for configuring the ETH_OAM layer 2 link detection.
Use network cables to connect network ports of slot 0/4 and slot 0/5 of the UA5000 to the router.
Set up an ETH_OAM link between slot 0/4 of the UA5000 and the router, and an ETH_OAM
link between slot 0/5 and the router.
Figure 30-5 Example network for configuring the ETH_OAM layer 2 link detection
MGC
Router Router
Link 1 Link 2
FE/GE FE/GE 0/11
P P A
V V 3
UA5000
M M
2
D D
0/4 0/5
phone1 phone32
Data Plan
Table 30-3 provides the data plan for configuring the ETH_OAM layer 2 link detection.

Table 30-3 Data plan for configuring the ETH_OAM layer 2 link detection
Type Item Data

group
Detection mode of the link group double-detect
NOTE
The ETH_OAM link
detection supports only
the double-link
detection.
Detection protocol of the link group ethoam
ETH_OAM Name of the ETH_OAM detection link Edetect1

detection link Edetect2
peerip 10.10.10.220
10.10.10.210
localip 10.10.10.221
10.10.10.221
NOTE
When you configure
the ETH_OAM link
detection, localip must
be configured with the
same IP addresses.
Figure 30-6 shows the flowchart for configuring the ETH_OAM link detection.

Figure 30-6 Flowchart for configuring the ETH_OAM link detection
Start
Enable the uplink port of

the standby control board
Add an ETH_OAM detection link

End
CAUTION
l Add a detection link group before setting up an ETH_OAM detection link.
l Run the uplink tps on command to enable the uplink port of the standby control board before
setting up the ETH_OAM detection link. Otherwise, when the active link is faulty, the
services cannot be switched to the standby link.
Procedure
Step 1 Enable the uplink port of the standby control board.
huawei(config)#uplink tps on

huawei(interface-eth)#detect-group add group1 mode double-detect
protocol ethoam
Step 3 Add an ETH_OAM detection link.

huawei(interface-eth)#ethoam add Edetect1 detect-group group1
peerip 10.10.10.220 interface 0/4 localip 10.10.10.221 rx-interval 30
tx-interval 40 multiplier 4 mdlevel 1
huawei(interface-eth)#ethoam add Edetect2 detect-group group1
peerip 10.10.10.210 interface 0/5 localip 10.10.10.221 rx-interval 30
tx-interval 40 multiplier 4 mdlevel 1


huawei(interface-eth)#display ethoam state
-----------------------------------------------------------------------
-----------------------------------------------------------------------
Edetect1 Up 0/4 master group1
Edetect2 Up 0/5 slave group1
-----------------------------------------------------------------------
huawei(interface-eth)#display ethoam configuration
-----------------------------------------------------------------------
LinkName : Edetect1
Peer IP : 10.10.10.220
Interface : 0/4
Local IP : 10.10.10.221
Multiplier : 4
MDLevel : 1
GroupName : group1
-----------------------------------------------------------------------
LinkName : Edetect2
Peer IP : 10.10.10.210
Interface : 0/5
Local IP : 10.10.10.211
Multiplier : 4
MDLevel : 1
GroupName : group1
----------------------------------------------------------------------
----End
Result
l Run the display ethoam state command to query the status of the detection link.
l Run the display ethoam configuration command to query the configuration of the
detection link.
the switchover. This ensures that the service interruption lasts for only a few hundred
milliseconds.

Configuration Guide-PVM CLI 31 Configuring the Environment Monitoring
31 Configuring the Environment

Monitoring
About This Chapter
This topic provides an overview of the environment monitoring and describes how to configure
the environment monitoring on the UA5000.
31.1 Introduction to the Environment Monitoring
During the environment monitoring, the environment monitoring serial port of the device is
connected to the communication serial port of the monitored device. Through the master-slave
node protocol or the access network protocol, the operator can directly monitor the environment
conditions of devices.
31.2 Configuration Example of the ESC
This topic describes how to set the analog and digital parameters of the ESC. In this example,
configuring the ESCM whose serial port type is RS232 is considered as an example. The
configuration procedures of the H302ESC, H303ESC, H304ESC, and H801ESC are the same
as the configuration procedure of the ESCM.
31.3 Configuration Example of the Fan Monitoring
This topic describes how to configure the speed adjustment mode and the alarm switch of the
fan. Thus, the fan speed of the UA5000 can be adjusted automatically, and the fan tray of the
UA5000 can be monitored.
31.4 Configuration Example of the Power Monitoring
This topic considers the Power4875L as an example and describes how to configure its
environment monitoring parameters. The procedures for configuring the Power4875,
Power4845, and Power4820 are the same as the procedure for configuring the Power4875L.
31.5 Configuration Example of the Universal Power Monitoring
This topic describes how to monitor the universal power through the ESC by using the
configuration example of the PSM-A power monitoring through the H303ESC. (The PSM-A is
one type of Emerson power and is displayed as PSMA on the CLI.)
31.6 Adding an EMU
This topic describes how to add an EMU. After connecting the EMU to the monitoring serial
port correctly, you need to add the corresponding EMU to the host system of the UA5000.
31.7 Setting the ESC Analog Parameters

This topic describes how to set the upper and lower alarm thresholds of the analog parameters,
such as temperature, humidity, voltage, and current, or how to set the customized alarms of the
analog parameters.
31.8 Setting the ESC Digital Parameters
This topic describes how to set the alarm levels of digital parameters such as the door status
sensor, or how to configure the customized alarms of the digital parameters.
31.9 Configuring the Fan Alarm Reporting
This topic describes how to configure the reporting of all the fan alarms to the control unit.
31.10 Setting the Fan Speed Adjustment Mode
This topic describes how to set the fan speed adjustment mode. If the fan is not in the automatic
speed adjustment mode, the flow of air is more when the temperature is low or normal.
31.11 Setting the Fan Speed
This topic describes how to set the fan speed.
31.12 Setting the Power Supply Parameters
This topic describes how to set the parameters of the power shelf in the UA5000 to ensure the
normal running of the power shelf.

31.1 Introduction to the Environment Monitoring

During the environment monitoring, the environment monitoring serial port of the device is
connected to the communication serial port of the monitored device. Through the master-slave
node protocol or the access network protocol, the operator can directly monitor the environment
conditions of devices.
Service Description
The environment parameters such as temperature, humidity, and power voltage can be monitored
to ensure that the UA5000 works stably in a suitable environment.
To perform the environment monitoring on a device, the environment monitoring functional

modules, such as the H303ESC, H304ESC, or ESCM must be provided. In addition, some
monitored devices provide the built-in monitoring modules, such as the Power4845, Power4860,
Power4875, and Power4875L. These functional modules that can implement the monitoring are
referred to as the environment monitor units (EMUs), regardless of whether they are built-in or
not.
The EMU supported by the UA5000 can be classified into the following four categories:
l Environment supervision circuit (ESC): Includes the H303ESC, H302ESC, H801ESC,

H304ESC, and ESCM. Monitors the environment parameters such as ambient temperature,
humidity, smoke, water, fire, voltage, and power through various sensors.
l FAN: Monitors the running status of the fan and adjusts the running speed of the fan
according to the settings.
l DIS: Refers to the power distribution unit (PDU). Divides one or two DC inputs into
multiple outputs.
l Power: Includes the Power4820, Power4845, Power4875, Power4875L, and PSE158.
Monitors the environment parameters such as temperature, humidity, voltage, and power
supply through various sensors.
According to the type of the adopted power supply mode (power distribution–DC, power–AC),
the device is generally configured with power shelf EMU or PDU EMU.
When the UA5000 is connected to the corresponding EMU, bits 1 to 5 of DIP switch S1 on the
ESC of the PDU need to be switched on.
The five bits of the DIP switch define the address of the slave node for the PDU EMU to
communicate with the host of the UA5000. When all the five bits are switched on, it indicates
that the address of the slave node is 0. This is the number of the slave node of the EMU assigned
by the UA5000.
NOTE
For the hardware connections of the environment monitoring board and the settings of the DIP switch, see
"ESC board" in the UA5000 Hardware Description.
For the principles, configuration table, functions, and sensors of the environment monitoring, see
"Environment Monitoring."

31.2 Configuration Example of the ESC

This topic describes how to set the analog and digital parameters of the ESC. In this example,
configuring the ESCM whose serial port type is RS232 is considered as an example. The
configuration procedures of the H302ESC, H303ESC, H304ESC, and H801ESC are the same
as the configuration procedure of the ESCM.
Prerequisite
l The ESCM and the shelf of the UA5000 must be connected through the RS232 serial port
cable according to the serial port type of the shelf.
l The settings of the ESCM DIP switch must be consistent with the slave node of the EMU.
NOTE
For the detailed settings of the DIP switch, see "ESC - Environment Monitoring."
l When you add the EMU to the device, you must comply with the following rules:
– The system supports only one type of EMU except the ESCM.
– If the ESCM is added to the system, you can add the other EMU.
Data Plan
In this example, the serial port type is RS232. Table 31-1 provides the data plan for configuring
the ESCM.
Table 31-1 Data plan for configuring the ESCM
Item Data Remarks
EMU Type: MiniESC The ESCM is displayed as

MiniESC on the CLI.
Number: 0 -
Subnode: 30 When the RS232 serial port

is selected for the ESCM, the
slave node number must be
set to 30.
Analog parameters Analog parameter ID: 0 Set the analog parameter

according to the actual
requirement. The built-in
analog parameter is set to
monitor the ambient
temperature for the device
running.
For the value of the
parameter and the details, see
the esc analog command.

Item Data Remarks
Upper alarm threshold of When the ambient

analog parameter 0: 54 temperature of the device
reaches or exceeds 54°C, the
host reports an alarm.
Lower alarm threshold of When the ambient

analog parameter 0: 6 temperature of the device is
equal to or lower than 6°C,
the host reports an alarm.
Analog parameter ID: 2 The customized humidity

monitoring analog parameter
is added to monitor the
humidity of the device.
For the value of the
parameter and the details, see
the esc analog command.
Upper alarm threshold of When the humidity of the

analog parameter 2: 75% RH device reaches or exceeds
75% RH, the host reports an
alarm.
Lower alarm threshold of When the humidity of the

analog parameter 2: 5% RH device is equal to or lower
than 5% RH, the host reports
an alarm.
Name of analog parameter 2: -

humidity
Alarm index ID of analog The customized humidity

parameter 2: 2 alarm of the system is used.
Unit of analog parameter 2: -

% RH
Sensor type of analog -

parameter 2: voltage type
Digital parameters Digital parameter ID: 0 Set the digital parameter

requirement. The monitoring
digital parameter of the MDF
is configured to monitor the
MDF status. When the MDF
is faulty, the host reports an
alarm.
Valid level of digital When the high level is used

parameter 0: high level to represent the valid level,
the host does not report an
alarm in case of high level.

Item Data Remarks
Digital parameter ID: 1 Set the digital parameter

requirement. The monitoring
digital parameter of the
cabinet door is set to monitor
the cabinet door status. When
the cabinet door is open, the
host reports an alarm.
Valid level of digital When the low level is used to

parameter 1: low level represent the valid level, the
host does not report an alarm
in case of low level.
Context
l The differences between the analog parameter and digital parameter are as follows:
– An analog parameter is a continuous value, such as temperature, voltage, and current.
When the analog parameter is used to monitor the interface, an analog parameter sensor
is usually used, which provides test analog parameters in real time.
– A digital parameter is a discrete value that indicates a state. A digital sensor has only
two values: normal and faulty.
l When you set the slave node and communication baud rate, ensure that the following
conditions are met:
– When the serial port for the ESCM is RS485, the settings of the slave node ID and the
DIP switch must be consistent. The communication baud rate must be set to 19200 bit/
s.
– When the serial port for the ESCM is RS232, the slave node ID must be set to 30. The
communication baud rate must be set to 9600 bit/s.
Figure 31-1 shows the flowchart for configuring the ESCM.

Figure 31-1 Flowchart for configuring the ESCM
Procedure
Step 1 Add an EMU.
Add the EMU with the EMU ID 0, the type ESCM (MiniESC on the CLI), the slave node 30,
and the serial port type RS232.
huawei(config)#emu add 0 MiniESC 0 30 rs232 MiniESC
Step 2 Set the analog parameters.

huawei(config)#interface emu 0
huawei(config-if-MiniESC-0)#esc analog 0 alarm-upper-limit 54 alarm-lower-limit
6
5 name humidity sensor-type 0:voltage analog-alarm 2 unit %RH
Step 3 Set the digital parameters.

huawei(config-if-MiniESC-0)#esc digital 0 available-level high-level
huawei(config-if-MiniESC-0)#esc digital 1 available-level low-level
Step 4 Query the ESC environment information.

huawei(config-if-MiniESC-0)#display esc environment info
EMU ID: 0 ESC environment state
---------------------------Analog Environment Info--------------------------
ID Name State Value AlmUpper AlmLower Unit
0 Temperature Normal 29.000 54 6 C
1 Input_-48V_0 Normal 48.046 70 35 volt
2 Humidity Normal 10.000 75 5 %RH
3 - Normal -128.000 127 -128 -
---------------------------Digital Environment Info---------------------------
ID Name State Value |ID Name State Value
0 Wiring Normal 1 |1 Door0 Alarm 1
2 - Normal 1 |3 - Normal 1

----------------------------------------------------------------------------

huawei(config-if-MiniESC-0)#quit
huawei(config)#save
----End
Result
After the configuration, the ESCM works in the normal state and monitors the analog and digital
monitoring parameters set on the UA5000. When a monitoring parameter exceeds the normal
range, the host reports an alarm.
31.3 Configuration Example of the Fan Monitoring

This topic describes how to configure the speed adjustment mode and the alarm switch of the
fan. Thus, the fan speed of the UA5000 can be adjusted automatically, and the fan tray of the
UA5000 can be monitored.
Prerequisite
The hardware DIP switch of the fan tray must be set so that it is consistent with the slave node
value of the EMU. The baud rate must be set to 19200 bit/s.
Data Plan
Table 31-2 provides the data plan for configuring the fan monitoring.
Table 31-2 Data plan for configuring the fan monitoring
Item Data Remarks
EMU Type: FAN -
Number: 1 -
Subnode: 6 This parameter corresponds to the

hardware DIP switch of the fan tray,
but cannot be the same as the slave
node of the ESC.
Serial port of environment The serial port of environment

monitoring communication: RS485 monitoring communication of the
fan tray must be set to RS485.
FAN Fan speed adjustment mode: In this mode, the fan speed is
parameters automatic adjusted according to the
temperature automatically. By
default, the fan speed adjustment
mode is automatic.

Item Data Remarks
Report the alarm that the fan tray When the fan tray fails to read the
fails to read the temperature sensor: temperature sensor, the host reports
permit the alarm automatically.
Report the alarm that the fan is When the fan is blocked, the host
blocked: permit reports the alarm automatically.
Report the alarm that the When the temperature of the fan tray
temperature is very high: permit is very high, the host reports the
alarm automatically.
Report the alarm that the power When the power supply of the fan
supply is faulty: permit tray is faulty, the host reports the
alarm automatically.
Figure 31-2 shows the flowchart for configuring the fan monitoring.
Figure 31-2 Flowchart for configuring the fan monitoring
start
Add a fan tray
Automatic
Set the fan speed
adjustment mode
Manual
Set the fan speed
Set whether to report the

alarm
Query the configuration

parameters
Save the data
End

Procedure
Step 1 Add a fan tray.
huawei(config)#emu add 1 fan 0 6 rs485
Step 2 Set whether to report the alarm.

huawei(config-if-fan-1)#fan alarmset block permit
Send command to environment monitor board ,please waiting for the ack...
huawei(config-if-fan-1)#
Execute command successful
huawei(config-if-fan-1)#fan alarmset read_tem_fault permit
huawei(config-if-fan-1)#fan alarmset tem_high permit
huawei(config-if-fan-1)#fan alarmset fault permit
Step 3 Query the configuration parameters.

huawei(config-if-fan-1)#display fan system parameter
EMU ID: 1
Fan configration parameter:
----------------------------------------------------------------------------
fan timing mode: auto timing
----------------------------------------------------------------------------
alarm_name alarm(permit/forbid)
read temperature sensor fault permit
fan block permit
temperature high permit
board fault permit
----------------------------------------------------------------------------

huawei(config-if-fan-1)#quit
huawei(config)#save
----End
Result
After the configuration, the fan tray can work in the normal state, and can adjust the fan speed
automatically. At the same time, the host reports an alarm when the fan fails to read the
temperature sensor, the fan is blocked, the temperature is very high, or the power supply is faulty.
31.4 Configuration Example of the Power Monitoring

This topic considers the Power4875L as an example and describes how to configure its
environment monitoring parameters. The procedures for configuring the Power4875,
Power4845, and Power4820 are the same as the procedure for configuring the Power4875L.
Prerequisite
l The ESC board and host must be connected through the environment monitoring cable.
l The settings of the ESC DIP switch must be consistent with the slave node of the EMU.
l When you add the EMU to the device, you must comply with the following rules:

– The system supports only one type of EMU except the ESCM.
– If the ESCM is added to the system, you can add the other EMU.
Data Plan
This example describes how to configure only the upper and lower alarm thresholds of ambient
temperature and upper and lower measurement thresholds of ambient temperature of the
Power4875L. Other parameters are set by default. For more information about the configurations
of the Power4875L parameters, see "31.12 Setting the Power Supply Parameters." Table
31-3 provides the data plan for configuring the Power4875L.
Table 31-3 Data plan for configuring the Power4875L

Item Data Remarks
EMU Type: Power4875L -
Number: 2 -
Shelf ID: 0 -
Subnode: 15 This parameter corresponds

to the hardware DIP switches
of the ESC, but cannot be the
same as the slave node of the
FAN.
Name: test -
Parameter configuration Upper alarm threshold of Other analog parameters are

ambient temperature: 55 °C set by default.
Lower alarm threshold of

ambient temperature: 5°C
Upper measurement
threshold of ambient
temperature: 100°C
Lower measurement
threshold of ambient
temperature: 0°C
Figure 31-3 shows the flowchart for configuring the Power4875L.

Figure 31-3 Flowchart for configuring the Power4875L
Procedure
Step 1 Add an EMU.
huawei(config)#emu add 2 power4875L 0 15 rs232 test
Step 2 Set the environment monitoring parameters of the power.

huawei(config-if-power4875L-2)#power environment temperature 55 5 100 0
This command is invalid unless in the contition of install the sensor, would
you continue? (y/n)[n]:y
huawei(config-if-power4875L-2)#
Step 3 Query the environment monitoring parameters of the power.

huawei(config-if-power4875L-2)#display power environment parameter
EMU ID: 2 power environment configration parameter
----------------------------------------------------------------------------
AnalogID Name AlmUpper AlmLower TestHigh TestLow Unit type
0 Temperature 55 5 100 0 C Current
1 Humidity 80 10 100 0 %R.H. Current
----------------------------------------------------------------------------
DigitalID Name Available Level|DigitalID Name Available Level
0 - 1 | 1 - 1
2 - 1 | 3 - 1
4 - 1 | 5 - 1
6 - 1
----------------------------------------------------------------------------

huawei(config-if-power4875L-2)#quit
huawei(config)#save
----End
Result
After the configuration, the Power4875L can work in the normal state. At the same time, when
the ambient temperature exceeds the configured upper or lower alarm threshold of ambient
temperature, the host reports an alarm.
31.5 Configuration Example of the Universal Power

Monitoring
This topic describes how to monitor the universal power through the ESC by using the
configuration example of the PSM-A power monitoring through the H303ESC. (The PSM-A is
one type of Emerson power and is displayed as PSMA on the CLI.)
Prerequisite
The settings of the H303ESC DIP switch must be consistent with the slave node of the EMU.
Data Plan
Table 31-4 provides the data plan for configuring the universal power monitoring.
Table 31-4 Data plan for configuring the universal power monitoring
Item Data Remarks
EMU Type: H303ESC -
Number: 0 -
Subnode: 30 The subnode of the

H303ESC is always 30.
Universal power Type: PSM-A (displayed as -

PSMA on the CLI)
Protocol file name: Use the name of the actual

power.pwr loaded protocol file.
Context
The UA5000 mainly uses the following types of the universal power:
l Zhujiang power
l Emerson power
l Beijing dynamic power
l Eltek power

l Delta-cimic power
l Zhongheng power
Figure 31-4 shows the flowchart for configuring the universal power monitoring.
Figure 31-4 Flowchart for configuring the universal power monitoring
Start
Add an EMU
Load the protocol file of

the universal power
Configure the type of the

universal power
Query the ESC

environment information
Save the data
End
Procedure
Step 1 Add an EMU.
Add the EMU with the EMU ID 0, the type H303ESC, the slave node 20, and the serial port
type RS232.
huawei(config)#emu add 0 H303ESC 0 30 rs232 H303ESC
Step 2 Load the protocol file of the universal power.

Obtain the protocol file of the universal power through the TFTP server. Then, run the following
command on the CLI with using the IP address of the actual server.
huawei(config)#load universal-power-protocol tftp 10.144.78.132 power.pwr
Step 3 Configure the type of the universal power.

huawei(config-if-H303ESC-0)#esc power powertype 1
Step 4 Query the ESC environment information.

huawei(config-if-H303ESC-0)#display esc power run info
huawei(config-if-H303ESC-0)#display esc power state


huawei(config-if-H303ESC-0)#quit
huawei(config)#save
----End
Result
After the configuration, the H303ESC works in the normal state, and monitors the universal
power used by the UA5000. When the monitored parameter exceeds the normal range, the host
reports an alarm.
31.6 Adding an EMU

This topic describes how to add an EMU. After connecting the EMU to the monitoring serial
port correctly, you need to add the corresponding EMU to the host system of the UA5000.
Context
The EMU supported by the UA5000 can be classified into the following four categories:
l Environment supervision circuit (ESC): Includes the H302ESC, H303ESC, H304ESC,
H801ESC, and ESCM. Monitors the environment parameters such as temperature,
humidity, smoke, water, fire, voltage, and power through various sensors.
l FAN: Monitors the running status of the fan and adjusts the running speed of the fan
according to the settings.
l DIS: Refers to the power distribution unit (PDU). Divides one or two DC inputs into
multiple outputs.
l Power: Includes the Power4820, Power4845, Power4875, Power4875L, and PSE158.
Monitors the environment parameters such as temperature, humidity, voltage, and power
supply through various sensors.
The serial ports of the preceding EMUs are as follows:
l The serial port type of the H302ESC, H303ESC, H304ESC, Power4820, Power4875,
Power4845, and Power4875L is RS232.
l The serial port types of the ESCM are RS485 and RS232. Select one serial port type during
the configuration according to the type of the monitored shelf.
Procedure
Step 1 Run the emu add command to add an EMU.
Step 2 Run the display emu command to query the status of the EMU.
----End
Example
To add an EMU with the EMU ID 0, the type ESCM (MiniESC on the CLI), the slave node 30,
and the serial port type RS232, do as follows:
huawei(config)#emu add 0 MiniESC 0 30 rs232 MiniESC
huawei(config)#display emu 0

EMU ID: 0
----------------------------------------------------------------------------
EMU name : MiniESC
EMU type : MiniESC
EMU state : Fault
Frame ID : 0
Subnode : 30
COM Port : RS232
----------------------------------------------------------------------------
NOTE
If the status of the EMU is displayed as Fault, check the following points:
l Check whether the physical connection is correct.
l Check whether the EMU type, shelf ID, subnode ID, and communication serial port are configured
correctly.
Related Operation
Table 31-5 lists the related operations for adding an EMU.
Table 31-5 Related operations for adding an EMU
Delete an EMU emu del If the EMU in the shelf needs to be

replaced, you need to delete the
configured EMU, and then add an
EMU.
Change the EMU emu modify The EMU ID must be unique, whereas
name the EMU name can be duplicate.
31.7 Setting the ESC Analog Parameters

This topic describes how to set the upper and lower alarm thresholds of the analog parameters,
such as temperature, humidity, voltage, and current, or how to set the customized alarms of the
analog parameters.
Prerequisite
The EMU must be added and work in the normal state.
Procedure
Step 1 Run the interface emu command to enter the corresponding environment monitoring mode.
Step 2 Run the esc analog command to set the ESC analog parameters.
Step 3 Run the display esc environment info command to query the ESC system analog parameters.
----End

Example
The ESCM (MiniESC on the CLI) is used in the following example. To set the upper temperature
threshold to 55°C, and lower temperature threshold to 5°C, do as follows:
Enter the ESCM config mode.

Set the ESCM analog parameters as follows: set the analog parameter ID to 0, the upper
temperature threshold to 55°C, and the lower temperature threshold to 5°C
5
Query the ESCM system analog parameters.

3 - Normal -128.000 127 -128 -
----------------------------------------------------------------------------
Related Operation
Table 31-6 lists the related operations for setting the ESC analog parameters.
Table 31-6 Related operations for setting the ESC analog parameters
Query the alarm information display esc alarm Only valid for the H302ESC,
H303ESC, H304ESC, and
H801ESC
Query the ESC system display esc system Only valid for the H302ESC,
configuration parameters parameter H303ESC, H304ESC, and
H801ESC
Query the ESC power supply display esc power Only valid for the H302ESC,
information H303ESC, H304ESC, and
H801ESC
Query the customized alarm display outside_analog Only valid for the H302ESC,
information of the analog private-alarm H303ESC, H304ESC,
parameters H801ESC, Power4875,
Power4875L, DIS, and
PSE158

31.8 Setting the ESC Digital Parameters

This topic describes how to set the alarm levels of digital parameters such as the door status
sensor, or how to configure the customized alarms of the digital parameters.
Prerequisite
The EMU must be added and work in the normal state.
Procedure
Step 1 Run the interface emu command to enter the environment monitoring mode.
Step 2 Run the esc digital command to set the ESC digital parameters.
Step 3 Run the display esc environment info command to query the ESC system digital parameters.
----End
Example
The ESCM (MiniESC on the CLI) is used in the following example. To set the alarm of the door
status sensor to high level, do as follows:
Enter the ESCM config mode.

Set the ESCM digital parameters.

huawei(config-if-MiniESC-0)#esc digital 0 available-level high-level
Query the settings of the digital parameters.

3 - Normal -128.000 127 -128 -
----------------------------------------------------------------------------
Related Operation
Table 31-7 lists the related operations for setting the ESC digital parameters.

Table 31-7 Related operations for setting the ESC digital parameters
Query the alarm information display esc alarm Only valid for the H302ESC,
H303ESC, H304ESC, and
H801ESC
Query the ESC system display esc system Only valid for the H302ESC,
configuration parameters parameter H303ESC, H304ESC, and
H801ESC
Query the ESC power supply display esc power Only valid for the H302ESC,
information H303ESC, H304ESC, and
H801ESC
Query the customized alarm display outside-digital Only valid for the H302ESC,
information of the digital private-alarm H303ESC, H304ESC,
parameters H801ESC, Power4875,
Power4875L, DIS, and
PSE158
31.9 Configuring the Fan Alarm Reporting

This topic describes how to configure the reporting of all the fan alarms to the control unit.
Prerequisite
The EMU of the fan tray must be in the position and work in the normal state.
Procedure
Step 1 Run the interface emu command to enter the FAN environment monitoring mode.
Step 2 Run the fan alarmset command to configure the fan alarm reporting.
Step 3 Run the display fan system parameter command to query the fan alarm information.
----End
Example
To forbid the reporting of the fan block alarm, do as follows:
huawei(config-if-fan-1)#fan alarmset block forbid
EMU ID: 1
----------------------------------------------------------------------------
----------------------------------------------------------------------------


fan block forbid
board fault permit
----------------------------------------------------------------------------
Related Operation
Table 31-8 lists the related operations for configuring the fan alarm reporting.
Table 31-8 Related operations for configuring the fan alarm reporting
Query the running display fan environment FAN environment

information of a fan tray info monitoring mode
Query the alarm information display fan alarm FAN environment

of a fan tray monitoring mode
31.10 Setting the Fan Speed Adjustment Mode

This topic describes how to set the fan speed adjustment mode. If the fan is not in the automatic
speed adjustment mode, the flow of air is more when the temperature is low or normal.
Prerequisite
The EMU of the fan tray must be in the position and work in the normal state.
Context
The fan tray of the UA5000 supports the following fan speed adjustment modes:
l Automatic
l Manual
By default, the mode is manual with the fan speed level 5. It is recommended that you change
the mode to automatic.
Procedure
Step 2 Run the fan speed command to set the fan speed adjustment mode.
Step 3 Run the display fan system parameter command to query the set parameters.
----End
Example
To set the fan speed adjustment mode to automatic, do as follows:
huawei(config-if-fan-1)#fan speed mode automatic

EMU ID: 1
----------------------------------------------------------------------------
----------------------------------------------------------------------------
fan block forbid
board fault permit
----------------------------------------------------------------------------
Related Operation
Table 31-9 lists the related operations for setting the fan speed adjustment mode.
Table 31-9 Related operations for setting the fan speed adjustment mode
Set the fan speed fan speed adjust You can set the fan speed in
the manual fan speed
adjustment mode.
Configure the reporting of all fan alarmset -

the fan alarms to the control
unit
Query the alarm information display fan alarm -

of a fan tray
31.11 Setting the Fan Speed

This topic describes how to set the fan speed.
Prerequisite
l The EMU of the fan tray must be in the position and work in the normal state.
l The fan speed adjustment mode must be set to manual.
Context
The fan speed levels are 0, 1, 2, 3, 4, and 5. Level 0 indicates the lowest fan speed and level 5
indicates the highest fan speed.
l The rated fan speed can meet the heat dissipation requirement of the system in the permitted
highest ambient temperature.
l When the fan runs at a low speed, the damage to the fan is reduced and its life is prolonged.
l When the system is abnormal or one fan is faulty, the normal fans can switch to the high
speed to increase the air flow so that the heat is dissipated.

l Reduction of the fan speed reduces the dust absorption and prevents the air filter from being
blocked.
l You can set the fan speed in the manual fan speed adjustment mode.
Procedure
Step 2 Run the fan speed command to set the fan speed.
Step 3 Run the display fan system parameter command to query the set parameters.
----End
Example
To set the fan speed to 3, do as follows:
huawei(config-if-fan-1)#fan speed adjust 3
EMU ID: 1
----------------------------------------------------------------------------
fan timing mode: manual timing
fan speed level: 3
----------------------------------------------------------------------------
fan block forbid
board fault permit
----------------------------------------------------------------------------
Related Operation
Table 31-10 lists the related operations for setting the fan speed.
Table 31-10 Related operations for setting the fan speed

Set the fan speed adjustment mode fan speed mode
Set the reporting of all the fan alarm fan alarmset

information to the control unit
Query the alarm information of a fan tray display fan alarm
31.12 Setting the Power Supply Parameters

This topic describes how to set the parameters of the power shelf in the UA5000 to ensure the
normal running of the power shelf.

Context
Table 31-11 lists the configuration commands of the power shelf.
Table 31-11 Configuration commands of the power shelf

Function Command Remarks
The configuration commands supported by the Power4875, Power4875L, Power4845, and

Power4820 are as follows:
Set the battery parameters power battery Set the charging current-
limiting coefficient, timed
even charging duration,
number, and capacity of the
battery sets.
Set the battery charging power charge Set the battery charging
parameters parameters, including the
charging mode and charging
voltage.
Set the environment power environment Set the upper and lower alarm
parameters of the power thresholds, and upper and
supply lower measurement
thresholds of the temperature
or humidity of the power
supply monitoring. Thus, an
alarm is generated when the
power supply works in the
environment that does not
meet the preset criteria, to
ensure the normal running of
the device.
Set the number of the power power module-num The Power4845 supports a
modules maximum of three rectifier
modules.
Set the parameters of the power module-parameter Set the on and off states of the
power module Power4845. The default state
is on. That is, the power
module is in the working
state.

Set the power-off power off Set the power-off thresholds

parameters of the power of the load and battery set.
supply l The power-off types of
the power supply are the
load power off and the
battery set power off.
l When the mains supply is
cut off, the battery set
supplies the power to the
shelf.
l When the voltage of the
battery set is lower than
the power-off threshold of
the load, the system cuts
off the power supply to
the load.
l When the voltage of the
battery set is lower than
the power-off threshold of
the battery set, the system
cuts off the power supply
to the battery set.
Set the standby digital power outside_digital Set the valid level, name, and
parameters of the power customized alarm of the
supply extended digital parameters
to monitor the digital
parameters of the device in
real time.
Set the power distribution power supply-parameter Set the alarm thresholds of
parameters of the power AC over-voltage, AC under-
supply voltage, DC over-voltage,
and DC under-voltage. Thus,
when the AC voltage or DC
voltage is abnormal, the
rectifier module can power
off automatically to protect
the system.
The configuration commands only supported by the Power4875L, Power4845, and

Set the battery test power battery-test Set the auto-test period
parameters parameter of the battery and
the end voltage of the battery
discharging to implement the
auto-discharging test of the
battery.

Set the high-temperature power temperature-off Set the high-temperature

power-off parameters of the power-off parameter for the
power supply load or battery. Thus, the load
or battery powers off
automatically in the high
working temperature for self-
protection.
The configuration commands only supported by the Power4875 and Power4875L are as
follows:
Set the standby analog power outside_analog Set the upper and lower alarm
parameters of the power thresholds, upper and lower
supply measurement thresholds,
sensor type, unit, name, and
customized alarm of the
analog parameters.
The configuration commands only supported by the Power4875L are as follows:
Set the installation time of power batteryinstall Set the installation time of the
the battery of the battery of the Power4875L
Power4875L system system. Thus, the battery can
be replaced in time when the
battery life expires.
Set certain parameters of the power default When you need to initialize
Power4875L system certain parameters of the
Power4875L system, run this
command.
When you set the parameters, ensure that the following conditions are met:
l DC over-voltage voltage > battery even charging voltage > battery float charging voltage
> DC under-voltage voltage > load power-off voltage > battery power-off voltage
l DC over-voltage > (float charging voltage + 2 V)
l Float charging voltage > (DC under-voltage + 2 V)
NOTE
Run the following commands to set the preceding parameters:

l Run the power charge command to set the even charging voltage and float charging voltage of the
battery.
l Run the power battery parameter command to set the DC over-voltage and under-voltage.
l Run the power temperature-off command to set the load power-off voltage of the battery and the
power-off voltage of the battery set.
Procedure
Step 1 Run the commands listed in Table 31-11 to configure the EMU of the power shelf.
----End

Example
To set the charging current-limiting coefficient to 0.2, timed even charging duration to 60 days,
number of battery sets to 1, and capacity of battery set 0 to 130 AH, do as follows:
huawei(config-if-power4875L-0)#power battery parameter 1 0.2 60 130
huawei(config-if-power4875L-0)#
Related Operation
Table 31-12 lists the related operations for configuring the EMU of the power shelf.
Table 31-12 Related operations for configuring the EMU of the power shelf
The configuration commands supported by the Power4875, Power4875L, Power4845, and

Query the alarm information of display power alarm

the power supply
Query the environment display power environment info

information of the power supply
Query the environment display power environment parameter

configuration parameters of the
power supply
Query the running information of display power run info

the power supply
Query the system configuration display power system parameter

parameters of the power supply
The configuration commands only supported by the Power4845 and Power4875L are as
follows:
Query the battery test parameters display power battery-test info
The configuration commands only supported by the Power4875L are as follows:
Query the installation time of the display power batteryinstalltime

Power4875L battery
Query the current use status of the display power battery-test-times

Power4875L battery
Query the current running time of display power current-time

the Power4875L
Query the system information of display power info

the Power4875L

Query the related information of display power module-time

the Power4875L

Configuration Guide-PVM CLI 32 Configuring the Integrated Data and Voice Networking
32 Configuring the Integrated Data and

Voice Networking
About This Chapter
This topic describes the related operation for configuring the integrated data and voice
networking of the UA5000.
32.1 Networking
The UA5000 accesses the data and voice service through the CSRI and ETDB boards. It transmits
the IP service upstream to the IP network through the IPM board, and transmits the traditional
voice service to the PSTN network through the PVM board.
32.2 Prerequisites
Before configuring the integrated data and voice networking, ensure that the UA5000 meets the
configuration prerequisites.
32.3 Data Plan (IPM)
Before the configuration, it is recommended that you implement the service data plan for the
required broadband services such as the ADSL access service and the SHDSL access service.
When configuring the service, configure according to the planned data.
32.4 Data Plan (PVM)
required voice services such as the ISDN service. When configuring the service, configure
according to the planned data.
32.5 Configuration Procedure (IPM)
Log in to the IPM through the serial port or the Telnet mode to configure the broadband services
of the UA5000 according to the planned broadband service data.
32.6 Configuration Procedure (PVM)
Log in to the PVM through the serial port or the Telnet mode to configure the narrowband
services of the UA5000 according to the planned voice service data.
32.7 Verification

After the broadband service is configured successfully, the subscribers should be able to access
the Internet through their PCs. After the voice service is configured successfully, the subscribers

32.1 Networking
The UA5000 accesses the data and voice service through the CSRI and ETDB boards. It transmits
the IP service upstream to the IP network through the IPM board, and transmits the traditional
voice service to the PSTN network through the PVM board.
Figure 32-1 shows the integrated data and voice networking of the UA5000.
Figure 32-1 Integrated data and voice networking of the UA5000
OSS
NMS
DHCP Server
MGC IPTV
Server
BRAS Router
V5
00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17
P P I I P P C C S S E E D E T
W W P P V V S S D D D D S D S
X X M M M M R R L L T T L T S
B B B B B B I I B B B B D B B
Splitter NT1 PBX
phone ISDN ISDN phone phone

Phone Phone
STB
PC TV
32.2 Prerequisites
Before configuring the integrated data and voice networking, ensure that the UA5000 meets the
configuration prerequisites.

The prerequisites for configuring the integrated data and voice networking of the UA5000 are
as follows:
l The hardware commissioning must be complete, and the system must be ready for service
configuration.
l The modem must be connected and must be in the normal state.
l The upper layer devices, including the BRAS, DHCP sever, multicast sever, MGC, and
NMS workstation must work in the normal state.
32.3 Data Plan (IPM)

required broadband services such as the ADSL access service and the SHDSL access service.
When configuring the service, configure according to the planned data.
Table 32-1 provides the data plan for configuring the integrated data and voice networking of
the UA5000.
Table 32-1 Data plan for configuring the integrated data and voice networking
Item Data Remarks
Upstream port Port number: 0/2/0; Rate: 100 Mbit/s; Flow If the upstream port is a
control switch state: enabled GE port, use the default
configuration.
Inband NMS NM VLAN ID: 31; type: standard The inband NMS
manages the PVM
IP address of the L3 interface: 10.5.24.3 board through the
IP address of the next hop router: 10.5.24.2 packet transmission of
the IPM board.
IP address of the NMS host: 10.140.5.79
l Community name: public, with the -

read-only right.
l Community name: private, with the
read-write right.
l Enable the standard SNMP trap
message.
ADSL service Subscriber access port number: 0/7/0– -

0/7/31
VPI: 8; VCI: 35
VLAN ID: 32-63; type: Mux
Traffic profile: Upstream bandwidth 512

kbit/s, downstream bandwidth 1 Mbit/s
Upstream port: 0/2/0
Traffic entry priority: 1

Item Data Remarks
SHDSL service Subscriber access port number: 0/8/0– -

0/8/15
VPI: 8; VCI: 35
VLAN ID: 64-79; type: Mux
Traffic profile: 1 Mbit/s
Upstream port: 0/2/0
Multicast service VLAN ID: 104; type: Smart The multicast service
uses the DHCP mode to
Subscriber access port number: 0/7/0– obtain the IP address.
0/7/31 The priority of the
VPI: 0; VCI: 35 multicast traffic entry is
higher than the priority
Upstream port: 0/2/0 of the Internet access
subscriber.
IP address of the L3 interface: 10.2.2.1
IP addresses of the DHCP server: 10.2.2.2,

10.2.2.3
IP address of the multicast program:

224.1.1.1
Right profile name: profile0
Program name: program1
Traffic entry priority: 5
Internet access mode xDSL service: VPI 8, VCI 35, PPPoE The xDSL services use
mode, set the modem to the bridge mode. the PC dialing method.
If the modem dialing
Multicast service: VPI 0, VCI 35, IPoE method is required, set
mode, set the modem to the bridge mode. the modem to the
bridged PPPoE mode.
32.4 Data Plan (PVM)

required voice services such as the ISDN service. When configuring the service, configure
according to the planned data.
Table 32-2 provides the data plan for configuring the integrated data and voice networking of
the UA5000.

Table 32-2 Data plan for configuring the integrated data and voice networking
Item Data
MG interface mgid: 0
code: text
Protocol: H.248
MG port: 2944; MGC: 2944
Whether the termination ID on the MG interface supports the

layering configuration: Yes
System parameter Overseas version flag: Britain
IP address Signaling IP address of MG interface 0 of the UA5000:

10.140.24.10/24
Media IP address of MG interface 0 of the UA5000:

10.140.24.10/24
Default gateway of MG interface 0 of the UA5000:

10.140.24.1/24
IP address of the MGC: 10.140.25.10/24
(Optional)Type of IP priority and ToS priority: Default values

service (ToS) strategy
ISDN BRA service IUA IUA link set number: 1

link parameters
IUA link number: 15
Local port number: 1401
Peer port number: 1400
ISDN PRA service IUA IUA link set number: 2

link parameters
IUA link number: 1
Local port number: 1402
Peer port number: 1404
32.5 Configuration Procedure (IPM)

Log in to the IPM through the serial port or the Telnet mode to configure the broadband services
of the UA5000 according to the planned broadband service data.
Procedure
Step 1 Query the host software version.
huawei(config)#display language

NOTE
If the queried host version does not match the planned host version, see the upgrade guide to update the
host software to the planned version.
Step 2 Query and confirm the board.

huawei(config)#board confirm 0
Step 3 Set the upstream port of the UA5000.

huawei(config)#interface ipm 0/2
huawei(config-if-ipm-0/2)#speed 0 100
huawei(config-if-ipm-0/2)#flow-control 0
huawei(config-if-ipm-0/2)#quit
Step 4 Configure a log host.

huawei(config)#loghost add 10.188.56.40 syslog-1
huawei(config)#loghost activate ip 10.188.56.40
huawei(config)#loghost add 10.188.57.40 syslog-2
huawei(config)#loghost activate ip 10.188.57.40
Step 5 Add a standard VLAN, and assign FE ports 6 and 7 and IP upstream port 0 to the VLAN.
Step 6 Configure the inband NMS.

huawei(conffig-if-vlanif31)#ip address 10.5.24.3 255.255.255.0
huawei(conffig-if-vlanif31)#quit
huawei(config)#ip route-static 0.0.0.0 0.0.0.0 10.5.24.2
huawei(config)#snmp-agent target-host trap address 10.140.5.79 securityname
private
huawei(config)#snmp-agent trap source vlanif 31
Step 7 Configure the ADSL service.

huawei(config)#vlan 32 to 63 mux
huawei(config)#port vlan 32 to 63 0/2 0
huawei(config)#display traffic table from-index 0
huawei(config)#traffic table index 7 ip car 10240 priority 1 priority-policy tag-In-
Package
huawei(config)#service-port vlan 32 adsl 0/7/0 vpi 8 vci 35 rx-cttr 7 tx-cttr 7


huawei(config)#adsl line-profile add 3
Command:
adsl line-profile add
3
Start adding
profile
Press 'Q' to quit the current configuration and new configuration will be
neglected
> Do you want to name the profile (y/n)
[n]:
> Please choose default value type 0-adsl 1-adsl2+ (0~1)
[0]:
> Will you set basic configuration for modem? (y/n)[n]:
> Please select channel mode 0-interleaved 1-fast (0~1) [0]:
> Will you set interleaved delay? (y/n)
[n]:
> Please select form of transmit rate adaptation in downstream:
> 0-fixed 1-adaptAtStartup 2-adaptAtRuntime (0~2) [1]:1
> Will you set SNR margin for modem? (y/n)[n]:y
> Target SNR margin in downstream(0~15 dB) [6]:
> Minimum SNR margin in downstream (0~6 dB) [0]:
> Maximum SNR margin in downstream (6~31 dB) [31]:
> Target SNR margin in upstream (0~15 dB) [6]:
> Minimum SNR margin in upstream (0~6 dB)
[0]:
> Maximum SNR margin in upstream (6~31 dB) [31]:
> Will you set parameters for rate? (y/n)[n]:y
> Minimum transmit rate in downstream (32~8160 Kbps) [32]:
> Maximum transmit rate in downstream (32~8160 Kbps) [6144]:1024
> Minimum transmit rate in upstream (32~896 Kbps)
[32]:
> Maximum transmit rate in upstream (32~896 Kbps) [640]:512
Add profile 3 successfully
huawei(config)#interface adsl 0/7
huawei(config-if-adsl-0/7)#alarm-config all 1
huawei(config-if-adsl-0/7)#deactivate all
huawei(config-if-adsl-0/7)#activate all profile-index 3
Step 8 Configure the SHDSL service.

huawei(config)#vlan 64 to 79 mux
huawei(config)#port vlan 64 to 79 0/2 0
huawei(config)#display traffic table from-index 0
huawei(config)#service-port vlan 64 shdsl 0/8/0 vpi 8 vci 35 rx-cttr 6 tx-cttr 6


huawei(config)#shdsl line-profile add 2
Command:
shdsl line-profile add
Start adding profile 2
During inputting,press 'Q' to quit,then settings at this time will be ignored
> G.SHDSL interface mode of line (1--two wire;2--four wire)
[1]:
> Do you use the default data to create a line profile?(y/n)
[y]:n
> G.SHDSL minimum line
rate
(Value must be multiple of 64,except 2312kbps,192~2304,2312 kbps)[2048]:1024
> G.SHDSL maximum line
rate
(Value must be multiple of 64,except 2312kbps,1024~2304,2312 kbps)[2048]:
1024
> Power Spectral Density mode (1--symmetric;2--asymmetric)
[1]:
> Transmission mode (1--G.991.2 Annex A;2--G.991.2 Annex
B;
3--support Annex A&B)
[3]:
> Remote enable (1--enabled;2--disabled)
[1]:
> Probe enable (1--disabled;2--enabled)
[1]:
> Do you config the target SNR margin?(y/n)
[n]:
Add profile 2 successfully
huawei(config-if-sdl-0/7)#alarm-config all 1
huawei(config-if-sdl-0/7)#deactivate all
huawei(config-if-sdl-0/7)#activate all 2
Step 9 Configure the multicast service.

huawei(config)#vlan 104 smart
huawei(config)#traffic table index 8 ip car 10240 priority 5 priority-policy tag-In-
Package


huawei(config)#dhcp mode layer-3 option-60
huawei(config)#dhcp-server 2 ip 10.2.2.2 10.2.2.3
huawei(config)#dhcp domain video //Refer to the actual DHCP option 60 threshold.
huawei(config-dhcp-domain-video)#dhcp-server 2
huawei(config-if-vlanif104)#ip address 10.2.2.1 24
huawei(config-if-vlanif104)#dhcp domain video gateway 10.2.2.1
huawei(config)#interface ipm 0/2
huawei(config-if-ipm-0/2)#native-vlan 0 vlan 104
huawei(config-if-ipm-0/2)#quit
huawei(config)#btv
huawei(config-btv)#igmp uplink-port 0/2/0
huawei(config-btv)#igmp video-port vpi 0 vci 35
huawei(config-btv)#igmp program add name program1 ip 224.1.1.1 vlan 104 bind 0/2/0
huawei(config-btv)#igmp profile profile0 program-name program1 watch
huawei(config-btv)#igmp user add slot 0/7 auth
huawei(config-btv)#igmp user bind-profile slot 0/7 profile-name profile0
Step 10 Configure the Internet access mode (configure the modem).

l PPPoE mode
– Set the modem to the bridge mode.
– Set the VPI/VCI of the WAN port on the modem to 8/35.
– Install the PPPoE dialup software on the computer terminal, and set the user name and
password.
l IPoE mode
– Set the modem to the bridge mode.
– Set the VPI/VCI of the WAN port on the modem to 0/35.
----End
32.6 Configuration Procedure (PVM)

Log in to the PVM through the serial port or the Telnet mode to configure the narrowband
services of the UA5000 according to the planned voice service data.
Procedure
Step 1 Configure the system networking mode to the integrated access networking.
huawei(config)#working mode integrated
Step 2 Query the host software version.

huawei(config)#display language
NOTE
If the version does not match, see the version upgrading guide to update the host software to a proper
version.
Step 3 Set the IP address of service network port.

huawei(interface-eth)#ip address 10.140.24.10 255.255.255.0 10.140.24.1 vlan_tag
1001

Step 4 Configure the QoS IP strategy.

Step 5 Configure the overseas version flag.

huawei(config)#display system parameters 1
Step 6 Configure the VoIP voice service.

huawei(config-if-h248-0)#if-h248 attribute mgip 10.140.24.10 mgport
2944 code text transfer udp domainName UA5000.com mgcip_1 10.140.25.10
mgcport_1 2944 mg-media-ip 10.140.24.10 start-nego tiate-versi 2
huawei(config-if-h248-0)#reset
huawei(config-esl-user)#mgpstnuser batadd 0/6/0 0/6/31 0 telno 12340001
huawei(config)#save
Step 7 Configure the ISDN BRA service.

huawei(config)#board add 0/12 h601dsld
huawei(config-sigtran)#iua-linkset add 1 0 pendingtime 4
huawei(config-esl-user)#mgbrauser batadd 0/12/0 0/12/1 1 15
huawei(config-esl-user)#display port state 0/12
huawei(config-esl-user)#display mgbrauser 0/12
huawei(config)#save
Step 8 Configure the ISDN PRA service.

huawei(config-sigtran)#iua-linkset add 2 0 pendingtime 4
huawei(config-esl-user)#mgprauser add 0/15/0 2 10
huawei(config-esl-user)#display mgprauser 0/15
huawei(config)#save
----End

32.7 Verification
After the broadband service is configured successfully, the subscribers should be able to access
the Internet through their PCs. After the voice service is configured successfully, the subscribers

Configuration Guide-PVM CLI A Acronyms and Abbreviations
A Acronyms and Abbreviations
A
ADSL asymmetric digital subscriber line
AG access gateway
B
BE best effort
BRA basic rate access
BRI basic rate interface
C
CCS common channel signaling
CCITT International Telegraph and Telephone Consultative
Committee
CLI command line interface
D
DNS domain name server
DSL digital subscriber line board
DSCP differentiated service codepoint
DSP digital signal processor
DTMF dual-tone multifrequency

EPON Ethernet passive optical network
F
FE fast Ethernet
FoIP fax over IP
FSK frequency shift keying
FTP File Transfer Protocol
G
GE gigabit Ethernet
GPON Gigabit-capable Passive Optical Network
H
HW highway
I
IP Internet Protocol
ISDN integrated services digital network
IUA ISDN Q.921-User Adaptation Layer
M
MAC media access control
MDU multi dwelling unit
MG media gateway
MGC media gateway controller
MGCP Media Gateway Control Protocol
MoIP modem over IP
N
NGN next generation network
NM network management
NMS network management system

NT1 network termination 1
O
OAM operations, administration and maintenance
OLT optical line terminal
ONU optical network unit
P optical network unit

PBX private branch exchange
PCM pulse code modulation
POS passive optical splitter
POTS plain old telephone service
PRA primary rate access
PRI primary rate interface
PSTN public switched telephone network
PVM packet voice module
Q
QoS quality of service
R
RTP Real-time Transfer Protocol
S
SCTP Stream Control Transmission Protocol
SIGTRAN signaling transport
SNMP Simple Network Management Protocol
T
TCP Transmission Control Protocol
TFTP Trivial File Transfer Protocol

U
UDP User Datagram Protocol
V
VAG virtual access gateway
VLAN virtual local area network
VoIP voice over IP
VQE voice quality enhancements

UA5000 Configuration Guide PVM CLI V100R017 08 PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

UA5000 Configuration Guide PVM CLI V100R017 08 PDF

Загружено:

Авторское право:

Доступные форматы

UA5000 Universal Access Unit

Configuration Guide-PVM CLI

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 08 (2011-11-15) Huawei Proprietary and Confidential i

About This Document

Product Name Version

N2000 BMS V200R011

l Installation and commissioning engineer

Issue 08 (2011-11-15) Huawei Proprietary and Confidential ii

9 Configuring the MG How to configure an MG interface.

15 Configuring the R2 How to configure the R2 access.

16 Configuring the V5 How to configure the V5 voice service.

Issue 08 (2011-11-15) Huawei Proprietary and Confidential iii

17 Configuring the SPC How to configure the SPC.

18 Configuring the DDI How to configure the DDI service.

19 Configuring the SDL How to configure the SDL service.

20 Configuring the MTA How to configure the MTA service.

21 Configuring the VFB How to configure the VFB service.

22 Configuring the ATI How to configure the ATI service.

23 Configuring the CDI How to configure the CDI service.

26 Configuring the Remote How to configure the remote subtending.

29 Configuring the Configuring the Reliability of the Voice Service.

31 Configuring the This topic provides an overview of the environment

Acronym and Abbreviation Acronyms and abbreviations used in the document.

Issue 08 (2011-11-15) Huawei Proprietary and Confidential iv

Indicates a hazard with a high level of risk, which if not

Indicates a hazard with a medium or low level of risk, which

Indicates a potentially hazardous situation, which if not

NOTE Provides additional information to emphasize or supplement

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are in boldface.

Italic Book titles are in italics.

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italic.

[] Items (keywords or arguments) in square brackets [ ] are

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

Issue 08 (2011-11-15) Huawei Proprietary and Confidential v

[ x | y | ... ] Optional alternative items are grouped in square brackets and

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

> Multi-level menus are in boldface and separated by the ">"

Issue 08 (2011-11-15) Huawei Proprietary and Confidential vi

Updates in Issue 08 (2011-11-15)

Updates in Issue 07 (2010-10-30)

Updates in Issue 06 (2010-05-30)

Updates in Issue 05 (2009-04-30)

Updates in Issue 04 (2008-11-20)

Issue 08 (2011-11-15) Huawei Proprietary and Confidential vii

Updates in Issue 03 (2008-08-20)

Updates in Issue 02 (2008-05-20)

Updates in Issue 01 (2008-03-25)

Issue 08 (2011-11-15) Huawei Proprietary and Confidential viii

About This Document.....................................................................................................................ii

2 Configuring the Maintenance Terminal...................................................................................9

3 CLI Operation Basics..................................................................................................................26

Issue 08 (2011-11-15) Huawei Proprietary and Confidential ix

3.3.8 Clearing the Terminal Screen..................................................................................................................39

4 Configuring the NMS.................................................................................................................42

7 Configuring the System DSP Channels..................................................................................74

8 Configuring the Clock................................................................................................................83

Issue 08 (2011-11-15) Huawei Proprietary and Confidential x

8.1 Introduction to the Clock..................................................................................................................................84