Igateway Bill User Manual

Chapter 1 System Introduction ......................................................................
1-1
1.1 Overview ................................................................................................ 1-1
1.1.1 System Overview ........................................................................... 1-1
1.1.2 Functional Characteristics .............................................................. 1-3
1.2 iGWB Networking ................................................................................... 1-4
1.2.1 Connecting to the Switch ............................................................... 1-5
1.2.2 Connecting to the Billing Center .................................................... 1-7
1.2.3 Connecting to the Browsing Terminal ............................................ 1-8
1.3 Operational Environment........................................................................ 1-8
Chapter 2 Installation Guide ........................................................................... 2-1
2.1 Overview ................................................................................................ 2-1
2.2 Preparations ........................................................................................... 2-1
2.3 Hardware Installation.............................................................................. 2-2
2.4 Operating System Installation ................................................................ 2-2
2.5 Billing Interface Installation..................................................................... 2-3
2.5.1 Overview ........................................................................................ 2-3
2.5.2 Installation of FTP Server .............................................................. 2-3
2.5.3 User Access Right and Parameter Configuration .......................... 2-3
2.5.4 FTAM Installation ........................................................................... 2-10
2.6 iGWB Software Installation and Configuration ....................................... 2-21
2.6.1 iGWB Application Program Software Installation ........................... 2-21
2.6.2 Installation of Java Runtime Environment ...................................... 2-29
2.6.3 iGWB Configuration ....................................................................... 2-33
2.7 Check after Installation ........................................................................... 2-33
Chapter 3 iGWB Configuration and Software Directory Structure ............. 3-1
3.1 Configuration of iGWB ............................................................................ 3-1
3.1.1 Activating iGWB Configuration Tool ............................................... 3-1
3.1.2 Configuring Address ...................................................................... 3-1
3.1.3 Configuring Channels .................................................................... 3-12
3.1.4 Configuring Backup Mode .............................................................. 3-14
3.1.5 Configuring Other Parameters ....................................................... 3-18
3.2 Bill Format Configuration ........................................................................ 3-20
3.2.1 Principle of Bill Classification and Format Conversion ................... 3-20
3.2.2 Bill Format Tool .............................................................................. 3-26
3.3 Default Directory Structure and File List ................................................. 3-38
Chapter 4 iGateway Bill Console Operation .................................................. 4-1
4.1 Start iGWB Console ............................................................................... 4-1
4.1.1 Start iGWB Console ....................................................................... 4-1
4.1.2 Overview Of iGWB Bill Console Functions .................................... 4-8
4.2 User Management .................................................................................. 4-9
4.2.1 Function ......................................................................................... 4-9
4.2.2 Access ........................................................................................... 4-10
4.2.3 Interface description ....................................................................... 4-11
4.3 Bill Browse .............................................................................................. 4-13
4.3.1 Function ......................................................................................... 4-13
4.3.2 Access ........................................................................................... 4-13
4.3.3 Interface Description ...................................................................... 4-14
4.3.4 Operations ..................................................................................... 4-15
4.4 Log Browse ............................................................................................ 4-20
4.4.1 Function ......................................................................................... 4-20
4.4.2 Access ........................................................................................... 4-20
4.4.4 Operations ..................................................................................... 4-21
4.5 Bill Backup .............................................................................................. 4-23
4.6 Bill Query ................................................................................................ 4-23
4.6.1 Function ......................................................................................... 4-23
4.6.2 Access ........................................................................................... 4-23
4.7 Server Status Query ............................................................................... 4-26
4.7.1 Function ......................................................................................... 4-26
4.7.2 Access ........................................................................................... 4-26
4.8 Handling Abnormal Situations ................................................................ 4-27
4.8.1 iGWB Console Cannot be Logged in Normally .............................. 4-27
4.8.2 Dual Server Switchover ................................................................. 4-28
4.8.3 Backup Media Space Insufficient ................................................... 4-29
4.8.4 Backup Media not Existing or Damaged ........................................ 4-29
4.9 Help ........................................................................................................ 4-29
4.9.1 Function ......................................................................................... 4-29
4.9.2 Access ........................................................................................... 4-29
4.10 Log Out ................................................................................................. 4-30
4.10.1 Function ....................................................................................... 4-30
4.10.2 Access ......................................................................................... 4-30
Chapter 5 SmartBackup .................................................................................. 5-1
5.1 Purpose of Bill Backup ........................................................................... 5-1
5.2 Directory Structure and Naming Rules for Bills ...................................... 5-1
5.3 Overview of SmartBackup ...................................................................... 5-2
5.4 Configuration of SmartBackup ............................................................... 5-3
5.4.1 Preparations ................................................................................... 5-3
5.4.2 Configuring SmartBackup .............................................................. 5-4
Chapter 6 iGWB Maintenance ......................................................................... 6-1
6.1 Common Problems and Solutions .......................................................... 6-1
6.1.1 BillRemote NT Server not Activated, Connection Failure .............. 6-1
6.1.2 Incorrect User Name and Password, or Abnormal Operation of
iGWB ....................................................................................................... 6-1
6.1.3 The Number of Users Currently Connected Reaching the Limit .... 6-2
6.1.4 Unknown Fault Occurrence, Operation Failure.............................. 6-2
6.1.5 The Running Authority of Java’s Minor Program Too Low ............ 6-2
6.1.6 Bill Server’s Initial Interface Cannot be Displayed ......................... 6-3
6.1.7 Connection to iGWB Server not Successful .................................. 6-3
6.1.8 Fault Occurs When Starting BillRemote Server ............................. 6-3
6.1.9 After Upgrading, the User End Interface Cannot Display
Normally .................................................................................................. 6-4
6.2 Various Alarms and Processing ............................................................. 6-4
6.2.1 Fault and Event Alarm ................................................................... 6-4
6.2.2 Resource Unavailable .................................................................... 6-11
6.2.3 Backup-related Alarm .................................................................... 6-12
Appendix A Installation of Operating System ............................................... A-1
A.1 Preparations for Installation ................................................................... A-1
A.1.1 Prepare the Installation CD ........................................................... A-1
A.1.2 Check Hardware Configurations of the Server .............................. A-1
A.1.3 Adjust BIOS Setup ......................................................................... A-2
A.2 iGWB Server Hardware Configuration ................................................... A-2
A.3 Operating System Installation ................................................................ A-5
A.3.1 Install Windows 2000 Server ......................................................... A-5
A.3.2 Install Internet Information Service (IIS) ........................................ A-6
A.3.3 Install Windows 2000 Service Pack 3 ............................................ A-6
A.3.4 Install IE5.5 .................................................................................... A-10
A.3.5 Configure Network Adapter IP Address ......................................... A-12
A.3.6 Hard Disk Partition ......................................................................... A-15
Appendix B Bill Backup .................................................................................. B-1
B.1 Purpose .................................................................................................. B-1
B.2 Bill Backup Types .................................................................................. B-1
B.3 Selection of Backup Objects .................................................................. B-2
B.4 Configuration of Relevant Bill Backup Parameters ................................ B-3
B.5 Directory Structure and Naming Rules .................................................. B-3
B.6 Deletion of Outdated Bill Files ................................................................ B-4
B.7 Backup Operation .................................................................................. B-5
B.7.1 Enter the Backup Interface ............................................................ B-5
B.7.2 Automatic Backup Function ........................................................... B-6
B.7.3 Manual Backup .............................................................................. B-9
B.7.4 Backup Media Operation ............................................................... B-11
B.8 Routine Operation Instructions .............................................................. B-13
B.8.1 Automatic Backup .......................................................................... B-13
B.8.2 Manual Backup .............................................................................. B-16
B.8.3 Multiple Backups ........................................................................... B-18
B.8.4 Backup Media Management .......................................................... B-19
Appendix C CMSC60 Bill Format ................................................................... C-1
Appendix D Abbreviations and Acronyms .................................................... D-1

HUAWEI
HUAWEI iGateway Bill

User Manual
V100R002
HUAWEI iGateway Bill
User Manual
Manual Version T2-030106-20040810-C-6.31
Product Version V100R002
BOM 31014106
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support
and service. Please feel free to contact our local office or company headquarters.
Huawei Technologies Co., Ltd.
Address: Administration Building, Huawei Technologies Co., Ltd.,
Bantian, Longgang District, Shenzhen, P. R. China
Postal Code: 518129
Website: http://www.huawei.com
Email: support@huawei.com
Copyright © 2004 Huawei Technologies Co., Ltd.
All Rights Reserved
No part of this manual may be reproduced or transmitted in any form or by any

means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks
, HUAWEI, C&C08, EAST8000, HONET, , ViewPoint, INtess, ETS, DMC,

TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium, M900/M1800,
TELESIGHT, Quidview, Musa, Airbridge, Tellwin, Inmedia, VRP, DOPRA, iTELLIN,
HUAWEI OptiX, C&C08 iNET, NETENGINE, OptiX, iSite, U-SYS, iMUSE, OpenEye,
Lansway, SmartAX, infoX, TopEng are trademarks of Huawei Technologies Co.,
Ltd.
All other trademarks mentioned in this manual are the property of their respective
holders.
Notice
The information in this manual is subject to change without notice. Every effort has
been made in the preparation of this manual to ensure accuracy of the contents, but
all statements, information, and recommendations in this manual do not constitute
the warranty of any kind, express or implied.
About This Manual
Release Notes
This manual applies to HUAWEI M800 CDMA Mobile Switching Center V610R003.
Related Manuals
The set of documentation for HUAWEI M800 CDMA Mobile Switching Center is listed
in the table below.
Manual Contents
HUAWEI M800 CDMA Mobile Switching Describes structure, major contents of manuals and
Center Documentation Guide retrieval methods of package of documents.
HUAWEI M800 CDMA Mobile Switching
Basic information on architecture, features, technical
Center Technical Manual-System
indices, functions and external interface attributes.
Description
Introduction to architecture, functional modules, and the
signal and message flows.
Architecture
Introduction to signaling system structure and
Center Technical Manual-Signaling
explanation of messages.
System

Detailed description on basic functions and their theories,
and briefing on the provision of various services.
Function
HUAWEI M800 CDMA Mobile Switching Introduction to hardware, including cabinets, subracks,
Center Hardware Description Manual boards and cables.
HUAWEI M800 CDMA Mobile Switching Instructions on operation and maintenance at various
Center Operation Manual-Routine terminals and common administrative operations on the
Operation system.
HUAWEI M800 CDMA Mobile Switching Introduction to principles for data configuration, including
Center Operation Manual-Data sequence of data configuration and principles for
Configuration numbering, as well as data configuration commands, and
notes on data configuration.
Introductions to theories, operations, examples and
Center Operation Manual-Performance
common performance measurement tasks.
Measurement
HUAWEI M800 CDMA Mobile Switching Introduction to provision of services other than basic
Center Operation Manual-Feature services, including theories of realization, data
Description configuration, service interworking and service flows.
Manual Contents
Introduction to requirements of routine maintenance and
Center Maintenance Manual-Routine
instructions on routine maintenance.
Maintenance
HUAWEI M800 CDMA Mobile Switching Instructions on replacement procedures of boards,

Center Maintenance Manual-Parts backplanes, terminal system parts replacement and
Replacement notes on replacement.
Instructions on analysis of service provision faults and
Center Maintenance
troubleshooting with the results of such analysis.
Manual-Troubleshooting
Instructions on installation of hardware and methods of
Center Installation Manual-Hardware
verification after installation.
Installation
Instructions on installation of software and remote
Center Installation Manual-Software
maintenance configuration.
Installation
HUAWEI M800 CDMA Mobile Switching Instructions on debugging after successful installation of
Center Installation Manual-System hardware and software, as well as description on initial
Commissioning verification, cutover, upgrading, patch loading, and online
capacity expansion.
HUAWEI iGateway Bill User Manual Introduction to theories, installation, operation,

maintenance and troubleshooting of iGWB.
Organization
This manual describes the principle, installation, operation, maintenance and fault
handling of the iGateway Bill (iGWB), aiming to instruct the users to correctly use the
iGWB. This manual is divided into six chapters and four appendixes as follows:
z Chapter 1 System Introduction. This chapter introduces the functions and
features, software and hardware structure, networking and relevant technical
indices of the iGWB.
z Chapter 2 Installation Guide. This chapter describes the installation and
configuration of the iGWB hardware, iGWB application software and charging
interface software.
z Chapter 3 iGWB Configuration and Software Directory Structure. This
chapter introduces the “Config” tool of the charging gateway, bill format
configuration tool and the directory structure of the system.
z Chapter 4 iGateway Bill Console Operation. This chapter describes the
function and operation of the bill console. The functions of the bill console include:
user management, bill and log browse, bill query and state information query.
z Chapter 5 SmartBackup. The SmartBackup is a backup tool that can be used to
back up bills. Adopting File Transfer Protocol (FTP), it enables the hot backup of
the bills between the active and standby iGWB servers or to the remote WS.
z Chapter 6 iGWB Maintenance. This chapter describes the fault processing in two
parts. The first part is the introduction of common problems and their solutions in
the process of iGWB installation and operation. The second part deals with the
handling methods of common alarms.
z Appendix A Installation of Operating System. This appendix introduces the
installation/configuration of RAID disk array and Windows 2000 Server in the
iGWB server. These parts of installation have been done before the iGWB server
is delivered, the information we provide here is for your reference only.
z Appendix B Bill Backup. In addition to providing SmartBackup tool, the iGWB
application software also supports backing up bills via local hard disk of iGWB
server or external devices. This chapter describes the operation of the second bill
backup method. The bill backup contains automatic backup and manual backup.
z Appendix C CMSC60 Bill Format. This appendix introduces the main
information about bill format of normal bill and metering bill.
z Appendix D Abbreviations and Acronyms
Intended Audience
The manual is intended for the following readers:

z Installation engineers
z Operation & maintenance personnel
z Network administration personnel
Conventions
The manual uses the following conventions:
I. General conventions
Convention Description
Arial Normal paragraphs are in Arial.
Arial Narrow Warnings, Cautions, Notes and Tips are in Arial Narrow.
Boldface Headings are in Boldface.
Courier New Terminal Display is in Courier New.
II. Command conventions
Boldface The keywords of a command line are in Boldface.
italic Command arguments are in italic.
[] Items (keywords or arguments) in square brackets [ ] are optional.
Alternative items are grouped in braces and separated by vertical bars.
{ x | y | ... }
One is selected.
Optional alternative items are grouped in square brackets and separated
[ x | y | ... ]
by vertical bars. One or none is selected.
Alternative items are grouped in braces and separated by vertical bars. A
{ x | y | ... } *
minimum of one or a maximum of all can be selected.
Optional alternative items are grouped in square brackets and separated
[ x | y | ... ] *
by vertical bars. Many or none can be selected.
III. GUI conventions
Button names are inside angle brackets. For example, click the <OK>
<>
button.
Window names, menu items, data table and field names are inside square
[]
brackets. For example, pop up the [New User] window.
Multi-level menus are separated by forward slashes. For example,
/
[File/Create/Folder].
IV. Keyboard operation
Format Description
Press the key with the key name inside angle brackets. For example,
<Key>
<Enter>, <Tab>, <Backspace>, or <A>.
Press the keys concurrently. For example, <Ctrl+Alt+A> means the three
<Key1+Key2>
keys should be pressed concurrently.
Press the keys in turn. For example, <Alt, A> means the two keys should
<Key1, Key2>
be pressed in turn.
V. Mouse operation
Action Description
Click Press the left button or right button quickly (left button by default).
Action Description
Double Click Press the left button twice continuously and quickly.
Drag Press and hold the left button and drag it to a certain position.
VI. Symbols
Eye-catching symbols are also used in the manual to highlight the points worthy of
special attention during the operation. They are defined as follows:
Caution: Means reader be extremely careful during the operation.
Note: Means a complementary description.
Environmental Protection
This product has been designed to comply with the requirements on environmental
protection. For the proper storage, use and disposal of this product, national laws and
regulations must be observed.
User Manual
HUAWEI iGateway Bill Table of Contents
Table of Contents
Chapter 1 System Introduction .................................................................................................... 1-1

1.1 Overview ............................................................................................................................ 1-1
1.1.1 System Overview .................................................................................................... 1-1
1.1.2 Functional Characteristics....................................................................................... 1-3
1.2 iGWB Networking............................................................................................................... 1-4
1.2.1 Connecting to the Switch ........................................................................................ 1-5
1.2.2 Connecting to the Billing Center.............................................................................. 1-7
1.2.3 Connecting to the Browsing Terminal ..................................................................... 1-8
1.3 Operational Environment ................................................................................................... 1-8
Chapter 2 Installation Guide......................................................................................................... 2-1

2.1 Overview ............................................................................................................................ 2-1
2.2 Preparations....................................................................................................................... 2-1
2.3 Hardware Installation ......................................................................................................... 2-2
2.4 Operating System Installation............................................................................................ 2-2
2.5 Billing Interface Installation ................................................................................................ 2-3
2.5.1 Overview ................................................................................................................. 2-3
2.5.2 Installation of FTP Server........................................................................................ 2-3
2.5.3 User Access Right and Parameter Configuration ................................................... 2-3
2.5.4 FTAM Installation .................................................................................................. 2-10
2.6 iGWB Software Installation and Configuration ................................................................ 2-21
2.6.1 iGWB Application Program Software Installation.................................................. 2-21
2.6.2 Installation of Java Runtime Environment............................................................. 2-29
2.6.3 iGWB Configuration .............................................................................................. 2-33
2.7 Check after Installation .................................................................................................... 2-33
Chapter 3 iGWB Configuration and Software Directory Structure........................................... 3-1

3.1 Configuration of iGWB ....................................................................................................... 3-1
3.1.1 Activating iGWB Configuration Tool........................................................................ 3-1
3.1.2 Configuring Address................................................................................................ 3-1
3.1.3 Configuring Channels............................................................................................ 3-12
3.1.4 Configuring Backup Mode..................................................................................... 3-14
3.1.5 Configuring Other Parameters .............................................................................. 3-18
3.2 Bill Format Configuration ................................................................................................. 3-20
3.2.1 Principle of Bill Classification and Format Conversion.......................................... 3-20
3.2.2 Bill Format Tool ..................................................................................................... 3-26
3.3 Default Directory Structure and File List.......................................................................... 3-38
i
User Manual
Chapter 4 iGateway Bill Console Operation ............................................................................... 4-1

4.1 Start iGWB Console........................................................................................................... 4-1
4.1.1 Start iGWB Console ................................................................................................ 4-1
4.1.2 Overview Of iGWB Bill Console Functions ............................................................. 4-8
4.2 User Management ............................................................................................................. 4-9
4.2.1 Function................................................................................................................... 4-9
4.2.2 Access................................................................................................................... 4-10
4.2.3 Interface description.............................................................................................. 4-11
4.3 Bill Browse ....................................................................................................................... 4-13
4.3.1 Function................................................................................................................. 4-13
4.3.2 Access................................................................................................................... 4-13
4.3.3 Interface Description ............................................................................................. 4-14
4.3.4 Operations............................................................................................................. 4-15
4.4 Log Browse ...................................................................................................................... 4-20
4.4.1 Function................................................................................................................. 4-20
4.4.2 Access................................................................................................................... 4-20
4.4.4 Operations............................................................................................................. 4-21
4.5 Bill Backup ....................................................................................................................... 4-23
4.6 Bill Query ......................................................................................................................... 4-23
4.6.1 Function................................................................................................................. 4-23
4.6.2 Access................................................................................................................... 4-23
4.7 Server Status Query ........................................................................................................ 4-26
4.7.1 Function................................................................................................................. 4-26
4.7.2 Access................................................................................................................... 4-26
4.8 Handling Abnormal Situations ......................................................................................... 4-27
4.8.1 iGWB Console Cannot be Logged in Normally..................................................... 4-27
4.8.2 Dual Server Switchover......................................................................................... 4-28
4.8.3 Backup Media Space Insufficient .......................................................................... 4-29
4.8.4 Backup Media not Existing or Damaged............................................................... 4-29
4.9 Help.................................................................................................................................. 4-29
4.9.1 Function................................................................................................................. 4-29
4.9.2 Access................................................................................................................... 4-29
4.10 Log Out .......................................................................................................................... 4-30
4.10.1 Function............................................................................................................... 4-30
4.10.2 Access................................................................................................................. 4-30
Chapter 5 SmartBackup................................................................................................................ 5-1

5.1 Purpose of Bill Backup....................................................................................................... 5-1
5.2 Directory Structure and Naming Rules for Bills ................................................................. 5-1
ii
User Manual
5.3 Overview of SmartBackup ................................................................................................. 5-2

5.4 Configuration of SmartBackup........................................................................................... 5-3
5.4.1 Preparations ............................................................................................................ 5-3
5.4.2 Configuring SmartBackup ....................................................................................... 5-4
Chapter 6 iGWB Maintenance ...................................................................................................... 6-1

6.1 Common Problems and Solutions ..................................................................................... 6-1
6.1.1 BillRemote NT Server not Activated, Connection Failure ....................................... 6-1
6.1.2 Incorrect User Name and Password, or Abnormal Operation of iGWB .................. 6-1
6.1.3 The Number of Users Currently Connected Reaching the Limit............................. 6-2
6.1.4 Unknown Fault Occurrence, Operation Failure....................................................... 6-2
6.1.5 The Running Authority of Java's Minor Program Too Low ..................................... 6-2
6.1.6 Bill Server's Initial Interface Cannot be Displayed .................................................. 6-3
6.1.7 Connection to iGWB Server not Successful ........................................................... 6-3
6.1.8 Fault Occurs When Starting BillRemote Server...................................................... 6-3
6.1.9 After Upgrading, the User End Interface Cannot Display Normally ........................ 6-4
6.2 Various Alarms and Processing......................................................................................... 6-4
6.2.1 Fault and Event Alarm............................................................................................. 6-4
6.2.2 Resource Unavailable ........................................................................................... 6-11
6.2.3 Backup-related Alarm............................................................................................ 6-12
Appendix A Installation of Operating System ............................................................................A-1

A.1 Preparations for Installation...............................................................................................A-1
A.1.1 Prepare the Installation CD.....................................................................................A-1
A.1.2 Check Hardware Configurations of the Server .......................................................A-1
A.1.3 Adjust BIOS Setup ..................................................................................................A-2
A.2 iGWB Server Hardware Configuration ..............................................................................A-2
A.3 Operating System Installation ...........................................................................................A-5
A.3.1 Install Windows 2000 Server ..................................................................................A-5
A.3.2 Install Internet Information Service (IIS) .................................................................A-6
A.3.3 Install Windows 2000 Service Pack 3.....................................................................A-6
A.3.4 Install IE5.5 ...........................................................................................................A-10
A.3.5 Configure Network Adapter IP Address................................................................A-12
A.3.6 Hard Disk Partition ................................................................................................A-15
Appendix B Bill Backup................................................................................................................B-1

B.1 Purpose .............................................................................................................................B-1
B.2 Bill Backup Types ..............................................................................................................B-1
B.3 Selection of Backup Objects .............................................................................................B-2
B.4 Configuration of Relevant Bill Backup Parameters ...........................................................B-3
B.5 Directory Structure and Naming Rules..............................................................................B-3
B.6 Deletion of Outdated Bill Files ...........................................................................................B-4
B.7 Backup Operation..............................................................................................................B-5
B.7.1 Enter the Backup Interface .....................................................................................B-5
iii
User Manual
B.7.2 Automatic Backup Function ....................................................................................B-6

B.7.3 Manual Backup .......................................................................................................B-9
B.7.4 Backup Media Operation ......................................................................................B-11
B.8 Routine Operation Instructions........................................................................................B-13
B.8.1 Automatic Backup.................................................................................................B-13
B.8.2 Manual Backup .....................................................................................................B-16
B.8.3 Multiple Backups...................................................................................................B-18
B.8.4 Backup Media Management .................................................................................B-19
Appendix C CMSC60 Bill Format .................................................................................................C-1
Appendix D Abbreviations and Acronyms .................................................................................D-1
iv
User Manual
HUAWEI iGateway Bill Chapter 1 System Introduction
Chapter 1 System Introduction
1.1 Overview
1.1.1 System Overview
iGateway Bill is a gateway device placed between switch and billing center for
caching and pre-handling bills.
The iGWB is composed of server and client. The server comprises two servers
installed with Windows 2000 and the client a PC installed with Windows 98/2000. In
normal condition, only the active server receives bills, the standby one is in
monitoring state. When hardware or software fault occurs to the active server, the
standby one automatically or manually starts to receive and store bills. The client
requires an IE browser (IE5.5 or later versions) with a Java runtime environment. It
can also be installed together with the server.
Both the iGWB active and standby server have four network cards connecting
respectively to the active and standby GSPC boards of Mobile Switching Center
(MSC)/Local Switching Center (LSC), Billing Center and the iGWB client. The position
of the iGWB in the network is shown in Figure 1-1.
1-1
User Manual
MSC/LSC
A S A S A S
GSPC GSPC ... GSPC WAN
DDN / E1
S
IP Router
A
Cascading
LAN Switch0 Link2 LAN Switch1
IP Router
Link0 Link1 Link3
Heartbeat path LAN Switch

COM
Active Standby
iGWB server iGWB server
LAN Switch R
Bill collector NMS server Bill service

R
console
Bill service
console
Equipment room Billing center/NMS center
A: Active S: Standby
Figure 1-1 Position of the iGWB in the network
Note:
Heartbeat is a term referring to the signal sent by one server to another indicating the server is in normal
operation. The iGWB keeps the normal state between the active and standby servers via heartbeat.
Heartbeat signal requires no response and it is sent between the active and standby servers regularly. It
is sent via network cables or serial port cables.
The MSC communicates with iGWB directly through GSPC board. One MSC may
have multiple Service Processing Module (SPM) and for each SPM there are two
GSPC boards working in active-standby mode. The bills of SPMs are transferred to
iGWB via GSPC boards.
To conform to the bill transfer protocol between iGWB and MSC, the following should
be noted:
z The GSPC board does not decide whether the bills are transferred via the active
GSPC board or the standby GSPC board. It is decided by a process in the
GSPC boards according to the link state between GSPC boards and iGWB.
1-2
User Manual
z When the communication between the active GSPC board and the iGWB active
server is normal, and bills are transferred from the active GSPC board to the
iGWB active server, select Link0. When Link 0 is disconnected, select Link 1 for
bill transfer. When both Link 0 and Link 1 are disconnected, select Link 2 for bill
transfer. Select Link 3 in case the above are all disconnected. That is, when
transferring bills, the iGWB active server is preferable. The standby server is
selected only when the active server is abnormal. (Note: Link 0 and Link 1 refer
respectively to the communication link between the active GSPC boards and the
second network adapter of the active iGWB server, and that between the
standby GSPC boards and the third network adapter of the active iGWB server.
Whilst Link 2 and Link 3 refer respectively to that between the active GSPC
boards and the second network adapter of the standby server, and that between
the standby GSPC boards and the third network adapter of the standby server,
as shown in Figure 1-1.)
iGWB software adopts multiple processes structure of high reliability. The interference
among the processes is minimal. Each process performs different functions and is
well independent of each other. The iGWB software is composed of server software,
maintenance tools and iGWB bill console. The iGWB software structure is shown in
Figure 1-2.
iGWB
Monitoring process Bill format setting program
Server parameter
configuration program
Bill server working process
Debugging message
view program
Web server process
Bill data
Bill console
FTP/FTAM server process

Billing Center
FTP client process
Figure 1-2 iGWB software structure
1.1.2 Functional Characteristics
The functions of the iGWB are as follows:

z Receiving bills from the MSC switch using self-defined interface protocol.
z Sorting bills on demand and classifying the bills into different categories. Bills in
different categories can be processed differently.
1-3
User Manual
z Providing FTP or FTAM interface for the Billing Center.

z Providing automatic or manual bill data backup.
The characteristics of the iGWB are as follows:
z Strong processing capacity: the iGWB processing capacity is as high as 1,600
bills/second.
z High reliability: the iGWB is in dual server configuration, and can ensure that no
bills will be repeated or lost even in abnormal conditions due to the application of
advanced software scenario.
z The sorting function facilitates the processing of the Billing Center: The bills are
sorted into different categories and stored under different directories. The Billing
Center can make different processing according to the bills of different
categories. The sorting conditions can be set.
z Multiple convenient bill backup modes guarantee data security.
1.2 iGWB Networking
The bill collectors in the Billing Center are located in the Billing Center. The iGWB and
the Billing Center are connected via LAN (near-end connection) or WAN (far-end
connection). The iGWB networking is shown in Figure 1-3.
The iGWB also interfaces with the billing center, which concerns networking with the
switch, the billing center, negotiating file transfer protocol and commissioning of
the collected bills.
1-4
User Manual
Bill collector
MSC1
Browsing
Active iGWB Standby iGWB terminal
Server Server
HUB
IP Router
DDN, X.25, 64k
MSC2
Active iGWB Standby iGWB IP Router

