Escolar Documentos
Profissional Documentos
Cultura Documentos
Document code
Product name
Target readers
Deployment engineers
Product version
Edited by
Document
version
IPCC
V1.6
Liu Jintao
Date
Reviewed by
Zhang Chunhe
Date
Reviewed by
Approved by
2007-11-02
Date
Zhang Chunhe
Date
Revision History
Date
Version
Description
Author
2007-11-02
V1.0
Liu Jintao
2008-01-07
V1.1
Liu Jintao
2008-02-13
V1.2
Liu Jintao
2008-03-21
V1.3
Liu Jintao
Date
Version
Description
Author
2008-06-10
V1.4
Liu Jintao
2008-08-10
V1.5
Liu Jintao
2008-11-29
V1.6
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
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
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
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 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-14 Data preparations...............................................................................................................................111
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-17 Data preparations...............................................................................................................................114
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-20 Data preparations...............................................................................................................................117
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-23 Data preparations...............................................................................................................................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-29 Data preparations..............................................................................................................................127
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-33 Data preparations..............................................................................................................................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
Keywords
IPCC, deployment guide
Abstract
This document instructs customer service engineers in preparing for IPCC deployment and in
debugging equipment and services.
Reference Documents
TopEng IPCC Configuration Template V1.3
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.
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:
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
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.
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:
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.
2008-12-02
Narrowband ACD
Packet ACD
Page 3 of 212
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
interface is the FE (IP) interface.
2008-12-02
Page 4 of 212
On the NGN network, the UAP8100 works with the CTI platform and implements the
following functions on the pure packet network:
Call distribution
Media conversion
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
interface is the FE (IP) interface.
2008-12-02
Page 5 of 212
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.
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
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.
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)
Page 9 of 212
SN
Key Item
Description
GT
Destination SPC
Signaling link
selection code
Circuit number
corresponding to the
signaling link
CIC distribution
2 MB signaling
10
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.
2008-12-02
Page 11 of 212
Description
IP address of an opposite
office
Prefix pointing to an
opposite office
2008-12-02
SN
Key Item
Description
Page 12 of 212
SN
Key Item
Description
10
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
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.
VLAN1
VLAN2
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.
In addition, the network port of the SBC server must be connected to the VLAN network.
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
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.
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.
Key Item
Description
client-address
server-address
softx-address
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
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.
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.
2008-12-02
Page 18 of 212
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.
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.
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.
2008-12-02
Page 20 of 212
Description
Protocol type
Registration
(authentication)
mode
IP address
User ID
Password
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
FP
V610R003.5Da17
OpenEye
TTS
InterPhonic4.0+ISP2.5
Page 21 of 212
Product
Name
Version
ASR
FS operating
system
SUSE9+SP03
FS cluster
software
Veritas4.1+MP2
SBC
I2000
I2000V300 R001.2DH04+SPC006
OAM
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.
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.
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.
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.
2008-12-02
Page 23 of 212
2008-12-02
Page 24 of 212
Hardware Installation
This chapter describes the following basics about the UAP8100 hardware installation:
For details, see the delivery-attached manual of the UAP8100 U-SYS UAP8100 Universal
Access Platform Hardware Installation Guide.
2008-12-02
Page 25 of 212
(1): power
supply board
(6): front board
(2): interface
board
(7): service
board
(3): Ethernet
communications board
(8): system administration
board
(5): mother
board
The front board consists of a service board, a system administration board, and an alarm
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
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
Back
Front
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.
2008-12-02
Page 28 of 212
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
2008-12-02
Page 29 of 212
FE port for separated networking of CTILINK and the memory (MEM) board
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.
Board
Working Mode
of the Current
Interface
Device of
the
Opposite
Interface
Working Mode of
the Opposite
Interface
UAP8100
MGC
IFM
LanSwitch
100M HSC
Auto Negotiation
LanSwitch
Auto Negotiation
1000M
HSC
LanSwitch
E8T
LanSwitch
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.
VLAN1
VLAN2
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.
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
DIP switch for specifying the device number and frame number of the MGC
DIP switch for specifying the grounding mode, matching resistance, and link attributes
of E1 lines for E32 boards
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
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
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
Description
Setting
S1
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.
2008-12-02
DIP
Switch
Description
Setting
S2, S3, S4
Page 36 of 212
DIP
Switch
S5
Description
Setting
cable type
Bit 1: for
specifying the
mode of cyclic
redundancy check
(CRC)
Bit 2: for
specifying the type
of the connected
E1 lines
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.
2008-12-02
Page 37 of 212
Helps to
S2
S3
S4
S5
Descriptio
n
Application
ON
Grounding
OFF
Not
grounding
Figure 1.3 E1 line interfaces that the DIP switches S6 to S13 control
DIP Switch
Helps to
S6
S7
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
OFF
ON
Application Scenario
ON
ON
OFF
ON
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.
Before installation, familiarize yourself with the Site Survey Report and pay attention to
the following points:
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.
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.
2008-12-02
Page 41 of 212
2008-12-02
Page 42 of 212
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.
2008-12-02
Page 43 of 212
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 S1 and S2
1 (J5)
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.
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
BAM IP address
Type the IP address of the BAM, that is, the IP address that is
used for communicating with the terminal.
Baud
Select 19200.
Data bit
Select 8.
Parity
Select None.
Stop bit
Select 1.
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.
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 S1 and S2
1 (JT6)
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.
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).
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
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.
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.
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
Helps to
Choose START > program > Huawei Local Maintenance Terminal > U-SYS
UAP8100 MGW V300R003 > U-SYS UAP8100 MGW Alert Management System.
2.
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.
2008-12-02
Page 51 of 212
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:
Documentation > Application and Software Product Line > Service and Software Public
> UAP&URP > Product Manual
Documentation > Application and Software Product Line > Service and Software Public
> CTI > Version Release Document
Documentation > Application and Software Product Line > Service and Software Public
> File Server > Technical Guide
2008-12-02
Page 53 of 212
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
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
Software
Data
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.
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.
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.
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.
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.
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.
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
2008-12-02
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
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
2008-12-02
Page 65 of 212
2008-12-02
Page 66 of 212
Step 8 Select Send to upgrade the BIOS. See the following figure.
2008-12-02
Page 67 of 212
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 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
Handling Process
Check the network connection between the BAM and the MGC, and check the
connection between the SMU and the HSC.
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.
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
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.
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
2008-12-02
Page 71 of 212
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
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.
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
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.
System Boot
CPU:
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
(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 ethernet (e) : 10.10.86.254
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)
:
2008-12-02
Page 76 of 212
CPU:
- MPC 750
vxWorks Version:
BSP Version in Ext btrm:
5.4.2
Version : V300R003B01D051
Version : V100R003B02D020
Nov 10 2004, 20:56:55
512 M
Extended bootrom
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";
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.
2008-12-02
Page 78 of 212
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.
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
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.
2008-12-02
Page 80 of 212
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
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 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
2008-12-02
Page 83 of 212
Step 2 Start the TTS service according to the type of the TTS server.
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
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.
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.
Page 85 of 212
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.
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.
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
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.
2008-12-02
Page 87 of 212
Data Preparation
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.
Module number range for an SMU: 226 (automatically assigned by the system)
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 FECFG
ADD EPICFG
ADD CDBFUNC
ADD CCURC
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 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,
Page 89 of 212
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
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
IP address of FE port
2008-12-02
Page 91 of 212
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
Number segment
planning
Configuration Procedure
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 OFI
Page 92 of 212
Ste
p
Description
Command
ADD LDNSET
ADD CALLSRC
ADD DNSEG
10
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.
Configuration Relations
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
Page 94 of 212
Parameter
Local DN set
Global DN set
Configuration Procedure
Figure 1.1 Steps for configuring the charging data
Step
Description
Command
MOD CHGMODE
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.
Configuration Relations
Figure 1.1 shows the relations between key parameters in data tables used when you configure
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
other UAP8100 MGC data in later steps. See Figure 1.2.
Figure 1.2 Parameter citing relations between charging data and other data
Parameter
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.
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.
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.
2008-12-02
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.
Configuration Procedure
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 BOSRC
SET CKICFG
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.
2008-12-02
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.
Figure 1.1 Data preparations
SN
Item
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.
Configuration Relations
You need to refer to the values of some parameters of the MGW data when you configure
other UAP8100 MGC data in later steps. See Figure 1.1.
2008-12-02
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
IP address of FE port
Configuring
hardware data
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.
2008-12-02
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
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.
Figure 1.1 Data preparations
SN
Item
Remarks
Destination
signaling point
code
Local signaling
point code
STP flag
The link set index is used to select the link set to which the
link belongs.
Signaling link
code
Link type
NOTE
If you select type 0 or 1, you need to configure the circuit timeslot.
2008-12-02
SN
Item
Remarks
Module number
of the CCU that
manages links
Configuration Procedure
Figure 1.1 lists the steps for configuring the MTP data.
Figure 1.1 Steps for configuring the MTP data
Step
Description
Command
ADD N7DSP
ADD N7LKS
ADD N7LNK
ADD N7RT
ACT N7LNK
For the description of parameters for each command, see the online help.
The following is an example:
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,
Configuration Relations
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
Configuring local
exchange data
Figure 1.2 shows the relations between key parameters in data tables used when you configure
the MTP data.
Figure 1.2 Relations between data tables
In MTP-M2UA signaling networking mode, the M2UA link set index defined in ADD M2LKS will be
referenced by ADD N7LNK.
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
Background Knowledge
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.
Local IP address
Peer IP address
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
Item
Remarks
IP address of
embedded signaling
gateway
NOTE
You must plan this port number and the local SCTP port number
of the M3UA link in a unified way.
Configuration Procedure
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 ESG
ADD M2LKS
ADD M2LNK
ACT M2LNK
For the description of parameters for each command, see the online help.
The following is an example:
//Add an embedded signaling gateway.
ADD ESG: SGID=2, SGNAME="M2UA SG", EID="192.16.254.49:5500";
2008-12-02
Configuration Relations
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
IP address of FE port
Configuring
hardware data
Configuring MTP
link data
Module number of
BSG
Configuring
hardware data
Equipment ID of the
MGW
Configuring media
gateway data
Figure 1.2 shows the relations between key parameters in data tables used when you configure
the M2UA data.
2008-12-02
Background Knowledge
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.
2008-12-02
Data Preparation
Before configuring the M3UA data, prepare the data items listed in Figure 1.1.
Figure 1.1 Data preparations
SN
Item
Remarks
Configuration Procedure
Figure 1.1 lists the steps for configuring the M3UA data.
Figure 1.1 Steps for configuring the M3UA data
Step
Description
Command
ADD M3LE
ADD M3DE
ADD M3DS
ADD M3LKS
ADD M3LNK
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.
For the description of parameters for each command, see the online help.
The following is an example:
//Add a local M3UA entity.
ADD M3LE: LEX=0, LENAME="UAP8100", OPC="001122", LET=AS, RC=12345;
2008-12-02
LOCIP1="192.16.254.38", LOCPORT=2905,
LSX=0;
LOCIP1="192.16.254.38", LOCPORT=2911,
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.
Configuration Relations
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
data and configuring
routing data
Module number of
BSG
Configuring
hardware data
Signaling point
code of destination
entity
Configuring SCCP
data and configuring
routing data
Module number of
IFM
Configuring
hardware data
Local signaling
point code
Configuring local
exchange data
Figure 1.2 shows the relations between key parameters in data tables used when you configure
the M3UA data.
2008-12-02
Background Knowledge
2008-12-02
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.
Figure 1.1 Data preparations
SN
Item
Remarks
Configuration Procedure
Figure 1.1 lists the steps for configuring the SIP data.
Figure 1.1 Steps for configuring the SIP data
Step
Description
Command
SET SIPCFG
SET SIPLP
The MSG supports the SIP protocol. You can run SET DPA to configure the protocol distribution
ability.
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.
2008-12-02
Configuration Relations
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
Local DN set
Call source
Data Preparation
Before configuring the routing data, prepare the data items listed in Figure 1.1.
Figure 1.1 Data preparations
SN
Item
Remarks
Routing policy
Configuration Procedure
Figure 1.1 lists the steps for configuring the routing data.
2008-12-02
Description
Command
ADD OFC
Add a sub-route.
ADD SRT
Add a route.
ADD RT
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.
For the description of parameters for each command, see the online help.
The following is an example:
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;
Configuration Relations
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
Sub-route
number
Configuring trunk
data
Input Parameter
Output Parameter
Parameter
Name
Parameter
Name
Location for
Citing
Destination
point code
DPC in office
direction
Configuring trunk
data (required by
No.7 trunks only)
Route selection
code
Configuring number
analysis data
Figure 1.2 shows the relations between key parameters in data tables used when you configure
the routing data.
2008-12-02
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
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.
Background Knowledge
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
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.
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.
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
Item
Remarks
Start CIC
10
11
Configuration Procedure
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 N7TG
ADD N7TKC
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.
For the description of parameters for each command, see the online help.
The following is an example:
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;
Configuration Relations
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
Configuring local
exchange data
Network
management source
code
Network
management data
Configuring charging
data
Configuring charging
data
Equipment ID of
trunk MGW
Configuring media
gateway data
Sub-route number
Configuring routing
data
Configuring
restricted call data
Figure 1.2 shows the relations between key parameters in data tables used when you configure
the No.7 trunk data.
2008-12-02
Background Knowledge
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
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:
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.
Figure 1.1 Data preparations
2008-12-02
SN
Item
Remarks
SN
Item
Remarks
Configuration Procedure
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 N1TG
ADD N1TKC
ADD CASCFG
For the description of parameters for each command, see the online help.
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.
The following is an example:
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",
Configuration Relations
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
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
Configuring local
exchange data
Network
management
source code
Configuring
network
management data
Equipment ID of
trunk MGW
Configuring media
gateway data
Sub-route number
Figure 1.2 shows the relations between key parameters in data tables used when you configure
the R2 trunk data.
Figure 1.2 Relations between data tables
2008-12-02
Description
Command
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.
Item
Remarks
Prefix table
Local DN set
Signal tone sending method
Number change index
3
2008-12-02
SN
Item
Remarks
Configuration Procedure
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 CNACLD
ADD DNC
ADD PFXPRO
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.
For the description of parameters for each command, see the online help.
The following is an example:
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,
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.
UAP 2 is used for contact center 2. The area code of contact center 2 is 0756. The NCC
service access code is 222.
UAP 3 is used for contact center 3. The area code of contact center 3 is 0757. The NCC
service access code is 333.
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.
Configuration Relations
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
Figure 1.2 shows the relations between key parameters in data tables used when you configure
the number analysis data.
2008-12-02
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."
2008-12-02
SN
Item
Remarks
Workstation planning
SN
Item
Remarks
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.
10
11
Remote port
12
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.
2008-12-02
The CDB can manage the trunk resources of the VRB as easily as it manages ordinary
trunk circuits.
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
SN
Item
Remarks
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 BRD
ADD CDBASSIST
ADD RCG
ADD RCWSCFG
ADD MEMCFG
SET EC
ADD ACD
10
MOD NOTEPRM
11
MOD INCFG
12
SET FAXPARA
13
SET FAXCFG
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.
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.
2008-12-02
Basic data, including the frame number, slot number, board location, board type, and
module number
MRP 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
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
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 BRD
ADD MSUCFG
ADD MRPCFG
ADD MEMCFG
ADD RCWSCFG
MOD NOTEPRM
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.
Figure 1.7 Relations between data tables
ADD BRD
[Frame number]
ADD MSUCFG
[MSU module number]
[Slot number]
[Module number]
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]
2008-12-02
Description
ADD BRD
Add a board.
RMV BRD
Delete a board.
LST BRD
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.
Description
ADD MSUCFG
RMV MSUCFG
MOD MSUCFG
LST MSUCFG
Description
ADD MRPCFG
RMV MRPCFG
MOD MRPCFG
LST MRPCFG
2008-12-02
//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";
Description
ADD MEMCFG
RMV MEMCFG
MOD MEMCFG
LST MEMCFG
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 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.
2008-12-02
Command
Description
ADD FILESVR
RMV FILESVR
MOD FILESVR
LST FILESVR
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.
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:";
ADD FILESVR: MN=80, IDXFS=1, FSTFSMIP="192.168.0.35",
FSTFSSBIP="10.76.172.146", SNDFSMIP="192.168.0.36", SNDFSSBIP="10.76.172.147",
SDIR="/share", MDIR="Y:";
ADD FILESVR: MN=80, IDXFS=2, FSTFSMIP="192.168.0.35",
FSTFSSBIP="10.76.172.146", SNDFSMIP="192.168.0.36", SNDFSSBIP="10.76.172.147",
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,
SDIR="/share", MDIR="Y:";
2008-12-02
Command
Description
ADD RCWSCFG
RMV RCWSCFG
MOD RCWSCFG
LST RCWSCFG
Description
MOD NOTEPRM
LST NOTEPRM
Description
MOD INCFG
LST INCFG
2008-12-02
Fiber
FS-1
A . FS
NFS
IP
192 .168 .4. xx (N
FS IP 1 NFS
IP 2
)
main .cf
Fiber
FS-2
Heartbeat
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
5624 - 2
Trunk
Fiber
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
In the ADD FILESVR command, First File Server Master IP and First File Server Slave IP are need
parameter at least.
2008-12-02
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'
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"
)
2008-12-02
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
Workstation numbers of
external resources
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
ADD RCG
ADD RCWSCFG
ADD MEMCFG
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.
2008-12-02
Configuration Relations
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
CDB resource
group data
CDB data
Media gateway ID
(narrowband)
Media gateway
data
Trunk data
Figure 1.2 shows the relations between the key fields of the data tables during the
configuration of the resource data.
Figure 1.2 Relations between data tables
2008-12-02
Description
SET TTSCON
LST TTSCON
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;
2008-12-02
Command
Description
SET TTSFP
LST TTSSFP
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";
Description
ADD TTSLANG
RMV TTSLANG
MOD TTSLANG
LST TTSLANG
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;
Description
ADD LANGCFG
RMV LANGCFG
MOD LANGCFG
LST LANGCFG
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
Description
ADD TTSASR
MOD TTSASR
RMV TTSASR
LST TTSASR
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;
Description
SET TTSPARA
LST TTSPARA
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;
2008-12-02
Description
SET TTSBGM
LST TTSBGM
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;
Description
SET TTSCFG
LST TTSCFG
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;
Description
SET WSLCS
LST WSLCS
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
Description
Command
ADD MODSRV
ADD SRVATTR
ADD SRVKEY
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
Description
ADD MODSRV
RMV MODSRV
MOD MODSRV
LST MODSRV
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.
Description
ADD SRVATTR
RMV SRVATTR
MOD SRVATTR
LST SRVATTR
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
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:
Descriptio
n
P245
Indicates the
policy for
handling the
file server
faults.
Value
Range
Defau
lt
Value
Remarks
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
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
0-65535
20000
P86
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.
2: 24 K VOX
4: 64 K WAV
8: 32 K VOX
16: A Law
32: Mu Law
Parame
ter No.
Descriptio
n
Value
Range
Defau
lt
Value
Remarks
P227
Indicates the
default voice
recording
format of the
VRB.
P238
2: 24 K VOX
4: 64 K WAV
8: 32 K VOX
16: A Law
32: Mu Law
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
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
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.
Description
SET SECPOLICY
LST SECPOLICY
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.
The following is an example:
SET SECPOLICY: ENABLEPOLICY=TRUE, OPLOCKTIME=5, ADMINLOCKTIME=5, OPONLINE=10;
2008-12-02
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.
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
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
Figure 1.1 General procedure for configuring the UAP8100 MGW data
2008-12-02
Board
Name
Board
Description
Slot Restriction
Working
Mode/Remarks
CMF
Front connect
management unit
1+1 backup
Board
Name
Board
Description
Slot Restriction
Working
Mode/Remarks
CLK
Clock unit
1+1 backup
SPF
Front signaling
processing unit
Load sharing
HRB
High-speed
routing unit
1+1 backup
E8T
Ethernet 8-port
twisted-pair
interface unit
None
OMU
Operation &
maintenance unit
1+1 backup
Main processing
unit
1+1 backup
Network packet
switch unit
1+1 backup
TDM central
switching net unit
1+1 backup
There is no restriction on
front and back insertion.
VPB
Voice processing
unit
2008-12-02
Load sharing
The FVGU is the
private VPU board in
the VIG networking.
Board
Name
Board
Description
Slot Restriction
Working
Mode/Remarks
FLU
1+1 backup
1+1 backup
Load sharing
There is no restriction on
front and back insertion.
T32
Load sharing
S2L
2*155M
SDH/SONET
optical interface
card
Echo cancellation
unit
ECU
There is no restriction on
front and back insertion.
-
2008-12-02
Step
Description
Command
Add a frame.
ADD FRM
Add a board.
ADD BRD
SET TIMESYC
ADD ZONE
BN=0,
BN=1,
BN=0,
BN=1,
Figure 1.2 shows the relations between the key parameters in configuration commands.
2008-12-02
Figure 1.3 Procedure for configuring data for the connection to the MGC
Step
Description
Command
Add an IP address.
ADD IPADDR
MOD IPIF
ADD ROUTE
SET VMGW
ADD MGC
ADD H248LNK
SET H248PARA
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-
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
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.
2008-12-02
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
Configuration Procedure
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
Ste
p
Description
Command
ADD L2UALNK
ADD MTP2LNK
In steps 1 and 2, the protocol type in the configuration commands must be M2UA.
The following is an example:
//Add an M2UA link set.
The SIGTRAN protocol and H.248 protocol between the UAP8100 MGC and UAP8100 MGW can be
borne by the same network cable.
2008-12-02
Command
Description
SET E1PORT
DSP E1PORT
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.
Description
SET S2LPORT
DSP S2LPORT
SET S2LFRM
DSP S2LFRM
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.
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.
Description
ADD TDMIU
RMV TDMIU
LST TDMIU
FN=1,
SN=12,
SPN=0,
EPN=31,
FS=DOUBLE_FRAME,
TXCS=HDB3,
2008-12-02
Command
Description
ADD OFCNAME
RMV OFCNAME
LST OFCNAME
MOD OFCNAME
Description
ADD OFCTKC
RMV OFCTKC
LST OFCTKC
DSP OFCTKC
The following is an example for configuring office name and office number:
ADD
ADD
ADD
ADD
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.
2008-12-02
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.
Description
Command
ADD IPADDR
MOD IPIF
ADD ROUTE
ADD GWADDR
ADD BEARREL
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.
2008-12-02
ADD
ADD
ADD
ADD
ADD
2008-12-02
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.
2008-12-02
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
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.
Description
Command
MOD CLKSRC
MOD CLK
SET LINECLK
The line clock source is set only when you choose to obtain the line clock for the MGW.
The following is an example:
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;
2008-12-02
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.
Document about the loading method of the call hold tone: Tone Producing and Loading
on the MGW
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
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.
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.
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.
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
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.
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
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.
For the list of two-stage dialing tone files, see attachment 6 VP Two-Stage Dialing Voice.
2008-12-02
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.
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.
The system plays the waiting tone to the subscriber.The IPCC system cannot provide the
third feature at present.
2008-12-02
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.
2008-12-02
----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
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:
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.
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
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:
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
[Quidway-Ethernet1/0/0] ip address 100.40.240.1 255.255.0.0
[Quidway-Ethernet1/0/0] quit
# 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
2008-12-02
# 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
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
# 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).
[Quidway-Ethernet0/0/0] ip address 10.10.20.129 255.255.255.0
# 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
[Quidway-Ethernet0/0/0] quit
2008-12-02
# 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.
[Quidway-Ethernet0/0/1] ip address 10.10.10.19 255.255.255.0
# Map the IP address of the softswitch of China Telecom to an IP address in the network
where the UAP8100 is located.
[Quidway-Ethernet0/0/1] ip address 10.10.10.20 255.255.255.0 sub
# Map the IP address of the softswitch of China Netcom to an IP address in the network
where the UAP8100 is located.
[Quidway-Ethernet0/0/1] ip address 10.10.10.21 255.255.255.0 sub
[Quidway-Ethernet0/0/1] quit
# 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.
[Quidway] sbc wellknownport clientaddr 100.100.1.1 sip 5060
# 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.
[Quidway] sbc wellknownport clientaddr 10.10.10.20 sip 5060
# 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.
[Quidway] sbc wellknownport clientaddr 10.10.10.21 sip 5060
# 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
[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.
[Quidway] sbc mapgroup intercom-ip 1002
[Quidway-intercom-ip-1002] clientaddr 10.10.20.129
[Quidway-intercom-ip-1002] serveraddr 10.10.10.20
[Quidway-intercom-ip-1002] softxaddr 10.10.10.22
[Quidway-intercom-ip-1002] media-clientaddr 10.10.20.129
[Quidway-intercom-ip-1002] media-serveraddr 10.10.10.19
[Quidway-intercom-ip-1002] enable
[Quidway-intercom-ip-1002] quit
# Configure the IP route from the NGN bearer network where the UAP8100 is located to
the NGN bearer network of China Netcom.
[Quidway] sbc mapgroup intercom-ip 1003
[Quidway-intercom-ip-1003] clientaddr 10.10.10.21
[Quidway-intercom-ip-1003] serveraddr 100.100.1.1
[Quidway-intercom-ip-1003] softxaddr 100.100.1.10
[Quidway-intercom-ip-1003] media-clientaddr 10.10.10.19
[Quidway-intercom-ip-1003] media-serveraddr 100.100.1.1
[Quidway-intercom-ip-1003] enable
[Quidway-intercom-ip-1003] quit
# Configure the IP route from the NGN bearer network of China Netcom to the NGN
bearer network where the UAP8100 is located.
[Quidway] sbc mapgroup intercom-ip 1004
[Quidway-intercom-ip-1004] clientaddr 100.100.1.1
[Quidway-intercom-ip-1004] serveraddr 10.10.10.21
[Quidway-intercom-ip-1004] softxaddr 10.10.10.22
[Quidway-intercom-ip-1004] media-clientaddr 100.100.1.1
[Quidway-intercom-ip-1004] media-serveraddr 10.10.10.19
[Quidway-intercom-ip-1004] enable
[Quidway-intercom-ip-1004] quit
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
2008-12-02
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
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
UAP8100, the workstation number
of the VP must be consistent with the
resource workstation data in the
UAP8100 configured through ADD
RCWSCFG.
GROUPNO = 0
MGWNO
2008-12-02
Field
Configuratio
n Item
Value
Rang
e
Defaul
t Value
Description and
Configuration Method
ACD
MODULE
132
PROCESS
73, 112
73
Statement
Value
Range
Defau
lt
Value
Description and
Configuration Method
[Station]
MID
132
System
configura
tion
74
2008-12-02
Field
Statement
Value
Range
Defau
lt
Value
Description and
Configuration Method
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
UAP8100, the workstation number
of the FP must be consistent with
the resource workstation data in the
UAP8100 configured through ADD
RCWSCFG.
CardCount = 1
1, 2
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
2008-12-02
Step
Description
Command
ADD RCG
ADD RCWSCFG
ADD MEMCFG
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.
2008-12-02
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.
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.
Fibers, trunk cables, and network cables are deployed according to the engineering
drawing.
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.
2008-12-02
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
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
-----------------------------
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.
2008-12-02
END
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
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 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 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
2008-12-02
Documentation > Application and Software Product Line > Service and Software Public
> UAP&URP > Version Release Document
2008-12-02
such as CCS, CTISERVER, CTILINK, IVR, Aplogic, and MCP are the same as those
specified in the release notes of the ICDV300R004C01B014.
2008-12-02
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.
2008-12-02
Appendix
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
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
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
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,
//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,
//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;
2008-12-02
//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 DNSEG: LP=0, SDN=K'6660000, EDN=K'6660009;
ADD DNSEG: LP=0, SDN=K'99000, EDN=K'99499;
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.
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=FALSE,
CODETYPE=ASN, UCATT=NOEC-0;
2008-12-02
SRC=0,
SN="TO_VRB",
RIP1="192.168.0.4",
RIP1="192.168.0.4",
RIP1="192.168.0.4",
RIP1="192.168.0.2",
//Configure the language information for the current UAP8100. (The engine names for
broadband and narrowband must be set.)
2008-12-02
CNACLD:
CNACLD:
CNACLD:
CNACLD:
CNACLD:
CNACLD:
CNACLD:
ADD
LST
ADD
ADD
//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
2008-12-02
BN=0,
BN=1,
BN=0,
BN=1,
//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";
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";
ADD IPADDR: BT=HRB, BN=0, IFT=ETH, IFN=1, IPADDR="10.51.5.18",
MASK="255.255.255.0", ISBEAR=YES, DSTIP="0.0.0.0";
ADD IPADDR: BT=HRB, BN=0, IFT=ETH, IFN=3, IPADDR="10.51.5.19",
MASK="255.255.255.0", ISBEAR=YES, DSTIP="0.0.0.0";
ADD IPADDR: BT=HRB, BN=0, IFT=ETH, IFN=4, IPADDR="10.51.5.20",
MASK="255.255.255.0", ISBEAR=YES, DSTIP="0.0.0.0";
ADD IPADDR: BT=HRB, BN=0, IFT=ETH, IFN=5, IPADDR="10.51.5.21",
MASK="255.255.255.0", ISBEAR=YES, DSTIP="0.0.0.0";
ADD IPADDR: BT=HRB, BN=0, IFT=ETH, IFN=6, IPADDR="10.51.5.22",
MASK="255.255.255.0", ISBEAR=YES, DSTIP="0.0.0.0";
ADD IPADDR: BT=HRB, BN=0, IFT=ETH, IFN=7, IPADDR="10.51.5.23",
MASK="255.255.255.0", ISBEAR=YES, DSTIP="0.0.0.0";
//Set the interface attributes. All interfaces must work in 100 M duplex mode.
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;
MOD IPIF: IFT=ETH, BT=HRB, BN=0, IFN=1, MTU=1500, ENABLE=YES, DESP="Ethernet
Interface", SPEED=M100, DUPLEX=FULL, AUTH=NONE, TIMEOUT=3, CRCLEN=BITS32,
2008-12-02
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";
VMGWID=0,
MGCIDX=0,
MIDTYPE=IP,
MID="192.168.0.200:2944",
//Set TC parameters. Increase receiving and sending gains to improve the voice quality of
calls.
2008-12-02
//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;
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
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
2008-12-02
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,
//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;
//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 DNSEG: LP=0, SDN=K'880000, EDN=K'880099;
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
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;
ADB MSBR:
CSC=0;
SD=K'880000,
ED=K'880099,
LP=0,
ET=COM,
SEID=K'880000,
RCHS=0,
2008-12-02
ADD RTANA: RSC=0, RSSC=0, RUT=ALL, ADI=ALL, CLR=ALL, TP=ALL, TMX=0, R=0,
ISUP=SIP_F;
ADD RTANA: RSC=2, RSSC=0, RUT=ALL, ADI=ALL, CLR=ALL, TP=ALL, TMX=0, R=2,
ISUP=SIP_F;
CNACLD:
CNACLD:
CNACLD:
CNACLD:
CNACLD:
CNACLD:
CNACLD:
CNACLD:
CNACLD:
CNACLD:
CNACLD:
CNACLD:
ADD
RCWSCFG:
MODULENO=251;
WSNO=5,
INOUT=INSIDE,
GROUPNO=3,
MMN=27,
WSTYPE=MSUF,
2008-12-02
2008-12-02
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