TopEng IPCC Deployment Guide V1.6

For internal use only
TopEng IPCC Deployment Guide
Document code
Product name
Target readers
Deployment engineers
Product version
Edited by
Application and Software Business

Support System & Operation
Support System Product Service
Department
Document
version
IPCC
V1.6

Drafted by
Liu Jintao
Date
Reviewed by
Zhang Chunhe
Date
Reviewed by
Approved by
2007-11-02
Date
Zhang Chunhe
Date
Huawei Technologies Co., Ltd.

All Rights Reserved.
Huawei Confidential. No disclosure without permission.
Revision History
Date
Version
Description
Author
2007-11-02
V1.0
The initial draft is complete.
Liu Jintao
2008-01-07
V1.1
1. The version configuration table of the product

is updated.
2. The content in section 3.8Connection of the
Alarm Box is modified.
3. The content in section 3.4Configuration of the
LanSwitch is modified.
4. The method for setting customer levels on the
platform is added.
5. The configuration of the two-stage dialing
voice is described.
6. The problem that calls are abnormal after the
E100 is used for NAT conversion is described.
7. The commands for setting workstation
licenses are added.
8. The SBC configuration is modified, and more
details are added.
9. The parameter configuration part is modified.
10.Notes are added to some configuration
commands.
11.The section 5.7"Configuring Echo
Cancellation" is added.
12.The chapter 6"Self-Check and Test" is
modified.
Liu Jintao
2008-02-13
V1.2
1. The MGC clock cable connection is described.

2. It is stressed that the active CLK board of the
MGW must be located in the slot 1.
3. The TTS configuration part is added.
4. The SBC side connection is described.
5. The MSU configuration is described.
Liu Jintao
2008-03-21
V1.3
1. The processes for applying for the licenses of

the software such as the platform software, FP
software, ASR software, Openeye software,
SysPatron software, and system customization
tool software.
2. The SBC configuration is updated, and the
HRP configuration is added.
3. MSU configuration instances are added.
4. The description of IVR configuration items is
modified.
Liu Jintao
Date
Version
Description
Author
2008-06-10
V1.4
1. The IPCC version configuration table is

updated.
2. The description of the mapping relations
between the DIP switches on the ERI board
and the E32 frame format is updated.
3. The platform configuration in section
3.4Configuration of the LanSwitch is
modified.
4. The description of data preparations and
configuration relations in MGC data
configuration is modified.
5. The setting of the MGC or MGW command
timeout interval is described.
6. The loading of SPT grammar packages in
multiple languages for the deployment in the
countries outside the Chinese mainland is
described.
7. The description of the MGC parameter
configuration is modified, and the parameters
whose values must be modified are stressed.
8. The mute operations and the prompt tone for
notifying agents of incoming calls are
described.
9. Key points during the data loading of the
UAP8100 MGC and MGW are added.
10.The IPCC service scenario tests, voice quality
tests, and pressure tests are described.
Liu Jintao
2008-08-10
V1.5

updated.
2. The description of the MGW FAN DIP
switchs configuration is added;
3. The description of the new commands about
MGW is added;
4. The description of the fileserver configuration
in B053 version is added.
Liu Jintao
2008-11-29
V1.6

updated.
2. The description of the SBC configuration is
added.
3. The description of VRB Fileserver
Configuration is modified;
4. The MGW frame cascading configuration is
deleted.
5. The description of MGW IP bearing command
is modified.
Liu Jintao
Contents
1 Overview of the IPCC System.........................................................1
1.1 Architecture of the IPCC System.......................................................................................................................1
1.2 Application of the UAP8100 in the IPCC System.............................................................................................3
1.2.1 Narrowband ACD.....................................................................................................................................3
1.2.2 Packet ACD..............................................................................................................................................4
1.2.3 ACD with the Integrated Configuration of Broadband and Narrowband Services..................................6
1.3 Typical Networking of the IPCC System...........................................................................................................6
2 Preparation for the Deployment.....................................................8

2.1 Planning the Signaling Network........................................................................................................................8
2.2 Planning the TCP/IP Network..........................................................................................................................12
2.2.1 Planning of UAP8100 Networking.........................................................................................................12
2.2.2 Planning of IPCC Networking................................................................................................................16
2.2.3 Device Type and Device List..................................................................................................................19
2.2.4 Planning of Multimedia User Data.........................................................................................................21
2.3 Checking Software Versions............................................................................................................................22
2.4 Application of Software Licenses....................................................................................................................23
2.4.1 Applying for a License of the ICD Platform..........................................................................................23
2.4.2 Applying for a License of the FP............................................................................................................23
2.4.3 Applying for a License of the ASR Software.........................................................................................23
2.4.4 Applying for a License of the OpenEye Software..................................................................................24
2.4.5 Applying for Licenses of the SysPatron Software and System Customization Tool..............................24
3 Hardware Installation..................................................................26
3.1 UAP8100 Hardware Installation......................................................................................................................26
3.1.1 Overview of the UAP8100 MGC Hardware..........................................................................................26
3.1.2 Overview of the UAP8100 MGW..........................................................................................................28
3.1.3 General Process of Installing the UAP8100 Hardware..........................................................................29
3.2 Installation of the Core Server on the CTI Platform........................................................................................30
3.3 Installation of the Storage Hardware on the File Server..................................................................................31
3.4 Configuration of the LanSwitch......................................................................................................................32
3.5 Installation of the SBC.....................................................................................................................................34
3.6 Configuration of the DIP Switches of Devices Before the UAP8100 Is Powered On....................................34
3.6.1 Mapping Between Device Numbers and Frame Numbers of the MGC.................................................34
3.6.2 Configuration of MGW Frame Numbers...............................................................................................36

3.6.3 Description of the DIP Switchs of a FAN Box.......................................................................................36
3.6.4 Description of the DIP Switchs of an EPI Board...................................................................................37
3.6.5 Description of the DIP Switches of an ERI Board.................................................................................37
3.6.6 Description of the DIP Switches of an E32 Board.................................................................................38
3.7 Points for Attention When Installing the UAP8100 Hardware........................................................................41
3.8 Connection of the Alarm Box..........................................................................................................................44
3.8.1 Overview of the Alarm Box....................................................................................................................44
3.8.2 Connection of the UAP8100 MGC and the Alarm Box.........................................................................45
3.8.3 Connection of the UAP8100 MGW and the Alarm Box........................................................................48
4 Software Installation...................................................................55
4.1 Software Installation of the UAP8100 MGC...................................................................................................55
4.1.1 Loading Data to Boards..........................................................................................................................58
4.1.2 Loading BIOS Files to Boards................................................................................................................63
4.1.3 Key Points During the Data Loading of the UAP8100 MGC................................................................70
4.1.4 Typical Cases..........................................................................................................................................71
4.2 Software Installation of the UAP8100 MGW..................................................................................................72
4.2.1 Overview................................................................................................................................................72
4.2.2 Loading Software to the OMU Manually...............................................................................................73
4.2.3 Loading Software to UAP8100 MGW...................................................................................................80
4.2.4 Key Points in Loading Software to UAP8100 MGW............................................................................81
4.3 Software Installation of the CTI3.4 Platform..................................................................................................82
4.4 Software Installation of the File Server...........................................................................................................82
4.5 Installation of the OpenEye Software..............................................................................................................83
4.6 Installation and Configuration of a TTS Server...............................................................................................83
4.7 Upgrading the SBC..........................................................................................................................................86
5 Data Configuration......................................................................87
5.1 Basic Rules for Configuring the UAP8100 Data.............................................................................................87
5.1.1 Purpose...................................................................................................................................................87
5.1.2 Configuration Rules................................................................................................................................88
5.2 UAP8100 MGC Data Configuration Procedure..............................................................................................89
5.2.1 Configuration Procedure.........................................................................................................................89
5.2.2 Configuring Hardware Data...................................................................................................................89
5.2.3 Configuring Local Exchange Data.........................................................................................................93
5.2.4 Configuring Charging Data....................................................................................................................96
5.2.5 Configuring Clock Data..........................................................................................................................98
5.2.6 Configuring Media Gateway Data........................................................................................................103
5.2.7 Configuring Signaling Data..................................................................................................................105
5.2.8 Configuring Routing Data....................................................................................................................118
5.2.9 Configuring Trunk Data........................................................................................................................122
5.2.10 Configuring Number Analysis Data...................................................................................................130
5.2.11 Configuring Resource Data................................................................................................................133

5.2.12 Configuring TTS Service Data...........................................................................................................147
5.2.13 Configuring IPCC Service Data.........................................................................................................152
5.2.14 Configuring Parameters......................................................................................................................154
5.2.15 Other Configurations on the MGC.....................................................................................................156
5.3 MGW Data Configuration.............................................................................................................................158
5.3.1 Procedure for Configuring MGW Data................................................................................................158
5.3.2 Configuring Hardware Data.................................................................................................................159
5.3.3 Configuring Data for the Connection to the MGC...............................................................................162
5.3.4 Configuring Signaling Link Data.........................................................................................................164
5.3.5 Configuring Bearing Data....................................................................................................................166
5.3.6 Configuring Clock Data........................................................................................................................171
5.3.7 Configuring Narrowband Call Hold Tone............................................................................................174
5.3.8 Other Configurations on the MGW......................................................................................................174
5.4 Configuring the CTI3.4 Platform...................................................................................................................175
5.4.1 Differences in Configuring the CTI3.4 Platform and the CTI3.2 Platform..........................................175
5.4.2 Changing the Setting Mode of the User Class......................................................................................177
5.4.3 Configuring and Loading a Tone File...................................................................................................178
5.4.4 Configuring Mute Operation and Incoming Call Prompt for the Agent...............................................179
5.5 Configuring Network Device Data................................................................................................................180
5.5.1 Configuring LAN Switch Data.............................................................................................................180
5.5.2 Configuring SBC Data..........................................................................................................................181
5.6 Configuring External VP/FP Data.................................................................................................................187
5.6.1 Overview..............................................................................................................................................187
5.6.2 Precautions............................................................................................................................................187
5.6.3 Configuring the Data on External VP/FP Connected to a UAP8100...................................................190
5.7 Configuring Echo Cancellation......................................................................................................................191
5.7.1 EC-Related Settings on the UAP8100 MGW.......................................................................................191
5.7.2 EC-Related Settings on the UAP8100 MGC........................................................................................191
5.7.3 EC-Related Settings on the No.7 Trunk Group....................................................................................191
5.7.4 EC-Related Settings on the OpenEye Terminal....................................................................................191
5.7.5 Precautions in Enabling EC..................................................................................................................192
6 Self-Check and Test...................................................................193

6.1 Checking the Hardware and Software of the UAP8100................................................................................193
6.1.1 Checking the Hardware of the UAP8100.............................................................................................193
6.1.2 Checking the Software Versions of the UAP8100................................................................................193
6.1.3 Checking Configurations......................................................................................................................195
6.1.4 Checking the Running of Devices........................................................................................................195
6.1.5 Checking Trunks...................................................................................................................................196
6.1.6 Checking the UAP8100 Using the Automatic Inspection Tool............................................................196
6.1.7 Checking the File Server Using the Automatic Inspection Tool..........................................................196
6.2 Checking External Resources........................................................................................................................197

6.2.1 Checking the Versions of the External VP and FP...............................................................................197
6.2.2 Checking the VP and FP Using the Automatic Inspection Tool...........................................................197
6.3 Checking the CTI Platform............................................................................................................................197
6.3.1 Checking the Version of the CTI Platform...........................................................................................197
6.3.2 Checking the CTI Platform Using the Automatic Inspection Tool.......................................................197
6.4 Testing the Service Scenarios of the IPCC System........................................................................................198
6.5 Testing the Voice Quality of the IPCC System..............................................................................................198
6.6 Pressure Test for the IPCC System................................................................................................................198
6.7 Quality Standards and Checklists for Self-checks.........................................................................................199
7 Appendix..................................................................................200
7.1 Configuration Instance Script for IPCC Service Applications (VRB Resource Board)................................200
7.1.1 Card Layout of the UAP8100 Hardware..............................................................................................200
7.1.2 MGC Configuration Instance...............................................................................................................201
7.1.3 MGW Configuration Instance..............................................................................................................204
7.2 Configuration Instance Script for IPCC Service Applications (MSU Resource Board)...............................207
7.2.1 Card Layout of the UAP8100 Hardware..............................................................................................207
7.2.2 MGC Configuration Instance...............................................................................................................207
7.3 Configuration Instance of M2UA Signaling..................................................................................................211
7.4 Common Analysis and Positioning Tools......................................................................................................211
7.5 Usage Instructions for Message Tracing........................................................................................................211
7.6 Acceptance Documents..................................................................................................................................212
7.7 Network Protocol Analysis Tool....................................................................................................................212
Figures
Figure 1-1 IPCC networking with the integrated configuration of broadband and narrowband services..............2
Figure 1-2 Networking diagram of the narrowband ACD......................................................................................4
Figure 1-3 Networking diagram of the packet ACD...............................................................................................5
Figure 1-4 Typical networking of the IPCC system................................................................................................6
Figure 2-1 Physical networking for the connection between the UAP8100 and No.7 signaling.........................10
Figure 2-2 Physical networking for the connection between the UAP8100 and No.7 signaling (M2UA-MTP). 11
Figure 2-3 TCP/IP networking of the UAP8100...................................................................................................14
Figure 2-4 IPCC networking diagram...................................................................................................................16
Figure 2-5 UAP8100 external bearer networking diagram...................................................................................18
Figure 3-1 Structure of an OSTA-based frame.....................................................................................................27
Figure 3-2 Front view of an MGC frame..............................................................................................................28
Figure 3-3 Front view of the MGW frame............................................................................................................28
Figure 3-4 Front view of the SSM-256 frame.......................................................................................................29
Figure 3-5 General process of installing the UAP8100 hardware........................................................................30
Figure 3-6 Cable connection between the disk array and the server....................................................................31
Figure 3-7 Cable connection between the disk array extension frame and the control frame..............................32
Figure 3-8 Rear view of the fan frame of an old MGW.......................................................................................42
Figure 3-9 Rear view of the fan frame of a new MGW........................................................................................43
Figure 3-10 Appearance of the alarm box.............................................................................................................44
Figure 3-11 Interfaces of the alarm box................................................................................................................45
Figure 3-12 Setting the UAP8100 MGC serial port.............................................................................................47
Figure 3-13 Two modes for connecting the UAP8100 MGW and the alarm box................................................48
Figure 3-14 Contents displayed when the alarm box is successfully connected..................................................51
Figure 4-1 Procedure of installing the software of the UAP8100 MGC..............................................................56
Figure 4-2 Typing the device number...................................................................................................................57
Figure 4-3 Procedure of loading software and data to the host through the BAM...............................................58
Figure 4-4 Loading path diagram..........................................................................................................................61

Figure 4-5 Procedure for installing software on the UAP8100 MGW.................................................................73
Figure 4-6 Procedure for loading software to the OMU manually.......................................................................74
Figure 4-7 Connection between the OMU and the LMT......................................................................................75
Figure 4-8 Process of installing board service software.......................................................................................81
Figure 5-1 General flow of configuring the data in the UAP8100 MGC.............................................................89
Figure 5-2 Relations between data tables.............................................................................................................92
Figure 5-5 Overall clock system structure............................................................................................................98
Figure 5-6 Clock synchronization when the UAP8100 MGC locks the peer clock signal.................................100
Figure 5-7 Clock connection between EPI and CKI in the basic frame in the UAP8100 MGC........................101
Figure 5-8 Clock synchronization when the peer device locks the clock signal of the UAP8100 MGC...........102
Figure 5-9 Typical signaling networking of the UAP8100 MGC.......................................................................105
Figure 5-10 Relations between data tables.........................................................................................................109
Figure 5-11 Relations between data tables..........................................................................................................113
Figure 5-12 Relations between data tables..........................................................................................................116
Figure 5-14 Typical trunk networking of the UAP8100 MGC...........................................................................122
Figure 5-18 Flow chart for configuring VRB office direction data....................................................................135
Figure 5-20 The change of the fileserver configuration......................................................................................144
Figure 5-22 General procedure for configuring the UAP8100 MGW data........................................................159
Figure 5-23 Procedure for configuring data for the connection to the MGC.....................................................162
Figure 5-24 Relations between the key parameters in configuration commands...............................................163
Figure 5-25 Typical signaling networking of the UAP8100 MGW....................................................................165
Figure 5-26 Structure of the clock system..........................................................................................................172
Figure 5-27 Configuring the media server..........................................................................................................175
Figure 5-28 Configuring agent ID announcement in a queue.............................................................................176
Figure 5-29 Configuring the setting mode of the user class in the VDN............................................................177
Figure 5-30 Configuring the two-stage dialing voice.........................................................................................178
Figure 5-31 Configuring the incoming call prompt for an agent........................................................................180
Figure 5-32 Networking in the case of SBC side connection.............................................................................187
Figure 5-33 Audio settings on an OpenEye terminal..........................................................................................192
Figure 7-1 MGC card layout...............................................................................................................................200
Figure 7-2 MGW card layout..............................................................................................................................201
Figure 7-3 MGC card layout...............................................................................................................................207
Tables
Table 2-1 No.7 signaling access planning...............................................................................................................9
Table 2-2 SIP trunk data planning.........................................................................................................................12
Table 2-3 TCP/IP network planning......................................................................................................................12
Table 2-4 SBC address planning...........................................................................................................................18
Table 2-5 Planning of multimedia terminal data...................................................................................................21
Table 2-6 Version configuration table of IPCC products......................................................................................22
Table 3-1 Mapping between DIP switch settings and frame numbers of the SIU board......................................34
Table 3-2 Mapping between DIP switch settings and the device numbers of the SIU board...............................35
Table 3-3 Mapping between the frame numbers and the settings of the DIP switch of the UAP8100 MGW......36
Table 3-4 Description of the DIP switches of an EPI board..................................................................................37
Table 3-5 Description of the DIP switches of an ERI board.................................................................................37
Table 3-6 E1 line interfaces that the DIP switches S2 to S5 control.....................................................................38
Table 3-7 Application of the settings of a DIP switch...........................................................................................39
Table 3-8 E1 line interfaces that the DIP switches S6 to S13 control...................................................................39
Table 3-9 Application of the settings of S6...........................................................................................................41
Table 3-10 Application of the settings of S14.......................................................................................................41
Table 3-11 Configuration of the RS-232 interfaces of an alarm box....................................................................46
Table 3-12 Setting of the parameters of the gateway for connecting the alarm box.............................................47
Table 3-13 Configuration of the RS-422 interfaces of an alarm box....................................................................49
Table 3-14 Basic operations about alarm parameter configurations.....................................................................51
Table 4-1 Settings of soft switches during the first power-on of boards...............................................................59
Table 4-2 Settings of soft switches during normal running of boards...................................................................59
Table 5-1 Steps for configuring the hardware.......................................................................................................91
Table 5-2 Parameter citing relations between hardware data and other data........................................................93
Table 5-3 Data preparations..................................................................................................................................93
Table 5-4 Steps for configuring the local exchange data......................................................................................94
Table 5-5 Parameter citing relations between local exchange data and other data...............................................96
Table 5-6 Steps for configuring the charging data................................................................................................96
Table 5-7 Parameter citing relations between charging data and other data.........................................................97
Table 5-8 Steps for configuring the clock data in the MGC...............................................................................103
Table 5-9 Data preparations................................................................................................................................104
Table 5-10 Parameter citing relations between MGW data and other data.........................................................105
Table 5-11 Data preparations...............................................................................................................................107
Table 5-12 Steps for configuring the MTP data..................................................................................................108
Table 5-13 Parameter citing relations between MTP data and other data...........................................................108
Table 5-15 Steps for configuring the M2UA data...............................................................................................111
Table 5-16 Parameter citing relations between M2UA data and other data........................................................112
Table 5-18 Steps for configuring the M3UA data...............................................................................................114
Table 5-19 Parameter citing relations between M3UA data and other data........................................................115
Table 5-21 Steps for configuring the SIP data.....................................................................................................117
Table 5-22 Parameter citing relations between SIP data and other data..............................................................118
Table 5-24 Steps for configuring the routing data...............................................................................................119
Table 5-25 Parameter citing relations between routing data and other data........................................................119
Table 5-26 Data preparations..............................................................................................................................124
Table 5-27 Steps for configuring the No.7 trunk data.........................................................................................124
Table 5-28 Parameter citing relations between No.7 trunk data and other data..................................................125
Table 5-30 Steps for configuring the R2 trunk data............................................................................................128
Table 5-31 Parameter citing relations between R2 trunk data and other data.....................................................129
Table 5-32 Step for configuring the SIP trunk data.............................................................................................130
Table 5-34 Steps for configuring the number analysis data................................................................................131
Table 5-35 Parameter citing relations between number analysis data and other data.........................................132
Table 5-36 Preparations for configuring the resource data.................................................................................133
Table 5-37 Preparations for configuring the VRB resource data........................................................................135
Table 5-38 Procedure for configuring the VRB resource data............................................................................136

Table 5-39 Relations between the parameters of the MSU resource data and other data...................................138
Table 5-40 Preparations for configuring the built-in MSU resource data...........................................................138
Table 5-41 Configuration procedure...................................................................................................................138
Table 5-42 MML commands...............................................................................................................................140
Table 5-50 Preparations for configuring external resources...............................................................................146
Table 5-51 Steps for configuring the VP or FP resource data.............................................................................146
Table 5-52 Relations between the parameters of resource data and other data...................................................147
Table 5-53 Commands.........................................................................................................................................148
Table 5-54 Commands.........................................................................................................................................148
Table 5-55 Commands.........................................................................................................................................149
Table 5-56 Commands.........................................................................................................................................149
Table 5-57 Commands.........................................................................................................................................150
Table 5-58 Commands.........................................................................................................................................150
Table 5-59 Commands.........................................................................................................................................150
Table 5-60 Commands.........................................................................................................................................151
Table 5-61 Commands.........................................................................................................................................151
Table 5-62 Procedure for configuring the service data.......................................................................................152
Table 5-63 Commands.........................................................................................................................................152
Table 5-64 Commands.........................................................................................................................................153
Table 5-65 Commands.........................................................................................................................................157
Table 5-66 Board description..............................................................................................................................159
Table 5-67 Procedure for configuring MGW hardware data..............................................................................161
Table 5-68 Procedure for configuring data for the connection to the MGC.......................................................163
Table 5-69 Preparations for configuring signaling link data...............................................................................165
Table 5-70 Procedure for configuring M2UA link data......................................................................................166

Table 5-74 MML commands of office name.......................................................................................................168
Table 5-75 MML commands of office number...................................................................................................169
Table 5-76 Procedure for configuring IP bearing data........................................................................................170
Table 5-77 Procedure for configuring MGW clock data.....................................................................................173
Table 5-78 Configuration procedure...................................................................................................................190
Keywords
IPCC, deployment guide
Abstract
This document instructs customer service engineers in preparing for IPCC deployment and in
debugging equipment and services.
Acronyms and Abbreviations
Reference Documents
TopEng IPCC Configuration Template V1.3
Overview of the IPCC System
The TopEng IPCC system supports the combined networking of broadband and narrowband
services. It supports multimedia access. The U-SYS UAP8100 universal access platform
(UAP8100 for short) is used for access. The actual networking can be narrowband or
broadband networking. The multimedia capabilities can be flexibly used according to
customer requirements.
The major differences between the IPCC networking and the traditional CC&CRM
networking are as follows:
The front end C&C08-Q ACD is replaced with the UAP8100 that uses the integrated
configuration of broadband and narrowband services.
IP agents are added to support IP-based construction and meet all-IP networking
requirements.
1.1 Architecture of the IPCC System

The TopEng IPCC system supports the combined networking of broadband and narrowband
services. It supports multimedia access. Figure 1.1 shows the system architecture of the IPCC.
Figure 1.1 IPCC networking with the integrated configuration of broadband and narrowband
services
In Figure 1.1, when broadband networking is used, the UAP8100 can function as an NE of the
NGN core network; when narrowband networking is used, the UAP8100 can function as an
NE of the PSTN or PLMN network. As an access platform for data calls, MSP can be used
with the computer telephony integration (CTI) platform or service platform in networking and
be deployed in the internal networks of carriers to process multimedia calls. The Web Server
provides Web-based access and supports the functions of Web site browsing and WECC. In
addition, agent groups can be deployed in different networks according to the actual
application. You are advised to deploy agent groups in the internal networks of carriers.
The CC&CRM networking consists of four parts: media access devices, central servers,
online customer service servers, and central agents and maintenance terminals. In the
CC&CRM system, central servers are the main components. Other devices access the central
servers.
1.
UAP8100
The UAP8100 connects to the MSC/LE/TE through the SS7 and performs the following
functions:
Implementing the call access of PSTN and PLMN networks
Establishing and releasing call bearer connections
The UAP8100 uses the TUP/ISUP interface, and its physical interface is the E1/T1/SDH
(TDM) interface.
The UAP8100 connects to the SoftSwitch/MSC Server through SIP, and establishes and
releases call bearer connections between offices. The UAP8100 uses the SIP-T/SIP
protocol, and its physical interface is the FE (IP) interface.
The interface between the UAP8100 and TMG uses the RTP/RTCP protocol to bear
media streams, and its physical interface is the FE interface.
The UAP8100 supports SIP agent access to complete SIP terminal registration by using
the SIP protocol.
The UAP8100 provides the connection between the CSTA II/INtess and the CTI
platform. The physical interface is the FE (IP) interface.
2.
2008-12-02
Web Server
Page 2 of 212
The Web Server provides Web-based access through HTTP/HTTPS.

3.
MSP
The MSP connects to the Email Server through SMTP/POP3 to receive and send emails.
The MSP connects to the SMC through SMPP or connects to the SMS gateway through
CMPP to receive and send short messages (SMs).
The MSP connects to the MMS center through MM7 to receive and send multimedia
messages (MMs).
The MSP connects to the WAP gateway through PAP to implement the WAP Push
function.
4.
CTI platform and service platform

The CTI platform implements the CTI function. It connects to the UAP8100 and MSP to
implement the unified processing of calls and intelligent routing, and connects to agents
to control call routing to agents.
The service platform connects to third-party application systems to exchange data among
service applications. The systems exchanging data with the CC&CRM service include
the BSS/OSS, OA (workflow and file exchange), network management system (NMS),
and OMA.
5.
Agents serve attendants through telephone lines and various multimedia channels.
Compared with the C&C08-Q, the UAP8100 does not support the following items:
AP automatic flow of the ACD service
TNPP interface machine, which provides the paging function
TUA agents using analog telephone sets
1B+1D agents
For the CC&CRM service platform, only the interfaces connecting the BSS/OSS system are
necessary in the construction of the CC&CRM service.
This document emphasizes on the planning and configuration of the UAP, data network, and
CTI platform. Thus, service descriptions are not detailed.
1.2 Application of the UAP8100 in the IPCC

System
The UAP8100 is applied to the IPCC system in the following forms:
2008-12-02
Narrowband ACD
Packet ACD
ACD with the integrated configuration of broadband and narrowband services
Page 3 of 212
1.2.1 Narrowband ACD

When the UAP8100 functions as the narrowband ACD, it works with the CTI platform and
provides functions such as call access, call distribution, and specialized resource function
(SRF). See Figure 1.1.
Figure 1.1 Networking diagram of the narrowband ACD
When the UAP8100 functions as the narrowband ACD, it works with the CTI and provides
functions such as call access, call distribution, specialized resource function (SRF), and agent
management. The SRF function covers voice playing, digit collecting, voice recording,
faxing, attendant service, TTS, and ASR.
The interface between the UAP8100 and LE is used to establish and release call bearer
connections. This interface uses the TUP/ISUP protocol, and its physical interface is the E1
(TDM) interface.
The interface between the UAP8100 and PBX is used to establish and release call bearer
connections. This interface uses the TUP/ISUP protocol, and its physical interface is the
E1/T1 (TDM) interface.
The interface between the UAP8100 and CTI Server supports the CSTA protocol and the
INTESS protocol of Huawei. Its physical interface is the FE (IP) interface.
The interface between the UAP8100 and IP agents uses the SIP protocol, and its physical
interface is the FE (IP) interface.
The interface between the UAP8100 and I2000 is the MML interface of Huawei. This
interface manages the configurations, faults, and performance of the UAP8100. Its physical
1.2.2 Packet ACD

When the UAP8100 functions as the SoftACD, its networking structure is as shown in Figure
1.1.
2008-12-02
Page 4 of 212
Figure 1.1 Networking diagram of the packet ACD
On the NGN network, the UAP8100 works with the CTI platform and implements the
following functions on the pure packet network:
Switch and access
Call distribution
SRF control and management
Media conversion
IP agent provision for the ICD of a call center
The SRF function covers voice playing, digit collecting, voice recording, faxing, TTS, ASR,
(voice) conference bridge, and video playing.
The interface between the UAP8100 and CTI Server supports the INTESS protocol of
Huawei. Its physical interface is the FE (IP) interface.
The interface between the UAP8100 and SoftSwitch is used to establish and release call
bearer connections between offices. This interface uses the SIP-T/SIP protocol, and its
physical interface is the FE (IP) interface.
The interface between the UAP8100 and TMG uses the RTP/RTCP protocol to bear media
streams, and its physical interface is the FE/GE interface.
The interface between the UAP8100 and broadband terminals uses the SIP protocol, and its
physical interface is the FE (IP) interface.
The interface between the UAP8100 and I2000 is the MML interface of Huawei. This
interface manages the configurations, faults, and performance of the UAP8100. Its physical
2008-12-02
Page 5 of 212
1.2.3 ACD with the Integrated Configuration of

Broadband and Narrowband Services
In 1.2.1 IStep 1Figure 1.1 and 1.2.2 IStep 1Figure 1.1, the UAP8100 is used as a universal
access platform. It can be used on narrowband networks such as PSTN and PLMN or on
broadband networks such as NGN and 3G network. It provides the following functions or
resources for a call center:
Call access
Call distribution
Media resources
Agent management
Media resource management covers voice playing, digit collecting, voice recording, faxing,
TTS, ASR, attendant service, video playing, audio codec conversion, and audio conference
bridge.
1.3 Typical Networking of the IPCC System

Figure 1.1 shows the typical broadband networking using the UAP8100. In this networking
diagram, the IP bearer backbone network is the trust area. The internal private network of the
carrier and the Internet are non-trust areas.
Figure 1.1 Typical networking of the IPCC system
You can use the existing access technologies to flexibly deploy IP agents. With the rapid
development of data services, individuals and enterprises have an increasing number of
2008-12-02
Page 6 of 212
channels to access the data services. The current mainstream access channels include the
xDSL, WLAN, community broadband service, and 3G wireless network. These access
channels have their own advantages. For example, the xDSL has wide coverage, whereas the
WLAN has high speed. You can flexibly select access channels according to the number of
agents and their geographic locations. In current IPCC offices, IP agents are all connected
through the internal private networks of carriers.
2008-12-02
Page 7 of 212
Preparation for the Deployment

As an entire customer service system, the IPCC system involves multiple NEs and
components. Therefore, on-site deployment personnel need to plan the signaling point
resource, IP address resource, and software versions before deployment.
2.1 Planning the Signaling Network

If the UAP8100 interconnects with the PLMN or PSTN network, plan the narrowband
signaling network. If the UAP8100 interconnects with the NGN network, plan the broadband
signaling network.
To avoid the faults of trunk circuits or links which are caused by the faults of the E32/S2L,
EPI, or IFM board, on-site deployment personnel need to comply with the following
principles when distributing trunk circuits and links.
Principle of Distributing Trunk Circuits

Each E32 board provides two physical interfaces, and each interface provides 16 E1 cables.
The access trunks include the internal trunks and the trunks between offices. The two
interfaces of the E32 board can access the trunks of different types; however, the same
interface can only access the trunks of the same type.
2008-12-02
If the office has only two E32 boards, the trunk circuits in the same office direction must
be distributed to the two E32 boards according to the load sharing principle, and the
internal trunks should also be distributed to the E32 boards evenly. This helps improve
the reliability of the system.
If the office has more than two E32 boards, on-site deployment personnel are advised to
distribute the internal trunks and the trunk circuits between offices to different E32
boards. This facilitates the maintenance and capacity expansion in the future. The trunk
circuits in the same office direction, however, must be allocated to different E32 boards.
This helps improve the reliability of the system.
If the office uses multiple S2L boards, the trunks of the same office direction do not
occupy all the optical interfaces of the S2L boards.
Page 8 of 212
When the UAP8100 interconnects with the ISUP of an opposite office, if certain specified
circuits are not configured, the UAP8100 sends UCIC messages to the switches of the
opposite office. After receiving the UCIC messages, however, certain switches may set the
circuits to block status. The circuits cannot be recovered even they are reset or re-configured
in the opposite office. (Note: Generally, the sixteenth slot of each E1 on the UAP8100 is not
configured. This slot will be blocked if the sixteenth slot of the opposite office is configured.)
The UCIC is a message type specified in the ITU-T Recommendation, and it is not supported
by the standards in China. Therefore, certain switches of Chinese manufacturers do not
process UCIC messages and leave the circuits in block status. To support the standards in
China and abroad, the UAP8100 uses the software parameter P18 to determine whether to
send UCIC messages. The P18 parameter can be set to 0 or 1. The default value is 1, which
indicates sending UCIC messages.
Bit 6
It determines whether to send UCIC messages after the UAP8100 receives the ISUP messages
and finds that the circuits are not configured. The value 1 indicates sending, and the value 0
indicates not sending.
Suggestion
Change the value of bit 6 of P18 to 0.
Principle of Distributing No.7 Links

As the rear board of the CSU board, each EPI provides eight E1 interfaces. The 1+1 backup
mode is adopted when the CSU boards are configured. During the failover of the active and
standby CSU boards, the EPI board can process signaling time slots by using H110 bus. If
faults occur on the EPI board, the UAP8100 cannot perform service switchover by using
H110 bus. Therefore, on-site deployment personnel need to comply with the following
principles during link interconnection and distribution:
If multiple links exist between the UAP8100 and a certain signaling point, connect the
links to EPI boards through different E1 cables. In this way, available links still exist
between two signaling points even when faults occur on an E1 interface. This helps
improve the reliability of the system.
If the UAP8100 office has multiple pairs of CSU+EPI boards, the E1 cables for
connecting the UAP8100 and certain signaling point must be distributed to different EPI
boards. In this way, available links still exist between two signaling points even when
faults occur on an EPI board. This helps improve the reliability of the system.
If the UAP8100 office has only one pair of CSU+EPI boards, in case faults occur on the
active EPI board, remove the E1 connector from the active EPI board and insert it to the
standby EPI board. Meanwhile, switch the active and standby CSU boards. This ensures
that the active CSU board and the active EPI board are located in the same slot.
For the No.7 signaling link access, pay attention to the key items listed in the following table.
Figure 1.1 No.7 signaling access planning
2008-12-02
SN
Key Item
Description
Internal signaling
point code (SPC)
As an exchange, the UAP8100 uses No.7 SPCs.
Page 9 of 212
SN
Key Item
Description
GT
The GT address of the UAP8100 is used for SCCP

routing. In the schemes of ACD service and RBT
service, the item is not required.
Destination SPC
The SPC of the switch that connects with the

UAP8100.
Signaling link
selection code
If multiple links exist in a link set, a mask policy

should be provided.
Signaling link code
This code is determined after the negotiation with the

opposite office.
Signaling link code

sending
The manner of sending signaling link codes is

determined after the negotiation with the opposite
office.
Circuit number
corresponding to the
signaling link
This number is determined after the negotiation with

the opposite office.
CIC distribution
The codes of the speech channels in different office

directions are specified.
2 MB signaling
The number of 2 M signaling links.
10
Circuit selection mode
Between two offices, the signaling point with a larger

code controls the circuits with even numbers; the
signaling point with a smaller code controls the circuits
with odd numbers. The two offices should determine
the mode together.
The networking diagrams are shown as follows.

Figure 1.2 Physical networking for the connection between the UAP8100 and No.7 signaling
2008-12-02
Page 10 of 212
Figure 1.3 Physical networking for the connection between the UAP8100 and No.7 signaling
(M2UA-MTP)
The UAP8100 V300R003 supports M2UA signaling, so No.7 signaling links can access the
UAP8100 through the EPI board or the IFM board of the MGC. The speech channels,
however, can access the UAP8100 through the E32/S2L board of the MGW.
Principle of Configuring SIP Trunk Networking

A local port number is configured for each MSG board, and a service port number (5060) is
configured for the MGC of the UAP8100. Both the local port and the service port use the SIP
protocol.
After processing the MAC message, the IFM board checks the destination port of the
message. If the destination port is a local port, the IFM distributes the message according to
the relation between the local port number and the MSG module number. If the destination
port is a service port, the IFM board distributes messages to any MSG board that can process
the SIP protocol according to the load sharing principle.
After receiving the first message sent from the service port, the IFM board sends the message
to the MSG board according to the load sharing principle. The message included the SIP local
port number of the MSG board. After receiving the sequent messages, the IFM board sends
the messages to the MSG board according to the relation between the local port number and
the MSG module number.
Principle of SIP Trunk Access

If the UAP8100 needs to interconnect with softswitch offices, packet data is required.
The SIP trunk is a type of packet trunk. The circuit defines physical channels, but the SIP
trunk defines logical channels. The SIP trunk is used to configure the information about the
interconnection between the UAP8100 and other softswitch devices and the interconnection
between the UAP8100 and SIP application servers. The information includes SIP-URL and
whether to support SIP-T.
2008-12-02
Page 11 of 212
Figure 1.1 SIP trunk data planning

Data
Description
IP address of an opposite
office
It specifies the IP address of an opposite office.
SIP protocol port number of

an opposite office
It specifies the IP address and SIP protocol port number of

an opposite office.
Prefix pointing to an
opposite office
It specifies the prefix pointing to an opposite office.
Supporting SIP-T or not
It specifies whether to support the transparent transmission

of the ISUP signaling.
Supporting heartbeat signals

or not
It specifies whether the MGC regularly sends heartbeat

signals to the SIP device of an opposite office.
2.2 Planning the TCP/IP Network

This section describes the planning of TCP/IP network of the IPCC. For details about data
network configuration, refer to the TopEng IPCC Configuration Template V1.1.
You can visit the Web site at http://support.huawei.com to obtain the TopEng IPCC
Configuration Template V1.1. The location of the document is as follows:
Documentation > Application and Software Product Line > Operation Support System >
Call Center and CRM > Technical Guide > Deployment Guide
2.2.1 Planning of UAP8100 Networking

Planning of the Internal Network
On the UAP8100, IP addresses need to be planned for the following components: VRB,
CSU/CCU, IFM, FEP, FileServer, BAM, OMU, and E8T/MPU.
For the TCP/IP networking, pay attention to the key items listed in the following table.
Figure 1.1 TCP/IP network planning
2008-12-02
SN
Key Item
Description
MEM of the CSU/CCU

board
It is used for the UAP8100 to connect with the FEP

to communicate with the CTI platform, VP, or FP.
MEM of the VRB board
It is used for the UAP8100 to communicate with the

FileServer.
Page 12 of 212
SN
Key Item
Description
IP address of the IFM

board
It is the IP address for the MGC to communicate with

external devices.
If there are two pairs of IFM boards, the IP addresses
of one pair of IFM boards are used for the MGC to
communicate with the MGW. The IP address of the
other pair of IFM boards can be used for the MGC to
communicate with the CTI platform or softswtich
devices.
It is recommended that each pair of IFM board be
planned to the same VLAN regardless of whether the
IFM boards are on the LanSwitch or external
switches.
IP address of the MGC

BAM
It is used for the BAM to communicate with system

boards. It is also provided for the I2000 and
maintenance client to access the BAM.
IP address of the E8T

board (it is configured
when the MGW is planned
in a single frame)
The functions of the IP address are as follows:
IP address of the MPU

board (it is configured
when the MGW is planned
in multiple frames)
It is used for the MGW to connect with the MGC.
IP address of the LMT of

the MGW
The LMT of the MGW can be installed together with

the BAM of the MGC.
The MGW communicates with the MGC through

H248.
The MGW connects to the IP backbone bearer

network through the RTP flow.
The LMT, however, is the OMU client of the MGW,

so it is recommended to separate the LMT from the
BAM.
8
IP address of the FileSever
Two IP addresses should be configured. One is used

for communicating with the VRB, and the other is
used for communicating with the Portal.
IP address of the interface

of OMU
It is used to connect with the LMT.
10
IP address of the FEP
It is used to communicate with the MEM of the

CSU/CCU board of the MGC.
For the TCP/IP networking of the UAP8100, see the following figure (the FileServer in the
figure indicates the active and standby file servers).
2008-12-02
Page 13 of 212
Figure 1.2 TCP/IP networking of the UAP8100
The switch in the figure refers to S5624. For the configuration of the S5624, see section 5.5Configuring
Network Device Data.
The FileServer in the figure refers to the active and standby file servers. Each file server adopts dual
network adapters to connect with two S5624 respectively. In the actual networking, the two file servers
connect to different S5624 through Gigabit network adapters.
VLAN Planning on the S5624

At least two VLANs should be planned in the UAP8100 networking. The network ports of the
IFM boards and the network ports corresponding to the MGW must be allocated to
independent VLANs. If the MGW is planned in a single frame, the network ports
corresponding to the MGW are located on the E8T board; if the MGW is planned in multiple
frames, the network ports are located on the MPU board.
SN of VLAN
Contained Network Ports
VLAN1
HSC, CTILINK, FS, BAM, TTS server, and cascade port
VLAN2
IFM, E8T/MPU, and cascade port
If the M3UA networking is used on-site or the UAP8100 interconnects with the softswitch
devices, multiple pairs of IFM boards may be configured. In that case, an additional VLAN is
required to accommodate the external networks.
Note that the cascading port on the switch must be able to transparently transmit data to all the
preceding VLANs.
2008-12-02
Page 14 of 212
An independent VLAN must be planned for the IFM network port that bears SIP signaling
and the E8T bearing network port in the conditions described as follows:
The network that interconnects with the UAP8100 is a PSTN or PLMN network.
SIP broadband agents are used.
There are two pairs of IFM boards.
In addition, the network port of the SBC server must be connected to the VLAN network.
Planning of Device Numbers

Each board of the UAP8100 has fixed IP address and MAC address, so address collision may
occur when multiple UAPs exist on the same LAN. In special cases, the IP addresses of
Huawei devices may conflict with the IP addresses of peer devices.
To solve this problem, we design device numbers for the UAP8100. If the device number of
the UAP8100 is X, the IP addresses of the BAM for communicating with the host
are172.2X.200.0 and 172.3X.200.0. For example, if the device number of the UAP8100 is 3,
you need to set DevNo. to 3, and set the IP addresses of the BAM to 172.23.200.0 and
172.33.200.0. The device number of the UAP8100 is set through the DIP switch on the SIU
board. For the details of setting the device numbers, see Chapter3Hardware Installation.
The device number ranges from 0 to 7. If multiple sets of UAPs connect with each other
through layer 2 network, device numbers must be set for UAPs for separation. The device
number of each UAP8100 is different. Do not use the device number 0. This helps to avoid
address collision during capacity expansion.
2.2.2 Planning of IPCC Networking

The IPCC networking includes the following three areas:
Core service area
Agent service area
External access area
In the core service area, the datacom devices are located, such as the F5 load balancer, core
switch, and firewall. These devices are used for the connection between servers and routing
devices.
In the agent service area, the devices such as agent access switch and agent convergence
switch are located. These devices are used to connect the agent service area to the core service
area and the external access area.
In the external access area, the devices such as the SBC, the UAP8100, and the switches
connecting to the core network are located. These devices help the agents to register on the
UAP8100.
The entire networking of the IPCC system is shown in the following figure.
2008-12-02
Page 15 of 212
Figure 1.1 IPCC networking diagram
Networking Planning of Core Service Area

In the core service area, it is recommended to use two 65- or 85-series switches as the core
switches, and use a firewall to separate the agent service area from external systems.
Configure at least two network adapters for each server, such as the CTILINK server and the
file server, to connect with the core switch and the S5624 respectively.
Reserve network ports on the core switch for the MGC BAM, and OMC. This facilitates the
maintenance of the UAP8100.
If there are any external VPs and ASR servers, connect these devices to the core switches.
If TTS servers exist in the system, and they use only the build-in VRB board of the MGC to
play voice, the TTS servers need to connect to the S5624 of the UAP8100.
If external VPs are used to play voice at the same time, they should be configured with two
network adapters. One is connected to the S5624 of the UAP8100, and the other is connected
to the core switches (this connection is not tested).
If only external VPs are used to play voice, the VPs and TTS servers are connected to the core
switches.
Networking Planning of Agent Service Area

Select switches for this area according to the number of agents. For details, see section
2.2.3Device Type and Device List. If the number of agents is large, the agent convergence
2008-12-02
Page 16 of 212
switches need to connect with the core service area and the external access area through
Gigabit network cables or optical fibers.
Networking Planning of External Access Area

The SIP agents can access the UAP8100 through the IP backbone bearer network, Internet, or
the private networks of carriers. Generally, the IP backbone bearer network and internal
communication network are allocated to the Trust area, and the Internet, the private networks
of carriers, and the LANs of enterprises are allocated to the non-trust area.
The session border controller (SBC) is located on the convergence layer of the MAN.
Terminal devices access the NGN network through the SBC. The SBC helps users to solve the
problems of security, NAT traversal, and QoS which occur when they use NGN services. The
SBC can also be located at the egress of the enterprise network to solve the problem of NAT
traversal by using the full proxy mode.
The SBC can be used for connecting different NGN networks to provide the functions of
interworking between different address domains, QoS guarantee, and network hiding.
Sometimes, the SBC is also called network border point (NBP).
Figure 1.1 SBC address planning
SN
Key Item
Description
client-address
It specifies the IP address of the interface of the SE2x00 user

side. The same SE2x00 can be configured with one or
multiple such interfaces. The signaling and media stream
have different client addresses.
server-address
It specifies the IP address of the interface used for

connecting the SE2X00 and the softswitch device. The same
SE2x00 can be configured with such one or multiple
interfaces. The signaling and media stream have different
server addresses.
softx-address
It specifies the IP address of the softswitch device

corresponding to the SE2x00. For the UAP8100, it is the IP
address for the IFM board to provide SIP signaling to
external systems. The SE2x00 can provide the proxy service
for multiple softswitch devices.
The IP address of the softswitch device configured on the terminal of the SE2x00 user side is the IP
address of the SE2x00 user side.
2008-12-02
Page 17 of 212
Figure 1.2 UAP8100 external bearer networking diagram
The network ports of the IFM board are connected to the LanSwitch. The SBC is a proxy
device for filtering the session layer-based signaling protocols and media streams. The
filtering function of the SBC is more powerful than the IP protocol-based filtering function of
the firewall.
In the previous figure, L1, L2, L3, L4, and L5 are layer 3 or layer 2 switches added when the
UAP8100 connects with the external bearer network. They cannot be used for internal
communication of the UAP8100, and any connection between these switches and the layer 3
switches (5624P) for internal communication of the UAP8100 is prohibited.
2.2.3 Device Type and Device List
Core switches
Two 65- or 85-serials switches are used as the core switches. The engine of each switch
has four SFP Gigabit interfaces. Each switch has one 48FE module and a GE module
with 20 electrical interfaces. The core switches are used in the interconnection between
servers and routing devices.
Switches used in the networking of IFM boards and MEM modules

Two S5624 are used to connect IFM boards and E8T boards, and connect MEM modules
and CTILINKs.
Switches used in the connection of UAP8100 and core network

The switch used for connecting the UAP8100 and the core network is configured with
sufficient bandwidth according to the message traffic. The message traffic includes the
signaling traffic and media traffic. If the traffic is less than 50 Mbps, the 35-serials layer
3 switches are recommended. If the traffic is more than 50 Mbps, the 56-serials switches
with Gigabit interfaces, or the 65- or 85-serials switches are recommended.
2008-12-02
Page 18 of 212
Switches used in the interconnection area of external services

Two S3528P are used in the interconnection area of external services. If there is no duallink in this area, only one switch is required. If the BOSS accesses the UAP8100 through
a Gigabit interface, three SFP modules should be configured for each S3528P.
Agent switch
In the office where both the agents and the center server are installed, one pair or
multiple pairs of S3552P are used according to the number of agents.
For the offices to which the agents connect through XDSL and WLAN, a pair of S3528P
is configured.
In a large-scale office, two S8505 are used as the agent core switches. One 48FE module
is configured for each switch to connect with agent access switches, and one Gigabit
module with eight ports is configured for each switch to connect with core switches or
firewalls.
In a middle-scale office, two S3528P are used as the agent core switches. One pair or
multiple pairs of S3552P are used according to the number of agents.
Firewalls used for service interconnection and separating severs from agents
Two Eudemon500 are used and configured to a two-node cluster. One 8FE interface is
configured for each firewall. If Gigabit interconnection is required, one 2 GE SFP
module needs to be configured. For example, if the BOSS uses a Gigabit interface for
access, one 2GE SFP module needs to be added.
Routers for the interconnection on the WAN

The AR2840 is used for the offices where are configured with only servers, the offices
where are configured with only agents, and the offices where are configured both servers
and agents. For the AR2840, one FE module and one E1 module should be configured. If
dual-link exists on the WAN, two routers are configured for each office. If there is no
dual-link, only one router needs to be configured. If the database disaster recovery is
required between two offices where only servers are installed, and high traffic occurs, the
two offices are connected through layer 3 core switches without any routers.
Load balancers
Two load balancers are configured to a two-node cluster. Four 10/100/1000 MB adaptive
interfaces and two multimode SFP interfaces are configured for each load balancer. The
types of the recommended load balancers are the BIGIP1500, Radware, and Citrix of F5.
Firewalls used in the WECC

Two Eudemon500 are used as the firewalls in the WECC, and one 4FE module is
configured for each firewall. The Eudemon200 can be used if the WECC has low
requirements for service application. If no two-node cluster exists in the WECC, only
one firewall needs to be configured.
Switches used in the WECC

Two S3582P are used in the WECC. If no two-node cluster exists in the WECC, only one
switch needs to be configured.
Switches used in the external interconnection area of the Internet

Two S3528P are used in the external interconnection area of the Internet. If there is no
dual-link in this area, only one switch is required.
SBC
The SessionEngine 2300 produced by Huawei is used. For the office where there are less
than 500 agents, the SessionEngine 2200 can be used.
2008-12-02
Page 19 of 212
The performance of the two FE interface on the engine of the Eudemon500 is poor, so they
can only be used as management interfaces.
The SessionEngine 2200 uses the two FE interfaces on the RPU main control board for
service processing. The performance of the FE interfaces on the interface board is poor, so
they can only be used as management interfaces or heartbeat interfaces.
The SessionEngine 2300 cannot use the FE interfaces on the RPU main control board for
service processing. The FE interfaces can only be used as management interfaces or heartbeat
interfaces. The SessionEngine 2300 can provide up to three GE interfaces at the same time. It
is incapable of providing any FE network port when it provides three GE interfaces. In actual
application, the usage of 2GE + 8FE is recommended. The two GE interfaces are used for
media transmission, and the FE interfaces are used for signaling transmission. The number 3
slot of the SessionEngine cannot be configured with any interface board.
If you want to convert addresses, you can use the Eudemon200 or Eudemon500. Do not use
the Eudemon100, because a bug exists on this device. After address conversion, the SIP
signaling is normal, but neither the caller nor the callee can hear the voice of the opposite
party.
In the recommended IPCC networking, the SBC connects to two switches through two
network cables. If the SBC connects to the same switches through two network cables and the
SBC works in active/standby mode, the datacom devices connected with the SBC need to
provide the function of layer 2 forwarding.
2.2.4 Planning of Multimedia User Data

In the IPCC networking, the data of the IP agents needs to be provided. The data is distributed
to multiple CSU/CCU boards according to the actual service requirement.
TheUAP8100 needs to interconnect with the multimedia terminal of the carrier, so the
multimedia terminal data needs to be provided.
2008-12-02
Page 20 of 212
Figure 1.1 Planning of multimedia terminal data

Data
Description
Protocol type
It specifies the protocol type adopted by the multimedia terminal, that

is, the SIP protocol.
Registration
(authentication)
mode
It specifies the registration (authentication) mode of the multimedia

terminal for registering on the UAP8100. The three registration
(authentication) modes are as follows:
No Auth: No registration (authentication) is required.
Auth By EID: The registration (authentication) is performed based on
the user ID and password.
Auth By IP: The registration (authentication) is performed based on an
IP address.
IP address
It specifies the IP address for the multimedia terminal when it performs

registration (authentication) based on an IP address.
User ID
The user ID should be a character string, and it consists of 32 digits at

most.
Password
It specifies the password for the multimedia terminal to register on the

UAP8100. The password should be a character string, and it consists
of 8 digits at most.
2.3 Checking Software Versions

Before installation, on-site deployment personnel need to check whether the software versions
are correct.
Figure 1.1 Version configuration table of IPCC products
Product
Name
Version
UAP8100
UAP8100 V300R003C01B053SPH005
UAP8100 V300R005C01B063SPC003BICC/Distributed
UAP8100 V300R003C01B072 (Broad Band VMS/MCNS)
ICD platform
ICDV300R004C01B072SPC002
ICDV300R004C01B112SPC001Used with UAP R5 Version
2008-12-02
VP
V610R003.5Da19 (the operating system of the VP is WIN2000Server)
FP
V610R003.5Da17
OpenEye
HUAWEI OpenEye NGN_VOIP V300R001C01B372
TTS
InterPhonic4.0+ISP2.5
Page 21 of 212
Product
Name
Version
ASR
Nuance ASR 8.5
FS operating
system
SUSE9+SP03
FS cluster
software
Veritas4.1+MP2
SBC
SessionEngine 2200 (SBCV200R005C02B052 or later)

SessionEngine 2300 (SBCV200R005C03B063 or later)
I2000
I2000V300 R001.2DH04+SPC006
OAM
OAMV2.0D313 (V100R001C01B031SP06 or later)

It is used together with the UOA.
If you use external VPs to provide the TTS function, check the version configuration table of
the VP for the TTS version.
At present, the VRB board of the UAP8100 does not support the ASR function, so external
VPs should be prepared to provide the ASR service.
If the SBC does not convert addresses through NAT devices, the SBC must be set to single
domain mode.
2.4 Application of Software Licenses

2.4.1 Applying for a License of the ICD Platform
To apply for a license of the ICD platform, do as follows:
Fill in the ICD Platform License Application according to the contract information. The
information that needs to be provided includes the customer name, contract number, host
name, MAC address, maximum agents, maximum concurrent PSTN calls, maximum
concurrent WEB calls, maximum VDNs, maximum automatic calls, whether to access
by group, and platform version.
Send the ICD Platform License Application to icd-license@huawei.com, and wait for the
reply.
For the ICD Platform License Application, refer to the attachment 1.
2.4.2 Applying for a License of the FP

To apply for a license of the FP, do as follows:
2008-12-02
Fill in the Fax Peripheral License Application according to the contract information. The
information that needs to be provided includes the customer name, the time of providing
Page 22 of 212
the license, contract number, host name, MAC address, FP version, maximum concurrent
PSTN calls, card type, and validity period.
Send the Fax Peripheral License Application to icd-license@huawei.com, and then wait
for the reply.
For the Fax Peripheral License Application, refer to the attachment 2.
2.4.3 Applying for a License of the ASR Software

To apply for a license of the ASR software, do as follows:
Get the information about the license of the ASR software from the ASR software
package.
The information includes the item, software model, PO number, and maximum ASR
channels.
Send the character string following the PO number to youchong@huawei.com or

22213@notesmail.huawei.com, and wait for the reply.
At present, the license application and approval of the ASR software cannot be performed through IT
systems. To apply for a license, you can send the related information, such as the item, contract number
and maximum ASP channels, to the mailbox of You Cong (22213). You Cong will process the mails and
provide you a license.
2.4.4 Applying for a License of the OpenEye

Software
To apply for a license of the OpenEye software, do as follows:
Before the project kickoff, send the information including the contract number, site name, the
number of licenses, and OpenEye software version number to the mailbox wxs@huawei.com
or 33936@notesmail.huawei.com of Wu Xiaosheng/33936. Wu Xiaosheng starts the e-flow
for applying the licenses of the OpenEye software, and provides the licenses to on-site
engineers.
2008-12-02
Page 23 of 212
2.4.5 Applying for Licenses of the SysPatron

Software and System Customization Tool
At present, only the antivirus software Trend ServerProtect can be installed on the customer
service devices such as the BAM, CP, VP, and FP because of IO problems. If no antivirus
software is installed, the security of the devices cannot be guaranteed. In this case, the
SysPatron software is a good choice. The SysPatron software is a tool for security
enhancement for the AIP products. It ensures that only the necessary process or ports can run
on or exist on the CP, VP and FP, which avoids virus intrusion.
The licenses of the SysPatron software and the licenses of the system customization tool are
applied for together. The information that needs to be provided includes the operating system
type, version number of SysPatron, user ID, name of the system customization tool, version
number of the system customization tool, and user ID. For details, see attachment 3 Measures
for Managing and Applying for Licenses. This document can be obtained from the tool
package that is released with the UAP version. Take B023 version for example, the path of
this document is UAP8100V300R003C01B023\Tools\SetWin2000.
2008-12-02
Page 24 of 212
Hardware Installation
This chapter describes the following basics about the UAP8100 hardware installation:
Hardware structure of the UAP8100 MGC and MGW
Basic sequence in which hardware is installed
Installation of the file server
Installation of the switch and the SBC
For details, see the delivery-attached manual of the UAP8100 U-SYS UAP8100 Universal
Access Platform Hardware Installation Guide.
3.1 UAP8100 Hardware Installation

3.1.1 Overview of the UAP8100 MGC Hardware
OSTA Platform
The OSTA platform is the hardware platform of the UAP8100 MGC, which simultaneously
provides two buses on the backplane: resource sharing bus and Ethernet bus. The OSTA
platform can be applied in various conditions and is of high reliability. It is used to exchange
and transmit length-variable data packets of communication devices.
The OSTA platform uses frames of the standard structure: 19-inch wide and 9 U high. Boards
are inserted in OSTA-based frames in front-and-back insertion mode, as shown in Figure 1.1.
2008-12-02
Page 25 of 212
Figure 1.1 Structure of an OSTA-based frame
(1): power
supply board
(6): front board
(2): interface
board
(7): service
board
(3): Ethernet
communications board
(8): system administration
board
(4): back board
(5): mother
board
(9): alarm board
In the OSTA frame,
The front board consists of a service board, a system administration board, and an alarm
board.
The back board consists of an interface board and an Ethernet board.
A power supply board can be inserted in the front board or the back board. The frontand-back insertion mode of boards separates the functions of the front board and back
board of a frame. It simplifies the design of a board, makes the function of a board more
particular, and reduces the hardware complexity. Thus, the front-and-back insertion
mode of boards improves the reliability of the system, the university of a frame, and the
flexibility of system configuration.
In the UAP8100 MGC, all frames can be used in different hardware. Each frame is designed
with 21 slots for standard boards. The fixed configuration of a frame is two system
administration boards, two Ethernet communications boards, one alarm board, and two power
supply boards (occupying two standard board slots each). These boards must be installed in
fixed slots, occupying nine standard board slots. The rest 12 slots on a frame are for service
boards and interface boards. Figure 1.2 shows the front view of an MGC frame.
2008-12-02
Page 26 of 212
Figure 1.2 Front view of an MGC frame
3.1.2 Overview of the UAP8100 MGW

The UAP8100 MGW supports 256K TDM switch and contains a fan box. The UAP8100
MGW uses the front-and-back insertion mode. Figure 1.1 shows the front view of the MGW
frame and Figure 1.2 shows the slots on the MGW frame.
Figure 1.1 Front view of the MGW frame
2008-12-02
Page 27 of 212
T N N T
N E E N
B T T B
Universal slot
Universal slot
Universal slot
1
5
Universal slot
Universal slot
Universal slot
1
4
Universal slot
Universal slot
Universal slot
1
3
Universal slot
Universal slot
Universal slot
1
2
Universal slot
Universal slot
Universal slot
1
1
Universal slot
Universal slot
9U
1
0
Universal slot
8U
0
9
Universal slot
0
5
Universal slot
0
4
Universal slot
0
3
Universal slot
0
2
Universal slot
0
1
0
6
0
7
0
8
Control board
0
0
Control board
Slot
No.
Universal slot
Figure 1.2 Front view of the SSM-256 frame
Back
Front
The slots in an SSM-256 frame are described as follows:
Front slots are 9 U high and back slots are 8 U high.
Back slots 07 and 08 are for NET boards.
Front slots 07 and 08 are for OMU boards (if the frame is a main control frame) or MPU
boards (if the frame is not a main control frame).
Back slots 06 and 09 are for TNU boards of the RTNB type.
Front slots 06 and 09 are for service resource boards of various types, for example PVPB
boards, but service boards that require front-and-back insertion cannot be inserted in
front slots 06 and 09.
Universal slots are for service processing boards of various types, but CLK boards must
be inserted in the back slots 00 and 01 of the main control frame.
3.1.3 General Process of Installing the UAP8100

Hardware
The proper operation of the UAP8100 depends on the quality of hardware installation.
Systematic and standard installation of the UAP8100 can effectively reduce the factors that
might lead to the instability of the device operation and improve the reliability and efficiency
of the device on-line operation.
Figure 1.1 shows the general process of installing the UAP8100 hardware.
2008-12-02
Page 28 of 212
Figure 1.1 General process of installing the UAP8100 hardware
For the methods of installing the MGC and MGW, see the U-SYS UAP8100 Universal Access
Platform Hardware Installation Guide. Pay special attention to the method of connecting
clock cables.
The path to the document at http://support.huawei.com is as follows:
Documentation > Application and Software Product Line > Service and Software Public
> UAP&URP > Product Manual > V300R003 > UAP
3.2 Installation of the Core Server on the CTI

Platform
Generally, the core server on the CTI platform is an AIX, HP, or PC server with at least the
following fast Ethernet (FE) ports:
2008-12-02
Page 29 of 212
FE port for separated networking of CTILINK and the memory (MEM) board
FE port for direct heartbeat link
FE port for providing service IP addresses
3.3 Installation of the Storage Hardware on

the File Server
To ensure performance and stability, the UAP file server must use the storage area network
(SAN) structure. The SAN structure requires two file servers that run the SuSE Linux
operating system and work in two-node cluster mode. The two-node cluster ensures the
security of the data and operation. Make sure that each file server is installed with at least two
hard disks and uses the RAID 1 mode. In addition, the SAN structure requires that the two file
servers must be connected to the same set of storage equipment. When multiple file servers
are available for load balancing, the N+X mode can be used.
Figure 1.1 Cable connection between the disk array and the server
ST3200
Controller
A
Controller
B
Optical fiber
Ethernet cable
Linux
Heartbeat
Linux
server
server
WS
Ethernet
For offices that require many resources, a disk array cabinet cannot meet the requirement of
performance. For these offices, an expansion disk frame is required. Figure 1.2 shows the
cable connection between the expansion disk frame and the controller frame.
2008-12-02
Page 30 of 212
Figure 1.2 Cable connection between the disk array extension frame and the control frame
The ID of the control frame is set to 1 and the ID of the extension frame is set to 2.
3.4 Configuration of the LanSwitch

If the configured working mode of the UAP8100 network interfaces is different from that of
the LanSwitch network interfaces connected to the UAP8100, problems such as packet loss
and connection intermittent blinking might occur. This affects the proper operation of the
UAP8100 and brings security risk to the UAP8100. To ensure the stable operation of on-line
devices and avoid risks, configure the working mode of the UAP8100 network interfaces and
the LanSwitch network interfaces that are connected to the UAP8100 according to the
specifications described in the following table.
Device
Board
Working Mode
of the Current
Interface
Device of
the
Opposite
Interface
Working Mode of
the Opposite
Interface
UAP8100
MGC
IFM
100M Full Duplex
LanSwitch
100M Full Duplex
100M HSC
Auto Negotiation
LanSwitch
Auto Negotiation
1000M
HSC
1000M Full Duplex
LanSwitch
1000M Full Duplex
E8T
100M Full Duplex
LanSwitch
100M Full Duplex
OMU
Auto Negotiation
LanSwitch
Auto Negotiation
MPU
Auto Negotiation
LanSwitch
Auto Negotiation
UAP8100
MGW
Make sure that the working mode of the network interfaces is configured at a time. If you
want to modify the configuration, run MOD commands. Note that the modification should be
made when the service traffic is low.
For the MGC, you can run MOD FECFG to change the working mode of the network
interfaces on IFM boards. The following is an example:
2008-12-02
Page 31 of 212
MOD FECFG: MN=35, EA=FH;//The modification takes effect after the IFM board is
restarted.
For the MGW, you can run MOD IPIF to change the working mode of the network
interfaces on OMU, MPU, E8T, and E1G boards. The following is an example:
MOD IPIF: IFT=ETH, BT=OMU, BN=0, IFN=0, SPEED=AUTO, DUPLEX=AUTO;//The modification
of the interface working mode leads to the failover of boards. Make sure that the
standby board works properly before you change the interface working mode.
The network interfaces on IFM boards and the network interfaces on the corresponding
boards of the MGW must be allocated to the same independent VLAN. If the MGW has only
one frame, the corresponding boards are E8T boards; if the MGW has multiple cascaded
frames, the corresponding boards are MPU boards.
Assume that the UAP8100 has multiple pairs of IFM boards: some IFM boards are used for
communicating with the MGW and others are used for communicating with other softswitch
devices, the SG, and the CTI platform. In this case, the network interfaces on the IFM boards
that are used for communicating with the MGW and the network interfaces on the
corresponding boards of the interconnection device must be allocated to an independent
VLAN.
The following describes the allocation of VLANs of switches.
At least two VLANs should be planned for a UAP8100 network. The network interfaces on
IFM boards and the network interfaces on the corresponding boards of the MGW must be
allocated to the same independent VLAN. If the MGW has only one frame, the corresponding
boards are E8T boards; if the MGW has multiple cascaded frames, the corresponding boards
are MPU boards.
VLAN No.
Contained Network Interfaces
VLAN1
HSC, CTI, FS, BAM, cascade interface and so on
VLAN2
IFM, E8T/MPU, and cascade interface
If the SIGTRAN networking is used on site, multiple pairs of IFM boards might be
configured. In that case, an additional VLAN is required to accommodate the SIGTRAN
network.
The IFM boards and the user-bearing E8T boards that the SIP trunk uses might be directly
connected to the switch in the NGN network. In that case, check whether the VLAN allocated
to the connected switch is correct.
An independent VLAN must be allocated for the IFM network interfaces that bear SIP
signaling and the bearing network interfaces of the E8T boards in the condition described as
follows:
The network that interconnects with the UAP8100 is a PSTN or PLMN network.
SIP broadband agents are used.
The MGC has two pairs of IFM boards.
In addition, the network interfaces of the SBC server must be connected to the VLAN
network.
Note that the cascade interface on the switch must be configured to transparently transmit data
to all the preceding VLANs.
2008-12-02
Page 32 of 212
3.5 Installation of the SBC

See the corresponding manual of the network security product: Quidway SessionEngine2300
Session Border Controller Installation Guide.
Documentation > Core Network Product Line > Fixed Core Network NGN >
SessionEngine SBC > Product Manual
3.6 Configuration of the DIP Switches of

Devices Before the UAP8100 Is Powered On
Before you power on the UAP8100, configure the following DIP switches of devices:
DIP switch for specifying the device number and frame number of the MGC
DIP switch for specifying the frame number of the MGW
DIP switch of an EPI board
DIP switch of an ERI board
DIP switch for specifying the grounding mode, matching resistance, and link attributes
of E1 lines for E32 boards
3.6.1 Mapping Between Device Numbers and Frame

Numbers of the MGC
Before you power on devices, make sure that the DIP switches for specifying device numbers
and frame numbers on all SIU boards of the MGC are correct.
An SIU board provides a 5-bit DIP switch, S3, for specifying frame numbers. Figure 1.1
shows the mapping between DIP switch settings and frame numbers. In addition, an SIU
board provides a 3-bit DIP switch for specifying device numbers. Figure 1.2 shows the
mapping between DIP switch settings and device numbers.
Figure 1.1 Mapping between DIP switch settings and frame numbers of the SIU board
DIP Switch
Bit
ON
ON
ON
ON
ON
ON
ON
ON
ON
OFF
ON
ON
ON
OFF
ON
ON
ON
ON
OFF
OFF
ON
ON
OFF
ON
ON
ON
ON
OFF
ON
OFF
ON
ON
OFF
OFF
ON
Frame No.
2008-12-02
Page 33 of 212
DIP Switch
Bit
ON
ON
OFF
OFF
OFF
ON
OFF
ON
ON
ON
ON
OFF
ON
ON
OFF
10
ON
OFF
ON
OFF
ON
11
ON
OFF
ON
OFF
OFF
12
ON
OFF
OFF
ON
ON
13
ON
OFF
OFF
ON
OFF
14
ON
OFF
OFF
OFF
ON
15
ON
OFF
OFF
OFF
OFF
16
OFF
ON
ON
ON
ON
17
OFF
ON
ON
ON
OFF
Frame No.
Figure 1.2 Mapping between DIP switch settings and the device numbers of the SIU board
DIP
Switch Bit
ON
ON
ON
ON
ON
OFF
ON
OFF
ON
ON
OFF
OFF
OFF
ON
ON
OFF
ON
OFF
OFF
OFF
ON
OFF
OFF
OFF
Device
No.
The configuration of the DIP switch for specifying the SIU device numbers must be planned globally. If
the SIU device number is set to X, the IP addresses for communicating with the host of the
corresponding BAM is 172.2X.200.0 and 172.3X.200.0. For example, if the SIU device number is set to
3, set the device number of the BAM to 3 when the BAM is installed. Then the IP addresses of the
network adapter for communicating with the host of the BAM are 172.23.200.0 and 172.33.200.0.
2008-12-02
Page 34 of 212
3.6.2 Configuration of MGW Frame Numbers

Before you install the software, check the MGW frame number. Make sure that the bits of the
DIP switch are correctly set. The rule for setting the DIP switch is as follows:
For a UAP8100 MGW frame, the four bits on the left (SW1 to SW4) are for specifying the
frame number; the four bits on the right (SW5 to SW8) are not used now and must be set to
OFF. A frame number is a binary value consisting of four bits, that is, frame number = (SW4)
(SW3)(SW2)(SW1). For the DIP switch, if a bit is set to ON, the corresponding value is 0; if a
bit is set to OFF, the corresponding value is 1. Figure 1.1 shows the mapping between frame
numbers and the settings of the DIP switch.
Figure 1.1 Mapping between the frame numbers and the settings of the DIP switch of the
UAP8100 MGW
Setting of DIP Switch Bits
Binary
Value
Frame
No.
SW4
SW3
SW2
SW1
ON
ON
ON
ON
0000
ON
ON
ON
OFF
0001
ON
ON
OFF
ON
0010
ON
ON
OFF
OFF
0011
ON
OFF
ON
ON
0100
ON
OFF
ON
OFF
0101
ON
OFF
OFF
ON
0110
ON
OFF
OFF
OFF
0111
OFF
ON
ON
ON
1000
3.6.3 Description of the DIP Switchs of a FAN Box

The first three bits of the DIP switchs S1 in fan box are used to set the address information,
generically, the address information is set to 1. For the DIP switch, if a bit is set to ON, the
corresponding value is 0; if a bit is set to OFF, the corresponding value is 1. The forth bit S1-4
is used to set the blast mode of the fan, the fan of UAP8100 MGW sends blast upwards, S1-4
is set to OFF. The below table shows the settings of the DIP switchs.
The configuration of address infomation
Blast mode
S1-1
S1-2
S1-3
S1-4
OFF
ON
ON
OFF
If there is mistake in the settings of the DIP switchs, the UAP cant monitor the state of the
fan.
2008-12-02
Page 35 of 212
3.6.4 Description of the DIP Switchs of an EPI Board

Figure 1.1 Description of the DIP switches of an EPI board
DIP
Switch
Description
Setting
S1
DIP switch for

specifying whether to
ground the cover of the
receiving cable of the
E1 line on an EPI board.
For 75-ohm coaxial cables, set S1 to ON,

which indicates grounding the cable cover.
(ON is the default value.)
For 120-ohm twisted pairs, set S1 to OFF,

which indicates not grounding the cable
cover.
DIP switch for

specifying whether to
ground the cable cover
of the sending cable of
the E1 line on an EPI
board.
For 75-ohm coaxial cables, set S2 to ON,

which indicates grounding the cable cover.
(ON is the default value.)
For 120-ohm twisted pairs, set S2 to OFF,

which indicates not grounding the cable
cover.
DIP switches for

selecting the trunk cable
type
For 75-ohm coaxial cables, set S3 to OFF,

set S4 to ON, and set the first and second
bits of S5 to ON.
For 120-ohm twisted pairs, set S3 and S4 to

OFF, set the first bit of S5 to OFF, and set
the second bit of S5 to ON.
S2
S3, S4, S5
The 120-ohm trunk interface board is not grounded. Therefore, if the E1 line to which an EPI
board connects is a 120-ohm twisted pair, make sure that S1 and S2 are set to OFF. Generally,
120-ohm twisted pairs are used for the deployment in countries except China. The factory
settings of an EPI board are for 75-ohm E1 lines. Check the settings of the DIP switches and
the line mode of the digital distribution frame (DDF) and connected devices.
3.6.5 Description of the DIP Switches of an ERI Board

Figure 1.1 Description of the DIP switches of an ERI board
2008-12-02
DIP
Switch
Description
Setting
S2, S3, S4
DIP switches for

selecting the trunk
For non-balancing coaxial cables of 75 ohms, set

S2, S3, and S4 to ON.
Page 36 of 212
DIP
Switch
S5
Description
Setting
cable type
For balancing coaxial cables of 120 ohms, set S2,

S3, and S4 to OFF.
Bit 1: for
specifying the
mode of cyclic
redundancy check
(CRC)
ON: disabling the CRC check function
OFF: enabling the CRC check function
Bit 2: for
specifying the type
of the connected
E1 lines
ON: The connected E1 line is a non-balancing

coaxial cable of 75 ohms.
ON: The connected E1 line is a balancing coaxial

cable of 120 ohms.
NOTE
The setting of the second bit of S5 must be the same as
that of S2, S3, and S4.
The CRC check mode of ERI boards is not related to the type of the trunks that are connected
to the ERI boards, but the CRC check mode of ERI boards must match the frame format of
E32 boards that are connected to the ERI opposite side. If the CRC check function of ERI
boards is disabled, the frame format of the E32 boards must be set to DOUBLE_FRAME by
running SET E1PORT. If the CRC check function of ERI boards is enabled, the frame format
of the E32 boards must be set to CRC4_MULTIFRAME by running SET E1PORT.
If the frame formats of E32 boards and ERI boards do not match, current noise might be heard
during conversation.
3.6.6 Description of the DIP Switches of an E32

Board
For E32 boards, DIP switches must be used to set the grounding mode of E1 lines at the line
side, the resistance that matches E1 lines, and the enabling and disabling of the report of link
attributes. The methods of setting the DIP switches on E32 boards are different from those of
setting the DIP switches on EPI and ERI boards.
The following describes the methods of setting the DIP switches on E32 boards:
Setting the grounding mode of E1 lines

The DIP switches S2, S3, S4, and S5 on an E32 board are for specifying the grounding
mode of E1 lines at the line side. S2, S3, S4, and S5 are all 8-bit DIP switches. Each bit
of these DIP switches represents one E1 line.
Figure 1.1 shows the E1 line interface that each DIP switch controls.
2008-12-02
Page 37 of 212
Figure 1.1 E1 line interfaces that the DIP switches S2 to S5 control

DIP Switch
Helps to
S2
Control interfaces for E1 lines 16 to 23.
S3
S4
S5
Figure 1.2 shows the application of the settings of a DIP switch.

Figure 1.2 Application of the settings of a DIP switch
DIP Switch
Setting
Descriptio
n
Application
ON
Grounding
When 75-ohm cables are used, this setting indicates

the unbalancing mode.
OFF
Not
grounding
When 120-ohm cables are used, this setting indicates

the balancing mode.
Setting the resistance that matches E1 lines

The DIP switches S6 to S13 on an E32 board are combined to set the resistance that
matches E1 lines. These DIP switches are all 8-bit DIP switches. Every two bits of these
DIP switches represent one E1 line.
Figure 1.3 shows the E1 line interface that each DIP switch controls.
Figure 1.3 E1 line interfaces that the DIP switches S6 to S13 control
DIP Switch
Helps to
S6
Control the interfaces for E1 lines 24 to 27.
S7
The functions of the eight bits of S6 are described as follows:
Bits 1 and 5 control the interface for E1 line 24.

2008-12-02
Page 38 of 212
DIP Switch
Helps to
S8
S9

S10

S11

S12

S13

2008-12-02
Page 39 of 212
In Figure 1.4, the first and fifth bits that are used to set the matched resistance of E1 lines
are taken as an example to describe the usage of the DIP switch S6.
Figure 1.4 Application of the settings of S6
DIP Switch Setting
Application Scenario
ON
ON
When the E1 line 24 uses a 75-ohm cable
OFF
ON
When the E1 line 24 uses a 120-ohm cable
Enabling or disabling the report of link attributes

Upper layer software determines to which interface that an E32 board is set according to
the setting of the DIP switch S14 on the E32 board. The DIP switch S14 has 8 bits.
Currently, only the first two bits are used.
Figure 1.5 shows the application of the settings of S14.
Figure 1.5 Application of the settings of S14

DIP Switch Setting
Application Scenario
ON
ON
When 75-ohm cables are used
OFF
ON
When 120-ohm cables are used
The resistance of the 32 E1 lines that are connected to an E32 boards must be the same. The
system does not support E32 boards that are connected to E1 lines of different resistances.
3.7 Points for Attention When Installing the

UAP8100 Hardware
Before installation, familiarize yourself with the Site Survey Report and pay attention to
the following points:
Position and status of the UAP8100 in the network
Type of the interfaces for lines
Length of different types of cables
In addition, check whether the requirements of customers for devices change

significantly before the installation.
2008-12-02
For the UAP8100 MGC and MGW, certain boards must be inserted exactly in the
specified front or back frames and slots. Make sure that these boards are inserted
Page 40 of 212
according to the requirements before you power on the boards; otherwise, the boards
might fail to work or be burned.
Before loading boards of the UAP8100 MGW, connect the PC to the OMU board
through a serial port and set the type of the corresponding slots to mobile network
application or fixed network application. The current UAP8100 integrates the features of
fixed networks. All boards on the UAP8100 can be set to FXXX (fixed network
application). Generally, the board types are set for fixed network application. Do not
change the board types; otherwise, the board cannot work properly.
For the UAP MGC BAM,
The network interface with the IP address 172.2X.200.0 is connected to the 5624-0
switch and the 5624-0 switch is connected to the 9-slot HSC board. This forms a host
plane.
The network interface with the IP address 172.3X.200.0 is connected to the 5624-1
switch and the 5624-1 switch is connected to the 7-slot HSC board. This forms a
standby plane.
The DDF frame must be grounded. If the DDF frame is not grounded and is inserted in
the same cabinet of the UAP8100, the trunk head might be damaged if the cabinet is
powered on after powered off.
Currently, there are two versions of MGW: old MGW (delivered before March, 2008) and
new MGW (delivered after March, 2008):
For an old MGW, on-site engineers must connect the power cable and monitor cable to
the fan frame in the SSM frame. For the connecting method, see the UAP8100 Hardware
Installation Manual of the UAP R003.
For a new MGW, the fan frame in the SSM frame has no power input port or monitor
port, and the frame transfer box has no power output port for the fan frame. The power
cable and monitor cable of the fan frame are inside the SSM frame. On-site engineers do
not need to connect cables to the fan frame.
Figure 1.1 Rear view of the fan frame of an old MGW
2008-12-02
Page 41 of 212
Figure 1.2 Rear view of the fan frame of a new MGW
2008-12-02
Page 42 of 212
3.8 Connection of the Alarm Box

3.8.1 Overview of the Alarm Box
The mechanism that the UAP8100 MGC uses to communicate with the alarm box is similar to
that used by the UAP8100 MGW. Therefore, a PC cannot be simultaneously connected to the
UAP8100 MGC alarm box and the UAP8100 MGW alarm box using serial port cables.
Appearance of the Alarm Box and Its Interfaces

Figure 1.1 Appearance of the alarm box
2008-12-02
Page 43 of 212
Figure 1.2 Interfaces of the alarm box
Interface 1: for controlling the alarm box

volume
Interface 3: RS-232 serial port
Interface 2: for specifying the usage of serial ports in the

interfaces 3 and 4
Interface 4: RS-422 serial port
Control of the Alarm Box Volume

RP1 and RP2 are used to control the alarm box volume. RP1 is used to control the volume of
the horn that is connected to JT9. RP2 is used to control the volume of the horn that is
connected to JT10 or the volume of the remote sound box. The methods of volume adjustment
are as follows:
Turning up the volume

Use a cross screwdriver to turn RP1 or RP2 counterclockwise, that is, from 3 to 1 (the
numbers displayed on the potentiometer).
Turning down the volume

Use a cross screwdriver to turn RP1 or RP2 clockwise, that is, from 1 to 3 (the numbers
displayed on the potentiometer).
3.8.2 Connection of the UAP8100 MGC and the Alarm

Box
The communication between the UAP8100 MGC and the alarm box is realized by the
connection between the UAP810 MGC BAM or WS and the RS-232 interface of the alarm
box.
2008-12-02
Page 44 of 212
Connection Cable
A connection cable is a serial port cable that is shipped with the alarm box. One end of the
cable is a DB9 connector for the BAM or WS; the other end is an RJ-45 connector for the
alarm box.
The serial port cable might be separated from the alarm box when delivered. Find the serial port cable in
the cable box.
Configuration of the RS-232 Interfaces of an Alarm Box

An alarm box provides four RS-232 interfaces: J4, J5, J6, and J7. These interfaces are
controlled by S1 and S2.
Figure 1.1 Configuration of the RS-232 interfaces of an alarm box
Number of Enabled
Interfaces
Configuration of S1 and S2
1 (J5)
2 (J5 and J6)
3 (J4, J5, and J6)
J7 is a standby RS-232 serial port, which is not used now. When the alarm box requires more RS232 serial ports, enable J7 by upgrading the software of the alarm box to ensure normal
communication.
The preceding configuration of DIP switches is for Chinese voice alarms. For English voice alarms,
the sixth bit of S2 must be set to ON.
The configuration of the announcement for abnormal system exit, debug serial port, and DY5
interface of the preceding DIP switches is out of the scope of this document. For the configuration of
these items, see the Universal Alarm Box User Manual.
Configuration of the UAP8100 MGC

Before you configure the UAP8100, make sure that the alarm box is connected to the serial
port of the BAM or WS.
To configure the UAP8100, do as follows:
Step 1 Choose the following on the BAM: START > program > U-SYS UAP8100 MGC
Operation and Maintenance Center > U-SYS UAP8100 MGC Server Gateway Tool.
2008-12-02
Page 45 of 212
Alternatively, choose the following on the WS: START > program > U-SYS UAP8100
MGC Operation and Maintenance Center > U-SYS UAP8100 MGC Workstation
Gateway Tool.
The window for configuring the gateway is displayed.
Step 2 Choose Connection > Create. Then set the parameters of the gateway for connecting the
alarm box according to Figure 1.1.
Figure 1.1 Setting of the parameters of the gateway for connecting the alarm box
Parameter
Setting
Serial port
Select the actual serial port that connects to a terminal on the

alarm box. For example, COM1.
BAM IP address
Type the IP address of the BAM, that is, the IP address that is
used for communicating with the terminal.
Client application type
Select New AlarmBox Class.
Baud
Select 19200.
Data bit
Select 8.
Parity
Select None.
Stop bit
Select 1.
Step 3 Click Create, as shown in Figure 1.1.

Figure 1.1 Setting the UAP8100 MGC serial port
2008-12-02
Page 46 of 212
----End
The gateway communications tool Convert.exe is in the installation path of the UAP8100
MGC BAM (D:\UAP8100 by default). To connect the alarm box to the WS, do as follows:
Copy the files Convert.exe and ConvertResDll.dll in D:\UAP8100 of the BAM to the
corresponding installation path of the UAP8100 MGC client (D:\UAP8100 by default). Then
run Convert.exe.
3.8.3 Connection of the UAP8100 MGW and the

Alarm Box
Connection Mode
The UAP8100 MGW and the alarm box can be connected in the following two modes:
Alarm box connecting to the LMT alarm subsystem

If the alarm box is connected to the LMT alarm subsystem, the UAP8100 MGW reports
alarm information to the LMT and the LMT forwards the alarm information to the alarm
box. The PC where the LMT alarm subsystem is installed communicates with the alarm
box using the RS-232 serial port. The configuration of the connection cable and the
alarm box serial box is the same as that described in section 3.8.2"Connection of the
UAP8100 MGC and the Alarm Box."
Alarm box connecting to the BAM in the main control frame of the UAP8100 MGW
The alarm box and the UAP8100 MGW are connected as follows:
The alarm box interface ALARM provided by the filtering box at the back of the main
control frame of the UAP8100 MGW is connected to the serial port of the alarm box
based on RS-422. The alarm information about devices including other service frames is
reported to the alarm box through the alarm signal interface that the main control frame
provides.
Figure 1.1 shows the two modes for connecting the UAP8100 MGW and the alarm box.
Figure 1.1 Two modes for connecting the UAP8100 MGW and the alarm box
2008-12-02
Page 47 of 212
Configuration of the RS-422 Interfaces of the Alarm Box

When the alarm box is connected to the UAP8100 MGW, the alarm box provides four RS-422
interfaces: JT6, JT7, JT8, and JT11. These interfaces are controlled by S1 and S2.
Figure 1.1 Configuration of the RS-422 interfaces of an alarm box
Number of
Enabled
Interfaces
Configuration of S1 and S2
1 (JT6)
2 (JT6 and JT7)
The preceding configuration of DIP switches is for Chinese voice alarms. For English voice alarms,
the sixth bit of S2 must be set to ON.
The configuration of the announcement for abnormal system exit, debug serial port, and DY5
interface of the preceding DIP switches is out of the scope of this document. For the configuration of
these items, see the Universal Alarm Box User Manual.
Alarm-Box-Control Configuration of the UAP8100 MGW

Before you configure the UAP8100 MGW, make sure that the alarm box is connected to the
UAP8100 MGW.
To configure the UAP8100 MGW, do as follows:
Step 1 Set the position of the alarm box.
Run the MML command SET BOXPOS to set the position of the alarm box. The position
that is set in the software must be the same as the actual position of the alarm box.
When the alarm box is connected to the LMT, set the position parameter to LOC.
When the alarm box is connected to the BAM, set the position parameter to BAM
(default value).
Step 2 Configure the transfer of alarm information.

This step is required only when the alarm box is connected to the LMT.
Choose START > program > Huawei Local Maintenance Terminal > U-SYS UAP8100
MGW V300R003 > tools > Alert Transmit Tool.
2008-12-02
Page 48 of 212
If Alert Transmit Tool is not found in the displayed window, restart the LMT software
installation program, select Modify, and select the alarm transmission tool to be installed.
Then go to the next step.
When the alarm transmission tool is run for the first time, the system displays a dialog box for
configuring the transfer of alarm information. Alternatively, you can choose Operate >
configuration to display the dialog box.
Set the parameters in the dialog box according to the following instructions:
Host IP Address: Indicates the IP address of the BAM, that is, the IP address that
corresponds to the OMC interface on the back NET board in the main control frame of
the UAP8100 MGW. The LMT visits the host of UAP8100 MGW using this IP address.
Available COM Port: This parameter must be configured according to the serial port to
which the alarm box is connected on the PC where the LMT is installed.
Step 3 Set the control parameters of the alarm box of the UAP8100 MGW.
Choose Management > Alert Box Control from the menu bar.
The Alert Box Control dialog box is displayed. Set the parameters in the Alert Box Control
dialog box according to the following instructions:
2008-12-02
Box Location: Set Alert Box Location to BAM or LMT according to the cable
connection that is set in Step 1.
Switch Off Alarm Indicator: Select the alarm indicator of which alarm level that you
want to turn off.
Page 49 of 212
Step 4 Click OK.

The UAP8100 MGW sends control commands to the alarm box instructing the alarm box to
perform operations.
If the alarm transmission tool displays the message " COM communication normal, Alarm
transmit begins," it indicates that the alarm box is successfully connected.
Figure 1.1 Contents displayed when the alarm box is successfully connected
When the alarm box receives alarm information after the alarm box is connected, the alarm
indicator of the corresponding level on alarm box flashes and the horn sounds an
announcement to notify maintenance engineers of the alarm. After maintenance engineers are
informed of the alarm, they must stop the alarm announcement and turn off the alarm
indicator; otherwise, the alarm announcement goes on and the alarm indicator remains
flashing.
----End
The MML commands RST ALMBOX, CLR BOXLGT, and STP BOXSND can be run to reset the
alarm box, turn off the alarm indicator, and stop the alarm announcement respectively.
Configuration of Alarm Parameters of the UAP8100 MGW
A record of alarm parameter configuration contains details about an alarm, including the
alarm name, alarm ID, alarm level, alarm class, NMS class, shielding of the alarm, and
reporting of the alarm.
An alarm ID uniquely identifies a record of alarm parameter configuration.
Users can change only the alarm shielding flag and reporting flag in the record of alarm
parameter configuration. Other parameters in the record are read-only.
Figure 1.1 describes the basic operations about alarm parameter configurations.
2008-12-02
Page 50 of 212
Figure 1.1 Basic operations about alarm parameter configurations

Operation
Helps to
Querying for the settings of

alarm parameters
Query for the settings of the alarm parameters according to

the query conditions.
Changing the settings of

alarm parameters
Change the settings of the alarm shielding flag and reporting

flag.
Restoring the settings of

alarm parameters
Restore the default values of the alarm parameters.
To change the settings of alarm parameters, do as follows:

Step 2 Display the Alarms Configuration Query dialog box.
1.
Choose START > program > Huawei Local Maintenance Terminal > U-SYS
UAP8100 MGW V300R003 > U-SYS UAP8100 MGW Alert Management System.
2.
Choose Management > Alert configuration from the menu bar.

The Alarms Configuration Query dialog box is displayed, shown as follows:
Maximum Return Number indicates the maximum number of found records that you want the
system to display. For example, if the value of this parameter is set to 80 and the number of found
records is 100, the system displays only the first 80 records in ascending order of alarm IDs.
After you select a record of alarm ID information, you can restore the default configuration of the
alarm ID by clicking Reset.
Step 3 Query for alarm information.

In the Alarms Configuration Query dialog box, set the query conditions including Alarm
ID, Alarm Severity, Modified Flag, Maximum Return Number, Shielded Flag and Alarm
box flag. Click OK. The query results are displayed in the Alarm Configuration View
dialog box, as shown in the following figure:
2008-12-02
Page 51 of 212
Step 4 Modify the attributes of alarm information.

In the Alarm Configuration View dialog box, double-click a record of alarm information, or
click Modify after selecting a record of alarm information.
The dialog box for setting the basic information about the alarm is displayed.
In the dialog box for setting the basic information about an alarm, you can set the level of the
alarm, whether to shield the alarm, and whether to transfer the alarm to the alarm box.
----End
MML commands LST ALMCFG and RST ALMCFG can be used to query for and restore the settings
of alarm parameters.
2008-12-02
Page 52 of 212
Software Installation
This chapter describes how to install the software of the UAP8100, CTI3.4 platform, file
server, and OpenEye. For more details about the software installation, see the U-SYS
UAP8100 Universal Access Platform MGC Software Installation Guide, U-SYS UAP8100
Universal Access Platform MGW Software Installation Guide, TopEng-Call Center
Installation Guide, FS Two-Node Cluster Installation Guide(V1.06,suse9sp3)-20080220, and
FS Single-Node System Installation Guide(V1.03,suse9sp3).
You can visit http://support.huawei.com to obtain the previous documents. The locations of
the documents are as follows:
> UAP&URP > Product Manual
> CTI > Version Release Document
> File Server > Technical Guide
4.1 Software Installation of the UAP8100 MGC

Figure 1.1 shows the procedure of installing the software of the UAP8100 MGC.
2008-12-02
Page 53 of 212
Figure 1.1 Procedure of installing the software of the UAP8100 MGC
Usually, the BAM software has been installed and debugged when in factories. To ensure
version matching and facilitate on-site deployment, however, the BAM server software was
uninstalled in factories. Therefore, on-site deployment personnel need to install only the BAM
server software. After the BAM is installed, install the SysPatron2000 and SetWin2000, and
perform security enhancement to servers. For the methods, see the operation guide in the
installation disk.
In the process of installing the BAM software, type the device number of the MGC according
to the actual setting of the physical DIP switch. Otherwise, the boards of the MGC cannot be
loaded with data.
2008-12-02
Page 54 of 212
Figure 1.2 Typing the device number
For details about re-installing the operating system and database, see the U-SYS UAP8100
Universal Access Platform MGC Software Installation Guide.
To load software and data to the host, see the procedure shown in the following figure.
2008-12-02
Page 55 of 212
Figure 1.3 Procedure of loading software and data to the host through the BAM
4.1.1 Loading Data to Boards

Load the host program and data files on the BAM server to boards.
The content loaded to boards contains the following:
Software
Data
Conditions of Data Loading

Data loading is needed in one of the following conditions:
First installation of software during deployment

During deployment, install BAM server software on the BAM server. After installation,
the host program exists in the loading directory of the BAM server. Then configure data
when the BAM server is offline (You also can configure data by using script files.). After
configuration, run the FMT command. Then data files are generated in the loading
directory of the BAM server.
Run the LON command to load the host program and data files to boards.
Software upgrade
During software upgrade, upgrade the BAM server software first. Then load the host
program and data files in the loading directory of the BAM server to foreground devices
to update the program and data on the foreground devices.
Loading of certain modified data

When boards run normally, the loading of certain data is performed online on the BAM,
and the data will take effect on corresponding boards at the same time. Some data,
2008-12-02
Page 56 of 212
however, can take effect on the boards only after the boards restart. For example, if you
run the MOD PUBPRM command to change the public parameter table, the change can
take effect only after the boards restart.
Methods of Loading Data

When the boards restart, they send the requests of loading programs and data to the BAM. To
response to the requests, the BAM sends the status information about the soft switches to the
corresponding boards. Then the boards load programs or data according to the status of soft
switches.
Usually, you can restart boards in two ways to load programs and data: resetting the boards
and powering off the boards. When the boards restart, the programs and data are loaded to the
RAM of the boards. The programs and data can be from the FLASH or from the BAM server.
There are four soft switches: program available, data available, program writable, and
data writable (the programs and data are in the FLASH). They are used for selecting the
loading path of programs and data.
After the first power-on of a board, there is no program and data in the FLASH of the board,
or there are programs and data in the FLASH but the version is incorrect. In such case,
programs and data can be loaded from the BAM server to boards. The settings of soft
switches are shown in the following table.
Figure 1.1 Settings of soft switches during the first power-on of boards
Soft Switch
Status
Program available
OFF
Data available
OFF
Program writable
ON
Data writable
ON
The soft switches of program available and data available are set to OFF, so the programs
and data are loaded to the RAM board from the BAM, and are written into the FLASH of the
board at the same time.
After the boards run normally, the settings of soft switches are shown in the following table.
Figure 1.2 Settings of soft switches during normal running of boards
2008-12-02
Soft Switch
Status
Program available
ON
Data available
ON
Program writable
OFF
Data writable
ON
Page 57 of 212
The soft switches of program available and data available are set to ON. The priority of the
FLASH is higher than that of the BAM, so the programs and data are loaded to the boards
from the FLASH. The soft switch of data writable is set to ON so that the data set online can
also be written into the FLASH. The data in the FLASH is updated all the time.
Certainly, you can select to load programs and data from the FLASH or BAM server
according to the actual needs.
The loading control switch is a soft switch, which is set on the maintenance console. Run
the MOD LSS command to change the setting of the switch for selecting loading paths,
and run the LST LSS command to view the setting.
To load data to boards, you can run the RST BRD command to reset the boards. Do not
directly pressing the reset buttons.
If the VRB board is running, do not run the LOF command. You can configure parameters
online and then run the FMT command.
Description of Data Files for Loading

The DATA directory in drive D of the BAM server stores the to-be-loaded files of the MGC
on the UAP8100. The files include board programs and data.
For example, the s3000.smu file is the program file of the SMU; the smubios2.bin file is the
level 2 BIOS file of the SMU; the Db_?.dat file contains the data loaded to modules; the
Db_73.dat file is the data file of module 73.
After the server program runs, the data configuration files used by the MGC, such as Db_?.dat, are
generated according to the commands run by operators. Do not modify or delete the files in the DATA
directory.
Paths for Loading Data

Figure 1.1 shows the network interface of the SMU is e0, and network interface of the rear
board (SIU) of the SMU is e1. The solid lines indicate the network cables, and the dashed
lines indicate the loading paths. The network port of the SMU (the network port at the top of
the SIU) in slot 6 or slot 8 connects to the HSC in slot 9, and the network port at the bottom of
the SIU connects to the HSC in slot 7.
The IP addresses of the two network adapters of the BAM for connecting with the MGC are
172.2X.200.0 and 172.3X.200.0 respectively. The subnet mask is 255.255.0.0.
The BAM uses the network port 172.2X.200.0 to load the programs and data of the SMU0 in
slot 6 through path 1, and uses the network port 172.3X.200.0 to load the programs and data
of the SMU1 in slot 8 through path 2.
When the default path is unavailable, the programs and data of the SMU0 in slot 6 are loaded
through path 3, and those of the SMU1 in slot 8 are loaded through path 4. The programs of
the VRB board and its pinch board are loaded through the resource sharing bus.
2008-12-02
Page 58 of 212
During data loading, the SMU uses a temporary IP address. After loading, the IP address of the SMU
in slot 6 is 172.2X.200.the module number of the SMU in slot 6, and the IP address of the SMU in
slot 8 is 172.2X.200.the module number of the SMU in slot 8.
The default IP address of the SMU in slot 6 on the basic shelf is 172.2X.200.2, and that of the SMU
in slot 8 on the basic shelf is 172.3X.200.2.
Figure 1.1 Loading path diagram
Preparation for Loading Data

Before power-on and data loading, you need to:
Check the hardware.

Check whether the physical connections of the major boards are correct.
2008-12-02
Check the software versions and hardware versions according to the version
configuration table (provided by Huawei) before inserting boards into the shelf.
Insert boards into the shelf.
Make sure that the BAM software is installed and works properly. Make sure that the
Exchange process of the BAM runs normally.
Make sure that the to-be-loaded files, including the programs and data, exist in the
DATA directory. The name format of the to-be-loaded files is db_?.dat (the question
mark "?" indicates a module number).
Page 59 of 212
Do not change the IP address of the BAM; otherwise, the data loading may be failed.
During deployment, you can use script files to generate the files for loading. The procedure is as
follows:
-Run the LOF command to set the BAM server to be offline.
-Run the SET CWSON:SWT=OFF command to disable the alarm switch.
-Run the SET FMT:OFF command to disable the format conversion switch.
-Run the command for batch processing, and run the script files provided by Huawei.
-Run the LON command to enable the alarm switch and format conversion switch.
-Run the FMT command.
The file db_?.dat is generated.
You can also configure data offline. After data configuration, run the FMT command.
Procedure of Loading Data

During deployment, to locate the problems occurring in data loading, you can load data to
shelves one by one. The procedure is as follows:
Step 1 Power on the basic shelf. After loading, observe whether the boards in the shelf work
properly.
Step 2 Power on the service shelves one by one. After loading, observe whether the boards in the
shelves work properly.
Step 3 Check versions of the software loaded to boards.
Check whether the software versions are consistent with those in the version configuration
table. In case that the software version of a board is inconsistent with that in the version
configuration table, if the soft switches of program unavailable and data unavailable are set
to OFF, reset the board and reload data to it. Then you can run the commands DSP BRDVER
and DSP EXVER to check the software versions on the boards and software versions of all
the modules respectively.
Step 4 Perform CRC to the data of a board. If the operation fails, reset the board and reload data to it.
Run the STR CRC command to start the CRC, and run the STP CRC command to stop the
operation.
If faults occur during the data loading of a shelf, you can power off the shelf. Then power on
the shelf after the problems are solved.
Troubleshooting
During troubleshooting, you need to pay attention to the information in the Exchange
window besides the indicators of boards.
If faults occur in the process of loading data, you can check the following items:
Whether the loading paths (including the physical connections) are correct, and whether
the boards work properly
Whether the data are configured correctly

If some key data is configured incorrectly, the data loading may be failed.
2008-12-02
Whether the to-be-loaded files of the BAM server are complete
Software parameters, such as the maximum number of tuples
Page 60 of 212
If the loading paths are correct, the data is configured correctly, and the DIP switches are set
correctly, you can use another board. If faults persist, the slot where the board is located may
be faulty.
If faults persist after you change a board, contact the technical support personnel. Do not
change hardware configurations.
----End
4.1.2 Loading BIOS Files to Boards

Overview
During building the UAP environment, upgrade the BIOS of the boards in shelves after
installing and configuring the SQL server (with its patches) and BAM software on the BAM
server. The BIOS files are loaded to two types of boards: system boards (SMU) and nonsystem boards. The BIOS files loaded to system boards and non-system boards are different.
The following describes the procedure of loading BIOS files to CSU boards. The non-system
boards for loading BIOS files include the IFM boards, CSU boards, VRB boards, and CDB
boards. The BIOS files loaded to these boards are the same.
Procedure of Loading BIOS Files

Step 1 Connect the serial port cables.
Connect the serial port cable of the BAM server to the serial port of the front board of the
BIOS which needs to be upgraded.
Step 2 Set the parameters of the HyperTerminal through the serial port of the BAM server.
Step 3 Start your PC, and run the HyperTerminal on the PC.
Choose Start > Program > Accessories > Communications > HyperTerminal. Then type a
name for the new connection in the window shown in the following figure.
2008-12-02
Page 61 of 212
Click OK, and select the serial port to be used. Then the system displays the following
window.
Set the parameters of the HyperTerminal in the window as shown in the previous figure.
Retain the default settings. Then click OK to access the winnow as shown in the following
figure.
2008-12-02
Page 62 of 212
Step 4 Restart the front board where the BIOS files need to be loaded, press the black button until the
following window appears.
If the window as shown in the following figure is displayed, press key D to stop loading.
2008-12-02
Page 63 of 212
Step 5 In the window as shown in the following figure, type loadXmodem, and then press Enter.
Step 6 In the window as shown in the following figure, right-click a blank area, and then choose
SendFile on the menu.
2008-12-02
Page 64 of 212
After that, the SendFile dialog box is displayed.
Type iobios.hdr in the Filename text box.

The iobios.hdr file is located in the Date directory in drive D. You can click Browse to select
it.
For the non-system boards, select the iobios.hdr file.
2008-12-02
Page 65 of 212
For the system boards, select the sysbios.hdr file.
Step 7 Select the protocol for loading BIOS files.

There are multiple protocols, and you can select Xmodem here. The Xmodem protocol is a
file transfer protocol. It is widely used for its good performance.
See the following figure.
2008-12-02
Page 66 of 212
Step 8 Select Send to upgrade the BIOS. See the following figure.
After upgrade, the system automatically loads data.
2008-12-02
Page 67 of 212
Then, the upgrade of the BIOS is completed.
4.1.3 Key Points During the Data Loading of the

UAP8100 MGC
Make sure that the to-be-loaded files exist in the DATA directory. The files include
programs and data. The name format of the to-be-loaded files is db_?.dat (the question
mark "?" indicates a module number).
During deployment, use script files to generate the files for loading.
Run the LOF command to set the MGC to be offline.
Run the SET CWSON:SWT=OFF command to disable the alarm switch.
Run the SET FMT:OFF command to disable the format conversion switch.
Run the command for batch processing, and run the script files provided by Huawei.
After that, run the LON command to enable the alarm switch, format conversion
switch. Run the FMT command. Then the file db_?.dat is generated.
You can also configure data offline. After data configuration, run the FMT command.
2008-12-02
If the BIOS version of a board is incorrect, run the CLR BIOSL2 command to clear the
level 2 BIOS of the board. Then reset the board and reload data.
After changing a device number, restart the board and the BAM. If the BIOS on boards
are not the latest level 2 BIOS, load the level 2 BIOS files.
Page 68 of 212
4.1.4 Typical Cases

Failure to Load Data to Boards Because the IP Address of the
BAM Server Is Not Set
Symptom
Data cannot be loaded to the boards. The serial port log shows that the connection to the
BAM server is failed.
Handling Process
Check the network connection between the BAM and the MGC, and check the
connection between the SMU and the HSC.
Check the IP addresses of the two network adapters of the BAM.

The IP addresses of the two network adapters are 172.2X.200.0 and 172.3X.200.0
respectively.
Check the to-be-loaded files.

The files should exist in the DATA directory of the BAM.
Failure to Access File Servers After the Failover of the Two-Node

Cluster
Symptom
After the failover of the two-node cluster, the boards cannot access file servers.
Cause Analysis
This is a bug of the Veritas two-node cluster software. Because of the bug, the mount
information of the NFS service of the two-node cluster cannot be synchronized. After the
failover (switchover), the boards fail to connect to file servers because the client does not
register on the active file server.
Handling Process
Copy the file /var/lib/nfs/rmtab on the active server to the standby server. You need to perform
this operation every time when you add a board.
Failed Switchover of the Two-Node Cluster Because the Mount

Operation Is Performed Manually
Symptom
Switchover of the two-node cluster is performed in the graphics interface of the VCS, but the
switchover is failed.
Cause Analysis
It is failed to unmount devices on the active server.
2008-12-02
Page 69 of 212
Handling Process
Step 1 Check the logs of the two-node cluster.
The cause of failed switchover is failure to unmount a device. The system displays a message
indicating that the device is busy.
Step 2 Check the resource dependency between the two nodes of the cluster.
The resources shared through the NFS protocol and the resources shared through the SMB
protocol must be offline before the mount resource.
Step 3 Communicate with on-site operators, finding that the mount operation is performed manually
before switchover.
Step 4 Take other resources offline, and run the umount l command. Then run the mount
command.
The device is uninstalled successfully.
Step 5 Take the resources online and perform the switchover of the two-node cluster.
No faults are found.
----End
Failure to Access the Graphic Interface After Adding Fiber

Storage Devices to the /etc/fstab File
Symptom
After a server is installed and restarted, it fails to display the graphics interface. The system
displays a message indicating that fsck /dev/sdc1 fails.
Cause Analysis
The device driver /dev/sdc1 corresponds to the fiber storage device. The device driver is
loaded after the /etc/init.d/boot.local file is run. The /etc/fstab file, however, is scanned before
the /etc/init.d/boot.local file is run. If the device driver /dev/sdc1 is added to the fstab file, it
fails to check the file system.
Handling Process
Run the mount -o remount,defaults / command to mount the root disk to read-write mode
Delete the content of /dev/sdc1 in the /etc/fstab file. The mount operation of /dev/sdc1 is
performed by the two-node cluster script.
4.2 Software Installation of the UAP8100 MGW

4.2.1 Overview
The BAM of the UAP8100 MGW works in server/client mode. Different from the
server/client mode of UAP8100 MGC, the server of the MGW runs on the OMU which has its
own operating system and storage device. The tables required by the MGW are directly stored
2008-12-02
Page 70 of 212
in the memory. Thus the efficiency is improved. The client is the LMT which runs on the
terminal workstation. The LMT implements the functions of data configuration and
maintenance management through connecting with the host.
The software installation of the UAP8100 MGW includes the LMT software installation,
manual loading of OMU board software, and loading of host software (other board software).
Usually, the lower layer support software and hardware logic are loaded to the UAP8100
MGW in factories. The software of the MGW should be installed or upgraded on site
according to the networking application and software version changes. Besides the lower
layer support software, other software needs to be loaded to or installed on the UAP8100
MGW. For the procedure for installing software, see the following figure.
Figure 1.1 Procedure for installing software on the UAP8100 MGW
4.2.2 Loading Software to the OMU Manually

The software installation of the OMU is completed in factories. The software includes the
device management software, service board software, and some configuration files. If the
active OMU works properly after power-on, it is unnecessary to reload software to the OMU
manually. If the OMU cannot be started, you can load software to the OMU.
For the procedure for loading software to the OMU, see the following figure.
2008-12-02
Page 71 of 212
Figure 1.1 Procedure for loading software to the OMU manually
Introduction to the OMU

The OMU is a core management unit. It manages and maintains the UAP8100 MGW, and
provides interfaces for the LMT system and the I2000.
Only when the OMU can be started properly, the host software of the UAP8100 MGW can be
installed and other boards can be started. The installation and upgrade of software for other
boards also require the cooperation of the OMU.
The upper layer software of the OMU includes the following:
momu.vfs: the host software
momu_hddrv.rbf: the hard disk logic software
momu_ebootrom.bin: the extended BootROM software
momu_VxWorks_l: image file of the lower layer operating system
Make sure that the previous software is complete and the versions are correct. Then you can
prepare for the software loading.
The connection between the OMU and the LMT is shown in the following figure.
2008-12-02
Page 72 of 212
Figure 1.1 Connection between the OMU and the LMT
OMC
COM
NET
OMU
FE0
FE1
FE2
LMT
COM
The OMU has a serial port for debugging external systems. This serial port is near the handle
bar. The two RJ45 connectors are located on the front board OMU and the rear board NET
respectively. The FE0 interface on the front board OMU is used for loading software to the
OMU. The IP address of the OMU is set on the terminal to which the serial port connects.
Actually, the IP address is that of the FTP server. The OMC interface on the rear board NET is
used for the communication between the LMT and the host. The IP address of the NET can be
set in the mml.txt file by running the ADD IPADDR command, set on the LMT by running
the ADD IPADDR command, or set in the HyperTerminal.
Preparation for Loading Software to the OMU Manually

Before loading software to the OMU manually, you need to perform the following operations:
Install the LMT to the PC.
Copy all the files and subdirectories under the BAM directory on the computer where the
versions are obtained to the directory with the same name (usually the BAM directory in
drive C) on the PC.
This directory stores the configuration files of all the versions and the destination files
required in software loading.
Manually change the IP address in the mml.txt file under C:\BAM on the PC, and then
allocate this IP address to the network interface of the NET board through software loading.
Before the OMU is started, the IP address of the network interface on the NET board cannot
be set by running the MML command. Therefore, you need to manually change the IP
address.
You can run the following command to change the IP address in the mml.txt file:
2008-12-02
Page 73 of 212

ADD
IPADDR
:
BT=OMU,
MASK="255.255.255.0";
BN=0,
IFT=ETH,
IFN=0,
IPADDR="10.110.86.253",
This IP address corresponds to that of the maintenance interface (OMC interface) on the NET
board. It is used for the OMU to connect to the LMT after the OMU is started.
Change the name of the license_fix.ini file in C:\bam\license\ppc to license.ini, and save
the license.ini file to the path C:\bam\license.
There is no license file in the BAM directory, so you need to perform this operation.
Otherwise, the system will display errors during software loading.
Coy the filelist.txt and momu_vxWorks_l files released together with versions to a
directory of the same level with the BAM directory.
For example, if the BAM directory is in C:\, this directory is also in C:\.
Connect the debugging network interface on the OMU to the network interface on the
PC by using a crossover cable when loading data to the BAM manually.
Install an FTP server on the PC and configure it. Copy all the files in the BAM directory
to the root directory (usually the BAM directory in drive C) of the FTP server, and set
the user name and password for logging in to the FTP server. For example, set the user
name to BAM, the password to BAM, and the path for uploading files to C:\. Use the
wftpd32 software to start the FTP server.
Use serial cables to connect the debugging serial portCOM0 on the OMU to the serial port on
the PC. Start the HyperTerminal on the PC to view the debugging information during software
loading.
Procedure for Loading Software to the OMU Manually

Step 1 Reset the OMU and start the BootROM.
If the OMU is powered on, reset the OMU. After the message "Booting from basic bootrom"
is displayed, you can use the HyperTerminal to view the start process of the OMU.
The words following the mark "//" are the description of the displayed information. In actual displaying,
these words do not exist.
//Some initial information generated when the OMU is started
The information includes the type of the main processor, the information about the
operating system, the date of version generation, the types of boards, the size of
memory, and the startup position.
Booting from basic bootrom...
Uncompessing...Done.
Enable data cacheAt
********************************************************************
HUAWEI UAP8100 MGW
System Boot
Copyright 2002-2005 Huawei Tech. Co., Ltd.

********************************************************************
CPU:
HuaWei UG01MMPU - MPC 750
vxWorks Version:
5.4.2
Creation date:
Dec 25 2003, 11:55:38
Board Type:
UG01MMPU
SDRAM Size:
512 M
Boot from:
Basic bootrom
//The information about checking hardware logic
Logic check......................success
2008-12-02
Page 74 of 212
//The versions of certain software

The software has been loaded and debugged by using dedicated devices in factories.
PCB
version....................Version : <UG01MMPU> REV 0
EPLD version....................Version : <EPLD> 100
Bootrom version..................1001
Extend Bootrom version...........1025
FPGA version.....................Version : <UG01MMPU> REV(IDE) 000
BSP version:.....................1.01.0
//The position of a board, including the frame number and slot number
Frame Number ...................1
Slot Number.....................8
//The information about the baud rate of serial ports
Debug serial baudrate............57600
//The following is the information about the IP address and MAC address
Debug network MAC address........90 61 fe 0 f7 8
Debug network IP address ........10.10.86.254
sysStartType is:1
Press ENTER key to stop auto-boot...
Step 2 Change the BSP configuration files of the OMU

After the BootROM is started, press any key within the last three seconds of auto booting to
access the BSP command menu. Use the command character p of the BSP to view the IP
address of the FTP server, user name, password, VxWorks image file name, and the IP address
of the debugging network interface that are configured. For other items, retain the default
settings. The following information is displayed:
[VxWorks Boot]: p
//Interface name
boot device
: fei
unit number
: 0
processor number
: 0
//VxWork image file name
file name
: momu_VxWorks_l
//The IP address of the debugging network interface FE0 of the OMU
This IP address is in the same network segment with that of the FTP server. It
cannot conflict with other IP addresses, especially the address of the OMC network
interface.
inet on ethernet (e) : 10.10.86.254
//This IP address can be the same as the previous one. It can also be 0.
inet on backplane
//The information
password
The FTP server is
IP address of the
host inet (h)
user (u)
ftp password (pw)
flags (f)
target name (tn)
(b): 0
about the FTP server, including the IP address, user name, and
installed on the PC, so the IP address of the FTP server is the
PC.
: 10.10.86.101
: bam
: bam
: 0x0
: umg750_0
If the previous settings are inconsistent with those on the PC, you can use the BSP command
character c to change the configuration items.
Usually, the information needs to be changed includes the file name, the IP address of the
network interface FE, the IP address of the FTP server, the user name and password for
logging in to the FTP server. For other information that is not changed, press Enter.
2008-12-02
Page 75 of 212
[VxWorks Boot]: c
boot device
: fei0
processor number
: 0
host name
: UMG001
file name
: momu_VxWorks_l
inet on backplane (b): 0
host inet (h)
: 10.10.86.101
gateway inet (g)
:
user (u)
: bam
ftp password (pw) (blank = use rsh): bam
flags (f)
: 0x0
target name (tn)
: umg750_0
startup script (s)
:
other (o)
:
Step 3 Download the momu_VxWorks_l file.

Use the BSP command character @ to download the momu_VxWorks_l file from the FTP
server.
[VxWorks Boot]: @
boot device
: fei0
unit number
: 0
processor number
: 0
//The momu_VxWorks_l file is downloaded from the FTP Server of the PC.
file name
: momu_VxWorks_l
inet on backplane (b): 0
host inet (h)
: 10.10.86.101
user (u)
: bam
ftp password (pw)
: bam
flags (f)
: 0x0
target name (tn)
: umg750_0
Attaching network interface fei0... done.
Loading... 2107879
//An error code may be included in the information.
The error code 0003 indicates that the FTP server is not started, 0212 indicates
that the user name or password of the FTP is incorrect, and 0226 indicates that the
file downloading path of the FTP server is incorrect.
Starting at 0x200000...
Host Name: bootHost
Attaching network interface fei0... done.
fei0 IP addr : 10.10.86.254
Attached TCP/IP interface to fei unit 0
Attaching network interface lo0... done.
Adding 4159 symbols for standalone.
Development System
VxWorks version 5.4.2
KERNEL: WIND version 2.5
Copyright Wind River Systems, Inc., 1984-2000
CPU: HuaWei UG01MMPU - MPC 750. Processor #0.
Memory Size: 0x4000000. BSP version 1.01.0.
WDB: Ready.
->
2008-12-02
Page 76 of 212
Step 4 Reset and restart the OMU.

After loading, the OMU resets automatically, and it restarts properly.
If the OMU restarts properly, the system will display the following information:
Reboot...
Booting from extended bootrom...
L2 cache testing...Ok!
press 't' to do SDRAM test:
SDRAM ECC start:
SDRAM ECC initialized.
Uncompressing...Done.
Enable data cache
Atta
*************************************************************************
CPU:
- MPC 750
vxWorks Version:
BSP Version in Ext btrm:
5.4.2
Version : V300R003B01D051
BSP Version in Bas btrm:

Creation date:
SDRAM Size:
Boot from:
Version : V100R003B02D020
Nov 10 2004, 20:56:55
512 M
Extended bootrom
Dynamic memory overload resume: 80

->
After the previous steps are performed, the software of the OMU is written into the hard disk
of the OMU, the hard disks are initialized, and some configuration files in the BAM directory
on the PC are uploaded to the hard disks of the OMU according to the description in the
filelist.txt file. In the previous operations, only partial configuration files are loaded. You
need to run the LOD TOBAM command to upload all the configuration files and destination
files that need to be loaded to the hard disk of the OMU.
Step 5 Install all the programs on the OMU.
After the OMU is started properly, connect it to the LMT, set the path of the FTP server to
C:\BAM before file transfer, and then upload all the programs to the hard disk of the OMU.
Connect the LMT to the UAP8100 MGW, and then run the following command on the MML
interface:
LOD TOBAM: VT="MS", SIP="10.10.86.101", UID="BAM", PWD="BAM";
In the command, 10.10.86.101 is the IP address of the FTP server.

You can run the LOD TOBAM command to load the basic voice files. By default, the special
file selection parameter is set to VPUT (VPU Tone).
2008-12-02
Page 77 of 212
When the LMT connects with the OMU, if the system prompts you to download configuration files,
click Do Not Download.
After you run the LOD TOBAM command, all the software and configuration files are uploaded to
the hard disk of the OMU. Uploading these files takes several minutes or more than ten minutes. The
LMT displays the message "Connection Timeout" during this period. This message, however, does
not indicate a fault.
On the LMT menu bar, choose System > Setting > Time Setting > MML Command
Timeout (20-600), and set the MML command timeout interval to 600 seconds to avoid
timeout messages. Then set the handshake interval (60-180s) to 180 seconds to avoid timeout
messages.
If the network quality is poor, a message indicating time-out may be displayed after 600
seconds. If such a message appears, you can observe the file transfer progress displayed on
the FTP server. If no message indicating successful file transfer is displayed on the FTP server
within several minutes, it indicates that the files are transferred completely and you can go to
the next step.
Load software to the standby OMU.
If the OMU works in active/standby mode, you need to load software to the standby OMU. To
load software to the standby OMU, you can synchronize the software on the active OMU to
the standby OMU.
Set the OMU to start in LOAD mode.

Run the following command on the LMT to set the OMU to start in the LOAD mode.
SET BRDSTART: MOD=LOAD;
Start the standby OMU.

Insert the standby OMU to a slot. Then the standby OMU powers on and starts
automatically. At that time, you do not need to connect the serial port cable and the
debugging network cable.
Synchronize the software on the active OMU to the standby OMU.

Run the SYC BAMFILE command on the LMT to synchronize the configuration files
and destination files on the active OMU to the standby OMU.
A large number of files need to be synchronized. Therefore, it takes two or three minutes to display the
file synchronization result after you run the SYC BAMFILE command. If there are files that are
synchronized unsuccessfully, run the SYC BAMFILE command again.
Reset the standby OMU.

Run the SYC BAMFILE command to synchronize files.
Run the RST BRD command to reset the standby OMU is reset.
----End
4.2.3 Loading Software to UAP8100 MGW

The host software of the UAP8100 MGW consists of the device management software and
board service software. The device management software provides the functions of device
management, device maintenance, performance monitoring, fault reporting, and device
debugging. The board service software is used to process the services of boards, such as voice
encoding and decoding, data communication, and processing of signaling protocol messages.
This section describes the installation of board service software.
2008-12-02
Page 78 of 212
Figure 1.1 shows the process of installing board service software.

Figure 1.1 Process of installing board service software
4.2.4 Key Points in Loading Software to UAP8100

MGW
2008-12-02
During loading, use the FTP tool provided by the MGW software. The tool can be
obtained in the path 02 BAM\tools\MGW tools.
When loading hardware data,
Make sure that the data is loaded to the center switching frame after the main control
frame.
Make sure that the data is successfully loaded to the TNU board of the center
switching frame before loading data to the UCLU board of the main control frame.
Make sure that the data is successfully loaded to the E8T board before loading data to
the HRU board.
Make sure that the data is successfully loaded to the FLU/BLU board of the center
switching frame before loading data to the service frame.
In the LOD TOBAM command, the special file selection parameter should be set to
VPUT (VPU Tone). Otherwise, the VPU board cannot be loaded with data.
After loading data to boards, run the commands CHK FILE and CHK VERSION to
check the data on the boards and the data stored in the OMU hard disk. During data
configuration, run the SAVE CFG command to save the configuration information in
time. Make sure that data stored in the memory is consistent with that stored in the hard
disk.
After loading data to the boards, run the following command to check the versions of the
programs running on the boards:
Page 79 of 212

CHK VERSION:VT=BRD;
If the system displays the following information, you need to load the LAN Switch
driver to the OMU:
++ -----------------------------------------------------------------------------++ Software name Software type Standard version Current version Flash version
++ -----------------------------------------------------------------------------++ lswextbtrm.bin
LANDRV
R005C02B049
<Unknown>
<Unknown>
++ -----------------------------------------------------------------------------Run the following command to load the LAN Switch driver to all the boards:
LOD LAN: EN=ENABLE;
You can also load the LAN Switch driver on specific frames or boards. For example, if
you want to load the LAN Switch driver to the OMU of slot 7 in No.1 frame, run the
following command:
LOD LAN: FN=1, SN=LSW1, EN=ENABLE;
If loading the LAN Switch driver manually, you need to load it to the main control frame
first.
4.3 Software Installation of the CTI3.4

Platform
The process of installing the software of the CTI3.4 platform is the same as that of installing
the software of the CTI3.2 platform. For details about the installation, see the TopEng-Call
Center Installation Guide (V300R004_03).
You can visit http://support.huawei.com to obtain the TopEng-Call Center Installation Guide
(V300R004_03). The location of the document is as follows:
> CTI > Version Release Document
4.4 Software Installation of the File Server

The file server of the IPCC system must be installed on the SUSE Linux9 SP3 operating
system. There are two types of file servers: file server cluster with disk array and stand-alone
file server.
To install the file server cluster with disk array, see the FS Two-Node Cluster Installation
Guide (V1.06,suse9sp3)-20080220. You can also use the automatic installation script. For
details, see the File Server Automatic Installation Guide(V1.00).
You can visit http://support.huawei.com to obtain the FS Two-Node Cluster Installation Guide
(V1.06,suse9sp3)-20080220 and File Server Automatic Installation Guide (V1.00). The
location of the documents is as follows:
For details about the installation of the stand-alone file server, see the FS Single-Node System
Installation Guide(V1.03,suse9sp3).
2008-12-02
Page 80 of 212
You can visit http://support.huawei.com to obtain the FS Single-Node System Installation

Guide (V1.03,suse9sp3). The location of the documents is as follows:
4.5 Installation of the OpenEye Software

When installing the OpenEye software, keep the default settings. After installation, modify the
fast.ini file in the installation directory (the default directory is Program Files\OpenEye in
drive C.
Change the values of LoginServerUrl0 and LoginBakServerUrl0 to the IP address of the
IFM on the UAP8100. If the UAP8100 has multiple IFM boards, run the ADD MMTE
command to add the IP address of the IFM board corresponding to the multimedia subscriber.
If the OpenEye accesses the UAP8100 through the SBC, provide the client IP address of the
SBC.
For example:
LoginServerUrl0=192.168.4.88:5060
LoginBakServerUrl0=192.168.4.88:5060
For more examples, see attachment 4 fast.ini.
4.6 Installation and Configuration of a TTS

Server
Currently, the UAP8100 supports the TTS version of Interphonic 4.0, ISP2.5 of iFLYTEK.
For other versions, contact the R&D personnel before using them. The installation process
consists of three procedures: installing a running library, installing a voice library, and
installing an encryption lock and an ISP.
Preparation for Installation

The TTS of iFLYTEK supports two languages in China: Chinese and English. The TTS is
encrypted by the dongle. Therefore, check whether the corresponding dongle is obtained
before deployment, and whether the number of dongle licenses and the versions of licenses
are consistent with those in the contract. Check whether the version of the ISP is ISP2.5.
Installing a Running Library

Step 1 Insert the TTS installation disk into the CD driver. The system runs the AutoRun.exe file. If
the system does not run the file automatically, double-click the AutoRun.exe file in the root
directory. In the case of hard disk file, double-click the setup.exe file in the Runtime
Enterprise directory.
Step 2 Select the option of installing running library.
The license agreement window is displayed.
Step 3 Select I accept the agreement, and click Next.
2008-12-02
Page 81 of 212
The window for entering user information and a sequence number is displayed.
Step 4 Enter user information and a sequence number, and click Next.
The window for selecting the installation path is displayed.
You can obtain the sequence number from the TTS installation disk of iFLYTEK.
Step 5 Select a proper installation path. The running library requires 50 MB disk space, and the 8 K
voice library requires 1 GB disk space. Thus, you need to make sure that the disk space is
sufficient when selecting a path. After selecting a path, click Next. Then the installation
window is displayed.
Step 6 The installation program prompts you whether to install the dongle driver before you install
the running library. Retain the default setting. That is, select the option of installing the dongle
driver.
Step 7 Click Next.
The installation of the running library begins.
Step 8 The system automatically installs the dongle drive after the installation of the running library
is completed. Then the system displays a message indicating that the dongle driver is installed
successfully.
Step 9 Click OK. Then the system is updated and the installation is completed.
----End
Installing a Voice Library

Step 1 Insert the InterPhonic 4.0 voice library disk into the CD driver. Select the option of installing
the voice library in the window for installing voice synthesis system.
Step 2 In the window for selecting the installation language, select simplified Chinese. Then click
OK.
Step 3 In the welcome window, click Next.
Step 4 In the window indicating that the preparation is done, click Install to start copying files.
Step 5 In the window indicating that the installation is completed, click Finish.
----End
There can be one or multiple voice libraries. After the installation, you can run the synthesis
demonstration program to check whether the voice library is installed correctly.
The installation disk provides the voice libraries with different sampling rates. The VP
supports only the linear wav of 8 k' 8 bit. Thus, select the installation disk of 8 k voice library.
2008-12-02
Page 82 of 212
Installing an Encryption Lock

When installing an encryption lock, insert the encryption lock into the parallel port or USB
port according to the type of the encryption lock. After fixing the dongle, choose Start >
iFLYTEK > InterPhonic 4.0. Use the tool for detecting the encryption lock to check whether
the dongle is installed properly, and whether the version of the dongle and the number of
licenses are consistent with that in the contract.
The software dongle of Microsoft TTS is not compatible with that of iFLYTEK.
Different versions of TTS software dongles are not compatible with each other. Thus, apply for a new
software dongle after upgrading the InterPhonic version.
Installing an ISP
Step 1 Run the ISP 2.5 installation program. Then a welcome window is displayed. Click OK to
access the License Agreement window.
Step 2 Select I accept the agreement, and click Next. Then a window for entering user information
and a sequence number is displayed.
Step 3 Enter user information and a sequence number, and click Next. Then a window for selecting
the installation path is displayed.
You can obtain the sequence number from the TTS installation disk of the iFLYTEK.
Step 4 Select a proper installation path, and click Next. Then the window for installing components
is displayed.
Step 5 Retain the default settings when installing components. Click Next to access the window for
starting the service.
Step 6 Set the service to start automatically. Deselect the option of starting the installed service
immediately after the installation is completed. Click Next to start the installation. Click
Finish after the installation is completed.
----End
Starting a TTS Server

Start a TTS server in ISP mode. Set the ISP before starting the TTS server. Two services can
be installed on a TTS server: TTS synthesis service and SRM service. The SRM service is
required only when the TTS server works in large scale mode. The TTS synthesis service
provides only the function of voice synthesis, and the SRM service provides only the function
of resource management.
Step 1 Find the configuration files ses.cfg, spi.cfg, spc.cfg, spw.cfg, and srm.cfg in the \bin\
directory on each TTS server. Change the value of local_ip to the IP address used for TTS
service on the current server.
[local]
local_ip=0.0.0.0
For example, the current server has two IP addresses, that is, 192.168.1.1 and 10.12.123.120.
The latter IP address is used for the TTS server. You can change the value of local_ip to
10.12.123.120.
2008-12-02
Page 83 of 212
Step 2 Start the TTS service according to the type of the TTS server.
Start a TTS synthesis server.

If the TTS server works as a TTS synthesis server, choose Management tools > Service
to start the following two services:
Speech Engine Services
Speech Platform Watcher
Start an SRM server.

In large scale mode, two servers need to work as SRM servers. Choose Management
tools > Service to start the following two services:
Speech Platform Watcher
Speech Resource Manager
The Speech Engine Services is a voice engine manager that provides specific voice services. On a
TTS synthesis server, this service must be started.
The Speech Platform Watcher is a daemon for voice services. It runs on any ISP host to monitor the
running of ISP services which work on this host. It also reports the exceptions of the system.
Therefore, this service must be started.
The Speech Resource Manager provides the function of dynamic load balancing. You need to enable
this function on only two TTS servers in a network segment.
----End
4.7 Upgrading the SBC

When the SBC reaches on site, the software is installed. Check the software version of the
SBC. If the version is earlier than any of the following versions, upgrade the SBC on site.
SE2200: SBCV200R005C02B052
SE2300: SBCV200R005C03B052
For the methods of upgrading the SBC, see the upgrade guides of the SBC.
For other reference documents of the SBC, you can visit http://support.huawei.com to obtain
them from the following location:
Documentation > Core Network Product Line > Fixed Core Network NGN >
SessionEngine SBC
If the SBC does not convert addresses through NAT devices, the SBC must be set to single domain
mode.
2008-12-02
Page 84 of 212
Data Configuration
This chapter describes how to configure the data for the UAP8100, CTI3.4 platform, and
network devices.
The UAP8100 MGC is designed with a relational database mechanism to manage the data in
the system. The database mechanism consists of multiple connected data tables. Each data
table describes a specific group of data. The data tables can be correlated through keywords.
To show the logical relation between services, ensure that the keywords to be referenced in
later data tables are defined in the related data tables, and prevent junk data, the UAP8100
MGC defines a strict data configuration procedure through the stored procedures of the
database. That is, you must follow a certain configuration procedure to create and configure a
database correctly.
As the MGW, the UAP8100 MGW provides the IP access and the speech path access of
narrowband services. In addition, narrowband VRBs use the external E1 interfaces provided
by the UAP8100 MGW as resource channels. Therefore, the UAP8100 MGW data includes
the basic hardware data, the data about the connection to the MGC, the TDM bearer data
required by the VRB, and the TDM bearer data required for narrowband interoperability with
the PSTN.
Data configuration for the CTI3.4 platform differs little from that for the CTI 3.2 platform.
The differences of the CTI3.4 platform configuration from the CTI 3.2 platform configuration
are detailed in this chapter.
5.1 Basic Rules for Configuring the UAP8100

Data
5.1.1 Purpose
2008-12-02
To reduce the frequency of message transfer among boards and frames and improve
system performance by allocating signaling links and internal and external trunks.
To ensure higher reliability by configuring links or circuits to the same office direction
on different boards.
To ensure load balancing among modules.
Page 85 of 212
5.1.2 Configuration Rules

Basic Rules for Configuring the UAP8100 MGC
Configure the signaling links to the same office direction in different frames of the
UAP8100 MGC. Configure the signaling links in the same frame on different CSUs or
CCUs.
Configure external trunk circuits to the same office direction on different CSUs or CCUs
in the UAP8100 MGC. Distribute these modules in different frames in the UAP8100
MGC.
Configure the internal trunk circuits used by the VRB on different CSUs or CCUs in the
UAP8100 MGC. Distribute these modules in different frames in the UAP8100 MGC.
Even up the number of internal trunks and the number of external trunks on each CSU or
CCU.
For a CSU or CCU configured with 2 Mbit/s signaling links, reduce the number of
internal and external trunks on this module by 10% compared with a module not
configured with any 2 Mbit/s signaling links.
Assign a CSU or CCU to the CDB in the local frame. Distribute the CSUs or CCUs to
the CDBs evenly.
Assign a VRB and the CSU or CCU configured for the trunk circuits of this VRB to the
same CDB. Make sure that each CDB manages the similar number of VRB sites.
You can assign the sites connected to the upper pinch boards and the lower pinch boards
on an MSU to different CDBs. Make sure that each CDB manages the similar number of
MSU sites.
In the case of multiple signaling points (SPs), assign a similar number of trunks to each
SP to balance the link load.
To configure the CDB functions, enable four functions: subscriber location, trunk
selection, MGW management, and BSG distribution. In the case of large-scale TTS
applications, global TTS management is required. If the office has two pairs of CDBs,
use one pair of CDBs for trunk selection and use the other pair for subscriber location,
MGW management, and BSG distribution.
Basic Rules for Configuring the UAP8100 MGW
2008-12-02
If the UAP8100 MGW has only one frame, that is, the main control unit, use an HRB to
transfer H.248 messages in a centralized way. In this case, you must enable the 100
Mbit/s full duplex mode at a forwarding network interface. If the UAP8100 MGW has
multiple frames, use an MPU in the central switching frame to transfer H.248 messages
in a centralized way. In this case, enable the auto-negotiation mode at the forwarding
network interfaces.
If the UAP8100 MGW has only one frame, distribute circuits to the same office direction
to different interface boards.
If the UAP8100 MGW has multiple frames, distribute circuits to the same office
direction to different frames.
Distribute TDM endpoints evenly among CMFs for management.
If the UAP8100 MGW has only one frame, distribute internal trunk circuits among
different interface boards. If the UAP8100 MGW has multiple frames, distribute internal
trunk circuits among these frames.
Page 86 of 212
5.2 UAP8100 MGC Data Configuration

Procedure
5.2.1 Configuration Procedure
Figure 1.1 General flow of configuring the data in the UAP8100 MGC
For the description of parameters in each command in later sections, see the online help of the
UAP8100 MGC BAM client or attachment 5 MML Commands in.chm format.
After configuring the UAP8100 MGC, run the FMT command and restart the frame to
ensure version consistency.
Run STR CRC to check consistency of the data on the board and the BAM. This can
ensure that the version configuration is correctly loaded.
5.2.2 Configuring Hardware Data

As a type of basic data of the UAP8100 MGC, hardware data is used to define the physical
hardware, physical ports, and relevant configuration information about the UAP8100 MGC.
To configure the hardware data, you need to make the following preparations:
2008-12-02
Page 87 of 212
Data Preparation
Detailed diagram of panel configuration

The diagram provides the type, position, and serial number of a device, such as the shelf,
frame, and board.
Device number
For the function and planning of the device numbers, see section 2.2"Planning the
TCP/IP Network."
The higher three bits of the S3 DIP switch on the SIU are used to set the device
numbers. The lower five bits of the DIP switch are used to set the frame numbers. For
details, see the UAP8100 Universal Access Platform Hardware Description Guide.
Frame number
A shelf supports up to 18 Open Standards Telecom Architecture Platform (OSTA) frames
numbered from 0 to 17. The numbering principles are as follows:
The frames inside a shelf are numbered in ascending order of the installation
positions.
The frames between shelves are numbered in ascending order of the shelf numbers.
During actual configuration, the lower five bits of the S3 DIP switch on the SIU are used
to number a frame. For details, see the UAP8100 Universal Access Platform Hardware
Description Guide.
Board module number

The UAP8100 MGC software regards the BAM and front boards as modules for
handling and numbering. The UAP8100 MGC can identify up to 256 modules numbered
from 0 to 255. The BAM is numbered 0.
The module number of a board starts from 2 based on the board type. Each board has a
unique module number. A pair of active and standby boards are regarded as one board
with one module number. The numbering rules are as follows:
Module number range for an SMU: 226 (automatically assigned by the system)
Module number range for a CDB: 2734
Module number range for an IFM, BSG, or MSG: 3572
Module number range for a CCU, CSU, VRB, or MSU: 73252

By default, the CCUs or CSUs occupy 20 module numbers, and the VRBs or MSUs
occupy 160 module numbers. Assign module numbers to CCUs or CSUs in ascending
order from 73. Assign module numbers to VRBs or MSUs in descending order from
252.
IP address of an FE port on an IFM

This IP address is frequently used in later steps of data configuration.
Set the mode at the port on the IFM to 100 Mbit/s full duplex.
Working mode of the E1 port

The working mode of the E1 port specifies whether the E1 port is connected with a 75ohm or 120-ohm cable. For details, see the UAP8100 Universal Access Platform
Hardware Description Guide.
Clock synchronization networking

This is used to specify how to configure the clock data.
2008-12-02
Page 88 of 212
Configuration Procedure
Figure 1.1 lists the steps for configuring the hardware.
Figure 1.1 Steps for configuring the hardware
Step
Description
Command
Add a shelf.
ADD SHF
Add a frame.
ADD FRM
Add a board.
ADD BRD
Add the configuration information about the FE port.
ADD FECFG
Add the configuration information about the E1 port on

the EPI.
ADD EPICFG
Enable CDB functions.
ADD CDBFUNC
Enable CDB resource management.
ADD CCURC
Set the protocol distribution ability.
SET DPA
For FE port configuration, the mode at the port on the IFM board must be set to forced
100 Mbit/s full duplex, regardless of whether the MGW uses the HRB or the MPU to
transfer H.248 messages in a centralized way.
For E1 port configuration, set the frame format to dual frame (DF). When the 75-ohm E1
cables are used, select the non-balanced mode for the E1 port. When the 120-ohm E1
cables are used, select the balanced mode for the E1 port.
To configure the CDB functions, enable the following functions only: subscriber
location, trunk selection, MGW management, and BSG distribution. If the large-scale
TTS function for the VRB is enabled, enable global TTS license management.
When running ADD BRD to add a board, you can see the default protocol distribution
capability preset by the system. The default values are as follows:
For an IFM: none
For a BSG: MGCP, H.248, and SCTP
For an MSG: TRIP, ENUM, STUN, MIDCOM, Original call, iDo, SMC, and
RADIUS
You need to enable the SIP distribution capability for the MSG in the IPCC.
Generally, the default configuration can meet the requirements. To enable a certain board to
distribute one or multiple protocol messages separately, run SET DPA.
For instance, a BSG normally distributes MGCP, H.248, and SCTP messages. You can run
SET DPA to specify a BSG to distribute messages of a specific protocol, such as the MGCP
protocol.
The following is an example:
ADD
ADD
ADD
ADD
ADD
2008-12-02
SHF:
FRM:
FRM:
BRD:
BRD:
SN=0,
FN=0,
FN=1,
FN=0,
FN=0,
LT="GXRZUAP", PN=0, RN=0, CN=0;

SN=0, PN=2;
SN=0, PN=3;
SN=0, LOC=FRONT, BT=IFMI, MN=35, ASS=1;
Page 89 of 212
ADD BRD: FN=0, SN=4, LOC=FRONT, BT=CCU, MN=73, ASS=5;

ADD BRD: FN=0, SN=4, LOC=BACK, BT=EPII;
ADD BRD: FN=0, SN=5, LOC=BACK, BT=EPII;
ADD BRD: FN=0, SN=10, LOC=FRONT, BT=CDBI, MN=27, ASS=11;
ADD BRD: FN=0, SN=12, LOC=FRONT, BT=BSGI, MN=39, ASS=255;
ADD BRD: FN=0, SN=12, LOC=FRONT, BT=BSGI, MN=40, ASS=255;
ADD BRD: FN=0, SN=14, LOC=FRONT, BT=MSGI, MN=72, ASS=15;
ADD BRD: FN=0, SN=13, LOC=BACK, BT=CKII;
ADD BRD: FN=0, SN=15, LOC=BACK, BT=CKII;
ADD BRD: FN=1, SN=0, LOC=FRONT, BT=VRB, MN=252, VRBLT=E1;
ADD BRD: FN=1, SN=0, LOC=BACK, BT=ERI;
ADD FECFG: MN=36, IP="10.51.4.40", MSK="255.255.255.0", DGW="10.51.4.1" ,
EA=FH;
ADD
FECFG:
MN=35,
IP="192.168.0.200",
MSK="255.255.255.0",
DGW="192.168.0.1" , EA=FH;
ADD EPICFG: FN=0, SN=4, E0=DF, E1=DF, E2=DF, E3=DF, E4=DF, E5=DF, E6=DF,
E7=DF, BM=BALANCE;//Use 120-ohm E1 cables.
ADD CDBFUNC: CDPM=27, FCF=LOC-1&TK-1&MGWR-1&DISP-1&GTTSLICM-1;//Suport the
large-scale TTS function.
ADD CCURC: CCUMN=73, CDBMN=27;
SET DPA: MN=72, DA=SIP-1;
Configuration Relations
Figure 1.1 shows the relations between key parameters in the data tables used when you
configure the hardware data.
2008-12-02
Page 90 of 212
Figure 1.1 Relations between data tables
You need to refer to the values of some parameters of the hardware data when you configure
other UAP8100 MGC data in later steps. See Figure 1.2.
Figure 1.2 Parameter citing relations between hardware data and other data
Parameter
Location for Citing
Board module number
Configuring media gateway data
Configuring signaling data
Configuring routing data
Configuring trunk data
Configuring resource data
Configuring media gateway data
Configuring resource data
IP address of FE port
Slot information of E1 port
2008-12-02
Page 91 of 212
5.2.3 Configuring Local Exchange Data

As one type of basic data of the UAP8100 MGC, the local exchange data defines the
following information about the local exchange: the DPC, global DN set, local DN set,
country code, area code, national toll area code, call source, and number segment.
Data Preparation
Before configuring the local exchange data, prepare the data items listed in Figure 1.1.
Figure 1.1 Data preparations
SN
Item
Remarks
Local signaling point

code
The local signaling point code is used to configure the

data related to the MTP signaling.
Global DN set planning
The global DN set specifies whether to enable the

multi-national code or multi-area code service.
Local DN set planning
The local DN set specifies the number of prefix sets

that a local user can have.
Call source planning
A call source is used to distinguish one caller group

from another.
NOTE
In the IVR service, you need to set the call source
information for the calls initiated by the CTI platform.
In UAP8100 V300R003, the default call source for the CTI
platform is 0. Therefore, you need to add call source 0.
Number segment
planning
The number segment planning helps in specifying the

number resources occupied by the local exchange.
Toll area code of a

national city or area
(optional)
The system presets a list of toll area codes of Chinese

cities or areas during initialization. When this device
is used outside the Chinese mainland, you need to
prepare this list.
Figure 1.1 lists the steps for configuring the local exchange data.
Figure 1.1 Steps for configuring the local exchange data
2008-12-02
Ste
p
Description
Command
Set the local exchange information.
SET OFI
Add a local SPC.
ADD OFI (optional)
Page 92 of 212
Ste
p
Description
Command
Modify the local exchange

information.
MOD OFI (optional)
Add a country code or area code.
ADD NCODE (optional)
Add a toll prefix.
ADD PFXTOL (optional)
Add a national toll area code.
ADD ACODE (optional)
Add a local DN set.
ADD LDNSET
Add a call source.
ADD CALLSRC
Add a user number segment.
ADD DNSEG
10
Set the DST.
SET DST (optional)
In step 2, due to limitation on the circuit identification code (CIC) signaling field, one SP
can handle up to 4,000 trunks. If the number of trunks accessed from a certain office
direction exceeds 4,000, and the peer office has only one SP, you need to configure
multiple SPs at the local exchange.
In step 3, when the local exchange has multiple SPs, you can run this command to enable
mutual assistance between multiple SPs.
To define the mutual assistance node for each originating signaling point at the local
exchange, you must run MOD OFI to modify the information about the local exchange.
In steps 4, 5, and 6, the system presets the toll area code for each Chinese city or area
during initialization. You need to perform these steps if you want to configure multiple
country codes or area codes for the local exchange or if the UAP8100 is used outside
China. The national toll area code is required for deployment outside China. You need to
add a national toll area code after adding the description for the toll prefix. If this
configuration sequence is incorrect, the configuration fails.
In step 8, when adding a call source code, set Pre-received Digit to 1.

SET
ADD
ADD
ADD
OFI: OFN="GXUAP", LOT=CMPX, NN=YES, NPC="222222", NNS=SP24, SPF=YES;

LDNSET: LP=0, NC=K'86, AC=K'771, LDN="GXHBRZ";
CALLSRC: CSC=0, CSCNAME="GXHBRZ", PRDN=1;
DNSEG: LP=0, SDN=K'99000, EDN=K'99499;
Figure 1.1 shows the relations between key parameters in data tables used when you configure
the local exchange data.
2008-12-02
Page 93 of 212
You need to refer to the values of some parameters of the local exchange data when you
configure other UAP8100 MGC data in later steps. See Figure 1.2.
Figure 1.2 Parameter citing relations between local exchange data and other data
2008-12-02
Parameter
Location for Citing
Local signaling point code
Page 94 of 212
Parameter
Location for Citing
Local DN set
Configuring number analysis data
Global DN set
Call source code
Route selection source code

Failure source code
5.2.4 Configuring Charging Data

The UAP8100 MGC does not provide the CDR functions of a common call office. This
section describes how to configure the charging data out of the requirement for the MGC to
provide charging selection code indexes for configuring the number analysis data. The
charging data configuration does not have any practical meaning.
Figure 1.1 Steps for configuring the charging data
Step
Description
Command
Modify the charging mode.
MOD CHGMODE
Add a local charging group.
ADD CHGGRP
The charging data contains the default charging index and charging analysis data. Therefore, you need to
change the charging mode and add a charging group only.

MOD CHGMODE: CHA=0, TA1="60", PA1=1, TB1="60", PB1=1, AGIO1=100;
ADD CHGGRP: RCHS=0, DCHS=0, LOAD=ALL, CODEC=ALL, CHA=0;
the charging data.
2008-12-02
Page 95 of 212
You do not need to configure the parameters in the ADD CHGANA or ADD CHGIDX command;
however, the relations between these two commands exist.
You need to refer to the values of some parameters of the charging data when you configure
Figure 1.2 Parameter citing relations between charging data and other data
Parameter
Location for Citing
Caller charging source code
Reverse charging source code

Charging selection code
5.2.5 Configuring Clock Data

Clock data configuration consists of the MGC clock data configuration and MGW clock data
configuration.
2008-12-02
Page 96 of 212
When the UAP8100 MGC needs to provide MTP links for connection with devices such as
the SP, STP, and service control point (SCP) in the SS7 network, you need to correctly
configure the clock data according to the clock networking of the UAP8100 MGC in addition
to hardware devices, such as the CSU, CCU, CKI, and EPI. Otherwise, the MTP links cannot
work.
If the IPCC office is interconnected with the softswitch by using SIP, the clock offices on the
UAP8100 MGC and UAP8100 MGW can use their own clocks.
Overall Clock System Structure

Figure 1.1 shows the overall structure of the clock system in the UAP8100 MGC.
Figure 1.1 Overall clock system structure
The LAN is not directly connected to the SMU. The LAN is connected to the HSC through a
cable.
The clock system in the UAP8100 MGC consists of the clock interface module, clock control
module, and clock distribution module.
Clock interface module

The clock interface module consists of the CKI and EPI.
The interfaces provided by the CKI can be directly connected with an external clock
source, such as the BITS, to obtain a 2 MHz or 2 Mbit/s clock source.
The CKI can obtain the 2 MHz clock signal in E1 channels from the EP1 by using a
dedicated clock cable.
Clock control module

The clock control module consists of the WS, BAM, SMU, and serial bus. The clock
control module enables you to perform operations on the clock system in the UAP8100
MGC, such as data configuration, maintenance, and status query.
Clock distribution module

The clock distribution module consists of the CKI, dedicated clock cable, and H.110 bus.
The CKI turns the obtained clock signal into the 16-channel time division clock signal by
using the drive. This clock signal is transferred to the specified EPI in each additional
frame in the system through the dedicated clock cable. The EPI transfers 8 kHz clock
signal to other EPIs in the local frame through the H.110 bus to synchronize the clock in
the entire system.
Clock Synchronization Methods

There are two methods for synchronizing the clocks between the UAP8100 MGC and the peer
device:
UAP8100 MGC locking the clock signal of the peer device

If the peer device can provide stable clock signal at stratum 3 or above, the EPI in the
UAP8100 MGC can obtain the clock signal through the E1 cable and send the signal to
the CKI through the 2 MHz clock cable. The CKI locks this clock source and generates
the clock information required by the entire UAP8100 MGC system.
2008-12-02
Peer device locking the clock signal of the UAP8100 MGC
Page 97 of 212
The CKI can export stable stratum 2 cock signal. This signal can be used as the clock
source to synchronize the downstream device. In this case, the clock source in the
UAP8100 MGC is the BITS.
UAP8100 MGC locking the clock signal of the peer device
Figure 1.1 shows the method for synchronizing the clock in the UAP8100 MGC when the
clock system in the UAP8100 MGC locks the clock signal of the peer.
Figure 1.1 Clock synchronization when the UAP8100 MGC locks the peer clock signal
The EPI is connected with the peer device through the E1 or T1 cable. The E1 or T1 cable
provides the 2 MHz clock signal.
The double shielded coaxial cable is used for the 2 MHz clock cable. The two shielding layers
of the cable are connected. The 75 SMB connector is used. The EPI that provides the E1 or
T1 cable is connected with the active and standby CKIs in the basic frame through two clock
cables to provide the 2 MHz clock source.
Only the EPI connected with the E1 or T1 cable can provide the 2 MHz clock signal. In actual
application, if the basic frame has four EPIs, you can connect the EPIs to the active and
standby CKIs to provide four channels of 2 MHz clock signal.
The active and standby CKIs provide two groups of H.110 bus clock signal to the EPIs in the
local frame through the H.110 bus to ensure clock synchronization of these EPIs.
The active and standby CKIs in the basic frame can provide the 8 kHz clock signal to EPIs in
slots 0 and 1 in an additional frame through four 8 kHz clock cables.
Figure 1.2 shows the connection between the EPI and the CKI in the basic frame.
Figure 1.2 Clock connection between EPI and CKI in the basic frame in the UAP8100 MGC
2008-12-02
Page 98 of 212
Due to the limited space for providing cables through the handle on the CKI, each CKI can provide up to
16 channels of clock signal. That is, up to 9 frames, including 8 additional frames and 1 basic frame, in
the system can be configured with SS7 interfaces.
The EPI in an additional frame provides the H.110 bus clock signal to other EPIs in the same
frame.
Peer device locking the clock signal of the UAP8100 MGC
Figure 1.3 shows the method for synchronizing the clock in the UAP8100 MGC when the
peer device locks the clock signal of the UAP8100 MGC.
Figure 1.3 Clock synchronization when the peer device locks the clock signal of the UAP8100
MGC
External active and standby BITSs are connected to the active and standby CKIs in the basic
frame through two coaxial clock cables to provide the clock source for the CKI. The clock
source can be 2 Mbit/s or 2 MHz signal.
The active and standby CKIs provide two groups of H.110 bus clock signal to the EPIs in the
local frame through the H.110 bus to ensure clock synchronization of these EPIs.
The active and standby CKIs in the basic frame can provide the 8 kHz clock signal to EPIs in
slots 0 and 1 in an additional frame through four 8 kHz clock cables.
The EPI in an additional frame provides two groups of H.110 bus clock signal to other EPIs in
the same frame.
If the links on the UAP8100 MGC side use the SIGTRAN protocol family M3UA or M2UA for
signaling interconnection, you do not need to configure the clock data on the MGC side.
The following figure shows the procedure for configuring the clock data in the MGC.
2008-12-02
Page 99 of 212
Figure 1.1 lists the steps for configuring the clock data in the MGC.
Figure 1.1 Steps for configuring the clock data in the MGC
Step
Description
Command
Add a clock source.
ADD BOSRC
Set the parameters for configuring the clock board.
SET CKICFG
Set the clock source in the local frame (optional).
SET CLKSRC
You need to configure the clock source only when the MGC uses the line clock signal of
the peer end.
When the MGC signaling links are distributed among multiple frames, you need to
configure the clock distribution data to ensure clock consistency in the entire system;
otherwise, signaling links in other frames cannot work.
You need to configure the clock distribution data for only those frames that contain signaling links.

ADD BOSRC: FN=0, SN=2, EN=0;
SET CKICFG: CL=LEVEL3, WM=AUTO, B1P=NOCFG, B2P=NOCFG, L1P=L1, L2P=L2;
5.2.6 Configuring Media Gateway Data

In the UAP8100, the UAP8100 MGW is used as the MGW (MGW) and the UAP8100 MGC
is used as the MGW controller (MGC). The UAP8100 MGW communicates with the
UAP8100 MGC by using H.248. The UAP8100 MGC authenticates the registration requests
to the MGW based on the IP address and UDP port number. The default gateway port is port
2944.
2008-12-02
Page 100 of 212
Data Preparation
Before configuring the MGW data, set the parameters used for interconnection between the
UAP8100 MGC and the UAP8100 MGW. See Figure 1.1.
SN
Item
IP address of the UAP8100 MGC
IP address of the UAP8100 MGW
UDP port on the UAP8100 MGW
Encoding and decoding modes of the UAP8100 MGW
UAP8100 MGW supporting hairpin connection or not
UAP8100 MGW supporting EC
Module number of the CSU or CCU that manages the UAP8100 MGW
One UAP8100 MGW can be managed by one CSU or CCU only. One CSU or CCU can manage
multiple UAP8100 MGWs.
In step 4, the encoding and decoding mode list of a certain MGW configured on the UAP8100 MGC
must have intersection with the list of encoding and decoding modes supported by the MGW.
Otherwise, the services in this MGW cannot function.
In step 6, the UAP8100 MGW needs to support EC in the IPCC. The general principle is that EC is
required in the case of cable switching.
Run ADD MGW to add an MGW.

The configuration of the new MGW must be the same as that of the UAP8100 MGW,
including the peer IP address, port, EID, EC, codec mode (generally binary ASN.1), and
support for hairpin calls. Generally, ACD services support the EC function. To enable ACD
services support the EC function, configure the EC pinch board on the VPU and set EC to
TRUE.
ADD MGW: EID="192.168.0.201:2944", GWTP=UMGW, MGWDESC="GXDXMGW", MGCMODULENO=73,
LA="192.168.0.200", RA1="192.168.0.201", RP=2944, HAIRPIN=S, EC=TRUE, CODETYPE=ASN;
You need to refer to the values of some parameters of the MGW data when you configure
2008-12-02
Page 101 of 212
Figure 1.1 Parameter citing relations between MGW data and other data
Input Parameter
Output Parameter
Parameter
Name
Location for
Setting
Parameter
Name
Location for
Citing
Module number of
CCU or CSU
Configuring
hardware data
Equipment ID of the
MGW
Configuring signaling
data and configuring
trunk data
Configuring
hardware data
5.2.7 Configuring Signaling Data

As the language for communication between devices, the signaling is the key to service
realization. Before configuring the signaling data, you need to know the networking topology
between local and external offices, the signaling interfaces between devices, and the signaling
protocols used at each signaling interface.
Figure 1.1 shows the typical signaling networking of the UAP8100 MGC.
Figure 1.1 Typical signaling networking of the UAP8100 MGC
The preceding figure covers all types of signaling protocols that access the UAP8100 V300R003. You
can configure the data according to the actually accessed signaling and by referring to the description on
the signaling protocols in later sections.
Configuring MTP Data

The MTP data is used to configure the data related to the MTP signaling during
interconnection between the UAP8100 MGC and devices such as the SP and signaling
transfer point (STP). You must finish configuring the hardware data, local exchange data, and
MGW data before configuring the MTP data.
2008-12-02
Page 102 of 212
Background Knowledge
SP and SPC
SPs include the OPC that originates a signaling message and destination signaling point
code (DPC) that receives a signaling message. The SP can be an exchange that provides
the SS7 functions, such as the PSTN exchange, data exchange, and ISDN exchange. The
SP can also be a special service center, such as the network management center,
maintenance center, and SCP.
A signaling point code (SPC) uniquely identifies an SP in a signaling network.
According to the SS7 definition, signaling networks are divided into four types:
international network, international reserved network, domestic network, and domestic
reserved network. One SP can be located in the preceding four types of signaling
networks at the same time and identified in the networks by separate signaling point
codes.
SLC
According to the SS7 definition, up to 16 signaling links are supported between 2
adjacent SPs. These 16 signaling links are called a signaling link set. A signaling link
code (SLC) uniquely identifies a signaling link in a signaling link set.
An SLC is a 4-bit field. You can specify the value of an SLC through data configuration.
The value range of an SLC is 0 to 15. In actual interconnection, the SLC of the same
signaling link between two SPs must be set to the same value at both SPs. Otherwise, the
MTP link cannot be located.
Mask
Masks are classified into the link set selection mask and link selection mask. The
working principles of the two masks are the same. Take the link selection mask for
example.
Working principles
In an ISUP message, the signaling link selection (SLS) code is a 4-bit binary code. In
a TUP message, the value of the SLS is the lower four bits of the CIC. The value of
the SLS varies with the call. Therefore, the number of links occupied by a signaling
unit also changes. Consequently, the load balancing among signaling links is
achieved.
Algorithm
The mask is a 4-bit binary code. The mask works with the SLS to select the signaling
link for the signaling unit through mask calculation. Bit 1 is used to retain the
corresponding bit of the SLS. Bit 0 is used to mask the corresponding bit of the SLS.
Thus, you can use a mask to retain or mask specified bits of the SLS to obtain valid
link selection bits. For instance:
In this example, the result of SLS and mask is a 4-bit binary string. The value range
of the result depends on the mask. Theoretically, as long as the number of links in a
certain link set minus the decimal value of the mask leaves 1, the signaling unit can
select links based on this result.
Overlapping
The preceding algorithm realizes load sharing for signaling link selection in one link set.
However, this algorithm has strict requirements on the number of times that bit 1 appears
2008-12-02
Page 103 of 212
and the position of bit 1 in the mask. Therefore, when the mask works with the link set
selection mask for link selection, overlapping easily occurs.
Overlapping means that a signaling unit always uses the same link set number and the
same signaling link number when selecting a link set and a signaling link.
For instance, suppose that two MTP link sets, that is, link sets 0 and 1, exist in one office
direction. Each MTP link set contains two links, that is, links 0 and 1. The link set
selection mask is 0010. The link selection mask is also 0010. The application algorithm
for the link set selection mask is the same as that for the link selection mask. Therefore,
when the system generates calls, the following situation may occur: Link 0 in link set 0
and link 1 in link set 1 are occupied at each time, and link 1 in link set 0 and link 0 in
link set 1 are always idle.
To avoid overlapping, you cannot set the link set selection mask or link selection mask to
the same code. It is recommended that you stagger the position of bit 1 in the two masks.
For instance, if the link set selection mask is 0110, set the link selection mask to 1001.
The UAP8100 MGC uses the remainder algorithm. No matter how many signaling links a link set
contains, the system automatically selects a valid link as long as the number of links in a certain link set
minus the decimal value of the mask leaves 1 or less. This algorithm greatly improves the flexibility of
data configuration.
Data Preparation
Before configuring the MTP data, prepare the data items listed in Figure 1.1.
SN
Item
Remarks
Destination
signaling point
code
The DPC is used for interconnection between the UAP8100

MGC and devices such as the SP, STP, and SCP.
Local signaling
point code
This item is used for interconnection between the UAP8100

STP flag
This item is used for interconnection between the UAP8100

Link set index
The link set index is used to select the link set to which the
link belongs.
Signaling link
code
The SLC is used to set the code of a link in a link set.
Link type
Four link types are available:
0 (TDM 64 kbit/s link)
1 (TDM 2 Mbit/s link)
2 (M2UA 64 kbit/s link)
3 (M2UA 2 Mbit/s link)
NOTE
If you select type 0 or 1, you need to configure the circuit timeslot.
2008-12-02
Page 104 of 212
SN
Item
Remarks
Module number
of the CCU that
manages links
This item specifies the CCU that manages links.
Figure 1.1 lists the steps for configuring the MTP data.
Figure 1.1 Steps for configuring the MTP data
Step
Description
Command
Add an MTP DSP.
ADD N7DSP
Add an MTP link set.
ADD N7LKS
Add an MTP link.
ADD N7LNK
Add an MTP route.
ADD N7RT
Activate an MTP link.
ACT N7LNK
For the description of parameters for each command, see the online help.
ADD N7DSP: DPX=0, DPC="009826", OPC="13FCA9", DPNAME="TO_OPT_AIP";
ADD N7LKS: LSX=0, ASPX=0, LSNAME="TO_AIP_LKS", SLSM=B0010;
ADD N7RT: LSX=0, DPX=0, RTNAME="TO_AIP_RT";
ADD N7LNK: MN=73, LNKN=0, LNKNAME="TO_AIP_LINK", LNKTYPE=0, TS=1,
SLC=0, SLCS=0;
ADD N7LNK: MN=73, LNKN=1, LNKNAME="TO_AIP_LINK", LNKTYPE=0, TS=2,
SLC=1, SLCS=1;
LSX=0,
LSX=0,
When configuring the MTP data, you need to refer to the values of some parameters of the
hardware data and MGW data. You need to refer to the values of some parameters of the MTP
data when you configure other UAP8100 MGC data in later steps. See Figure 1.1.
Figure 1.1 Parameter citing relations between MTP data and other data
Input Parameter
2008-12-02
Output Parameter
Parameter
Name
Location for
Setting
Parameter
Name
Location for
Citing
Module number of
CSU
Configuring
hardware data
Destination
signaling point code
Configuring routing
data
Local signaling point

code
Configuring local
exchange data
Page 105 of 212
the MTP data.
In MTP-M2UA signaling networking mode, the M2UA link set index defined in ADD M2LKS will be
referenced by ADD N7LNK.
Configuring M2UA Data

The M2UA data is used to configure the link data for interconnection between the UAP8100
MGC and an embedded signaling gateway that supports the M2UA protocol. You must finish
configuring the hardware data and MGW data before configuring the M2UA data.
In MTP-M2UA signaling networking mode, you need to configure the MTP data in addition
to the M2UA data described in later sections. For how to configure the MTP data, see
Configuring MTP Data.
2008-12-02
Page 106 of 212
Signaling gateway
As a signaling proxy, a signaling gateway is located at the intersection of the circuit
switching network and IP-based packet network. The signaling gateway translates the
SCN signaling into the IP signaling and terminates the SCN signaling. In actual
networking, a signaling gateway may exist in different forms.
Independent signaling gateway

The signaling gateway can work as an independent device. An independent signaling
gateway converts and adapts the protocol used by the SS7 to the M3UA protocol. For
instance, Huawei SG7000 is an independent signaling gateway.
Embedded signaling gateway

An embedded signaling gateway integrates signaling gateway functions. It converts
and adapts the protocol used by the SS7 to the M2UA protocol, the V5 protocol to the
V5UA protocol, and the protocol used by the DSS1 signaling to the IUA protocol
according to the actual networking. For instance, Huawei TMG8010 is an embedded
signaling gateway.
Integrated signaling gateway

The signaling gateway functions can be embedded in a softswitch. That is, the
softswitch provides signaling conversion and adaptation in addition to MGW control
and call processing. For instance, Huawei UAP8100 MGW can be used as an
integrated signaling gateway.
Client/Server mode of SCTP association

The SCTP association works in Client/Server mode. To ensure that the protocol works,
you must specify the working mode for each device in the SCTP association. Normally,
when a certain device works as the SG, it is the server in the SCTP association. Devices
connected with the server in the SCTP association must be clients.
The combination of the following parameters uniquely identifies an SCTP association:
Local IP address
Local port number
Peer IP address
Peer port number
The preceding parameters are used for interconnection between the SCTP and the SIGTRAN. Both
ends need to negotiate the values of the parameters.
After specifying the local IP address and the peer IP address, use the local SCTP port number and
the peer SCTP port number to determine the links between two signaling devices. If all the peer
links use one SCTP port number, the SCTP port number used by a local link must be unique. If all
the local links use one SCTP port number, the SCTP port number used by a peer link must be
unique.
It is recommended that all the links at the server use one SCTP port number and the SCTP port
number used by each link at the client be unique.
Data Preparation
Before configuring the M2UA data, prepare the data items listed in Figure 1.1.
2008-12-02
Page 107 of 212

SN
Item
Remarks
IP address of
embedded signaling
gateway
This item is used for interconnection between the

UAP8100 MGC and an embedded signaling gateway.
Local SCTP port

numbers of M2UA
links (at Client)

Peer SCTP port

numbers of M2UA
links (at the Server)

NOTE
You must plan this port number and the local SCTP port number
of the M3UA link in a unified way.
Figure 1.1 lists the steps for configuring the M2UA data.
Figure 1.1 Steps for configuring the M2UA data
Ste
p
Description
Command
Add a signaling gateway.
ADD ESG
Add an M2UA link set.
ADD M2LKS
Add an M2UA link.
ADD M2LNK
Activate an M2UA link.
ACT M2LNK
//Add an embedded signaling gateway.
ADD ESG: SGID=2, SGNAME="M2UA SG", EID="192.16.254.49:5500";
//Add an M2UA link set.

ADD M2LKS: M2LSX=0, LSNAME="M2UA LinkSet 0", SGID=2, TM=LOADSHARE, IFT=INTEGER;
ADD M2LKS: M2LSX=1, LSNAME="M2UA LinkSet 1", SGID=2, TM=LOADSHARE, IFT=INTEGER;
//Add an M2UA link.

ADD M2LNK: MN=39, LNKN=0, M2LSX=0, LOCPORT=2904, LOCIP1="192.16.254.38",
PEERPORT=2904, PEERIP1="192.16.254.49";
ADD M2LNK: MN=40, LNKN=0, M2LSX=1, LOCPORT=2910, LOCIP1="192.16.254.38",
PEERPORT=2904, PEERIP1="192.16.254.49";
2008-12-02
Page 108 of 212
Some parameters defined in configuration of the hardware data and MGW data are indexed
during M2UA data configuration. Some parameters defined in M2UA data configuration are
indexed in configuration of the MTP link data. See Figure 1.1.
Figure 1.1 Parameter citing relations between M2UA data and other data
Input Parameter
Output Parameter
Parameter
Name
Location for
Setting
Parameter
Name
Location for
Citing
Configuring
hardware data
M2UA link number
Configuring MTP
link data
Module number of
BSG
Configuring
hardware data
Equipment ID of the
MGW
Configuring media
gateway data
the M2UA data.
2008-12-02
Page 109 of 212
Configuring M3UA Data

The M3UA data is used for connecting the UAP8100 MGC to devices such as the SG and
SCP through M3UA links. You must finish configuring the hardware data, local exchange
data, and MGW data before configuring the M3UA data.
Peer-to-peer or non-peer-to-peer networking mode of the M3UA protocol
Non-peer-to-peer networking mode

In this networking mode, one end is an application server, and the peer end is a
signaling gateway.
Peer-to-peer networking mode

Both ends are application servers or both ends are signaling gateways.
The M2UA supports the non-peer-to-peer networking mode only. The M3UA supports the peer-to-peer
networking mode and the non-peer-to-peer networking mode.
Local and destination M3UA entities

The local and destination M3UA entities can be considered as the mapping of the local
and destination SS7 SPs in the M3UA.
2008-12-02
Page 110 of 212
Data Preparation
Before configuring the M3UA data, prepare the data items listed in Figure 1.1.
SN
Item
Remarks
Signaling point code of local

entity
This item is used for interconnection between

the UAP8100 MGC and an SG.
Signaling point code of

destination entity
IP address of destination entity
Local SCTP port numbers of

M3UA links (at Client)

the UAP8100 MGC and an SG
Local SCTP port numbers of

M3UA links (at Server)

the UAP8100 MGC and an SG
Figure 1.1 lists the steps for configuring the M3UA data.
Figure 1.1 Steps for configuring the M3UA data
Step
Description
Command
Add a local M3UA entity.
ADD M3LE
Add a destination M3UA entity.
ADD M3DE
Add the additional M3UA routing service

(optional).
ADD M3DS
Add an M3UA link set.
ADD M3LKS
Add an M3UA link.
ADD M3LNK
Add an M3UA route.
ADD M3RT
In step 3, if the UAP8100 MGC works in non-exclusive SP mode, you need to run ADD M3DS to add
the additional M3UA routing service for each AS that shares the SPC with the UAP8100 MGC.
//Add a local M3UA entity.
ADD M3LE: LEX=0, LENAME="UAP8100", OPC="001122", LET=AS, RC=12345;
//Add a destination M3UA entity.
2008-12-02
Page 111 of 212
ADD M3DE: DEX=10, DENAME="SG", DPC="001177", STPF=TRUE, DET=SG, ADJF=YES;

ADD M3DE: DEX=20, DENAME="PSTN Switch", DPC="1100cc", STPF=FALSE, DET=SP;

ADD M3LKS: LSX=0, LSNAME="To SG", ADX=10, TM=LOADSHARE, WM=ASP;
//Add an M3UA link.

ADD M3LNK: MN=39, LNKN=0, LNKNAME="To SG #0",
PEERIP1="192.16.254.55", PEERPORT=2905, CS=C,
ADD M3LNK: MN=40, LNKN=0, LNKNAME="To SG #1",
PEERIP1="192.16.254.55", PEERPORT=2905, CS=C,
LOCIP1="192.16.254.38", LOCPORT=2905,
LSX=0;
LOCIP1="192.16.254.38", LOCPORT=2911,
LSX=0;
//Add an M3UA route to the PSTN exchange.

ADD M3RT: RTNAME="To F_office", DEX=20, LSX=0;
The non-peer-to-peer networking mode is used for the UAP8100 MGC and the SG7000. The local entity
type of the UAP8100 MGC is AS. Thus, the entity type of the SG7000 must be set to SG. The PSTN
switch needs to transfer SS7 messages to the UAP8100 MGC through the SG7000. Thus, the destination
entity type of the PSTN switch must be set to SP. In addition, you must set the working mode of the
M3UA link set to ASP.
You need to refer to the values of some parameters of the local exchange data, hardware data,
and MGW data when you configure the M3UA data. You need to refer to the values of some
parameters of the M3UA data when you configure the SCCP data and routing data. See Figure
1.1.
Figure 1.1 Parameter citing relations between M3UA data and other data
Input Parameter
Output Parameter
Parameter
Name
Location for
Setting
Parameter
Name
Location for
Citing
IP address of FE
port
Configuring
hardware data
Signaling point
code of local entity
Configuring SCCP
routing data
Module number of
BSG
Configuring
hardware data
Signaling point
code of destination
entity
Configuring SCCP
routing data
Module number of
IFM
Configuring
hardware data
Local signaling
point code
Configuring local
exchange data
the M3UA data.
2008-12-02
Page 112 of 212
Configuring SIP Data

The SIP data defines the configuration information, including the server port number, local
port number, and local IP address used by the SIP protocol in the local exchange. You must
configure the SIP data before configuring the SIP trunk data and SIP user data; otherwise, the
SIP protocol stack in the host cannot work.
You must configure the SIP data after configuring the hardware data, local exchange data, and
charging data.
Well-known port number

This is also known as the server port number. This port number is used for connecting
the UAP8100 MGC to SIP-enabled devices.
Local port number

The local port number is used for load balancing among MSGs during handling of
incoming SIP packets distributed by the IFM of the UAP8100 MGC. The distribution
policies are as follows:
For the first SIP packet sent by the local exchange

Each MSG has a unique local port number. The system designates a port number in
the first SIP packet sent by the local exchange. The peer uses this port to return a
response. This port number is the local port number of the MSG. When the peer
returns a response, the IFM distributes the SIP packet to the MSG through this port.
For the first SIP packet sent by other offices

The port number carried by the SIP packet is the well-known port number 5060.
Thus, the IFM distributes the first SIP packet at the transport layer to an MSG in load
sharing mode. After the MSG handles the packet, the system designates a port
2008-12-02
Page 113 of 212
number in the SIP packet. The peer uses this port to return a response. In this way,
subsequent SIP packets in this call are forwarded through this port.
Data Preparation
Before configuring the SIP data, prepare the data items listed in Figure 1.1.
SN
Item
Remarks
Module number of MSG
This item is used to handle the SIP protocol

messages.
Local port number
This item identifies and distributes an SIP protocol

message to the related MSG for handling.
NOTE
The range of the local port number is defined in SET
SIPCFG. The local port number usually starts from 5061.
Figure 1.1 lists the steps for configuring the SIP data.
Figure 1.1 Steps for configuring the SIP data
Step
Description
Command
Set the global SIP configuration.
SET SIPCFG
Set the local SIP port number.
SET SIPLP
Add one or multiple multimedia devices.
ADD MMTE/ADB MMTE
Add one or multiple multimedia subscribers.
ADD MSBR/ADB MSBR
The MSG supports the SIP protocol. You can run SET DPA to configure the protocol distribution
ability.
Steps 3 and 4 are used to configure an SIP agent terminal.
You need to know the module number of the CCU, CSU, or IFM to be referenced before performing
step 3.
You need to know the multimedia device ID, local DN set, call source code, and charging source
code to be referenced before performing step 4.
In steps 3 and 4, you can run ADB MMTE or ADB MSBR to add multimedia devices or users in
batch. You can add up to 300 multimedia devices or users at one time.

SET
SET
ADB
ADB
ADB
2008-12-02
SIPCFG: MNP=5061, MXP=5188, SVP=5060;

SIPLP: MN=72, PORT=5601;
MMTE: SEID=K'99000, EEID=K'99299, MN=73, PT=SIP, IFMMN=35, AT=NA;
MMTE: SEID=K'99300, EEID=K'99499, MN=73, PT=SIP, IFMMN=35, AT=NA;
MSBR: SD=K'99000, ED=K'99299, LP=0, ET=COM, SEID=K'99000, RCHS=0, CSC=0;
Page 114 of 212
ADB MSBR: SD=K'99300, ED=K'99499, LP=0, ET=COM, SEID=K'99300, RCHS=0, CSC=0;
You need to refer to the values of some parameters of the hardware data and local exchange
data when you configure the SIP data. See Figure 1.1.
Figure 1.1 Parameter citing relations between SIP data and other data
Parameter Name
Location for Setting
MSG/CCU/CSU/IFM module number
Configuring hardware data
Local DN set
Configuring local exchange data
Call source
Configuring local exchange data
Charging source code
Configuring charging data
5.2.8 Configuring Routing Data

The routing data is used to define the routing-related configuration information, such as the
office direction, route, sub-route, and routing analysis data during number analysis and call
connection. You must finish configuring the local exchange data and signaling data before
configuring the routing data.
Data Preparation
Before configuring the routing data, prepare the data items listed in Figure 1.1.
SN
Item
Remarks
Signaling point code

of destination entity
This SPC is used to set up a direction between the local

exchange and the destination office.
Routing policy
You need to determine policies for selecting the preferred

trunk, sub-route, and trunk group of a route according to
network planning.
Basic routing data

planning
You need to determine the related route selection code and

route selection source code.
Figure 1.1 lists the steps for configuring the routing data.
2008-12-02
Page 115 of 212
Figure 1.1 Steps for configuring the routing data

Ste
p
Description
Command
Add an office direction.
ADD OFC
Add a sub-route.
ADD SRT
Add a route.
ADD RT
Add a time index.
ADD TMIDX (optional)
Add the routing analysis data.
ADD RTANA
In step 4, the time index is used for dynamic routing. The time index table divides a day into multiple
time segments on the basis of a week. Each time segment is identified by a time index. The system can
dynamically select routes based on the time segments during route analysis.
During initialization, the system sets a time index table with the time index 0. This table does not divide
a day into time segments. Therefore, this time index table cannot achieve dynamic routing. To support
routing based on time segments, you must run ADD TMIDX to add a time index.
After adding the time index, you must run ADD RTANA to modify all the route selection codes in the
system based on the routing analysis data corresponding to the new time index. Otherwise, routing may
fail.
Suppose that you configure a valid time index for a certain caller number when configuring the caller
number analysis data by using ADD CNACLR. After adding another time index by using ADD
TMIDX, you must change the caller number analysis data to match the new time index by using ADD
CNACLR.
ADD OFC: O=1, ON="TO_AIP_OFC", DOT=CMPX, DOL=SAME, DPC1="009826";
ADD SRT: SRC=1, O=1, SRN="TO_AIP_SRT", TSM=CYC;
ADD RT: R=1, RN="TO_AIP_RT", SRST=SEQ, SR1=1, TRIPFLAG=NO;
ADD RTANA: RSC=0, RSSC=0, RUT=ALL, ADI=ALL, CLR=ALL, TP=ALL, TMX=0, R=1,
ISUP=ISUP_M;
You need to refer to the values of some parameters of the local exchange data and signaling
data when configuring the routing data. You need to refer to the values of some parameters of
the routing data when you configure the trunk data and number analysis data. See Figure 1.1.
Figure 1.1 Parameter citing relations between routing data and other data
2008-12-02
Input Parameter
Output Parameter
Parameter
Name
Parameter
Name
Location for
Citing
Route selection
source code
Configuring local exchange

data
Sub-route
number
Configuring trunk
data
Page 116 of 212
Input Parameter
Output Parameter
Parameter
Name
Parameter
Name
Location for
Citing
Destination
point code
Configuring M3UA data or

configuring MTP data
DPC in office
direction
Configuring trunk
data (required by
No.7 trunks only)
Route selection
code
Configuring number
analysis data
the routing data.
2008-12-02
Page 117 of 212
You must define sub-routes in ADD SRT before citing them in ADD RT. If only one sub-route is
defined in ADD SRT, you do not need to set sub-routes 2 to 32 in ADD RT. If only two sub-routes are
defined in ADD SRT, you do not need to set sub-routes 3 to 32 in ADD RT. The same is true as the
number of defined sub-routes increases.
2008-12-02
Page 118 of 212
5.2.9 Configuring Trunk Data

The trunk data includes:
SIP trunk data
No.7 trunk data
R2 trunk data
You must finish configuring the hardware data, local exchange data, charging data, MGW
data, protocol data, signaling data, and routing data before configuring the trunk data.
Figure 1.1 shows a typical trunk networking of the UAP8100 MGC.
Figure 1.1 Typical trunk networking of the UAP8100 MGC
Figure 1.1 covers all the types of trunks accessed to the UAP8100 V300R003. You can configure the
data according to the actually accessed trunk and by referring to the description on the trunks in later
sections.
Configuring No.7 Trunk Data

The No.7 trunk data is used to configure the information related to No.7 trunks when you
connect the UAP8100 MGC to the PSTN switch. The information includes the signaling types
and CICs of No.7 trunk circuits. You must finish configuring the hardware data, local
exchange data, charging data, MGW data, signaling data, and routing data before configuring
the No.7 trunk data.
The No.7 trunk is a circuit trunk that uses the SS7 as the inter-office signaling. Because both
the TUP and ISUP protocols in the SS7 can be used to control inter-office trunk circuits, the
No.7 trunks can be divided into the TUP trunk and ISUP trunk.
CIC
The CIC is an important parameter for No.7 trunk interconnection. A CIC uniquely
identifies a trunk circuit between two SPs. The CIC is included in TUP and ISUP
messages only. The CIC contains 12 bits. Therefore, one trunk group supports up to 212
trunk circuits, that is, 4096 trunk circuits.
2008-12-02
Page 119 of 212
To connect two exchanges through the SS7, you must set the CIC of the same trunk circuit to the same
value at both exchanges; otherwise, exceptions occur. For instance, a channel is available in one
direction only.
Controlled and non-controlled trunk circuits

In a bi-directional trunk group, to prevent two exchanges from occupying the same trunk
circuit at the same time, the ITU-T defines that each of two connected exchanges
controls a half of all the trunk circuits. The principle is that the exchange with the larger
SPC controls circuits of even CICs. The exchange with the smaller SPC controls circuits
of odd CICs.
Based on this principle, each exchange occupies the controlled trunk circuits when
sending outgoing messages. The local exchange tries to occupy a trunk circuit controlled
by the peer office only when all the trunk circuits controlled by the local exchange are
busy. If the peer office also tries to occupy the trunk circuit at this time, the local
exchange gives up the trunk circuit and tries for the next.
If the UAP8100 is connected to a switch by using ISUP trunks and a specific circuit is not
controlled by the UAP8100 or peer office, the UAP8100 sends a UCIC message to the peer.
After receiving the UCIC message, switches of some vendors permanently block the circuit.
That is, you cannot restore the circuit even by resetting or re-configuring the circuit on the
softswitch. (Normally, slot 16 of each E1 circuit on the UAP8100 is left not configured. If the
peer configures this slot, the slot will be blocked).
The UCIC is a message type defined in the ITU-T standard protocol. The UCIC is not
supported in China. Thus, after receiving a UCIC message, switches of some Chinese vendors
permanently block the circuit. To support both international and Chinese standards, the
UAP8100 allows you to specify whether to send UCIC messages by using a software
parameter. By default, the international standard is supported. That is, the UAP8100 sends
UCIC messages. To change the value of the parameter, perform the following steps:
Change the value of the software parameter on the UAP8100 MGC that controls UCIC
sending. Set the value of bit 6 of software parameter P18 to 0.
Bit 6: Controls whether the UAP8100 sends UCIC messages when finding that no circuits are
available through the ISUP message (1: Send; 0: Not send)
1.
Run LST SFP to view the value of P18.
2.
Run MOD SFP to set the value of bit 6 in P18 to 0. Bit 6 is the seventh binary bit
counting from right. The rightmost bit is bit 0.
For instance, the original value of P18 is FFFF. After the value of bit 6 is set to 0, the
value of P18 is FFBF.
Data Preparation
Before configuring the No.7 trunk data, prepare the data items listed in Figure 1.1.
2008-12-02
Page 120 of 212

SN
Item
Remarks
OPC of the signaling in No.7 trunk

group
DPC of the signaling in No.7 trunk

group
These are used for interconnection

between the UAP8100 MGC and a PSTN
switch.
Direction of No.7 trunk group, that is,

outgoing trunk, incoming trunk, or
bidirectional trunk
Signaling type of No.7 trunk group,

that is, TUP or ISUP
Mode of selecting No.7 trunk circuits
Start CIC
Bearer sub-route of No.7 trunk circuit

(LST SRT)
CSU that manages No.7 trunk circuits
Number range of No.7 trunk circuit
The circuit number range is the unified

logical numbers of the No.7 trunk circuits
in the UAP8100 MGC. The physical
numbering of No.7 trunk circuits on the
trunk MGW is defined by the terminal ID
of the starting circuit.
10
UAP8100 MGW ID (LST MGW)
11
Terminal ID of circuit number
This item is used for interconnection

between the UAP8100 MGC and a trunk
MGW.
Figure 1.1 lists the steps for configuring the No.7 trunk data.
Figure 1.1 Steps for configuring the No.7 trunk data
2008-12-02
Step
Description
Command
Add a No.7 trunk group.
ADD N7TG
Add a No.7 trunk circuit.
ADD N7TKC
Add a PCM port.
ADD PCMPORT (optional)
Page 121 of 212
In step 3, for ISUP or TUP circuits, when you run ADD N7TKC to add a No.7 trunk circuit, the default
PCM type of the circuit is E1 and the default PCM encoding mode is rate A. In North America and
Japan, the PCM type of the trunk circuit is normally T1 and the PCM encoding mode is rate . At this
time, you need to run ADD PCMPORT to add a PCM port.
When configuring a trunk circuit, you need to specify the module number of a CSU or
CCU. In the case of multiple CSUs or CCUs, try to distribute circuits to the same office
direction in different CSUs or CCUs. Each CSU can manage up to 5,000 circuits. A
circuit number in a certain CSU or CCU is a unique logical code. You can add up to 320
trunk circuits at one time. Run this command for multiple times to add more than 320
trunk circuits. The TID must be preset in the MGW.
When adding a trunk circuit, make sure that a circuit number is uniquely related to a TID
to avoid a large workload in configuration at later stages.
ADD N7TG: TG=1, EID="192.168.20.13:2944", G=INOUT, SRC=1, TGN="TO_AIP_TG";
ADD N7TKC: MN=73, TG=1, SC=0, EC=31, SCIC=0, SCF=FALSE, TID="0", SEN=0;
You need to refer to the values of some parameters of the local exchange data, charging data,
MGW data, and routing data when configuring the No.7 trunk data. You need to use the
network management source code defined by the No.7 trunk data when you configure the
network management data. See Figure 1.1.
Figure 1.1 Parameter citing relations between No.7 trunk data and other data
Input Parameter
Output Parameter
Parameter
Name
Location for
Setting
Parameter
Name
Location for
Citing
Call source code
Configuring local
exchange data
Network
management source
code
Network
management data
Configuring charging
data

of outgoing trunk
Configuring charging
data
Equipment ID of
trunk MGW
Configuring media
gateway data
Sub-route number
Configuring routing
data
Restricted call group

number (optional)
Configuring
restricted call data
the No.7 trunk data.
2008-12-02
Page 122 of 212
Configuring R2 Trunk Data

The R2 trunk data is used to configure the information related to the R2 trunk on the
UAP8100 MGC. You must finish configuring the hardware data, local exchange data,
charging data, MGW data, signaling data, and routing data before configuring the R2 trunk
data.
In the UAP8100, the R2 trunks are used to bear narrowband resource data. They are used to connect the
VRB and the E32.
The R2 trunk is a circuit trunk. It uses the R2 signaling as the inter-office signaling. Because
the R2 signaling is a type of channel associated signaling (CAS), you need to set the
parameters related to the R2 signaling during configuration of the R2 trunk data.
The R2 signaling is defined in ITU-T Q.40Q.490; however, the realization mode of the R2
signaling varies from one country or area to another. Therefore, there are many versions of the
R2 signaling. Some versions, such as the Russian CAS, differ greatly from the standard
version of the R2 signaling.
Transmission modes
In a multi-segment route, there are two transmission modes of the CAS: end-to-end
mode and hop-by-hop mode.
End-to-end mode
The originating exchange sends a route-interpretable called number to the first transit
exchange. The first transit exchange interprets the route and connects the related
2008-12-02
Page 123 of 212
incoming trunk circuit and outgoing trunk circuit. Then, the call from the originating
exchange is connected to the next transit exchange. After that, the originating
exchange sends another route-interpretable called number to another transit
exchange. This transit exchange interprets the route and connects the related
incoming trunk circuit and outgoing trunk circuit. Then, the call from the originating
exchange is connected to the next transit exchange or the terminating exchange. The
same is true for the subsequent procedure. In this mode, a call is quickly connected
and the register is used efficiently; however, the signaling mode of the register must
be the same in each exchange on the multi-segment route.
Hop-by-hop mode
Each transit exchange must receive all the called numbers sent by the previous
exchange before forwarding the called numbers to the next transit exchange or
terminating exchange. This mode has low requirements for lines. In addition, the
signaling mode of the register can be different in each exchange on the multi-segment
route. In this mode, however, calls are slowly connected.
For the register signaling, the R2 signaling system in the UAP8100 MGC supports both
transmission modes at the same time. You can select a mode according to the line quality.
For instance, you can select the hop-by-hop mode on low-quality circuits. You can use
the end-to-end mode on high-quality circuits. For the line signaling, only the hop-by-hop
mode can be used.
Control modes
A control mode refers to a method of controlling the transfer process of the signaling.
There are three control modes:
Non-compelled mode (pulse mode)

The originating exchange keeps sending one pulse signal or one group of pulse
signals to the terminating exchange, regardless of whether the terminating exchange
receives the correct signal or signals. This mode features simple devices but low
reliability.
Half-compelled mode
The originating exchange sends one pulse signal or one group of pulse signals and
waits for the confirmation signal from the terminating exchange before sending the
next signal.
Full-compelled mode
The originating exchange keeps sending the forward signal before receiving the
confirmation signal from the terminating exchange. The terminating exchange keeps
sending the confirmation signal before the originating exchange stops sending the
forward signal. In this mode, the forward signal and backward signal are continuous.
Thus, this mode is also called continuous compelled mode.
Data Preparation
Before configuring the R2 trunk data, prepare the data items listed in Figure 1.1.
2008-12-02
SN
Item
Remarks
Direction of R2 trunk group,

that is, outgoing trunk,
incoming trunk, or bidirectional
trunk

the UAP8100 MGC and the UAP8100 MGW.
Page 124 of 212
SN
Item
Remarks
Number range of R2 trunk

circuit
The circuit number range is the unified logical

numbering of the R2 trunk circuits in the
UAP8100 MGC. The physical numbering of R2
trunk circuits on the trunk MGW is defined by
the terminal ID of the starting circuit.
Terminal ID of circuit number

the UAP8100 MGC and the UAP8100 MGW.
Figure 1.1 lists the steps for configuring the R2 trunk data.
Figure 1.1 Steps for configuring the R2 trunk data
Ste
p
Description
Command
Add an R2 trunk group.
ADD N1TG
Add an R2 trunk circuit.
ADD N1TKC
Add the configuration information of the

channel associated signaling.
ADD CASCFG
When adding a trunk circuit, make sure that a circuit number is uniquely related to a TID to
avoid a large workload in configuration at later stages.
ADD N1TG: TG=0, EID="192.168.0.201:2944", G=INOUT,
TGN="TO_VRB";
ADD N1TKC: MN=73, TG=0, SC=0, EC=255, TID="0";
ADD CASCFG: SN="TO_VRB";
SRC=100,
SN="TO_VRB",
You need to refer to the values of some parameters of the local exchange data, charging data,
MGW data, and routing data when you configure the R2 trunk data. You need to use the
network management source code defined by the R2 trunk data when you configure the
network management data. See Figure 1.1.
2008-12-02
Page 125 of 212
Figure 1.1 Parameter citing relations between R2 trunk data and other data
Input Parameter
Output Parameter
Parameter
Name
Location for
Setting
Paramete
r Name
Location for
Citing
Call source code
Configuring local
exchange data
Network
management
source code
Configuring
network
management data

of outgoing trunk
Equipment ID of
trunk MGW
Configuring media
gateway data
Sub-route number
the R2 trunk data.
Configuring SIP Trunk Data

An SIP trunk is a packet trunk. Different from the physical channel defined in the circuit
relay, the SIP trunk is defined as a logical channel used for internetworking, authentication,
and call addressing between local exchange and peer office.
The SIP trunk data is used to configure the relevant information when you connect the
UAP8100 to a softswitch or an SIP application server. The information includes the SIP-URL
and whether to support the SIP-T. You must finish configuring the hardware data, local
exchange data, charging data, protocol data, and routing data before configuring the SIP trunk
data. Figure 1.1 lists the step for configuring the SIP trunk data.
2008-12-02
Page 126 of 212
Figure 1.1 Step for configuring the SIP trunk data

SN
Description
Command
Add an SIP trunk group.
ADD SIPTG
The UAP8100 needs to set the SIP trunk, SIP session heartbeat, and support for the SIP-T
through negotiation with the peer. If the peer switch supports the heartbeat, set use heartbeat
to Yes. The minimum and maximum durations of the heartbeat timer are set through
negotiation between the UAP8100 and the peer switch. If you want the UAP8100 to support
the SIP-T and the peer switch supports the SIP-T, select SIP-T for incoming and outgoing
trunks. The SIP-T is not recommended now. For the description of parameters, see the online
help.
To set the trunk group number to 1, sub-route number to 1, IFM module number to 35, IP
address of the peer SoftX3000 to 10.23.6.68, and port on the peer SoftX3000 to 5060, and
enable the peer switch to support the heartbeat mechanism, run the following command:
ADD SIPTG: TG=1, CSC=0, SRT=1, RCHS=0, OTCS=0, IMN=35, OSU="10.23.6.68:5060",
UHB=YES, XHB=1;
In the case of the networked contact center (NCC) service, you need to configure two SIP
trunks for a UAP8100: the SIP trunk for connection with the local softswitch device and the
SIP trunk for connection with other UAP8100 devices in the NCC. When the NCC contains
multiple UAP8100s, you need to configure SIP trunks for directly connecting the local
UAP8100 to other UAP8100s.
5.2.10 Configuring Number Analysis Data

Data Preparation
Before configuring the number analysis data, prepare the data items listed in Figure 1.1.
SN
Item
Remarks
Prefix table
The prefix table is used to add call

prefixes in the system.
Call source code
These items are used to configure DN

processing.
Local DN set
Signal tone sending method
Number change index
3
2008-12-02
Number conversion type and related

information
This is used to configure number change.
Page 127 of 212
SN
Item
Remarks
Failure cause code
Failure source code planning
These are used to configure failure

processing data.
Failure processing type
The number analysis data includes the call prefix, number change, and prefix processing.
Figure 1.1 lists the steps for configuring the number analysis data.
Figure 1.1 Steps for configuring the number analysis data
Ste
p
Description
Command
Add a call prefix.
ADD CNACLD
Add the number change information.
ADD DNC
Add the prefix processing data.
ADD PFXPRO
Add the failure processing data.
ADD CFPRO (optional)
Before adding a call prefix, run related commands to obtain the following parameters defined
in the system:
Local DN set
To obtain this parameter, run LST LDNSET.
Route selection code

To obtain this parameter, run LST RTANA.
Charging selection code

To obtain this parameter, run LST CHGIDX.
ADD CNACLD: PFX=K'0771114, CSTP=ADD, MINL=7, MAXL=7;
ADD DNC: DCX=11, DCT=MOD, DCL=7, ND=K'1140771;
ADD
PFXPRO:
CSC=0,
PFX=K'0771114,
CCF=YES,
SENDTONE=NST,
ISREANA=YES;
2008-12-02
DDCX=11,
Page 128 of 212
In the case of the NCC service, you need to configure the number analysis data on the NCC
access code for the UAP8100. The service attribute is local outgoing call.
For instance, an NCC contains three sets of UAP8100:
UAP 1 is used for contact center 1. The area code of contact center 1 is 0755. The NCC
service access code is 111.
You need to configure the number analysis data on contact center 2 and contact center 3 for
UAP 1: Set 0756222 for contact center 2. Use the preset route to UAP 2 as the route selection
code. Set 0757333 for contact center 3. Use the preset route to UAP 3 as the route selection
code.
The procedure for configuring the number analysis data for UAP 2 and UAP 3 is similar to
that for UAP 1.
You need to refer to the values of some parameters of the local exchange data and routing data
when you configure the number analysis data. You need to refer to the values of some
parameters of the number analysis data when you configure the local exchange data and trunk
data. See Figure 1.1.
Figure 1.1 Parameter citing relations between number analysis data and other data
Input Parameter
Output Parameter
Parameter
Name
Location for
Setting
Parameter
Name
Location for
Citing
Local DN set
Configuring local
exchange data
Number change
index
Configuring local
exchange data and
configuring trunk data
Global DN set
Configuring local
exchange data
Call prefix
Number change
index (optional)
Configuring number
analysis data
the number analysis data.
2008-12-02
Page 129 of 212
For the parameters of ADD LDNSET and ADD CALLSRC in Figure 1.2, see related description in
section 5.2.3"Configuring Local Exchange Data."
5.2.11 Configuring Resource Data

Data Preparation
Before configuring data, you need to make preparations according to the items listed in Figure
1.1.
Figure 1.1 Preparations for configuring the resource data
2008-12-02
SN
Item
Remarks
Workstation planning
Plan the mapping relations between the

workstation numbers and module numbers of the
VRB or MSU, as well as the home relations of
the CDB module numbers.
Page 130 of 212
SN
Item
CDB module number

planning
Workstation type planning
Remarks
Plan workstation types for the VP, FP, and CP.
Configure whether to support the EC function.
NOTE
For the RBT service deployed on NGN, the EC
function is not required. For the IPCC application, the
EC function must be available on all CP workstations.
TID of the UAP8100 MGW
Plan the E1 circuit that bears voice streams.
UAP8100 MGW device ID

corresponding to a VRB
workstation
The ERI board of each VRB provides eight E1

trunk cables to directly connect to the E32 board
of the UAP8100 MGW. You need to know the
MGW ID and the corresponding TID.
IP address of the file server
IP addresses of the VRB or

MSU and the MEM board
When playing voices, the VRB or MSU needs to

communicate with the file server through the
MEM board.
IP address of the MRP pinch

board of the MSU
This IP address is used for the service bearing

channel.
Module number of the CCU

or CSU
This information is used for communication on

service handling.
10
IP address of the FEP on the

CTI
11
Remote port
Plan the IP port for connecting the FEP on the

CTI and the file server.
12
File sharing path on the file

server
All files played by the VRB or MSU are obtained

from the file server through this path.
Configuring Internal Resource Data

i. Configuring VRB Data
The configuration of the UAP8100 resource data consists of two parts:
Configure the related data of the R2 signaling when the VRB is considered as a virtual
office direction.
Configure the related data of the VRB workstation, such as the file server configuration
table, VRB workstation information table, and CDB resource assistance table.
The two parts are described as follows.

In the actual application of call center services, the VRB uses the E1 resources provided by
the MGW, and occupies the TIDs of a certain range. The VRB is considered as a virtual office
direction to achieve the following objectives:
2008-12-02
Page 131 of 212
The CDB can manage the trunk resources of the VRB as easily as it manages ordinary
trunk circuits.
Alarm information can be reported normally.
The CDB will not distribute call requests to a faulty VRB.

As a virtual office direction, the VRB does not have the signaling processing capability of the
ordinary signaling system number 7 (SS7). Thus, you need to configure the trunk resources
used by the VRB to R2 trunk circuits without configuring SS7 data.
Before configuring the VRB workstation information, you need to configure the office
direction table, sub-route, trunk group table, and trunk circuit table as you configure other
office directions. You can configure the VRB workstation information table only after
configuring the basic data. Otherwise, the maintenance console displays a message notifying
the failure of adding workstation information.
In the UAP8100, the VRB office direction data is automatically generated by default, with no
need to configure it. To manually add or change the VRB office direction data, see Figure 1.1.
Figure 1.1 Flow chart for configuring VRB office direction data
As the provider of narrowband voice playing and digit collecting resources on the platform,
the VRB board used by the UAP8100 is developed from the VRS component of the AIP.
When configuring VRB data, you need to set the working mode of the VRB, connecting to the
AIP or UAP. Other data is from the initialization file of the narrowband VP. You can convert
the original text file to the corresponding configuration commands.
Before configuring the VRB resource data, you need to make preparations according to the
items listed in Figure 1.2.
Figure 1.2 Preparations for configuring the VRB resource data
2008-12-02
SN
Item
Remarks
IP address of the VRB
This IP address is used to access the file

server or FEP.
Page 132 of 212
SN
Item
Remarks
Workstation number of the VRB

board
Each board is configured with two

workstations at present for logging in to the
CDB.
Installation and configuration of the

file server
The VRB can access files only through the

file server.
For the procedure for configuring R2 trunk circuits, see section 5.2.8"Configuring Routing
Data" and section 5.2.9"Configuring Trunk Data."
The general steps for configuring the VRB resource data is listed in Figure 1.3.
Figure 1.3 Procedure for configuring the VRB resource data
Ste
p
Description
Command
Add a VRB board.
ADD BRD
Configure public parameters, module

parameters, and software parameters
(optional).
MOD PUBPRM/MOD MPRM/

MOD SFP
Add the CDB module resource assistance

data (optional).
ADD CDBASSIST
Add a resource group.
ADD RCG
Add resource workstation information.
ADD RCWSCFG
Add the file server configuration.
ADD FILESVROR ADD

VRBFILESVR
Add the MEM board configuration.
ADD MEMCFG
Set the EC function (mandatory for CPs)
SET EC
Configure ACD service data (optional).
ADD ACD
10
Configure the Note parameters (optional).
MOD NOTEPRM
11
Configure IN parameters (optional).
MOD INCFG
12
Configure fax parameters (optional).
SET FAXPARA
13
Configure fax information (optional).
SET FAXCFG
Pay attention to the following points:
2008-12-02
Generally, you can use the default values of the public parameters, module parameters,
and software parameters in VRB data.
Generally, the CDB resource assistance is configured only when multiple pairs of CDB
boards exist.
Page 133 of 212
Before configuring the resource workstation information table, you need to configure the
resource group and resource trunk information.
You need to set whether to support the TTS function before adding resource workstation
data.
If the VRB board is set to the FP, you can use only the first two trunks. Other trunks are
not available.
The adding file server command in the version before V300R003C01B053 is ADD
VRBFILESVR, in the V300R003C01B053 version or later version, the command is
ADD FILESVR.
After the VRB board is successfully added, the system automatically adds the file server
information of the VRB. Therefore, you can only change the file server information but
not add it. When you change the file server information, note that the mapping drive
must be in lowercase. Otherwise, an error is reported in cyclic redundancy check (CRC).
When adding the MEM configuration to the VRB module, you need to set the protocol
type to NULL, and set the remote address to the address of the file server rather than the
address of the CTILINK. In the V300R003C01B053 version or later version, when
adding the MEM configuration, dont need to fill the remote IP.
If the VRB board is set to the CP, you need to enable the EC function.
After changing the values of the Note parameters by running MOD NOTEPRM, you
need to restart the VRB board to make the new values take effect.
After the EC function is enabled on the VRB board, you need to format and restart the board. Otherwise,
the VPM pinch board still loads the No EC program. That is, for any change to the VRB resource
capability, such as the EC, TTS, and fax functions, the VPM pinch board may load different software.
Therefore, you need to format and reload the VRB board after a change.
The following is an example for configuring VRB data (B023 version):

ADD RCG: GN=1, GNAME="TO_VRB";
//Add the workstation information table.
ADD
RCWSCFG:
WSNO=0,
INOUT=INSIDE,
GROUPNO=1,
MMN=27,
WSTYPE=VP,
MODULENO=252, EID="192.168.0.201:2944", SEPN=0, EPN=4, TID0="0", TID1="32",
TID2="64", TID3="96", DMODE=HALF, TTSCAP=SUP;
ADD
RCWSCFG:
WSNO=10,
INOUT=INSIDE,
GROUPNO=1,
MMN=27,
WSTYPE=CP,
MODULENO=251,
EID="192.168.0.201:2944",
SEPN=0,
EPN=4,
TID0="256",
TID1="288", TID2="320", TID3="352", DMODE=HALF, TTSCAP=SUP;
//Change the file server configuration.
MOD
VRBFILESVR:
MN=252,
FSTFSIP="192.168.0.4",
UID=65534,
GID=65533,
SDIR="/share", MDIR="Y:";
MOD
VRBFILESVR:
MN=251,
FSTFSIP="192.168.0.4",
UID=65534,
GID=65533,
//Set the IP address and port number for the VRB to communicate with the file
server, and then restart the VRB board.
ADD MEMCFG: MN=252, PROTYPE=NULL, LIP="192.168.0.30", RIP1="192.168.0.4",
RP=8888;
RP=8888;
//Configure the EC function.
SET EC: MN=251, STS=ENABLE;
//Change the values of the Note parameters.
MOD NOTEPRM: NOTEAMOUNT=36000;
ii. Configuring MSU Resource Data

The MSU resource data consists of the following items:
2008-12-02
Basic data, including the frame number, slot number, board location, board type, and
module number
MSU data, including the related workstation information.
Page 134 of 212
MRP data
Local IP address of the MSU
File server data
This chapter focuses on the configuration related to the built-in MSU. You can configure the
MSU resource data only after configuring the related CDB data.
When configuring the UAP8100 MGC, you need to cite certain parameter values set in the
CDB data for the MSU resource data. See Figure 1.4.
Figure 1.4 Relations between the parameters of the MSU resource data and other data
Input Parameter
Output Parameter
Parameter
Name
Location for
Setting
Parameter
Name
Location
for Citing
MSU resource group

number
CDB resource group

data
Module number of the

CDB to which the
workstation belongs
CDB data
Before configuring the built-in MSU resource data, you need to make preparations according
to the items listed in Figure 1.5.
Figure 1.5 Preparations for configuring the built-in MSU resource data
SN
Item
Remarks
IP address of each RMSU board
It is the IP address of the built-in RMSU

board.
IP address of each MRP pinch

board
It is the IP address of the service bearing

channel of the built-in RMSU.
IP address, protocol type, and

shared directory of the file server
These items are used to connect the MSU

and the file server.
The general procedure for configuring the built-in MSU resource data is listed in Figure 1.6.
Figure 1.6 Configuration procedure
2008-12-02
Step
Description
Command
Add an RMSU board.
ADD BRD
Add the MSU configuration.
ADD MSUCFG
Add the MRP configuration.
ADD MRPCFG
Set the local IP address of the MSU.
ADD MEMCFG
Page 135 of 212
ADD FILESVR (or ADD

MSUFILESVR)
Add the workstation configuration.
ADD RCWSCFG
Configure the Note parameters (optional).
MOD NOTEPRM
Configure IN parameters (optional).
MOD INCFG
The command for adding the file server configuration is ADD MSUFILESVR in
versions earlier than V300R003C01B030, and is ADD FILESVR in versions later than
V300R003C01B030. The V300R003C01B030 supports broadband features. Thus, in the
following description, the command for adding the file server configuration is ADD
FILESVR.
In the configuration of the built-in MSU resource data, the index on the key fields of each
data table is shown in Figure 1.7. You need to add the configurations of resource groups.
ADD BRD
[Frame number]
ADD MSUCFG
[MSU module number]
[Slot number]
[MRP lower board available]
[Module number]
[MRP upper board available]
ADD MRPCFG
[MSU module number]
[MRP board location]
[MRP IP address]
ADD MEMCFG
[MSU module number]
[Protocal Type]
[local IP address]
ADD FILESVR
[Module No]
[File Server IP Address]
[share directory]
iii. Adding the MSU Board Configuration
2008-12-02
Page 136 of 212
Figure 1.8 MML commands

Command
Description
ADD BRD
Add a board.
RMV BRD
Delete a board.
LST BRD
Query for a board.
When you run ADD BRD to add a RMSU board, the MRIA board is optional though it
must physically exist. The MSU board can work normally without the MRIA board.
Generally, you need to set the RMSU board to run independently. Thus, the Assistant
slot number parameter in the ADD BRD command must be set to 255.
iv. Configuring the MSU

Command
Description
ADD MSUCFG
Add the MSU configuration.
RMV MSUCFG
Delete the MSU configuration.
MOD MSUCFG
Modify the RMSU configuration.
LST MSUCFG
Query for the RMSU configuration.
The following is a sample command:

//Set the MSU board to the audio board.
ADD MSUCFG: MRFID=73, MRFTYPE=AUDIO, RSMD=EM;
v. Configuring the MRP

Command
Description
ADD MRPCFG
Add the MRP configuration.
RMV MRPCFG
Delete the MRP configuration.
MOD MRPCFG
Modify the MRP configuration.
LST MRPCFG
Query for the MRP configuration.
2008-12-02
Page 137 of 212
//The MRP configuration is to be added. The lower pinch board is located on the MSU
board; the pinch board type is audio; the module number of the MSU board is 213;
the IP address of the MRP is 191.169.1.123; the mask is 255.255.0.0.
ADD MRPCFG: MBID=213, BID=LMRPB, MRPT=MRPC, MIP="191.169.1.123", IPM="255.255.0.0";
vi. Configuring the Module Parameters of the MEM Board

Figure 1.11 lists the MML commands for configuring the module parameters of the MEM
board.
Command
Description
ADD MEMCFG
Add the MEM configuration table.
RMV MEMCFG
Delete the MEM configuration table.
MOD MEMCFG
Modify the MEM configuration table.
LST MEMCFG
Query for the MEM configuration table.
The ADD MEMCFG command is used to add two local IP addresses of the MSU for the
communication with the file server. The two local IP addresses of the MSU normally connect
to the two IP addresses of the file server respectively.
For the MSU, the PROTYPE field must be set to NULL.
For the MSU, the RIP1 field is not used. This field is set to the primary IP address of the
active file server in this document.
For the MSU, the RP field is not used. This field can be set to any value.
The local IP address is different from the local IP address 2, and they cannot belong to
the same network segment.
The TTSIP is different from the local IP address and the local IP address 2, and they
cannot belong to the same network segment. The TTSIP must belong to the same
network segment as the TTS Server.

ADD MEMCFG: MN=80, PROTYPE=NULL, LIP="192.168.0.80", RIP1="192.168.0.33", RP=1111,
LIP2="10.76.172.80", TTSIP="192.168.1.80";
vii. Configuring the File Server

2008-12-02
Command
Description
ADD FILESVR
RMV FILESVR
Delete the file server configuration.
MOD FILESVR
Modify the file server configuration.
LST FILESVR
Query for the file server configuration.
Page 138 of 212
You need to first add the file server record where the group number is 0.
The MSU supports up to 16 groups of file servers at present. The group numbers are
from 0 to 15.
The four file servers in each group have different addresses.
You need to set the UID and GID of only group 0. The UIDs and GIDs of other groups
are the same as those of group 0 by default. For Linux servers, the UID and GID are set
to 65534 and 65533 respectively. For Windows servers, the UID and GID can be set to
any values, but the values must be the same as those set for the NFS shared directory.
The primary and secondary IP addresses of the first and second file servers must comply
with the following rules:
To set the local IP addresses of the VRB or MSU, make sure that the local IP addresses
and the first or second IP address of the VRB or MSU belong to the same network
segment, that is, the network segment of the local IP address 1 or 2 in the ADD
MEMCFG command.
The following are sample commands:
//ADD MEMCFG LIP="192.168.0.80" LIP2="10.76.172.80", to configure three groups
of servers
ADD FILESVR: MN=80, IDXFS=0, FSTFSMIP="192.168.0.33",
FSTFSSBIP="10.76.172.148", SNDFSMIP="192.168.0.34", SNDFSSBIP="10.76.172.149",
SDIR="/share", MDIR="X:";
SDIR="/share1", MDIR="Z:";
//device number = 2, ADD MEMCFG LIP="0.0.0.0", to configure one group of
servers if LIP2 is not set
ADD FILESVR: MN=80, IDXFS=0, FSTFSMIP="172.22.201.1 ",
FSTFSSBIP="172.32.201.1", SNDFSMIP="172.22.201.2", SNDFSSBIP="172.32.201.2,
viii. Configuring Resource Workstation Data

Before configuring the resource workstation information table, you need to configure the
resource group and resource trunk information. The command for adding the MSU
workstation configuration is the same as that for adding the VRB workstation
configuration.
Figure 1.13 lists the MML commands for configuring the resource workstations.
2008-12-02
Command
Description
ADD RCWSCFG
Add a resource workstation.
RMV RCWSCFG
Delete a resource workstation.
MOD RCWSCFG
Modify a resource workstation.
LST RCWSCFG
Query for a resource workstation.
Page 139 of 212
The following are examples of the commands:

Command for configuring a fax workstation:
ADD RCWSCFG: WSNO=1, INOUT=INSIDE, GROUPNO=0, MMN=27, WSTYPE=MSUF, MODULENO=80;
Commands for configuring two audio stations that support the TTS function:
ADD RCWSCFG: WSNO=1, INOUT=INSIDE, GROUPNO=0, MMN=27, WSTYPE=MSUA, MODULENO=80,
MRPNO=0, TTSCAP=SUP;
ix. Configuring the Note Parameters

Command
Description
MOD NOTEPRM
Modify the settings of the Note parameters.
LST NOTEPRM
Query for the settings of the Note parameters.

MOD NOTEPRM: NOTEPATH="note", NOTEHEAD="note", UPDATEPATH="update",
NOTEAMOUNT=20000, STARTIDX=1, POSTFIX=DOT24, UPDATEINTERVAL=1000,
DELINTERVAL=2000;
x. Configuring the IN Parameters

Command
Description
MOD INCFG
Modify the settings of the IN parameters.
LST INCFG
Query for the settings of the IN parameters.

MOD INCFG: SERVICEPATH="service", STANDARDPATH="standard", TONEPATH="tone",
DEFAULTRBTPATH="default";
The Change of Fileserver Configuration

In the B053 version or later version, the VRB/MSU boards can support 16 groups of
fileserver, one group includes four suits of fileserver.
The VRB/MSU boards have to have two IP address, one IP address in one plane, and the two
IP address must not in the same IP segment. When the VRB/MSU boards have a natural
connection with fileserver, the IP address in 20 plane communicates with the First File
Server Master IP which added by the ADD FILESVRcommand. When there is a
connection mistake, the VRB/MSU boards find an usable fileserver by the order First File
Server Master IP, First File Server Slave IP, Second File Server Master IP, Second File Server
Slave IP.
2008-12-02
Page 140 of 212
The picture Figure 1.1 shows the change:

Figure 1.1 The change of the fileserver configuration
Array
Fiber
FS-1
A . FS

NFS
IP
192 .168 .4. xx (N
FS IP 1 NFS
IP 2
)
main .cf
Fiber
FS-2
Heartbeat
Float IP : 192 .168 . 3.30

GE
GE
5624 -1
GE
E
R
I
E
R
I
E
R
I
E
R
I
E
R
I
E
R
I
S
I
U
V
R
B
V
R
B
V
R
B
V
R
B
V
R
B
V
R
B
S
M
U
VRB 252
LIP :
RIP :
S
I
U
H
S
C
S
M
U
FS- 2
Heartbeat
GE
GE
GE
E
R
I
E
R
I
E
R
I
E
R
I
E
R
I
E
R
I
E
R
I
E
R
I
E
R
I
E
R
I
E
R
I
E
R
I
S
I
U
V
R
B
V
R
B
V
R
B
V
R
B
V
R
B
V
R
B
V
R
B
V
R
B
V
R
B
V
R
B
V
R
B
V
R
B
S
M
U
B. MGC
MOD FILESVR : MN =252 , IDXFS =IDX 0,

SNDFSMIP =" 192 .168 .4 .30 ";
5624 - 2
Trunk
192 .168 . 3.252

192 .168 . 3.30
Fiber
Float IP 1: 192 .168 .3 .30

Float IP 2: 192 .168 .4 .30
5624 -1
GE
H
S
C
FS-1
5624 -2
Trunk
Array
Fiber
GE
H
S
C
S
I
U
H
S
C
S
M
U
VRB 252
LIP :
RIP :
LIP 2:
RIP 2:
192
192
192
192
E
R
I
E
R
I
E
R
I
E
R
I
E
R
I
E
R
I
V
R
B
V
R
B
V
R
B
V
R
B
V
R
B
V
R
B
.168
.168
.168
.168
. 3 . 252
. 3 . 30
. 4 . 252
. 4 . 30
The change of MGC Configuration Data
Before the B053 version:

MOD VRBFILESVR: MN=252, FSTFSIP="192.168.3.30", UID=65534, GID=65533,
SDIR="/share", MDIR="y:";
After the B053 version:

ADD FILESVR: MN=252, PROTOCOL=NFS, IDXFS=IDX0, UID=65534, GID=65533,
FSTFSMIP="192.168.3.30", SNDFSMIP="192.168.4.30", SDIR="/share", MDIR="y:";
In the ADD FILESVR command, First File Server Master IP and First File Server Slave IP are need
parameter at least.
The change of Fileserver Configuration
Step 1 Open the file /etc/sysconfig/network/ifcfg-eth-****.

Step 2 Add the blue part as below in the file ifcfg-eth-****.
The file ifcfg-eth-**** is the network card configuration which provide the NFS service.
BOOTPROTO='static'
BROADCAST='192.168.3.255'
IPADDR='192.168.3.30'
MTU=''
NETMASK='255.255.255.0'
2008-12-02
Page 141 of 212
NETWORK='192.168.3.0'
REMOTE_IPADDR=''
STARTMODE='onboot'
LABEL_0=0
IPADDR_0=192.168.4.30
NETMASK_0=255.255.255.0
UNIQUE='svHJ.sWQdX4kVaYC'
_nm_name='bus-pci-0000:03:00.0'
Step 3 Modiry the file main.cf

Before modification:
IP fsip (
Device = eth3
Address = "192.168.1.110"
NetMask = "255.255.255.0"
)

Share dNFS_Share1 (
PathName = "/share"
Client = "192.168.1.0/255.255.255.0"
OtherClients = { "10.76.172.0/255.255.255.0",
"192.168.0.0/255.255.255.0" }
Options = "rw,async,insecure"
)
After modification:
IP fsip1 (
Device = eth3
Address = "192.168.1.110"
NetMask = "255.255.255.0"
)
IP fsip2 (
Device = eth3
Address = "192.168.4.110"
NetMask = "255.255.255.0"
)
Share dNFS_Share1 (
PathName = "/share"
Client = "192.168.1.0/255.255.255.0"
OtherClients = { "192.168.4.0/255.255.255.0",
"192.168.0.0/255.255.255.0" }
Options = "rw,async,insecure"
)
Configuring External Resource Data

The external resources of the UAP8100 are used as the TTS and ASR on the platform. The
principle is the same as that of the AIP.
2008-12-02
Page 142 of 212
Before configuring VP or FP resource data, you need to make preparations according to the
items listed in Figure 1.1.
Figure 1.1 Preparations for configuring external resources
SN
Item
Remarks
IP addresses of external
resources
The IP addresses are used for logging in to the FEP.
IP address of the CDB
The IP address is used to communicate with the FEP.
Workstation numbers of
external resources
The workstation numbers are used for logging in to the

CDB.
Figure 1.2 describes the general steps for configuring the VP or FP resource data.
Figure 1.2 Steps for configuring the VP or FP resource data
Step
Description
Command
Configure resource groups.
ADD RCG
Add resource workstation information.
ADD RCWSCFG
Add the MEM configuration of the CDB.
ADD MEMCFG
Add the MEM module information of the CDB to

the CTILINK.
The VP, FP, and FEP configurations are the same as those on the AIP. For details, refer to the
corresponding documents.
Relevant configurations are the same as the VRB resource configurations. The only difference is that
you need to set the resource type to external resources when configuring resource workstation
information.
The following is an example for configuring external workstation data:

ADD RCG: GN=2, GNAME="TO_VP";
//Add the workstation information table.
ADD RCWSCFG: WSNO=2, INOUT= OUTSIDE, GROUPNO=1, MMN=27, WSTYPE=VP, MODULENO=74,
EID="192.16.10.10:5500", SEPN=0, EPN=4, TID0="2048", TID1="2080", TID2="2112",
TID3="2144", DMODE=HALF, TTSCAP=NSUP;
ADD RCWSCFG: WSNO=2, INOUT= OUTSIDE, GROUPNO=1, MMN=27, WSTYPE=VP, MODULENO=74,
EID="192.16.10.10:5500", SEPN=0, EPN=4, TID0="2048", TID1="2080", TID2="2112",
TID3="2144", DMODE=HALF, TTSCAP=NSUP;
//Set the IP address and port number of the CDB.
ADD MEMCFG: MN=27, PROTYPE= FEP, LIP="192.168.1.102", RIP1="192.168.1.100",
RIP2="192.168.1.101", RP=5600, DGW="192.168.1.1";
2008-12-02
Page 143 of 212
When configuring the resource data, you need to cite certain parameter values set in the trunk
data and media gateway data. See Figure 1.1.
Figure 1.1 Relations between the parameters of resource data and other data
Input Parameter
Output Parameter
Parameter Name
Location for
Setting
Parameter
Name
Location for
Citing
VRB or MSU resource

group number
CDB resource
group data
Number of the CDB

module to which a
workstation belongs
CDB data
Media gateway ID
(narrowband)
Media gateway
data
Circuit end point ID

(narrowband)
Trunk data
Figure 1.2 shows the relations between the key fields of the data tables during the
configuration of the resource data.
2008-12-02
Page 144 of 212
5.2.12 Configuring TTS Service Data

Setting the TTS Connection Mode
When using the TTS, you need to set the connection mode for the TTS server and UAP VP.
The supported modes at present are the large-scale mode and small-scale mode. When the
large-scale mode is adopted, you need to set SRM support to SUP (Supported), and select
GTTSLICM(support). If the small-scale mode is adopted, you need to set SRM support to
NSUP (Not support), and run the SET WSLCS command to set the number of TTS licenses.
The setting must be reported to the CDB module. After the SET WSLCS command is
successfully run, you need to format and restart the VRB board. The VP program must also be
restarted. The SRM mode previously described is the load balancing function of the TTS. If
only one TTS server exists and the load balancing function is not enabled, you need to set the
TTS connection mode to the small-scale mode in the UAP configuration.
Note: After the TTS connection mode is set to the small-scale mode, you cannot see the status
of the TTS server on the TTS monitoring window of the UAP, or see the connection status of
the channel between the VRB board and TTS server on the program window of the TTS
server.
Figure 1.1 Commands
Command
Description
SET TTSCON
Set the TTS connection mode.
LST TTSCON
Query for the TTS connection mode.
Assume that the TTS connection mode is set to the large-scale mode on the UAP; the IP
addresses of the active and standby SRMs are 10.18.3.122 and 10.18.2.123 respectively; the
failure alarm threshold of the TTS server is 50; the value of TTS Server Fail Count Period
is 4. The command is as follows:
SET TTSCON: SRMSUP=SUP, MNSRMIP= "10.18.3.122", BKPSRMIP="10.18.2.123", SRVFCT=50,
SRVFCP=4;
Assume that the TTS connection mode is set to the small-scale mode on the UAP; the IP
address of the active TTS server is 10.12.12.1; the port number of the active TTS server is
3200; the user name is Jeevan; the company name is Huawei; the sequence number is
xcvg12h; the product name is TTS; the failure alarm threshold of the TTS server is 50; the
failure alarm statistics period is 4. The command is as follows:
SET TTSCON: SRMSUP=NSUP, PTTSIP="10.12.12.1", PTTSPRT=3200, UNAME="Jeevan",
CNAME="Huawei", SNO="xcvg12h", PNAME= "TTS", SRVFCT=50, SRVFCP=4;
Setting the Default File Path of the TTS

Set the default file path of the TTS. If a user does not specify any path, use the default path.
Figure 1.1 Commands
2008-12-02
Command
Description
SET TTSFP
Set the default file path of the TTS.
Page 145 of 212
LST TTSSFP
Query for the default file path of the TTS.
Assume that you need to set the file path of the TTS on the VRB board whose module number
is 100. The command is as follows:
SET TTSFP: MN=100, ACDFP="ACD", VFP="Voice", TVFP="Temp";
Setting the TTS Language

When using the TTS, you need to set the language for the TTS conversion.
Figure 1.1 Commands
Command
Description
ADD TTSLANG
Add a TTS language.
RMV TTSLANG
Delete an existing TTS language.
MOD TTSLANG
Modify the attributes of an existing TTS language.
LST TTSLANG
Query for the TTS language configuration.
Assume that the TTS language is Chinese; the converted voice format is 64 K linear wav; the
text code is GBK; the engine information is xxxx; the GBK punctuation is PUNC0-1 and
PUNC1-1. The command is as follows:
ADD TTSLANG: LANGID=CHINESE, VFRMT=LINEWAVE64K, TEXTENC=GBK, ENGINFO="xxxx",
GBKPUNC=PUNC0-1&PUNC1-1;
Setting Language Parameters

When using languages, you need to set the parameters of the corresponding language.
Figure 1.1 Commands
Command
Description
ADD LANGCFG
Add a language parameter configuration.
RMV LANGCFG
Delete an existing language parameter configuration.
MOD LANGCFG
Modify an existing language parameter configuration.
LST LANGCFG
List the language parameter information.
Assume that you need to add a language parameter configuration. The access code is
60022168; the language is Chinese; the maximum length is 120; the low-voice ratio is 100;
the medium-voice ratio is 100; the high-voice ratio is 100; the subsequent max length is 60.
The command is as follows:
2008-12-02
Page 146 of 212
ADD LANGCFG: AC=13431, LANGID= CHINESE, MAXLEN=120, VRATIO0=100, VRATIO1=100,

VRATIO2=100, SSML=60;
Adding the TTS Configuration

Add the TTS and ASR configurations.
Figure 1.1 Commands
Command
Description
ADD TTSASR
Add the TTS and ASR configurations.
MOD TTSASR
Modify the TTS and ASR configurations.
RMV TTSASR
Delete the TTS and ASR configurations.
LST TTSASR
Query for the TTS and ASR configurations.
Assume that you need to add the TTS configuration on the VRB board whose module number
is 252. The maximum number of TTS licenses is 20. The command is as follows:
ADD TTSASR: MN=252, TTSSRV=YES, ASRSRV=NO, SVSRV=NO, DGSRV=NO,
TTSPRVDER=INTERPHONIC, TEXTPATH="ttstext", WAVEPATH="ttswav",
BKWAVEPATH="backwav.wav", SVRIP="192.168.0.8", SVRIPMSK="255.255.255.0",
CONNRESNUM=20;
Setting the Default Parameter Values of the TTS

When using the TTS to produce voices, you need to use the default parameter values if the
specified parameter values are incorrect.
Figure 1.1 Commands
Command
Description
SET TTSPARA
Set the default parameter values of the TTS.
LST TTSPARA
Query for the default parameter values of the TTS.
Assume that the default language of the VRB board whose module number is 22 is Chinese,
and the default template is PUTOM. The command is as follows:
SET TTSPARA:MN=22, LANG= CHINESE, TMPL= PUTOM;
Setting the Background Music of the TTS

To play background music for the TTS, you need to set the background music files.
2008-12-02
Page 147 of 212
Figure 1.1 Commands

Command
Description
SET TTSBGM
Set the background music of the TTS.
LST TTSBGM
Query for the background music of the TTS.
Assume that the TTS of the VRB board whose module number is 100 supports the playing of
background music; the path of the background music file is y:\bgmusic.wav; the audio mixing
ratio is 20. The command is as follows:
SET TTSBGM: MN=100, BGMSUP=SUP, BGMF="y:\bgmusic.wav", MXR=20;
Setting the TTS Workstation Parameter

When using the TTS, you need to set the TTS workstation parameter. This parameter specifies
the alarm threshold for the TTS workstation failure.
Figure 1.1 Commands
Command
Description
SET TTSCFG
Set the TTS workstation parameters.
LST TTSCFG
Query for the TTS workstation parameters.
Assume that an alarm is triggered for the No. 20 TTS workstation on the VRB board whose
module number is 100 when the number of failure times in every three hours exceeds 1000.
The command is as follows:
SET TTSCFG: MN=100, WSNO=20, WSFT=1000, WSFP=3;
Setting the Number of Workstation Licenses

When using an external VP to implement the TTS or ASR function, or using a built-in VRB
board to implement the TTS function in small-scale mode, you need to set the number of TTS
or ASR licenses on the VP.
Figure 1.1 Commands
Command
Description
SET WSLCS
Set the number of workstation licenses.
LST WSLCS
Query for the number of workstation licenses.
Assume that you need to set both the numbers of TTS licenses and ASR licenses on the VP
whose workstation number is 20 to 10. The command is as follows:
SET WSLCS: WS=20, TTSL=10, ASRL=10;
2008-12-02
Page 148 of 212
Example of the TTS Configuration

The following is an example for the TTS configuration:
//Configure the information about the TTS server so that the boards can provide the
TTS function.
SET TTSCON: SRMSUP=SUP, MNSRMIP="192.168.0.85", BKPSRMIP="192.168.0.86";

//Configure the language information for the local terminal. (The engine names for
broadband and narrowband services must be set.)
ADD TTSLANG: LANGID=CHINESE, VFRMT=LINEWAVE64K, TEXTENC=GB-2312, ENGINFO="GXHBRZ",
GB2PUNC=PUNC0-1&PUNC1-1&PUNC2-1&PUNC3-1&PUNC4-1&PUNC5-1&PUNC6-1&PUNC7-1&PUNC81&PUNC9-1&PUNC10-1&PUNC11-1&PUNC12-1&PUNC13-1&PUNC14-1;
//Configure the parameters for segmentation.
ADD LANGCFG: AC=60022168, LANGID=CHINESE, MAXLEN=120, VRATIO0=100, VRATIO1=100,
//Set the number of TTS channels.
CONNRESNUM=20;
5.2.13 Configuring IPCC Service Data

Figure 1.1 describes the procedure for configuring the service data.
Figure 1.1 Procedure for configuring the service data
Step
Description
Command
Add the service console module settings.
ADD MODSRV
Add the service attribute table.
ADD SRVATTR
Add the service key distribution data.
ADD SRVKEY
Add the SRC of the IP service.
ADD IPSRC
Steps 3 and 4 are performed to configure the default service key (201) data. This data must be
configured for any type of applications.
The following is an example for steps 3 and 4:
\\The following two commands are run to configure the default service key data.
For the IPCC service, the data is used to play related tones for SIP trunks;
for the RBT service on NGN, the data is used to play the default RBT. The
default service key data must be configured for any type of applications.
ADD SRVKEY: MN=80, SRVKEY1=201;
ADD IPSRC: SKEY=201, MN=80;
2008-12-02
Page 149 of 212
Adding Service Module Settings

Figure 1.1 Commands
Command
Description
ADD MODSRV
Add the service console module settings.
RMV MODSRV
Delete the service console module settings.
MOD MODSRV
Modify the service console module settings.
LST MODSRV
Query for the service console module settings.
These commands are used to set the corresponding services supported by each UAP8100
module. The value-added services supported by the UAP8100 include the ACD, ICD, AP,
INTESS, TUA, and CRBT. These services are described as follows:
The ACD service is a traditional call distribution service that provides the agents and IVR
flow with a single function.
The ICD service is a new call distribution service that provides the agents with multiple
functions and serves the service systems such as the call processing center.
The AP service is an automatic paging service that serves the automatic paging center.
The INTESS service is a service that uses the INTESS protocol and serves the traditional 160
and 168 information centers.
The TUA service is used by TUA remote agents or IP agents.
The CRBT service is the color ring back tone service.
The service console module setting table stores the basic data of the ICD service. The service
numbers generated by this table are used by other tables.
Adding the Service Attribute Table

Figure 1.1 Commands
Command
Description
ADD SRVATTR
Add the service attribute table.
RMV SRVATTR
Delete the service attribute table.
MOD SRVATTR
Modify the service attribute table.
LST SRVATTR
Query for the service attribute table.
The ADD SRVATTR command is used to set the access code and number length of the
service console. The access code and number length are used for intelligent service number
analysis. You need to add a call prefix that is consistent with the access code before adding the
corresponding service console attribute.
2008-12-02
Page 150 of 212
Each access code corresponds to a service number that records the type of the service console
module.
Before configuring the service attribute table, run the related commands to query for the
defined parameters in the following tables:
Number analysis table
Service console module setting table

When the time delay trigger point and triggering delay set in the called number analysis table for the call
prefix are inconsistent with those set in the service attribute table, the system uses the delay triggering
point and triggering delay set in the service attribute table.
Before configuring the IPCC service data, make sure that the MEM module information of the CSU or
CCU is already configured, and the MEM module can normally communicate with the CTILINK.
Otherwise, the service prefix cannot reach the platform.

ADD MEMCFG: MN=73, PROTYPE=FEP, LIP="192.168.0.20", RIP1="192.168.0.2",
RIP2="192.168.0.3", RP=5600;
ADD CNACLD: PFX=K'114, CSTP=ADD, MINL=3, MAXL=3;

ADD MODSRV: SRVTYPE=ICD, SRVNAME="114", SRVDESC="114", ATTRIB=GLOBAL;
ADD SRVATTR: DNSET=0, ACCESS=K'114, SRVNO=0;
5.2.14 Configuring Parameters

For the descriptions of the UAP public parameters, module parameters, and software
parameters, refer to the UAP Parameter Description corresponding to the UAP version.
Currently, the only parameter whose value must be changed is the No.P245 software
parameter. The command for changing the parameter value is MOD SFP: ID=P245,
VAL="0";. The following table describes the meaning of the No.P245 software parameter.
Parame
ter No.
Descriptio
n
P245
Indicates the
policy for
handling the
file server
faults.
Value
Range
Defau
lt
Value
Remarks
Bit (0-15): This parameter

determines whether the CDB
blocks the corresponding media
resource workstation when a fault
occurs on the file server.
0: No
1: Yes
The IPCC system of the customer service center involves only a small number of voice files.
The voice files that are played many times will be stored to the cache of the VRB board. In
this case, you need to change the value of the No.P245 parameter to 0, which indicates that
the workstation channel is not blocked when a fault occurs on the file server. Thus, the VRB
board can play the voice files stored in the cache, and the system reliability is improved.
For other parameters, you can change their values according to the actual service
requirements. Examples are as follows.
2008-12-02
Page 151 of 212
Public Parameters
None.
Module Parameters
MML command: MOD MPRM
Pay attention to the module parameters listed in the following table.
Parame
ter No.
Description
Value
Range
Default
Value
Remark
s
P83
Indicates the number of ITU

and TCAP state machines
that can coexist on the UAP.
0-65535
20000
P86
Indicates the number of

ANSI TCAP state machines
that can coexist on the UAP.
0-65535
20000
Generally, the memory distributed to the CSU or CCU board on the UAP after startup is 87%.
If plenty of circuits and multimedia users are distributed to the CSU or CCU for management,
more memory is distributed to the CSU or CCU after startup. As a result, the CSU or CCU
board occupies too much memory, and the CSU or CCU board is repeatedly restarted. To
solve this problem, you can change the values of the No.P83 and No.P86 parameters to reduce
the memory distributed to the CSU or CCU board after startup. The commands are as follows:
MOD MPRM: ID=P83, VAL=100; //Number of ITU TCAP state machines
MOD MPRM: ID=P86, VAL=100; //Number of ANSI TCAP state machines
After the values of the module parameters are changed, format data and restart the
board. Then the memory distributed to the CSU or CCU board after startup is reduced
by about 6%.
Software Parameters
MML command: MOD SFP
Pay attention to the software parameters listed in the following table.
2008-12-02
Parame
ter No.
Descriptio
n
Value
Range
Defau
lt
Value
Remarks
P226
Indicates the
default voice
playing
format of the
VRB.
The meanings of the values are as

follows:
2: 24 K VOX
4: 64 K WAV
8: 32 K VOX
16: A Law
32: Mu Law
Page 152 of 212
Parame
ter No.
Descriptio
n
Value
Range
Defau
lt
Value
Remarks
P227
Indicates the
default voice
recording
format of the
VRB.

follows:
P238
2: 24 K VOX
4: 64 K WAV
8: 32 K VOX
16: A Law
32: Mu Law

follows:
2: 24 K VOX
4: 64 K WAV
8: 32 K VOX
16: A Law
32: Mu Law
You can change the default voice recording or playing format of the VRB or MSU
according to the actual situation and customer requirements.
Parame
ter No.
Descriptio
n
Value
Range
Defau
lt
Value
Remarks
P86
Indicates the
call internal
parameter 5.
7FFF
The default value in Hongkong is

EFFF.
2008-12-02
Indicates the
default voice
playing
format of the
MSU.
Check whether the outbound numbers of the local office need to carry area codes. If yes,
change the value of the No.P86 software parameter to 7F7F. For example, when the
ADD LDNSET command specifies that the local area code for toll calls is 0771 and the
outbound calling number is 07711234567, you see 1234567 in the result of signaling
tracing if the value of the No.P86 software parameter is not changed. The area code 0771
is missing. If the outbound calling number is 07721234567 and the value of the No.P86
software parameter is not changed, you see 7721234567 in the result of signaling tracing.
The number 0 in the area code is deleted, which causes the failure of the calls whose
calling numbers must be analyzed.
Parame
ter No.
Descriptio
n
Value
Range
Defau
lt
Value
Remarks
P50
Indicates the
call internal
parameter 2.
FFFF
The default value in Singapore is

F7FF.
Page 153 of 212
If a call is sent from the MGC to the platform and a zero is added to the calling number,
you can change BIT3 in the No.50 software parameter to delete the zero. The changed
value of the No.50 software parameter is FFF7. The meaning of BIT3 is as follows:
BIT3: It indicates whether the URP8100 MGC changes the calling number according
to the address nature when the called party is a local subscriber and has the
CID right.
When BIT3 = 1, a zero (for domestic numbers) or two zeroes (for international
numbers) are added to the calling number.
When BIT3 = 0, the calling number is not changed. This parameter has similar
function to BIT14 in the call internal parameter 1.
5.2.15 Other Configurations on the MGC

Setting the Timeout Interval of a Command
To set the timeout interval of a command on the MGC client, choose System > Command
timeout settings > MML Command Time Out(Sec)/Monitor Command Time Out(Sec),
and set the two parameters MML Command Time Out(Sec) and Monitor Command Time
Out(Sec) to 60 to prevent timeout messages.
When you configure data online and a large amount of data is involved (for example, adding circuits or
SIP users), it takes a long time for the command to complete running and timeout may occur. Therefore,
you are advised to set the timeout interval to a relatively large value.
Setting the Security Policy

To avoid account locking caused by abnormal disconnections on the MGC client, you need to
set the security policy for an account before debugging.
Figure 1.1 Commands
Command
Description
SET SECPOLICY
Set the security policy for the global account.
LST SECPOLICY
Delete the service attribute table.
Change the number of the same accounts that can be concurrently online to 10, and change
the locking duration of the account to 5, in minutes.
SET SECPOLICY: ENABLEPOLICY=TRUE, OPLOCKTIME=5, ADMINLOCKTIME=5, OPONLINE=10;
Loading the Grammar Module

Different grammars are used to play the basic announcement in different languages. Thus,
different grammar modules must be loaded. A grammar module must match the loaded
standard voice.
To download the grammar packages, visit http://support.huawei.com and choose:
2008-12-02
Page 154 of 212
Software > Version Software > Application and Software Product Line > Service and
Software Public > AIP&ACD > C&C08-AIP > GAM > GAM_OSTAV1.1XXXXX
To know the version of the grammar package in the required language, query the version
description document in the grammar package of each version.
The procedure for installing a grammar package is as follows:
Step 1 Refer to the grammar package upgrade guide to back up the .ddm file in the Data directory
on the BAM.
Step 2 Run the grammar package installation program, select the language required in the local
country or area, and complete the installation according to the messages displayed on the
screen.
Step 3 Check the Data directory on the BAM for the .ddm file of the selected language.
Step 4 Run LST LANGID to check whether the .ddm file of the selected language is loaded. If yes,
run RMV LANGPKG to delete the .ddm file on each VRB module.
Step 5 Run SET LANGID to bind the .ddm file to the ID of the language to be loaded. If the
language ID is smaller than or equal to 24, you do not need to change the language name.
Otherwise, you need to change the language name. The language ID is very important and
must match the tone code.
Step 6 Run LOD LANGPKG to load the .ddm file to the VRB board of each module. If there are
two or more languages, make sure that the grammar packages of all the required languages
are loaded to the VRB board of each module.
Step 7 Run ACT LANGPKG to activate the .ddm file of each loaded language on the VRB board of
each module.
Step 8 Test the voice playing in the selected language. If no problem is found, run CON LANGPKG
to confirm the .ddm file. After this operation, the .ddm file is automatically loaded when the
VRB board is restarted. Perform this operation on all VRB modules.
Step 9 Run SPD LANGPKG to check the grammar package status on each VRB. Make sure that the
required grammar packages are loaded on the VRB board of each module, and all the
grammar packages are in Running state.
Pay attention to the following points:
When loading a grammar package, you need to set the loading switch of the VRB board
to program writable and data writable by running MOD LSS.
If the grammar package of the required language is not available at

http://support.huawei.com, or the existing grammar rules cannot meet requirements, you
need to collect the grammar rules and submit the requirements to the R&D department
through the workflow.
The UAP is already embedded with the grammar module for English and Mandarin by
default. If you use the basic announcement in the two languages, no grammar module
needs to be loaded.
----End
2008-12-02
Page 155 of 212
5.3 MGW Data Configuration

5.3.1 Procedure for Configuring MGW Data
As the media gateway, the UAP8100 MGW provides the IP access and the speech path access
for narrowband services. In addition, narrowband VRBs use the external E1 ports provided by
the UAP8100 MGW as resource channels. Therefore, the UAP8100 MGW data includes the
following items:
Basic hardware data
Data for the connection to the MGC
TDM bearer data required by the VRB
TDM bearer data required for the narrowband interoperability with the PSTN
IP bearer data required for the interoperability with the broadband network.
Figure 1.1 shows the general procedure for configuring the UAP8100 MGW data.
2008-12-02
Page 156 of 212
Figure 1.1 General procedure for configuring the UAP8100 MGW data
5.3.2 Configuring Hardware Data

The hardware data of the UAP8100 MGW includes the frame data, board data, clock data,
and network management interface data. This section provides several rules for configuring
boards.
Figure 1.1 Board description
2008-12-02
Board
Name
Board
Description
Slot Restriction
Working
Mode/Remarks
CMF
Front connect
management unit
The CMF board is placed in

the universal front slot. There
is no restriction on front and
back insertion.
1+1 backup
Page 157 of 212
Board
Name
Board
Description
Slot Restriction
Working
Mode/Remarks
CLK
Clock unit
The CLK board is placed in

back slots 0 and 1 in the main
control frame. There is no
restriction on front and back
insertion.
1+1 backup
SPF
Front signaling
processing unit
The SPF board is placed in

the universal front slot. There
back insertion.
Load sharing
HRB
High-speed
routing unit
The HRB board is placed in

the universal front slot.
Except front slots 0 and 1 in
the main control frame, the
corresponding back interface
unit is the E8T.
1+1 backup
E8T
Ethernet 8-port
twisted-pair
interface unit
The E8T board is placed in

the universal back slot.
Except back slots 0 and 1 in
the main control frame, the
corresponding front board is
the HRB.
None
OMU
Operation &
maintenance unit
The OMU board is placed in

front slots 7 and 8 in the main
control frame.
1+1 backup
The corresponding back

board is the NET.
MPU
Main processing
unit
The MPU board is placed in

front slots 7 and 8 in the
frames other than the main
control frame.
1+1 backup

board is the NET.
NET
Network packet
switch unit
The NET board is placed in

back slots 7 and 8.
1+1 backup
The corresponding front

board is the MPU or OMU.
TNU
TDM central
switching net unit
The TNU board is placed in

back slots 6 and 9.
1+1 backup
There is no restriction on
front and back insertion.
VPB
Voice processing
unit
The VPB board is placed in

the universal front slot.
2008-12-02
Load sharing
The FVGU is the
private VPU board in
the VIG networking.
Page 158 of 212
Board
Name
Board
Description
Slot Restriction
Working
Mode/Remarks
FLU
Front link unit
The FLU board is placed in

the front slots other than front
slots 6, 7, 8, and 9 in the
central switching frame.
1+1 backup

board is the BLU.
BLU
Back link unit
The BLU board is placed in

the back slots other than back
slots 6, 7, 8, and 9 in the
central switching frame.
1+1 backup
The corresponding front

board is the FLU.
E32
32*E1 port TDM

interface board
The E32 board is placed in

Load sharing
T32
32*T1 port TDM

interface board
The T32 board is placed in

the universal back slot,
except back slots 0 and 1 in
the main control frame. There
back insertion.
Load sharing
S2L
2*155M
SDH/SONET
optical interface
card
The S2L board is placed in

Load sharing or 1+1

backup
Echo cancellation
unit
The ECU board is placed in

the front slots other than front
slots 7 and 8 in the main
control frame and service
frames.
ECU
-
Figure 1.2 Procedure for configuring MGW hardware data
2008-12-02
Step
Description
Command
Add a frame.
ADD FRM
Add a board.
ADD BRD
Set the time synchronization type.
SET TIMESYC
Set the time zone.
ADD ZONE
Page 159 of 212

MOD FRM: FN=1, FNM="GXHBRZ_MGW", FD="GXHBRZ_MGW";
ADD BRD: FN=1, SN=0, BP=FRONT, BT=VPU, HBT=VPB, BS=LOADSHARE,
ADS=ACTIVE;
ADS=ACTIVE;
ADD BRD: FN=1, SN=2, BP=FRONT, BT=CMU, HBT=CMF, BS=ONEBACKUP, BN=30;
ADD BRD: FN=1, SN=14, BP=FRONT, BT=HRB, HBT=HRU, BS=ONEBACKUP, BN=0;
ADD BRD: FN=1, SN=0, BP=BACK, BT=CLK, HBT=CLK, BS=ONEBACKUP, BN=0;
ADD BRD: FN=1, SN=2, BP=BACK, BT=E32, HBT=E32, BS=LOADSHARE,
ADS=ACTIVE;
ADS=ACTIVE;
ADD BRD: FN=1, SN=6, BP=BACK, BT=TNU, HBT=TNU, BS=ONEBACKUP, BN=1;
ADD BRD: FN=1, SN=14, BP=BACK, BT=E8T, HBT=E8T, BS=NULLBACKUP, BN=0;
SET TIMESYC: INFO=RTC;
SET ZONE: ZONE=8;
BN=0,
BN=1,
BN=0,
BN=1,
5.3.3 Configuring Data for the Connection to the

MGC
The UAP8100 MGC completes call control, and the UAP8100 MGW completes service
bearing. The MGC and MGW communicate with each other by using the standard media
gateway control protocol H.248.
Figure 1.1 Procedure for configuring data for the connection to the MGC
Figure 1.2 shows the relations between the key parameters in configuration commands.
2008-12-02
Page 160 of 212
Figure 1.2 Relations between the key parameters in configuration commands
Figure 1.3 Procedure for configuring data for the connection to the MGC
Step
Description
Command
Add an IP address.
ADD IPADDR
Modify the IP interface configuration.
MOD IPIF
Add a static route.
ADD ROUTE
Set a virtual media gateway.
SET VMGW
Add a media gateway controller.
ADD MGC
Add an H.248 signaling link.
ADD H248LNK
Set the H.248 parameters (optional).
SET H248PARA
Activate the virtual media gateway.
ACT VMGW
2008-12-02
After adding the IP address of an interface, you need to change the interface attributes as
follows: If the HRB is used to transfer messages in a centralized way, the network
interface must work in 100 Mbit/s full duplex mode. If the MPU in the central switching
frame is used to transfer messages, the corresponding network interface works in auto-
Page 161 of 212
negotiation mode. Generally, the first network interface on the E8T board is used to bear
the H.248 signaling links.
A default static route must be set. On-site deployment engineers, however, often forget
this.
For the setting of virtual media gateways (VMGWs), one MGW can support up to 16
VMGWs and can connect with up to 16 MGCs. These VMGWs share one physical
MGW. The value of MIDTYPE is always IP. The MGW ID uses the IP address + Port
number format. The value of Max. loss HB count is 5. When the MGW and MGC are
located in a poor network environment, you need to set this parameter.
When you set the parameters of the VMGW, please make the value of the parameter
RLSINTV equal to Three Minutes.
When you add an MGC, the combination of one VMGWID and one MGCID identifies
only one connection between the MGW and MGC. The MGW must be in Master state.
When you add an H.248 signaling link, use UDP as the transfer protocol.
The H.248 parameters are optional. You can use the default values for these parameters.
That is, select the BINARY coding scheme and the UDP transfer protocol for the
UAP8100 application.

ADD IPADDR: BT=HRB, BN=0, IFT=ETH, IFN=0, IPADDR="192.168.0.201",
MASK="255.255.255.0", DSTIP="0.0.0.0";
MOD IPIF: IFT=ETH, BT=HRB, BN=0, IFN=0, MTU=1500, ENABLE=YES, DESP="Ethernet
Interface", SPEED=M100, DUPLEX=FULL, AUTH=NONE, TIMEOUT=3, CRCLEN=BITS32,
KEEPALIVE=10, AUTONEGO=YES, VENABLE=NO, VID=6, IFSTAT=YES, ENRATE=NO, RATE=10000,
ENPOE=NO;
ADD ROUTE: BT=HRB, BN=0, DSTIP="192.168.0.200", DSTMASK="255.255.255.0",
RTTYPE=NEXTHOP, PREF=60, FLAG=NORMAL, NEXTHOP="192.168.0.200";//when the HRB is
used to transfer messages in a centralized way
SET VMGW: VMGWID=0, MIDTYPE=IP, MID="192.168.0.201:2944", RPTIMES=3, RPINTV=3,
RLSINTV=3, LNKFAILLEN=30, IPNUM=86016, TDMNUM=400384, ATMNUM=221184, AUTOSWP=YES,
LNKHBTIME=3, LNKMAXHBLOSS=5, STACKVER=1;
ADD
MGC:
VMGWID=0,
MGCIDX=0,
MIDTYPE=IP,
MID="192.168.0.200:2944",
MSS=MASTER;
ADD H248LNK: LINKID=0, VMGWID=0, MGCIDX=0, TT=UDP, LOCALIP="192.168.0.201",
LOCALPORT=2944, PEERIP="192.168.0.200", PEERPORT=2944, LINKNAME="TO_GXRZMGC",
FN=0, SN=0, BP=FRONT;
ACT VMGW: VMGWID=0;
If multiple frames are cascaded in the MGW, you need to use the MPU in the central switching
frame to transfer H.248 messages. If only the main control frame exists, you can use the HRB to
transfer H.248 messages in a centralized way.
If you use the HRB to transfer H.248 messages in a centralized way, do not use the third interface of
the E8T as the interface for transferring messages. In addition, you need to run MOD IPIF to set the
interface for transferring messages to work in forced 100 Mbit/s full duplex mode. If you use the
MPU in the central switching frame to transfer H.248 messages, the corresponding interface works
in auto-negotiation mode.
Do not forget to configure routing data.
5.3.4 Configuring Signaling Link Data
2008-12-02
Page 162 of 212
If the UAP8100 MGW does not bear SS7, skip this section.
As an integrated signaling gateway, the UAP8100 MGW converts SS7 to M2UA signaling,
and then sends the signaling to the UAP8100 MGC.
Figure 1.1 shows the typical networking.
Figure 1.1 Typical signaling networking of the UAP8100 MGW
UAP8100
MGC
M2UA
No.7
PSTN
UAP8100 MGW
Data Preparation
Figure 1.1 Preparations for configuring signaling link data
SN
Item
Remarks
M2UA link group numbers
M2UA link numbers
Number of the SPF board for

processing the M2UA protocol
Local or remote IP address
Local or remote SCTP port

number
The data must be consistent with that on the

peer UAP8100 MGC.
Figure 1.1 describes the procedure for configuring the M2UA data of the UAP8100 MGW.
Figure 1.1 Procedure for configuring M2UA link data
Ste
p
2008-12-02
Description
Command
Page 163 of 212
Ste
p
Description
Command
Add an M2UA link.
ADD L2UALNK
Add an MTP2 signaling link.
ADD MTP2LNK
In steps 1 and 2, the protocol type in the configuration commands must be M2UA.
ADD L2UALKS: PROTYPE=M2UA, LKS=0, TM=OVERRIDE;

//Add an M2UA link.
ADD
L2UALNK:
PROTYPE=M2UA,
BN=0,
LNKNO=0,
LKS=0,
LOCALPN=2904,
LOCALIP1="192.16.254.49", REMOTEPN=2904, REMOTEIP1="192.16.254.38", PRIO=0;
ADD
L2UALNK:
PROTYPE=M2UA,
BN=0,
LNKNO=1,
LKS=0,
LOCALPN=2904,
LOCALIP1="192.16.254.49", REMOTEPN=2910, REMOTEIP1="192.16.254.38", PRIO=1;
//Add an MTP2 signaling link.
ADD MTP2LNK: LNKNO=0, LKS=0, BINIFID=0, LNKTYPE=MTP2_64K, IFBT=E32, IFBN=0,
E1T1N=8, STRTTS=16, SPFBN=0, SUBBN=1;
The SIGTRAN protocol and H.248 protocol between the UAP8100 MGC and UAP8100 MGW can be
borne by the same network cable.
5.3.5 Configuring Bearing Data

Configuring TDM Bearing Data
When configuring the TDM bearing data for the UAP8100 MGW, you need to set E1 port
parameters and add TDM endpoints.
The UAP8100 MGW uses the TDM interface (E1) provided by the E32 or S2L interface
board. Each E32 board has two physical interfaces. Each interface has 16 E1 lines that support
the access of 32-line E1 users in total. E1 port transmission lines consist of the 120-ohm
twisted pair cable and 75-ohm coaxial cable. The E1 coaxial cable with 75-ohm characteristic
impedance must be grounded in non-balancing mode.
The S2L interface board provides the SDH optical interface and bears large-capacity TDM
services. During the interconnection with the SDH optical interface, check whether the
parameters such as subscription and unsubscription bytes, frame type, load type, and framing
mode are consistent with those on the peer device. If not, the interconnection fails. The
function of monitoring the SDH interface performance is optional.
By default, the DIP switch on the E32 board is set to support the access by using the 75-ohm
coaxial cable.
Setting the E1 Port Parameters
When the UAP8100 MGW is interconnected with TDM devices through the E1 port, the
frame format and line code format at the two ends must be consistent.
2008-12-02
Command
Description
SET E1PORT
Set the port attributes of the E32 board.
DSP E1PORT
Query for the port status of the E32 board.
Page 164 of 212
When you run SET E1PORT to set the frame format, make sure that the frame format is consistent
with that at the peer end. The frame format of the E32 board for connecting external trunks must be
consistent with that in the peer office. The frame format of the E32 board for connecting internal
trunks must be consistent with that of the ERI board. If the CRC function is disabled on the ERI
board, the frame format must be DOUBLE_FRAME. If the CRC function is enabled on the ERI
board, the frame format must be CRC4_MULTIFRAME.
If the frame formats at the two ends are inconsistent, the E1/T1 remote alarm occurs on the MGW.
Setting the SDH Interface Attributes

The S2L board provides two STM-1 SDH optical interfaces. When you configure the SDH
interface, make sure that the parameters such as the frame type, load type, framing mode, and
frame format are consistent with those of the peer SDH interface.
Command
Description
SET S2LPORT
Set the S2L interface attributes.
DSP S2LPORT
Query for the S2L interface attributes.
SET S2LFRM
Set the S2L frame format.
DSP S2LFRM
Query for the S2L frame format.
Adding TDM Endpoints

For TDM bearing, one trunk provides 32 timeslots (for T1, the last eight timeslots are not
available). In the H.248 protocol, a timeslot is a terminal resource, that is, a termination ID
(TID). The UAP8100 MGC matches a trunk circuit with a physical timeslot at the UAP8100
MGW side through a TID.
The UAP8100 MGW supports VMGWs, and the TDM resources of a physical device can be
allocated to different VMGWs through data configurations. Therefore, you need to specify the
VMGW to which a TID belongs when you set this TID.
Meanwhile, TIDs are managed by the CMU module. Thus, you also need to specify the CMU
module that manages the TID to be set.
When setting TIDs, pay attention to the following points:
2008-12-02
The E32 board supports up to 1024 physical timeslots. Therefore, the difference between
the start value and end value of TIDs must be less than 1024.
The RS1L board supports up to 2048 physical timeslots. Therefore, the difference
between the start value and end value of TIDs must be less than 2048. You can divide
these timeslots to two 1024-timeslot segments during the configuration.
The S2L board supports up to 4096 physical timeslots, but you can divide these timeslots
to four 1024-timeslot segments during the configuration. The four 1024-timeslot
segments can be inconsecutive, but you need to set the segment with the smallest start
value of TIDs first, and then set another segment with a larger start value of TIDs. For
example, the S2L board has two timeslot segments, 02047 and 30725119. You
cannot set the segment 30725119 before setting the segment 0-2047.
Page 165 of 212
For each TDM interface board (including E32, RT32, and S2L), the start value of TIDs
divided by 1024 must be a positive integer. In addition, regardless of whether the input
timeslot range is fully configured with 1024 timeslots, 1024 timeslots starting from the
start TID are all occupied by the local interface board, and the timeslot ranges of
different interface boards cannot overlap. Assume that the timeslot range of the E32
board is set to 10561057. Then the timeslots ranging from 1024 to 2047 are reserved
for the E32 board. If the timeslots added to other interface boards within the range
10242047, the system displays a message indicating that the input TID belongs to the
range used by another interface board.
The load type of all timeslots on a TDM interface board (including the E32 and S2L
boards) must be consistent.
The trunk type of the timeslots in a trunk (that is, an E1 port) must be consistent. It is not
allowed to set the timeslots ranging from 0 to 12 in a trunk to external timeslots when the
timeslots ranging between 13 and 23 are set to R2 signaling timeslots.

Command
Description
ADD TDMIU
Add the TDM resource of a VMGW.
RMV TDMIU
Delete the TDM resource of a VMGW.
LST TDMIU
Query for the TDM resource of a VMGW.
The following is an example for configuring TDM bearing:

SET
E1PORT:
RXCS=HDB3;
FN=1,
SN=12,
SPN=0,
EPN=31,
FS=DOUBLE_FRAME,
TXCS=HDB3,
ADD TDMIU: BT=E32, BN=0, TIDFV=0, TIDLV=1023, VMGWID=0, HOSTID=0, RT=Extern,

CASNO=0;
Adding the Office Name & Office Number of the Trunk

In the R3B053 version of the MGW, the new commands which are configurating the office
name and configurating the office number are added. These commands are used to describe
the trunk connected to which office.
The below tables show the new commands.
Figure 1.4 MML commands of office name
2008-12-02
Command
Description
ADD OFCNAME
Add the office name
RMV OFCNAME
Delete the office name
LST OFCNAME
Query for the office name
MOD OFCNAME
Modify the office name
Page 166 of 212
Figure 1.5 MML commands of office number

Command
Description
ADD OFCTKC
Add the office number
RMV OFCTKC
Delete the office number
LST OFCTKC
Query for the office number
DSP OFCTKC
Modify the office number
The following is an example for configuring office name and office number:
ADD
ADD
ADD
ADD
OFCTKC: OFC=1, BT=E32, BN=0, PNSV=0, PNEV=15;

OFCTKC: OFC=100, BT=E32, BN=0, PNSV=16, PNEV=31;
OFCNAME: OFCNO=1, OFCINFO="toMSC";
OFCNAME: OFCNO=100, OFCINFO="toVRB";
Configuring IP Bearing Data

Set the IP addresses of specified interfaces on a specific board, including the FE, GE,
Trunking, POS, and ATM interfaces.
When configuring the IP addresses of the interfaces, pay attention to the following points:
Each interface on the OMU, PPU, or SPF board can be configured with a maximum of
one primary IP address and seven secondary IP addresses. The HRU board can be
configured with a maximum of 16 IP addresses. Each VLAN on the GE or FE interface
corresponds to a sub-interface. Each physical interface or sub-interface can be
configured with a maximum of eight IP addresses and one detection IP address.
The system supports the configuration of the primary IP address, secondary IP addresses,
and the detection IP address. You need to set the primary IP address of an interface
before setting the secondary IP addresses and the detection IP address.
For the FE, POS, or ATM interface provided by the MHRU board, one pair of primary
and secondary interfaces shares one interface number and can be configured with only
one IP address. For the GE interface provided by the MHRU board, the interfaces
provided by the primary and secondary MHRU boards are numbered separately and can
be configured with an IP address each.
Setting the IP Address of a Gateway

The IP address of a gateway is set according to the IP address of the Ethernet interface
(regardless of whether the interface functions as a bearing interface or a control interface) on
the HRB board. One IP address can be configured with a maximum of two gateways that
work in active and standby mode. The system uses the gateway that is detected first. The POS
interface does not require a gateway because the POS interface uses the point-to-point PPP
protocol as the link layer protocol, with no need to configure routes for forwarding data
packets.
In the MGW, the HRB board forwards an IP packet according to the source IP address of the
IP packet and the gateway address set by a user. For example, on the E8T board at the back of
the HRB board, if the addresses of the first and second IP interfaces are respectively
10.0.0.1/24 and 192.168.0.1/24, the two gateway addresses set for the two interfaces are
respectively 10.0.0.2/24 and 192.168.0.2/24. Thus, the IP packet whose source address is
2008-12-02
Page 167 of 212
10.0.0.1/24 will be sent to the gateway 10.0.0.2/24, and the IP packet whose source address is
192.168.0.1/24 will be sent to the gateway 192.168.0.2/24.
Configuring Bearing Relations
One bearing address can have bearing relations with up to 14 VPUs. One VPU can be
configured with a maximum of eight bearing relations. When configuring bearing relations,
you need to allocate each bearing address to different VPU boards.
Configuring an M2UA Link Set
When configuring SS7 trunk data, you need to determine whether to use M2UA or M3UA to
forward signaling. If M2UA is used, you need to configure the L2UA link set first.
The L2UA link set contains both the narrowband link and broadband link.
The L2UA link set is a set of SCTP links between the MGW and MGC.
If the S2L is used for circuit access and the peer end has requirements for configurations such as the
SDH subscription and unsubscription bytes and SDH interface performance monitoring, see the
related descriptions in the user manual.
You need to confirm the framing mode of the S2L port with the peer end before configuring TID
data.
Figure 1.1 Procedure for configuring IP bearing data

Step
Description
Command
Add the IP address of an interface.
ADD IPADDR
Modify the IP interface configuration.
MOD IPIF
Add a static route.
ADD ROUTE
Set the IP address of a gateway.
ADD GWADDR
Configure bearing relations.
ADD BEARREL
Add an L2UA link set.
ADD L2UALKS
Generally, do not configure trunk binding for the bearing network interfaces of the E8T
board, but distribute an independent IP address to each bearing network interface for
separate binding.
Except the No.2 interface (the third network interface from top to bottom), other network
interfaces on the E8T board can be normally used.
In the UAP R3B053 version or later version, there is not the command of configuring
bearing relations ADD BEARREL, the command of ADD GWADDR must be used to
add gateway IP address to the bearing IP.
The following is an exampleR3B023:

MASK="255.255.255.0", ISBEAR=YES;
MASK="255.255.255.0", ISBEAR=YES;
2008-12-02
Page 168 of 212

ENPOE=NO;
ENPOE=NO;
ADD ROUTE: BT=HRB, BN=0, DSTIP="0.0.0.0", DSTMASK="0.0.0.0", RTTYPE=NEXTHOP,
NEXTHOP="10.51.5.1";
ADD
ADD
ADD
ADD
ADD
GWADDR: BT=HRB, BN=0, IPADDR="10.51.5.1", MASK="255.255.255.0";

BEARREL: BN=0, IP="10.51.5.18";
BEARREL: BN=0, IP="10.51.5.19";
BEARREL: BN=1, IP="10.51.5.18";
BEARREL: BN=1, IP="10.51.5.19";
The following is an exampleR3B053:

MASK="255.255.255.0", FLAG=MASTER, INVLAN=NO, IFMPLS=NO;
MASK="255.255.255.0", FLAG=MASTER, INVLAN=NO, IFMPLS=NO;
MOD IPIF: IFT=ETH, BT=HRB, BN=0, IFN=1, SPEED=M100, DUPLEX=FULL;
MOD IPIF: IFT=ETH, BT=HRB, BN=0, IFN=3, SPEED=M100, DUPLEX=FULL;
ADD GWADDR: BN=0, IPADDR="10.51.5.18", GWIP="10.51.5.1", TIMEOUT=Aging;
ADD GWADDR: BN=0, IPADDR="10.51.5.19", GWIP="10.51.5.1", TIMEOUT=Aging;
5.3.6 Configuring Clock Data

General Structure of Clock Synchronization
Clock signals are distributed among the frames in the UAP8100 MGW through clock cables.
The clock system consists of the CLK, NET, and interface boards that provide the function of
line clock extraction. See Figure 1.1.
2008-12-02
Page 169 of 212
Figure 1.1 Structure of the clock system
External clock sources supported by the clock system include the 2048 kbit/s and 2048
kHz BITS clocks and the 8 kHz line clock. You can choose an external clock source
according to the actual situation.
The clock system also provides a BITS clock output interface that connects lower
devices and provides BITS clock sources for lower devices.
The clock system extracts the 8 kHz line clock from an external clock source or from the
E32, T32, or S2L interface board of the local device, and provides the 16 kHz clock
signals after the internal clock distribution and clock driving.
The 16 kHz clock signals provided by the CLK board are sent to the NET board of the
main control frame through the backplane bus. Then the clock signals are sent to the
NET boards in other frames through external cables. The NET boards complete the
frequency dividing, frequency doubling, and clock driving before distributing the clock
signals to each service board.
Procedure for Implementing Clock Synchronization

The UAP8100 MGW provides the level-2 or level-3 clock source of high accuracy for lower
devices or other devices on the access network. The clock signals required by the system are
generally extracted and distributed by an independent CLK board or a clock pinch board.
Procedure for Extracting Clock Signals
The UAP8100 MGW supports the 2048 kHz and 2048 kbit/s BITS clocks, as well as the 8
kHz line clock. Clock signals can be obtained in the following two modes:
In one mode, a device receives two-line 8 kHz line clock signals from an interface board and
establishes a connection with the interface board through a clock cable. The interface board
providing the 8 kHz line clock signals can be the E32, T32, S2L, P4L, or P1H board. Each
interface board provides an interface that can be separated by a cable and supply two-line
signals. The two-line signals connect to the active and standby CLK boards respectively.
In the other mode, a device receives one-line 2048 kbit/s or 2048 kHz clock signals from the
BITS clock synchronization system. The type of the input signals can be set through software.
2008-12-02
Page 170 of 212
Procedure for Distributing MGW Clock Signals

The CLK board of the UAP8100 MGW provides the following signals:
18-line 16 kHz line clock signals

These signals are sent to the NET board in the local frame through the backplane bus,
and then connects to the active and standby NET boards in other frames through clock
cables.
One-line 2048 kbit/s or 2048 kHz external synchronization clock signals

These signals are used by the access network or other devices.
For single frame-based or multiframe-based networking, the clock signals from the CLK
board to the NET board in the main control frame do not require external cables, but are
connected through the channel provided by the backplane.
The active CLK board is located in slot 1, and the standby CLK board is located in slot 0.
After receiving the 16 kHz line clock signals sent from a clock cable, the NET board produces
the following three clocks through the internal clock processing module:
32.768 MHz clock: TDM HW synchronization clock for TDM bearing processing
38.88 MHz clock: TDM SDH synchronization clock, including the synchronization
clock that is transferred in SDH mode and required by the ATM and POS services
2 kHz clock: TDM SDH frame clock
Then the NET board drives the three clocks and provides them for the internal service boards
using different bearing modes. For NET boards in cascading mode, the procedure is the same.
Configuring Clock Data

The implementation of the MGW clock has two modes, obtaining the line clock and obtaining
the clock from a BITS clock source. The clock data configuration depends on the on-site
networking. Figure 1.1 describes the procedure for configuring clock data.
Figure 1.1 Procedure for configuring MGW clock data
Step
Description
Command
Modify the clock source configuration information (optional).
MOD CLKSRC
Modify the clock board configuration information (optional).
MOD CLK
Set the line clock source.
SET LINECLK
The line clock source is set only when you choose to obtain the line clock for the MGW.
MOD CLKSRC: BRDTYPE=CLK, GPSPRI=FOURTH, LINE1PRI=FIRST, LINE2PRI=SECOND,
EXTPRI=THIRD, SRCTYPE=EXT2MHZ, FSSM=FORCE, EXTSSM=UNKNOWN, SLOT=SA4;
MOD CLK: BRDTYPE=CLK, MODE=AUTO, GRADE=THREE, TYPE=EXT2MHZ, SRC=NULL, CTRL=NO,
CLKMODE=SOURCE;
SET LINECLK: LINE=LINE1, BT=E32, BN=0, PN=0, SLOT=SA4;

SET LINECLK: LINE=LINE2, BT=E32, BN=1, PN=0, SLOT=SA4;
2008-12-02
Page 171 of 212
In UAP R001 series versions, if the active CLK board of the MGW is located in slot 0 in frame 1,
unknown problems may occur. Therefore, the active CLK board of the MGW must be located in slot 1 in
frame 1.
5.3.7 Configuring Narrowband Call Hold Tone

When the UAP8100 is used in the call center networking, the UAP8100 can play the call hold
tone for subscribers who are holding calls for assistance. This improves user experiences.
Trunk devices can play the call hold tone for narrowband telephone users in the Hold state
only if the call hold tone is loaded to the MGW. You can make the call hold tone by yourself
and then load it to the MGW. Refer to the following:
Sample tone file: P0025S0051A00000000.stf
Document about the loading method of the call hold tone: Tone Producing and Loading
on the MGW
5.3.8 Other Configurations on the MGW

Setting Timeout Intervals for Commands
On the LMT menu bar, choose System > Settings > Time settings > MML command
timeout(20-600), and set the MML command timeout interval to 600 seconds to avoid
timeout messages. Then set the handshake interval to 180 seconds to avoid timeout messages.
If a command is run and no result is returned within the time specified by the MML Command
Timeout Interval parameter because of poor network conditions, the system displays a timeout
message, and the command is stopped. To avoid this problem, you are advised to set the MML
Command Timeout Interval parameter to the largest possible value.
Configuring the Maintenance Network Interface

The MGW is maintained through the OMC network interface. After setting the IP address of
the OMC network interface, you need to add the default routing information to the OMU
board to facilitate MGW maintenance in the maintenance network segment.
If you do not add the routing information, the LMT terminal cannot connect to the OMU
because the OMU board does not have the return route.
ADD IPADDR: BT=OMU, BN=0, IFT=ETH, IFN=0, IPADDR="192.168.116.116",
MASK="255.255.255.0", DSTIP="0.0.0.0";
ADD ROUTE: BT=OMU, BN=0, DSTIP="0.0.0.0", DSTMASK="0.0.0.0", RTTYPE=NEXTHOP,
NEXTHOP="192.168.116.1";
Setting TC Parameters
To improve the conversation quality, you need to modify the values of TC parameters on the
MGW. You can set the receiving gain and sending gain to properly larger values according to
the on-site voice conditions. For example, you can run SET TCPARA: RG=2, TG=2 to
increase the values of the receiving gain and sending gain by 2 dB.
2008-12-02
Page 172 of 212
5.4 Configuring the CTI3.4 Platform

Data configuration for the CTI3.4 platform is almost the same as that for the CTI3.2 platform.
This chapter describes the differences between the configurations of the CTI3.4 platform and
the CTI3.2 platform, and the methods for configuring various voice data in the platform.
5.4.1 Differences in Configuring the CTI3.4 Platform

and the CTI3.2 Platform
Data configuration for the CTI3.4 platform is almost the same as that for the CTI3.0 or
CTI3.2 platform in the following aspects:
When configuring the media server, set CP site to Support, Preoccupied idle CP site
per module to 0, Max. network board site per module to 0, Support to transform the
reason code of to Yes, and Version negotiation support to Yes, set the actual number of
ACD modules used in the office, and provide the correct number of an ACD module. See
Figure 1.1.
Figure 1.1 Configuring the media server
2008-12-02
When configuring the ACD module number on the CTI3.4 platform, add the module number of each
CCU or CSU in the UAP8100.
For the boards in the UAP8100, you need to set the module numbers for CSUs and CCUs on the
CTI3.4 platform. If the system has an external VP or FP, you need to set the module number of CDB
in the CTILINK. You need to configure CSUs, CCUs, and CDBs in the CTILINK. If the system
does not have any VP or FP, you do not need to configure the module number of CDB.
The UAP8100 cannot report the agent IDs through the SPT. The UAP8100 can report the
agent ID through the VP.
Page 173 of 212
Figure 1.2 Configuring agent ID announcement in a queue
The tone file for reporting the agent ID is stored in the note folder of the file server. The tone file
includes the announcement "Dear customer, you'll be served by no. xx agent" and voices 0 to 9.
Choose Centralized Configuration Console > System Configuration > Media Server/CCS >
Report Agent ID by VP. Configure the file names of key voices 0 to 9 for reporting the agent ID
through the VP. See Figure 1.2. Key voice 0 corresponds to the tone file note1 or ent1.
The UAP8100 supports announcement of the SPT voice in the process and announcement of the
agent ID through the SPT. The UAP8100 converts the SPT announcement into the standard voice
announcement by the VP. The file of the standard voice is stored in the standard folder of the file
server.
Set both HostType and UseMenuPlay of the IVR to 2.
In the UNIX operating system, the IVR configuration file is icdpub.ini in icddir/config.
[IVR]
HostType=2
UseMenuPlay=2
In the Windows operating system, the IVR configuration is in the
[HKEY_LOCAL_MACHINE\SOFTWARE\huawei\IVR] registry.
"HostType"=dword:00000002
"UseMenuPlay"=dword:00000002
2008-12-02
Page 174 of 212
For the HostType configuration item, the value 0 refers to the ACD, the value 1 refers to the
AIP or URP, and the value 2 refers to the UAP8100.
If the value of the UseMenuPlay configuration item is 0, it means playing the voice by using
shared files on the VP. This mode is supported by both the AIP and UAP8100. This mode,
however, affects the performance and thus is not recommended. If the value is 1, it means
playing the voice by applying for VP channels. This mode is supported by the AIP, not by the
UAP8100. This is the default value. This mode is compatible with the AIP of earlier versions.
If the value is 2, it means playing the menu voice through the combination of voice playing
messages and digit collecting messages. This mode is supported by the AIP of
V610R003.5Da04 or a later version, the UAP, and the URP. For a UAP, a URP, or an AIP of
V610R003.5Da04 or a later version, this mode is recommended.
The incoming call prompt for agent is configured in the queue parameters. In the case of an
incoming call, the UAP8100 plays this prompt tone to the agent. The default announcement
duration for the prompt is 200 ms. To ensure that the prompt is heard by the agent, you need
to set this duration to 400 ms and modify the length of the tone file to support 400 ms or
longer voice playing.
On the UAP8100, if you set the speech mode at the subscriber side to the speak-only mode,
the subscriber cannot hear the prompt for mute operations.
5.4.2 Changing the Setting Mode of the User Class

Log in to the configuration console by using a VDN agent ID. Set Set by at the lower-right
corner on the User Class page to Service. This setting determines the call success rate of the
platform.
Figure 1.1 Configuring the setting mode of the user class in the VDN
Two setting modes of the user class are available: platform and service. By default, the
platform setting mode is used.
For the platform, the handling method varies from one setting mode of the user class to the
other. After an incoming call accesses the platform, the CCS obtains the setting mode of the
user class by reading the configuration file. If the service setting mode is used, the platform
judges the user class in the service database by invoking the stored procedure without any
handling. If the platform setting mode is used, the platform judges the user class in the
tSpecialCustomer UIDB table by invoking the spCustomerSel stored procedure through the
platform data source. In this case, the platform is under heavy pressure. If the data source is
incorrect, or the UIDB does not contain any stored procedure or table, a fault occurs during
query. Thus, the CCS times out when returning a routing result. As a result, the call is
disconnected.
To judge the user class at the platform, set Set by to Platform. To judge the user class in the
service database by invoking the stored procedure, set Set by to Service. If you do not need to
judge the user class of an incoming call, set Set by to Service to save platform resources.
2008-12-02
Page 175 of 212
5.4.3 Configuring and Loading a Tone File

You need to set four types of voice when configuring the platform: prompt tone, two-stage
dialing voice, SPT voice, and SIG voice. The IPCC solution differs from the previous solution
for the customer service system in that the IPCC solution uses the UAP8100 as the device for
access and announcement. The UAP8100 does not contain any SPT or SIG. Thus, the
announcement modes of the SPT voice and SIG voice are different from those in the previous
solution for the customer service system.
The four types of voice are described as follows:
Prompt Tone
The prompt tone can be played by the VP. The configuration of the prompt tone is the same as
that in the previous solution for the customer service system.
Create a note folder in the root directory of the file server. Place the tone files in this folder.
Name a tone file in the note+number or ent+number format. You can change the format of
the file name by running MOD NOTEPRM on the UAP8100 MGC. VP announcement
configuration of the platform and the prompt tone in the process can be read from the tone
files in the note folder.
Two-Stage Dialing Voice

The two-stage dialing voice is classified into SPT announcement and VP announcement. You
need to configure VP announcement in the IPCC. The two-stage dialing voice announced by
the VP belongs to the prompt tone. The naming mode and storage path of a two-stage dialing
tone file are the same as those of a prompt tone file. Choose Centralized Configuration
Console > System Configuration > CCS/Media Server > CTI Server Dial Voice to
configure the mapping between keys and names of a two-stage dialing tone file. See Figure
1.1.
Figure 1.1 Configuring the two-stage dialing voice
For the list of two-stage dialing tone files, see attachment 6 VP Two-Stage Dialing Voice.
2008-12-02
Page 176 of 212
SPT Voice
In the IPCC system, the platform does not allow the SPT to announce the agent ID in the
queue. You need to set the agent ID announcement to the VP prompt tone. The UAP8100
supports the SPT announcement in the GSL process.
In the UAP8100, the SPT voice is called standard voice. You need to store the tone file in the
standard folder on the shared disk. This folder is at the same level as the note folder. You
need to load the standard tone file to the memory on the VRB. You cannot update the tone file
by placing it in the update folder. During startup, the VRB loads the tone file. You can also
run UPD STD to load the tone file.
For the list of standard tone files, see attachment 7 Standard.
SIG Voice
In the IPCC system, the UAP8100 automatically converts the SIG voice into the TONE voice
for announcement. You must store the SIG tone file in the TONE folder on the shared disk.
This folder is at the same level as the note folder. You need to load the SIG tone file to the
memory on the VRB. You cannot update the tone file by placing it in the update folder.
During startup, the VRB loads the tone file. You can also run UPD STD to load the TONE
tone file.
The SIG voice is not provided during deployment. You need to make the SIG voice on site.
The format of the voice is 8 kHz or 6 kHz vox. The tone file is named in the following format:
eight-bit hexadecimal number.vox. For example, 0000001e.vox.
For how to make the SIG voice in the IPCC project of Guangxi subsidiary of China Telecom,
see attachment 8 Tone.
5.4.4 Configuring Mute Operation and Incoming Call

Prompt for the Agent
Mute Operation
In the IPCC environment, the mute function of the agent is not complete. It is recommended
that you use the hold function.
The mute function has the following three features:
The subscriber cannot hear the agent.
The agent can hear the subscriber.
The system plays the waiting tone to the subscriber.The IPCC system cannot provide the
third feature at present.
Incoming Call Prompt for the Agent

This voice is configured in the queue parameters. Normally, the voice features beep. This
voice is used to notify an agent of an incoming call. This voice is played to the agent through
2008-12-02
Page 177 of 212
the conference site channel. The UAP8100 of the B023 and patch release support
announcement of a specified tone file in the conference site channel only. Therefore, you need
to set the announcement mode to announcement of a specified tone file, as shown in Figure
1.1. If you set another mode, announcement fails.
Figure 1.1 Configuring the incoming call prompt for an agent
The restrictions on announcement in the conference site channel of the UAP8100 R3 are as follows:
The UAP8100 of B023 and related patch releases provide narrowband resources only and supports
announcement of a specified tone file on the conference site.
The UAP8100 of B03X and related patch releases provide broadband resources only and supports
announcement by the SIG or SPT on the conference site. The UAP8100, however, supports
announcement of a specific tone file only for the background voice.
The UAP8100 of B05X or a later version provide both narrowband and broadband resources and support
announcement by the SIG or SPT on the conference site. The UAP8100, however, supports
announcement of a specific tone file only for the background voice.
5.5 Configuring Network Device Data

5.5.1 Configuring LAN Switch Data
Normally, a Quidway S5624 switch is installed in the UAP8100. For the configuration script
of the switch, see the TopEng IPCC Configuration Template V1.1 and 3116A04Y-Quidway
S5600 Series LAN Switch Operation Guide-Release 1510(V1.01).
Find the preceding documents by visiting http://support.huawei.com and choosing:
Call Center and CRM > Technical Guide > Deployment Guide
Documentation > Data Communication Product Line > Product > Ethernet Lanswitch >
Low-End Lanswitch > Product Manual
In the standard networking of the IPCC that provides the broadband access, the S5624 switch
is not connected to any switches. In this case, you cannot directly log in to the S5624 switch
by using a maintenance terminal in the maintenance network segment. You can solve this
problem by using the following method:
Configure the IP address of a VLAN on the S5624 switch. This VLAN contains the network
interfaces that the S5624 switch uses to connect the BAM, file server, and CTILINK. Enable
the Telnet protocol. You can access the BAM, file server, and CTILINK in the maintenance
network segment. Therefore, you can log in to any of these devices and then access the S5624
switch by using Telnet to maintain the S5624 switch.
2008-12-02
Page 178 of 212
5.5.2 Configuring SBC Data

Step 1 Clarify the networking requirements before configuring the SBC. The requirements include
the networking purpose, role of the SBC in the network, and subnet division.
Step 2 Draw a clear and complete networking diagram based on the preceding elements.
Step 3 Configure the working parameters for interfaces and components of the SBC.
Step 4 Configure the IP address of each interface on the SBC according to the subnet division.
Step 5 Set the routing.
Step 6 Configure a signaling proxy if required.
Step 7 Configure other settings if required.
Step 8 Enable the single-domain mode of the SBC if the foreground of the SBC does not pass
through an NAT device, such as a firewall, for address translation.
For details on configuration of each protocol or function of the SBC, see the Quidway
Eudemon 2300 Session Border Controller Operation Guide by visiting
http://support.huawei.com and choosing:
Documentation > Core Network > Fixed Core Network NGN > SessionEngine SBC >
Product Manual
For a sample SBC configuration, see the next section or attachment 9 SBC Configuration
Instanc.
If the foreground of the SBC needs to pass through an NAT device for address translation, you can use a
Eudemon200/500 firewall. The Eudemon100 firewall is not recommended because this firewall has
bugs. If you use a Eudemon100 firewall, after an SIP call passes through the NAT device, the signaling
is normal, but neither of the two parties can hear the other party.
----End
Sample Configuration
The SBC can work in either of the following modes:
Single-domain mode
For interconnection between the UAP8100 and the SBC during bearer networking, the
SBC must work in single-domain mode. Use the single-domain mode when the SBC is
not connected to an NAT device in the internal network.
Multi-domain mode
If the single-domain mode cannot meet the requirements for networking, you must use
the multi-domain mode of the SBC.
In multi-domain mode, the SBC is connected to an NAT device in the internal network,
or connected to NAT and IAD devices at the same time. The multi-domain mode applies
to enterprise users who require address translation. In multi-domain mode, the SBC
needs to be connected to an NAT device and an egress router. At this time, the SBC
regularly sends UDP packets to the NAT device to update the NAT table, thus keeping
the address translation relations valid.
2008-12-02
Page 179 of 212
Physical structure
SE2200
The front panel contains three slots. The top slot, that is, slot 0, is used for the RPU. The
other two slots, that is, slots 1 and 2 counting from left, are used for service interface
cards.
When an SE2200 is used, only two FE interfaces on the RPU are used for service
processing due to restrictions on the capacity and performance. The performance of an
interface on an additional FE interface board is lower than that on the RPU. Therefore,
additional FE interface boards are not recommended. Considering the performance and
capacity, you need to use the FE interfaces for both signaling and media when the SBC
works as the signaling proxy or interworking gateway. That is, one FE interface on the
RPU is used for the trusted domain where the UAP8100 is located, and the other FE
interface is used for the untrusted domain.
SE2300
The front panel contains five slots. The top slot, that is, slot 0, is used for the RPU. The
other four slots, that is, slots 1 to 4 counting from left, are used for service interface
cards.
The SE2300 provides a larger capacity and better performance than the SE2200. In
addition, the SE2300 can provide up to three GE interfaces. When the SE2300 provides
three GE interfaces, the SE2300 does not provide any FE interfaces. In actual
applications, it is recommended that you use the SE2300 to provide two GE interfaces
and eight FE interfaces. You can use the two GE interfaces for media transmission and
the FE interfaces for signaling transmission.
Data configuration
The service interfaces on the SBC use the three-dimension numbering method. The principles
are as follows:
The format of an interface number is interface-type X/0/Z.
In the preceding format, interface-type refers to the interface type. The SE2200 supports
FE interfaces only. The SE2300 supports both FE and GE interfaces. X refers to the slot
number. Z refers to the serial number of the interface.
For the slot number, see the preceding description. The slot numbers of different
interfaces on the same interface module are the same. The serial number of each
interface type starts from 0. An interface is numbered according to the serial number on
the interface module.
You can configure the SBC in either of the following ways:
Connect the serial port on a PC or terminal to the console interface on the SBC through
the console interface cable.
If the SBC was powered on before, log in to the SBC by using Telnet through the LAN
or WAN when there are reachable routes between the configuration terminal and the
SBC.
After you configure a group of settings and enable the expected functions, save the current
configuration file to a storage device. Run the save command to save the current
configuration to the storage device. If the system supports a file system, you can save the file
using the current startup configuration filename. The following is an example:
<Quidway> save
The current configuration will be written to the device.
Are you sure?[Y/N]y
2008-12-02
Page 180 of 212
%Send save command to system successfully.

%Warning,Don't reset system until finish synchronizing device.
%Save the configuration ... Successfully.
At present, during the networking of a UAP8100, the proxy configuration or interworking

gateway configuration of an SBC is involved. The proxy configuration corresponds to the
proxy mapping group in the SBC. The interworking gateway configuration corresponds to the
interworking gateway mapping group in the SBC. You cannot directly delete or change the
configuration of a mapping group. To delete or change the configuration of a mapping group,
you need to disable the mapping group. The examples are as follows:
When the SBC works as the signaling proxy and media proxy, you need to create a proxy
mapping group in the SBC. The purpose of creating a proxy mapping group is to bind
the mapping of signaling addresses and the mapping of media stream addresses. The
proxy mapping group must contain the following IP addresses:
Client IP address in signaling mapping
Server IP address in signaling mapping
IP address of the softswitch or IADMS network management station in signaling

mapping
Client IP address in media mapping
Server IP address in media mapping
For instance, in IPCC applications of an operator, you need to separate the NGN bearer
network where the UAP8100 is located from the IP agent subnet by using the SBC. The
configuration script for proxy mapping in the SBC is as follows:
# Set the IP address of each interface on the SE2300.
<Quidway> system-view
[Quidway] interface ethernet2/0/0
[Quidway-Ethernet2/0/0] ip address 100.10.230.2 255.255.0.0
[Quidway-Ethernet2/0/0] quit
[Quidway] interface ethernet1/0/0
# Enable HRP two-node cluster hot backup.

[Quidway] hrp enable
# Enable automatic backup of configuration commands, connection state, and user

registration information.
[Quidway] hrp auto-sync
# In the HRP environment, when the primary unit becomes the secondary unit, use this
command to delete all the call information, registration information, and session table
entries on this unit and synchronize the related information from the new primary unit.
[Quidway] hrp delete-all
# Enable call information backup.

[Quidway] hrp enable sbcall
# Enable SIP signaling proxy.

[Quidway] sbc sip enable
# Configure the proxy mapping group in the SE2300.

[Quidway] sbc mapgroup proxy 1
# Configure the IP addresses of the SE2300 in signaling mapping.

[Quidway-proxy-1] clientaddr 100.10.230.2
2008-12-02
Page 181 of 212
[Quidway-proxy-1] serveraddr 100.40.240.1

[Quidway-proxy-1] softxaddr 100.100.20.10
# Configure the IP addresses of the SE2300 in media stream mapping.

The IP address used by mapping of media stream addresses can be the same as or different from that
used by mapping of signaling addresses. For the SE2300, it is recommended that the IP addresses be
different. It is recommended that different interfaces be used for transmission of the signaling and media
streams.
[Quidway-proxy-1] media-clientaddr 100.10.230.2
[Quidway-proxy-1] media-serveraddr 100.40.240.1
# Enable the proxy mapping group.

[Quidway-proxy-1] enable
# Configure the well-known SIP port numbers of the SE2300 and the UAP8100. The
following configuration script describes the well-known port number automatically
generated after the signaling mapping is configured.
After the signaling mapping group is configured, the SE2300 automatically generates the default values
of well-known port numbers of the client and the UAP8100. Check whether the well-known port
number of each protocol is the same as the well-known port number provided by the UAP8100. If yes,
you can use the default configuration. Otherwise, you need to set the well-known port number of each
protocol to the same as that provided by the UAP8100.
[Quidway-A] sbc wellknownport clientaddr 100.10.230.2 sip 5060
[Quidway-A] sbc wellknownport softxaddr 100.100.20.10 sip 5060
# Configure the dynamic port range of the SE2300.

[Quidway-A] sbc portrange signal begin 10001 end 29999
[Quidway-A] sbc portrange media begin 30000 end 49999
# Configure the static route to UAP8100.

[Quidway-A] ip route-static 100.100.20.10 16 100.40.240.2
When the SBC works as an interworking gateway, it uses the IP route for interworking.
In the case of the IP route interworking gateway, the mapping group must contain the
client IP address, server IP address, and softswitch IP address in signaling mapping.
For instance, in IPCC applications of an enterprise intranet, you need to interwork the
NGN bearer network where the UAP8100 is located with that of the softswitch of China
Telecom and that of China Netcom by using an SE2200. You also need to separate these
networks by using the same SE2200. The IP address of the UAP8100 is 10.10.10.22. The
IP address of the softswitch of China Telecom is 10.10.20.128. The IP address of the
softswitch of China Netcom is 100.100.1.10. The configuration script for interworking
gateway mapping in the SBC is as follows:
# Enable the SIP interworking gateway.
[Quidway] sbc sip enable
# Set the IP address of each interface on the SE2200.

[Quidway] interface Ethernet0/0/0
# Add the IP address for interconnection between the SE2200 and the softswitch of
China Telecom (the signaling and the media streams share the IP address).
# Add the IP address for interconnection between the SE2200 and the softswitch of
China Netcom (both the signaling and the media streams share the IP address).
[Quidway-Ethernet0/0/0] ip address 100.100.1.1 255.255.255.0 sub
2008-12-02
Page 182 of 212
# Add the IP address for interconnection between the SE2200 and the UAP8100.
[Quidway] interface Ethernet0/0/1
# Configure the IP address for transmission of media streams between the SE2200 and
the UAP8100.
# Map the IP address of the softswitch of China Telecom to an IP address in the network
where the UAP8100 is located.
# Map the IP address of the softswitch of China Netcom to an IP address in the network
where the UAP8100 is located.
# Map the IP address of the SIP well-known port on the SE2200 to an IP address in the
NGN bearer network of China Telecom.
[Quidway] sbc wellknownport clientaddr 10.10.20.129 sip 5060
# Map the IP address of the SIP well-known port on the SE2200 to an IP address in the
NGN bearer network of China Netcom.
# Configure the SIP well-known port on the SE2200. Map the IP address of the
softswitch of China Telecom to an IP address in the NGN bearer network where the
UAP8100 is located.
# Configure the SIP well-known port on the SE2200. Map the IP address of the
softswitch of China Telecom to an IP address in the NGN bearer network where the
UAP8100 is located.
# Configure the SIP well-known port on the softswitch of China Telecom.

[Quidway] sbc wellknownport softxaddr 10.10.20.128 sip 5060
# Configure the SIP well-known port on the softswitch of China Netcom.

# Configure the SIP well-known port on the UAP8100.

# Configure the dynamic port range.

[Quidway] sbc portrange signal begin 10001 end 29999
[Quidway] sbc portrange media begin 30000 end 49999
# Enable the function of interworking gateway in IP routing mode.

[Quidway] sbc intercom ip-route enable
# Configure the IP route from the NGN bearer network where the UAP8100 is located to
the NGN bearer network of China Telecom.
[Quidway] sbc mapgroup intercom-ip 1001
[Quidway-intercom-ip-1001] clientaddr 10.10.10.20
[Quidway-intercom-ip-1001] serveraddr 10.10.20.129
[Quidway-intercom-ip-1001] softxaddr 10.10.20.128
[Quidway-intercom-ip-1001] media-clientaddr 10.10.10.19
[Quidway-intercom-ip-1001] media-serveraddr 10.10.20.129
[Quidway-intercom-ip-1001] enable
2008-12-02
Page 183 of 212
[Quidway-intercom-ip-1001] quit
# Configure the IP route from the NGN bearer network of China Telecom to the NGN
bearer network where the UAP8100 is located.
# Configure the IP route from the NGN bearer network where the UAP8100 is located to
the NGN bearer network of China Netcom.
# Configure the IP route from the NGN bearer network of China Netcom to the NGN
bearer network where the UAP8100 is located.
Two configurations about safety function, please make the function of sending ICMP
unreachable control messages disable.
# Drop the UDP messages which are not needed by the SBC.
[Quidway] sbc invalid-packet drop enable
# Disable the NAT processing the ICMP protocol.

[Quidway] undo nat alg enable icmp
SBC Side Connection

The SBC supports both direct connection and side connection modes in a data network.
Figure 1.1 shows the networking diagram in the case of SBC side connection. In side
connection mode, an SBC is connected to the switch or router through two network cables.
The IP addresses of two network interfaces must be in different network segments. One IP
address is in the same network segment as the SIP signaling IP address and the bearer IP
address of the UAP8100. The other IP address is in the same network segment as the IP
address of the agent. In the case of two-node SBC cluster, the switch or router connected with
the SBCs must support layer 2 forwarding and forward VRRP packets sent by the SBCs.
2008-12-02
Page 184 of 212
Figure 1.1 Networking in the case of SBC side connection
5.6 Configuring External VP/FP Data

5.6.1 Overview
For how to configure the data of an external VP or FP, see the following documents:
C&C08-AIP Resource Component FP User Manual - (V610R003_03)
C&C08-AIP Resource Component VP User Manual - (V610R003_10)
C&C08-AIP Resource Component TTS User Manual - (V610R003_04)
C&C08-AIP Resource Component ASR User Manual
Find the preceding documents by visiting http://support.huawei.com and choosing:

> AIP&ACD > Product Manual
5.6.2 Precautions
Precautions in Configuring VP Data
When configuring the VP data, you can specify whether the VP is connected to an AIP or
UAP by configuring the fields in VP.ini. The following table lists the basic formats and
meaning of the fields in VP.ini.
2008-12-02
Page 185 of 212
Field
Configuratio
n Item
Value
Rang
e
Defaul
t Value
Description and
Configuration Method
VP
GROUP
VP group number.
Generally, VPs can be classified
based on the connected host module
numbers. Two VPs that are
connected to the same module have
the same VP group number. This
item is meaningless now.
WORKSTATION
1254
VP workstation number.
The workstation number of a VP
starts from 1. Each VP has a unique
workstation number.
When the VP is connected to a
UAP8100, the workstation number
of the VP must be consistent with the
resource workstation data in the
UAP8100 configured through ADD
RCWSCFG.
WORKSTATION
2
VP workstation number 2.
For a VP with more than 120
channels, you should assign another
workstation number for every 120
additional channels. The workstation
number must be unique in the
network segment.
When the VP is connected to a
of the VP must be consistent with the
resource workstation data in the
RCWSCFG.
GROUPNO = 0
Resource group number reported by

the logged-in CDB when the VP is
connected to a UAP8100.
The value needs to be the same as
that in the UAP8100 configured
through ADD RCG.
MGWNO
2008-12-02
Number of the MGW connected to

the VP when the VP is connected to a
UAP8100.
Page 186 of 212
Field
Configuratio
n Item
Value
Rang
e
Defaul
t Value
Description and
ACD
MODULE
132
Module number of the logged-in AIP

host or the CDB in the logged-in
UAP8100.
The value of this parameter is set to
the module number of the CDB
when the VP is connected to a
UAP8100.
PROCESS
73, 112
73
The value 73 means that the VP is

connected to an AIP.
The value 112 means that the VP is
Precautions in Configuring FP Data

When configuring the FP data, you can specify whether the FP is connected to an AIP or UAP
by configuring the fields in FP.ini. The following table lists the basic formats and meaning of
the fields in FP.ini.
Field
Statement
Value
Range
Defau
lt
Value
Description and
[Station]
MID
132
Module number of the logged-in

ACD.
System
configura
tion
The value of this parameter is set to

the module number of the CDB
when the FP is connected to a
UAP8100.
PID_FAX = 74
64, 74, 85,

112
74
Process ID of the FP in the ACD.

Set the value to 112 when the FP is
You cannot change the value of this
parameter at will. An incorrect
change to the value may prevent the
FP from logging in to the host.
2008-12-02
Page 187 of 212
Field
Statement
Value
Range
Defau
lt
Value
Description and
NodeNumber =
1
1254
FP workstation number.
A workstation number identifies an
FP. Each workstation can have up
to 60 fax channels. Each FP
supports up to 1 workstation, that
is, 60 fax channels.
When the FP is connected to a
of the FP must be consistent with
the resource workstation data in the
RCWSCFG.
CardCount = 1
1, 2
Number of sound cards.
GroupNo
FP group number.
This number is the resource group
number reported by the logged-in
CDB when the FP is connected to a
UAP8100.
The value needs to be the same as
that in the UAP configured through
ADD RCG.
MgwIdx
MGW number of the UAP8100 that

the FP is connected to.
5.6.3 Configuring the Data on External VP/FP

Connected to a UAP8100
Procedure
Figure 1.1 lists the steps for configuring the external VP or FP resource data.
Figure 1.1 Configuration procedure
2008-12-02
Step
Description
Command
Add the number of the resource group.
ADD RCG
Add the information about the resource

workstation.
ADD RCWSCFG
Add the MEM configuration of the CDB.
ADD MEMCFG
Page 188 of 212
Configuring the Information about a Resource Workstation

You must finish configuring the information about the resource group and resource trunk
before configuring the resource workstation information.
For the data configuration of this command, see section 5.2.11"Configuring Resource Data."
For an external VP or FP, set the workstation to external. You do not need to set the module
number.
Configuring the MEM Data of a CDB

Since the CDB communicates with the FEP, the communication protocol must be FEP. The
principles for configuring the MEM on the CDB must be the same as those on the CSU or
CCU.
If no external VP or FP is connected, you do not need to configure the MEM data for the CDB.
5.7 Configuring Echo Cancellation

In a call between a subscriber and an agent in the IPCC system, if the subscriber or agent
hears apparent echo, you can eliminate the echo by enabling echo cancellation (EC) in the
IPCC system.
5.7.1 EC-Related Settings on the UAP8100 MGW

The VPU in the MGW must be configured with an EC pinch board.
Run ADD MGW in the UAP8100 MGC to enable EC. The following is an example:
LA="192.168.0.200", RA1="192.168.0.201", RP=2944, HAIRPIN=S, EC=TRUE, CODETYPE=ASN,
UCATT=NOEC-0;
You can use the default values of EC-related parameters in the MGW. Change the values only
when required. Run SET ECPARA to change the values.
5.7.2 EC-Related Settings on the UAP8100 MGC

If the VRB in the UAP8100 MGC is set to a CP workstation, you need to enable EC on this
VRB by running SET EC. After the EC function is enabled, the VRB can provide 120 voice
channels only. That is, only the front four E1 cables are available. The four E1 cables
connected to the ERI are unavailable. The following is an example of enabling EC:
5.7.3 EC-Related Settings on the No.7 Trunk Group

You need to enable EC for all the EC-related settings. That is, set ECCAP to FORCEEC,
and ECHAIR to YES. The following is an example:
ADD N7TG: TG=1, EID="192.168.0.200:2944", G=INOUT, SRC=1, TGN="to_AIP_TG",
ECCAP=FORCEEC, ECHAIR=YES;
2008-12-02
Page 189 of 212
5.7.4 EC-Related Settings on the OpenEye Terminal

The OpenEye terminal supports EC. Choose Options > System Settings > Audio on the
OpenEye login interface, as shown in the following figure. In addition, select Noisy in Scene
Settings to effectively shield background noise during a call.
Figure 1.1 Audio settings on an OpenEye terminal
5.7.5 Precautions in Enabling EC
2008-12-02
Enable EC in the NGN or PSTN regardless of whether the IPCC system provides the
access of broadband or narrowband services; otherwise, the agent hears apparent echo.
Enable EC on each broadband terminal, that is, OpenEye terminal, in the IPCC system.
Enable EC at the access point of narrowband services and conversion point for
narrowband and broadband services in the IPCC system. If the IPCC provides the
narrowband access and IP agents, you need to enable EC on the VPU.
Page 190 of 212
Self-Check and Test
6.1 Checking the Hardware and Software of

the UAP8100
6.1.1 Checking the Hardware of the UAP8100
The standards for the check items are as follows:
Cabinets are steady after being installed.
All cable apertures of the cabinets are sealed using tidy, insulated, and fire-resistant
materials. The seams of the cable apertures are not wider than 1.8 cm.
Boards can be easily inserted and removed.
Blank panels are all installed.
Fibers, trunk cables, and network cables are deployed according to the engineering
drawing.
Cables are away from direct hot air.
Power cables and earth wires are whole segments of copper core materials without
connectors between two ends.
The labels of all cables conform to standards and are correctly pasted.
Power cables and earth wires are correctly and reliably connected.
The PGND grounding bar of the power distribution cabinet or power distribution box is
properly connected to that provided by the customer.
The PGNDs of cabinets are connected to those of communications hosts through shortcircuiting cables.
6.1.2 Checking the Software Versions of the

UAP8100
The version of the UAP8100 software used on site might be different from that used for
illustration in this section. But the contents to be checked and the check methods are the same.
For details, see the related description in the release documents.
2008-12-02
Page 191 of 212
Checking the MGC Software Version

Run the MML command DSP INVER to check whether the software versions in the
foreground and background are the same as the version described in the VDD. For example,
for the UAP8100 V300R003C01B020, the following information is displayed when DSP
INVER is run after software installation:
%%dsp inver:CONFIRM=Y;%%
RETCODE = 0 Operation succeeded
Version of every module
----------------------ModuleNo
BAM
Module
Module
Module
Module
Module
Module
Module
Module
Module
Module
Module
(Result number = 12)
2
3
27
35
36
71
72
73
74
75
252
Module state
Version information
<NULL>
Active
Active
Active
Active
Active
Active
Active
Active
Active
Active
Active
UAP8100
UAP8100
UAP8100
UAP8100
UAP8100
UAP8100
UAP8100
UAP8100
UAP8100
UAP8100
UAP8100
UAP8100
MGC V300R003C01B020 2007-05-14

V300R003C01B020
V300R003C01B020
V300R003C01B020
V300R003C01B020
V300R003C01B020
V300R003C01B020
V300R003C01B020
V300R003C01B020
V300R003C01B020
V300R003C01B020
V300R003C01B020
Run DSP BVER to check the version of level 2 BIOS of each board. The correct version is
EBTM USP001. Assume that the following information is displayed after the version of the
level 2 BIOS of the CSU board in frame 0 and slot 5 is checked:
%%DSP BVER: FN=0, SN=5,CONFIRM=Y;%%
RETCODE = 0 Operation succeeded
CSU Board Version Information
-----------------------------
PCB Version = CSU VER 4

BIOS Level1 Version = SF3USPI4 101
BIOS Level2 Version = EBTM USP001
Software Version = UAP8100 V300R003C01B020
Logic Version = (U62) 0003
---
END
As shown in the displayed information, the version of the level 2 BIOS is incorrect. In this
case, run CLR BIOSL2 to clear the level 2 BIOS. Then reset the board and re-load the level 2
BIOS.
Re-loading MGC Data and Verifying the Version and Data

After all data of the MGC is configured, run FMT to format the data. Then restart all frames
to ensure that the version and data at the foreground and those at the background are
consistent.
After all frames are restarted, run STR CRC to check the data consistency between the
foreground and background of each module. Make sure that the versions and data are
correctly loaded.
2008-12-02
Page 192 of 212
Checking the MGW Software Version

Run LST VER to check the MGW software version. Currently, the version of the UAP8100
MGW software is V100R003C03B161SP02. As a result, the correct information to be
displayed after LST VER is run should be as follows:
%%LST VER:;%%
RETCODE = 0 accomplished
Result of current software query
--------------------------------
Current software version = V100R003C03B161SP02

Current software status = Normal
---
END
Verifying the MGW Version

After MGW boards are loaded, run CHK FILE and CHK VERSION to check the versions
that are loaded in each boards and the MGW version data that are stored in the OMU hard
disk.
After all data is configured, run SAVE CFG to save the configuration. Then run DSP CFG:
FP=DC; to check the consistency between the configurations stored in the memory and those
in the hard disk.
6.1.3 Checking Configurations

Check the following:
Whether the configured board type is the same as the actual one and whether the board
state is Normal
Whether the configurations of the system parameters and the system time are correct and
as planned
Whether the actual configurations and planned configurations of interfaces are the same
Whether the configurations of E1 interfaces and the time slot that the clock abstracts are
correct
Whether the number and configurations of signaling links meet service requirements and
are as planned
Whether redundant data exists
Whether basic announcements are correct
6.1.4 Checking the Running of Devices

Check the following:
2008-12-02
Whether boards can be powered on and whether they can work properly
Whether the local maintenance terminal (LMT) system can work properly and whether
system maintenance operations can be performed
Whether the following version matching is correct:
Between the host MGC and standby MGC
Between the host MGW and the LMT
Between the UAP8100 and the CTI platform
Between the UAP8100 and the voice peripheral (VP)
Page 193 of 212
Between the UAP8100 and the fax peripheral (FP)
Whether the settings of the DIP switches for frames and boards are correct
Whether the settings of the backup and loading DIP switches are correct
Whether the network interfaces work in full duplex mode or auto-negotiation mode
Whether services work properly
Whether the call put-through rate and the announcements that are played are normal, by
making test calls
Whether one of the core servers of the CTI platform is in the Active state and the other
one is in the Standby state
Whether the connections between the IVR, MCP, and APLOGIC are normal
6.1.5 Checking Trunks

Cross wires might cause problems such as one-way audio, no audio, crosstalk, and digitcollection exceptions. To avoid these problems, check the internal and external trunks of the
UAP8100. For the method and procedure of checking trunks, see the URP8100 V300R001
Trunk Check Operation Guide.
> UAP&URP > Technical Guide
6.1.6 Checking the UAP8100 Using the Automatic

Inspection Tool
The UAP8100 MGC can be checked by the automatic inspection tool that is shipped with the
UAP8100V300R003C01B023 in the Tools\Breeze iCheck directory. You can also download
the automatic inspection tool at http://support.huawei.com.
Software > Version Software > Application and Software Product Line > Service and
Software Public > UAP&URP > UAP8100 > UAP8100 V300R003 >
UAP8100V300R003C01B023
The UAP8100 MGW can be checked by the MGW health check tool and the MGW
information collection tool. The MGW health check tool and the MGW information collection
tool are in the installation directory of the automatic inspection tool CSP-ISE iCheck C03B44.
By default, the path to the Chinese version of CSP-ISE iCheck C03B44 is C:\Program
Files\CSP-ISE iCheck C03B443\iCHECK_URP8100MGW V300R001_CH.rar\bin. The
executable file of the MGW health check tool is HealthCheck.exe and that of the MGW
information collection tool is InfoCollector.exe. The operation guide for the MGW health
check tool is the iCHECK_UAP8100V300R003C01B001 MGW Information Collector User
Guide. The operation guide for the information collection tool is the
iCHECK_UAP8100V300R001C001B001 MGW Health Check Tool User Guide.
The path to the CSP-ISE iCheck C03B443 at http://support.huawei.com is as follows:
Software > Mini-tool software > Application and Software Product Line > Operation
Support System > ICD
The path to the operation guides for the MGW health inspection tool and the MGW
information collection tool at http://support.huawei.com is as follows:
2008-12-02
Page 194 of 212
> UAP&URP > Version Release Document
6.1.7 Checking the File Server Using the Automatic

Inspection Tool
The file server can be checked by the FS automatic check script FileServer_Check.sh. The
script is in the installation directory of the automatic inspection tool CSP-ISE iCheck
C03B443. The default path to the script is C:\Program Files\CSP-ISE iCheck C03B443. For
the operation guide of the FileServer_Check.sh script, see the iCHECK_FS
V100R001C01B003 Configuration Guide.
The path to the automatic check script of the file server at http://support.huawei.com is as
follows:
> File Server
6.2 Checking External Resources

6.2.1 Checking the Versions of the External VP and
FP
Check whether the versions of the external VP and FP are the same as those specified in the
related description in the release documents.
According to the UAP8100V300R003C01B053 Compatibility Requirement Table, the
matching version of the external VP is V610R003.5Da19 and that of the external FP is
V610R003.5Da17.
6.2.2 Checking the VP and FP Using the Automatic

Inspection Tool
The VP and FP can be checked by the automatic inspection tool CSP-ISE iCheck C03B443.
6.3 Checking the CTI Platform

6.3.1 Checking the Version of the CTI Platform
Currently, the version of the CTI platform that supports the IPCC system is
ICDV300R004C01B014. You need to check whether the versions of the platform components
2008-12-02
Page 195 of 212
such as CCS, CTISERVER, CTILINK, IVR, Aplogic, and MCP are the same as those
specified in the release notes of the ICDV300R004C01B014.
6.3.2 Checking the CTI Platform Using the Automatic

Inspection Tool
The CTI platform can be checked by the automatic inspection tool CSP-ISE iCheck
C03B443. Currently, the CSP-ISE iCheck C03B443 does not integrate the round inspection
package of the CTI3.4. Instead, the round inspection package of the CTI3.2 can be used to
check the CTI platform.
6.4 Testing the Service Scenarios of the IPCC

System
The IPCC system has multiple types of service scenarios, such as outgoing calls, three-party
conversations, and call transfer. Because of the flexibility of SIP messages, in different service
scenarios, the interaction messages between the UAP8100 and the softswitch devices from
different manufacturers and of different versions vary. This might lead to problems such as
voice delay or one-way audio. To make sure that all services can work properly, on-site
service scenarios must be tested according to the UAP8100 V300R003 Guide to the Dialing Test
in Deployment, but now, there is not English version about this document.
The path to the UAP8100 V300R003 Guide to the Dialing Test in Deployment at
http://support.huawei.com is as follows:
6.5 Testing the Voice Quality of the IPCC

System
For the IPCC system, the voice quality during a call depends on multiple factors. For
example, the data transmission network, UAP8100 device, audio adapter drive and settings of
the agent terminal, earphone, and OpenEye software. You need to pay attention to the voice
quality when testing service scenarios. If the voice quality has problems, locate and handle the
problems according to the Location of Voice Quality Problems for the TopEng-IPCC.
The paths to the preceding two documents at http://support.huawei.com are respectively:
Call Center and CRM > Technical Guide
2008-12-02
Page 196 of 212
6.6 Pressure Test for the IPCC System

Generally, after the IPCC system is debugged, pressure tests must be performed on the
UAP8100, platform, and data network using high-volume traffic. Pressure tests aim to check
whether the IPCC system can work properly in high-volume traffic. For the method of
performing pressure tests, see the Location of Voice Quality Problems for the TopEng-IPCC.
The paths to the preceding two documents at http://support.huawei.com are respectively:
6.7 Quality Standards and Checklists for Selfchecks

Before cutover, check the IPCC system according to main self-check items and checklists.
The checklist for the UAP8100 is the UAP8100 V300R003 Quality Check Criteria.
The checklist for the file server is the iCHECK_FS File Server Quality Check Criteria.
The checklist for external resources is the CC&CRM - AIP Quality Check Standard
V6.1-20060905-B.
The checklist for the platform is the CC&CRM ICDV300R002 Platform Software
Quality Check Standard V6.6 20070419-B.
The paths to the preceding documents at http://support.huawei.com are respectively:

> File Server
2008-12-02
Page 197 of 212
Appendix
7.1 Configuration Instance Script for IPCC

Service Applications (VRB Resource Board)
The instance script described in this chapter is based on the configuration of the UAP 8100
device in an on-line office.
7.1.1 Card Layout of the UAP8100 Hardware

Figure 1.1 MGC card layout
Back
board
E
T
I
E
T
I
E
T
I
S
I
U
Front
board
V
R
B
V
R
B
V
R
B
S
M
U
H
S
C
1
S
I
U
S
M
U

H
S
C
1

Air defense frame
2008-12-02
Back
board
B
F
II
B
F
II
B
F
II
B
F
II
S
I
U
Front
board
I
F
M
I
F
M
I
F
M
I
F
M
C
C
U
C
C
U
S
M
U
H
S
C
0
S
I
U
S
M
U
H
S
C
0
CKI
CKI
C
D
B
M
S
G
C
D
B
B
S
G
B
S
G
M
S
G
A
L
U
Page 198 of 212
Figure 1.2 MGW card layout
Back
board
C
L
K
C
L
K
E
3
2
E
3
2
T
N
U
N
E
T
N
E
T
T
N
U
E
8
T
E
8
T
Front
board
V
P
B
V
P
B
C
M
F
C
M
F
O
M
U
O
M
U
H
R
U
H
R
U
7.1.2 MGC Configuration Instance

//Configure hardware data. The BSG board must be in the load sharing mode.
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
SHF:
FRM:
FRM:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
SN=0,
FN=0,
FN=1,
FN=0,
FN=0,
FN=0,
FN=0,
FN=0,
FN=0,
FN=0,
FN=0,
FN=0,
FN=0,
FN=0,
FN=1,
FN=1,
FN=1,
FN=1,
FN=1,
FN=1,
LT="GXRZUAP", PN=0, RN=0, CN=0;

SN=0, PN=2;
SN=0, PN=3;
SN=4, LOC=FRONT, BT=CCU, MN=73, ASS=5;
SN=4, LOC=BACK, BT=EPII;
SN=5, LOC=BACK, BT=EPII;
SN=10, LOC=FRONT, BT=CDBI, MN=27, ASS=11;
SN=12, LOC=FRONT, BT=BSGI, MN=39, ASS=255;
SN=12, LOC=FRONT, BT=BSGI, MN=40, ASS=255;
SN=14, LOC=FRONT, BT=MSGI, MN=72, ASS=15;
SN=13, LOC=BACK, BT=CKII;
SN=15, LOC=BACK, BT=CKII;
SN=0, LOC=FRONT, BT=VRB, MN=252, VRBLT=E1;
SN=0, LOC=BACK, BT=ERI;
//Configure security schemes for accounts.

E7=DF;
//Set the IP address of the IFM board and set the port to 100 M full duplex.
ADD
ADD
MOD
MOD
FECFG:
FECFG:
FECFG:
FECFG:
MN=35,
MN=36,
MN=35,
MN=36,
IP="10.51.5.10", MSK="255.255.255.0", DGW="10.51.5.1";

IP="192.168.0.200", MSK="255.255.255.0", DGW="192.168.0.1";
EA=FH;
EA=FH;
//Add the CDB function. If no TTS exists, set only the following items:
ADD CDBFUNC: CDPM=27, FCF=LOC-1&TK-1&MGWR-1&DISP-1&CSTA-1;
//Add the CDB function of managing the global TTS resources.

ADD CDBFUNC: CDPM=27, FCF=LOC-1&TK-1&MGWR-1&DISP-1&CSTA-1&GTTSLICM-1;
2008-12-02
Page 199 of 212
//Configure the information about the current office, call resources, charge data, and number
segments.
SET OFI: OFN="GXUAP", LOT=CMPX, NN=YES, NPC="222222", NNS=SP24, SPF=YES;
ADD LDNSET: LP=0, NC=K'86, AC=K'771, LDN="GXHBRZ";
ADD DNSEG: LP=0, SDN=K'888000, EDN=K'888200;
ADD CALLSRC: CSC=0, CSCNAME="GXHBRZ", PRDN=3;
ADD CHGANA: CHA=0,VA=1, PA=60, PB=60, CONFIRM=Y;
MOD
CHGMODE:
CHA=0,
DAT=NORMAL,
TA1=60,
PA1=1,
TB1=60,
PB1=1,
AGIO1=100,CONFIRM=Y;
ADD CHGGRP: RCHS=0, DCHS=0, LOAD=ALL, CODEC=ALL, CHA=0,CONFIRM=Y;
ADD CHGIDX: CHSC=0, RCHS=0, LOAD=ALL, BT=RBT, CODEC=ALL, CHA=0;
//Configure the MGW. If VRU boards have EC pinch boards, enable the EC function.
LA="192.168.0.200", RA1="192.168.0.201", RP=2944, HAIRPIN=S, EC=FALSE,
CODETYPE=ASN, UCATT=NOEC-0;
//Configure SIP data.

SET SIPCFG:UST=NO;
SET SIPLP: MN=72, PORT=5061,CONFIRM=Y;
SET DPA: MN=72, DA=SIP-1,CONFIRM=Y;
//Configure SIP phone data.

ADB MMTE: SEID=K'888000, EEID=K'888200, MN=73, PT=SIP, IFMMN=35, AT=NA
ADB MMTE: SEID=K'6660000, EEID=K'6660009, MN=73, PT=SIP, IFMMN=35, AT=NA
ADB MMTE: SEID=K'99000, EEID=K'99299, MN=73, PT=SIP, IFMMN=35, AT=NA;
ADB MMTE: SEID=K'99300, EEID=K'99499, MN=73, PT=SIP, IFMMN=35, AT=NA;
ADB MSBR: SD=K'888000, ED=K'888200, LP=0, ET=COM, SEID=K'888000, RCHS=0,
CSC=0, ICR=LCO-1&LC-1&LCT-1&NTT-1&ITT-1&ICTX-1&OCTX-1&INTT-1&IITT-1, OCR=LCO1&LC-1&LCT-1&NTT-1&ITT-1&ICTX-1&OCTX-1&INTT-1&IITT-1;
ADB MSBR: SD=K'6660000, ED=K'6660009, LP=0, ET=COM, SEID=K'888000, RCHS=0,
CSC=0, ICR=LCO-1&LC-1&LCT-1&NTT-1&ITT-1&ICTX-1&OCTX-1&INTT-1&IITT-1, OCR=LCO1&LC-1&LCT-1&NTT-1&ITT-1&ICTX-1&OCTX-1&INTT-1&IITT-1;
ADB MSBR: SD=K'99000, ED=K'99299, LP=0, ET=COM, SEID=K'99000, RCHS=0, CSC=0,
ICR=LCO-1&LC-1&LCT-1&NTT-1&ITT-1&ICTX-1&OCTX-1&INTT-1&IITT-1,
OCR=LCO-1&LC1&LCT-1&NTT-1&ITT-1&ICTX-1&OCTX-1&INTT-1&IITT-1;
ADB MSBR: SD=K'99300, ED=K'99499, LP=0, ET=COM, SEID=K'99300, RCHS=0, CSC=0,
ICR=LCO-1&LC-1&LCT-1&NTT-1&ITT-1&ICTX-1&OCTX-1&INTT-1&IITT-1,
OCR=LCO-1&LC1&LCT-1&NTT-1&ITT-1&ICTX-1&OCTX-1&INTT-1&IITT-1;
//Configure SIP trunk data.

ADD OFC: O=1, ON="NNSS1", DOT=CMPX, DOL=HIGH;
ADD OFC: O=2, ON="NNSS2", DOT=CMPX, DOL=HIGH;
ADD SRT: SRC=1, O=1, SRN="NNSS1";
ADD SRT: SRC=2, O=2, SRN="NNSS2";
ADD SIPTG: TG=1, SRT=1, TGN="NNSS1", ICR=LCO-1&LC-1&LCT-1&NTT-1&ITT-1&INTT1&IITT-1&CCR1-1&CCR2-1&CCR3-1&CCR4-1&CCR5-1&CCR6-1&CCR7-1&CCR8-1&CCR91&CCR10-1&CCR11-1&CCR12-1&CCR13-1&CCR14-1&CCR15-1&CCR16-1,
OCR=LCO-1&LC1&LCT-1&NTT-1&ITT-1&INTT-1&IITT-1&CCR1-1&CCR2-1&CCR3-1&CCR4-1&CCR5-1&CCR61&CCR7-1&CCR8-1&CCR9-1&CCR10-1&CCR11-1&CCR12-1&CCR13-1&CCR14-1&CCR15-1&CCR161, IMN=35, OSU="10.53.0.3:5060", UHB=YES;
ADD SIPTG: TG=2, SRT=2, TGN="NNSS2", ICR=LCO-1&LC-1&LCT-1&NTT-1&ITT-1&INTT1&IITT-1&CCR1-1&CCR2-1&CCR3-1&CCR4-1&CCR5-1&CCR6-1&CCR7-1&CCR8-1&CCR91&CCR10-1&CCR11-1&CCR12-1&CCR13-1&CCR14-1&CCR15-1&CCR16-1,
OCR=LCO-1&LC1&LCT-1&NTT-1&ITT-1&INTT-1&IITT-1&CCR1-1&CCR2-1&CCR3-1&CCR4-1&CCR5-1&CCR61&CCR7-1&CCR8-1&CCR9-1&CCR10-1&CCR11-1&CCR12-1&CCR13-1&CCR14-1&CCR15-1&CCR161, IMN=35, OSU="10.53.4.3:5060", UHB=YES;
ADD RT: R=0, RN="NNSS1&2", SRST=PERC, SR1=1, SR2=2, PSR1=50, PSR2=50,
TRIPFLAG=NO;
ISUP=NOCHG;
2008-12-02
Page 200 of 212
//Add CDB resource management function.

ADD CCURC: CCUMN=73, CDBMN=27;
//Configure VRB data.

ADD CASCFG: SN="TO_VRB";
ADD N1TG: TG=0, EID="192.168.0.201:2944", G=INOUT,
TGN="TO_VRB";
SRC=0,
SN="TO_VRB",
//Add resource groups and resource sites.

ADD RCG: GN=1, GNAME="TO_VRB";
ADD
RCWSCFG:
WSNO=0,
INOUT=INSIDE,
GROUPNO=1,
MMN=27,
WSTYPE=VP,
MODULENO=252, EID="192.168.0.201:2944", SEPN=0, EPN=4, TID0="0", TID1="32",
TID2="64", TID3="96", DMODE=HALF, TTSCAP=SUP;
ADD
RCWSCFG:
WSNO=1,
INOUT=INSIDE,
GROUPNO=1,
MMN=27,
WSTYPE=VP,
MODULENO=252,
EID="192.168.0.201:2944",
SEPN=4,
EPN=4,
TID0="128",
ADD
RCWSCFG:
WSNO=10,
INOUT=INSIDE,
GROUPNO=1,
MMN=27,
WSTYPE=CP,
MODULENO=251,
EID="192.168.0.201:2944",
SEPN=0,
EPN=4,
TID0="256",
ADD
RCWSCFG:
WSNO=20,
INOUT=INSIDE,
GROUPNO=1,
MMN=27,
WSTYPE=FP,
MODULENO=250,
EID="192.168.0.201:2944",
SEPN=0,
EPN=1,
TID0="1024",
DMODE=HALF;
ADD
RCWSCFG:
WSNO=2,
INOUT=OUTSIDE,
GROUPNO=1,
MMN=27,
WSTYPE=VP,
EID="192.168.0.201:2944", SEPN=0, EPN=1, TID0="1280", DMODE=HALF, TTSCAP=SUP;
//Add the echo cancellation function for the conference.

//Add a file server.

MOD VRBFILESVR: MN=252, FSTFSIP="192.168.0.4", UID=65534, GID=65533, SDIR="/share",
MDIR="y:";
MDIR="y:";
MDIR="y:";
//Add MEM configuration items to VRB boards.

ADD MEMCFG: MN=252, PROTYPE=NULL, LIP="192.168.0.30",
RP=8888;
RP=8888;
RP=8888;
ADD MEMCFG: MN=27, PROTYPE=FEP, LIP="192.168.0.25",
RIP2="192.168.0.3", RP=5600;
RIP1="192.168.0.4",
RIP1="192.168.0.4",
RIP1="192.168.0.4",
RIP1="192.168.0.2",
//Configure the TTS.

//Configure the information about the TTS client to enable boards to provide the TTS
function.
SET TTSCON: SRMSUP=SUP, MNSRMIP="192.168.0.85", BKPSRMIP="192.168.0.86";
//Configure the language information for the current UAP8100. (The engine names for
broadband and narrowband must be set.)
2008-12-02
Page 201 of 212
ADD TTSLANG: LANGID=CHINESE, VFRMT=LINEWAVE64K, TEXTENC=GB-2312, ENGINFO="GXHBRZ",

//Configure segmentation information.

ADD LANGCFG: AC=60022168, LANGID=CHINESE, MAXLEN=120, VRATIO0=100, VRATIO1=100,
//Set the number of TTS channels.

CONNRESNUM=20;
//Add number conversion configurations.

ADD DNC: DCX=1, DCT=INS, ND=K'11832D;
//Add prefix data.

ADD
ADD
ADD
ADD
ADD
ADD
ADD
CNACLD:
CNACLD:
CNACLD:
CNACLD:
CNACLD:
CNACLD:
CNACLD:
PFX=K'888, MINL=6, MAXL=6;

PFX=K'114, CSTP=ADD, MINL=3, MAXL=3;
PFX=K'118114, CSTP=ADD, MINL=6, MAXL=6;
PFX=K'13, CSA=LC, RSC=0, MINL=11, MAXL=11;
PFX=K'15, CSA=LC, RSC=0, MINL=11, MAXL=11;
//Configure service data.

RIP2="192.168.0.3", RP=5600;
ADD
LST
ADD
ADD
MODSRV: SRVTYPE=ICD, SRVNAME="114", SRVDESC="114", ATTRIB=GLOBAL;

MODSRV: (query for service sequence number)
SRVATTR: DNSET=0, ACCESS=K'114, SRVNO=0;
SRVATTR: DNSET=0, ACCESS=K'118114, SRVNO=0;
//Modify NOTE parameter values.

MOD NOTEPRM: NOTEAMOUNT=49999;
//Add the configurations of trunk group bearing: prefix 11832D to the called number.
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
TGLD: CLI=0, TOP=3, RI=0, EI=1;

TGLDIDX: TG=1, CSC=0, LP=0, PFX=K'EEEEEEEE, CLI=0;
//Format data and manually restart frames.

FMT:;
7.1.3 MGW Configuration Instance

//Add hardware data.
2008-12-02
Page 202 of 212
MOD FRM: FN=1, FNM="GXHBRZ_MGW", FD="GXHBRZ_MGW";

ADS=ACTIVE;
ADS=ACTIVE;
ADD BRD: FN=1, SN=2, BP=FRONT, BT=CMU, HBT=CMF, BS=ONEBACKUP, BN=30;
ADD BRD: FN=1, SN=14, BP=FRONT, BT=HRB, HBT=HRU, BS=ONEBACKUP, BN=0;
ADS=ACTIVE;
ADS=ACTIVE;
ADD BRD: FN=1, SN=6, BP=BACK, BT=TNU, HBT=TNU, BS=ONEBACKUP, BN=1;
BN=0,
BN=1,
BN=0,
BN=1,
//Set the time synchronization mode and time zone.

SET TIMESYC: INFO=RTC;
SET ZONE: ZONE=8;
//Add the IP addresses of OMC network interfaces and E8T interface boards.
ADD IPADDR: BT=OMU, BN=0, IFT=ETH, IFN=0, IPADDR="192.168.116.116",
MASK="255.255.255.0", DSTIP="0.0.0.0";
MASK="255.255.255.0", DSTIP="0.0.0.0";
MASK="255.255.255.0", ISBEAR=YES, DSTIP="0.0.0.0";
//Add routing information.

ADD ROUTE: BT=HRB, BN=0, DSTIP="0.0.0.0", DSTMASK="0.0.0.0", RTTYPE=NEXTHOP,
NEXTHOP="10.51.5.1";
ADD ROUTE: BT=OMU, BN=0, DSTIP="0.0.0.0", DSTMASK="0.0.0.0", RTTYPE=NEXTHOP,
NEXTHOP="192.168.116.1";
ADD ROUTE: BT=HRB, BN=0, DSTIP="192.168.0.200", DSTMASK="255.255.255.0",
RTTYPE=NEXTHOP, NEXTHOP="192.168.0.200";
//Add the IP address of the NMS.

ADD GWADDR: BT=HRB, BN=0, IPADDR="10.51.5.1", MASK="255.255.255.0";
//Set the interface attributes. All interfaces must work in 100 M duplex mode.
ENPOE=NO;
2008-12-02
Page 203 of 212

ENPOE=NO;
ENPOE=NO;
ENPOE=NO;
ENPOE=NO;
ENPOE=NO;
ENPOE=NO;
//Add bearing relations.

ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
BEARREL:
BEARREL:
BEARREL:
BEARREL:
BEARREL:
BEARREL:
BEARREL:
BEARREL:
BEARREL:
BEARREL:
BEARREL:
BEARREL:
BN=0,
BN=0,
BN=0,
BN=0,
BN=0,
BN=0,
BN=1,
BN=1,
BN=1,
BN=1,
BN=1,
BN=1,
IP="10.51.5.18";
IP="10.51.5.19";
IP="10.51.5.20";
IP="10.51.5.21";
IP="10.51.5.22";
IP="10.51.5.23";
IP="10.51.5.18";
IP="10.51.5.19";
IP="10.51.5.20";
IP="10.51.5.21";
IP="10.51.5.22";
IP="10.51.5.23";
//Configure the media gateway.

SET VMGW: VMGWID=0, MIDTYPE=IP, MID="192.168.0.201:2944", RPTIMES=3, RPINTV=3,
RLSINTV=30, LNKFAILLEN=30, IPNUM=86016, TDMNUM=400384, ATMNUM=221184, AUTOSWP=YES,
LNKHBTIME=3, LNKMAXHBLOSS=5, STACKVER=1;
//Add the MGC.

ADD
MGC:
MSS=MASTER;
VMGWID=0,
MGCIDX=0,
MIDTYPE=IP,
MID="192.168.0.200:2944",
//Add an H.248 link.

ADD H248LNK: LINKID=0, VMGWID=0, MGCIDX=0, TT=UDP, LOCALIP="192.168.0.201",
LOCALPORT=2944, PEERIP="192.168.0.200", PEERPORT=2944, LINKNAME="TO_GXRZMGC", FN=0,
SN=0, BP=FRONT;
//Activate the media gateway.

ACT VMGW: VMGWID=0;
//Set TC parameters. Increase receiving and sending gains to improve the voice quality of
calls.
2008-12-02
Page 204 of 212
SET TCPARA: G723RT=G723_RATE_63, G726RT=G726_RATE_40_ITUT, BPCM=G711A, BPT=PT20,

PLC=ENABLE, G711PT=PT20, G726PT=PT20, G723PT=PT30, G729PT=PT20, ISDNPT=PT10, RG=2,
TG=2, R2198RN=1, R2198RNT=96, RFC2833RDT=DISABLE, G711RDT=DISABLE, DL=40, ICCA=10,
JCNCA=40, MADA=120, EDA=ENABLE, EG711FLAA=ENABLE, VRS=DISABLE, G711VADPT=13,
DTMFMODE=INBAND;
//Add TDM bearing relations. Do not configure TID for the interfaces that are not connected
to trunks. Otherwise, the MGW alarm subsystem generates alarms.
ADD TDMIU: BT=E32, BN=0, TIDFV=0, TIDLV=511, VMGWID=0, RT=EXTERN;
ADD TDMIU: BT=E32, BN=1, TIDFV=1024, TIDLV=1279, VMGWID=0, RT=EXTERN;
//Configure all boards to start in the FLASH mode.

SET BRDSTART: MOD=FLASH;
7.2 Configuration Instance Script for IPCC

Service Applications (MSU Resource Board)
The instance script described in this chapter is based on the configuration of the UAP 8100
device in an on-line office.
7.2.1 Card Layout of the UAP8100 Hardware

Figure 1.1 MGC card layout
Back
board
M
R
I
M
R
I
M
R
I
S
I
U
Front
board
M
S
U
M
S
U
M
S
U
S
M
U
H
S
C
1
S
I
U
S
M
U

H
S
C
1

Air defense frame
Back
board
B
F
II
B
F
II
S
I
U
Front
board
I
F
M
I
F
M
C
C
U
C
C
U
S
M
U
H
S
C
0
S
I
U
S
M
U

H
S
C
0
C
D
B
CK
I
C
D
B
M
S
G
CKI
M
S
G
A
L
U
7.2.2 MGC Configuration Instance

//Configure hardware data.
2008-12-02
Page 205 of 212

ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
SHF:
FRM:
FRM:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
BRD:
SN=0,
FN=0,
FN=1,
FN=0,
FN=0,
FN=0,
FN=0,
FN=0,
FN=0,
FN=0,
FN=0,
FN=0,
FN=0,
FN=1,
FN=1,
FN=1,
FN=1,
FN=1,
FN=1,
FN=1,
FN=1,
FN=1,
FN=1,
FN=1,
FN=1,
FN=1,
FN=1,
FN=1,
FN=1,
FN=1,
FN=1,
FN=1,
FN=1,
FN=1,
FN=1,
FN=1,
FN=1,
FN=1,
FN=1,
LT="daping", PN=0, RN=0, CN=0, PL=2, PT=PDB48V;

SN=0, PN=2;
SN=0, PN=3;
SN=8, LOC=FRONT, BT=SMU;
SN=16, LOC=FRONT, BT=ALU;
SN=17, LOC=FRONT, BT=UPWR;
SN=17, LOC=BACK, BT=UPWR;
SN=1, LOC=FRONT, BT=IFM, MN=35, ASS=0;
SN=5, LOC=FRONT, BT=CCU, MN=73, ASS=4;
SN=11, LOC=FRONT, BT=CDB, MN=27, ASS=10;
SN=15, LOC=FRONT, BT=MSG, MN=72, ASS=14;
SN=8, LOC=FRONT, BT=SMU;
SN=16, LOC=FRONT, BT=ALU;
SN=0, LOC=FRONT, BT=MSU, MN=252;
SN=0, LOC=BACK, BT=MRI;
//Configure security schemes for accounts.

E7=DF;
//Set the IP address of the IFM board and set the interface to 100 M full duplex.
ADD FECFG: MN=35, IP="10.59.36.21", MSK="255.255.255.128", DGW="10.59.36.1", EA=FH,
SO=AD-0&FC-0;
//Add the CDB function. If no TTS exists, set only the following items:
ADD CDBFUNC: CDPM=27, FCF=LOC-1&TK-1&MGWR-1&DISP-1&CSTA-1;
//Add the CDB function of managing the global TTS resources.

ADD CDBFUNC: CDPM=27, FCF=LOC-1&TK-1&MGWR-1&DISP-1&CSTA-1&GTTSLICM-1;
//Configure the information about the current office, call resources, charge data, and number
segments.
SSET OFI: OFN="CQDXUAP", LOT=CMPX, NN=YES, NPC="FFFFFF", NNS=SP24, SPF=YES;
ADD LDNSET: LP=0, NC=K'86, AC=K'23, LDN="CQIPCC";
ADD CALLSRC: CSC=0, CSCNAME="CQDXUAP", PRDN=1;
ADD CHGANA: CHA=0,VA=1, PA=60, PB=60, CONFIRM=Y;
MOD
CHGMODE:
CHA=0,
DAT=NORMAL,
TA1=60,
PA1=1,
TB1=60,
PB1=1,
2008-12-02
Page 206 of 212
AGIO1=100,CONFIRM=Y;
ADD CHGGRP: RCHS=0, DCHS=0, LOAD=ALL, CODEC=ALL, CHA=0,CONFIRM=Y;
ADD CHGIDX: CHSC=0, RCHS=0, LOAD=ALL, BT=RBT, CODEC=ALL, CHA=0;
//Configure SIP data.

SET SIPCFG:UST=NO;
SET SIPLP: MN=72, PORT=5061;
SET DPA: MN=72, DA=SIP-1;
//Configure SIP phone data.

ADB MMTE: SEID=K'880000, EEID=K'880099, MN=73, PT=SIP, IFMMN=35, PASS="cqipcc",
AT=ABE;
ADB MSBR:
CSC=0;
SD=K'880000,
ED=K'880099,
LP=0,
ET=COM,
SEID=K'880000,
RCHS=0,
//Delete the default VRB sub link and office direction.

RMV SRT: SRC=0, FRDF=TRUE;
RMV OFC: O=0, FRDF=TRUE;
//Configure SIP trunk data.

ADD OFC: O=0, ON="huawei_ss1", DOT=CMPX, DOL=HIGH;
ADD OFC: O=1, ON="huawei_ss2", DOT=CMPX, DOL=HIGH;
ADD OFC: O=2, ON="zhongxing_ss1", DOT=CMPX, DOL=HIGH;
ADD OFC: O=3, ON="zhongxing_ss2", DOT=CMPX, DOL=HIGH;
ADD SRT: SRC=0, O=0, SRN="huawei_ss1";
ADD SRT: SRC=1, O=1, SRN="huawei_ss2";
ADD SRT: SRC=2, O=2, SRN="zhongxing_ss1";
ADD SRT: SRC=3, O=3, SRN="zhongxing_ss2";
ADD SIPTG: TG=0, SRT=0, TGN="huawei_ss1", ICR=LCO-1&LC-1&LCT-1&NTT-1&ITT-1&INTT1&IITT-1&CCR1-1&CCR2-1&CCR3-1&CCR4-1&CCR5-1&CCR6-1&CCR7-1&CCR8-1&CCR9-1&CCR101&CCR11-1&CCR12-1&CCR13-1&CCR14-1&CCR15-1&CCR16-1, OCR=LCO-1&LC-1&LCT-1&NTT-1&ITT1&INTT-1&IITT-1&CCR1-1&CCR2-1&CCR3-1&CCR4-1&CCR5-1&CCR6-1&CCR7-1&CCR8-1&CCR91&CCR10-1&CCR11-1&CCR12-1&CCR13-1&CCR14-1&CCR15-1&CCR16-1, IMN=35,
OSU="10.59.34.4:5060", UHB=YES;
ADD SIPTG: TG=1, SRT=1, TGN="huawei_ss2", ICR=LCO-1&LC-1&LCT-1&NTT-1&ITT-1&INTT1&IITT-1&CCR1-1&CCR2-1&CCR3-1&CCR4-1&CCR5-1&CCR6-1&CCR7-1&CCR8-1&CCR9-1&CCR101&CCR11-1&CCR12-1&CCR13-1&CCR14-1&CCR15-1&CCR16-1, OCR=LCO-1&LC-1&LCT-1&NTT-1&ITT1&INTT-1&IITT-1&CCR1-1&CCR2-1&CCR3-1&CCR4-1&CCR5-1&CCR6-1&CCR7-1&CCR8-1&CCR91&CCR10-1&CCR11-1&CCR12-1&CCR13-1&CCR14-1&CCR15-1&CCR16-1, IMN=35,
OSU="10.59.18.4:5060", UHB=YES;
ADD SIPTG: TG=2, SRT=2, TGN="zhongxing_ss1", ICR=LCO-1&LC-1&LCT-1&NTT-1&ITT-1&INTT1&IITT-1&CCR1-1&CCR2-1&CCR3-1&CCR4-1&CCR5-1&CCR6-1&CCR7-1&CCR8-1&CCR9-1&CCR101&CCR11-1&CCR12-1&CCR13-1&CCR14-1&CCR15-1&CCR16-1, OCR=LCO-1&LC-1&LCT-1&NTT-1&ITT1&INTT-1&IITT-1&CCR1-1&CCR2-1&CCR3-1&CCR4-1&CCR5-1&CCR6-1&CCR7-1&CCR8-1&CCR91&CCR10-1&CCR11-1&CCR12-1&CCR13-1&CCR14-1&CCR15-1&CCR16-1, IMN=35,
OSU="10.59.32.10:5060", UHB=YES;
ADD SIPTG: TG=3, SRT=3, TGN="zhongxing_ss2", ICR=LCO-1&LC-1&LCT-1&NTT-1&ITT-1&INTT1&IITT-1&CCR1-1&CCR2-1&CCR3-1&CCR4-1&CCR5-1&CCR6-1&CCR7-1&CCR8-1&CCR9-1&CCR101&CCR11-1&CCR12-1&CCR13-1&CCR14-1&CCR15-1&CCR16-1, OCR=LCO-1&LC-1&LCT-1&NTT-1&ITT1&INTT-1&IITT-1&CCR1-1&CCR2-1&CCR3-1&CCR4-1&CCR5-1&CCR6-1&CCR7-1&CCR8-1&CCR91&CCR10-1&CCR11-1&CCR12-1&CCR13-1&CCR14-1&CCR15-1&CCR16-1, IMN=35,
OSU="10.59.16.10:5060", UHB=YES;
ADD RT: R=0, RN="huawei_ss", SRST=PERC, SR1=0, SR2=1, PSR1=100, PSR2=0,
TRIPFLAG=NO;
ADD RT: R=2, RN="zhongxing_ss", SRST=PERC, SR1=2, SR2=3, PSR1=100, PSR2=0,
TRIPFLAG=NO;
2008-12-02
Page 207 of 212
ISUP=SIP_F;
ISUP=SIP_F;
//Add prefix data.

ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
ADD
CNACLD:
CNACLD:
CNACLD:
CNACLD:
CNACLD:
CNACLD:
CNACLD:
CNACLD:
CNACLD:
CNACLD:
CNACLD:
CNACLD:

PFX=K'34567, CSTP=ADD, MINL=5, MAXL=5, DEST=0;
PFX=K'0, CSA= LC, RSC=0, MINL=4, MAXL=12;
//Add resource groups.

ADD RCG: GN=1, GNAME="vpcp";
ADD RCG: GN=2, GNAME="TTS";

ADD RCG: GN=3, GNAME="fax";
//Add resource sites.

ADD
RCWSCFG:
MODULENO=251;
WSNO=5,
INOUT=INSIDE,
GROUPNO=3,
MMN=27,
WSTYPE=MSUF,

MRPNO=0, TTSCAP=NSUP;
MRPNO=1, TTSCAP=NSUP;
//Add MSU configurations.

ADD MSUCFG: MRFID=251, MRFTYPE=FAX, RSMD=EM;
//Configure MRP information.

ADD MRPCFG: MBID=252, BID=LMRPB, MRPT=MRPC, MIP="10.59.36.31",
IPM="255.255.255.128", MRPDR="10.59.36.1", PFF=YES, HPFF=YES, VADF=YES, ECF=YES,
CNGF=NO, ECT=ECT64, HL=6, VOL=0, IG=0, JBF=NO, JBM=1, JBOF=5, JBL=5, MD=MDIN,
CD=CSEG729A, DCD=CSEG729A, CPL=PL10, DPCL=PL10, CPUT=80, FUP=10000, UPN=320;
ADD MRPCFG: MBID=252, BID=UMRPB, MRPT=MRPC, MIP="10.59.36.32",
ADD MRPCFG: MBID=251, BID=LMRPB, MRPT=MRPF, MIP="10.59.36.35",
ADD MRPCFG: MBID=250, BID=LMRPB, MRPT=MRPC, MIP="10.59.36.37",
2008-12-02
Page 208 of 212
ADD MRPCFG: MBID=250, BID=UMRPB, MRPT=MRPC, MIP="10.59.36.38",

//Add information about the MEM module of MSU boards.

RIP2="192.168.100.110", RP=1111, DGW="0.0.0.0", MASK="255.255.255.0",
DGW2="0.0.0.0", MASK2="255.255.255.0", TTSIP="192.168.3.20",
TTSMASK="255.255.255.0";
RIP2="192.168.100.110", RP=1111, DGW="0.0.0.0", MASK="255.255.255.0",
DGW2="0.0.0.0", MASK2="255.255.255.0", TTSMASK="255.255.255.0";
RIP2="192.168.100.110", RP=1111, DGW="0.0.0.0", MASK="255.255.255.0",
DGW2="0.0.0.0", MASK2="255.255.255.0", TTSMASK="255.255.255.0";
//Add information about the file server.

ADD FILESVR: MN=252, PROTOCOL=NFS, IDXFS=IDX0, FSTFSMIP="192.168.1.110",
//Configure service data.

RIP2="192.168.1.21", RP=5600, DGW="0.0.0.0", MASK="255.255.255.0", DGW2="0.0.0.0",
MASK2="255.255.255.0", TTSMASK="255.255.255.0";
ADD MODSRV: SRVTYPE=ICD, SRVNAME="1", SRVDESC="34567", ATTRIB=GLOBAL;

LST MODSRV: (query for service sequence number)
ADD SRVATTR: DNSET=0, ACCESS=K'34567, SRVNO=0, MIN=0, MAX=24, TRIGPOS=255,

TRIGTIME=255;
//Modify NOTE parameters.

MOD NOTEPRM: NOTEPATH="note", NOTEHEAD="note", UPDATEPATH="update",
NOTEAMOUNT=49999, STARTIDX=1, POSTFIX=NULL, BUFSIZE=2097152, UPDATEINTERVAL=1000,
DELINTERVAL=2000;
//Configure the TTS.

SET TTSCON: SRMSUP=SUP, MNSRMIP="192.168.3.10", SRVFCT=50, SRVFCP=4;
ADD TTSLANG: LANGID=CHINESE, VFRMT=LINEWAVE64K, TEXTENC=GB-2312, ENGINFO="intp40",
//Format data and manually restart frames.

FMT:;
2008-12-02
Page 209 of 212
7.3 Configuration Instance of M2UA Signaling

Considering the configuration of boards, resource sites, the configuration of M2UA signaling
and that of the preceding instance are the same. The differences between the two instances lie
in the configuration of signaling data and trunk data. For details about the configuration of
M2UA signaling, see attachment 10 M2UA Configuration Instance.
7.4 Common Analysis and Positioning Tools

For details about the usage and analysis of the Ethereal tool, see the attachment 11 Use of
Common Analyzing and Positioning Tools.
7.5 Usage Instructions for Message Tracing

During a call, messages that need to be traced are SIPOP, INTESS, SRM, RIM, VRB, CDB,
and INTERFACE SIGNALING.
Basic process of a call in the UAP8100 (the sequence of modules that a call passes through)
is: INTERFACE SIGNALING, INTESS, CDB, RIM, VRB, and SIPOP.
7.6 Acceptance Documents
UAP8100 Acceptance Manual_(V300R003_01)

Documentation > Application and Software Product Line > Service and Software
Public > UAP&URP > Technical Guide > Acceptance Manual
Checklist on the URP8100 V300R001 Before Cutover

Documentation > Application and Software Product Line > Service and Software
Public > UAP&URP > Technical Guide > Quality Check Guide
7.7 Network Protocol Analysis Tool
Document name.
Ethereal Operation Guide
Document location
Documentation > Access Network Product Line > Broadband Access > Broadband
Access products > Function and Feature > Instrument and Tool
2008-12-02
Page 210 of 212

TopEng IPCC Deployment Guide V1.6

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

TopEng IPCC Deployment Guide V1.6

Hochgeladen von

Copyright:

Verfügbare Formate

For internal use only