Server Server
HUB
Browsing
terminal
Figure 1-3 Connection of the iGWB and the Billing Center
1.2.1 Connecting to the Switch
When the iGWB and the GSPC communicate via the network, the iGWB acts as the
server (the port number is 9900), and the GSPC acts as the client.
Among the four network adapters congfigured for each iGWB, network adapters 2
and 3 are used for communication with the GSPC boards. Specifically, network
adapter 2 of the active/standby iGWB server is used for communication with the
active GSPC boards, and network adapter 3 is used for communication with the
standby GSPC boards.
Since the iGWB is the server of the GSPC board, to connect the iGWB with the
GSPC board after startup, the GSPC board should be informed of the IP address and
monitoring port number of the iGWB. This is achieved by configuring parameters on
the corresponding MSC data management console.
The detailed procedures are as follows:

1) Log on to the Network Management System (such as the iManager M2000) as a
super user.
1-5
User Manual
2) Start the MML client under the corresponding MSC/LSC icon; or directly start
MSC operation console and select MML client in the navigation tree.
3) Select "Add charging IP address configuration information" to configure GSPC
board and iGWB IP address, as shown in the example in Figure 1-4.
Figure 1-4 Configuration table
Input the module number, as shown in Figure 1-5. The module number must exist in
the corresponding SPM description table.
Figure 1-5 SPM configuration table
The active bill server IP address 1 should not be null. The active bill server IP
addresses 1 and 2 are the IP addresses of the second and the third network adapters
of the active server respectively. The standby bill server IP addresses 1 and 2 are the
IP addresses of the second and the third network adapters of the standby server. For
correct configuration, enter corresponding bill server IP address in the configuration
table shown in Figure 1-5.
The rule to assign IP address of the bill server connecting to the switch is as follows:
z The second network adapters of the active and the standby bill servers should
connect to the active GSPC board on the switch. Their network segment should
be the one the active GSPC board connects to.
z The third network adapters of the active and the standby bill servers should
connect to the standby GSPC board. Its network segment must be the one the
standby GSPC board connects to.
For the configuration of the bill server network adapter IP address, refer to "3 iGWB
Configuration and Software Directory Structure".
1-6
User Manual
1.2.2 Connecting to the Billing Center
The iGWB provides a 100M Ethernet port, which can connect with the billing center
via either LAN or WAN through routers.
The activities between the iGWB and the bill collector are actually bill file transfer and
deletion operations. At present the file transfer protocols supported by the iGWB are
FTP and FTAM. It is recommended that the FTP protocol be used.
z When the FTP is used between the iGWB and the Billing Center, the iGWB
serves as the Server of the FTP.
z When the FTAM is used between the iGWB and the Billing Center, the iGWB
serves as the Responder of the FTAM.
In the seven-layer OSI reference model, the FTAM is located on the application layer.
The bottom protocol stacks supported are:
z UTS-TCP stack (FTAM over TCP/IP)
z UTS-LAN stack (FTAM over IEEE802.3)
I. Parameter configuration
1) Configure the network adapter connecting with the bill collector

The gateway of the network adapter (the fourth network adapter) for communication
between the active/standby servers and the bill collector needs to be configured. The
IP address connecting to the Billing Center must be within the network segment of the
Billing Center.
Note:
If the iGWB is connected to the billing center through WAN, its IP address does not have to be in the
same network section as that of the billing center. The router will decide the proper routing. Such rules
apply to the similar circumstances under which the IP addresses are required to be in the same section
in the following chapters.
2) FTAM software installation

If the FTAM protocol is used between the iGWB and the bill collector, the FTAM
software should be installed in the iGWB. Please refer to 2.4.4 and 2.4.5 of
Installation Guide for the detailed installation procedures and parameter configuration.
3) FTP parameter setting
When installing Windows Operating System, you can select to install FTP. The FTP
parameter setting is simple, for you need only to configure FTP users and the
1-7
User Manual
directory FTP opens to the Billing Center. Please refer to “User Access Right and
Parameter Configuration" in Section 2.4.3 for details.
II. User authority setting
For data security purpose, correct Windows user name and password must be
provided when the billing center fetches the bill file from the iGWB by FTP or FTAM.
Please refer to “User Access Right and Parameter Configuration" in Section 2.4.3 for
details of setting user name, password, and access authority.
1.2.3 Connecting to the Browsing Terminal
The first network adapter of the iGWB is for connection with the bill console. The
corresponding network adapter configuration adopts virtual IP technology.
In this case, the basic IP (the first IP address of the physical network adapter),
extended IP (the second IP address of the network adapter) and subnet mask
(generally 255.255.0.0) must be configured. The basic IP is used as the heartbeat
path between the active and the standby iGWB servers.
The extended IP is used as the occupying IP of the virtual IP address of the bill
console). The virtual IP and the browsing client IP are in the same network segment.
Refer to "3 iGWB Configuration and Software Directory Structure" for details.
1.3 Operational Environment
For the operational environment of the iGWB bill console and the server, refer to
Table 1-1.
Table 1-1 Operational environment of the iGWB bill console and the server
iGWB bill console Server

Dual DELL server/ IBM server/ other
PC P4 1.6GHz CPU/128 MB
Hardware platform type of server with equivalent
memory/20GB hard disk or higher
performance
Windows 2000 Server( Windows 2000

Service Pack3 or later patch)
Software platform Windows operating system or
Windows NT Server 4.0( Windows NT
Service Pack6a or later patch)
Power
300 W 1,200 W
consumption
Normal: 15°C ~ 35°C
Temperature
Safe: 0°C ~ 45°C
1-8
User Manual
iGWB bill console Server

Normal: 30% ~ 65%
Relative humidity
Safe: 10% ~ 90%
1-9
User Manual
HUAWEI iGateway Bill Chapter 2 Installation Guide
Chapter 2 Installation Guide
2.1 Overview
This chapter introduces the installation and configuration of the iGWB hardware,
billing interface software, and iGWB application software.
Note:
Before delivery, the iGWB server has been configured with RAID and installed with Windows 2000
Server. The user can skip this part and proceed to the software installation of iGWB applications and
charging interface. The installation of Windows 2000 Server and the configuration of RAID are detailed
in Appendix A "Installation of Operating System".
2.2 Preparations
Preparations for the installation:

1) Tools
A flat screwdriver, a cross screwdriver
2) Check the hardware configuration of the server
The iGWB adopts dual server configuration with local RAID. It may adopt two Dell or
other servers with equivalent performance.
Note:
The installation procedures in this section are mainly related to DELL2650 series server. You can see
this section for the installation of other types of servers.
The basic hardware configuration of the server is as follows (See the inventory for
specific server type selected and configuration):
The basic hardware configuration of each iGWB server is

z CPU: 1* Intel Xeon 2.4 GHz or higher CPU
2-1
User Manual
z Hard disk: 2 (or 5)* 36.4 GB hard disks

z Memory: 512 MB
z Network adapter: Four network adapters. Two of them are the integrated network
adapter on main board. The rest are Intel Fast Ethernet LAN Controllers.
z RAID: 1* PERC 3/Di.
z CD-ROM: 1* CD/DVD-ROM
z Floppy Drive: 1* 3.5’’ floppy drive
Before installing the operating system, check whether the basic hardware
configuration of the server has been completed (mainly if the number of network
adapters and hard disks meets the requirement of basic configuration). This
configuration directly influences the following software installation.
Note:
The network adapter type can differ from the types listed above. If there is any change of the network
adapter type, the supplier will provide corresponding drivers. Therefore, install the operating system
flexibly.
3) Check necessary installation software

z Windows 2000 Server
z Windows 2000 Service Pack3 or higher version
z FTAM installation software (optional)
z iGWB installation software (including Java Runtime Environment)
2.3 Hardware Installation
During actual assembly, install the iGWB dual server system in the IMM (Integrated
Management Module) standard cabinet. For the detailed installation of this cabinet,
see HUAWEI M800 CDMA Large-capacity Mobile Switching Center Installation
Manual-Hardware Installation.
2.4 Operating System Installation
The RAID disk array and Windows 2000 Server operating system must be installed
before the delivery of charging gateway server. Thus, the user is no need to re-install
them. For the specific procedure, see Appendix A "Installation of Operating System".
2-2
User Manual
2.5 Billing Interface Installation
2.5.1 Overview
The iGWB supports two kinds of online billing interface: FTP and FTAM. The FTP
server software has already been installed during the installation of Windows 2000, so
it is unnecessary to install it again. If you adopt the FTP interface, you must configure
the FTP server. If you adopt FTAM interface, you must install and configure the FTAM
software.
Generally, when you adopt the FTP as the interface, the iGWB serves as the Server
and the billing center serves as the Client. When you adopt the FTAM as the interface,
the iGWB serves as the Responder and the Billing Center serves as the Initiator.
2.5.2 Installation of FTP Server
The installer of Windows 200 provides the FTP Server as a part of the operating
system. The FTP has been installed with IIS. For its installation procedures see
Appendix A "Installation of Operating System".
2.5.3 User Access Right and Parameter Configuration
The Billing Center must use the correct user name and password when fetching bills
from iGWB via the FTP or FTAM. Therefore, the iGWB needs to set Windows user
name and password for the Billing Center. Moreover, open the relevant directory of bill
files for the Billing Center to obtain the bill files
I. Setting user access right
The section describes how to set access permissions for the Billing Center to access
iGWB.
1) Select the [Start/Programs/Administrative Tools /Computer management] menu
to run the computer management program, in the [Computer Management]
interface, select [Computer Management (Local) /System Tools/Local Users and
Groups/Users], as shown in Figure 2-1.
2-3
User Manual
Figure 2-1 Computer management interface
2) Select "Users" and click [Action/New User] to create a new user and a password
for the Billing Center to log into iGWB. Figure 2-2 shows the pop-up dialogue
box.
Figure 2-2 Input interface for new user
3) Input the user name, password and confirm password. Tick "Password never
expires". Avoid ticking "User must change password at next login" and "Account
is disabled". "User cannot change password" is optional. Then, click <Create>.
2-4
User Manual
4) Exit.
II. Configuring FTP(FTAM) parameter
This section introduces the parameter configuration of FTP charging interface. For the
parameter configuration of FTAM charging interface, see the related contents in
section 2.5.4 "FTAM Installation"
1) Run [Start/Programs/Administrative Tools/Internet Services Manager]. The
[Internet Information Services] interface pops up, as shown in Figure 2-3.
Figure 2-3 Interface of Internet Information Services
2) Select "Default FTP Site", and then click [Action/Properties]. The interface
[Default FTP Site Properties] appears, as shown in Figure 2-4.
2-5
User Manual
Figure 2-4 Interface of Default FTP Site Properties
3) Tick "Allow Anonymous Connections" only in [Security Accounts]. Avoid ticking

"Allow only anonymous connections" and "Allow IIS to control password". The
other parameters remain unchanged. Then click <OK>.
4) In Figure 2-3, select "Default FTP Site" in the [Internet Information Services]
interface and click [Action/New/Virtual Directory]. Then [Virtual Directory Creation
Wizard] pops up , as shown in Figure 2-5.
2-6
User Manual
Figure 2-5 Initial interface of Virtual Directory Creation Wizard
5) Click <Next>in Figure 2-5, and then the following interface will pop up, prompting
you to input the alias of virtual directory.
Figure 2-6 [Virtual Directory Creation Wizard]_Virtual Directory Alias
2-7
User Manual
6) Input the alias of virtual directory in Figure 2-6, and then click <Next>. The
following interface appears, requiring to input the actual hard disk path for FTP
open directory, as shown in Figure 2-7.
Figure 2-7 [Virtual Directory Creation Wizard]_FTP Site Content Directory
7) Input the actual path of FTP directory opened to the Billing Center in Figure 2-7,
and then click <Next>. The interface pops up, as shown in Figure 2-8. It is
required to set the access permissions for the FTP open directory.
2-8
User Manual
Figure 2-8 [Virtual Directory Creation Wizard] _Access Permissions
8) Tick both "Read" and "Write", as shown in Figure 2-8, and then click <Next>. The
interface as shown in Figure 2-9 pops up. Click <Finish> to complete the creation
of virtual directory.
Figure 2-9 [Virtual Directory Creation Wizard]_Finish
2-9
User Manual
9) Create and set the other FTP open directories according to the previous
procedures. For example, in Figure 2-10, ch1 and ch2 under Default FTP Site
are the FTP open directories created via the procedures stated previously.
Figure 2-10 Created open FTP directory
2.5.4 FTAM Installation
The FTAM protocol used in the iGWB adopts the UTS-FTAM 7.2 developed by
VERTERL. It contains the software of protocol stack and application layer. The stack
protocol software is UTS-NetLink 5.2 and the application layer one is UTS-FTAM 7.2.
I. Applying for license
The UTS-NetLink 5.2 and UTS-FTAM 7.2 software are independent installation disks
that require independent Licenses respectively. The License is bound with the
physical address of network adapter ((MAC address). Since it takes you 24 hours to
obtain the License, please make preparations in advance.
1) Execute the C:\>ipconfig /all command on the active and standby iGWB servers
respectively to obtain the MAC addresses of network adapters that connect the
active/standby iGWB server to the Billing Center.
2) Send the MAC address (for the dual server system, both computers must apply
for Licenses) to license@vertel.com or tekview@sh163b.sta.net.cn via E-mail.
Then you can obtain the licenses about 24 hours later.
For contents of the e-mail, see the following template.
Dear Sir,
2-10
User Manual
I'm an engineer working in Huawei Technologies Co., Ltd. I have just purchased two
sets of software of UTS-NetLink 5.2 and UTS-FTAM 7.3. Would you like to send the
correlated licenses to me? Here is my hostid:
hostid-1: 00-02-55-C7-54-C5
hostid-2: 00-02-55-C7-54-C6
Thank you!
Caution:
Never send two or more hostids of one server to the supplier. That means you would like to purchase
two or more Licenses for one server.
3) You can receive the License through e-mail. Sample of License sent by Vertel is
as follows.
SERVER snaylm 00065B24A878
VENDOR vertellm
INCREMENT UTSftam vertellm 1.9999 30-jul-2002 4 F3A2A3EB13BA ck=129 \
SN=200003150434
INCREMENT UTS-TCP vertellm 5.9999 30-jul-2002 uncounted C51951682126 \
HOSTID=00065B24A878 ck=129 SN=200003150434
INCREMENT UTS-LAN vertellm 5.9999 30-jul-2002 uncounted 807A7126DB50 \
HOSTID=00065B24A878 ck=129 SN=200003150434
The first four lines are License of UTS_FTAM and the latter four are that of
UTS_NetLink. Replace the server name snaylm in the License of UTS_FTAM with
the host name. The usage of the Licenses is detailed in the installation procedures
later.
II. Installing UTS-NetLink5.2
1) Insert the installation disk of UTS-NetLink5.2 and double click the Setup.exe file.
2) When the installation wizard of the installer is ready, the [Welcome] interface will
pop up.
3) Click <Next>, and the [Software License Agreement] dialogue box appears.
2-11
User Manual
4) Click <Yes>, and the [Choose Destination Location] dialogue box appears,
prompting the user to select destination directory of the program, as shown in
Figure 2-11.
Figure 2-11 Choose destination Location
5) Click <Browse> to select the installation directory. The default installation

directory given in the installer is recommended. Then, click <Next>.
6) There pops up the [Select Program Folder] dialogue box, prompting the user to
input the folder name of the program. Use the default folder name given in the
installer directly, and then click <Next>.
7) The [Start Copying Files] dialogue box appears, prompting that the file copying is
started.
8) Click <Next> to start copying the files.
9) After the file copying is completed, the [UTS-NetLink Configuration] dialogue box
appears, as shown in Figure 2-12.
2-12
User Manual
Figure 2-12 UTS netlink configuration
10) Click <Next> and the [Configuration Applet] dialogue box pops up, as shown in
Figure 2-13.
2-13
User Manual
Figure 2-13 Vertel UTS-netlink 5.2 (Jun 20 2001) - configuration applet
11) Configure parameters such as NSAP for the current network adapter. The
default parameters are recommended.
12) After the installation is completed, select [Start/Setting/Control Panel]. Then
double click "Vertel UTS-NetLink" to modify or view the configuration. Click
<OK>, the [Network Configuration] dialogue box appears, as shown in Figure
2-14.
2-14
User Manual
Figure 2-14 Network configuration
13) Click <Next>, the installer will start configuring the network components. After
that, the [Setup Complete] dialogue box pops up.
14) In the [Setup Complete] dialogue box, select "No, I will restart my computer later",
and then click <Finish>.
15) Copy and save the License of UTS_NetLink to the file C:\Program Files\Vertel
UTS-NetLink\etc\license.dat and exit. Thus, the installation of UTS-NetLink 5.2 is
completed.
III. Installing UTS-FTAM7.2
1) Insert the installation disk of UTS-FTAM7.2 and double click Setup.exe.

2) When the installation wizard of the installer is ready, the [InstallShield Wizard]
dialogue box will pop up, querying if UTS_FTAM 7.2 should be installed.
3) Click <Next > to install UTS_FTAM. Then, the [InstallShield Wizard] dialogue box
pops up, prompting the user to select the destination directory of the program.
4) Click <Next> to select the default installation directory. The [InstallShield Wizard]
dialogue box pops up, prompting the user to select the installation type.
5) The program offers three installation types: Typical, Compact and Custom.
Select <Typical> and click <Next>.
6) The [InstallShield Wizard] dialogue box appears, prompting the user to input the
folder name of the program. Use the default folder name given in the program
and click <Next>.
2-15
User Manual
7) The information of the current installation will be displayed in [InstallShiled

Wizard]. Check if the current installation information is correct. If so, click <Next>
to start copying files.
8) When the files have been copied, the [Install Services] dialogue box displays the
directory of the services installed, as shown in Figure 2-15.
Figure 2-15 Install services
9) Click <OK> to use the default directory. The [InstallShield Wizard] dialogue box
will pop up, querying whether to restart the computer.
10) Select "No, I will restart my computer later", and click <Finish> to complete the
installation.
11) Create the license.dat file under the directory of C:\UTS_FTAM\Flexlm\. Copy
the License of UTS_FTAM7.2 and save it to the license.dat file and exit.
12) Restart the computer. Thus, complete the software installation.
IV. Verfiying the installation of UTS_FTAM 7.2
1) After installing the UTS_FTAM and restart the computer, click the
[Start/Programs/Administrative Tools/Services] menu to observe if the following
three services can be started normally.
z UTS Provisioning Service
z Vertel FTAM Server
z Vertel Lock Manager
If any service is not started, it indicates unsuccessful installation. Please re-install the
program according to the installation procedures. If the three services can be started
normally, proceed to the next step.
2-16
User Manual
2) Click the [Start/Programs/UTS-NetLink/Command Line Utilities] menu to open a

window of command lines. Input strxt to execute the Responder test program.
Then press <Enter>, the window of command lines displays:
C:\Program Files\Vertel UTS-NetLink\bin>strxt
STRXT 5.3.0.2 - (C) Copyright Vertel 1989-2002. All rights reserved.
Waiting for a connection...
Click the [Start/Programs/UTS-NetLink/Command Line Utilities] menu again to open a

new window of command lines, Input sttxt to execute the initiator test program . Then,
press <Enter>, and the window of command lines displays:
C:\Program Files\Vertel UTS-NetLink\bin>sttxt
STTXT 5.3.0.2 - (C) Copyright Vertel 1989-2002. All rights reserved.
Resolved IP address (hex): 0A0BF249
Establishing 1 connection(s) using CLASS 0 NS TYPE RFC1006.
-> Connection 1 established.
A few seconds later, display the following lines:
TX: Con 1: Size 32512 SDUs 5823 bytes 189317376 in 10 secs: 18488.03 Kb/sec
TX: Accumulated throughput after 0:00:10
TX: Total SDU 5823 Last duration: 18488.03 Kb/sec Overall: 18488.03 Kb/sec
TX: Con 1: Size 32512 SDUs 6161 bytes 200310528 in 10 secs: 19561.58 Kb/sec
TX: Accumulated throughput after 0:00:20
TX: Total SDU 11984 Last duration: 19561.58 Kb/sec Overall: 19024.80 Kb/sec
The above contents indicate the successful UTS-NetLink installation. Press <Ctrl+C>
to terminate the test programs and close the two windows of command lines. If the
Responder and initiator test programs are not interconnected, the License of
UTS-NetLink may be set unsuccessfully. Please set the License file properly
according to the installation procedures. Then, restart the computer.
3) Create an aetable.txt file. Configure the standby iGWB server (igwb2) as
Responder and the active iGWB server (igwb1) as the Initiator. Open the
aetable.txt file of igwb1 in the directory of C:\UTS_FTAM\cfg\ and perform the
configuration as follows:
igwb2tcp {1 3 9999 1 7} 1 /0a0bf9cc/0200/0201/0202 2 0
igwb2lan {1 3 9999 1 7} 1 /47000100065B24A8781D/0200/0201/0202 0 4
2-17
User Manual
The boldface 0a0bf9cc in the first line above is the hexadecimal IP address of igwb2
and the boldface 47000100065B24A8781D in the second line above is the NSAP of
igwb2. After completing the configuration, save it and exit.
4) Click [Start/Run] to open the [Run] dialogue box. Input cmd, and then press
<OK> to open the window of command lines. Input cd uts_ftam\bin and press
<Return> to confirm. Input the command fls -p igwb2tcp!c:\ and press <OK>.
The window of command lines displays the following contents:
C:\UTS_FTAM\bin>fls -p igwb2tcp!c:\
Enter initiator ID for filestore igwb2tcp: administrator (Note: Input a user name
here)
Enter password: (Note: Input a password here)
AUTOEXEC.BAT Multimedia Files/ VRV.LST ftam/
BillSvr/ My Installations/ VRV2k.LST iGWB_Client/
CONFIG.SYS NOTWORM VRVKB.EXE lint/
Config.Msi/ NTDETECT.COM WINNT/ lotus/
Dell/ Program Files/ an_bkup/ notes/
IO.SYS RECYCLER/ billdebug.txt ntldr
InetPub/ REPORT.LOG billprotocol.txt pagefile.sys
KAV/ TEMP/ boot.ini state.dat
KRECYCLE/ Test/ bootfont.bin unzipped/
MSDOS.SYS UTS_FTAM/ debugwslog.txt vrv2000/
44 File(s)
The above contents show that the UTS_FTAM7.2 software with TCP (Transmission
Control Protocol) can run normally.
5) Input the command fls -p igwb2lan!c:\ in the window of command lines, and
then press <Enter>. The window displays:
C:\UTS_FTAM\bin>fls -p igwb2lan!c:\
Enter initiator ID for filestore igwb2lan: administrator (Note: Input a user name here)
Enter password: (Note: Input a password here)
AUTOEXEC.BAT Multimedia Files/ VRV.LST ftam/
BillSvr/ My Installations/ VRV2k.LST iGWB_Client/
CONFIG.SYS NOTWORM VRVKB.EXE lint/
2-18
User Manual
Config.Msi/ NTDETECT.COM WINNT/ lotus/
Dell/ Program Files/ an_bkup/ notes/
IO.SYS RECYCLER/ billdebug.txt ntldr
InetPub/ REPORT.LOG billprotocol.txt pagefile.sys
KAV/ TEMP/ boot.ini state.dat
KRECYCLE/ Test/ bootfont.bin unzipped/
MSDOS.SYS UTS_FTAM/ debugwslog.txt vrv2000/
44 File (s)
The above contents show that the UTS_FTAM7.2 software with LAN protocol stack
can run normally.
6) The verification is completed, indicating successful software installation.
V. Parameter configuration
Initiator end must be configured with some information of Responder end to be

accessed.
Configuring C:\UTS_FTAM\cfg\aetable.txt file:
AE_NAME AP_TITLE AE_QUAL /NETWORKADDRESS/TSAP/SSAP/PSAP NS TC
=================================================================
filestore {1 3 9999 1 7 } 1 /49010000E840B32001/0200/0201/0202 04
Agent {1 3 9999 1 7} 0 /49010000E840B32001/2121/2222/3333 04
ANON {1 3 9999 1 7} 0 /49010000E840B32001/2121/2222/3333 04
The fields are described as follows:
AE_NAME: The application entity name defined by the user (39 characters in
maximum)
AP_TITLE: The identifier of application process
Example: { 1 3 9999 1 ftam-nil-ap-title (7) }
AE_QUALIFIER: identifying one application entity together with AP_TITLE
NETWORK ADDRESS: Namely NSAP, network service access point (the logic
identifier of network layer service)
TSAP: transport layer service access point (the logic identifier of transport layer
service)
2-19
User Manual
SSAP: session layer service access point (the logic identifier of session layer)
PSAP: presentation layer service access point (the logic identifier of presentation
layer service)
NS: network layer service mode (optional)
Connectionless-oriented mode = 0 (default)
Connection-oriented mode = 1
TCP/IP mode for lower layer = 2
TC: Transport class of transport layer (optional)
class zero = 0 (default)
class one = 1
class two = 2
class three = 3
class four = 4
Generally, the default values are as follows:
In OSI-LAN, NS = 0, TC = 4
In OSI-WAN, NS = 1, TC = 0
In OSI-TCP, NS = 2, TC = 0
VI. Common commands of UTS-FTAM 7.2
Example:
Copy a file: fcp -p filestore!c:\c12345 d:\d12345
Delete a file: frm -p filestore!c:\c12345
Remove a file: fmv -p filestore!c:\c12345 d:\d12345
List a directory: fls -p filestore!c:\
Note: To view the detailed meaning of command parameters, please run the
command name directly without adding any parameter.
VII. Cautions for UTS-FTAM7.2
1) Vertel UTS-NetLink 5.2 does not support DHCP to obtain IP address

automatically. Otherwise the UTS Provision Services can not be activated.
2) FTAM7.2 does not support the machine name with delimiter "-".
2-20
User Manual
2.6 iGWB Software Installation and Configuration
2.6.1 iGWB Application Program Software Installation
Run the "Setup.exe" file in the installation disk1 of the iGWB to start the iGWB
software installation process. The window as shown in Figure 2-16 will pop up.
Figure 2-16 "Welcome" interface
Click <Next> to display the [Software License Agreement] interface, as shown in

Figure 2-17.
2-21
User Manual
Figure 2-17 Software license agreement
Click <Yes>, and display the interface as shown in Figure 2-18 o show the user
information.
Figure 2-18 "User information" window
2-22
User Manual
Enter the [user information] window, and click <Next>, an interface for selecting the
program folder will pop up, as shown in Figure 2-19.
Figure 2-19 Select program folder
Click <Next> to display the interface as shown in Figure 2-20.
2-23
User Manual
Figure 2-20 "Choose destination location" window
In the above window, if you want to change the destination folder of the iGWB
program, click <Browse>, and then choose the appropriate installation directory
according to actual requirements. Then click <Next> to display the interface as shown
in Figure 2-21.
2-24
User Manual
Figure 2-21 Choose destination location for original bills
In the above interface, if you want to change the path of the original bills, click
<Browse> to select an appropriate directory according to the actual requirements.
Then select <Next> to display the interface as shown in Figure 2-22.
2-25
User Manual
Figure 2-22 Choose destination location for final bills
In the above interface, if you want to change the path of the final bills, click <Browse>,
and select an appropriate directory according to the actual requirements. Then click
<Next> to display the interface as shown in Figure 2-23.
2-26
User Manual
Figure 2-23 Choose destination location
In the above interface, if you want to change the installation path of the iGWB console
(no change is preferable), click <Browse> and select an appropriate directory
according to the actual requirements. Then click <Next> to display the interface as
shown in Figure 2-24.
2-27
User Manual
Figure 2-24 Before starting copying files
Click <Next> to display the interface as shown in Figure 2-25.
Figure 2-25 Copy files
In the above interface, upon the completion of file copying, the interface as shown in
Figure 2-26 will pop up.
2-28
User Manual
Figure 2-26 Setup complete
In the above interface, click <Finish> to finish the installation of the iGWB software.
2.6.2 Installation of Java Runtime Environment
After installing the iGWB application software, search "JRE12.exe" under the directory
"\Inetpub\wwwroot\plugin". Double click to run this program and start to install the
Java runtime environment, as shown in Figure 2-27.
2-29
User Manual
Based on the installation program prompt, agree the Software License Agreement
and enter the interface as shown in Figure 2-28 to set the installation path.
Figure 2-28 Set the path
2-30
User Manual
Based on the installation program prompt, select the installation path and enter the
interface as shown in Figure 2-29 to select browsers.
Figure 2-29 Select Browsers
Tick the "Microsoft Internet Explorer" in Figure 2-29, click <Next> to start the
software installation process. A progress bar appears, as shown in Figure 2-30.
Figure 2-30 Copying file process
After the completion of the file copying, restart the computer to complete the
installation of JAVA runtime environment.
After installing the Java runtime environment, you need to install the JAVA patch . Run
the file JREPatch.exe to complete the automatic installation of JAVA patch.
After installing the iGWB software, set the startup mode of the [Process Watch Dog
Service] in the iGWB as [Manual] for secure parameter configuration of iGWB
software and SmartBackup backup tool. The Process Watch Dog Service is used to
monitor the iGWB server program. If the iGWB server program is not running, the
Process Watch Dog Service will attempt to run the program again and again.
2-31
User Manual
Open the [Start/Programs/Administrative Tools/Services] menu as shown in the

following figure.
Figure 2-31 Dialogue box of Services
In the above figure, select [Process Watch Dog Service] and double click to display
the interface as shown in Figure 2-32.
Figure 2-32 Setting service startup type
2-32
User Manual
In the above figure, select the Startup Type to be "Manual", and then click <OK>.
When completing the iGWB configuration, set the service to be "Automatic" before the
formal operation of iGWB.
After installing the iGWB software, check whether there is

"C:\inetpub\wwwroot\invoker.exe". If there is not, it is impossible to start up the
BillRemote service. Hence the bill console cannot connect the iGWB.
2.6.3 iGWB Configuration
After installing the iGWB software, configure relevant parameters to ensure the
normal operation of iGWB. In addition, if adopt the SmartBackup tool to backup bills,
configure relevant parameters for the tool in advance. For the details, see Chapter 3
"iGWB Configuration and Software Directory Structure".
2.7 Check after Installation
The following is the description of the programs for the iGWB software running.
If the directory is "C:\billsvr" during the installation of iGWB, the operating program of
iGWB is saved under the directory "C:\billsvr\bin". The commonly used programs
include:
1) Kernel.exe
General control module: Start and monitor all the other modules and initialize other
resources. Start this program when starting the iGWB program.
Note:
If "kernel" is used to start the iGWB instead of the PWD (process watch dog) in on-site upgrade, the
PWD can not restart iGWB when iGWB is abnormal. Therefore, when the active and standby server can
operate normally, kill the active and standby iGWB through KillKernel, and then start the PWD by directly
setting it to be automatic. That is, start the iGWB through the PWD. In this way the PWD can monitor the
operation of iGWB. When the iGWB is abnormal, restart it.
2) Msgserver.exe
Debug the output window of printing message, as shown in Figure 2-33.
2-33
User Manual
Digit
Figure 2-33 Debugging print output window
3) Killkernel.exe
Killkernel.exe is a program for exiting the iGWB program. When the iGWB is running,
you can use this program to exit the iGWB program normally.
4) Config.exe
The iGWB quick configuration tool, used to configure some commonly used and
compulsory parameters for the iGWB running.
5) BillFormt.exe
Tool for bill conversion configuration, it is used to flexibly configure the format
conversion of bills.
6) ShowIcon.exe
A program used to request the iGWB to display the small icons for indication purpose.
When the iGWB software is automatically started by the PWD after Windows is
started, the small indication icon in the lower right cannot appear. The user may run
this command to display the small icon.
I. Check whether the program can run normally
When configure the iGWB parameters correctly and run the iGWB normally, a small
icon will appear in the tool bar (with the shape of a bulb), as shown in Figure 2-34.
Figure 2-34 Normal running indication of the application program
When the program is activated, it can receive and store bill data of the active iGWB
server., The small icon is as shown in Figure 2-35.
2-34
User Manual
Figure 2-35 Indication of the application program activated
Note:
Due to the internal realization reasons, the small icon will be lit after one minute or longer.
When the small icon is not normally displayed after the program is run, run the
program "C:\billsvr\bin\showicon.exe" to display it.
II. Check whether the heartbeat of dual servers is normal
The dual servers use two heartbeat paths by default: serial port 1 and network
adapter 1. Observe the output print message of the program (run the program
"C:\billsvr\bin\msgserver.exe"), there cannot be the print message "HandShake
timeout, Link1 is broken" (the message indicates heartbeat link 1, namely the network
adapter heartbeat path is broken).
Make sure that the two heartbeats are normal, that is, no fault message displayed like
the words in red in Figure 2-36.
Digit
Figure 2-36 Check the heartbeat path of the dual servers
III. Check whether the switchover of the dual servers is normal
Note:
Strictly follow the procedures below to test it.
1) Test whether the active server can take over the task of the standby server
normally
2-35
User Manual
z Shut down the active server first, start the standby server, and run the iGWB
software in the standby server. Then wait for the standby server to be activated.
z After the standby server is activated, start the originally active server and run the
iGWB software in it to see if it can be activated normally.
z If the originally active server can be activated normally, the test is passed.
Otherwise, check whether the configuration parameters of the originally active
server are correct.
2) Check whether the standby server can take over the task of the active server
normally.
z Shut down the standby server first, start the active server, and run the iGWB
software in the active server. Then wait for the active server to be activated.
z After the active server is activated, start the standby server and run the iGWB
software in the standby server.
z Stop the PWD service on the active server. Run Killkernel.exe of the active
server so that the active server can exit the Kernel program.
z Check whether the standby server is activated in five minutes. If the standby
server can be activated normally, it passes the test. Otherwise, check whether
the configuration parameters of the standby server are correct.
IV. Check whether the bill console can log on to the server normally
When the server is activated, access "IP->OMC" (IP->OMC indicates the IP address
on the iGWB connecting to the bill console) with IE at the console. Check whether the
console can log on to the server normally (user name: admin, password: sa).
Note:
Start the BillRemote service first when browsing the bill and querying the server status in the bill console.
The setting procedure of BillRemote service startup is the same as that of PWD Service. Please see
2.5.2 for details. For example, the setting procedure in Windows 2000 server is as follows:
Click [Start/Programs/Administrative Tools/Services], find "BillRemote Service”, and select menu
[Action/Start] to start the service.
V. Check whether the connection between the iGWB and the switch is normal
As shown in the following figure, observe the print message of the program (run the
program "C:\billsvr\bin\msgserver.exe"). The message "Local Primary links is 3,
Secondary links is 1" indicates the connection number between this server and the
active GSPC board is 3, while that between this server and the standby GSPC board
is 1. The message "Peer Primary links is 3, Secondary links is 1" indicates the
2-36
User Manual
connection number between the other server and the active GSPC board is 3, while
that between that server and the standby GSPC board is 1, as shown in Figure 2-37.
Digit
Figure 2-37 Connection of the iGWB to the switch
VI. Check whether bills are normally received and saved
If the switch already sends bills to the iGWB, you may check whether the bills are
received and saved normally with the following method (the configuration is based on
the default data).
For example, today is May 3rd, 2001, check whether bill files exist under the directory
"D:\BillFront\data\20010503". The sizes of all the bill files except the last one should
be 3000k. If the bill files meet the conditions described above, it indicates that the bill
files have already been received and saved normally.
If the bill files are not received and saved normally, check it by the following
procedures:
1) Check whether the bill length set in the iGWB is the same as that sent by the
host. If not, correct it.
2) Check whether the connection between the iGWB and the host is normal. If not,
remove corresponding network faults.
3) Check whether the hard disk used to save status files and bill data is normal. If
not, remove the corresponding hard disk faults.
VII. Check relevant parameters of iGWB configuration
The configuration program divides all the configuration items into several categories:
address, path, backup, and others. Select a proper category from the left and the right
will display the corresponding configuration item list. Revise the values of the
configuration items in this list. During the revision, brief explanations of the currently
selected configuration items will be displayed in the descriptive bar in the lower part of
the list. After the revision, save the configurations with the "Save to registry table"
short-cut button or the "Save to registry table" option in the [Operation] menu. For the
detailed configuration method, see Chapter 3, "iGWB Configuration and Software
Directory Structure".
2-37
User Manual
HUAWEI iGateway Bill Chapter 3 iGWB Configuration and Software Directory Structure
Chapter 3 iGWB Configuration and Software

Directory Structure
After the iGWB installation is finished, you must carry out data configuration using
iGWB configuration tool. The data to be configured include address, channels,
backup, and other related data.
The backup is detailed in Chapter 5, SmartBackup—Bill Backup.
3.1 Configuration of iGWB
3.1.1 Activating iGWB Configuration Tool
To activate the iGWB configuration tool, you can:

z Select [Start/Programs/CDMA iGateway Bill/iGateway Bill Config Tool].
z Run the file "C: \BillSvr\bin\config.exe".
All the configuration objects are displayed.
Note:
After data configuration, click the shortcut icon or select the menu [Action/Save to Registry] to
save the result.
3.1.2 Configuring Address
To configure address, do as follows:

1) Set network adapters.
2) Allocate IP addresses to network adapters.
3) Configure address parameters.
I. Setting Network Adapters
iGWB provides four network adapters. Two are built in the main board and the other
two are external adapters. The interfaces of these physical network adapters are
exposed at the back of the host.
3-1
User Manual
The properties of the four network adapters in "My Network Places" are shown as:
z Broadcom NetXtreme Gigabit Ethernet Adapter - Onboard - Link A
z Broadcom NetXtreme Gigabit Ethernet Adapter - Onboard - Link B
z Intel Fast Ethernet LAN Controller - PCI Slot 1
z Intel Fast Ethernet LAN Controller - PCI Slot 2
The former two are built-in network adapters, and the latter two are plug-in network
adapters.
Name the above four network adapters "Network adapter 1", "Network adapter 2",
"Network adapter 3" and "Network adapter 4" in turn.
II. Allocating IP Address
The assignment of the four network adapters are as follows:

z Network adapter 1 connects to the NMS client
z Network adapter 2 connects to the active GSPC.
z Network adapter 3 connects to the standby GSPC.
z Network adapter 4 connects to the Billing Center.
To allocate IP addresses to those network adapters, do as follows:
1) Check the correspondence between the network adapter interfaces and local
connections.
z Right-click "My Network Places" and select [Properties].
Icons of the four adapters are displayed in the [Properties] window.
z Unplug the cable to disconnect the four network interfaces from the network.
A red X is displayed on the icon of each network adapter.
z Connect a network interface with the network using a network cable.
If the red X on the icon of corresponding adapter disappears, the
correspondence between the network interface and the adapter is correct.
2) Bind the network adapters.
z Right click "My Network Places", select [Properties] and click <Advanced>.
z In the [Advanced Settings] dialog box displayed, select [Adapters and
Bindings], as shown in Figure 3-1.
3-2
User Manual
Figure 3-1 Adjust binding sequence of network adapter
z Check the connections.

The connection sequence of local adapters should be:
z Adapter 1
z Adapter 2
z Adapter 3
z Adapter 4
If the actual connection differs from the above sequence, adjust the network adapter
as follows:
1) Select the adapter to be adjusted under [Connections].
2) Click the Up/Down key to move it to the correct place.
3) Press <OK>.
III. Configuring IP Address Parameters
You should configure the following data:

z The IP address for the connection between the iGWB and the MSC
z Heartbeat local address
3-3
User Manual
z Heartbeat remote address

z Connect bill console virtual address (the virtual IP address used for connecting to
the bill console)
Figure 3-2 shows the data to be configured.
Figure 3-2 iGWB configuration tool
Table 3-1 describes the address parameters shown in Figure 3-2.
Table 3-1 Description of address parameter configuration interface
Name Description Remarks

Enter the IP address of the second network
Active address Used to connect the active GSPC adapter on the server: IP12 (on server 1) and
IP22 (on server 2).
Enter in the IP address of the third network
Standby Used to connect the standby
adapter on the server: IP13 (on server 1) and
address GSPC
IP23 (on server 2).
Heartbeat local Used to specify the heartbeat path Enter IP111 for server 1 and IP211 for server 2,
address of the local iGWB server as shown in Figure 3-3.
Heartbeat Used to specify the heartbeat path Enter IP211 for server 1 and IP111 for server 2,
remote address of the remote iGWB server as shown in Figure 3-3.
3-4
User Manual
Name Description Remarks

Parameters related to the virtual
address used to connect the bill
console.
The parameters include:
z Original IP address: If the
operating system is Windows Original IP address: If the operating system is
NT, it is the extended IP Windows NT, enter IP112 for server 1 and
address, which forms the IP212 for server 2. If the operating system is
virtual IP. If the operating Windows 2000, enter IP111 for server1 and
Connect bill IP211 for server 2, and do not configure IP112
system is Windows 2000
console virtual and IP212.
Server, it is the IP address of
address
the network adapter
Virtual IP address: Virtual IP address used for
connecting with the Client,
connecting the bill console.
since extended IP is not used
in the technology of forming Virtual IP mask: Enter 255.255.0.0 here.
virtual IP.
z Virtual IP address: The virtual
IP formed.
z Virtual IP mask: The mask of
the virtual IP address formed.
The iGWB adopts virtual IP technology, that is, the active node is assigned with IP
addresses (as shown in Figure 3-3). The clients access the server by the virtual IP
(public IP address). The clients do to distinguish the active server from the standby
server. When the active server is active, the clients are connected to the primary
server by virtual IP. When the standby server is active, the clients are connected to
the standby server.
Active server Standby server
IP111 IP211
IP112 IP12 IP13 IP14 IP22 IP23 IP24
IP212
1 2 3 4 1 2 3 4
Virtual IP address for
connecting to the client
Client
Figure 3-3 Virtual IP addresses
The functions of all the IP addresses are as follows:
3-5
User Manual
z Virtual IP for client connection: IP address used to connect the client. It is

dynamically possessed by the activated nodes.
z IP111 and IP211: The first IP address of the network adapter 1 on the active and
the standby servers. They serve as the heartbeat path of the dual-server.
z IP112 and IP212: The second IP address of the network adapter 1 on the active
server and the standby servers (also named as "extended IP"). They are used as
the occupying IP addresses for the virtual IP open to the client, and will be
replaced once the server node is activated. In Windows 2000 Server operating
system, you need not configure those two IP addresses. In such case, the iGWB
application takes the virtual IP connecting with the client as the second IP
address of the network adapter 1 of the activate server node.
z IP12 and IP22: The IP addresses of the network adapter 2 on the active and the
standby servers. They are used to connect all the active GSPCs.
z IP13 and IP23: The IP addresses of the network adapter 3 on the active and the
standby servers. They are used to connect all the standby GSPCs.
z IP14 and IP24: IP addresses of the network adapter 4 on the active and the
standby servers. They are used to connect with the Billing Center.
Note:
z IP111, IP211, Virtual IP for client connection, IP12, IP22, IP13, IP23, IP14, and IP24 must be
assigned by the operator according to actual deployment.
z The virtual IP for client connection must be in the OMC segment.
z IP14 and IP24 must be in the Billing Center segment.
z IP12 and IP22 must be in the same segment as the active GSPC.
z IP13 and IP23 must be in the same segment as the standby GSPC.
Follow the rules below when assigning network adapter IP addresses:

z The address format is "S.X.Y.Z".
z S can be any value, for example, "129". Ensure that the addresses are not
conflict with each other.
z X stands for the network adapter number. It is "1" for network adapter 1, "2" for
network adapter 2, and alike.
z Y stands for the server number. It is "1" for the active server and "2" for the
standby server.
z Z stands for the address number. It is "1" for the first address and "2" for the
second address (extended IP).
z The IP masks of all the network adapters are the same, that is, 255.255.0.0.
3-6
User Manual
Note:
If the four network adapters of the server are in the same network segment, some network adapter IP
addresses may be invalid. In the above rules, X stands for network adapter number. It ensures that the
four network adapters are in different network segments.
Configure the IP addresses as follows:

1) Configure the network adapter 1 as below:
z Active server:
IP111: 129.1.1.1, subnet mask: 255.255.0.0
IP112: 129.1.1.2, subnet mask: 255.255.0.0

z Standby server:
IP211: 129.1.2.1, subnet mask: 255.255.0.0
IP212: 129.1.2.2, subnet mask: 255.255.0.0
The IP addresses 129.1.1.1 and 129.1.2.1 serve as the heartbeat IP address between
the dual servers. The IP addresses 129.1.1.2 and 129.1.2.2 serve as the occupying
IP address of the virtual IP for client connection.
z Active server:
IP12: 129.2.1.1, subnet mask: 255.255.0.0
z Standby server:
IP22: 129.2.2.1, subnet mask: 255.255.0.0
The IP addresses 129.2.1.1 and 129.2.2.1 are used for the communication between
the iGWB and the active GSPCs.
z Active server:
IP13: 129.3.1.1, subnet mask: 255.255.0.0
z Standby server:
IP23: 129.3.2.1, subnet mask: 255.255.0.0
the iGWB and the standby GSPCs.
z Active server:
IP14: 129.4.1.1, subnet mask: 255.255.0.0
z Standby server:
3-7
User Manual
IP24: 129.4.2.1, subnet mask: 255.255.0.0
the iGWB and the Billing Center.
Note:
z Make sure that the network adapter 1 is in the first place. The method of adjusting binding sequence
of network adapter is introduced previously. The reason is as follows.
z The bill console is developed by Java. The communication route between the bill console and the
iGWB is:
z bill console->BillRemote service at the iGWB server->OMM process at the iGWB server.
z The bill console visits the server via the IP address of the iGWB "Virtual IP for client connection", and
the BillRemote service at the iGWB server listens for the connection request from the bill console on
the first IP address of the first network adapter of the server. If network adapter 1 is not in the first
place, BillRemote will not be able to get the connection request from the bill console on the first IP
address of the first network adapter. Accordingly, when the bill console uses the IP address of
network adapter 1 "Virtual IP for client connection" to connect to the server, bill console will not be
able to establish the connection with the server.
The iGWB adopts virtual IP technology for the "connect to bill console virtual IP". The
adapter connecting to the client (i.e. bill console) in IE browsing mode also serves as
the heartbeat path for the dual servers.
Three IP addresses are involved in planning a virtual IP address:

z The actual IP address of the network adapter
z The extended IP address
z The virtual IP address.
Therefore, to assign a virtual IP address for two servers, five IP addresses are
needed:
z IP11 and IP12: Actual IP addresses of the network adapters
z IP21 and IP22: Extended IP addresses
z Virtual IP
Taking the IP address of "connecting bill console" as an example, the network
adapters of "connecting bill console" are the first network adapters of server 1 and
server 2. Among them, IP111 and IP211 are the first IP addresses of the first network
adapters of server 1 and server 2. IP112 and IP212 are the second IP addresses of
the network adapters (extended IP), acting as the IP of position occupying.
To configure multiple IP addresses for one network adapter (suppose the IP address
of the network adapter 1 is 129.1.1.1), do as follows:
3-8
User Manual
5) Click [Control Panel/Network/Protocol/TCP/IP], select the [Attribute] tab, and

click <Advanced>.
6) In the [Advanced IP Addressing] dialog box displayed, click <Add>, enter the IP
addresses and related subnet masks, and click <OK>. See Figure 3-4.
Figure 3-4 Configure multiple IP addresses
In the above figure, 129.1.1.1 is the actual IP address. The IP address 129.1.1.2 is
the extended IP address. "Extended IP address" has no actual meaning and can be
configured freely. It is used to realize virtual IP technology.
Figure 3-5 shows the IP addresses of the iGWB.
3-9
User Manual
Active server Standby server
129.1.1.1 129.2.1.1 129.3.1.1 129.4.1.1 129.1.2.1 129.2.2.1 129.3.2.1 129.4.2.1

129.1.1.2 129.1.2.2
Virtual IP: 129.1.1.3
Client
Figure 3-5 Configure the virtual IP address
Note:
If Windows 2000 Server operating system is adopted, the IP addresses "129.1.1.2" and "129.1.2.2" will
not exist in the above figure.
[Example]
To configure iGWB network adapter IP addresses using the iGateway Bill Config tool,
do as follows:
1) Select [Start/Programs/CDMA iGateway Bill/iGateway Bill Config Tool] or run
"c:\billsvr\bin\config.exe".
2) Configure the IP addresses of the active server as Figure 3-6.
3-10
User Manual
Figure 3-6 Configuring IP address parameters of the active server
Note:
If Windows 2000 Server operating system is adopted, the IP address of the network adapter connecting
with the client should be configured, that is, set it to 129.1.1.1.
3) Configure the IP addresses of the active server as Figure 3-7.
3-11
User Manual
Figure 3-7 Configuring IP address parameters of the standby server
Note:
For Windows 2000 Server operating system, the IP address of the network adapter connecting with the
client should be configured, that is, set it to 129.1.2.1.
3.1.3 Configuring Channels
To configure channels, do as follows:

1) In the [iGateway Bill Config Tool] window, click [Channels].
The parameters to be configured are displayed, as shown in Figure 3-8.
3-12
User Manual
Figure 3-8 Channel parameter configuration
2) Configure the channels.

The channels comprise of Ch_1, Ch_2, and so forth if bills are to be distributed as
normal bills and metering bills.
You can configure the file size, file generation time, file name format, and backup path
independently. You can use default values or assign value according to actual
requirements.
The file name is in the format "prefix + file serial number.suffix". Table 3-2 describes
parameters related to channels.
Note:
The name of the Self-defined bill file can not contain characters such as "^" and ";"; otherwise irregular
line feed will occur when browsing logs and bills at the bill console.
Table 3-2 Description of channel configuration parameters
Domain Description
Description Description of the channel configured. This parameter is read-only.
3-13
User Manual
Domain Description
Specifies the size of the final bill file generated in the channel with k as its unit. If
File size the current bill file size is greater than the specified size, a new bill file will be
generated.
Specifies the generation time of the bill file in the channel in seconds. Within this
File generation time duration, even if the current bill file is not beyond the specified size, a new bill file
will still be generated.
Specifies the file name format of the final bill as "prefix + file serial number.
suffix" and each part can be configured independently. Click the "+" in the left of
File name format the configuration item, all the sub-configuration items can be displayed.
Note: self-defined bill file name cannot contain characters such as "^" and ";".
Specifies the prefix of the file name. It can be ordinary character strings, which
can include the following special character strings:
%Y-- year in four digits
Prefix %M-- month in two digits

%D-- date in two digits
%C-- channel number in two digits
The prefix can be null.
Specifies the width of the file serial number and the default value is 8. In order to
Digital width
avoid the repetition of the file serial number, value less than 8 is not suggested.
Extension Specifies the extension name of the file. The default name is DAT.
Specifies the backup destination path of the bill data in the channel. With the
button at the right of the configuration item, you can select a path. If multiple
backups are required, you can enter multiple paths, but should separate the
paths with ",".
Backup destination
path Note: If SmartBackup is adopted, this parameter will be invalid and can be null.
See chapter 5 for details about SmartBackup. This parameter is used in another
backup mode supported by the system, in which the bills are backed up to the
local hard disk of iGWB server (or other backup media on the server). This
backup mode is elaborated in Appendix B.
3.1.4 Configuring Backup Mode
Note:
z The SmartBackup tool provided by the iGWB software is recommended for bill backup. For details of
SmartBackup tool, see Chapter 5 SmartBackup.
z iGWB also allows bills to be backed up to the local hard disk of iGWB server or other backup media
on the server. For more information, see Appendix B Bill Backup.
3-14
User Manual
To use SmartBackup tool to back up bills, configure the backup parameters as

follows.
1) In the [iGateway Bill Config Tool] window, click "Backup".
The data configuration of the relevant bill backups are displayed, as shown in
Figure 3-9.
2) Set the Backup mode of both the original bills and final bills to "Manual", as
shown in Figure 3-9, and Figure 3-10.
Figure 3-9 Setting backup mode of original bilsl
3-15
User Manual
Figure 3-10 Setting backup mode of final bills
Note:
z When SmartBackup tool is used to back up bills and the "Backup mode" is set to "Manual", most of
the backup parameters in the configuration tool of iGateway Bill will be invalid.
z The backup parameters in [iGateway Bill Config Tool] are used in another bill backup mode, in which
the bills are backed up to the local hard disk of iGWB server or other backup media on the server.
Backup parameters include the backup parameters of the original bills, the final bills
and the status files. For detailed description, see Table 3-3 (Take the backup
parameters of original bills as main examples).
Table 3-3 Backup parameter description
Domain Meaning
Original bill backup
Specifies the original bill backup parameters.
parameters
3-16
User Manual
Domain Meaning
Specifies the backup mode of the original bills, including automatic, semi
-automatic and manual.
The automatic mode enables automatic startup and termination of backup at
specified time every day, automatic searching for the files without backup and
automatic saving of the backup progress information.
The semi-automatic mode also enables automatic searching for the files
Backup mode without backup and automatic saving of backup progress information, but it
requires manual startup and termination of backup.
The manual backup requires manual startup and termination of backup, and
requires specifying the files to be backed up.
Note: The "automatic" and "semi-automatic" modes are invalid to the
SmartBackup tool. They are only valid to the other backup method, which is
elaborated in Appendix B Bill Backup.
Specifies the storage days of the original bills in the iGWB, and the bill files
beyond the storage days will be deleted by the backup module.
Bill storage days
Note: This parameter is valid to both SmartBackup and the other backup
method, which is elaborated in Appendix B Bill Backup.
Specifies the automatic startup time of the backup. The start hour, minute and
Start time second can be configured independently. At present, it can be configured to
minute level.
Specifies the automatic end time of the backup. The end hour, minute, and
End time second can be configured independently. At present, it can be configured to
minute level.
Specifies the backup path of the original bills. If multiple backups are
Target destination
required, you can enter multiple paths with "," in between.
This is a combined configuration item, which also includes the final bill backup
Final bill backup
parameters. Click the "+" at the left of the configuration item, and all the
parameters
sub-configuration items can be displayed.
This is a combined configuration item, which also includes the status file
backup parameters. Click the "+" at the left of the configuration item, and all
Status file backup the sub-configuration items can be displayed.
parameters
Note: If SmartBackup tool is adopted, this parameter will be invalid and
should be null. It is only valid to the backup method elaborated in Appendix B.
There are three backup modes: automatic, semi-automatic and manual. In automatic
mode, the server backs up the original bills into specified "Target destination" when it
is the specified "Start time" and stops the transaction automatically when it is the
specified "End time". In semi-automatic mode, the bill backup is started manually (at
the bill console) and the server automatically stops backup when backup is complete
or you can stop the backup of bills manually in the backup process. In manual mode,
the original bills are backed up manually.
3-17
User Manual
In the automatic backup mode, only the bills that have been automatically backed up
(including automatic and semi-automatic backup) and are beyond the bill storage
days can be deleted, i.e. those bills that are beyond the storage days but have not
been backed up yet will not be deleted. In the manual backup mode, bills that are
kept beyond the bill storage days will be deleted. Hence bills should be backed up in
time when adopting manual backup mode.
Note:
The SmartBackup tool only backs up final bills. To use SmartBackup tool, you must set the "Backup
mode" to be "manual" first to disable the other backup method supported by the iGWB.
3) Restart the iGWB to validate the data configured.
3.1.5 Configuring Other Parameters
After configuring IP address, channels, and backup mode, you need specify the billing
interface, that is, whether FTP or FTAM serves as the billing interface. This parameter
is invalid when FTP is used to send bills.
To configure the billing interface, do as follows:

1) In the [[iGateway Bill Config Tool] window, click "Miscellaneous". See Figure
3-11.
Note:
The "Node ID" of the active and standby servers must be set correctly, otherwise iGWB may run
abnormally.
3-18
User Manual
Figure 3-11 Billing interface configuration
2) Set the billing center interface, and then click the (Save to Registry) or
select the menu [Action/Save to Registry] to save the configuration.

You can execute "config.exe" to configure or view the parameters required for the
iGWB operation. The original configuration parameters can be put in the configuration
tool from the Registry, or the configuration information modified in the configuration
tool can be saved to the Registry. You can save all the configuration parameters in
file .CFG.
Note:
The iGWB Config Tool (config.exe) is used to modify configuration only. The data configuration are
saved in the Registry. The iGWB software does not allow the modification of settings such as bill file
directory, after server configuration is completed and server is in operation. Since the iGWB program
only reads configuration information upon startup, you must restart the iGWB program if configuration is
modified.
3-19
User Manual
3.2 Bill Format Configuration
3.2.1 Principle of Bill Classification and Format Conversion
The iGWB provides functions such as bill classification and format conversion.
Figure 3-12 shows the bill processing flow.
Original Bill
Classification Format Conversion
Final Bill
Figure 3-12 Bill processing flow
The bill processing is parameter-drived. That is, once you set the parameters, the bill
processing will be performed according to the parameters specified.
The bill format is classified into two types: bill of plane structure and bill of ASN.1
coding structure.
The length of the bill of plane structure is fixed and the meaning of each byte (bit) is
clearly defined.
The ASN.1 structure is "tree structure" on the whole. The length of the bill of ASN.1
structure is not fixed, and some of the fields have the attribute of "validity". Only when
the "validity" attribute is real, the corresponding field is available.
At present the bill format base of the version V100 can only process the classification
and conversion of the bills of plane structure, and is used to define the structure of
various bill formats needed.
Since the positions, types, and lengths of the bill fields of the plane structure are fixed,
the bill structure can be described in a table, as shown in Table 3-4.
Table 3-4 Bill Structure
Field Name Field Type Field Length Bit field or not Enum or not
Field1 char 4 0 0
3-20
User Manual
Field Name Field Type Field Length Bit field or not Enum or not
Field2 short 1 0 0
Field3 long 1 0 0
Field4 BCD 10 0 0
Field5 char 4 1 0
Field6 char 4 1 0
Field7 char 1 0 1
Field8 char 4 1 1
Field9 char 4 1 1
In the above table, each line defines clearly the type and length of one field in the bill.
If it is stipulated that the sequence to define the fields in the table is the same as that
of the corresponding fields in the bill, the positions of the fields are also fixed. The bill
structure in the above bivariate table is defined as source format, and the original
format described in Table 3-4 is name "Source".
According to the definition in this table, you can divide an original bill into several
single fields. With the value of each field, you can reorganize these fields or
reorganize them after format conversion to obtain "final bill".
To reorganize these, define a format to be obtained, namely destination format, as

shown in Table 3-5.
Table 3-5 Destination Format
Bit field or Source Format

Field Name Field Type Field Length Enum or not
not Name
Dest1 char 1 0 1 Field7
Dest2 BCD 10 0 0 Field4
Dest3 long 1 0 0 Field3
Dest4 short 1 0 0 Field2
Dest5 char 4 0 0 Field1
The destination format described in Table 3-5 is named "Dest".
According to the above target format definition, you can organize the fields and obtain
bill with 5 fields:
z The first field comes from the seventh field of Source
z The second field comes from the fourth field of Source
3-21
User Manual
z The third field comes from the third field of Source

z The fourth field comes from the second field of Source
z The fifth field comes from the first field of Source
"Field name" defines the field included in the final bill, and "source format name" is
the reference of the original bill field, indicating that the value of a certain field in the
final bill comes from a certain field in the original bill.
The final bill is obtained by reorganizing some of the fields to form the format
expected on the basis of classifying the origin bills. The field format is not changed at
all. In fact, format change is required, and the library of the iGWB performs format
conversion by using conversion expression. For example, if using Text (Field7,
DIV_TIP, FILL_BLANK, LEFT) expression to replace Field 7 field in "Source Format
Name", the field Dest1 in the final bill obtained is a text character string. This is the
principle of bill format conversion.
"Source Format" is used to represent the bill format to be converted, and "Destination
Format" to represent the bill format expected. Figure 3-13 shows the relation between
"Source Format" and "Destination Format".
Conversion Expression
Source Format Destination Format
Sort the original bill into single field Combine the original bill field again
Figure 3-13 Relation between "Source Format" and "Target Format"
Since the iGWB needs to perform format conversion according to the charging
requirement from the Billing Center and the requirement of bill browsing, the formats
used in the library include the following mated formats: conversion source format and
conversion destination format; browse source format and browse destination format
(including front viewing and back viewing).
Conversion source format divides the original bill into some fields, while conversion
target format reorganizes the fields in the original bill to obtain the final bill format.
The source format of front viewing divides the original bill into some fields according
to browsing requirement (possibly different from the conversion source format), while
the destination format of front viewing organizes the fields of corresponding source
format (first convert field values into texts) to form the format that can be browsed.
The source format of back viewing divides the final bill into some fields according to
browsing requirement, while the destination format of back viewing organizes the
3-22
User Manual
fields of corresponding source format (first convert field values into texts) to form the
format that can be browsed.
All the bill formats are saved in the database file "\BillSvr\Format\BillFormat.mdb ",
and all the formats are saved in one database table (namely the format base).
However, the formats are separated from each other when using the special format
base configuration tool to view (data view).
It is easy to realize bill classification on the basis of dividing an original bill into
separate fields. The purpose of classification is to process bills of different settings
according to different procedures, and save them in different physical paths. The
channel is the description of the attributes and path of saving the bill after
classification. The function of classification is to classify different types of bills (this
type can be set) according to users' requirements, so as to perform other processing.
Because you have got the value of each field, you can set the bill type according to
the values of some fields
For example, if the value of Field3 is larger than 10000, the bill type is A; if the value
of Field3 is 10000, the bill type is B; if the value of Field3 is smaller than 10000, the
bill type is C.
The following expressions can be used to implement bill classification (each line
represents classification of a bill type), as shown in Table 3-6.
Table 3-6 Classification expression_1
Bill type Classification condition Classification format

A Field3 > 10000 Source
B Field3 = = 10000 Source
C Field3 < 10000 Source
In the above table, "Classification Format" is relevant to "Classification condition": the

field name in "Classification condition" must be that of the field in "Classification
format". Add the channel and conversion format to the field, as shown in Table 3-7.
"Classification format" and "Conversion format" are respectively the above-mentioned
conversion source format and conversion destination format.
Table 3-7 Classification expression_2
Channel No Bill type Classification condition Classification format Conversion format

1 A Field3 > 10000 Source Dest
2 B Field3 = = 10000 Source Dest
3 C Field3 < 10000 Source Dest
3-23
User Manual
In the above table, the first line can be explained like this:
z The bill meeting the following conditions is the bill of type A: according to the
source format for explaining the bills, the value of Field3 is larger than 10000.
z The bill of type A is converted into the final bill by using Dest Format (Dest is the
destination format).
z The bill is sent to Channel 1 for saving after being converted.
The explanation of the second and the third line is similar. A, B, C, is only a
descriptive text.
If the user needs to browse the bills, he/she can define the source format and
destination format for viewing, and add the destination format name of viewing to the
corresponding line.
The bill format base of the iGWB uses one text file (\BillSvr\Format\Channel.cfg) to
save classification conditions. The format is shown in Table 3-8.
Table 3-8 Classification condition format
Front Back
Channel Descripti Classification Classification Conversion Conversion
viewing viewing
ID -on format condition format mode
format format
Front Back
Classification Conversion
1 Type1 Condition1 0/1 viewing viewing
format1 format1
format1 format1
Front Back
format2 format2
format2 format2
Front Back
format3 format3
format3 format3
In the above table, one line corresponds to one line in the text file, and each line
defines one classification condition, and the conversion format, conversion mode,
front viewing format, and back viewing format of the bills classified according to this
condition. In addition, the user can define the "QueryFormat". QueryFormat is a
format for iGWB to query bill. It is actually a subset of viewing format, only including
the fields for querying. And the user can also edit and save channel.cfg as text file, so
as to generate bill classification and format conversion settings in line with the
practical requirements.
The conditions of classification can be set flexibly by being described in C language

expression. The condition of classification is set according to the content of the bill,
and all the data fields in the bill can be references for classification. For example,
classify bill of the Normal Bill type to a certain channel, and Metering Bill to another
channel.
3-24
User Manual
The classification also has the function of filtration. For example, the user sets two
channels: channel 1 is Normal bill, and channel 2 is Metering bill. The channel can be
set by editing classification configuration file "channel.cfg", which records the
classification setting information directly in text file mode.
The following introduces different meanings of various items in "channel.cfg" file.

Open the classification configuration file [C: \BillSvr\format\channel.cfg] in text
mode. The file contents include Channel ID, Description, Pickup Format, Pickup
Conditions, Conversion Format, Conversion Mode, Front Viewing Format, Back
Viewing Format, Query Format, Back Query Format. They are described below:
z Channel ID: use positive integer to code continuously starting from 1. It is used
as the classification channel ID;
z Channel description: use characters to simply explain the channels, which will
appear in the channel description when the user operates the bill console to
browse bills and to backup the bills.
z Pick up format: the name of classification format;
z Pick up conditions: i.e. classification condition for example, "bill_type<32"
indicates the bill is a Normal bill, and "bill_type==32" indicates the bill is a
Metering bill. The field "bill_type" stands for bill type. The bill field used in pick up
conditions must be defined in pick up format when bill format is set;
z Conversion format: define the conversion destination format of bills in this
channel generally use the default configuration;
z Conversion mode: option 0 stands for binary conversion, 1 for text conversion.
The default is 0;
z Front viewing format: original bill viewing format;
z Back viewing format: final bill viewing format;
z QueryFormat: original bill query format;
z Back QueryFormat: final bill query format.
This file can be edited as text file of another name, and be renamed as "channel.cfg"
after the edition.
Note that the new channel.cfg setting is not valid until iGWB is restarted. You can also
restart BillRemote service to make the modification valid.
The classification result directory is specified during installation, and the default is "E:
\BillBack". Under this directory, the program will set up directories ch1_1, ch1_2, etc.
corresponding to the classification setting.
If classification is not needed, you can define only one channel in the configuration file
"Channel.cfg". Generally, the default classification configuration after the installation
of charging gateway is adopted.
3-25
User Manual
3.2.2 Bill Format Tool
Caution:
z iGateway bill allows the users to customize their final bill format, which is done by configuring the
format library. The principle of format conversion is described in the previous section.
z iGateway bill provides a "BillFormat" tool for the users who have special requirements on their final
bills to customize their final bill format. As the configuration process is rather complicated and
incorrect configuration may result in disastrous data loss, the tool is only for advanced users and
experts. Normally, default format should be used. If you have specific requirements to the bill format,
contact Huawei engineer.
I. Functions
The bill format tool offers the following functions:

z Add new format
You can add new formats by selecting "Add original format" and "Add destination
format".
z Set format
This function allows setting of the existing formats. For the source format, the format
setting actually is the definition process of "decompose region" for bills; for destination
format, the format setting is the definition process to convert the domains in the
source format to form destination format.
z Set enumeration value
The function of enumeration value is to explain the value of binary fields in source bill
with enumeration character strings during bill conversion and browsing, so that you
can directly see the meaning of the field instead of binary digits. You can use the Bill
Format Tool to define the enumeration value of various fields.
II. Operation of bill format tool
To use the bill format tool, do as follows:

1) Select [Start\Programs\CDMA iGateway Bill\Bill Format Tool] or run application
program C:\BillSvr\bin\BillFormat.exe.
2) Select the menu [Operate\Format Management] to configure and manage bill
format.
Figure 3-14 shows the [Bill Format Set] window and Figure 3-15 shows the [Format
Management] dialog box. There are tool buttons with equivalent function of the menu
options in the interface shown in Figure 3-14.
3-26
User Manual
Figure 3-14 The "Format Management" menu
Figure 3-15 The "Format Management" interface
As shown in Figure 3-15, "Format Management" provides the following functions:

z Browse format
z Delete format
z Add original format
3-27
User Manual
z Add destination format.

The operations of the functions are introduced below.
z Browse Format
To browse the format, select any format in the window as shown in Figure 3-15, and
click <Browse Format>.
The format is displayed, as shown in Figure 3-16.
Figure 3-16 Browse format
z Delete Format
To delete a format, do as follows:
3) Select the format to be deleted in the window as shown in Figure 3-15, and click
<Delete Format>.
A message is displayed, as shown in Figure 3-17.
Figure 3-17 The dialogue box for confirmation of the format deletion
4) Click <OK> to delete the selected format.

z Add original format
3-28
User Manual
To add original format, do as follows:

1) Click <Add Original Format> in the window as shown in Figure 3-15.
2) In the [Add format] dialog box displayed, enter the format name and description,
and then click <OK>. See Figure 3-18.
Figure 3-18 The dialogue box for adding an original format
z Add destination format

To add destination format, do as follows:
1) Select original format corresponding to the destination format in the window as
shown in Figure 3-15, and click <Add Destination Format>.
The [Add format] dialogue box is displayed, with the original format name.
2) Enter the format name and description in the dialogue box and click <OK>. See
Figure 3-19.
Figure 3-19 The dialogue box for adding the destination format
The specific operations of adding original format and adding destination format are
similar to that of resetting the existing format. Below is an example of destination
format addition aiming at explaining the operation of format setting.
3) Click <OK> in the dialog box, as shown in Figure 3-19.
A window as shown in Figure 3-20 is displayed, showing the new record created.
The new record displays various information about the field.
3-29
User Manual
You can insert, add, or delete records by using the [Operate] menu in [Bill
Format Set] window and the tool buttons in the tool bar of the window, as shown
in Figure 3-21.
Figure 3-20 Add destination format
Figure 3-21 Format record operation
3-30
User Manual
The format name currently being set is displayed in the title bar of the window shown
in Figure 3-20 (for destination format, its corresponding original format name is also
displayed). The meanings of various fields in the format base are as follows:
z Struct field name: The fields included in the format.
z Struct field description: The descriptive text, explaining the fields included in the
structure. It can be null.
z Bit field indication: Whether the format field is bit field or not.
z Struct field data type: The data type of format field. For destination format to be
browsed, the data type of all the fields are "char".
z Struct field length: Field length.
The number of bytes that the fields practically occupy is relevant to "bit field
indication", struct field data type", and "struct field length".
For example:
Struct field type is "char", bit field indication is 0, struct field length is 10, then the
fields actually occupy 10 bytes.
Struct field type is "char", bit field indication is 1, struct field length is 4, then the fields
only occupy 4 bits of a byte.
Struct field type is "long", bit field indication is 0, struct field length is 1, then the field
time occupies 4 bytes.
Struct field type is "long", bit field indication is 1, struct field length is 10, then the field
time occupies 10 bits of 4 bytes.
For original bill, this length is the field length in the bill.
For destination format, this length is the length of the field converted, that is, the
expected length. If the data length converted is not enough, then use filling symbols
to fill in.
z Length for service station displaying: The length of the field displayed (character
number) when bills are browsed. For original format, this field is invalid.
z Alignment mode for service station displaying: The alignment mode of the fields
in the displaying column when bills are browsed. There are three field alignment
modes: "align left", "align right", "align center". For original format, this field is
invalid.
z Enum value: Mark if the field is Enum type or not. Only the field of value type can
be set as Enum type. If a field is Enum type, the value of the field is not
displayed when displaying. Instead the character string standing for the value is
displayed.
The Enum value of all Enum fields must be set in the format base, otherwise,
the fields not set with Enum value will be displayed as empty.
3-31
User Manual
z Transfer expression: This field is empty in original format, and only valid in target
format. When transferring original bills into target format bills, all fields will be set
in "Transfer expression".
z Element ID for bill query: Query ID is only used in bill query. The field query ID
corresponds to query conditions.
Now you can set all fields of one format record.
Settings of each field:
Double-click "Struct field name", and select "struct field name" in the pull-down box.
These "struct field names" are the existing "struct field names" in original format. If
this field already has "Struct field description" in original format, "Struct field
description" in target format will be selected automatically, or we can double-click
"Stuct field description", and manually select them in the pull-down box.
In "Bit field indication", select 0 or 1 to show the state of bit field. "Struct field data
type" and "Alignment mode for service station displaying" can be selected through the
pull-down box.
Double-click "Enum value" in the record of Enmu value to be set, and click and <…>
button appears, as shown in Figure 3-22. Configure one or several Enum fields and
their Enum value in the pop-up window, as shown in Figure 3-23. When browsing the
format, if a Enum value is defined in this field, an accessory mark will be displayed in
this field.
Figure 3-22 Set Enum value_1
3-32
User Manual
Figure 3-23 Set Enum value_2
Double-click "Transfer expression" field, click the appeared button <…> to pop up the
window as shown in Figure 3-24. Select the needed function and parameter, and
confirm them to finish the configuration of transfer expression.
3-33
User Manual
Figure 3-24 Set transfer expression
For other fields that need the values input, manually enter the values.
The explanation for other operation methods:
Select a whole record by clicking the record serial number in the recording header, or
directly draw the mouse to select multiple records, and press <CTRL+C> or
<CTRL+V> to copy and paste the records.
Or while keeping pressing <CTRL>, click the record item with the mouse. And the
accumulated value of "Struct field length" appears, according to which we can easily
record the total occupied length of the fields already added so as to check if the field
length meets the requirement of the bill field.
III. Explanations of struct field types and transfer expression function in

format base
Table 3-9 lists the Struct field types (namely field types) used in bill format base.
Table 3-9 Explanation of struct field type
Type name Byte length Explanation

Char 1 Character types
unsigned char 1 Unsigned character type
Int 2 Integrating
3-34
User Manual
Type name Byte length Explanation

unsigned int 2 Unsigned Integrating_
Short 2 Short integrating
BCD 1 Forward BCD code
RBCD 1 Reverse BCD code
Long 4 Long int
unsigned long 4 Unsigned long int
Float 4 Float typ
Double 8 Double accurate type
For the explanation of transfer expression function in bill format base, see Table 3-10.
Note:
The Field_Name appearing in all the functions is the field in original format.
3-35
User Manual
Table 3-10 Explanation of Transfer expression function
Name of the function Function of the function

Block copy
BlockCopy(Field_Name)
Parameter Field_Name is the field to be copied.
Convert two-bit year into four-bit year, and get binary integer of two
GetFullBinYear(Field_Name) bytes.
Field_Name is two-bit year data
Convert the specified field into text.
Field_Name is the field name to be converted.
DivideSign is the divide sign among fields, and follows the end of
the field and is used to separate the field from the succeeding
fields.
DIV_BLANK: blank
DIV_COMMA: comma
DIV_COLON: colon
DIV_SLASH: slash
DIV_DOT: dot
DIV_TIP: tip
DIV_LINE: line
Text(Field_Name, DivideSign,
DIV_NULL: null
FillSign, AlignMode,
FillSignEx) FillSign is fill sign, used to fill in when the converted length is
smaller than the required length
FILL_ZERO: Character 0
FILL_BLANK: blank
FILL_HYPHEN: hyphen-
FILL_MIN: Min <
FILL_MAX: Max >
FillSignEx is expanded fillsign; optional parameter. If this
parameter is configured, the fillsign is FillSignEx when Fiel_Name
is empty. If it is not configured, the fillsigns are all FillSign.
AlignMode is alignment mode.
LEFT: Align left
RIGHT: Align right
GetFullTextYear(Field_Name, Convert two-bit year into four-bit year and get a character string
DivideSign, FillSign, with the length of 4.
AlignMode) Parameter and Text function are the same.
3-36
User Manual
Name of the function Function of the function

Mainly used to browse destination format, and to provide Enum
character strings for the bill console during browsing. Field_Name
must be of numerical value type, the function searches the
corresponding character string according to this value and returns
to this character string.
EnumOtherInfo(Field_Name, EnumOtherInfo is default value, if there is no character string
EnumOtherInfo, DivideSign) corresponding to Field_Name in format base, the function returns
to this value.
DivideSign is the divide sign among the fields, and used to
separate the Field_Name field from succeeding fields. The value of
this parameter is the same as DivideSign parameter of Text
function.
Create the date and time format YYYY/MM/DD HH:MM:SS
DateAndTime(year, month, The former six parameters are the Struct fields of year, month, day,
day, hour, minute, second, hour, minute and second in the definination of original format.
DivideSign) DivideSign is the divide sign among the fields, and its value is the
same as that of the DivideSign parameter of Text function.
Binary field is converted into text according to hexadecimal system.
HBCDToText(Field_Name,
Field_Name is the field to be converted into hexadecimal format.
DivideSign, FillSign,
AlignMode) The parameter values of DivideSign, FillSign, AlignMode are the
same as that of Text function.
Convert the field of BCD type with length indication into text. The
field of this type does not end with 0xF. Instead a field length value
is put in front of the field.
Field_Name is the field to be transferred into text.
BCDNOEXPLAIN(Field_Name
, Field_Length, DivideSign) Field_Length is the length of Field_Name (it is the bit number of
BCD code instead of byte length). It is also a field in the original
bill.
DivideSign is the divide sign among the fields, the parameter value
is the same as the DivideSign parameter of Text function.
Specially used to get the Enum value for "Service code" field of the
MSC bill.
EnumTBSInfo(TBS, TBS field is the indication of telephone service or bearer service.

tele_bearer_code, DIV_TIP) Tele_bearer_code is service code, the value of this field varies with
the value of TBS.
TBS and tele_bearer_code are both a field in original format.
Convert the data type of unsigned char, short, long, unsigned long,
TextEx(Field_Name,
int, unsigned int, int64 and the content of 0xF of Field_Name field
DivideSign, FillSign,
into empty character string, the other function of TextEx is same as
AlignMode, FillSignEx)
Text. Parameter is the same as Text function.
3-37
User Manual
3.3 Default Directory Structure and File List
I. Major files installed under c:\billsvr\bin
Backsave.exe Back save module executable file. It is used to save the call
bill files required by the billing center.
Backupmodule.exe Backup module executable file. It is used to backup call bills

over a long period of time. It reads the specific files from the hard disk and writes
them into other storage devices during low traffic hours. It can be activated and
terminated by the bill console to save the call bill files into hard disks, or MO.
Billalarm.exe Alarm module executable file. It processes alarm messages

coming directly from the functional modules.
OMM.exe Operation and maintenance executable file. It provides an

interface for operation and maintenance on the iGateway bill, including an interface
with the bill console and user authority management
Cluster.exe Dual server module executable file. It takes care of the

dual-server data synchronization, heartbeat detection, system switch on failure and
resource management (including volume label, virtual IP, etc.)
Frontsave.exe Front save module executable file. It saves original call bills.
Kernel.exe Main control module executable file. It is responsible for

starting all the other modules and monitoring their running status as well as initiation
of some resources.
Killkernel.exe Executable file to quit the kernel.exe process.
Convert.exe Bill processing module executable file. This is an optional

module. It converts the call bill format according to the requirements of the billing
center. Such conversion includes converting the call bills to some text format and
adjusting the data fields in the original call bills.
Msgserver.exe Executable file for debugging print information observing

program. The debugging messages of the iGateway bill are sent directly to the
debugging message output module, which will decide either displaying them on the
monitor screen or saving them on the disks.
Netmsc.exe Host communication with switch module executable file. The

host communication module establishes TCP connection with the specific modules in
the host. It receives the original call bill data from the host while sending the alarm
messages generated by the iGateway bill to it.
Asn1.dll Asn.1 decoding dynamic library
3-38
User Manual
Sfhnet.dll Auxiliary dynamic library of network module state file
Sfhsave.dll Auxiliary dynamic library of save module state file
Format.dll Dynamic library required by format conversion
II. Files installed under c:\billsvr\format
Channel.cfg Setup file for the channel to the Billing Center
Billformat.mdb Setup file for generated bill format
III. Files installed under c:\winnt\system32
Mfcn42d.dll Dynamic linked library of VC
Mfco42d.dll Dynamic linked library of VC
Mfcd42d.dll Dynamic linked library of VC
Mfc42d.dll Dynamic linked library of VC
Msvcrtd.dll Dynamic linked library of VC
IV. Files installed under c:\InetPub\wwwroot
Config.ini Bill console configuration information file
BillAll.jar Package file of the bill console server (BillRemote)
BillApplet.jar Package file of the bill console client
Default.htm Start page of the bill console client
Default2.htm Login page of the bill console client
Go.bat File to startup the batch processing of BillRemote in

command line mode
RightGroups.txt User group configuration file
Rights.txt User group authority configuration file
Rt.jar Package file of the classes provided by Java
String.en.US Characters in the bill console client interface
Invoker.exe Executable file for starting up the BillRemote service
Users.txt User information file
Help.html Bill console Help file
PWD.exe Executable file for iGWB monitoring program
3-39
User Manual
V. Files installed under c:\InetPub\wwwroot\plugin
JRE12.exe Executable file for installation program under Jave operating

environment
JREPatch.exe Java patch program
VI. Files installed under c:\InetPub\wwwroot\Imgs
*.jpg Picture file used by bill console Help
VII. Files installed under c:\InetPub\wwwroot\Images
*.jpg Picture file used by bill console client
VIII. Files installed under c:\InetPub\wwwroot\Html
Contents.htm Bill console Help file
Head.htm Bill console Help file
Main.htm Bill console Help file
IX. Directory structure for saving original bill files
The original bill files received by iGWB are stored in order in the naming format from
B000000001.BIL to B999999999.BIL. The file size can be set but cannot be smaller
than 1M. The file saving directory is named by date and a new path name is formed
each day. Only when the original bill reaches the specified length can a new file be
setup. All the bill files are saved by date directory. When creating a file, check the
system time and determine whether to create a new directory and create the file
under this directory. The following is an example of the directory structure:
D:\BillFront\data\20000505\b000000001.bil
..................
D: \BillFront\ may be set by the user.
X. Directory structure for saving final bill files
1) Root directory
3-40
User Manual
E:\billback. The volume label and path name in the directory are set during system
installation.
2) Sub-directory 1
This directory name cannot be modified.
\backdata\chl_x\date\: x is the channel No. The bill files are put under different
directories by date under the channel directory and the files under each channel are
numbered separately. For example:
E:\BillBack\backdata\chl_1\20000505\Shenzhen20000609_01_00000001.DAT
3) Sub-directory 2
The read and write attributes of the directory are open to the Billing Center. This
directory name cannot be modified.
\backdatabak\chl_x\: x is the channel No. The directories are not subdivided by date
under each channel directory. Instead all the files are put together. For example:
E:\BillBack\backdatabak\chl_1\Shenzhen20000609_01_00000001.DAT
XI. Directory structure of the state file
1) Root directory
D:\StatusFile.
The volume label and path name in the directory are set during system installation.
2) State file of backup module
D:\StatusFile\BackupInfo\Backup.ini
3) State file of network module
D:\StatusFile\Network\status.dat
4) Active state file of the front and back save modules
D:\StatusFile\info\F_Save_Info.dat
D:\StatusFile\info\B_Save_x_Info.dat
X is the channel No.
3-41
User Manual
5) Standby state file of the front and back save modules

E:\StatusFileB\bakinfo\F_Bak_Info.dat
E:\StatusFileB\bakinfo\B_Save_Bak_x_Info.dat
"E:\StatusFileB" is set when installing the system and "x" is the channel No. The
standby state file of the front and back save modules is the real-time backup of the
active state file of the front and back save modules.
6) Backup file of the state file of the front and back save modules
D:\StatusFile\Status\MMDDF_Save_Info.dat
D:\StatusFile\Status\MMDDB_Save_x_Info.dat
"MMDD" is the month and the day and "x" is the channel No. The backup file backups
the active state file of the front and back save modules by day.
3-42
User Manual
HUAWEI iGateway Bill Chapter 4 iGateway Bill Console Operation
Chapter 4 iGateway Bill Console Operation
4.1 Start iGWB Console
4.1.1 Start iGWB Console
The iGWB console is the iGWB service management software. To start the iGWB
console, a Web browser, that is, Microsoft Internet Explore (IE4.0 version or above),
and a JavaPlugIn (JRE12.exe file) are required. The JavaPlugIn provides a Java
program runtime environment.
To Start iGWB Console:

1) Activate the browser and enters the domain name address or IP address of the
iGWB server.
If you have not installed Java, a window as shown in Figure 4-1 is displayed.
Figure 4-1 Start the iGWB console
If it is the first time to run the iGWB console or no Java program runtime environment
has yet been installed, load the JavaPlugIn (JRE12.exe file) according to the prompt
in Figure 4-2.
2) In the window displayed in Figure 4-1, click "click here to install Java".
4-1
User Manual
The [File Download] dialogue box is displayed, as shown in Figure 4-2.
Figure 4-2 Confirmation box of downloading Java runtime environment JRE12.exe
3) Select "Run this program from its current location", and click <OK> to download
the file "JRE12.exe".
The download progress is displayed, as shown in Figure 4-3.
Figure 4-3 File download
When the download is completed, the Security Warning dialogue box is displayed,
prompting that the publisher is reliable and the content to be installed is safe.
4) Click <Yes> to unpack Java operating environment, as shown in Figure 4-4.
4-2
User Manual
Figure 4-4 Unpack Java runtime environment
Then it starts to install the Java browser. The [Software License Agreement] dialogue
box is displayed, as shown in Figure 4-5.
5) Click <Yes> to accept the software license agreement.

The [Choose Destination Location] dialog box is displayed, as shown in Figure 4-6.
4-3
User Manual
Figure 4-6 Select installation folder
6) Select the destination folder and click <Next>.

The [Select Browsers] dialog box is displayed, as shown in Figure 4-7.
Figure 4-7 Select Browsers
7) Select the "Microsoft Internet Explorer" and click <Next>.

A progress bar is displayed, as shown in Figure 4-8.
4-4
User Manual
Figure 4-8 Copying file process
After the files are copied, the installation program prompts the installation process is
completed.
The iGWB is generally configured as active/standby dual server system. After the
installation of the Java browser, a dual server patch should be installed.
8) In the window as shown in Figure 4-1, click "click here to install the patch".
The location of downloading is displayed, as shown in Figure 4-9.
Figure 4-9 Confirmation box of Java patch downloading
9) Click <OK>.
The security warning interface is displayed, as shown in Figure 4-10.
10) Click <Yes> to download JREpatch and install the Java patch.
4-5
User Manual
Figure 4-10 "Security warning" interface
11) Click "Here to run Huawei iGateway Bill Console" in Figure 4-1 to open the
browser and log in to the iGWB server.
Now iGWB console starts running.
Figure 4-11 is the initial interface of iGWB console after entering the WWW server.
You are required to enter user name and password. The default user name and
password of the system are "admin" and "sa" respectively. The user can modify the
password after login.
Figure 4-11 iGWB console login interface
Once the correct user name and password are entered, the operation interface as
showed in Figure 4-12 appears. You can conduct authorized operation and
maintenance on the iGWB through this interface.
4-6
User Manual
Figure 4-12 iGWB console operation interface
The icons in Figure 4-12 from up to down are: <User Management>, <Bill Browse>,
<Log Browse>, <Bill Backup>, <Bill Query>, <Status Information>, <Help> and <Log
Out>.
Note:
z The SmartBackup provided by iGWB is recommended to back up bills. See Chapter 5
SmartBackup—Bill Backup Tool for details.
z The <Bill Backup> in the iGWB console operation interface is another system-supported bill backup
mode, via which you can back up bills to external storage equipment, such as MO or hard disk in
iGWB server. See Appendix B Bill Backup for details.
If the user name or password provided is not correct, or the iGWB is not running
normally, the system will return an alarm information, as shown in Figure 4-13.
Figure 4-13 Warning information
4-7
User Manual
4.1.2 Overview Of iGWB Bill Console Functions
The iGWB Bill Console has the following functions:
I. User management
You can manage iGWB console users. The iGWB console has users of two levels:
the system administrators and common users.
The system administrators have all the authorities, including browsing bill files and
logs, backup of bill files, and managing users. When modifying the user attributes, the
administrators cannot modify the user name attribute.
The common users do not have the authority of managing users. They can only
modify the user attribute of their own, such as password, description, but not the user
name and the user group attributes. The common users have the authorities of
browsing bill files and logs, and backup of bill files.
II. Bill browse
You can browse original bills and final bills of various formats by designating a time
range (date: day, month and year; start time: hour, minute and second; end time: hour,
minute and second).
III. Log browse
There are three types of logs:

z Original bill log
z Final bill log
z Backup log.
You can browse logs by designating a time range (date: day, month and year; start
time: hour, minute and second; end time: hour, minute and second).
IV. Bill backup
Note:
See Appendix B Bill Backup for details. However, this backup mode is not recommended. The
SmartBackup provided by iGWB is recommended to back up bills. See Chapter 5 SmartBackup—Bill
Backup Tool for details.
You can back up original bills or final bills in any of the following ways:
4-8
User Manual
z Automatic backup
z Semi-automatic backup
z Manual backup
The automatic backup is started periodically by the iGWB.
You can enable the semi-automatic backup through the iGWB console. For
semi-automatic backup, parameters of start time and end time, and paths cannot be
specified, but end date must be designated.
You can perform manual backup by specifying time or bill serial number. Backup
media and paths can be designated.
You can also browse the backup media during the backup process.
V. Bill query
You can query bills by bill format, bill type, bill record type, start/end date, start/end
time, conversation duration, telephone number, and call termination cause.
VI. Status information
The iGWB console also provides other information like the CPU load, virtual memory
utilization, maximum virtual memory, virtual memory used, available space of original
bill storage disk, available space of final bill storage disk, and the iGWB in service
(active iGWB server or standby iGWB server), etc.
4.2 User Management
4.2.1 Function
User management includes the management of the system administrators and

common users.
A system administrator has all the operation and maintenance authorities, including:
z Bill browsing
z Log viewing
z Bill backup
z User management, except deleting system default user "admin".
A common user has no authority of administrating users. He can only modify his own
password and description attributes. He has no authority to modify the user name,
user group attributes and cannot add, modify or delete other users. The common user
can browse bills, view logs, and backup bills.
4-9
User Manual
The system presents different interfaces according to user authorities, thus

preventing the user from seeing commands beyond his authority.
4.2.2 Access
Click "User Management" icon in Figure 4-12.

z If the user is system administrator, the user management interface is displayed,
as shown in Figure 4-14. The <New>, <Modify>, <Delete> buttons in the figure
can be used.
Figure 4-14 User management-system administrator interface
z If the user is a common user, the management interface is as shown in Figure

4-15. The <New>, <Modify>, <Delete> buttons are gray indicating they can not
be used by common users. Common users can only browse it.
4-10
User Manual
Figure 4-15 User management-common user interface
The following is a brief description of <New>, <Modify>, and <Delete> buttons.
4.2.3 Interface description
I. <Add>
Click <New> in Figure 4-14, an interface as shown in Figure 4-16 is displayed. For
example, to add a common user named "commonuser", enter necessary information
and click <Confirm>. See Figure 4-16.
Figure 4-16 Add a common user
4-11
User Manual
The process of adding a system administrator is similar to that of a common user. But
in the [Description] field, the "admins" must be selected from the [User Group]
pull-down menu, and "system administrator" or similar description should be entered
to specify the identity.
II. <Modify>
Only the system administrator has authority to modify the attributes of other users.
To modify the attributes of a user, do as follows:

1) Select the user to be modified in Figure 4-14, and click <Modify>.
A dialogue box is displayed, as shown in Figure 4-17.
2) Modify the password, description, user group, or other items of the user, and
then click <Confirm>.
Note:
You cannot modify user name. However, you can delete the user and then add a new user.
For instance, to change the newly added user "commonuser" in Figure 4-16 from a
common user to a system administrator
1) Select the user "commonuser" in Figure 4-14, and click <Modify>.
2) In the dialog box, as shown in Figure 4-17, select "Admins" from the pull-down
box [User Group].
Figure 4-17 Modify the user
4-12
User Manual
If a common user wants to modify his password, he can find and select himself in
Figure 4-15, and click <Modify>. The following procedures are the same as the
above.
III. <Delete>
To delete a user, select that user in Figure 4-14, and click <Delete>. A confirmation
box as shown in Figure 4-18 appears. Click <Confirm> to delete the user. The
system does not allow deleting system default administrators.
Figure 4-18 User deletion confirmation dialogue box
4.3 Bill Browse
4.3.1 Function
This menu is used to examine all the bill information of a certain period in a day.
4.3.2 Access
Click "Bill Browse" icon in Figure 4-12.
A dialogue box is displayed, as shown in Figure 4-19, which requires you to specify
the browse conditions.
4-13
User Manual
Figure 4-19 Bill browse condition dialogue box
Bill statistical function is provided in bill browse, which helps the users take statistics
the original bills. Click the button in Figure 4-19, all the bill records and their
sizes of the date specified in the date drop box will be displayed.
4.3.3 Interface Description
Table 4-1 describes the items displayed in the bill browse condition dialogue box.
Table 4-1 Items of bill browse condition dialogue box
Domain Name Meaning

Bill type Pull down the menu to select and browse the original bill or the final bill.
The original bill is "Bill front browse source bill, Meter bill". The final bill is
Bill format
"CHN_1_Normal-bill, CHN_2_Meter-bill"
Select the year, month, and date of the bill. The format is shown in Figure
Date
4-19.
Start time Enter the hour, minute and second. The format is shown in Figure 4-19.
End time Enter the hour, minute and second. The format is shown in Figure 4-19.
Note:
z The original bill refers to the most original bill received by the iGWB.
z The final bill refers to the bill generated by sorting and combining original bills. It is the bill sent to the
Billing Center.
4-14
User Manual
4.3.4 Operations
I. Browsing original bills
To browse original bills, do as follows:

1) Specify the browse conditions as shown in Figure 4-19, select the "Bill front
browse source bill" bill format and click <Start Browsing>.
A bill file list is displayed, as shown in Figure 4-20.
Figure 4-20 The list of bill files
2) Select a bill file from list and click <View>.

The detailed information of this bill file is displayed, as shown in Figure 4-21.
4-15
User Manual
Figure 4-21 Detailed information of original bill file
The <First Page>, <Previous Page>, <Next Page> and <Last Page> buttons are
available to switch between pages.
To jump to specific page, enter a record number (not bigger than the total record
number) in "Go to" text box, and press <Enter>.
The record number of the current page is displayed at the bottom.
To print the current page, click <Print> (one print operation can only print the data of
the current page).
To facilitate operation and viewing, the system provides the function for the users to
define customized window layout, such as hiding columns. After the setting, only the
saved current layout will be used (including future browsing). The system will display
the bill file information according to user’s settings.
The detailed operation procedure is as follows:
Right-click on a field in Figure 4-21, and the system will display the layout adjustment
menu, as shown in Figure 4-22.
4-16
User Manual
Figure 4-22 Layout adjustment
Description of the layout adjustment menus:
[Align Left]: Align the information of this field to the left.
[Align Center]: Display the information of this field in the center.
[Align Right]: Align the information of this field to the right.
[Show All Columns]: All columns are displayed (including the hidden columns).
[Hide]: Hide selected columns.
[Show]: Show the hidden columns.
[Save Layout]: Save the current layout for future use.
II. Single record display
Double-click the bill record in Figure 4-21, and the detailed information of the bill
record will be displayed, as shown in Figure 4-23.
4-17
User Manual
Figure 4-23 Detailed messages of a bill
In Figure 4-21, you can scroll the bar vertically or horizontally to view the bill file
information. You can also speed up the browsing process by paging up and down or
by turning directly to the first page or the last page.
III. Browsing final bills
To browse final bills, do as follows:

1) In Figure 4-19, enter the date, start time, and end time.
2) Select the "final bill" in the [Bill Type] list and a channel in the [Bill Format] list,
and then click <Start Browsing>.
The system displays the file list of final bills, as shown in Figure 4-24.
4-18
User Manual
Figure 4-24 Final bill file list
3) Select a bill file and click <View>, or double click this final bill.
The detailed information of the bill file is displayed, as shown in Figure 4-25.
Figure 4-25 Final bill detail information
You can use the <Return> button to go to the previous dialogue box.
The browsing of hot bill is almost the same as that of the normal bill.
When a certain bill file has been selected in Figure 4-19, if there is anything abnormal
about the network, an alarm window will be displayed, as shown in Figure 4-26.
4-19
User Manual
Figure 4-26 System alarm report of network error
4.4 Log Browse
4.4.1 Function
This function is to view the operation records (logs). All the operation information
(including abnormal operation information) is recorded in the log file.
4.4.2 Access
Click <Log Browse> in Figure 4-12, and the system displays a dialogue box, as
shown in Figure 4-27.
Figure 4-27 Log browsing condition dialogue box
4-20
User Manual
Table 4-2 describes the items in Figure 4-27.
Table 4-2 Items of log browse dialogue box
Domain Name Meaning Remarks

The start date of the logs for browsing. The format is shown in
Start date
Figure 4-27.
The end date of the logs for browsing. The format is shown in
End date
Figure 4-27.
Category Including original bill log, final bill log and backup bill log. Note 1
Note 1:
Original bill log is the log relating to the original bills and its contents are: log generating date (year/month/day), time
(hour/minute/second), log information, original bills generated.
Final bill log is the log relating to the final bills and its contents are: log generating date (year/month/day), time
(hour/minute/second), log information, final bills generated.
Backup bill log is the log generated during bill backup and its contents are: log generating date (year/month/day),
time (hour/minute/second), log information. The log information records the user’s backup operations, such as bill file
manually backed up by the user and backup media queried by the user.
4.4.4 Operations
To browse log:
1) In the interface shown in Figure 4-27, enter the start date and end date, select
"Original bill log", "Final bill log", or "Backup bill log" in the [Category], and then
click <Start Browse>.
The file list is displayed, as shown in Figure 4-28.
4-21
User Manual
Figure 4-28 Log file list
2) Select a log file and click <View>.

The detailed information of the log file is displayed, as shown in Figure 4-29.
Figure 4-29 Log file messages
There are many recorded fields in a log file. The scroll bar has to be moved to the left
or to the right during the browsing process, which brings much inconvenience. The
system has customized the layout adjustment function for subscribers. You can set up
customized layout such as hiding the listed information not in his interest. After the
4-22
User Manual
setting is completed, only the current layout that has been saved can function in the
subsequent browsing (including future login by the subscriber). The system will
display the log file information according to subscriber’s settings, such as align left,
align center, align right, show and hide the columns. Right click a field in Figure 4-30,
and the system will display the layout adjustment menu shown in Figure 4-30.
Figure 4-30 Log record layout adjustment
4.5 Bill Backup
See Appendix B Bill Backup for details.
4.6 Bill Query
4.6.1 Function
You can query the bill according to the designated condition.
4.6.2 Access
Click <Bill Query> in Figure 4-12, and the bill query condition dialog box will appear,
as shown in Figure 4-31.
4-23
User Manual
Figure 4-31 Bill query
[Bill Type]: Select original bill or final bill.
[Bill Format]: Select the format of the bill to be inquired. For different types of bill files,
the formats are different. When the subscriber changes the bill file category, the bill
format will change accordingly.
[Record Type]: Includes MOC, MTC, TRANSIT, CFW, MT_SMS, MO_SMS, etc.
[Start Time]: Input the start time in the pull-down list.
[End Time]: Input the end time in the pull-down list.
[Duration]: The restricted range of conversation time.
[Phone Number]: Input the number of the caller, called or the third party.
[Location]: Input Current LAC of caller, Initial LAC of caller, Current LAC of called,
Initial LAC of called.
[Termination Cause]: Includes call timeout, normal call clear.
[Current Progress]: The progress of querying the corresponding bill according to set
conditions.
After inputting and selecting the items as shown in Figure 4-31, click <Start>, the
system would display the record number in compliance with the condition. If the
queried records are not found, the "record found" is 0, if the queried record number is
4-24
User Manual
not 0, the system will display the numbers of the records in accordance with the
conditions, as shown in Figure 4-32.
Figure 4-32 Bill query results
When browsing the bill files, the user may speed up browsing by paging up and down.
If currently it is the first page, the <First Page> and <Previous Page> buttons are in
unavailable state. If currently it is the last page, the <Next Page> and <Last Page>
buttons are in unavailable state. The record number of the current page is displayed
at the bottom.
During the browsing process, the system traces the user on a real time basis and
updates and displays the number of the current page on the left lower part.
There are a number of record domains queried, the user needs to use the horizontal
scroll bar when browsing the bill files, which is not convenient. So the system
provides layout adjustment function. The user can set personalized layout such as
hiding column information not relevant. After the setting it will not function during
browsing only when it is saved. The system will display bill file information according
to the user’s setting of the layout, e.g. column width adjustment, column display or
hide, and automatic adjustment of column width.
Right click a field in Figure 4-32, the system will display the layout adjustment menu,
as shown in Figure 4-33.
4-25
User Manual
Figure 4-33 Layout adjustment
The functions and usage of the items in the layout adjustment menu are the same as
introduced in "Bill Browse".
4.7 Server Status Query
4.7.1 Function
You can query the server status information, including the utilization of system
resource, virtual memory and bill storage disks.
4.7.2 Access
Click <Status Information> in Figure 4-12, and the system will display the dialogue
box indicating the status information, as shown in Figure 4-34.
4-26
User Manual
Figure 4-34 Status information
[System Resource Used]: Server CPU utilization ratio and memory utilization ratio.
[Virtual Memory]: Maximum virtual memory and used virtual memory of the Server
[Bill Save Disk]: Space of the original bill storage disk and space of the final bill
storage disk.
[Other Information]: Other information includes the serial numbers of the current files
of various channels, etc.;
[Primary Host Running/Slave Host Running]: The server in service (active server or
standby server).
4.8 Handling Abnormal Situations
4.8.1 iGWB Console Cannot be Logged in Normally
I. iGWB not running
After the correct user name and password is entered, the system displays the
message "Login failure, possible cause: wrong user name or password, or abnormal
operation of iGateway Bill". It means the iGWB is not in operation or its operation is
abnormal and the user should login again after the iGWB is started.
4-27
User Manual
II. iGWB console server not operating
After the correct user name and password is entered, the system displays the
message "The BillRemote Service on the remote server end is not running,
connection failure", as shown in Figure 4-35.
Message
Figure 4-35 Message of connection failure with the iGWB
It indicates the iGWB BillRemote service is not started, and you should start the
service first: Select [Start/Settings/Control Panel/Services] (for Windows NT) or
[Start/Programs/Administrative Tools/Services] (for Windows 2000 Server). Use the
scroll bar to check if there is "BillRemote Service". If it exists but is not in operation,
click <Start> to start the BillRemote Service. You can log in the iGWB console after
the BillRemote Service has been started.
III. Network fault
During the operation process (such as viewing bill and log messages), if a network
fault occurs, the system will display "Network communication error, operation failed".
In this case, you should check if the network is normal, or exit the client end and
reconnect.
IV. iGWB switchover
After login to the iGWB console, if iGWB switchover occurs, the user cannot view the
bill until the iGWB runs normally after the switchover.
4.8.2 Dual Server Switchover
When the dual server switchover is performed, if bill files are being backuped in one
iGWB server, the backup process will stop; when the other iGWB server is started,
the ongoing backup will not continue.
Since bill files are stored in the disk array of the active and the standby servers
respectively, after the switchover, the bill data will be scattered.
The following handling should be adopted: insert new backup medium in the active
iGWB server after the switchover to backup bill files generated after the switchover.
The bills generated before the switchover will be continue to back up when the
4-28
User Manual
inactive iGWB server is active again. The user may number the backup media
according to the generating sequence of the bill files backuped.
If the backup stopped due to dual server switchover is automatic backup, the
automatic backup can still be carried on later. If it is manual backup, the user must
take corresponding measure after the switchover.
4.8.3 Backup Media Space Insufficient
When backup space insufficiency occurs during the backup process, the iGWB will
generate a fault alarm. When the fault alarm occurs, you should replace the already
fully written backup medium with a vacant one to continue the backup process.
4.8.4 Backup Media not Existing or Damaged
When backup medium is found not existing or is damaged for the backup, an event
alarm will be generated. Upon learning the event alarm, you must insert a vacant
backup medium and restart the backup process.
4.9 Help
4.9.1 Function
The on-line help gives a general aspect of the iGWB console, and describes the
methods in using the related function menus.
4.9.2 Access
Click <Help> in Figure 4-12. The system displays the interface as shown in
Figure 4-36.
4-29
User Manual
Figure 4-36 iGWB console on-line help
The information in the left column includes the contents of the help information, such
as preface, important information, term explanation, login and logout, user
management, bill browsing, log browsing, bill backup, storage medium browsing, etc.
Click any of these topics, the detailed help information will be presented.
4.10 Log Out
4.10.1 Function
To log out of the iGWB console.
4.10.2 Access
Click <Log Out> in Figure 4-12, and the system is displayed a dialogue box as shown
in Figure 4-37.
Figure 4-37 Log out
Click <Yes> to log out of the iGWB console.
4-30
User Manual
HUAWEI iGateway Bill Chapter 5 SmartBackup
Chapter 5 SmartBackup
Provided by the iGateway Bill (iGWB for short), the SmartBackup is an auxiliary tool
that can be used to back up bills. Adopting File Transfer Protocol (FTP), it enables the
hot backup of the bills between the active and standby iGWB servers or to the remote
WS.
5.1 Purpose of Bill Backup
The purpose of bill backup is to keep the bill file on the backup media for recovering
damaged bills in the billing center.
In some special cases, the backup of the bills are also sent to the billing center for
charging. In this case, bills must be backed up in the billing center and the storage
media.
5.2 Directory Structure and Naming Rules for Bills
All the bill records are stored in iGWB in the form of bill files, and the bill records can
also be backed up in this form.
The original bill records in iGWB are stored in files, and the size of the file can be
configured. All the original bill files are denominated and numbered together. The
name format is BXXXXXXXXX.BIL, in which X refers to the number from 0 to 9. The
serial number is from 1 to 999999999.
The original bill files are stored daily in the directory (one directory a day) named by
the date when the files are generated.
The iGWB will preprocess the original bills to generate the final bills provided
eventually for the Billing Center. The final bill records will be stored in files, and the
final bill files should be stored to the directory.
Different types of files can be stored in different directories whose name is CHL_X, in
which, X is the serial number of channels (begin from 1). There are sub-directories
under each channel directory, and there is one directory for the bill files of each day,
with the directory name being the date when the file is generated. In each channel all
files are denominated and numbered uniformly. The denomination format is
"prefix+XXXXXXXX.suffix", in which X refers to the number from 0 to 9. The serial
number is from 1 to 99999999. The prefix and suffix can be customized.
5-1
User Manual
The SmartBackup tool only backs up final bill files. The final bill files are backed up
into the storage media with the same directory structure as that in iGWB. The final bill
files are stored in the form of Channel directory\date directory\bill file.
5.3 Overview of SmartBackup
The SmartBackup is a bill-backup tool of iGWB. It enables the hot backup of the bills
between the active and standby iGWB servers or to the remote Work Station (WS) by
adopting FTP. Only the final bills are backed up.
The hot backup of bills between the active and standby iGWB servers works in the
following way:
z The SmartBackup is run on both the active and standby iGWB servers. The local
active/standby iGWB server serves as the FTP Client and the peer
standby/active iGWB server as the FTP Server.
z By FTP, the final bills generated by the local iGWB server are sent to the peer
iGWB server in real time and saved in it.
According to actual requirement, remote WS can be configured. With the
SmartBackup run on both the active and standby iGWB servers, the remote
maintenance WS can serve as the FTP Server and the local standby/active iGWB
server as the FTP Client. By FTP, the final bills generated by the iGWB can be
backed up to the hard disk of the maintenance WS in real time.
Note:
z The active and standby iGWB servers and the maintenance WS must have been installed with FTP
Server service. The FTP Server service is installed in the iGWB servers when the operating system
is installed.
z The iGWB delivered to users does not include the maintenance WS used for bill backup. The user
should prepare the PC for the maintenance WS if that function is required. Since the final bills can
be backed up via the dual-server hot backup between the active and standby iGWB servers, the
user can decide whether to backup the bills to the maintenance WS.
The working principle of SmartBackup and the networking of it are shown in Figure
5-1.
5-2
User Manual
Active iGWB Standby iGWB

HUB
Receive Receive
FTP Server FTP Server
Send Send
SmartBackup SmartBackup
Send Send
HUB
Receive
Maintenance console
FTP Server
Hard disk
External MO
Figure 5-1 SmartBackup working principle & networking diagram
Necessary parameters should be configured before the SmartBackup is run. During

the parameter configuration, the backup task can be set as automatic startup. Thus,
the backup task automatically runs on SmartBackup startup. The backup task can
also be set as manual startup; in such case, the backup task should be activated
manually.
5.4 Configuration of SmartBackup
5.4.1 Preparations
1) Stop Process Watch Dog (PWD) service: Click [Control Panel/Administrative

Tools/Services] to terminate PWD service.
2) Terminate iGWB program: Execute KillKernel.exe under \billsvr\bin to terminate
iGWB program
3) Check relevant parameters concerning backup in [iGateway Bill Config Tool]:
Execute config.exe under \billsvr\bin and check the backup mode and
destination path. The backup mode under [Backup/Final bill backup parameters]
should be "Manual" and the destination path under [Backup/Status file backup
parameters] should be null, as shown in Figure 5-2.
5-3
User Manual
Figure 5-2 Modify Backup configuration information
4) If relevant backup parameters in [iGateway Bill Config Tool] are modified, the
configuration information should be saved. Click the button in the toolbar to
save the information, and close [iGateway Bill Config Tool].

5) Run iGWB application: Execute Kernel.exe under \billsvr\bin to run iGWB
program again.
6) Install SmartBackup: Execute Setup.exe under directory disk1 on SmartBackup
installation software and install SmartBackup according to system prompt.
5.4.2 Configuring SmartBackup
Run SmartBackup. Find the file "SmartBackup.exe" under the installation directory of
SmartBackup (default path: C:\BillSvr\bin), and double click it. An icon

will appear in the taskbar, and the [Task Manager] widow, as shown in Figure 5-3, will
pop up.
5-4
User Manual
Figure 5-3 SmartBackup initial operation interface
Only after the backup task is configured can the SmartBackup be run. Each backup
task can accomplish the backup of the final bills under one bill channel to
corresponding directory of peer server only. Therefore, only by configuring relevant
parameters of every task can the SmartBackup run normally.
The principles for configuring backup task are:
The final bills of each channel will be backed up to the peer server. If remote
maintenance WS is necessary, the final bills will be backed up to the remote WS at
the same time.
Therefore, if there are n channels in iGWB, 2n tasks will be performed, i.e. n tasks to
back up bills to the peer server, and n tasks are performed to back up bills to remote
WS.
If remote maintenance WS is not necessary, the final bills will be backed up to the
peer iGWB server only, and n backup tasks should be configured.
The configuration of the SmartBackup will be introduced below, with two final bill
channels as example.
5-5
User Manual
I. The following operations should be performed on the peer iGWB server or

remote maintenance WS, to which the final bills are to be backed up
Note:
z Please refer to the FTP access authority and FTP open directory setup procedure introduced in
2.4.3 User Access Right and Parameter Configuration, which explains how to setup the user and
password used to log on FTP server, and the FTP open directory.
z Based on a Windows NT environment, the following explains how to open backup directory in peer
computer. This open procedure is similar on a Windows 2000 platform. Please refer to the section
"Configuring FTP(FTAM) Parameter " in 2.4.3 User Access Right and Parameter Configuration for
the particular steps.
1) Create backup directory in the peer iGWB server. For example, create two
directories "E:\PeerBackup\CHL_1" and "E:\PeerBillBackup\CHL_2".
2) Click [Start/Programs/Management Tools/Internet Service Manager] to open the
two backup directories created above in FTP service.
3) Configure FTP open directory properties. Assign alias to the two backup
directories respectively. For example, "E:\PeerBackup\CHL_1" has an alias of
"PeerBackupChl1" and "E:\PeerBillBackup\CHL_2" an alias of
"PeerBackupChl2". Specify the user access authority of the directory. Please
note that "Access" must be set as "Read" and "Write", as shown in Figure 5-4.
The FTP open directories are as shown in Figure 5-5, please note that the
"Directory Listing Style" must be set as "UNIX".
Figure 5-4 Set FTP directory properties
5-6
User Manual
Figure 5-5 FTP open directories on peer computer
Note:
The following configuration is only for the iGWB configured with remote WS. If no remote WS is
configured, it can be neglected.
4) Create backup directories in the maintenance WS: Assign a logic partition in the
remote WS for bill backup, and create two directories on it, e.g.
"\BillBackup\Chl_1" and "\BillBackup\Chl_2".
5) Open the FTP directory on the remote WS: Click [Start/Programs/Microsoft
Internet Server/Internet Service Manager] to open the two backup directories
created above to FTP service.
6) Configure FTP open directory properties. Assign alias to the two backup
directories respectively, e.g. "\BillBackup\Chl_1", alias "BackupChl1" and
"\BillBackup\Chl_2", alias "BackupChl2". Specify the user access authority of the
directory. Please note that "Access" must be set as "Read", as shown in Figure
5-6. The FTP open directories configured are shown in Figure 5-7, please note
that the "Directory Listing Style" must be set as "UNIX".
5-7
User Manual
Figure 5-6 Set FTP directory properties
Figure 5-7 FTP open directories on remote WS
II. The following operations should be performed on the local iGWB server,
where the backup task is created
1) Create backup tasks in local iGWB server: In the [Task Manager] dialog box of
the SmartBackup shown in Figure 5-3, click the <Load Task from BAU> button
(or <Load Task from iGWB>.
2) Click <OK>, two backup tasks, CH1Backup and CH2Backup, will be loaded, as
shown in Figure 5-8. (The SmartBackup also determines the number of backup
5-8
User Manual
tasks to be loaded according to the iGWB-matched version used. The number of

backup tasks to be loaded depends on the number of channels of iGWB
version.)
Figure 5-8 Load task from BAU (iGWB)
Note:
If <Load Task from BAU> is selected, the program will specify task name, read and load part of the
information in the iGWB Registry, such as "Local Directory" and some configuration parameters of task,
etc. If <Add Task> is selected, you should configure all the parameters, including task name and local
bill directory, etc. If new backup task is to be added after the backup task has been configured via <Load
task from BAU>, you can click <Add Task> to achieve the purpose.
3) Configure the backup task, which duplicates final bills in channel1 to peer iGWB
server: Double click "CH1Backup" in the [Task Manager], a dialog box will pop
up, as shown in Figure 5-9.
5-9
User Manual
Figure 5-9 Parameter configuration dialog box
The parameters in the dialog box are described as below:
"Parameters at BAU":
Local Directory Depth (levels): The level of local directory, it is configured to level 1
when bill files are directly saved under the directory configured in the "Local
Directory", and configured to level 2 when bill files are saved under the date directory
configured in the "Local Directory".
Local Directory: The directory where the bill to be backed up is saved, e.g. the
directory path of final bill channel 1.
Local Filename Extension: the extension of the bill file to be backed up.
Local Filename SN Length: the length (digit) of the serial numbers in the filename of
the bill file to be backed up.
5-10
User Manual
Reconnecting Server Interval: the time interval for which a new connection is
originated after the connection with FTP Server fails.
File Searching Interval: the time interval for which a new searching of bills (to be
backed up) starts after the bill backup is completed.
File Transfer Mode: the file is moved or copied to the peer computer.
Startup Type: The backup task is manually started up or automatically activated

when SmartBackup start up.
"Parameters at FTP Server":
Limit of Store Time (days): the maximum days for which the backup of the bill files
is kept on FTP Server. If any bill directory saved on FTP Server crosses the limit, it
will be deleted by FTP Client.
Caution:
It is valid only when the "Local Directory Depth (levels)" is 2. If the local directory depth is 0, there is no
limit on the days for which the backup of bills will be stored.
Limit of Files Stored: the maximum number of bill files that can be saved on FTP
Server. You can limit the number of bill files saved on FTP Server. If the number of
files to be backed up at the moment plus the files already saved on the FTP Server
exceeds the limit, the files backed up in earlier days will be deleted.
Caution:
It is valid only when the "Local Directory Depth" is 1. If it is 0, there is no limit on the number of backups
saved on FTP Server.
FTP Directory: The directory on FTP Server saving the backup of bills, i.e. the open
directory.
Server Address: URL address or IP address used to log into FTP Server.
User Name: User name used to log into FTP Server.
Password: Password used to log into FTP Server.
5-11
User Manual
4) Configure the task "CH1Backup" (backing up final bills in channel1 to peer iGWB
server) as shown in Figure 5-10.
Figure 5-10 Configure backup task (copy final bills in channel1 to peer iGWB server)
Task Name: CH1Backup (you can modify it if necessary).
Local Directory: E:\BillBack\Backdata\CHL_1
Limit of Store Time: 14 (it can be configured according to actual condition).
FTP Directory: PeerBackupChl1
Server Address: Input IP address of the peer iGWB server.
User Name and Password: input the user name and password the local iGWB
server uses to log into FTP Server. If anonymous user is configured, you can log into
the FTP Server with "anonymous".
Click <OK> to finish the setting.
5-12
User Manual
5) Configure the task "CH2Backup" (backing up final bills in channel2 to peer iGWB
server) in the same way, as shown in Figure 5-11.
Figure 5-11 Configure backup task (copy final bills in channel2 to peer iGWB server)
Click <OK> to finish the configuration.

6) Configure the task, which backs up final bills in channel1 to the remote WS. Click
<Add Task> in [Task Manager], and set relevant parameters, as shown in Figure
5-12.
5-13
User Manual
Figure 5-12 Configure task (backing up final bills in channel1 to remote WS)
Sever address: Input address of the remote WS.
FTP Directory: FTP directory opened on remote WS, which is used to save the
backup of the bills under channel directory.
Limit of Store Time: Normally the bills backed up to remote WS can be saved longer
than those backed up to the active and standby iGWB servers. In addition, the
capacity can be expanded by adding hard disks to the remote WS. The
recommended value for this parameter is 6 months.
Click <OK> to finish the configuration.
Caution:
To restrict the backup space of the remote WS, set the "Limit of Store Time" to a number greater than 0.
5-14
User Manual
7) Configure the task of backing up final bills in channel2 to the remote WS in the
same way.
8) After the above information are configured, 4 backup tasks will be displayed in
the [Task Manager] window, as shown in Figure 5-13. You can start any one of
them by clicking the <Start> button.
Figure 5-13 Backup tasks configured
If the parameters are configured correctly and all the equipment are properly
connected, the backup tasks will be enabled.
In such case, if there are bills in the final bill directory on iGWB, you will see the
backing up information of the bills by clicking the <Debug Info> button in [Task
Manager], as shown in Figure 5-14.
5-15
User Manual
Figure 5-14 Debugging information of bill backup
9) Check whether the bills in each channel can be normally backed up to peer
iGWB server or remote WS.
10) If normal, exit the SmartBackup program. Click the SmartBackup icon on the
taskbar, and select [Exit] in the window popped up, as shown in Figure 5-15.
Figure 5-15 Exit SmartBackup
11) Start up PWD service, so as to start up iGWB program and SmartBackup tool at
the same time. Select [Start/Programs/Management Tools/Service] to start up
PWD service.
Configure the backup task (bill backed up to the peer server and remote WS) for
another iGWB server in the same way as described above. Normally, the iGWB works
in dual-server mode. If the active iGWB has been configured, the standby iGWB
should be configured in the same way.
When configuring SmartBackup parameters on the standby iGWB, the parameters of

backup task to remote WS should be the same as those configured on the active
iGWB. However, some of the parameters of backup task to peer server should be
modified accordingly, such as the "Server Address" should be set as "BillSvr1."
5-16
User Manual
HUAWEI iGateway Bill Chapter 6 iGWB Maintenance
Chapter 6 iGWB Maintenance
This chapter describes the fault processing in two parts. The first part is the
introduction of common problems and their solutions in the process of iGWB
installation and operation. The second part describes the handling of common alarms.
6.1 Common Problems and Solutions
This section mainly describes the steps in analyzing, locating, and solving common
problems occurred during the process of iGWB installation and operation.
6.1.1 BillRemote NT Server not Activated, Connection Failure
Log onto the bill console. If there is a prompt: "The BillRemote service on the remote
server end is not running, connection failure", it indicates that, the BillRemote service
at the iGWB server end is not activated. The handling process is as follows:
1) Check in the directory of “C:\InetPub\wwwroot” whether Invoker.exe and
BillAll.jar files exist. If not, re-install iGWB; otherwise, proceed to step 2.
2) Check in the Services window whether the Billremote service is activated. If not,
activate the BillRemote service; otherwise, proceed to step 3.
3) Check if the fault is removed. If not, please contact Huawei engineers for
solution.
6.1.2 Incorrect User Name and Password, or Abnormal Operation of iGWB
Log onto iGWB Server. If there is a prompt: of "login failure, possible cause: wrong
username or password, or abnormal operation of iGateway Bill.", it indicates that the
user name and password are not correct, or the iGWB is not activated, or iGWB is
activated but runs abnormally (such as accidental ending of the OMM module). The
handling process is as follows:
1) Check if the user name and the password are correct. If not correct, input the
correct user name and password again, otherwise proceed to step 2.
2) Check if the iGWB server is activated, if not activated, activate the iGWB, if
otherwise proceed to step 3.
3) Check if the Operation and Maintenance Module (OMM.exe) is activated, if not
activated, activate the OMM.exe; otherwise re-start the iGWB.
6-1
User Manual
6.1.3 The Number of Users Currently Connected Reaching the Limit
Log on the bill console, there is a prompt "Too many users currently connected.
Please try later". Usually there are two possible causes.
1) The number of users connected to the bill console has reached the maximum
limit.
2) The server has not monitored the exits of users. For instance the network failure
occurs when the user exits. The server cannot monitor the "exits" of the user,
and the user number recorded at the server is not changed.
The handling method is as follows:
Check if the number of users currently connected has reached the maximum limit (the
default subscriber number in connection is 5). If it has reached the maximum number,
modify Config.ini\MAX_SESSION_COUNT value and restart the BillRemote. Or wait
a while (the server conducts polling once every 180 seconds, which can be modified
by re-configuring Config.ini\ MAX_SHAKE_HAND_INTERVAL value) until the
server ”finds” out the abnormally exited user (if any) and allows other user to connect.
6.1.4 Unknown Fault Occurrence, Operation Failure
A prompt "unknown fault occurs and operation fails" appears when logging on to the
bill console. This is because the iGWB server’s IP address (the first IP address of the
first network card in iGWB) and the virtual IP address are not within the same network
segment.
Re-configure the IP address to make sure they are in the same network segment. If
the problem still exists, contact Huawei's engineers for solution.
6.1.5 The Running Authority of Java's Minor Program Too Low
Log on the bill console, there is a prompt of "the monitor's Java authority is too low
and the program can not run". This indicates that the browsed iGWB server’s IP
address input in bill console is not the virtual address of the browsed iGWB server,
and the server end has not been installed with Java patch file. At this time, please
check if the browsed iGWB server’s IP address is within the same network segment
of the first IP address of the first network card. If not within the same network
segment, re-configure the IP address so that the browsed iGWB server’s IP address,
the first IP address of the first network card, and the virtual IP address are within the
same network segment. If the problem still exists, contact Huawei’s engineers for
solution. Please install Java patch file for the iGWB server and input correct iGWB IP
address in the bill console.
6-2
User Manual
6.1.6 Bill Server's Initial Interface Cannot be Displayed
When IE is used to browse the iGWB sever, use IE in the bill console, there occurs
the fault of "this page cannot be displayed". This is because WWW server is not
started. Run [Start/Programs/Management Tools/Service] to see if the WWW
service state is "running". If no, start WWW server, otherwise re-install IIS.
6.1.7 Connection to iGWB Server not Successful
When IE is used to browse the iGWB server, use IE in the bill console, the connection
to the iGWB server cannot be successful. The fault reason might be that the IE
browser is set with a proxy or the network between the user end and the server is not
through. At this time proceed as following steps.
1) Check if the network between the user end and the iGWB server is in connection.
If not connected, check the lines to ensure the network is well connected and
re-configure the network, otherwise continue step 2.
2) Check if the browser is set with a proxy, if yes, remove the proxy. The proxy
removing steps are:
IE5: tool->Internet options-> connect-> LAN configuration. Remove the proxy in the
box in front of "user proxy server".
IE4: queryview->options -> connect, remove proxy.
If the problem still exists, please contact Huawei's engineers.
6.1.8 Fault Occurs When Starting BillRemote Server
When starting BillRemote, the following fault occurs: "can not start \\billsvr\ BillRemote
Service. The fault 0203: the operation system cannot find the input environment
options". Billsvr stands for iGWB server name.
There are two causes for this problem:

1) C:\INETPUB\wwwroot\Invoker.exe or BillAll.jar files are lost, or wrong registration
table.
2) The user has run C:\InetPub\wwwroot\go.bat file to start the BillRemote service.
At this time, if the BillRemote Service is restarted in the "control panel->service",
the fault also occurs.
Please follow the following steps to remove the faults.
1) Check if Invoker.exe or BillAll files are lost, if yes, re-install iGWB, otherwise
proceed to step 2.
2) Check the registration table ([HKEY_LOCAL_MACHINE\SYSTEM\
CurrentControlSet\Services\BillRemote\Parameters] "AppParameters"=
"-Djava.security.manager -Djava.security.policy=BillRemote.policy -classpath
6-3
User Manual
rt.jar; BillAll.jar; com. huawei. billserv.server. StartFromHere",

"Application"="java") to see if it is correct. If not correct, modify and correct it
according to the above configuration, otherwise continue step 3.
3) Check if C:\InetPub\wwwroot\go.bat is running. If so, stop the operation of
C:\InetPub\wwwroot\go.bat file, and then re-start BillRemote Service. If the
problem still exits, contact Huawei's engineers.
6.1.9 After Upgrading, the User End Interface Cannot Display Normally
After iGWB is upgraded, the user end interface is not upgraded and the display is
abnormal. This is because after the upgrading of iGWB, the files of the previous
version (usually under the temporary file directory C:\WINNT\ Temporary Internet
Files) have not been deleted, and IE has not checked the latest version of the iGWB
server. So the bill console is still of the previous version, or the log-on interface is
abnormal.
At this time please re-configure the IE options.

1) As for IE5, open the explorer, and select [tool->Internet options->senior->safe].
2) Select "clear Temporary Internet Files when shut down", and click <OK> button
to shut down the explorer.
3) Restart the explorer and the bill console restores to normal condition.
To avoid such a problem, this option should be set at user end before the iGWB of the
user end is upgraded.
6.2 Various Alarms and Processing
6.2.1 Fault and Event Alarm
We can view the alarm information generated by iGWB via the alarm console of the
WS. The alarms of iGWB can be classified into two types: fault alarm and event alarm.
The fault alarm includes insufficient disk space, the billing center not fetching bills for
a long time, interrupted heartbeat between active and standby iGWB servers,
active/standby iGWB server switchover, abnormal iGWB serial port, and interrupted
connection between active and standby iGWB serverss. The event alarm includes
failures in writing bill files.
6-4
User Manual
I. Disk Space Insufficient
Alarm Name Alarm parameter Server number Alarm level Alarm type
0==Disk (master) storing original bill 0==Active iGWB
files; (Server A);
Disk space
Critical alarm Fault alarm
insufficient 1==Disk (slave) storing final bill files; 1==Standby
2==MO storing backup bill files iGWB (Server B)
Note: The alarm parameter 2 only applies to the backup modes presented in Appendix B, which backup bill to local
hard disk of iGWB Server (or other medium on iGWB Server).
The minimum space of the master disk for alarms is specified by the key value of
HKEY_LOCAL_MACHINE\SOFTWARE\HUAWEI\BillSvr\FrontSaveModu\MiniAlarmR
oom in registry. The unit of this key value is M. When the available space of master
disk is less than the minimum space specified by this key value, the iGWB will
produce the disk space insufficient alarm, with the alarm parameter of 0.
The minimum space of the slave disk for alarms is specified by the key value of
HKEY_LOCAL_MACHINE\SOFTWARE\HUAWEI\BillSvr\BackSaveModu\MiniAlarmR
oom in registry. The unit of this key value is MB. When the available space of slave
disk is less than the minimum space specified by this key value, the iGWB will
produce the disk space insufficient alarm, with the alarm parameter of 1.
The minimum space of MO for alarms is 20MB. When the available space of MO is
less than this minimum alarm space, the iGWB will produce the disk space insufficient
alarm, with the alarm parameter of 2.
Two kinds of factors cause the active/standby disk space insufficient:

1) The key value of Final\BillStoreDays or Orig\BillStoreDays under
HKEY_LOCAL_MACHINE\SOFTWARE\HUAWEI\BillSvr\BackupModu\ in the
registry (these two key values specify respectively the days of storing the original
bill files and final bill files in the master/slave disks) is too large, causing the
pileup of bill files in the master/slave disks.
2) The bill file collector of the billing center has not fetched the bill files in time,
causing the pileup of bill files in the master/slave disks.
After the alarm of disk space insufficient occurs, if corresponding manual interference
is not performed, it will probably cause the following alarms after a period of time:
z When the available spaces of master/slave disks are less than the 1/5 of the
minimum alarm space, the alarm of active/standby iGWB server switchover will
occur.
z When the space of MO is not available, the backup of bill files will fail, which
results in the event alarm of writing bill files failed.
6-5
User Manual
After the fault alarm of disk space insufficient occurs, handle in the following ways to
remove this alarm:
1) Determine which server (active iGWB or standby iGWB) produces this alarm
according to the server number.
2) Determine which disk has the insufficient space according to the alarm
parameter. If the parameter is 0 or 1, go to Step 3. If the parameter is 2, go to
Step 6.
3) Reduce the key value of Final\BillStoreDays or Orig\BillStoreDays under
HKEY_LOCAL_MACHINE\SOFTWARE\HUAWEI\BillSvr\BackupModu\ in the
registry.
4) Determine those bill files that have been backed up via the bill console, and then
delete those bill files.
5) If it is the slave disk that has insufficient space, inform timely the billing center to
fetch the final bill files or delete the old needless bill files.
6) Take out the current MO, and replace it with a new usable MO.
II. Billing Center Not Fetching Bills for a Long Time
Alarm
Alarm name Server number Alarm level Alarm type
parameter
Billing center not 0==Active iGWB (Server A);
fetching bills for a long None Critical alarm Fault alarm
time 1==Standby iGWB (Server B)
If the key value of HKEY_LOCAL_MACHINE\SOFTWARE\HUAWEI\BillSvr\

BackSaveModu\IsGSM in the registry is 1, it indicates iGWB is compatible with Bill
Administrator Unit (all the following contents aim at this status). Only with this kind of
configuration is it able to produce this kind of alarm.
If HKEY_LOCAL_MACHINE\SOFTWARE\HUAWEI\BillSvr\BackSaveModu\
FetchFileTimeOut exists in the registry, its key value will specify a time (time of
timeout in unit of minute). If during this period the billing center does not fetch bills,
the iGWB will produce the alarm of "billing center not fetching bills for a long time". If
the time of timeout is not specified in the registry, the time of timeout is 30 minutes by
default.
The key value of HKEY_LOCAL_MACHINE\SOFTWARE\HUAWEI\BillSvr\BackDIR in

the registry specifies the root directory of storing final bill files, e.g., E:\BillBack. For
each channel, iGWB opens specific sharing directory storing the final bill files for
billing center The hierarchy of this directory is "root directory\backdatabak\channel
sub-directory". Suppose the root directory of storing the final bill files is E:\BillBack,
and iGWB has two channels, then the directories open to the billing center are:
E:\BillBack\backdatabak\Chl_1\
6-6
User Manual
E:\BillBack\backdatabak\Chl_2\
The main factors causing this fault alarm are:

1) The charging collector of billing center has not logged in iGWB and fetched bill
files.
2) The fault occurs in the network between iGWB the collector.
After this fault alarm occurs, if corresponding manual interference is not performed, it
will probably cause the alarm of slave disk space insufficient.
To remove this alarm, handle in the following ways:

1) Determine which server (active iGWB or standby iGWB) produces this alarm
according to the server number.
2) Determine whether FTAM or FTP service is running normally.
3) Use the common network testing tool to test whether the network between iGWB
and the bill collector is normal. If the network link fails, check whether network
hardware is normal.
4) Use the explorer to view the bill files under the directory open to the billing center,
and determine whether the timeout bill file that the billing center has not fetched
exist. If so, and if the FTAM or FTP service is normal and the network link
between the iGWB and the billing center is normal, inform the billing center to
fetch the bill file.
III. Active/Standby iGWB Server Heart-beat Interrupt
Alarm
Alarm name Alarm parameter Server number Alarm level
type
Active/standby 0==Active iGWB (Server A); Fault
iGWB server None Major alarm
1==Standby iGWB (Server B) alarm
heart-beat interrupt
Set the heartbeat path in the registry. Set the first heartbeat path under
HKEY_LOCAL_MACHINE\SOFTWARE\HUAWEI\BillSvr\Cluster\Link\1. LocalIP
specifies the local (active/standby iGWB server) IP address of the heartbeat path.
ServerIP specifies the remote (active/standby iGWB server) IP address of the
heartbeat path. Set the second heartbeat path under HKEY_LOCAL_MACHINE\
SOFTWARE\ HUAWEI\BillSvr\Cluster\Link\2 as follows: LinkType="COM",
Port=0x00000001, that is, specify COM1 as the second heartbeat path.
The iGWB has the timing detection mechanism for the heartbeat signals. If in the
specified time interval (this time interval is specified by the key value of
HKEY_LOCAL_MACHINE\SOFTWARE\HUAWEI\BillSvr\Cluster\ HeartbeatTimeOut
in the registry, with the unit of second), no heartbeat signals are received from the
remote iGWB server, this alarm will occur. The heartbeat signal interrupt will cause
6-7
User Manual
such phenomena as the active/standby iGWB server cannot be synchronous and

both iGWB server are active, etc.
The relevant alarms occurred prior to the occurring of this alarm include abnormal
iGWB server serial port and interrupted connection between active and standby
iGWB servers.
Handle this fault alarm in the following ways:

1) If the iGWB server serial port abnormal alarm occurs, refer to corresponding
solutions in section 6.2.5.
2) If the alarm for interrupted connection between active and standby iGWB servers,
refer to corresponding solutions in section 6.2.7.
IV. Active/Standby iGWB Server Switchover
Alarm name Alarm parameter Server number Alarm level Alarm type
Active/standby 0==Active iGWB (Server A);
iGWB server None Critical alarm Fault alarm
switchover 1==Standby iGWB (Server B)
The factors causing this fault alarm mainly include:

1) The available space of active/standby disk is less than 1/5 of the minimum space.
See section 6.2.1.
2) iGWB cannot write the bill data in bill files. See section 6.2.6.
3) The communication between iGWB and GSPC board is abnormal. When the
number of socket connections of both network adapters connecting iGWB and
GSPC board remains at "0" for a certain period of time (10 minutes), the
connection with GSPC is regarded as abnormal.
The alarms that occur almost simultaneously with this alarm include the disk space
insufficiency alarm and writing bill files failure alarm.
After this alarm occurs, handle it in the following ways:

1) View whether the alarm of disk space insufficiency occurs, refer to
corresponding solutions in section 6.2.1.
2) View whether the alarm of writing bill files failure occurs, refer to corresponding
solutions in section 6.2.6.
3) Check the status of connection with GSPC (execute "netstat" in the command
line mode). If connection to GSPC board fails, check in the data management
console the data configuration and whether the network hardware connection
between iGWB and GSPC is correct.
6-8
User Manual
V. iGWB Serial Port Abnormal
iGWB serial port 0==Active iGWB (Server A);

None Major alarm Fault alarm
abnormal 1==Standby iGWB (Server B)
COM1 is the second heartbeat path between the active and standby iGWB servers.
This heartbeat path is set under
HKEY_LOCAL_MACHINE\SOFTWARE\HUAWEI\BillSvr\Cluster\Link\2 in the registry.
LinkType="COM", Port=0x00000001, that is, the COM1 is specfied as the second
heartbeat path.
There is the timing detection mechanism for COM1 heartbeat path. If no signal can be
received from COM1 in the specified time, this alarm will occur. After this alarm
occurs, iGWB attempts to send the heartbeat signal to the remote via COM1.
The factors causing this alarm mainly include:

1) The remote iGWB server is not running.
2) COM1 is damaged.
3) The serial port line connecting the COM1s of the active and standby iGWBs is
damaged.
4) The serial port line is connected incorrectly (connect to the COM2s of
active/standby iGWB) or is not connected.
After this alarm occurs, handle in the following ways:
1) Determine which server (active or standby iGWB) produces this alarm according
to the server number.
2) View whether the remote iGWB server is running. If the remote iGWB has
stopped running, start the process "Kernel.exe" of the remote iGWB server.
3) Check whether the serial port line has been connected to the COM1s of
active/standby iGWB. If not, connect it to COM1 correctly.
4) In Windows 2000, Select [Start/Programs/Administrative Tools/Computer
Managmen/Device Manager/Port(COM&LPT)] and double click
"Communications Port(COM1)" to check whether the status of COM1 device on
the active/standby iGWB is normal.
5) Use such tools as the multimeter to check whether the serial port line is
available.
6-9
User Manual
VI. Writing File Failed Alarm
0==Writing original bill files to master
disk failed; 0==Active iGWB
Writing bill 1==Writing final bill files to slave disk (Server A); Event
Major alarm
files failed failed; 1==Standby iGWB alarm
2==Writing backup bill files to.MO (Server B)
failed;
Note: The alarm parameter 2 only applies to the backup modes presented in Appendix B, which backup bill to local
hard disk of iGWB Server (or other medium on iGWB Server).
The iGWB will check whether the writing to disk is successful each time. Once the
writing failed, it will generate this alarm.
The factors causing this alarm mainly include disk space insufficiency, bad track on
the disk, and unformatted disk.

1) Determine which server (active or standby iGWB) produces this alarm according
to the server number.
2) If the alarm parameter is 2, check whether there is disk in the MO drive, whether
the disk has been formatted, whether the disk has free space, and then perform
corresponding processing.
3) If the alarm parameter is 0 or 1, check whether the corresponding disk space is
sufficient, and whether the disk is physically damaged.
VII. Active/Standby iGWB Server Private Network Interrupt
Active/standby 0==Active iGWB (Server A);
iGWB server private None Major alarm Fault alarm
network interrupt 1==Standby iGWB (Server B)
The private network (the network adapter connecting to the WS) is the first heartbeat
path between the active and standby iGWBs. The first heartbeat path is set under
HKEY_LOCAL_MACHINE\SOFRWARE\HUAWEI\BillSvr\Cluster \Link\1 in the
registry. LocalIP specifies the local (active/standby iGWB) IP address of the heartbeat
path. ServerIP specifies the remote (active/standby iGWB) IP address of the
heartbeat path.
There is the timing detection mechanism for this heartbeat path. If no signal can be
detected from the private network in the specified time, this alarm will occur. After this
6-10
User Manual
alarm occurs, the standby iGWB server will still try to connect with the active iGWB
server, and the active iGWB server still wait for the connection with the standby iGWB
server.
The factors causing this alarm mainly include:

1) The configurations of LocalIP and ServerIP in the registry are incorrect.
2) The network is connected incorrectly.
3) The remote iGWB server is not running.
1) View whether the remote iGWB server is running. If the remote iGWB server has
stopped running, start the process of Kernel.exe of the remote iGWB server.
2) View the LocalIP and ServerIP in the registry of active/standby iGWB server is
set as follows: LocalIP of active iGWB = ServerIP of standby iGWB; LocalIP of
standby iGWB = ServerIP of active iGWB.
3) Check whether the network physical connection is correct.
6.2.2 Resource Unavailable
The required resources for iGWB running include the FTP or FTAM service, the IP
address resource for connecting console, the IP address resource for connecting the
billing center, and disk array resource.
I. Service Resources Unavailable
Alarm name Alarm parameter Alarm level Alarm type

0: FTP service
Service unavailable 2: WWW service Critical alarm Fault alarm
3: BillRemote service
Main reasons causing this alarm: FTP or FTAM services cannot be started (WWW or
BillRemote service invalid may lead to this alarm).
If relevant services are not installed or cannot be started, then refer to section
"Installation Guide" to install the services correctly.
II. IP Address Unavailable
IP address 0==IP address for connecting OMC unavailable;

Critical alarm Fault alarm
unavailable 1==IP address for connecting billing center unavailable
6-11
User Manual
This alarm occurs when the fault happens in active virtual IP. The reason of this alarm
mainly is Network adapter failure.
After this alarm occurs, check the network adapter by using the PING program to find
out the bad network adapter and replace it.
III. Disk Array Resource Unavailable
Alarm Name Alarm parameter Alarm level Alarm type

0= Drive 1 on the disk array storing the original bill
Disk array Critical
files = drive on the disk array storing the final bill Fault alarm
unavailable alarm
files
If the disk array resource is unavailable, the following methods are recommended:
1) Check whether there is any program operating on the disk array. If so, close the
program.
2) Check whether the cable connecting to the disk array is loose.
3) Check whether the disk array card is damaged.
6.2.3 Backup-related Alarm
Note:
The following types of alarms only apply to the backup modes presented in Appendix B ( backup of bill
files to local hard disk of iGWB Server or other media on iGWB Server).
I. Backup Media Nonexistent

1==MO 1 nonexistent;
Backup media 2==MO 2 nonexistent;

Critical alarm Event alarm
nonexistent 3==Tape 1 nonexistent;
4==Tape 2 nonexistent
The factor causing this alarm is that there is no corresponding backup media in the
backup equipment.
After this alarm occurs, perform the following operations: determine which equipment
has no backup media according to the alarm parameter, and then place the
corresponding backup media in this equipment.
6-12
User Manual
II. Bills not Backed up in Specified Time Existed

0==Original bill files not backed up
Bills Not Backed up in existed; Critical alarm Event alarm
Specified Time Existed
1== Final bill files not backed up existed
The main cause of this alarm is: The user selects auto or semi-auto mode to backup,
but does not configure the backup path correctly. Or the backup media is not in
normal condition. There are too many bill files not backed up before the due time.
After this alarm occurs, start the backup process in the bill console to back up the bill
files that are not backed up.
6-13
User Manual
HUAWEI iGateway Bill Appendix A Installation of Operating System
Appendix A Installation of Operating System
This chapter introduces the configuration of the Redundant Arrays of Inexpensive

Disks (RAID) of the iGWB server, as well as the installation of the operating system.
Before iGWB server is delivered, the RAID has been configured and the operating
system has been installed already. Therefore, this appendix is for reference only.
A.1 Preparations for Installation
A.1.1 Prepare the Installation CD
The following software installation CD or installer is required for installation.

z Dell OpenManage Server Assistant Bootable CD
z Windows 2000 Service Pack 3 or later version
A.1.2 Check Hardware Configurations of the Server
Adopting dual-server configuration with local RAID, the iGWB can be equipped with
two DELL PowerEdge2650 (DELL PE2650 for short) servers or other servers of the
same performance.
Basic hardware configuration of the server (please refer to the packing list for the model
and hardware configuration of the server):
The basic hardware configuration of DELL PE2650 includes:

z CPU: 1* Intel Xeon 2.4 GHz or higher CPU
z Hard disk: 2 (or 5)* 36.4 GB hard disks
z Memory: 512 MB
z Network adapter: Four network adapters. Two of them are the integrated network
adapter on main board. The rest are Intel Fast Ethernet LAN Controllers.
z RAID: 1* PERC 3/Di.
z CD-ROM: 1* CD/DVD-ROM
z Floppy Drive: 1* 3.5’’ floppy drive
Before the operating system is installed, check whether the basic configuration of the
hardware is complete (especially the number of network adapters and hard disks),
since it is essential to the software installation followed.
A-1
User Manual
Note:
The model of the server may be different from those mentioned above. If so, relevant driver will be
provided for installation.
A.1.3 Adjust BIOS Setup
To any server, the setup of the Basic Input/ Output System (BIOS) is essential to both
the startup of the server and the installation of the operating system. Therefore, it is
necessary to adjust the setup of the BIOS before installing the operating system.
For the server DELL2650, the BIOS should be adjusted as below:
I. Start up the server and press <F2> to enter the CMOS setting.
II. Set "Report Keyboard Errors" to be "Do Not Report".
III. Set “Boot Sequence”.
1) CD-ROM device
2) Hard drive C:
3) Diskette drive A:
IV. Save the modifications, and reboot the server.
Caution:
Select the default value for other options of the BIOS setup.
A.2 iGWB Server Hardware Configuration
The Dell PowerEdge 2650 server is delivered together with three CDs:
z Dell OpenManage Server Assistant Bootable CD
z Dell OpenManage Systems Management
z Product Documentation
Using these three CDs, you can easily install the operating system, manage the server
and query documents. Herein, the Dell OpenManage Server Assistant Bootable CD is
a bootable CD. You must use this CD for some configurations before installing
Windows 2000 Server.
A-2
User Manual
I. Starting up the server
Start up the server, and insert the Dell OpenManage Server Assistant Bootable CD into
the CD-ROM to boot the system.
II. Run DELL OpenManage Server Assistant
The DELL OpenManage Server Assistant on the CD runs after the system is started.
The main page of DELL OpenManage Server Assistant appears where you can choose
the language for the program, for example, Chinese. Click the area “Click here for
server setup” to go to the next page.
Set the date and time, enter the "Set the Date and Time” page to set the proper Date,
Time and Time Zone. Then, click <Continue> to go to the next page.
III. Configure RAID
Enter the “Configure RAID” page where the summary of all available RAID
configurations of the server is listed.
In “Configure RAID?”, select [Configure RAID] and then click <Continue> to go to the
next page.
Note:
Any delivered iGWB server must be configured with two or five hard disks. In case of two hard disks, they
are configured as RAID1; in case of five hard disks, four of them are configured as RAID5 and one works
as the hot backup disk. This is called local disk array, through which the whole system becomes more
reliable. The disk array composed of two or five hard disks equals a physical hard disk for the operating
system, and is partitioned into three logical partitions, drive C, D and E. Drive C is used for installing the
operating system, drive D for storing bill files and drive C for storing the final bill files to be provided to the
billing center.
1) Create Virtual Disk Wizard (1 of 2 steps) — PERC 3/Di

Enter the “Create Virtual Disk Wizard”. Select [RAID 1] or [RAID 5] as the RAID level
from the “Select virtual disk properties” list. Then, click <Continue> to go to the next
page.
2) Create Virtual Disk Wizard (2 of 2 steps) — PERC 3/Di
The “Virtual Disk Property Summary” appears, listing the RAID level you have set in the
last step (either RAID 1 or RAID 5), virtual disk size and the selected array disk
information.
A-3
User Manual
Click <Continue>, a message box pops up, prompting “All existing virtual disks on this
controller will be deleted and all data will lose”. Click <OK>, and the DELL
OpenManage Server Assistant begins to create virtual disks. In a few seconds, the
creation is completed and you are navigated to the next page.
IV. Selecting the operating system
Enter the “Select Operating System to Install” page where you should select “Microsoft
Windows 2000 Server” from the list. Then, click <Continue> to go to the next page.
V. Configuring hard disk driver
Enter the “Configure Hard Driver” page where you should set the file system of the boot
partition and its size. Select “NTFS-NT file system” from the “Select File System for
Boot Partition” list, and then select the default value 4096 in the “Booting partition size”.
Click <Next> to go to the next page.
VI. Configuring the network adapter
Enter the “Network Adapter Configuration” page. First, select “Obtain IP address from
DHCP server” because the IP address of the network adapter is configured after the
operating system is installed. Then, click <Continue> to go to the next page.
VII. Entering configuration information
Go to the “Enter Microsoft 2000 Server Configuration Information” page. The basic
information of the operating system includes:
z Language: Select “Simplified Chinese”;
z Organization: Determine according to actual conditions, for example, “HUAWEI”;
z User Name: Determine according to actual conditions;
z Product ID: CD KEY of the Microsoft Windows 2000 Server CD;
z Computer Name: Determine according to actual conditions, for example, “IGWB1”
and “IGWB2”;
z Installation Directory: Use the default value, “Winnt”;
z License Type: Select the “Per-server” mode, and the client license is 20.
Check “Join WorkGroup” on the lower part of the page and fill in the workgroup name;
Click <Continue> to go to the next page.
VIII. Operating system installation summary
Enter the “Operating System Installation Summary” page where some parameters you
have set are displayed, as shown in Table A-1. Click <Continue>, and the DELL
OpenManage Server Assistant copies all the required device drivers for Windows 2000
A-4
User Manual
installation to the hard disk. In subsequent installation, the Windows 2000 Installer will
invoke these drivers to install devices automatically.
Table A-1 Operating system installation summary
System Dell 2650

Operating system Microsoft Windows 2000 Server
File system boot environment NTFS
Primary partition size 4096MB
Utility partition size 32MB
Installation disk Hard Disk on PERC 3/Di
IX. Windows installation wizard
After the device drivers are copied, you are navigated to the “Windows Installation
Wizard” page. Insert the Microsoft Windows 2000 Server installation CD as prompted,
and the DELL OpenManage Server Assistant begins to copy the Windows 2000
installation files to the hard disk.
In about some minutes, the message “File copied” pops up. Take out the installation CD,
and then click <Finish> to reboot the system.
A.3 Operating System Installation
The software installed in iGWB includes

z Windows 2000 Service Pack3 or higher version
z IE5.5 or later version
z FTAM installation software (optional)
z iGWB installation software (including Java Runtime Environment)
In this chapter, the installations of the first two items are introduced. Please refer to
A.3.4 for the installation of IE5.5, and Chapter 2 Installation Guide for the installation of
FTAM and iGWB applications.
A.3.1 Install Windows 2000 Server
I. Installing Windows 2000 Server
Insert the Windows 2000 Server CD as prompted and click <Next>. The installation of
Windows 2000 begins immediately.
A-5
User Manual
Sufficient information has been collected in above procedure, so the Windows 2000
operating system will be installed automatically. During the installation, the server may
be restarted several times.
A.3.2 Install Internet Information Service (IIS)
1) Restart the Windows OS, insert Windows 2000 Server (CD). Select
[Start/Settings/Control Panel]τ"Add/Remove programs"τ"Add/Remove Windows
Components".
2) Select "Internet Information Services (IIS)" from the [Windows Components
Wizard] dialog box popped up. Click <Details>.
3) Select the components to be installed. Currently, except "NNTP Service", "SMTP
Service" and "Visual InterDev RAD Remote Deployment Support", all the other
components should be selected. Click <OK>.
4) Click <Next> in the next interface popped up, the components will be installed one
by one automatically.
A.3.3 Install Windows 2000 Service Pack 3
To ensure normal system operation after Window 2000 is installed, it is necessary to

install the patch program Windows 2000 Service Pack 3 (W2Ksp3en.exe) of Windows
2000.
1) Setup wizard
First, unpack Windows 2000 Service Pack 3 setup program, then pop up the setup
wizard, as shown in Figure A-1.
Figure A-1 Windows 2000 SP3 setup wizard
A-6
User Manual
Click <Next> to continue.

2) Confirm license agreement
The License Agreement confirmation interface will pop up, as shown in Figure A-2.
Figure A-2 License Agreement interface
Please carefully read this agreement and select "I Agree", and then click <Next> to
continue.
3) Install options
The interface [Select Options] pops up, as shown in the Figure A-3.
A-7
User Manual
Figure A-3 Select options
To uninstall SP3, select the recommended option "Archive Files". Click <Next> to
continue.
4) Update system
Interface [Update Your System] will pop up, as shown in Figure A-4.
Figure A-4 Check system configuration
The SP3 setup program starts to backup original system files, then to update the
system. The whole process takes several minutes.
A-8
User Manual
5) Complete patch program installation

After SP3 is installed, the setup wizard interface pops up, as shown in Figure A-5.
Figure A-5 Installation of SP3 setup wizard completed
Click <Finish> to restart the server to validate the updated Windows 2000 Service Pack
3.
6) Check patch version
Select the menu [Start/Settings/Control Panel] and run "System" in the control panel.
Select [General] tab from the popup interface, as shown in Figure A-6.
A-9
User Manual
Figure A-6 System properties
Check whether "Service Pack 3" is included in the "System" content list of the interface.
If this item exists, the patch program has been successfully installed.
Note:
After installing Microsoft Windows 2000 Server, adjust the BIOS setup, and set the startup sequence of the
server.
z Hard drive C:
z CD-ROM device
z Diskette drive A:
Please refer to A.1.3 Adjust BIOS Setup for details.
A.3.4 Install IE5.5
The IE5.5 is required to ensure normal operation of the iGWB server. Thus, you need to
upgrade the inbuilt IE5.0 of Windows 2000 Server to 5.5.
1) Start setup
A-10
User Manual
Run the IE5.5 setup to start the installation wizard.

2) Confirm license agreement
The “Supplement End User License Agreement for Microsoft Software” pops up, as
shown in Figure A-7.
Figure A-7 License agreement
Select [I accept the agreement], and click <Next>. The interface shown in Figure A-8
pops up.
A-11
User Manual
Figure A-8 Installation content

3) Install progress
The setup starts to copy files. After all files are copied, the grayed <Next> is activated.
4) Complete installation
After the installation is completed, click <Finish> to restart the computer.
A.3.5 Configure Network Adapter IP Address
During Windows 2000 system installation, the network adapters can be automatically
installed without manual intervention. The following example describes the
configuration method of network adapter IP addresses.
1) Activate network connection
Click the menu [Start/Settings/Control Panel] and select "Network and Dial-up
Connections". In the network connections, select the ones for which IP addresses will
be configured, as shown in Figure A-9.
A-12
User Manual
Figure A-9 Connection status
Click <Properties> to continue.

2) Set connection properties
The interface [Properties] pops up, as shown in Figure A-10.
A-13
User Manual
Figure A-10 Connection properties
Select "Internet Protocol (TCP/IP)" and click <Properties> to continue.

3) Set IP address
The interface [Internet Protocol (TCP/IP) Properties] pops up, as shown in Figure A-11.
A-14
User Manual
Figure A-11 Internet protocol (TCP/IP) properties
Select "Using the following IP Address", and set the corresponding IP address, subnet
mask and default gateway.
Multiple IP addresses can be set if necessary: select <Advanced> button in Figure A-11
to enter advanced IP addressing interface, then click <Add> to add IP address and
subnet mask.
Click <Ok> to complete IP address setting.
A.3.6 Hard Disk Partition
The hard disk can be divided into three logical hard drives: C, D and E, all in the NTFS
format.
z Drive C is used as the system drive, used for the installation of Windows 2000
Server.
z Drive D is used to store original bill files.
z Drive E is used to store final bill files for the Billing Center.
A-15
User Manual
The size of each logical partition can be defined as per the following rule: Drive C is
always set as 4G, while the sizes of the rest drives should be defined in the following
ratio: D:E = 1:1.
The following is the procedure of setting partition and drive letters according to the
above rule.
1) Start the program "Computer Management"
Select [Start/Programs/Administrative Tools/Computer Management] to pop up the
interface [Computer Management], as shown in Figure A-12.
Figure A-12 Computer management
From the tree on the left, select “Storage/Disk Management", then the current partition
status of the server will be displayed on the right, as shown in Figure A-12.
2) Change CD-ROM drive letter
Select the CD-ROM drive, right click and select "Change Drive Letter and Path" in the
shortcut menu to pop up the dialog box "Change Drive Letter and Paths for (D:)", as
shown in Figure A-13.
A-16
User Manual
Figure A-13 Change drive letter and paths for (D:)
Click <Edit> to pop up the interface [Edit Drive Letter or Path], as shown in Figure A-14.
Figure A-14 Edit drive letter or path
Specify the CD-ROM drive as drive "F", and click <OK> to pop up the dialog box
[Confirm], as shown in Figure A-15.
Figure A-15 Confirm dialog box
Click <Yes> to confirm the setting, then the drive letter is successfully changed.
3) Create extended partitions
Select the "Unallocated" area in "Disk 0", as shown in Figure A-12. Right click and
select "Create Partition" in the shortcut menu, then "Create Partition Wizard” is
activated, as shown in Figure A-16.
A-17
User Manual
Figure A-16 Create partition wizard

4) Select partition type
The interface [Select Partition Type] pops up, as shown in Figure A-17.
Figure A-17 Select partition type
Select "Extended partition" and click <Next> to continue.

5) Specify partition size
A-18
User Manual
The interface [Specify Partition Size] pops up, as shown in Figure A-18.
Figure A-18 Specify partition size
Select the default value, i.e. the maximum value of the disk space. Then click <Next> to
continue.
6) Complete partition creation
The interface [Completing the Create Partition Wizard] pops up, as shown in Figure
A-19.
A-19
User Manual
Figure A-19 Completing the Create Partition Wizard
Make sure the creation is correct, and then click <Finish> to complete the creation. The
[Computer Management] interface will pop up as shown in Figure A-20.
A-20
User Manual
Figure A-20 Computer management
You may see that the status of "Unallocated" area of “Disk 0” shown in Figure A-12 has
changed into "Free Space".
7) Create logical drives
Select the "Free Space" area in Figure A-20, right click and select "Create Partition" in
the shortcut menu. Activate "Create Partition Wizard", as shown in Figure A-16, then
click <Next> to continue.
8) Select partition type
The interface [Select Partition Type] pops up, as shown in Figure A-21.
A-21
User Manual
Figure A-21 Select partition type
Select ”Logical Drive” and click <Next> to continue.

9) Specify partition size
The interface [Specify Partition Size] pops up, as shown in Figure A-22.
Figure A-22 Specify Partition Size
Enter about half of total space in the field "Amount of disk space to use", click <Next> to
continue.
A-22
User Manual
10) Specify drive letter or path

The interface [Assign Drive Letter or Path] pops up, as shown in Figure A-23.
Figure A-23 Assign drive letter or path
Assign drive letter "D:" for the logical drive currently created, then click <Next> to
continue.
11) Format partition
The interface [Format Partition] pops up, as shown in Figure A-24.
A-23
User Manual
Figure A-24 Format partition
Select "Format this partition with the following settings:" and keep the default settings
for all parameters in the column "Formatting". Then click <Next> to continue.
12) Complete logical drive creation
The interface [Completing the Create Partition Wizard] pops up, as shown in Figure
A-25.
A-24
User Manual
Figure A-25 Completing the Create Partition Wizard
Make sure the creation is correct and click <Finish> to complete logical drive creation.
Now the logical drive D is successfully created.
Follow the above steps to create logical Drives E. Allocate all the rest space for Drive E.
A-25
User Manual
HUAWEI iGateway Bill Appendix B Bill Backup
Appendix B Bill Backup
In addition to providing SmartBackup tool, the iGWB application software also

supports backing up bills via local hard disk of iGWB server or external devices such
as MO on iGWB server. In such case, iGWB server should be configured with
external devices, such as MO drive.
The user may select the proper backup mode as needed. Since the quality of MO
backup mode is not so reliable, the SmartBackup tool is recommended for the
backup.
Note:
This appendix introduces the backup mode via external devices such as MO of iGWB server (or local
hard disk of iGWB server). When this mode is used, the backup modes of original and final bills in the
iGWB Config tool should be set as “Automatic” or “Manual” and the path of backup status files should be
designated.
B.1 Purpose
The purpose of bill backup is to store bills of a period of time in the backup medium.
The backup bills are used to recover the data only when the bills in the Billing Center
are damaged and iGWB is required to provide the bills again which no longer exist in
the iGWB. If these bills exist in the iGWB, they can be backed up at the iGWB and
sent to the Billing Center.
Under some special circumstances, the backup bill will be sent to the Billing Center
for charging. In such a case, two copies of the bill must be backed up, one is sent to
the Billing Center, and the other is saved and kept for long time. The multiple backup
method is introduced later in this section.
B.2 Bill Backup Types
There are two backup modes: automatic backup and manual backup; and there are
also two backup modes according to the backed up bill objects: original bill backup
and final bill backup.
B-1
User Manual
iGWB automatic backup can be in two modes according to the starting mode: i.e.,
automatic backup able to be regularly started by iGWB, or to be started by the user
through the bill console, which is called completely automatic backup; and automatic
backup that can be started only by the user through the bill console, which is called
the semiautomatic backup.
Bill backup includes complete backup and scattered backup according as how and
why the backup is made. Complete backup means backing up all bills in iGWB, and
scattered backup means backing up only some bills in iGWB. Complete backup is the
major backup mode intended to ensure the data security of iGWB. The bills backed
up are stored for a longer period or sent to the billing center for charging. Complete
backup can be performed either automatically or manually. Scattered backup can only
be performed manually, and the bills backed up are mainly sent to the billing center
for bill recovery or for some other applications.
In iGWB, the various types of backup have some mutually repulsive relationships:
1) Manual backup cannot be run simultaneously as automatic backup.
2) For the automatic backup, full-automatic and semi-automatic backup of bills of
the same type cannot be implemented simultaneously. That is, full-automatic
and semi-automatic backup of neither original bills nor final bills can be
implemented simultaneously.
B.3 Selection of Backup Objects
According to user backup requirements, iGWB Primary Server and Secondary Server
are both configured with one or two backup drives. Each backup drive can be used to
back up original bills or final bills. Among them, original bills refer to the most original
bills received by iGWB; final bills refer to bills generated after the sorting, combination,
and processing of original bills. Final bills are those to be sent to the billing center.
The same quantity of destination backup drives should be installed at the same time
in both Primary Server and Secondary Server. This is because backup drives can be
accessed by only processors to which they belong, thus guaranteeing that there is an
available backup drive when either Primary Server or Secondary Server is the active
processor, so as to realize backup at any time.
Normally, only one backup drive needs to be installed in both Primary Server and
Secondary Server. But should this backup device be used to back up original bills or
final bills? This selection is made mainly according to the following factors:
1) As what are sent to the billing center are final bills, what the user is most
concerned with is the final bills. So, normally, the user should try as much as
possible to back up the final bills. Under this basic principle, the user can refer to
the following rules.
B-2
User Manual
2) When bills in iGWB need only to be sent to one billing center, and when there is
no big difference between the final bill format and original bill format and content,
better back up the final bills;
3) When bills in iGWB need only to be sent to one billing center, and when there is
a big difference between the final bill format and original bill format and content
(e.g., after format conversion, some data domains in original bills are omitted in
the final bills), in this case, we can select which type of bills to back up according
to the user focus. It must be pointed out here that according to the backed up
original bill data, we can restore final bill data, but the data of the former cannot
be restored according to the latter;
4) When bills stored in iGWB only need to be sent to one billing center:
If iGWB has two directories used for final bills (one directory opens to the billing
center, and the other is used to store final bills for the data source), whether to back
up original bills or final bills can be selected according to the principle above.
If iGWB has only one directory for final bills only one final bill file is kept in iGWB, and
this directory opens to the billing center. If the billing center deletes the file in iGWB
after it fetches the file from iGWB in FTP/FTAM mode, original bills should be backed
up. Since iGWB cannot control the lifetime of the final bill file in iGWB, it is
troublesome to back up the final bill file. (In principle, the billing center shouldn’t
delete the bill file in iGWB, and the bill file is cleared by iGWB itself.) If the billing
center doesn’t delete the bill file in iGWB after fetching it, the backup should be
selectively implemented according to the principle above.
5) When bills stored in iGWB should be sent to more than one billing center, usually
original bill files should be backed up, because there is only one backup device,
and it is not suitable to back up the backup final files to be sent to whichever
billing center. If it is required to back up final bills to be sent to all billing centers,
then the manual backup mode should be taken, as will be described below.
For cases where two backup drives are installed in iGWB, flexible selections can still
be made according to user requirements. We can also select a drive to back up
original bills, and another drive to back up final bills.
B.4 Configuration of Relevant Bill Backup Parameters
Bill backup parameters are introduced in the previous sections. For details, refer to
sections 3.1.2 and 3.1.3 of "3 iGWB Configuration and Software Directory Structure".
B.5 Directory Structure and Naming Rules
All the bill records are stored in iGWB in the form of bill files, and the bill records can
also be backed up in this form.
B-3
User Manual
The original bill records in iGWB are stored in files, and the size of the file can be
configured. All the original bill files are denominated and numbered together. The
name format is BXXXXXXXXX.BIL, in which X refers to the number from 0 to 9. The
serial number is from 1 to 999999999.
The original bill files are stored according to the directory, one directory each day, and
the name of directory is the date when the file is generated.
The iGWB will preprocess the original bills to generate the final bills provided
eventually for the Billing Center. The final bill records will be stored in files, and the
final bill files should be stored to the directory. Different types of files can be stored in
different directories whose name is CHL_X, in which, X is the serial number of
channels (begin from 1). There are sub-directories under each channel directory, and
there is one directory for the bill files of each day, with the directory name being the
date when the file is generated. In each channel all files are denominated and
numbered uniformly. The denomination format is "prefix+XXXXXXXX.suffix", in which
X refers to the number from 0 to 9. The serial number is from 1 to 99999999. The
prefix and suffix can be customized.
After the original bill files and the final bill files are backed up into the medium, the
directory structure stored in the backup medium is the same as that in iGWB. The
original bill files are stored in the way one date directory per day, and the final bill files
are stored in the form of Channel directory\date directory\bill file. The names of final
bill files can be configured.
B.6 Deletion of Outdated Bill Files
Outdated bill files in iGWB are deleted by iGWB itself, the days that the bill files are
kept in iGWB can be configured in the Config tool. Bill files beyond this term will be
considered as outdated.
iGWB checks and deletes the outdated bill files in iGWB at the fixed time every day.
Files to be deleted include outdated original bill files and final bill files. iGWB deletes
bill files as follows:
1) For a bill file backed up automatically (including full-automatically and
semi-automatically): If iGWB detects that the bill file has already expired and has
been backed up, it will delete this bill file. If iGWB detects that the bill file has
already expired but has not been backed up yet, it will not delete this bill file but
will give the alarm "Disk space insufficient" or "Failed to write the bill file".
Problems can be analyzed and located based on these alarm parameters. In
case of such an alarm, outdated bill files not backed up yet should be backed up.
2) For a bill file backed up manually: If iGWB detects that the bill file has already
expired, it will delete this file no matter whether the file is backed up. Therefore, if
B-4
User Manual
bill files are backed up manually, they should be backed up in time to prevent
bills not backed up from being deleted.
B.7 Backup Operation
B.7.1 Enter the Backup Interface
I. Function
The iGWB itself has no bill backup operation interface. Backup of bills can be
conducted via the bill console connected to the iGWB.
II. Access
Log in the console with correct account and password. The interface of the bill
console is shown, then click the <Bill Backup> icon in the interface to enter the main
interface of bill backup.
The main interface of bill backup is shown in Figure B-1.
Figure B-1 Main interface of backup operation
B-5
User Manual
III. Interface description
The backup types that can be operated by the users include original bill automatic
backup, final bill automatic backup and manual backup.
Note:
Only by selecting the "automatic" and "semi-automatic" in the "backup" configuration item of the iGWB
Config Tool, the original bill automatic backup and final bill automatic backup selection items appear in
the "Backup task" pull-down box of the above figure.
By specifying the backup type in the [Backup Task] of Figure B-1, the users can
perform various operations to bill file backup.
B.7.2 Automatic Backup Function
I. Function
iGWB has perfect automatic backup function. Based on such functions, the user can
very conveniently satisfy its various demands. The interface is simple, easy to
operate, thus alleviating a lot of operator burden.
Of the two automatic backup modes, completely automatic backup is more

convenient to the user.
In the completely automatic backup mode, bill backup can take place automatically
during some idle hours of the day (with little bill data, such as deep in the midnight, or
early in the morning). The starting and ending time of backup can be set according to
user demands, e.g., automatic backup of bill files of the previous day can be set at
2:00~5:00 every day, so that the daily backup won't basically need user interference.
What the user has to do is to replace some blank backup media after some certain
interval, or replace a blank medium when the backup medium is full. By adopting a
suitable backup method, bill files generated by each product using iGWB during a day
can all be stored in one storage medium, so it never occurs that the operating
personnel will be required to replace a blank medium at midnight, or the daily
automatic backup rate cannot catch up with the daily bill generating rate.
iGWB periodically backs up some important information files, which include some
status files used to restore bills. If iGWB has only one backup drive, information files
and bill files will be backed up to the same backup medium. If two backup drives are
installed, the user can select either backup drive to back up information files.
B-6
User Manual
Backed up information files are normally stored in the same backup medium as bill
files in the same period of time. Bill files and information files are stored in different
directories.
Note:
z If the user adopts the semiautomatic backup mode to back up bill files, the user must start automatic
bill backup every day via the bill console, resulting in more work for the user. But with the
semiautomatic backup, the user can designate the range of bill files to be backed up by setting the
ending point of semiautomatic backup. Besides, semiautomatic backup start at any time, which is
very flexible. The semiautomatic backup modes apply only in some special cases.
z With the automatic backup method, the user can, according to specific demands, switch
conveniently between completely automatic backup and semiautomatic backup.
II. Access
Select "Original bill auto backup" or "Final bill auto backup" in [Backup Task] in Figure
B-1. If the selected backup does not run, the following interface will appear at the bill
service console, as shown in Figure B-2.
Figure B-2 Auto backup interface when the auto backup is not running
B-7
User Manual
When the current backup is in operation, the user can view the status of the ongoing
automatic backup on the interface as shown in Figure B-2.
Under special circumstances, the user might require to stop the ongoing fully
automatic backup. To stop it, select the corresponding backup type in [Backup Task],
and then click <Stop> in Figure B-2.
To start the automatic backup immediately, select the corresponding backup type in
[Backup Task], and then click <Start> in Figure B-2. An interface of the bill service
console as shown in Figure B-3 will appear.
Figure B-3 Setting the parameters of starting automatic backup
The user may specify the ending conditions for auto backup. In the list box [End Date]
in Figure B-3, select a date as the ending condition of the automatic backup. Click
<Start> to start the automatic backup. All bill files generated before this specified date
will be backed up. And the backup will end when all the bill files conforming to the
specified period of time are backed up.
Note:
z Through the automatic backup interface, the users can switch between the fully automatic backup
mode and the semi-automatic backup mode conveniently. It is realized by selecting "Fully auto" or
"Semiauto" in the backup mode of the backup interface.
z Some exclusive backup modes are already introduced in B.2. In auto backup, the fully auto backup
and semi-auto backup of bills of the same type can not be performed at the same time. That is, the
fully auto backup and semi-auto backup of original bills can not be performed at the same time, and
that of final bills can not be performed at the same time either.
B-8
User Manual
B.7.3 Manual Backup
I. Function
The user can adopt manual backup method to backup all the bill files in iGWB. When
several fragmentary bill files are needed (e.g. for file restoration), manual backup can
also be adopted.
The user can perform manual backup for both the original bill files and final bill files.
There are two types of manual backup:

1) Backup all the bill files in certain days.
2) Backup all the bill files within specified serial numbers.
II. Access
Select "Manual backup" in the [Backup Task] in Figure B-1 to enter the operation
interface, as shown in Figure B-4.
Figure B-4 Manual backup interface
When the manual backup is going on, the user can view the status of manual backup
through the interface shown in Figure B-4.
B-9
User Manual
If the user expects to stop the running manual backup, just click <Stop> in Figure B-4.
If neither the manual backup nor the automatic backup is ongoing (the manual
backup and the automatic backup cannot be performed simultaneously), and if the
user expects to perform the manual backup, just click <Start> in Figure B-4, and an
interface as shown in Figure B-5 will appear.
Figure B-5 Setting manual backup parameters
In Figure B-5, the user need set three kinds of parameters: [Backup Bill Types] (if this
is the final bill, it is necessary to specify the channel of the final bills), [Backup Bill],
and [Backup Destination]. After setting the parameters in the interface as shown in
Figure B-5, click <Confirm> to start the manual backup.
The system will prompt that the starting of backup operation is successful, as shown
in Figure B-6.
Figure B-6 Starting the manual backup operation successfully
Click <OK> as shown in the above figure, and the system will display the status
information of manual backup, as shown in Figure B-7.
B-10
User Manual
Figure B-7 Bill backup status information
B.7.4 Backup Media Operation
I. Function
1) View the free space of the backup media.

2) View the bill files stored in the backup media.
II. Access
To perform operations on the backup medium, just click <Backup Media Operation>
in Figure B-7, and an interface as shown in Figure B-8 appears.
B-11
User Manual
Figure B-8 Backup media operation interface
Select the medium to be operated in the list [Backup Media], as shown in Figure B-8.
In the edit box on the right, the free space of the medium selected is displayed.
To check what bills have been backed up to the medium, select the backup medium
and then the directory in the left column, and the range of bills in this selected
directory is displayed in the edit box.
For example, select the original bill backup directory "BackupOrig" of MO1 and the
date directory "2001.06.08", and the system will display the information of the bills of
that date, including the date when the bill files were generated, the minimum bill
filename and the maximum bill filename, as shown in Figure B-9.
B-12
User Manual
Figure B-9 Viewing the information of files in backup media
B.8 Routine Operation Instructions
The routine task of the user is the complete backup of the generated bill files. When
there are special requirements such as bill restoration, the user must perform
fragmentary backup of bill files.
B.8.1 Automatic Backup
It is very convenient for the user to adopt the automatic backup mode in operation. All
the selected contents can be backed up automatically, and the iGWB will not delete
bills that are not backed up automatically. Even when the system time is modified
unexpectedly, the bill files can also be backed up correctly.
I. Fully automatic backup mode
With the completely automatic backup mode, most of the bill backup work is done by
iGWB automatically, and the user has almost nothing to do. In most cases, he needs
only to replace the backup medium regularly, so it is the most common operation
mode.
With the completely automatic backup mode, iGWB will regularly start bill backup
every day. If the designated ending time is reached and if automatic backup has still
not ended, iGWB will end bill automatic backup. What the user has to do is to replace
the backup medium at a proper time.
B-13
User Manual
Normally, the user should first clarify several parameters: total bill data a day, selected
backup medium capacity, and backup data storage duration. For example:
According to the traffic model, we can calculate the total call times during one day.
With the bytes for each bill (note that original bills and final bills might have different
lengths), we can obtain the backup data amount for a day. Now suppose that the data
amount for a day is 0.5G bytes, and the backup medium is the 1.3G byte writable MO
disk;
In this case, one MO disk can hold the data for 1.3/0.5=2.6 days. As the data of one
day requires 0.384MO disk, 3 months, i.e., 92 days (considering that 2 months have
31 days) would need 92X0.384=35.3 MO disks. Therefore, the user should prepare
38 MO disks (To cope with potential risk, three extra MO disks will be added). Now,
number and label these 38 MO disks. For the first time, insert disk 1#. After disk 1# is
fully written during backup, an alarm of disk backup full will be given, at which the
user should take out this disk 1# (note that the alarm might be generated at midnight,
but the user might only discover it the second day), and then insert the blank disk 2#,
till all the 38 MO disks are used, thus, completing a backup cycle (the actual data
amount might be different from the estimate, so the backup time can also be different
from the estimate, so the backup time length of the 38 MO disks might also not be
completely the same as the predicted backup cycle. Of course, we can still guarantee
the accuracy of the backup period. In this example, we can prepare 43 CDs to
guarantee that the bill data volume of the three months can be stored in them. But if
after three months, only 35 CDs may be used and then, the rest CDs are no longer
used in the backup period. Hence the backup CDs of the previous period can be
recycled in the next backup period and it will start again from 1# CD.
When the next backup cycle begins, bills backed up in the last cycle may not be
useful any longer, so disks used in the last cycle can be used for this cycle, beginning
with disk 1#.
Before inserting disk 1# the next time, make sure that the content in disk 1# is cleared
to do so, insert the disk with the content into the magnetic CD drive on the bill service
console, and use the file manager to delete all files on it.
In this sample, we can also keep the backup data permanently. The changes to the
actual situation and other requirements can also be met by some minor changes.
In the above example, we change the MO disks only after seeing an alarm. This will
lead to such a consequence: bill files generated on the same day might be stored on
two MO disks. If bill files of the same day are not stored on one MO disk, it will affect
backup data management. So, the method of replacing MO disks only after an alarm
is given is not suitable. Instead, the following method can be adopted: the user can
change MO disks once every two days, without waiting for any alarm. In this way, the
user must prepare 46 MO disks.
B-14
User Manual
During backup medium management, it can also go without numbering the backup
media beforehand, but numbering them sequentially when taking them out from the
drive.
For easy backup data management, when backup media are taken for storage, the
user must use the browsing medium content function on the bill console, and stick a
content label to each backup medium.
The result of automatic backup can be used purely for reservation, or for off-line
charging. Suppose the 21st of each month through the 20th of the next month is a
charging cycle, now what we need to do is only to take out the backup medium from
the backup device on the 21st day, and then sending other backed up media together
to the off-line billing center. But here we get a problem. What if the data of the 20th
day is still not completed backed up when we wish to take out the backup medium on
the 21st day? Luckily, this problem is addressed and solved in this system in the way
that the user uses the semiautomatic backup method. When the user tries to take out
the backup medium on the 21st day, he can send a command via the bill console to
iGWB, asking iGWB to back up all bill files not already backed up before the 21st day.
During backup, if alarms of inadequate backup space are given, we need only to take
out the fully written backup medium, and replace it with a new and blank medium, so
that automatic backup can continue.
II. Semi-automatic backup mode
Semiautomatic backup mode and completely automatic backup mode are quite
similar, but bill backup cannot be automatically started by iGWB. Instead, it must be
started by a user through the bill console. Moreover, semiautomatic backup has no
ending time restriction. Semiautomatic backup can be started by the user at any time,
and the user can designate the backup range of semiautomatic backup. Thus it is
very flexibly, and can be interchanged with the completely automatic backup mode.
So, it is usually used as a complement to the completely automatic backup mode.
Semiautomatic backup running method: first, cancel the automatic start function of
completely automatic backup through the bill service console, that is, iGWB can no
longer make automatic bill file backup at a designated time every day. Instead, a
command is sent at an idle calling hour every day from the bill console asking iGWB
to make the automatic backup.
Semiautomatic backup can designate only the ending point of backup (the user can
designate the backup of all bills not backed up before a certain date), and its starting
point is the earliest file in iGWB that is not backed up.
For the semiautomatic backup, its backup medium management is the same as that
of completely automatic backup, so it will not be repeated here.
B-15
User Manual
If we choose completely automatic backup to back up bill files, semiautomatic backup

can be used as a supplement to automatic backup. If it is not suitable in iGWB to
make automatic backup for a period of time, say, the traffic during the time span of
completely automatic backup at a special date is so big that backup will affect iGWB
performance, or if equipment is repaired at this special period which makes bill
backup inappropriate, then we can temporarily transfer from the completely automatic
backup mode to the semiautomatic backup mode: adopting the semiautomatic
backup mode to back up generated bill files at an idle calling time.
Semi-automatic and full-automatic backup of original bills (or final bills) cannot be
implemented simultaneously. Except the above differences, semiautomatic backup of
all other parameters such as backup media is the same as automatic backup.
B.8.2 Manual Backup
To make complete backup of bill files, manual backup is a bit more complicated than
automatic backup, and during deletion of bills, it is impossible to determine whether
bill files are already backed up, which might lead to deletion of bills not backed up.
But some users might be used to old manual operation modes, and the manual
backup mode can be used to realize some special complete backup demands, so,
this system still provides interfaces and functions of manual backup. But manual
backup is not a recommended working mode.
There are two manual backup modes: one is backup of all bill files generated within
several days; the other mode is backup of all bill files during a bill file serial number
range.
During the complete backup of bill files in the manual backup mode, we must adopt
the first manual backup. If bill backup is not made for a long time, daily deletion of
outdated bills might delete outdated bills in iGWB that are not manually backed up.
So, during the manual mode of complete bill file backup, we must periodically (e.g.,
daily) make manual backup of bill files that are not backed up.
In the manual mode of complete bill file backup, we must also define the following
parameters: total bill data amount of the day, the selected backup medium capacity,
and backup data storage duration. In this case, the manual backup strategy is similar
to that of automatic backup in many ways. So, let's continue our discussion still with
examples of automatic backup.
In this example, manual backup, like automatic backup, can also make MO
management: prepare enough MO disks for a bill backup cycle; number the used MO
disks in the same sequence as that in which the disks are to be used.
In this example, one MO disk can store bill files for a little more than 2 days. To store
all bill files generated in one day to the same MO disk for better backup file
B-16
User Manual
management, it is thus decided to store bills of two days on every MO disk. During
idle hours of each day, the user can start iGWB manual backup through the bill
console, so as to back up all bill files generated the previous day (assuming that the
user makes daily manual backup, then during the start, the earliest bills that are not
backed up in iGWB are bill files of yesterday; otherwise, if the use has not made
manual backup every day, he must start the backup from the earliest date when bills
are not backed up). If the MO disk has stored bill files of 2 days, then take out the MO
disk, make a content label, and insert the next MO disk. Keep it going on till the
backup cycle ends, then switch to the next backup cycle.
It must be noted that important files that iGWB must back up every day can only be
backed up automatically, not manually. If the information file backup drive is the same
as that for the above manual backup, then the information files of every day must be
stored on the same MO disk as manual backup files, and the MO disk must also be
put in the drive even when not during manual backup so as to avoid errors during
information file automatic backup.
If final bill files in iGWB are sent to multiple different billing centers, and if not the
same backup drives are configured as for the billing center, we should normally select
backup of original bills. If we wish to back up final bills, and if we wish to store final
bills to be sent to different billing centers on different backup media respectively, then
we can take the manual backup of final bills. What follows describes this with the data
amount in the sample of automatic backup.
First, we can select the backup medium capacity according to the bill data amount to
be sent every day to various billing centers, then confirm how many MO disks are
required to back up the bills to be sent to various billing centers according to such
parameters as the backup data storing duration. MO disks used backup and to be
sent to different billing centers must be stored separately.
Next, during daily final bill manual backup, first back up the final bills to be sent to a
certain billing center. After the manual backup, take out the MO disk, and insert
another MO disk that backs up final bills to be sent to another billing center, and start
the backup of final bills to be sent to another billing center, till all final bills to be sent
to different billing centers are backed up. When manual backup is not made, insert
the MO that is used to back up files to be sent to a certain designated billing center
into the backup drive, and the daily information files will be backed up to this MO disk.
Due to its flexibility, manual backup can be used to perform some specific file
recovering tasks.
When it occurs that files are damaged so that we need several bill files or those of
several days in iGWB, we can use manual backup so as to back the bill files that
should be separately backed up to a designated backup medium. In this case, we
should prepare several backup media for such partial manual backup, which must
B-17
User Manual
also be numbered for management according to the same sequence as they will be
used. Such manual backup involves the following specific steps:
First, we must stop the running automatic backup, so as to take out the backup
medium in the backup drive needed for manual backup, and insert that needed for
partial manual backup.
Next, we must start manual backup through the bill console, and specify the backup
of bill files to be backed up to the manual backup medium. We should better control
the quantity of files to be backed up within the space range of one backup medium. If
the files to be backed up cannot be contained in one backup medium, we can also
manually back up these files in several batches. If it occurs that the backup space is
not enough, iGWB will give a fault alarm, so that we can take out the backup medium,
and insert the backup medium of the next serial number into the backup drive so as
to continue the manual backup.
During manual backup, after taking out the backup medium, we must also label the
content in the same way as described for automatic backup.
It must be noted that before manual backup, we must first stop the automatic backup
function, and note not to mix the media used for manual backup with those used for
automatic backup. Besides, the backup media used for file recovering must also be
separated from other backup media so as to avoid confusion of backup data.
B.8.3 Multiple Backups
In some cases, the same bill file needs to be backed up in two copies, one to be sent
to the billing center, and one to be reserved by the user himself. This can be
conveniently performed with automatic backup and manual backup.
If it is wished to use automatic backup to realize multiple backup, iGWB must then be
installed with two backup drives. When configuring the destination path of backup
files in the Config tool, we must designate two bill automatic backup directories.
During automatic backup, iGWB will separately back up the same bill files to the
media in two backup drives.
If we wish to use the manual backup function to realize multiple backup, we can take
the following measures:
1) If two backup drives are installed in iGWB, then designate two backup directories
during manual backup. Manual backup will back the same bill files separately to
media in two backup drives.
2) If only one backup is installed in iGWB, then designate only one backup directory
during manual backup. After manual backup, we should take out the medium in
the backup drive, then insert a new backup medium, and make another manual
backup of the same files. In this way, the same bill files are backed up.
B-18
User Manual
We can also combine the iGWB automatic backup and manual backup to realize
multiple backups of bills in the following way: first use the automatic backup function
to make an automatic backup of the bill files, then use the iGWB manual backup
function to make another backup of the same bill files, so as to obtain two copies of
the same bill file.
B.8.4 Backup Media Management
Normally, there are 4 types of backup media: media used for original bill file automatic
backup, media used for final bill file automatic backup, media used for complete
manual backup, and media used for partial manual backup. Of the first 3 types,
maybe one or two types are used only according to the specific circumstances. The
user must categorize the various different backup media, so as to avoid backup data
confusion. If what is backed up is final bills, then backup of bills to be sent to different
billing centers must also be managed separately. Different backup media must also
be numbered sequentially and well labeled for easier backup data indexing and
management.
Given below are the recommended backup medium management methods:

1) Remove labels of all blank media to be used for backup, prepare them for
various types of backup. Such backup media can be stored together for easier
management.
2) When a certain type of backup needs blank backup media, take one blank
medium from those stored together.
3) When backup media used for backup are taken out for reservation, they must
also be categorize into different backup medium sets, and be numbered
according to the sequence used in this set. Then labels must be prepared for
them according to the bills stored on such backup media so that they can then
be sent to different backup medium sets for reservation.
4) If backup media used for reservation should be reused after a period of time, we
must first clear the content in them, take off the labels, then send them to the
blank backup medium set stored together so that they can be launched into a
new backup cycle.
Note that before sending backup media for reservation, we must prepare content
labels for them according to the bills stored in them for easier backup data indexing
and management. Backup medium content labels should better include the following
items:
5) Backup medium set this label belongs to, e.g., that which describes which type
of backup this backup medium belongs to.
6) Serial No. of this label.
7) Storage time of this backup medium.
B-19
User Manual
8) Which bill files are stored in this backup medium, which can be obtained on the
bill console: on the bill console, make operations as shown in Sector "Backup
media operation" and check which directories exist under the root directory of
this backup disk, then check which bill files are stored under each directory.
B-20
User Manual
HUAWEI iGateway Bill Appendix C CMSC60 Bill Format
Appendix C CMSC60 Bill Format
I. For main information about CMSC60 normal bill, please see the table below.
Table C-1 Information about CMSC60 normal call bill
Field Name Meaning Remarks(e.g. value)

Each bill is assigned a serial number in sequence.
In the same MSC, if the serial numbers of two bills
Serial No.
are the same, they will be considered as the
repeated bills.
In the module, each bill is assigned a serial
number in sequence. In the same module, if the
Serial No. In module
serial numbers of two bills are the same, they will
be considered as the repeated bills.
The module number filled in means that the bill is
output from this module, this is to say, if the
Module No.
module will output bill, module number in the bill
will be filled with this module’s Module No.
Including MOC, MTC, TRANSIT, CFW,

CDR type Types of the bill
ROAM, GWO, etc.
Charge start time Start time and date of the call.

All together 14 bytes with the first 2 bytes
The number of the subscriber who initiates the indicate number_plan, number_type and
Caller party number
call. number_length. The next 12 bytes is the
caller number in BCD code format.
Contain called number_plan,
Called party number The number of the called subscriber. number_type and number_length. The
structure is the same as caller number.
Contain number_plan, number_type and
number_length. Third party number will be
valid only in MOC, MTC and CFW bill in
Third party number The number of the third party of a forwarded call case of forwarding call occurring. For the
bill generated in common call, the field is
invalid and should be filled with default
value.
The roaming number is the mobile called
roaming number. It is valid when called
subscriber in MOC, MTC and CFW bill is
Temporary local subscriber number, i.e. the
Called TLDN local mobile subscriber. If the called is
roaming number.
PSTN or other network mobile subscriber,
without mobile number, the field is invalid.
Fill in the default value FF if it is invalid.
C-1
User Manual

Directory number of the subscriber, i.e. the
number dialed by the calling subscriber. It
Called MDN
indicates for which subscriber this bill is
generated.
The length is 8 bytes and the format is
The International Mobile Subscriber Identity of the
BCD code. If the bill types are TRANSIT,
Served IMSI charged mobile subscriber. It is a unique number
ROAM, and GATEWAY_OUTGOING, the
used to identify a mobile subscriber.
field is invalid and should be all filled in FF.
Charged mobile subscriber electronic sequence

No. The electronic serial number is a unique
Served ESN
number used to identify a particular mobile station
equipment
It means the occupied incoming trunk group ID of
Incoming trunk group ID
certain call.
It means the occupied outgoing trunk group ID of
Outgoing trunk group ID
certain call.
Charge duration The duration of the call, calculated by the second.
When one call creates multiple CDR (in case of
long time call or charging rate change), these
First CDR index indexes of first CDR are the same. According to
the field, it can merge the CDR created in the
same call.
For one call, if it will create one bill and the value
is 0. If create multiple bills, then the first bill is 1,
Sequence of
the remained will be accumulated 1. The bill can
intermediate CDR
be split according to the field if there are multiple
bills.
The record type value is: 0,1,2,3, and
stands respectively for the only bill_record
Indicating whether the record is a single-charging
Record type for this call, the first bill_record for this call,
record or a multiple-charging record.
the intermediate bill_record of this call,
and the last bill_record for this call.
It means whether the user is normal user
or prepaid user.
User type Indicating the type of a mobile user
"0" for ordinary user, "1" for prepaid user,
"0×1F" for invalid
Such as normal call clear, call timeout,
Cause for termination The cause code for termination of the call.
Network causes.
Cause for partial recorde For example: whether it is caused by
Coding for causes for intermediate CDR
termination service timeout
The number of the MSC where the MS is
Local MSC ID originally located. It is also the MSC ID in which
the charged subscriber is initialized.
C-2
User Manual

For bills not directly billed to the user (for
The number of the MSC where the MS is currently
The ID of MSC to which example: the outgoing gateway bill,
located. During the call, it is different from the
the charged user belongs roaming bill and tandem bill), the current
local MSC number when handover occurs.
MSC ID is null.
The code of the location area where the calling
Current LAC of caller
MS is currently located.
The number of the cell where the calling MS is
Current cell ID of caller
currently located.
The code of the location area where the calling For intra-office call, caller initial location,
Initial LAC of caller caller current position, called initial
MS is originally located.
location, and called current location are
The number of the initial cell where the calling MS reflected in one bill. For outgoing call,
Initial cell ID of caller there is only caller location information; for
is originally located.
incoming call, there is only called location
The number of the location area where the called information; for tandem call, there is no
Current LAC of called
is currently located. caller/called location and cell information.
When there is no location and cell
The number of the cell where the called MS is information, the corresponding field is
Current cell ID of called
currently located. filled with 0.
The code of the location area where the called
Initial LAC of called
MS is originally located.
The number of the cell where the called MS is
Initial cell ID of called
originally located.
For mobile originating call, it is caller call
reference. For mobile termination call, it is called
Call Reference Number
call reference. It is not useful for non-caller or
non-called bill and will be filled FF.
including Call forwarding unconditional

indication, Call forwarding busy
Service feature indication Service feature indication1 is the service of
indication, Call forwarding no answer
1 transfer type.
indication, Other forwarding indication,
Call transfer indication
Service feature indication
Service feature indication 2 is call wait. Such as Call wait indication
2
Service feature indication Service feature indication 3 is multi-party Including Three-party indication,
3 conversation type. Conference call indication.
Indicating whether the conversation is charged or Such as No charge, Charge, No charge
Free indicator
not. indication, etc.
Indicate whether the charged mobile subscriber is
Roaming flag local subscriber or roaming subscriber. It is valid
only for MOC or MTC bill.
It is used for identifying intelligent service of the
charged intelligent subscriber in this call; it can
Charged subscriber
record max three intelligent services. It is valid
intelligent service flag 1
only for the intelligent subscriber in MOC, MTC
and CFW.
C-3
User Manual

Charged subscriber
and CFW.
Charged subscriber
and CFW.
It is receiving or sending short message byte It is valid only in MT_SMS and MO_SMS
Number of bytes
quantity. bill.
It is valid only in MT_SMS and MO_SMS
SMC ID Address of the Short Message Center.
bill
Initial MSCID MarketID of The Market ID of MSC to which the calling user
Caller belongs when the conversation begins.
Initial MSCID SwNum of The switch number of MSC to which the calling
Caller user belongs when the conversation begins.
The market ID of MSC to which the calling user
Current MSCID MarketID
belongs. It is the same as his initial MSC ID when
of Caller
no MSC handover occurs. For a call, if caller subscriber is local
mobile subscriber, caller initial MSCID
The switch number of MSC to which the calling and current MSCID is valid. If called
Current MSCID SwNum
user belongs. It is the same as his initial MSC ID subscriber is the local mobile subscriber,
of Caller
when no MSC handover occurs. called initial MSCID and current MSCID is
Initial MSCID MarketID of The market ID of MSC to which the called user valid. For forwarding subscriber, it will not
Called belongs when the conversation begins be reflected in bill because the initial and
current MSCID may not be gotten. If there
Initial MSCID SwNum of The switch number of MSC to which the called is no MSCID information, the
Called user belongs when the conversation begins corresponding field should be filled 0.
The market ID of MSC to which the called user

MSCID MarketID of
belongs. It is the same as his initial MSC ID when
Called
no MSC handover occurs.
The switch number of MSC to which the called
MSCID SwNum of Called user belongs. It is the same as his initial MSC ID
when no MSC handover occurs.
II. For main information about CMSC60 trunk metering bill, please see the
table below.
Table C-2 Information about CMSC60 trunk metering bill
Field Name Meaning

Each bill is assigned a serial number in sequence. In the same MSC, if the serial numbers
Serial No.
of two bills are the same, they will be considered as the repeated bills.
C-4
User Manual
Field Name Meaning

In the module, each bill is assigned a serial number in sequence. In the same module, if the
Serial No. In module
serial numbers of two bills are the same, they will be considered as the repeated bills.
Trunk group property Indicates whether it is incoming trunk group or outgoing trunk group.
CDR type Types of the bill.
Charge start time Represents year, month, day, hour, minute, and second in sequence.
Charged trunk group ID It represents charging trunk group ID.
The ID of the local MSC to which the mobile user belongs. It is also the ID of MSC to which
Local MSC ID
the charged user initially belongs.
Call_meter 1 After last time generating call_meter, hop the table value based on the table accumulation.
Table_1_call_times After last time generating call_meter, the call times value based on the table accumulation.
Table_2_call_times The call times value based on the table accumulation.
C-5
User Manual
HUAWEI iGateway Bill Appendix D Abbreviations and Acronyms
Appendix D Abbreviations and Acronyms
Abbreviation Full name

A
ASCII American Standard Code for Information Interchange
ASN.1 Abstract Syntax Notation One
B
BAU Bill Administration Unit
BCD Binary Coded Decimal
BIOS Basic Input Output System
C
CDMA Code Division Multiple Access
CPU Central Processing Unit
D
DHCP Dynamic Host Configuration Protocol
DNS Domain Name System
F
FTP File Transfer Protocol
G
GMSC Gateway Mobile Switching Center
I
iGWB iGateway Bill
IP Internet Protocol
ISO International Organization for Standardization
L
LAN Local Area Network
M
MAC Medium Access Control
MML Man Machine Language, Man-Machine Language
MO Magneto-Optical
MSC Mobile Switching Center
N
D-1
User Manual
HUAWEI iGateway Bill Appendix D Abbreviations and Acronyms
Abbreviation Full name

NetBIOS Network Basic Input/Output System
NMS Network Management System
O
OEM Original Equipment Manufacturer
OMC Operation & Maintenance Center
OSI Open System Interconnection
R
RAID Redundant Arrays of Inexpensive Disks
S
SMTP Simple Mail Transfer Protocol
SNMP Simple Network Management Protocol
SPC Service Processing Board
SPM Service Processing Module
T
TCP Transfer Control Protocol
W
WAN Wide Area Network
WINS Windows Internet Name Service
WS Work Station
WWW World Wide Web
D-2

Igateway Bill User Manual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Igateway Bill User Manual

Uploaded by

Copyright:

Available Formats

Chapter 1 System Introduction ......................................................................

Appendix D Abbreviations and Acronyms .................................................... D-1

HUAWEI iGateway Bill

Manual Version T2-030106-20040810-C-6.31

Product Version V100R002

Huawei Technologies Co., Ltd.

Address: Administration Building, Huawei Technologies Co., Ltd.,

Bantian, Longgang District, Shenzhen, P. R. China

Postal Code: 518129

All Rights Reserved

No part of this manual may be reproduced or transmitted in any form or by any

, HUAWEI, C&C08, EAST8000, HONET, , ViewPoint, INtess, ETS, DMC,

HUAWEI M800 CDMA Mobile Switching

HUAWEI M800 CDMA Mobile Switching Instructions on replacement procedures of boards,

HUAWEI iGateway Bill User Manual Introduction to theories, installation, operation,

The manual is intended for the following readers:

The manual uses the following conventions:

III. GUI conventions

IV. Keyboard operation

Caution: Means reader be extremely careful during the operation.

Note: Means a complementary description.

Chapter 1 System Introduction .................................................................................................... 1-1

Chapter 2 Installation Guide......................................................................................................... 2-1

Chapter 3 iGWB Configuration and Software Directory Structure........................................... 3-1

Chapter 4 iGateway Bill Console Operation ............................................................................... 4-1

Chapter 5 SmartBackup................................................................................................................ 5-1

5.3 Overview of SmartBackup ................................................................................................. 5-2

Chapter 6 iGWB Maintenance ...................................................................................................... 6-1

Appendix A Installation of Operating System ............................................................................A-1

Appendix B Bill Backup................................................................................................................B-1

B.7.2 Automatic Backup Function ....................................................................................B-6

Appendix C CMSC60 Bill Format .................................................................................................C-1

Appendix D Abbreviations and Acronyms .................................................................................D-1

Chapter 1 System Introduction

1.1.1 System Overview

GSPC GSPC ... GSPC WAN

Heartbeat path LAN Switch

Bill collector NMS server Bill service

Figure 1-1 Position of the iGWB in the network

Monitoring process Bill format setting program

FTP/FTAM server process

Figure 1-2 iGWB software structure

1.1.2 Functional Characteristics

The functions of the iGWB are as follows:

z Providing FTP or FTAM interface for the Billing Center.

1.2 iGWB Networking

DDN, X.25, 64k

Active iGWB Standby iGWB IP Router

Figure 1-3 Connection of the iGWB and the Billing Center

1.2.1 Connecting to the Switch

The detailed procedures are as follows:

Figure 1-4 Configuration table

Figure 1-5 SPM configuration table

1.2.2 Connecting to the Billing Center

1) Configure the network adapter connecting with the bill collector

2) FTAM software installation

II. User authority setting

1.2.3 Connecting to the Browsing Terminal

1.3 Operational Environment

iGWB bill console Server

Windows 2000 Server( Windows 2000

iGWB bill console Server

Chapter 2 Installation Guide