Installation Manual-System Commissioning

Chapter 1 Overview 1-1.........................................................................................

1.1 Preparations 1-1...........................................................................................1.2 Basic Procedures 1-1...................................................................................

Chapter 2 Network Check 2-1...............................................................................

2.1 Check Network Communication 2-1.............................................................2.2 Check Network Attribute Configuration 2-1..................................................2.3 Check Client Software 2-2............................................................................

2.3.1 Check "M900 M1800 Client" 2-2..........................................................2.3.2 Check "M900 M1800 Maintenance" 2-2...............................................2.3.3 Check "M900 M1800 Alarm" 2-3..........................................................

Chapter 3 Hardware Commissioning 3-1.............................................................

3.1 Related Concepts 3-1...................................................................................3.1.1 Loading 3-1..........................................................................................3.1.2 Loading Modes 3-2..............................................................................3.1.3 Load File List 3-4..................................................................................

3.2 Basic Procedures of Hardware Commissioning 3-5.....................................3.3 Power-on/Loading Procedures 3-5...............................................................

3.3.1 Preparations 3-5...................................................................................3.3.2 Power-on/Loading Sequence and Path 3-6.........................................3.3.3 Powering on AM Cabinet for Loading 3-8............................................3.3.4 Powering on LIM Cabinet for Loading 3-9............................................3.3.5 Powering on SRM Cabinet for Loading 3-9..........................................3.3.6 Powering on SPM Cabinet for Loading 3-11..........................................3.3.7 Parallel Loading 3-11.............................................................................

3.4 Check Loading Effect 3-12.............................................................................3.4.1 Solutions to Inconsistent Foreground and Background Data 3-12.........3.4.2 Checking Methods for Board Version Consistency betweenForeground and Background 3-14..................................................................

3.5 Important Points upon Loading 3-15..............................................................3.5.1 GCPC and GSPC Loading 3-15.............................................................3.5.2 Global Resource Loading 3-15..............................................................3.5.3 Path Loading 3-16..................................................................................

3.6 Common Loading Problems and Solutions 3-16............................................3.6.1 AMP, CDP or GSPC Loading Unsuccessful 3-16..................................3.6.2 GQSI/BCC Loading Unsuccessful 3-16.................................................3.6.3 GMHI Loading Successful but GSRC/GSPT LoadingUnsuccessful 3-17...........................................................................................3.6.4 Loading Failure Caused by Lack of Basic Configuration Data 3-17.......

3.6.5 Inconsistency between CDP Loading Program and DataVersion 3-17....................................................................................................3.6.6 Cases about CDP Loading upon Upgrading 3-18..................................

Chapter 4 Trunk and Signaling Commissioning 4-1...........................................

4.1 Basic Commissioning Procedures 4-1..........................................................4.2 Loading of Trunks and Signaling Data 4-1...................................................4.3 Commissioning of Trunk and Signaling in Local Office 4-1..........................4.4 Joint Commissioning of Trunks and Signaling 4-2.......................................

4.4.1 Preparations prior to Joint Commissioning 4-2....................................4.4.2 Basic Procedures for Joint Commissioning 4-2...................................

4.5 Troubleshooting in Trunk and Signaling Commissioning 4-4.......................

Chapter 5 Service Commissioning 5-1................................................................

5.1 Basic Procedures 5-1...................................................................................5.2 Data Loading 5-1..........................................................................................5.3 Service Test 5-1...........................................................................................

5.3.1 Basic Service Dialing Test 5-2.............................................................5.4 Supplementary Service Verification 5-2.......................................................

5.4.1 IN Service Verification 5-3....................................................................5.4.2 Handover Function Verification 5-4......................................................

5.5 Charging Verification 5-4..............................................................................5.5.1 Charging Gateway Verification 5-4......................................................5.5.2 Bill Verification 5-7...............................................................................

5.6 Troubleshooting in Service Commissioning 5-9...........................................

Chapter 6 Specified Trunk Commissioning 6-1..................................................

6.1 Significance of Specified Trunk Test 6-1......................................................6.2 Test Type and Dialing Scheme 6-1..............................................................6.3 Specified Trunk Test in VMSC 6-2...............................................................

6.3.1 Specified Speech Test 6-2...................................................................6.3.2 Specified A Interface Circuit Test 6-10...................................................6.3.3 Specified TUP Circuit Test 6-11.............................................................6.3.4 Specified ECP Channel Test 6-13.........................................................

6.4 Specified Trunk Test of GMSC 6-14...............................................................6.4.1 Special Test Call Prefix for Tandem to GMSC 6-14...............................6.4.2 Not Special Test Call Prefix for Tandem to GMSC 6-16........................

Chapter 7 Equipment Preliminary Acceptance and Cutover 7-1.......................

7.1 Equipment Preliminary Acceptance 7-1.......................................................7.2 Cutover 7-1...................................................................................................

Appendix A Upgrade Instruction A-1....................................................................

A.1 Setup/upgrade Tool A-1...............................................................................A.1.1 Path of Upgrade Tool A-1....................................................................A.1.2 Functions of Upgrade Tool A-2............................................................A.1.3 Application Environment of Upgrade Tool A-2.....................................

A.2 Upgrade BAM Software with Setup/Upgrade Tool A-2.................................A.2.1 Preparations A-3..................................................................................A.2.2 BAM Software Upgrade Procedures A-6.............................................A.2.3 Handle BAM Software Upgrade Failure A-11........................................

A.3 Host Upgrade Instruction A-13.......................................................................A.3.1 Preparations A-13..................................................................................A.3.2 Upgrade Process A-14...........................................................................A.3.3 Fallback Process A-15...........................................................................

Appendix B Patch Operations B-1........................................................................

B.1 Patch Operations on Host System B-1.........................................................B.1.1 Functions of Host Patches B-1.............................................................B.1.2 Host Patch Features B-1......................................................................B.1.3 Host Patch Status B-2..........................................................................B.1.4 Host Patch Operation Commands B-3.................................................B.1.5 Host Patch Operation Procedures B-4.................................................

B.2 Cautions for Patch Operations B-8...............................................................

Appendix C Online Expansion C-1.......................................................................

C.1 Expansion Modes and Configuration Instructions C-1.................................C.1.1 LIM Module Expansion Principle C-1...................................................C.1.2 SPM Expansion Principle C-3..............................................................C.1.3 SRM Expansion Principle C-3..............................................................

C.2 LIM Module Expansion Process C-3............................................................C.2.1 Add GE16 and GECS Board C-3.........................................................C.2.2 Add LIM Frame C-4..............................................................................

C.3 SPM Module Expansion Process C-4..........................................................C.3.1 Add GCPC Board C-4..........................................................................C.3.2 Add GVDP Board C-5..........................................................................C.3.3 Add SPM Frame C-5............................................................................

C.4 SRM Module Expansion Process C-6..........................................................C.4.1 Add GSRC Board C-6..........................................................................C.4.2 Add GSPT Board C-6...........................................................................

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

HUAWEI

M900/M1800 MSC/SSP/IP Installation Manual - System Commissioning

V610

M900/M1800 MSC/SSP/IP

Installation Manual

Volume System Commissioning

Manual Version T2-030443-20040110-C-6.21

Product Version V610

BOM 31040843

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: [email protected]

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 M900/M1800 MSC/SSP/IP V610.

Organization

This manual introduces the tests, commissoning methods and checks carried out for the system after the hardware and software installation. It consists of the following sections:

Chapter 1 Overview It briefs the preparations and basic procedures for system commissioning.

Chapter 2 Network Check It covers network communication check, network attribute configuration check, and client software check.

Chapter 3 Hardware Commissioning It covers hardware data configuration, board power-on and loading, board operation check, and hardware data configuration check.

Chapter 4 Trunk and Signaling Commissioning This part introduces the interconnection of the trunks and signaling interworking between the local office and the transmission/peer office, and the methods to check the connection and configuration of inter-MSC trunks and signaling.

Chapter 5 Service Commissioning This part describes the commissioning methods of basic services and intelligent services, and the ways to check the system’s ability to provide services and the system’s charging function.

Chapter 6 Specified Trunk Commissioning This part introduces the method of commissioning specified trunk by extracting 1 or 2 timeslots in each E1 system in a office direction.

Chapter 7 Equipment Preliminary Acceptance and Cutover This party gives the contents of preliminary acceptance before the cutover and points for attention during the system cutover.

Appendix A Upgrade Instruction It gives the instructions on upgrading a BAM server software and Host software.

Appendix B Patch Operations This part introduces the basic concepts and methods of patching operations, along with the functions, features, status, commands and operation steps of patches.

Appendix C Online Expansion It describes the capacity expansion methods of LIM, SPM and SRM.

Appendix D Abbreviations and Acronyms

Intended Audience

The manual is intended for the following readers:

Operator of the report system Telecommunications management personnel Intelligent network system engineers

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.

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

[ x | y | ... ] Optional alternative items are grouped in square brackets and separated by vertical bars. One or none is selected.

{ x | y | ... } * Alternative items are grouped in braces and separated by vertical bars. A minimum of one or a maximum of all can be selected.

[ x | y | ... ] * Optional alternative items are grouped in square brackets and separated by vertical bars. Many or none can be selected.

III. GUI conventions


< > Button names are inside angle brackets. For example, click the <OK> button.

[ ] Window names, menu items, data table and field names are inside square brackets. For example, pop up the [New User] window.

/ Multi-level menus are separated by forward slashes. For example, [File/Create/Folder].

IV. Keyboard operation

Format Description

<Key> Press the key with the key name inside angle brackets. For example, <Enter>, <Tab>, <Backspace>, or <A>.

<Key1+Key2> Press the keys concurrently. For example, <Ctrl+Alt+A> means the three keys should be pressed concurrently.

<Key1, Key2> Press the keys in turn. For example, <Alt, A> means the two keys should be pressed in turn.

V. Mouse operation

Action Description

Click Press the left button or right button quickly (left button by default).

Double Click Press the left button twice continuously and quickly.

Drag Press and hold the left button and drag it to a certain position.

VI. Symbols

Eye-catching symbols are also used in the manual to highlight the points worthy of special attention during the operation. They are defined as follows:

Caution, Warning, Danger: Means reader be extremely careful during the

operation.

Note, Comment, Tip, Knowhow, Thought: Means a complementary description.

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.

Installation Manual - System Commissioning M900/M1800 MSC/SSP/IP Table of Contents

i

Table of Contents

Chapter 1 Overview....................................................................................................................... 1-1 1.1 Preparations....................................................................................................................... 1-1 1.2 Basic Procedures............................................................................................................... 1-1

Chapter 2 Network Check............................................................................................................. 2-1 2.1 Check Network Communication ........................................................................................ 2-1 2.2 Check Network Attribute Configuration ............................................................................. 2-1 2.3 Check Client Software ....................................................................................................... 2-2

2.3.1 Check "M900 M1800 Client" ................................................................................... 2-2 2.3.2 Check "M900 M1800 Maintenance"........................................................................ 2-2 2.3.3 Check "M900 M1800 Alarm" ................................................................................... 2-3

Chapter 3 Hardware Commissioning .......................................................................................... 3-1 3.1 Related Concepts .............................................................................................................. 3-1

3.1.1 Loading.................................................................................................................... 3-1 3.1.2 Loading Modes........................................................................................................ 3-2 3.1.3 Load File List ........................................................................................................... 3-4

3.2 Basic Procedures of Hardware Commissioning ................................................................ 3-5 3.3 Power-on/Loading Procedures .......................................................................................... 3-5

3.3.1 Preparations ............................................................................................................ 3-5 3.3.2 Power-on/Loading Sequence and Path .................................................................. 3-6 3.3.3 Powering on AM Cabinet for Loading ..................................................................... 3-8 3.3.4 Powering on LIM Cabinet for Loading..................................................................... 3-9 3.3.5 Powering on SRM Cabinet for Loading................................................................... 3-9 3.3.6 Powering on SPM Cabinet for Loading................................................................. 3-11 3.3.7 Parallel Loading..................................................................................................... 3-11

3.4 Check Loading Effect....................................................................................................... 3-12 3.4.1 Solutions to Inconsistent Foreground and Background Data ............................... 3-12 3.4.2 Checking Methods for Board Version Consistency between Foreground and Background .................................................................................................................... 3-14

3.5 Important Points upon Loading........................................................................................ 3-15 3.5.1 GCPC and GSPC Loading.................................................................................... 3-15 3.5.2 Global Resource Loading...................................................................................... 3-15 3.5.3 Path Loading ......................................................................................................... 3-16

3.6 Common Loading Problems and Solutions ..................................................................... 3-16 3.6.1 AMP, CDP or GSPC Loading Unsuccessful ......................................................... 3-16 3.6.2 GQSI/BCC Loading Unsuccessful ........................................................................ 3-16 3.6.3 GMHI Loading Successful but GSRC/GSPT Loading Unsuccessful.................... 3-17 3.6.4 Loading Failure Caused by Lack of Basic Configuration Data ............................. 3-17


ii

3.6.5 Inconsistency between CDP Loading Program and Data Version ....................... 3-17 3.6.6 Cases about CDP Loading upon Upgrading......................................................... 3-18

Chapter 4 Trunk and Signaling Commissioning ........................................................................ 4-1 4.1 Basic Commissioning Procedures ..................................................................................... 4-1 4.2 Loading of Trunks and Signaling Data .............................................................................. 4-1 4.3 Commissioning of Trunk and Signaling in Local Office ..................................................... 4-1 4.4 Joint Commissioning of Trunks and Signaling................................................................... 4-2

4.4.1 Preparations prior to Joint Commissioning ............................................................. 4-2 4.4.2 Basic Procedures for Joint Commissioning ............................................................ 4-2

4.5 Troubleshooting in Trunk and Signaling Commissioning .................................................. 4-4

Chapter 5 Service Commissioning.............................................................................................. 5-1 5.1 Basic Procedures............................................................................................................... 5-1 5.2 Data Loading...................................................................................................................... 5-1 5.3 Service Test ....................................................................................................................... 5-1

5.3.1 Basic Service Dialing Test ...................................................................................... 5-2 5.4 Supplementary Service Verification................................................................................... 5-2

5.4.1 IN Service Verification............................................................................................. 5-3 5.4.2 Handover Function Verification ............................................................................... 5-4

5.5 Charging Verification ......................................................................................................... 5-4 5.5.1 Charging Gateway Verification................................................................................ 5-4 5.5.2 Bill Verification......................................................................................................... 5-7

5.6 Troubleshooting in Service Commissioning ...................................................................... 5-9

Chapter 6 Specified Trunk Commissioning................................................................................ 6-1 6.1 Significance of Specified Trunk Test ................................................................................. 6-1 6.2 Test Type and Dialing Scheme.......................................................................................... 6-1 6.3 Specified Trunk Test in VMSC........................................................................................... 6-2

6.3.1 Specified Speech Test ............................................................................................ 6-2 6.3.2 Specified A Interface Circuit Test.......................................................................... 6-10 6.3.3 Specified TUP Circuit Test .................................................................................... 6-11 6.3.4 Specified ECP Channel Test................................................................................. 6-13

6.4 Specified Trunk Test of GMSC........................................................................................ 6-14 6.4.1 Special Test Call Prefix for Tandem to GMSC...................................................... 6-14 6.4.2 Not Special Test Call Prefix for Tandem to GMSC............................................... 6-16

Chapter 7 Equipment Preliminary Acceptance and Cutover .................................................... 7-1 7.1 Equipment Preliminary Acceptance................................................................................... 7-1 7.2 Cutover .............................................................................................................................. 7-1

Appendix A Upgrade Instruction .................................................................................................A-1 A.1 Setup/upgrade Tool...........................................................................................................A-1

A.1.1 Path of Upgrade Tool..............................................................................................A-1 A.1.2 Functions of Upgrade Tool .....................................................................................A-2 A.1.3 Application Environment of Upgrade Tool ..............................................................A-2


iii

A.2 Upgrade BAM Software with Setup/Upgrade Tool............................................................A-2 A.2.1 Preparations............................................................................................................A-3 A.2.2 BAM Software Upgrade Procedures.......................................................................A-6 A.2.3 Handle BAM Software Upgrade Failure ...............................................................A-11

A.3 Host Upgrade Instruction.................................................................................................A-13 A.3.1 Preparations..........................................................................................................A-13 A.3.2 Upgrade Process ..................................................................................................A-14 A.3.3 Fallback Process ..................................................................................................A-15

Appendix B Patch Operations......................................................................................................B-1 B.1 Patch Operations on Host System ....................................................................................B-1

B.1.1 Functions of Host Patches......................................................................................B-1 B.1.2 Host Patch Features ...............................................................................................B-1 B.1.3 Host Patch Status ...................................................................................................B-2 B.1.4 Host Patch Operation Commands..........................................................................B-3 B.1.5 Host Patch Operation Procedures..........................................................................B-4

B.2 Cautions for Patch Operations ..........................................................................................B-8

Appendix C Online Expansion .....................................................................................................C-1 C.1 Expansion Modes and Configuration Instructions.............................................................C-1

C.1.1 LIM Module Expansion Principle ............................................................................C-1 C.1.2 SPM Expansion Principle .......................................................................................C-3 C.1.3 SRM Expansion Principle .......................................................................................C-3

C.2 LIM Module Expansion Process........................................................................................C-3 C.2.1 Add GE16 and GECS Board ..................................................................................C-3 C.2.2 Add LIM Frame.......................................................................................................C-4

C.3 SPM Module Expansion Process......................................................................................C-4 C.3.1 Add GCPC Board ...................................................................................................C-4 C.3.2 Add GVDP Board ...................................................................................................C-5 C.3.3 Add SPM Frame .....................................................................................................C-5

C.4 SRM Module Expansion Process......................................................................................C-6 C.4.1 Add GSRC Board ...................................................................................................C-6 C.4.2 Add GSPT Board....................................................................................................C-6

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

Installation Manual - System Commissioning M900/M1800 MSC/SSP/IP Chapter 1 Overview

1-1

Chapter 1 Overview

1.1 Preparations

System commissioning is a series of tests and checks carried out for the system after the hardware and software installation, so as to ensure that the system can meet the design requirements and operate stably, reliably and safely.

System commissioning is the most important and complicated part of the office deployment process. Preparation work must be checked item by item in strict compliance with the regulations before the system commissioning to avoid any unexpected problem that might arise in the process.

The following requirements should be met for system commissioning:

The hardware installation has been checked to be in good condition and compliant with the acceptance standards;

The power supply of each frame is in good condition with a normal voltage range; The board trial power-on check is successful with status of each power supply

board being normal; O&M software (including that of BAM, iGWB, operation terminal and OMC) is

running normally. The software versions are correct. And the network communication is normal.

1.2 Basic Procedures

Due to its complexity, the system commissioning process can be divided into the following seven steps:

I. Network Check

It covers network communication check, network attribute configuration check, and client software check.

II. Hardware Commissioning

The contents include hardware data configuration, board power-on and loading, board operation check, and hardware data configuration check.

Installation Manual - System Commissioning M900/M1800 MSC/SSP/IP Chapter 1 Overview

1-2

III. Trunk and Signaling Commissioning

The contents include the interconnection of the trunks and signaling between the local office and the transmission/peer office, and check of the connection and configuration of inter-MSC trunks and signaling.

IV. Service Commissioning

The contents include commissioning of all basic services and intelligent services provided by the system, check of the system’s ability to normally provide services, and check of the system’s charging function, etc.

V. Specified Trunk Commissioning

Extract 1 or 2 timeslots for each E1 system on this office direction for specified trunk test, without commissioning the peer office. The purpose is to test the availability of such physical channels as trunk circuit, A interface circuit, ToneID, speech channel, voice file, IWF channel, and ECP channel.

VI. Preliminary Acceptance of Project

It refers to the preliminary acceptance made with the office party personnel present before the cutover i.e. after the service commissioning is completed. This work should be done as per the checklists and operation guides comprised in M900/M1800 MSC/SSP/IP Acceptance Manual based on the actual conditions of MSC. Before the formal acceptance, the project supervisor should arrange an acceptance carried out by the company alone.

VII. Cutover

After the project preliminary acceptance, the project supervisor should cooperate with the customer in the formulation of a detailed cutover scheme and the further implementation. In the process of the cutover, use such means as traffic measurement to observe the equipment operation and solve any possible problems following the cutover in time.

Note:

Operation procedures for system upgrading, patching and online expansion are available in the Appendix of this manual.

Installation Manual - System Commissioning M900/M1800 MSC/SSP/IP Chapter 2 Network Check

2-1

Chapter 2 Network Check

2.1 Check Network Communication

The following two methods can be used to check whether the network communication on the workstation is normal (The second method is recommended):

Open the window [Network Neighbours] and check whether other computers can be viewed. If they are visible, the network communication is normal, otherwise it is abnormal. This method cannot guarantee that the communication between WS and BAM is normal one hundred percent, because BAM may not be able to keep normal communication with the LAN where the WS is located.

In the DOS mode run command "Ping 172.20.200.200" (Suppose it is the IP address of the first network adapter of BAM). If the return information is "Reply from 172.20.200.200: byte=32 time<10ms TTL=128", the communication with BAM is normal. If the return information is "Request Timed Out" or the "time" duration in it is too long, the connection with the BAM server is abnormal.

2.2 Check Network Attribute Configuration

If the network communication is abnormal, please check whether network adapter installation, network cable connection, network adapter and network configuration, and network attribute configuration are correct.

The most common cause for abnormal network communication is incorrect network attribute configuration. Therefore the following configurations of network attributes should be checked specially:

First check whether the mandatory network components including Microsoft Network User, TCP/IP and Network adapter have been correctly installed. If one of them is missing, it must be added.

Then check whether resources conflicts exist between network adapter and other equipment. If any conflict exists, please reinstall the network adapter or manually modify the resource configuration. It is recommended not to modify the resource configuration if unnecessary.

Check whether TCP/IP attributes and network ID (NI) are correctly configured, whether the IP address and the subnet mask are correctly set, and whether the work group is correctly set.


2-2

2.3 Check Client Software

The Client software provided by M900/M1800 MSC/SSP/IP includes:

M900 M1800 Alarm

M900 M1800 Client M900 M1800 Maintenance M900 M1800 Server Gateway Tool Online Help Documentation

The above terminal software can be used to realize most operations and manintenance on the equipment.

2.3.1 Check "M900 M1800 Client"

The simplest but effective way to check "M900/M1800 MSC/SSP/IP MML Input Aid Tool" is to check the host version No.

When all host boards are in normal operation, execute command "DSP EXVER" to view version No.s of all modules. If the return result is normal, the host can correctly receive and execute MML commands. In this case, the MML command line tool is normal. If the return result indicates that a certain module has timed out, while the version report of other modules is normal, the problem exists with the hardware connection or the relevant module is not in the normal operational status. In this case, please refer to the relevant part in the M900/M1800 MSC/SSP/IP Installation Manual-Hardware Installation and check whether the installation is correct until the results of all module versions are correct.

2.3.2 Check "M900 M1800 Maintenance"

The check on "M900/M1800 MSC/SSP/IP Service Maintenance System" can be implemented in two steps: check whether the communication with AMP is normal, then check whether the communication with SPM is normal.

Caution:

The check on "M900/M1800 MSC/SSP/IP Service Maintenance System" must be implemented while the AMP board is in normal operation (It is recommended to check this item while all boards are in normal operation).


2-3

I. Check communication between Service Maintenance System and AMP

On the interface [M900/ M1800 MSC/SSP/IP Service Maintenance System], select "DeviceBoard" from the navigation tree to pop up [Hardware Configuration Status Panel]. If the displayed board information is consistent with the actual configuration, the communication between "M900/M1800 MSC/SSP/IP Service Maintenance System" and AMP is normal.

II. Check communication between Service Maintenance System and SPM

Prior to this check, make sure the communication between M900/M1800 MSC/SSP/IP Service Maintenance System and AMP is normal, and the states of boards GSPC and GBDP are displayed as normal on the "Hardware Configuration Status Panel".

The following simple method can be used to check the communication between M900/M1800 MSC/SSP/IP Service Maintenance System and SPM: On [Hardware Configuration Status Panel], right click GSPC and GVDP for query. If the query does not time out and board information can be returned, the communication is normal.

2.3.3 Check "M900 M1800 Alarm"

Upon deployment commissioning, manually trigger a fault alarm (e.g. disconnect the E1 trunk to a certain office direction), and make sure this alarm is not shielded. In this case, the corresponding alarm information is displayed on the interface [M900/M1800 MSC/SSP/IP Alarm Console]. At the same time, the alarm box also generates the corresponding alarm information. Confirm the alarm information is accurate, then recover the manually generated fault. At this time, the corresponding recovery alarm information is displayed on [M900/M1800 MSC/SSP/IP Alarm Console], and the alarm item generated just now becomes grey. In the above process, if no abnormal sign appears, the M900 M1800 Alarm tool can run normally.

Installation Manual - System Commissioning M900/M1800 MSC/SSP/IP Chapter 3 Hardware Commissioning

3-1

Chapter 3 Hardware Commissioning

3.1 Related Concepts

3.1.1 Loading

This is a process of loading the host programs and data files in the loading directory of the BAM server to the host (mobile switch). This operation is necessary in the following cases:

I. Upon initial software installation for deployment

Upon the new deployment, install the BAM server software onto the BAM server. The host programs are available in the loading directory of the BAM server after the installation.

Then configure data in the offline status, or perform batch operation to configure data via data script files.

After configuration, execute the format conversion command "FMT" and the data loading files exist in the loading directory of the BAM server.

Execute the online command "LON" to enter the online status. Load the host programs and data files in the loading directory of the BAM server to

the host (mobile switch).

II. Software updating or upgrading

The BAM server software should be upgraded first. Then load the host programs and data files in the loading directory of the BAM

server to the host switch to update the host running programs and data.

III. Some data to be loaded after modification

Normally data configuration is implemented in the online status and the command can be set online. But some individual commands should be loaded, such as the command MOD MAXT which is used to modify the maximal number of tuples.


3-2

Note:

The host programs are the software of host boards. Data files are the configuration data files or script data files generated after the format conversion command FMT is executed, such as hardware configuration data files, and trunk configuration files, etc.

3.1.2 Loading Modes

I. Two loading modes are available for program and data loading

The board program and data files can be loaded in the following two modes:

Load the host programs and data files directly from BAM to DRAM; Load the host programs and data files from the Flash Memory to DRAM.

Figure 3-1 and Figure 3-2 respectively illustrate the process of "Loading board program and data files to AMP board" and the process of "Loading board program and data files via AMP board to GBAC board".

Flash Memory DRAM

Prog

ram

2

3

CPU

GAMP

Program Data BAM

1

Data

Figure 3-1 Loading board program to AMP board


3-3

Flash Memory DRAM CPU

GAMP

Program Data BAM

1

Flash Memory DRAM

Prog

ram

3

4GBAC

2Da

ta

Prog

ram

Data

CPU

Figure 3-2 Loading board program from AMP board to GBAC board.

In Figure 3-1, "1" indicates loading program and data directly from the BAM to the DRAM; "2" indicates writing the program and data in the DRAM into the Flash Memory; "3" indicates loading program and data directly from the Flash Memory to the DRAM if necessary.

The program and data loading modes can be selected by modifying the board loading switch. There are two options for the loading switch: program available and data available (program and data in Flash Memory). If it is set to program available and data available, the program and data in the Flash Memory will be used upon board startup. Otherwise program and data should be loaded from BAM upon board startup. The program or data loading path can also be selected separately.

The loading directory selection switch of the M900/M1800 MSC board is set via the modification of the software switch command MOD LSS for board loading.

Caution:

If loading program or data from the Flash Memory, make sure that the Flash Memory has been written and the version is correct, otherwise the loading may not succeed or wrong program may be loaded.


3-4

3.1.3 Load File List

The loading programs and software/hardware configuration data of M900/M1800 MSC/SSP/IP are all stored in the loading data storage directory of the BAM system server (default as D:\iMSC\HOSTDATA).

1) The loading files stored in the directory D:\iMSC\HOSTDATA are listed in the following table.

Table 3-1 Board loading files

Files Description

D:\iMSC\HOSTDATA\Cc08.amp AMP board loading program

D:\iMSC\HOSTDATA\Cc08.cdp CDP board loading program

D:\iMSC\HOSTDATA\Cc08.ncc NCC board loading program (when GSPC board is used)

D:\iMSC\HOSTDATA\cc08cpc.ncc NCC board loading program (when GCPC board is used)

D:\iMSC\HOSTDATA\cc08.vdp GVDP board module loading program

D:\iMSC\HOSTDATA\cc08.spc GSPC board loading program

D:\iMSC\HOSTDATA\Cc08.bcp BCP board loading program

D:\iMSC\HOSTDATA\Cc08.bcc BCC board loading program

D:\iMSC\HOSTDATA\Cc08.cdi GCDI board loading program

D:\iMSC\HOSTDATA\cc08.mhi GMHI board loading program

D:\iMSC\HOSTDATA\cc08_2.spd GSPT board loading program

D:\iMSC\HOSTDATA\cc08.src GSRC board loading program

D:\iMSC\HOSTDATA\Cc08.hn7 GHN7 board loading program

D:\iMSC\HOSTDATA\cc08n7.cpc

D:\iMSC\HOSTDATA\cc08cas.cpc

D:\iMSC\HOSTDATA\cc08pra.cpc

D:\iMSC\HOSTDATA\cc08rsa.cpc

D:\iMSC\HOSTDATA\cc08v5.cpc

GCPC board loading program

D:\iMSC\HOSTDATA\e16.bin GE16 board loading program

D:\iMSC\HOSTDATA\et16.bin GETS board loading program

D:\iMSC\HOSTDATA\gecs.bin GECS board loading program

D:\iMSC\HOSTDATA\gecp.bin GECP board loading program

D:\iMSC\HOSTDATA\stu2.bin GSTU board loading program

D:\iMSC\HOSTDATA\qsi.bin GQSI board loading program

D:\iMSC\HOSTDATA\bac.bin GBAC board loading program


3-5

2) The GSPT signal tone loading files are stored in the subdirectory "D:\iMSC\HOSTDATA\Voice". They are named by numbers.

3) "D:\iMSC\HOSTDATA\Db_*.dat" is the loading data for each module. For instance: Db_20.dat is the data of the module numbered as 20.

Caution:

After the server programs are running, data configuration files required by the mobile switch such as "Db_*.dat" will be generated according to the configuration commands of the user. Never delete any file in this directory!

3.2 Basic Procedures of Hardware Commissioning

Step 1: Configure system hardware data as per the design and execute the corresponding scripts; Step 2: Power on the system for loading as per the detailed procedures; Step 3: Observe the operation of the system after powering it on, and solve any problems that occur in the observation process.

3.3 Power-on/Loading Procedures

3.3.1 Preparations

The following requirements should be met before the system is powered on for loading:

Check whether the hardware installation is correct. The physical connections on the loading paths of all boards should be specially checked;

Check against the version configuration list whether the software version and hardware version are correct. Correctly set the DIP switches of all boards.

The hardware data has been formatted. That is, execute the command "FMT" to convert the format of all data. And BAM is in the online status. Namely, execute the command "LON" to enable the online status";

Both the secondary power switch and alarm switch at the top of the host cabinets (including AM cabinet, LIM cabinet, SRM cabinet and SPM cabinet) are off.

All boards have been inserted into the corresponding slots of the frames. Power switches of all secondary power supply boards are off, but their alarm

switches are on. Activate the Exchange process of the BAM Manager to observe the loading

process, or activate runtime alarm of the MML Client or the maintenance console to observe the loading process.


3-6

Caution:

1) Wear antistatic wrist strap when powering on the system for loading! 2) During loading, pay attention to the meanings of DIP switches and indicators. Details are available in M900/M1800 MSC/SSP/IP Hardware Description Manual.

3.3.2 Power-on/Loading Sequence and Path

I. Loading sequence

System loading is implemented via AMP. Other boards (except CDP and GSPC) cannot be loaded unless AMP is correctly loaded. Namely, the loading program and data of all boards are loaded via AMP.

Besides, the maintenance of all boards are carried out via AMP, and faults of all boards are reported via AMP.

Normally, AMP is loaded first, followed by GBAC in the CCM frame. After these two types of boards are successfully loaded, other boards can be loaded as per the sequence of requests from other boards. A lot of boards should be loaded for the M900/M1800 MSC/SSP/IP, including AMP, GBAC, BCP, CDP, NCC, GQSI, GE16, GSTU, GETS, GECP, GECS, GMHI, GSRC, GSPT, GSPC, GVDP, GCPC and GHN7. The recommended loading sequence is:

CKM frame t AMP t CCM frame (GBAC) t CPM frame (BCP t CDP) t GNET frame (NCC) t internal LIM frame (GQSI t GMHI) t external LIM frame (GQSI t GE16/GSTU/GECP/GECS/GETS) t SRM frame (GSPT/GSRC) t SPM frame (GSPC, GVDP, BCC t GCPC).

Caution:

The program and data loading mode for MSC is designed as a multi-thread mechanism. Namely, one loading task exists as an independent sub-thread. Therefore multiple boards can be loaded simultaneously. Six boards can be loaded in parallel for M900/M1800 MSC. If more than six boards are requested for loading at the same time, the loading request may be repeated for several times and some boards may not be loaded successfully as no response is received. (If the Flash Memory has been written before the unsuccessful board loading, the board will probably run by loading program and data in the original Flash Memory).


3-7

II. Loading paths

The loading paths include the standard 10Mbit/s Ethernet cable, HDLC link, serial port and the bus on the backplane. One of them or the combinations of several of them will be used for the loading of different boards. All main paths for board loading are shown in Table 3-2. They can be used during loading to detect the causes for unsuccessful loading.

Table 3-2 Loading paths of major boards

Frame name Board name Loading path Description

AMP BAMtAMP AMP board is loaded from BAM via network cable

BCP BAMtAMPtBCP BCP and AMP belong to the CPM module, therefore the program of BCP is loaded from AMP via the backplane bus of the CPM frame.

BAMtAMPtBCPtCDP (program)

Both CDP and AMP belong to the CPM module, therefore the program is loaded from AMP via the backplane bus of the CPM frame

CPM

CDP

BAM t CDP (data) The data of CDP is loaded directly from BAM via network cable and LAN Switch

CCM GBAC BAMtAMPtGBAC GBAC board is loaded from AMP via the HDLC signal cable between CPM and CCM

CNET NCC BAMtAMPtCCMtNCC The NCC board of CNET is loaded from AMP in the CPM frame via the HDLC signal cable of CCM.

GQSI BAMtAMPtCCMtGQSI The GQSI board of the LIM frame is loaded from AMP of the CPM frame via the HDLC signal cable of CCM

GE16/GSTU/GECP/GECS/GETS

BAMtAMPtCCMtGQSItGE16/GSTU/GECP/GECS/GETS

GE16/GSTU/GECP/GECS/GETS boards are loaded from GQSI board via the backplane bus of the local frame

LIM

GMHI BAMtAMPtCCMtGQSItGMHI

GMHI is loaded from GQSI via the backplane bus of the local frame

GSPC BAMtGSPC GSPC is loaded from BAM via network cables

GVDP BAMtAMPtCCMtGVDP

GVDP is loaded from AMP of the CPM frame via the HDLC signal cable of CCM

BCC BAMtAMPtCCMtBCC

BCC is loaded from AMP of the CPM frame via the HDLC signal cable of CCM

SPM

GCPC BAMtAMPtCCMtBCCtGCPC

GCPC is loaded from BCC board via the backplane bus of the local frame.


3-8

Frame name Board name Loading path Description

SRM GSPT/GSRC BAMtAMPtCCMtGQSItGMHItGSPT/GSRC

GSPT/GSRC boards are loaded via the 8 Mbit/s HW cable of the internal LIM frame

3.3.3 Powering on AM Cabinet for Loading

1) Switch on the primary power supply of the AM cabinet in the PDF cabinet. 2) Switch on the four secondary power switches on the power distribution box of the

AM cabinet. 3) Switch on all secondary power supply boards in CKM, CCM and CPM frames. 4) AMP boards start loading automatically. Once the AMP boards are in normal

operation, press the reset button of the BCP boards to reload the two BCP boards. 5) Once the BCP board is in normal operation, press the reset button of the CDP

boards to reload all CDP boards. 6) Once the CDP board is in normal operation, press the reset button of the GBAC

boards to reload the two GBAC boards. 7) Once the GBAC board is in normal operation, execute the command DSP BVER

on the maintenance console to query the software versions of AMP, BCP, CDP and GBAC boards. Compare the software versions corresponding to these boards with the values given in the version matching table and check whether the loading is successful. If not successful, press the reset button of the corresponding board(s) to reload them until successful. (For instance: The loading of boards in the CPM frame via AMP may last for a long time, therefore GBAC board may not be loaded successfully if it cannot receive loaded data. In this case, it should be reset for reloading after all other boards are loaded )

8) After confirming that the loading of above boards succeeded, power on all the secondary power supply boards in the CNET frame. Press the reset buttons of the two NCC boards to reload them.

9) Once the NCC boards are in normal operation, execute the command DSP BVER on the maintenance console to query the software version of the NCC boards. Compare the results with the software versions corresponding to these boards given in the version matching table to check if the loading is successful. If not successful, press the reset button of the corresponding board(s) to reload them until successful.

Until now, loading of the AM/CM cabinet has been completed.


3-9

Note:

The board status displayed on [Equipment Panel] on the maintenance console can be used to judge the operational status of a board.

3.3.4 Powering on LIM Cabinet for Loading

1) Switch on the primary power supply of the LIM cabinet. 2) Turn on the four secondary power switches on the power distribution box of the

LIM cabinet. 3) Power on all the secondary power supply boards in the lowermost frame of the

LIM cabinet. 4) GQSI boards start loading automatically. When the GQSI boards are operating

normally, press the reset button of the other interface processing boards such as GE16 and GECP to reload them.

5) After the interface processing boards are operating normally, execute the command DSP BVER on the maintenance console to query the software version of these interface processing boards. Compare the results with the software versions corresponding to these boards given in the version matching table to check if the loading is successful. If not successful, press the reset button of the boards to reload them until successful.

6) As per steps 3~5, power on the other LIM frames of the LIM cabinet for loading. 7) If the system comprises several LIM cabinets, load the rest LIM cabinets as per

steps 1~6.

Until now, the loading of the LIM cabinet has been completed.

Note:

For each LIM frame in which GE16 are inserted fully, one time only half of the LIM frame will be loaded with boards, so that all GE16 boards can be loaded successfully.

3.3.5 Powering on SRM Cabinet for Loading

1) Switch on the primary power supply of the SPM cabinet. 2) Turn on the four secondary power switches on the power distribution box of the

SRM cabinet. 3) Power on all the secondary power supply boards in an LIM frame of the SRM

cabinet.


3-10

4) GQSI boards start loading automatically. When the GQSI boards starts operating normally, press the reset button of the other interface processing boards such as GMHI to reload them.

5) When the GMHI boards start operating normally, execute the command DSP BVER on the maintenance console to query the software version of these boards. Compare the results with the software versions corresponding to these boards given in the version matching table to check if the loading is successful. If not successful, press the reset button of the boards to reload them until successful.

6) If the SRM cabinet comprises two LIM frames, power on the other LIM frame for loading as per steps 3-5.

7) Power on all the secondary power supply boards in an SRM frame of the SRM cabinet.

8) The GSRC and GSPT boards in the SRM frame start loading automatically. After the boards are operating normally, execute the command DSP BVER on the maintenance console to query the software version of these boards. Compare the results with the software versions corresponding to these boards given in the version matching table to check if the loading is successful. If not successful, press the reset button of the corresponding board(s) to reload them until successful.

9) If the SRM cabinet comprises two SRM frames, power on the other SRM frame for loading as per steps 7~8.

10) To update the GSPT voice files, execute steps 11~16. 11) Execute the command FMT SPDMEM on the maintenance console to format the

voice storage unit of the GSPT board. Note: This step is not necessary if voice files of this board are updated.

12) Create 5 folders under the directory D:\iMSC\HOSTDATA\VOICE. Note that the length of each folder name should be limited to no more than 8 bytes. Divide all voice files equally into 5 parts and copy them to the 5 folders respectively.

13) Execute the command LOD SPDVOICE on the maintenance console and select "Batch Loading" for the loading mode of the GSPT board voice files. Enter the name of one of the 5 new folders for the path. Note that each GSPT board needs the loading operation five times to complete the loading.

14) Execute the command DSP SPDVOICE on the maintenance console to observe the voice files on the updated GSPT board. Compare them with the voice file names under the directory D:\iMSC\HOSTDATA\VOICE\ on the BAM to ensure that the voice files have all been correctly loaded to the GSPT board. If the loading of a voice file fails, execute the command LOD SPDVOICE and set "Single Loading" to [Loading Mode], then enter the name of the voice file to be loaded.

15) Execute the command RST BRD on the maintenance console to reset the GSPT board that has been loaded with the voice files.

16) Update the voice files of the other GSPT boards as per steps 12-15.

Until now, the loading for the SRM cabinet has been completed.


3-11

3.3.6 Powering on SPM Cabinet for Loading

1) Switch on the primary power supply of the SPM cabinet in the PDF cabinet. 2) Turn on the four secondary power switches on the power distribution box of the

SPM cabinet. 3) Power on all the secondary power supply boards in the lowermost frame of the

SPM cabinet. 4) BCC boards start loading automatically. Once the BCC boards are in normal

operation, press the reset button of the other boards such as GSPC, GVDP and GCPC to reload them.

5) Once the boards are in normal operation, execute the command DSP BVER on the maintenance console to query the software version of the boards in the frame. Compare the results with the software versions corresponding to these boards given in the version matching table to check whether the loading is successful. If not successful, press the reset button of the boards to reload them until successful.

6) As per steps 3~5, power on the rest SPM frames of the SPM cabinet for loading.

Until now, the loading for the SPM cabinet has been completed.

Note:

After hardware loading, please carefully check the status of the control panel, board indicators and HDLC link status to ensure the board loading is correct.

3.3.7 Parallel Loading

The above loading is carried out in the designed sequence. In the actual operation, parallel loading is also allowed.

Theoretically the parallel loading of 10 processes can be supported simultaneously. But for enormous program data , only 4~5 processes can be loaded in parallel.

Therefore, if all boards request for loading at the same time, process loading programs and data may not be available for some boards. Beyond the specified duration (40 seconds for normal boards), the board which fails in applying for loading process will automatically run the program and data in its own Flash Memory. If the program and data can be run, reloading of program and data will be aborted.


3-12

Note:

Some problems may exist in the co-operation of the original program and data loaded from the Flash Memory and the new terminal version software, therefore the host programs must be loaded in the designed sequence.

3.4 Check Loading Effect

3.4.1 Solutions to Inconsistent Foreground and Background Data

I. For new office

After loading the data for a new office, execute the command STR CRC to check whether the data of each module is consistent with the data in the BAM. If the CRCs of some modules are incorrect, please reset this module of Level-3 so as to reload data.

The MSC stores data not only in the host, but also stores two types of data in the AM module:

Configuration and maintenance data are stored in the AMP board, with the module No. as "0";

Other global user data and maintenance data are stored in the CDP board with the module No. “216~219”.

Note:

Data is stored in both the active and the standby boards of each module. But the command STR CRC is only used to check the data in the active board. Therefore, active/standby switchover is necessary in this checking.

II. Check online office

If the foreground data and background data of an online office are checked out inconsistent via CRC, especially when the system table (Table 0 and Table 1) are checked out incorrect, some problems may occur, and these problems should be solved first.

1) If all tables are correct except Table 0:

The general cause is that the maximum number of tuples of some table is changed, and not reloaded after formatting. In this case, the data must be reloaded.


3-13

2) Table 0 and some other tables are incorrect:

In this case, other tables are normally sequencing tables, such as User Data Index table. If one subscriber cannot be added (because the background has been formatted but not set to the host), the actual number of tuples in Table 0 of the host will be inconsistent with the background, which causes incorrect check result of Table 0. The variance between the User Data Index table and the background record causes incorrect check result of this table. At this time, execute the command LST USD to check whether any data record has been set to the host. If no data has been set, the query result will be:

Module Table ID Record No.

81 13 <NULL>

81 29 <NULL>

81 50 <NULL>

81 52 <NULL>

81 106 <NULL>

81 112 134

Normally, BAM regularly resends these data to the relevant modules of the host in sequence. But if the front part data of a module cannot be correctly set, the rest data cannot be resent. In thise case, all data can be reset via the command SND SPD.

3) If unset data is not queried, and the foreground is inconsist with the background.

If error occurs in the check of Table 1, the problem is generally caused by the incorrect description of the background. This problem seldom exists in formally released versions. In this case, check the memory and compare it with the background so as to further locate the problem.

Following procedures can be used to locate the causes for host data setting failure:

First check whether the check conditions are met for storage procedures; Errors occurred in formatting: Activate the DataMan service to check the specific

error information and then locate the problem. Host setting timed out: It is normally caused by unsuccessful communication

between the foreground and the background. In this case, please check whether the Exchange service is normal and whether the link communication between modules is normal.

Host returns setting failure: Relevant information can be displayed in Exchange via modification of Bam.ini. It is recommended to save Exchange output information as a text file so as to locate the problem. Problems can also be located via the debugging information in the the program.


3-14

3.4.2 Checking Methods for Board Version Consistency between Foreground and Background

After program loading, execute the command STR CHKBVER to check whether the board versions match or execute the command DSP BVER to check the board vesion, so as to find out whether the board loading is correct. The system will list the time required for the checking of all board software versions. If any board of different software version is found, reset this board for reloading.

Caution:

Only one board version test task is allowed in the system at one time. Before executing the command STR CHKBVER for test, execute the command CVT BVER to import the latest version information into the database.

Upon query of board version via command STR CHKBVER or DSP BVER, You can get these version information: PCB and board software versions (report software versions of odd-numbered chips and even-numbered chips respectively), filing time, hardware logical version, DSP software version (ignored if hardware logic or DSP is unavailable), name of the loaded software and its loading time, etc. Generally, the final time is regarded as the criteria for loading different host programs.

For example:

C842CPC REV0 SV0110002100(000405)LV03000 (AMP 6.10 MSC-AM V610R001THAB01D009)

Where:

1) C842CPC REV0 is the C842CPC PCB of version REV.0; 2) SV0110002100(000405): board software version (software versions of

odd-numbered chips and even-numbered chips are reported respectively) and filing time, "01100" stands for versions of odd No., "02100" for versions of even No., while "000405" for filing time;

3) LV03000: hardware logical version and DSP software vesion (No DSP software version but LV03000 hardware logical software is available for CPC). Ignore this part if hardware logical version or DSP software version is unavailable;

4) AMP 6.10 MSC-AM V610R001THAB01D009: the name and version of the loaded software, and the loading time. This item is not required for the query of some boards.


3-15

Caution:

The final part is the host version date. It is consistent with the date of the terminal version displayed via the command DSP EXVER ([Module No.]=0). Board software versions 01100 and 02100 and the logical version 000405 are all consistent with the version matching table.

3.5 Important Points upon Loading

3.5.1 GCPC and GSPC Loading

GCPC and GSPC can be used in the CNET frame. When added with the corresponding software, it can function as an NCC board to realize the management function of the CNET frame.

In design, GCPC and GSPC share the same software name CC08.NCC but have their own programs. Therefore, it is necessary to change the program file name upon board software replacement, otherwise the same program will be loaded.

After the terminal installation, CC08.NCC will be defaulted as the program of GSPC:

If GSPC is used, the program can be loaded without any change; If GCPC is used, CC08.NCC (in the directory of D:\iMSC\HOSTDATA\) should be

changed into CC08SPC.NCC and CC08CPC.NCC into CC08.NCC.

In unexpected cases, the corresponding board files can be copied from the setup CD to the loading directory D:\iMSC\HOSTDATA\), but the file name should be changed into CC08.NCC.

3.5.2 Global Resource Loading

The E1 and CPC of SPM module and the SRC and SPT of SRM module are global resources. When configured or modified, these resources are still in nonoperational status. In this case, the command MNT BRD should be executed to activate the boards bearing these resources (Board activation will not affect the ongoing services). The activation result should be reported to SPM module so that it can manage and use the resources normally. Otherwise the data of the SPM module corresponding to the global resources will be reloaded so as to employ the resources (In thise case, it is useless to reload the boards like GE16, GCPC, GSRC and GSPT).


3-16

3.5.3 Path Loading

Except boards like CDP, GSPC, BCP, GBAC and GFSN, all other boards can be loaded through the path: BAMtCCMHWtAMPtHost boards. To load program data correctly, make sure that the AMP is successfully loaded and is operating normally, and the CCMHW is normal.

Note:

The process will last for 80~85 seconds from powering on AMP, loading program and data, and successfully writing data into the Flash Memory, to the start of normal system operation.

General fault analysis method is: In case there is no loading request, CCMHW is abnormal; In case of repeated loading or loading timeout, the board software is incorrect or the basic hardware data are not correctly configured.

3.6 Common Loading Problems and Solutions

The following are the some loading problems and corresponding solutions.

3.6.1 AMP, CDP or GSPC Loading Unsuccessful

Both the programs and data of AMP and GSPC boards are loaded directly from the BAM. The CDP program is loaded via AMP from the BAM, while the CDP data is loaded directly from the BAM. Normally faults on these boards are caused by the interrupted communications between the BAM and AMP, CDP and GSPC boards. In this case, alarms may be generated for interrupted communication link between the foreground and background GCPC boards, interrupted communication between GSPC and BAM boards, and so on. Besides, execution of command "PING 172.20.X.Y" (X: frame No. of the board, Y: slot No. of the board) on the BAM will fail. When such circumstances occur, the frame backplane of the board should be checked for whether the DIP switch settings for the frame number are correct and whether the network cables are in normal condition.

Besides, the configuration error of basic hardware data may also lead to unsuccessful board loading.

3.6.2 GQSI/BCC Loading Unsuccessful

GQSI is the core board of the LIM frame. The failure of loading these boards will result in failure in loading boards of the whole frame. Programs and data are loaded by the


3-17

AMP to the GQSI boards via the CCM HW. When loading fails, check whether the CCM configuration, HDLC signal cable connections, and backplane DIP switches are correctly set.

BCC boards and QSI boards may have the similar cases.

3.6.3 GMHI Loading Successful but GSRC/GSPT Loading Unsuccessful

The GSRC/GSPT boards are loaded by the GMHI boards via 4 HDLC signaling timeslots of the 8 Mbps HW cables. When loading fails, check whether the GSRC/GSPT board resource configuration, 8 Mbps HW cable connections, and backplane DIP switches are correctly set.

Note that the GSRC/GSPT board DIP switches determine both the frame number and the slot number.

3.6.4 Loading Failure Caused by Lack of Basic Configuration Data

Prior to board loading, the basic data must be configured. Otherwise, the loading will fail.

For GSPC board, commands SET OFI and ADD MAPACCFG should be executed to correctly configure local office information and MAP function information. Otherwise repeated loading may be incurred.

For GSRC board, the command ADD SRCCFG must be executed to correctly configure GSRC board resources. Otherwise the loading will fail.

For GSPT board, the command ADD SPDCFG must be executed to correctly configure GSPT board resources. Otherwise the loading will fail.

For GVDP board, commands ADD CDBFUNC and ADD VLRCFG must be executed to correctly configure CDB function and VLR information. Otherwise the loading will fail.

Besides, for all boards to be loaded via CCMHW, CCMHW resources must be correctly configured. Otherwise the loading will fail.

3.6.5 Inconsistency between CDP Loading Program and Data Version

The loading directories for CDP program and data are different. When the central processing frame is powered on and reset, CDP cannot start program loading until the AMP and BCP are loaded. If it waiting time is too long, CDP will automatically read the original program in the Flash Memory, but the data is the new version loaded from the BAM. This causes the inconsistency between the program and the data version.

The solution is to reset all CDP active/standby boards one by one.


3-18

3.6.6 Cases about CDP Loading upon Upgrading

Phenomenon: After an office is upgraded, calls within the local office are normal, but some outgoing circuits cannot be used, and the call tracing prompts "No channels available".

I. Cause analysis

If the outgoing circuits are in the SPM module, outgoing calls should be analyzed by CDP. Execute the command STR CRC to check whether the data of all CDP modules and BAM data are consistent. If the trunk line hunting data stored in modules 218 and 219 are inconsistent with the those in the BAM, the error should be caused by incomplete CDP loading.

Note:

In the main control frame, the CDP loading path is CDPtBCPtAMPtBAM. The premise for CDP program loading is that the active BCP board and the active AMP board are in the normal operational status.

AMP, BCP and CDP use CPC board. They use the same BIOS. It has been defined in the BIOS program that if no response is received from BAM within 40 seconds since the start of CDP's program loading request, and the program and data in the Flash Memory are correct, CDP will directly run the program in the Flash Memory, then send a db_c.dat file loading request to BAM.

Therefore, if the original program in CDP is correct, CDP may often invoke program directly from the Flash Memory without waiting for program to be loaded from the background.

II. Resolutions and recommendations

The above analysis shows that it is not an ideal way to load CDP program by powering off the main control frame upon upgrading, because inconsistency may occur between program and data versions on the CDP. The correct loading and upgrading procedures should be:

1) Power off the main control frame first and power on it again for loading, or reset the active/standby AMP boards to ensure that new program is loaded for AMP (It takes 80-85 seconds).

2) Reset the active/standby BCP boards and make sure that new program is loaded for BCP.


3-19

3) Reset CDP and make sure new program is loaded. 4) After loading, make sure to execute the command DSP BVER to check whether

the version No.s of each board is consistent with the program used for the current upgrading.

Caution:

Upon upgrading, pay attention to the [Exchange] window so as to ensure that the loaded program files of all boards can be viewed.

Installation Manual - System Commissioning M900/M1800 MSC/SSP/IP Chapter 4 Trunk and Signaling Commissioning

4-1

Chapter 4 Trunk and Signaling Commissioning

4.1 Basic Commissioning Procedures

trunk and signaling commissioning can be performed in the following procedures: Step 1. Configure trunk and signaling data and execute the corresponding script files; Step 2. Load system data; Step 3. Commission the trunks and signaling of the local office; Step 4: Jointly commission the trunks and signaling between the local office and the peer office.

4.2 Loading of Trunks and Signaling Data

As trunk and signaling data have nothing to do with the AM, it suffices to reset and load the CDP and GSPC boards. After loading, execute the command "STR CRC: MN=255;" to perform CRC check on all the modules. For any module that failed in the check should be reset again for loading.

Caution:

Wear antistatic wrist strap when powering on the system for loading. When resetting the GSPC board for loading, the GCPC board subordinate to GSPC will perform reloading automatically.

4.3 Commissioning of Trunk and Signaling in Local Office

This part includes the following tasks:

I. Self-loop all E1s of the local office at the cabling rack:

The specific procedures of the self-loop test:

1) Remove the connectors of all E1s from the cabling rack; 2) Self-loop the first E1 system of the local office with connectors; 3) Execute the command "DSP E1CH" to view the status of the first E1 system; 4) Check the connections of the E1 at the cabling rack if its status is "peer end out of

sync" or "peer end alarm".


4-2

5) After the status of the first E1 becomes normal, self-loop other E1 systems as per steps 2~4;

6) Restore all connectors to the normal status.

II. Self-loop all signaling links

Execute the command STR LNKTST to perform self-loop test on all signaling links. If the test fails, check the connections of corresponding cables as per the prompt information in the self-loop test report.

4.4 Joint Commissioning of Trunks and Signaling

4.4.1 Preparations prior to Joint Commissioning

The following preparatory work is necessary before the joint commissioning:

1) The network operator should have installed the E1s from the local distribution frame to the local transmission side, from the peer transmission side to the peer distribution frame, and from the peer distribution frame to the peer switching system.

2) The operational modes of E1s and the CIC numbering method have been determined by both offices;

3) The E1 system to which the signaling links belong and the timeslots occupied by the links in the E1 system have been determined by both offices;

4) Relevant data has been configured at the transmission side and the peer office; 5) Relevant data configuration and commissioning of the local office have already

been completed.

4.4.2 Basic Procedures for Joint Commissioning

The joint commissioning process includes the following three basic procedures:

I. Jointly commission E1 system

The specific procedures of the self-loop test are as follows:

1) Remove connectors of all E1s from the distribution frame;

Self-loop the first E1 system of the peer office with connectors.

Contact the peer office to check whether the port status of the first E1 system is normal;

If the status is abnormal, record the number of this E1 system;

If the status of this E1 is abnormal while the status of another E1 has become normal, the possible cause is that the two E1 systems are not correctly interconnected. Record this abnormality if any.


4-3

2) If the E1 status is normal and the status of another E1 suddenly turns from originally abnormal to normal now, the cause is that twisted interconnections of cables exist between the two E1s. To solve this problem, correct the cable connections at the cabling rack of the local or peer office.

3) Restore all connectors to normal status. 4) Self-loop other E1s of the peer office as per steps 2-7; 5) Notify the peer office and the transmission office of the numbers of the E1s that fail

the self-loop test and the E1s that are incorrectly interconnected. The three parties should negotiate about the resolution.

6) Conduct commissioning again on the adjusted E1s as per the above steps till all E1s of the peer office succeed in the self-loop test.

7) Execute the command DSP E1CH to check if the port status of each E1 is normal.

II. Jointly commission signaling links

The specific procedures of the signaling link test are as follows:

1) Use SS7 Tracing function on the maintenance console to trace the signaling links under commissioning.

2) Observe from the window [SS7 Tracing] if both receiving and sending of SS7 messages are normal.

3) Execute the command DSP N7LNK to view if the status of each signaling link is normal and if the SLS (Signaling Link Selection) code borne by the signaling link is in compliance with the load-sharing requirements.

III. Commission trunk circuits

1) Execute the command DSP N7C on the maintenance console to view the circuit status of the E1 system under commissioning.

2) Reset them with the command RST N7C if the status of some circuits is abnormal. 3) If those circuits are still in abnormal status after the reset, check whether the CIC

settings at the local and peer offices are consistent.

Note:

The above commissioning methods apply to SS7. Compared with SS7, R2 signaling system commission comprises no commission of signaling links. But the commission methods for trunks in R2 system are almost the same as those in SS7. In the actual office deployment, perform commissioning on the E1s, signaling links and circuits step –by step in the configured office directions. It is not necessary to wait until all office directions are configured.


4-4

4.5 Troubleshooting in Trunk and Signaling Commissioning

I. Data configuration is correct yet the port status of some E1 system is abnormal

Execute the section-by-section self-loop method to locate the faulty section from local end equipment to the distribution frame and the optical transceiver of the local end, then to the optical transceiver and the distribution frame of the peer end. When a certain section of cable is found faulty, first check whether the receiving and sending ends are wrongly connected, then whether the cable is damaged at some point(s).

II. Signaling links still can not be used for service transmission after data modification

Generally, the signaling links should be re-activated to successfully re-locate the links after the signaling link data have been modified.

III. The SLS borne by the signaling link is not in compliance with the load-sharing principle

The load-sharing function of signaling links is jointly determined by "Signaling Link Set Selection" and "Link Selection". If the bits in "Signaling Link Set Selection" and "Link Selection" set as "1" overlap, the load-sharing function might be unavailable.

Installation Manual - System Commissioning M900/M1800 MSC/SSP/IP Chapter 5 Service Commissioning

5-1

Chapter 5 Service Commissioning

5.1 Basic Procedures

Service commissioning can be conducted in four steps: 1) configure service data and execute the relevant scripts; 2) load data; 3) test services; and 4) verify charging.

The following preparatory work is necessary prior to the service test

1) Work out the dialing check plan and send it to the relevant switching offices. 2) Configure the test data of the local office as per the result negotiated with the

relevant switching offices; 3) Relevant service data have already been configured for relevant offices. 4) Network configuration between the office and the billing center have been

completed.

5.2 Data Loading

Basically, as service data is only related with the GSPC boards, it suffices to reset the GSPC boards for data loading. After the loading is completed, execute the command "STR CRC: MN=255;" to perform CRC check on all modules. For any module that fails the check, reset it again for loading.

Caution:

Wear antistatic wrist strap when powering on the system for loading! When resetting the GSPC board for loading, the GCPC board subordinate to it will perform reloading automatically.

5.3 Service Test

Prior to the test, register the related traffic measurement tasks, so that the traffic measurement results can be observed after the test.


5-2

5.3.1 Basic Service Dialing Test

I. Location update verification

Ordinary location update Periodic location update IMSI attach/detach Subscriber deletion

II. Local service dialing test

[Local Basic Call Dialing Test]

Intra-office ordinary subscribers, PPS subscribers and roaming subscribers respectively call ordinary subscribers, PPS subscribers and roaming subscribers in the intra-office, local office, national office and international toll office.

[Special Service Dialing Test]

Emergency call Special service emergency call

[Short Message Service Dialing Test]

Mobile originated short messages Mobile terminated short messages

[Paging Station Dialing Test]

[Information Station Dialing Test]

III. Foreign office service test

Ordinary subscribers, PPS subscribers and roaming subscribers in foreign offices (non-home local office, national office and international toll office) respectively call ordinary subscribers, PPS subscribers and roaming subscribers in the home office.

5.4 Supplementary Service Verification

I. Call forwarding

Call forwarding unconditional (CFU) Call forwarding on mobile subscriber busy (CFB) Call forwarding on mobile subscriber no reply (CFNRy) Call forwarding on mobile subscriber not reachable (CFNRc)

II. Presentation

Calling line identification presentation (CLIP)


5-3

Calling line identification restriction (CLIR) Connected line identification presentation (COLP) Connected line identification restriction (COLR)

III. Call completion services

Call hold (CH) Call wait (CW)

IV. Multi-party service (MPTY)

V. Closed user group service (CUG)

VI. Charging service

Advice of charge information (AoCI) service Advice of charge (Charging) AoCC service

VII. Call restriction services

Incoming call barring service, BAIC and BIC-Roam

Outgoing call barring service, BAOC, BOIC and BOIC-exHC

VIII. Unstructured supplementary service data (USSD)

IX. ODB service

5.4.1 IN Service Verification

I. Number segment triggered IN service

Number segment triggering PPS subscriber calls ordinary mobile subscriber Ordinary mobile subscriber calls number segment triggering PPS subscriber

II. MSC functions as OVERLAY SSP for tandem of IN calls from other MSC

OVERLAY IN subscribers call ordinary mobile subscribers Ordinary mobile subscribers call OVERLAY IN subscribers

III. Access code test

PPS subscribers dial IN service numbers to test subscription, recharging and query.


5-4

Note:

The above commissioning is conducted for the basic test items of the VMSC. Detailed test contents are described in M900/M1800 MSC/SSP/IP Acceptance Manual. Data configuration and operation methods related with the tests are described in the corresponding parts in M900/M1800 MSC/SSP/IP Operation Manual. Besides, M900/M1800 MSC/SSP/IP can function as independent VMSC, GMSC, or as combined equipment of VMSC and GMSC, therefore the services to be commissioned are not of the same type. Engineers should select the right service as per the actual requirements.

5.4.2 Handover Function Verification

Intra-MSC handover Inter-MSC handover Inter-MSC subsequent handover to the third-party MSC

Inter-MSC subsequent handover back to the original MSC

5.5 Charging Verification

Charging verification includes two parts: charging gateway verification and bill verification.

5.5.1 Charging Gateway Verification

This involves the server configuration verification, operational status verification and dual-system switchover check.

I. Server configuration verification

1) Check whether network adapter has been configured with the corresponding IP address.

2) Check whether the hardware installation and connection are normal. 3) Check whether any file is lost.

After running the setup program and copying files, if the server is restarted after iGWB software installation, check whether any files are lost. For example, files in the directory C:\Inetpub\wwwroot including Invoker.exe, BillAll.java and PWD.exe, etc. check whether the program files in C:\billsvr\bin are complete, and whether the following program files exist: Kernel.exe, Cluster.exe, Omm.exe, NetMsc.exe, Msgserver.exe, Killkernel.exe, Frontsave.exe, Convert.exe, Config.exe, BillFormt.exe, billalarm.exe, BackupModule.exe, Backsave.exe and ShowIcon.exe. Check whether Bill Remote service and Watch Dog Process service are available.


5-5

4) Check whether the first network adapter is in the first place

Click the menu [Start/Settings/Control Panels/Network] and select [Binding]. In the drop box [Show Bindings for], select "All Protocols". Open "TCP/IP Protocol” to make sure that network adapter No.1 is in the first place. If not, select network adapter No.1, click "Move Up" until it moves to the first place.

5) Check whether the virtual IP is correctly configured

Set virtual IP for the bill application console: The original IP of bill application console' virtual IP is the first IP address of the first network adapter. The first IP address of the first network adapter and the virtual IP address must be in the same network segment, while the virtual IP address cannot be conflicted with any other IP addresses.

6) Check whether the dual-system heartbeat is correctly configured

The local heartbeat address is the first IP address of the first network adapter, while the peer heartbeat address is the first IP address of the first network adapter of the peer server.

7) Check whether the setting of active/standby information is correct

Start the "iGateway Bill Config Tool" and check whether the "Backup Destination Path" for directories "iGateway Bill – Channel – Ch_1" and "iGateway Bill – Channel – Ch_2" are correctly set.

8) Check whether the billing center interface is correctly set

Start "iGateway Bill config Tool" and set "iGateway Bill – Miscellaneous – Billing center interface ". Its default setting is FTP, i.e. if the FTP protocol is used by the billing center for bill access, this item will not be configured.

9) Check whether the start status of "Process Watch Dog Service" is correctly set

After configuration and prior to iGWB running, set the start status of "Process Watch Dog Service" as "Manual", and modify it back to "Automatic" until all service checks succeed.

10) Check whether FTP/FTAM service is available

Confirm the protocol through which the billing center extracts bills and check whether the service of the corresponding protocol is available. If the FTP protocol is used, check whether the FTP service is available. If the FTAM protocol is used, and DSET products are installed, check whether ftr and osilanf services are available. If OpenFt is installed, check whether services like OSI-LAN Protocol, OpenFt FTAM, Server, OpenFt Security Server and OpenFt Server are availalbe.

11) Check whether ftp setting for active/standby bill servers are consistent

If the dirctory opened for the billing center is not set as "Writable" in the standby bill server, the billing center will be able to extract bills after switchover but cannot delete overdue bills.

12) Check whether the auto restart mechanism of BAM is normal


5-6

II. Operational status verification

1) Check whether the dual-system heartbeat is normal

Observe print messages of the program (run the program C:\billsvr\bin\msgserver.exe) and check whether any information in red is displayed, such as "HandShake timeout, Link1 is broken" or "HandShake timeout, Link2 is broken". These messages indicates that fault exists on the heartbeat link.

2) Check whether the connection between the iGWB and the host is normal

Observe print messages of the program (Run the program C:\billsvr\bin\msgserver.exe). The message "Local Primary links is 3, Secondary links is 1" indicates that 3 connections exist between the local server and the active SPC board, and 1 connection between the local server and the standby SPC board. The message "Peer Primary links is 3, Secondary links is 1" indicates that 3 connections exist between another server and the active SPC board, and 1 connection between the server and the standby SPC board.

3) Check whether bill can be received and saved normally

If the host has sent out bills, check whether bill files exist in the directory D:\BillFront\data\20020805 (20020805 is the bill generation date). If any bill file exists, it means bill files can be received and saved normally.

4) Check whether the bill application console can be activated

Start IE in the Client computer, enter the virtual IP address of the bill application console and the initial interface of the bill application console appears. Upon the first running of this console, it is necessary to install the Java operational environment and Java patch C:\Inetpub\wwwroot\plugin\JRE12.EXE on the initial interface. After the installation, click "Here to run Huawei iGateway Bill Console" to start this software. The default user name of this software is "admin" with the password as "sa".

5) Check whether sufficient space is available for each drive of iGWB 6) Check whether bills can be collected normally

Check the two file directories of iGWB E:\BillBack\backdatabak\CHL_1 and E:\BillBack\backdatabak\CHL_2. If bills generated 3-5 days ago exist in either of the two dirctories, delay must occur when the bill collecting software is applied for billing collection.

7) Check whether the CPU load is normal. The load should not be greater than 50% for a long time.

8) Check whether the MO drive can be normally read and written.

III. Dual-system switchover check

Check whether take-over by the active server is normal

1) Shut down the active server, start the standby server and run the iGWB software on it. then wait until it is activated.


5-7

2) After the standby server is activated, start the active server, and run the iGWB software on it to check whether it can be normally activated.

3) If the active server can be activated normally, this verification is successful; otherwise, check whether the configuration paramters of the active server are correct.

Check whether the take-over by the standby server is normal

4) Shut down the standby server, start the active server and run the iGWB software on it. Then wait until it is activated.

5) After the active server is activated, start the standby server and run the iGWB software on it.

6) Terminate the PWD service of the active server and run Killkernel.exe of it to exit its Kernel program.

7) Five minutes later, check whether the standby server is activated. If it can be normally activated, this verification is successful; otherwise, check whether the configuration paramters of the standby server are correct.

5.5.2 Bill Verification

After iGWB verification and basic service commissioning, it is necessary to check whether the formats of all fields of the bills generated in the local office are consistent with the requirements of the Client (such as calling number, called number, call start time, and call duration), whether all types of bills can be generated correctly, and whether long bills can be handled, etc. Bills of the following types should be specially checked:

I. MO bills

If a mobile subscriber respectively calls another mobile subscriber and fixed subscriber, check whether the generated bills are correct after successful connection and disconnection. Repeat the calls and check whether multiple identical bills with the same sequence No. are generated if the call times out.

II. MT bill

When a mobile subscriber is the called party, while the callers are respectively another mobile subscriber and a fixed subscriber, check whether the bills generated are correct after successful connection and disconnection. Repeat the calls and check whether multiple identical bills with the same sequence No. are generated if the call times out.

III. Roaming bill

Arrange a roaming mobile subscriber in the local office, or configure the roaming subscriber type (via the command ADD MSTY) to set the roaming type of the


5-8

subscriber, make calls to generate bills, and check whether roaming bills can be generated and whether the data is correct.

IV. Tandem bill

Check whether tandem bills can be generated and the charging data is correct.

V. Emergency call bill

After a mobile subscriber originates an emergency call, check whether an emergency call bill is generated and whether the data is correct.

VI. Call forwarding bill

Please refer to the checklist of the M900/M1800 MSC/SSP/IP Acceptance Manual and check whether all kinds of call forwarding bills can be generated, whether the data is correct, and whether supplementary service codes for the bills are correct.

VII. Call waiting bill

Please refer to the checklist of the M900/M1800 MSC/SSP/IP Acceptance Manual and check whether call waiting bills can be generated for all types of call waitings and whether the supplementary service codes for the bills are correct.

VIII. Call hold bill

Please refer to the checklist of the M900/M1800 MSC/SSP/IP Acceptance Manual and check whether call hold bills can be generated, whether the data is correct and whether the supplementary service codes for the bills are correct.

IX. Multi-party call bill

Please refer to the checklist of the M900/M1800 MSC/SSP/IP Acceptance Manual and check whether multi-party call bills can be generated, whether the data is correct and whether the supplementary service codes for the bills are correct.

Note:

What kind of bills will be generated are determined by the role of M900/M1800 MSC/SSP/IP in the network, subscriber attribute and call services, etc.


5-9

5.6 Troubleshooting in Service Commissioning

I. During the specified trunk test, the signaling procedure is correct but no ringback tone can be heard and neither party can hear each other’s voice

The cause is that the CIC configured for this trunk circuit in the local office is inconsistent with that in the peer office. In this case, inquire the peer office for the CIC configuration. If the CIC data configuration returned by the peer office is consistent with that of the local office, the cause might be that the E1 system has been interconnected incorrectly with another E1 system, as shown in the following figure. To solve this problem, disconnect the E1 from the distribution frame and query the number of the E1 in abnormal status in the peer office to locate the E1 that has been wrongly interconnected with by this E1 of the local office. Notify the transmission office to modify relevant data.

System A

System B

Receive

Send

Receive

Send

System A

System B

Receive

Send

Receive

Send

Local office Peer office

Figure 5-1 Wrong E1 interconnections

II. Monologue during specified trunk test

The occurrence of monologue is generally caused by twisted interconnections of cables, as shown in the following figure. To solve this problem, disconnect the E1 from the distribution frame and query the numbers of the two E1s in abnormal status to locate the two E1s that have been interconnected in a twisted way. Adjust the E1 cable position correspondingly from the distribution frame to solve this problem.


5-10

System A

System B

Receive

Send

Receive

Send

System A

System B

Receive

Send

Send

Receive

Local office Peer office

Figure 5-2 Mismatched cables

Installation Manual - System Commissioning M900/M1800 MSC/SSP/IP Chapter 6 Specified Trunk Commissioning

6-1

Chapter 6 Specified Trunk Commissioning

6.1 Significance of Specified Trunk Test

When the peer office is not being commissioned, extract 1~2 timeslots of each E1 in the local office to test the specified trunk. This is to test the availability of trunk circuit, A interface circuit, ToneID, speech channel, voice file, IWF channel, ECP channel and other physical channels. The test can be conducted without blocking the channels and circuits. Through the test, such problems as self-loop, monologue and poor speech quality, etc. can be found out, which is especially useful for the test of equipment operating on the network.

6.2 Test Type and Dialing Scheme

Currently supported specified test types and dialing schemes are listed in Table 6-1:

Table 6-1 Types and dialing schemes of specified tests

Serial No. Type of specified test Dialing scheme

1 Specified A interface circuit test x4*MID*BSN

2 Specified TUP trunk circuit test x5*MID*BSN

3 Specified ECP channel test x8*Ecp*Index

4 Specified Tone_ID test x1*Tone_ID

5 Specified SPT channel test x2*MID*Dev*Channel

6 Specified voice file test x3*MID*Dev*File

Where:

x: the call prefix configured; MID: module ID. It must be a three-digit number for A interface, TUP trunk and

ECP channel, e.g. 001. For other test type, it can be a number other than a three-digit number, e.g. 1;

BSN: the No. of the circuit to be tested. It is always a four-digit number like 0001; Channel: SPT channel No.; Ecp: ECP channel No. It is always a five-digit number like 00001; Index: the index of EC parameter. It is always a five-digit number like 00001; Dev: the type of Signal Tone board. "1" stands for GSPT board; File: the name of voice file.


6-2

6.3 Specified Trunk Test in VMSC

6.3.1 Specified Speech Test

I. Specified Tone_ID test

The specified Tone_ID test is conducted to verify the correctness of the basic synchronous tone table.

The following are voice files and contents correponding to the Tone_IDs in normal cases. If a Tone_ID is configured in the basic synchronous tone table, the synchronous tone should be heard during the specified test, otherwise the asynchronous tone will be heard.

Execute the command LST BASESYNTONE to query the synchronous tone table configured. The specific announcement contents are finalized by the network operator. For example: A network operator has set a comparison table of Tone_IDs and announcement contents as described in Table 6-2.

Table 6-2 Tone_ID and announcement contents

tone_id Voice file name Voice content Remarks

0 None Tone recorded in timeslot 0 64 seconds

1 fffff801 Last-minute announcement for IN subscriber

2 fffff802 Time announcement Played every 10 seconds around the clock

3 fffff803 Dial tone 450Hz, -10!3dBm0 and continuous

4 fffff804 Special dial tone 450Hz, -10!3dBm0, 0.4s ON/0.04s OFF

5 fffff805 Busy tone 450Hz, -10!3dBm0, 0.35s ON/0.35s OFF

6 fffff806 Ringback tone 450Hz, -10!3dBm0, 1.0s ON/4.0s OFF

7 fffff807 Incoming call stand by 450Hz, -20!3dBm0, 0.4s ON/4.0s OFF

8 fffff808 fffff608

Sorry, The telephone you called is out of service due to an outstanding invoice.

9 fffff809 Send test code 5E to the host


6-3


10 fffff80a fffff60a

Sorry! The nµmber you dialed is out of service.

11 fffff80b fffff60b

Sorry, The malicious call tracing operation is not successful.

12 fffff80c fffff60c Sorry, The called has applied for suspense.

13 fffff80d fffff60d

Sorry! you have not apply for IDD service, please make registrations, for more information, please dial 1860.

14 fffff80e fffff60e

Sorry! The network is busy now, please redial later.

15 fffff80f fffff60f

Sorry, The trunk is busy now, please try again later.

16 fffff810 fffff610

Sorry! Your telephone service is suspended, for more information, please dial 1860.


The subscriber you dialed is call forwarding, please hold on.


The called is busy now, please try again later.


The nµmber is incorrect, please check and dial again.


Sorry, the nµmber you dialed does not exist, please check it and redial.


Sorry! The way you are dialing is not correct, to make a fix to local mobile call, it is not necessary to include the "0", please dial 1860 for more information.


Sorry, The subscriber you dialed is not in the service area, please redial later.

23 fffff817 Two-stage dial tone 400Hz, -10!3dBm0, continuous


Sorry your mobile phone seems not supporting the AOC service.


Sorry, The subscriber you talked to has used up his card, and the call is over.

26 fffff81a fffff620

Sorry, Your telephone is out of service due to outstanding invoice.

27 fffff81b fffff621 Sorry, your call is restricted.

28 fffff81c Report malicious call number (after the host has downloaded the calling number)


6-4


29 fffff81d Music

30 fffff81e Congestion tone 450Hz, -10!3dBm0, 0.7s ON/0.7s OFF

31 Reserved


Sorry, called subscriber is not reachable, please dial later.


Sorry! The way you are dialing is not correct, to make a mobile to mobile call, it is not necessary to include the "0", please dial 1860 for more information.

34 Announcement recorded in timeslot 34 64 seconds

35 Announcement recorded in timeslot 35 64 seconds


The nµmber you are calling has been changed.


Sorry! The nµmber you dialed can not go through for a line breakdown. For more information, please dial 189 or 1860."


Sorry! The subscriber you dialed is incoming call forwarding, please hold on.


Sorry! The subscriber you dialed is busy now, please redial later!

40 fffff828 fffff628 Sorry, your prepaid card has been used up.

41 fffff829 Unallocated number tone

(450Hz, -10!3dBm0, 0.1s ON/0.1s OFF/0.1s OFF/0.1s off/0.1s ON/0.1s OFF/0.4s ON/0.4s OFF)


The nµmber you dialed has been upgraded, please add zero after the third dialed digital of original subscriber nµmber.


Sorry, Please omit the national code and dial again.

44 fffff82c fffff62c Sorry, the call forward is not successful.


Sorry, No channel available, please try again later.

46 fffff82e fffff62e

Sorry, Your telephone can make an emergency call only.

47 fffff82f fffff62f

Sorry! The have not applied for this service, please dial 1860 for more information.


6-5



Sorry! Please include area code before the nµmber you dialed, for more information, please dial 1860.


Sorry! The subscriber you dialed is busy now, please hold on.

50 fffff832 Three-party call alert 950Hz, -20!3dBm0, 0.4s ON/10.0s OFF

51 fffff833 Howler tone 950Hz 0.4dB

52 fffff834 Toll call announcement 450Hz, -10!3dBm0, 0.2s ON/0.2s OFF/0.2s ON/0.6s OFF


Hello! Please dial 110 for police, 119 for fire, 120 for ambulance and 122 for traffic accident.

54 fffff836 Mute 55H


Sorry! The incoming call of subscriber you dialed is barred.


Sorry! Your telephone charge is overdue, please recharge it, thank you!


Sorry, called mobile subscriber is busy, please dial later.


Sorry, the subscriber you dialed is powered off.


Sorry, the service is not available, please register it first.

60 fffff83c fffff63c

Sorry, this is not a local subscriber, please add zero before the phone nµmber.


Sorry! The subscriber you dialed is no answer, please redial later.

62 fffff83e fffff63e Call is on hold, please wait for a moment.

Operation procedures for specified Tone_ID test are as follows:

1) Add authority for the MS

Suppose the number of the MS is 13307556666 (without country code)

ADD TSTRHT: D=K'13307556666;

2) Execute the command MOD SFP to set bit13 (new service and supplementary service support flag of incoming call) of the software parameter P49 (Calling


6-6

Internal Parameter 1) to "0", then new services and supplementary services are supported for incoming calls.

3) Add call prefix

Suppose the call prefix is 789:

ADD CNACLD: P=0, PFX=K'789, CSTP=NEW, CSA=TON, MINL=6, MAXL=10, CLDT=PSTN;

Caution:

[Service Category] should be set to "New Service/Supplementary Service" and [Service Attribute] should be set to "Voice Playback".

4) Add calling number analysis data for the MS

Suppose the number of MS is 13307556666 (without country code)

ADD CNACLR: CSC=0, CID=K'13307556666, PFX=K'789, RUT=TST;

Caution:

[Calling Number] should be configured as a complete MS number (without country code), while [Calling Subscriber Type] should be configured as "Test".

5) Dialing test

To test TONE_ID=18, dial 7891*18 with the MS of number 13902700021. You should hear the announcement "The subscriber you dialed is busy. Please dial again later" (The specific announcement is defined by the network operator).

II. Specified speech channel test

This test is conducted to verify the correctness of synchronous tone play on the board.

Operation procedures are as follows:

1) Add test authority


ADD TSTRHT: D=K'13307556666;


6-7

2) Execute the command MOD SFP to set bit13 (new service and supplementary service support flag of incoming call) of the software parameter P49 (Calling Internal Parameter 1) to "0", then new services and supplementary services are supported for incoming calls.

3) Add call prefix

Suppose the call prefix is 789.


Caution:

[Service Category] should be set to "New Service/Supplementary Service", while [Service Attribute] should be set to "Voice Playback"

4) Add caller analysis data



Caution:


5) Upon specified channel test, the announcement to be played can be configured in the basic synchronous tone table. TONE_ID is set to 58.

ADD BASESYNTONE: TONEID=RESERVE58, CODE1="FFFFF830";

Then the prompt announcement "Sorry! The subscriber you dialed has powered off" will be heard every time when test of the specified channel is performed (The specific announcement is defined by the network operator).

6) Dialing test

To test SPT channel 70 of module 1, dial 7892*1*1*70 with the MS of number 13307556666 ;


6-8

To test SPT channel 70 of module 8, dial 7892*1*1*230 with the MS of number 13307556666.

Caution:

In the test of GSPT board, the call can be conducted via any module.

III. Specified voice file test

Contents of all announcements loaded to the board (including basic synchronous tone, IN service tone, tone elements) can be checked via specified voice file test.

Note:

During specified voice file test, announcements are played in the synchronous tone mode.

Operation procedures for specified voice file test are as follows:



ADD TSTRHT: D=K'13307556666;


3) Add call prefix

Suppose the call prefix is 789


Caution:

[Service Category] should be set to "New Service/Supplementary Service", while [Service Attribute] should be set to "Voice Playback".


6-9




Caution:


5) Dialing scheme

Voice file codes can be divided into two types, as described in Table 6-3:

Table 6-3 Dialing scheme for specified voice file

Example Voice file

code format Dialing test

method Name of the voice file to be tested Dialing scheme

fffff802 ***3*mid*dev*802(*** is the call prefix)

fffff80a ***3*mid*dev*80#0 or ***3*mid*dev*80*0 fffffxyz Enter xyz directly

fffff82f ***3*mid*dev*82#5.or ***3*mid*dev*82*5

00000002 ***3*mid*dev*00000002

01400006 ***3*mid*dev*01400006 All other voice codes not belonging to the first type

Enter 8 digits for all codes

0140000a ***3*mid*dev*0140000#0 or *3*mid*dev*0140000*0

Note:

1) Handling methods for numbers greater than 10 in the hexadecimal voice codes: If a, b, c, d, e, or f exists in the file name, dial two digits, with "*"or "#" as the conversion symbol. For instance: The dialing mode for hexadecimal number "a" is "*0" or "#0"; while that for "b" is "*1" or "#1". This method is valid for all the rest by analogy. 2) To specify voice files of SPM modules for test, the Module No. can be the number of any SPM module since voice files are shared resources. 3) If there are multiple GSPT boards, the current tone-play board is selected in turn. The same voice file can be specified for test for several times so as to test all the boards. 4) Please refer to Table 6-2 Tone_ID and Announcement Contents to get the information about file names and contents of basic synchronous tones.


6-10

6.3.2 Specified A Interface Circuit Test

Operation procedures of specified A interface circuit test are as follows:


Suppose the number of the calling MS is 13902700021 (without country code)

ADD TSTRHT: D=K'13902700021;


3) Add call prefix


ADD CNACLD: CSTP=BASE, PFX=K'789, CSA=SPL, MINL=13, MAXL=17;

Caution:

[Service Category] should be configured as "New Service/Supplementary Service", while [Service Attribute] as "Private Line Call". The value of [Minimum Number Length] should be the call prefix length plus 10.

4) Add number conversion

The converted number is 13902700020 (a mobile number in the home office)

ADD DNC: DCX=2, DCT=MOD, DCP=0, DCL=13, ND=K'13902700020;

Caution:

Set [Number Conversion Type] to "Change All".


Suppose the calling number is 13902700021.

ADD CNACLR: CSC=0, CID=K'13902700021, P=0, PFX="***", DDCX=2 , RUT=TST;


6-11

Caution:

[Called Number Conversion Index] should be consistent with [Number Conversion Index] configured in the command ADD DNC (2 is selected in this example). [Calling Subscriber Type] should be configured as "Test".

6) Test process

Both blocked and unblocked local circuits can be used for specified A interface test. Generally, the circuit to be used for specified A interface test is blocked in the local end before the test and unblocked after the test to ensure that this circuit is not seized by another call.

To test circuit 1 of module 1, dial 7894*001*0001 with the MS whose number is 13902700021. If the call is connected, the MS of the number 13902700020 should ring, and the conversation after hookoff should be normal. Command DSP AC can be executed to check whether the circuit is seized.

6.3.3 Specified TUP Circuit Test




ADD TSTRHT: D=K'13902700021;


3) Add call prefix



Caution:



6-12


Suppose the number after conversion is 26540001 (it cannot be a home office mobile number)

ADD DNC: DCX=2, DCT=MOD, DCP=0, DCL=13, ND=K'26540001;

Caution:

1. Set [Number Conversion Type] to "Change All". 2. The called number after conversion (such as 26540001 in the example) should be in the office direction to which the TUP circuit belongs. Otherwise the test will fail. 3. The specified trunk test does not support the circuit test in the R2 signaling system but TUP or ISUP circuit test.


Suppose the number of the calling MS is 13902700021

ADD CNACLR: CSC=0, CID=K'13902700021, MAXLEN=24, P=0, PFX="789", DDCX=2, RUT=TST;

Caution:


6) Test process

Both blocked and unblocked circuits at the local end can be used for specified TUP circuit test. Therefore the circuit is always blocked prior to the test and unblocked after the test so that this circuit is not seized by another call.

Normally, the result of the specified TUP circuit test is that the call is connected and successful, and the specified TUP circuit is in the seized status at the same time.

To test circuit 33 of module 1, dial 7895*001*0033 with the MS whose number is 13902700021. After the call is connected, the phone 26540001 should ring, and the conversation after hookoff should be normal. In this case, command DSP N7C can be executed to view whether the circuit is seized.


6-13

6.3.4 Specified ECP Channel Test




ADD TSTRHT: D=K'13902700021;


3) Add call prefix



Caution:



Suppose the number after conversion is 26540001

ADD DNC: DCX=2, DCT=MOD, DCP=0, DCL=13, DAI=UDN ND=K'26540001;

Caution:

Set [Number Conversion Type] to "Change All",


Suppose the number of the calling MS is 13902700021

ADD CNACLR: CSC=0, CID=K'13902700021, MAXLEN=16, P=0, PFX="789", DDCX=2, RUT=TST;


6-14

Caution:


6) Test process

To test the ECP channel 1023 with the EC parameter index 1, dial 7898*01023*00001 with the MS of number 13902700021. After the call is connected, the phone 26540001 should ring.

The conversation after hookoff should be normal. In this case, command DSP RESCH can be executed to view whether the ECP circuit is seized.

6.4 Specified Trunk Test of GMSC

6.4.1 Special Test Call Prefix for Tandem to GMSC

The end office uses a special call prefix to originate a call, and connects it to GMSC via tandem. Then GMSC sends the call to one end office connected with the specified outgoing trunk.

I. Originate calls from fixed end office to test specified outgoing trunk in GMSC

1) In the end office, configure number analysis data which can be routed to the GMSC via the call prefix "139B".

2) Execute the command MOD SFP to set bit13 (new service and supplementary service support flag of incoming call) of the GMSC software parameter P49 (Calling Internal Parameter 1) to "0", then new services and supplementary services are supported for incoming calls.

3) In GMSC, configure the call prefix as "139B", [Service Category] as "New Service/Supplementary Service", [Service Attribute] as "Private Line Call", and both [Minimum Number Length] and [Maximum Number Length] as "14".

4) In GMSC, configure a number conversion index. Set [Number Conversion Type] to "Change All", and [New Number] to a fixed subscriber number or a VMSC MSISDN under test

5) In GMSC configure a calling number analysis record for called number conversion:

Set [Call Source Code] consistent with the call source code of the fixed end office trunk. Set [Caller Number] to the calling number used for dialing test (area code is also


6-15

required if it is attached in IAI), [Calling Subscriber Type] to "Test", [Call Prefix] to “139B”, and [Called Number Conversion Index] to the index added previously.

6) Dial the following numbers to test the specified trunks:

For example: In the number 139*5*001*0063, the first 6 digits are fixed. 001 stands for the module number (ranging from 000 to 127), while 0063 for the No. of the specified trunk circuit for test (ranging from 0000 to 6399).

In summary, the dialed number should be of 14 digits and the called number in the incoming IAI signaling should be in the format of 139B5B001B0063.

7) To test a specified trunk from GMSC to the calling fixed end office, execute the command MOD SFP to set the software parameter "P75 (Nesting Dialing at the Same Office Direction Allowed)" to "1".

Note:

In the called numbers of IAI messages sent from the fixed end office and VMSC, "B" stands for different meanings: "B" stands for "*" in the former, while in the latter, it stands for "#".

II. Originate calls from VMSC to test specified outgoing trunk in GMSC

The operation method is similar to that used to originate calls from the fixed end office:

1) In the VMSC, configure number analysis data which can be routed to the GMSC via the call prefix "139B".


3) In GMSC, set the call prefix to "139B", [Service Category] to "New Service/Supplementary Service", [Service Attribute] to "Private Line Call", and both [Minimum Number Length] and [Maximum Number Length] to "14".

4) In GMSC configure a number conversion index. Set [Number Conversion Type] to "Change All", and [New Number] to a fixed subscriber number or a VMSC MS number under test

5) In GMSC, configure one calling number analysis data record for called number conversion:

Configure [Call Source Code] consistent with the call source code of the VMSC trunk. Set [Calling Number] to the calling subscriber number used for dialing test (country code is also required if it is attached in IAI), [Calling Subscriber Type] to "Test", [Call Prefix] to "139B" and [Called Number Conversion Index] to the index added previously.


6-16

6) Dial the following number to test the specified trunks:

For example: In the number 139#5#001#0063, the first 6 digits are fixed, 001 stands for Module ID (ranging from 000 to 127), and 0063 for the No. of the specified trunk circuit to be tested (ranging from 0000 to 6399).

In summary, the ldialed number should be of 14 digits and the called number in the incoming IAI signaling should be in the format of 139B5B001B0063.

7) To test a specified trunk from GMSC to the VMSC where the caller is located, execute the command MOD SFP to set the software parameter P75 (Nesting Dialing at the Same Office Direction Allowed) to "1".

Note:

In the called number of IAI messages sent from the fixed end office and VMSC, "B" stands for different meanings: "B" stands for "*" in the former number, while in the latter, it stands for "#".

6.4.2 Not Special Test Call Prefix for Tandem to GMSC

Conduct calling number analysis and number initial special processing for a test number sent from end office and convert the called number into the specified trunk test number to be used (in the format of XXXX5BXXXBXXXX).

I. Originate calls from fixed end office to test specified outgoing trunk in GMSC

1) Make sure one call prefix of the end office can be routed to GMSC. The call prefix 138888 is used in the following as an example.


3) In the GMSC, configure the corresponding called number prefix "138888". Set [Service Category] to "Basic Service", [Service Attribute] to "Local", both [Maximum Number Length] and [Minimum Number Length] to "13", and [Called Number Type] to the user number type in the office connected with the specified outgoing trunk.

4) Configure two number conversion indices in GMSC: Set [Number Conversion Type] to "Change number in positive sequence of

designated position", [Conversion Start Position] to "0", [Number Conversion Length] to "6", and [New Nubmer] to "138B5B".


6-17

Set [Number Conversion Type] to "Insert number at designated position", [Conversion Start Position] to "9", and [New Nubmer] to "B".

5) Configure calling number analysis data in the GMSC for called number conversion:

Set [Call Source Code] consistent with the call source code of the fixed end office trunk. Set [Calling Number] to the number of the calling PSTN subscriber for dialing test (Area code is also required if it is attached in IAI), [Call Prefix] to "138888", and [Called Number Conversion Index] to the first conversion index added in Step 4.

6) Configure number initial special processing data in GMSC:

Set [Call Source Code] consistent with the call source code of the fixed end office trunk, [Called Number] to "138B5B", [Called Number Conversion Flag] to "Yes", and [Re-analyze] to "Yes". Set [Called Number Conversion Index] to the second conversion index added in Step 4.

After the above two conversions, the number format becomes "138B5BxxxBxxxx". The following is another conversion for this number.

Note:

The premise for number conversion is that both [Calling Number Analysis Flag] and [Called Number Special Processing Flag] of 138888 in Call Prefix Analysis table are set to "Yes".

7) Configure the call prefix "138B" in GMSC. Set [Service Category] to "New Service/Supplementary Service", [Service Attribute] to "Private Line Call", and both [Minimum Number Length] and [Maximum Number Length] to "14".

8) Configure one number conversion index in GMSC. Set [Number Conversion Type] to "Change All", and [New Nubmer] to the tested fixed user number or MSISDN.

9) In GMSC, configure one calling number analysis data record for called number conversion:

[Call Source Code] must be consistent with the call source code of the trunk from the PSTN fixed end office to the GSMC. Set [Calling Number] to the calling user number used for test (Area code is also required if it is attached in IAI), [Calling Subscriber Type] to "Test", [Call Prefix] to "138B", and [Called Number Conversion Index] to the number conversion index added in Step 8.


For example, in the number 1388880010063, the first 6 digits are fixed, 001 stands for Module ID (ranging from 000 to 127), and 0063 for the No. of the specified trunk circuit to be tested (ranging from 0000 to 6399).

The dialed number should always be of 13 digits.


6-18

11) To test the specified trunk from GMSC to the fixed end office, execute the command MOD SFP to set the software parameter P75 (Nesting Dialing at the Same Office Direction Allowed) to "1".

II. Originate calls from VMSC to test specified outgoing trunk in GMSC

The operation method is similar to that used to originate calls from the fixed end office:

1) Make sure one call prefix of the VMSC can be routed to GMSC. The call prefix 138888 is taken as example in the following description.


3) In GMSC, configure the call prefix "138888" for the corresponding called number analysis in GMSC. Set [Service Category] to "Basic Service", [Service Attribute] to "Local", both [Maximum Number Length] and [Minimum Number Length] to "13", and [Called Number Type] to the user number type in the office connected with the specified outgoing trunk.

4) Configure two number conversion indices in GMSC: Set [Number Conversion Type] to "Change number in positive sequence of

designated position", [Conversion Start Location] to "0", [Number Conversion Length] to "6", and [New Nubmer] to "138B5B".

Set [Number Conversion Type] to "Insert number at designated position", [Conversion Start Location] to "9", and [New Nubmer] to "B".

5) Configure calling number analysis data in the GMSC for called number conversion:

Set [Call Source Code] consistent with the call source code of the fixed end office trunk, [Calling Number] to the calling MSISDN used for test (country code is also required if it is attached in IAI), [Call Prefix] to "138888", and [Called Number Conversion Index] to the first conversion index added in Step 5.

6) Configure number initial special processing data in GMSC:

Set [Call Source Code] consistent with the call source code of the fixed end office trunk, [Called Number] to "139B5B", and [Called Number Conversion Flag] to "Yes". Set [Called Number Conversion Index] to the second conversion index added in Step 3, and [Reanalyze] to "Yes".

After the above two conversions, the number format becomes "138B5BxxxBxxxx". The following is another conversion for this number.


6-19

Note:

The premise for number conversion is that both [Calling Number Analysis Flag] and [Called Number Special Processing Flag] of 138888 in Call Prefix Analysis table are set to "Yes".

7) Configure the call prefix "138B" in GMSC. Set [Service Category] to "New Service/Supplementary Service", [Service Attribute] to "Private Line Call", and both [Minimum Number Length] and [Maximum Number Length] to "14".

8) Configure one number conversion index in GMSC. Set [Number Conversion Type] to "Change All", and [New Nubmer] to the fixed user number or VMSC MSISDN used for test.

9) Configure one calling number analysis data record for called number conversion

[Call Source Code] must be consistent with the call source code of the trunk from the VMSC to the GMSC. Set [Calling Number] to the calling user number used for test (country code is also required if it is attached in IAI), [Calling Subscriber Type] to "Test", [Call Prefix] to "138B", and [Called Number Conversion Index] to the number conversion index added in Step 8.


For example in 1388880010063, the first 6 digits are fixed, 001 stands for the Module No. (ranging from 000 to 127), and 0063 for the specified trunk circuit No. to be tested (ranging from 0000 to 6399).

The dialed number should always be of 13 digits.

To test a specified trunk from GMSC to the VMSC where the caller is located, execute the command MOD SFP to set the software parameter P75 (Nesting Dialing at the Same Office Direction Allowed) to "1".

Installation Manual - System Commissioning M900/M1800 MSC/SSP/IP Chapter 7 Equipment Preliminary Acceptance and Cutover

7-1

Chapter 7 Equipment Preliminary Acceptance and Cutover

7.1 Equipment Preliminary Acceptance

After completing the service commissioning, the office deployment personnel should conduct preliminary acceptance of the equipment together with the personnel from the office party as per the plan. In the process, each preliminary acceptance item should be checked and verified according to the M900/M1800 MSC/SSP/IP Acceptance Manual. The results should be submitted to the office party for confirmation.

7.2 Cutover

Generally, the cutover should be conducted after 24:00 at night. Before the cutover, consultations should be made with the office party so as to determine the cutover scheme of the equipment. Unified cutover should apply to all switching offices before putting the equipment into operation. In the process of cutover, cooperation of various switching offices is needed to modify the relevant data so that the services point to the newly-added MSC.

Installation Manual - System Commissioning M900/M1800 MSC/SSP/IP Appendix A Upgrade Instruction

A-1

Appendix A Upgrade Instruction

The M900/M1800 MSC/SSP/IP system software can be upgraded in two steps:

1) Upgrade the BAM server software through the setup/upgrade tool

Upgrade tool are provided in the setup software and can be used to upgrade the software version of the BAM server. (For terminal workstation, the upgrade can be completed by reinstalling the terminal software).

2) Upgrade the host programs by loading programs and data

After BAM is upgraded, load the new host programs and data to the foreground and the host programs is then upgraded.

Caution:

The upgrade instruction in this chapter is the general instruction. The upgrade of a specific version should be in compliance with the upgrade instruction applied for the on-site upgrade!

A.1 Setup/upgrade Tool

For the sites operating online, smooth upgrade of the original software version at the minimum cost is required. Therefore, convenient, swift, safe and reliable upgrade tool are needed.

A.1.1 Path of Upgrade Tool

The M900/M1800 MSC/SSP/IP system provides terminal upgrade tool. The upgrade tool and their support files are stored in Upgrade directory of the software setup CD. If this directory not exist, the upgrade function is not provided.

Not all versions of BAM setup CDs provide the BAM upgrade function, since the upgrade function is oriented towards some basic versions. Before using the BAM server upgrade function, check whether the version provides this function and make sure of the basic version it supports.


A-2

Caution:

Different upgrade tools are used for different host programs. And these tools can upgrade any earlier version to their representing version by default. Make clear the version represented by the upgrade tool before the upgrade, so as to avoid upgrade error or failure.

A.1.2 Functions of Upgrade Tool

The upgrade tool are mainly used to upgrade the software version of the BAM server. The BAM server upgrade involves the upgrade of the data stored in the server, including the BAM database, BAM applications and data, host programs and host data.

For BAM applications, BAM data, host programs and host data, the upgrade can be completed by overwriting the old files with the latest version.

For the BAM database, the differences between versions are: additions and deletions of tables and fields in the tables, and modification of the field value. But it is required that the original data be saved before the upgrade.

The complex part of the upgrade is BAM database upgrade.

To upgrade the M900/M1800 MSC/SSP/IP system, it is necessary to load programs and data to the host after the BAM server is upgraded.

A.1.3 Application Environment of Upgrade Tool

To guarantee the operation success, the upgrade tool should be run in the BAM server of M900/M1800 MSC/SSP/IP.

A.2 Upgrade BAM Software with Setup/Upgrade Tool

With the setup/upgrade tool, the BAM system of original version can be upgraded to the latest version. After confirming that the setup CD of the current version provides the upgrade function, you can upgrade the software through the following operations.


A-3

Caution:

In the upgrade process, follow the instructions given by the setup program. Do not force to abort the setup program as it might lead to the unavailability of the BAM database. In the case the BAM database becomes unavailable due to abnormal abortion, check whether the backup database "BamOldBackup" is available. If yes, change its name to "Bam" to recover the original "Bam" database. The backup database file is automatically created by the setup/upgrade program at the beginning of the upgrade.

A.2.1 Preparations

I. Make sure BAM is operating normally prior to the upgrade

Prior to the version upgrade, make sure the BAM server to be upgraded is in the normal operational status. Otherwise the upgrade is not allowed.

II. Get the information of the current version in the BAM server and the target version to be upgraded to

The version upgrade tool contrapose some basic versions. Therefore it is mandatory to know the information of the current version in the BAM server and the information of the target version to be upgraded to before the upgrade starts definitely.

With the command DSP EXVER, you can get the information of the current version of the BAM server and the current version information of all modules in the host.

To get the information of the BAM target version to be upgraded, you should query the Release Notes or contact the version administrator.

III. Check the data consistency between the BAM and the host

Before the version upgrade, make sure the data in the BAM database are consistent with those in the host.

Execute the command "STR CRC: MN=255;" to conduct CRC on all modules between the foreground and the background, and check the returned result.


A-4

Caution:

Make sure all data tables are consistent. For inconsistent tables, locate the causes for inconsistency, and then decide whether to start the upgrade.

IV. Get the BAM software and data of the target version

Get the upgrade software and data of the target version, including the following basic data:

MML configuration script The BAM database generated with MML script

V. Check the upgrade tool of the target version

Check whether the obtained version upgrade tool are correct. The tool are stored in the sub-directory named upgrade in the directory of the setup CD. Under this directory is the file readme.txt, which records the version upgrade modes supported by the obtained upgrade tool. Check whether the tool support the version upgrade plan to be started.

VI. Make sure all alarms have been handled

During the upgrade process, the latest alarm database will directly replace the previous, and all previous alarms will then get lost automatically and cannot be queried. Therefore it is necessary to check with the network operator whether all alarms have been handled before the upgrade.

VII. Make sure all traffic measurement tasks and results have been processed

During the upgrade process, the lastest traffic measurement database (Stats) will directly replace the previous, all previous traffic measurement tasks and measurement results then cannot be queried after the upgrade, and all traffic measurement tasks will have to be registered again via corresponding commands. Therefore it is necessary to make sure before the upgrade that all traffic measurement results have been processed and command script files are available which will be used to register all the traffic measurement tasks again after the upgrade.

VIII. Start the emergency workstation to substitute BAM

Start the emergency workstation to substitute the BAM server: Take off the network cable from the BAM server and connect it to the emergency workstation. Make sure this emergency workstation can function as the BAM server and work normally.


A-5

IX. Back up BAM databases

Method 1:

Execute the MML comand BKP dB to backup the BAM databases at the Client. Backup files are stored in the default backup directory. (The directory can be selected during BAM setup. The default is F:\iMSC\). The following are the backup databases, registries and INI files:

AlarmYYYYMMDD.dat (Alarm database)

BamYYYYMMDD.dat (BAM database)

StatsYYYYMMDD.dat (Traffic measurement database)

TestYYYYMMDD.dat (Test database)

BamRegYYYYMMDD.bak (Registry data)

BamIniYYYYMMDD.bak (INI File)

In the above items, YYYY stands for backup year, MM for month, and DD for date.

If the backup directory and setup directory (This can be selected during BAM setup. The default is D:\iMSC\.) are consistent, or the backup directory is the subdirectory of the setup directory, the backup files should be copied to another directory so that the BAM database can be restored to that before the upgrade in the case of upgrade failure.

Method 2:

The database can be backed up with SQL Server Enterprise Manager. In this way, only the corresponding databases can be backed up, excluding the registries and INI file.

Registry files can be backed up manually: Run the registry editor program Regedit.exe, and select the registration key "HKEY_LOCAL_ MACHINE\SOFTWARE\Huawei\VMSC" to export the registry files.

The procedures to back up the database with the SQL Server Enterprise Manager are as follows:

1) Select [Start/Programs/Microsoft SQL Server 2000/Enterprise Manager] to start the Enterprise Manager process.

2) Select the database Bam. Right click to select [All Tasks/Backup Database]. 3) Click <Remove> to delete the default file names in the list "Backup to". 4) Click <ADD> and fill in the backup path and file name. 5) Click <OK> to finish backing up the database Bam. 6) Repeat the above procedures to back up other databases such as Alarm, Stats,

Test and VDP, etc.


A-6

Caution:

For the sake of security, it is recommended to manually back up the BAM applications and databases in D:\iMSC\, that is, copy all files under this directory to the folders in the backup directory.

X. Back up the original host programs, patches and data

During version upgrade, both the host programs and data are overwritten by the latest version. For the sake of version fallback in case of upgrade failure, the host programs, patches and data should be backed up before the upgrade. That is, copy the host programs and data directory (D:\iMSC\Hostdata\) to the backup direcotry.

Caution:

Copy this directory to another computer (the emergency workstation if possible for the purpose of emergency restoration) to avoid the loss of backup files in the case of BAM failure.

XI. Manually back up original registry files

Select [Start/Run/REGEDIT] to run the registry program Regedit.exe, export the registry file. and save it in the specified directory.

A.2.2 BAM Software Upgrade Procedures

The common software upgrade using the upgrade tool are as follows:

I. Exit BAMService, Smirror and Process Watch Dog services and set the startup mode again

1) Exit BAMService, Smirror and Process Watch Dog services

Select [Start/Settings/Control Panel] to pop up the window [Control Panel].

In the popup window, select [Service] to pop up the [Services] dialog box, which is shown in Figure A-1. Select "BAMService" from this box and then click <Stop>. In the next popup dialog box as shown in Figure A-2, click <YES> to exit the BAMService.

The operations to exit Smirror and Process Watch Dog services are completely the same as those of BAMService.


A-7

Figure A-1 "Services" dialog box

Figure A-2 Close BAMService service

2) Modify the service modes of BAMService, Smirror and Process Watch Dog services

Click <Startup…> in the [Services] dialog box, set "Startup Type" to "Manual" in the popup service parameter dialog box, then click <OK> to end the operation, as shown in Figure A-3.


A-8

Figure A-3 Modify the service mode of BAMService

The operations to modify the service mode of Smirror and Process Watch Dog are completely the same as those of BAMService.

3) Exit "Security Manager" and other software

Exit "Security Manager" on the BAM server and all Client software, and then shut down the Clients on all workstations. Exit all programs possibly connected with the SQL server database of the BAM, such as TableBrowser, Enterprise Manager and Query Analyzer, etc.

Click <Close> in the [Service] dialog box to end the operation.

II. Eixt the BAM program and interrupt all connections to the database

1) Unplug the network cable between BAM and LAN Switch. 2) Exit BAM Manager

After exiting the BAMService, exit all programs running on BAM. Double click the BAM Manager icon in the lower right of the taskbar to pop up the window [BAM Manager]. Click <Exit> in the menu bar to pop up the dialog box [BAM Security Manager], then click <YES> to end the operation, as shown in Figure A-4.


A-9

Figure A-4 Exit BAM Manager

3) Exit BAM gateway

Click "BAM Communication Network Gateway" in the taskbar to pop up the interface [BAM Communication Network Gateway]. Select [Operation/Exit], then click <YES> in the [Exit] dialog box to end the operation, as shown in Figure A-5.

Figure A-5 Exit the BAM gateway

III. Start Installation/upgrading tool to upgrade

1) Select upgrade mode

Double click file "Setup.exe" in the setup CD to run the setup/upgrade tool. Select the upgrade mode "Update M900/M1800 Server Program", then click <Next>, as shown in Figure A-6.


A-10

Figure A-6 Select the Upgrade mode

2) Upgrade BAM database

The setup/upgrade tool will first back up the background database automatically so that the database can be automatically restored in the case of upgrade errors. The backup database is named "BamOldBackup" automatically by the system. If the BAM database becomes unavailable due to abnormal interruption during the upgrade process, change this name to "Bam" to restore the original "Bam" database.

Then the latest database files will be copied automatically.

Caution:

Do not click <Cancel> during file copying, otherwise data in the BAM database will be lost!

The setup/upgrade tool will upgrade the BAM database automatically after all database files are copied. During the upgrade process, an operational status bar indicating [Upgrading tools are working...] is shown in the window.

This indicates that the setup/upgrade tool is upgrading the BAM database. Please wait patiently.

3) Upgrade terminal applications, terminal data, host programs, and host data


A-11

After upgrading the database, the setup/upgrade tool will continue to upgrade the terminal applications and data as well as the host programs and host data.

First, it will back up the programs and applications of the original environment automatically, next update the terminal applications and data, and finally update the system information.

IV. Restart BAM to start the BAMService and BAM programs

After the above operations are completed, select the prompt "Yes, I want to restart my computer now" in the popup interface, and then click <Finish> to restart the BAM.

After the BAM is restarted, click [Start/Settings/Control Panel/Service] to open the [Service] dialog box. Check whether the service status of BAMService is "Started" and whether the start parameter is "Automatic". If BAMService has not been started, select BAMService, then click <Start> to start the service. And if the startup status is not "Automatic", click <Startup…> to set the startup parameter to "Automatic".

V. Plug the network cable back to the BAM server

Take off the network cable from the emergency workstation and plug it back to the BAM server. Now the BAM software has been successfully upgraded.

Caution:

If you have manually modified the system environment, the setup program will not be able to proceed in the correct way.

A.2.3 Handle BAM Software Upgrade Failure

I. Log files generated in the upgrade

During the version upgrade process, the upgrade tool of the “Bam” database will create an operation log file in the setup directory (D:\iMSC) during the operation process. The name of this file is in the format like "UpgradeY2001M09D28H19M34.txt". In this format, the four digits after "Y" stand for the upgrade year, the two digits after "M" for month, the two digits after "D" for date, the two digits after "H" for hour, and the two digits after "M" for the upgrade minute. If any error occurs during the upgrade of "Bam" database,


A-12

please find the log file created during the upgrade and transfer it to Huawei local branch to locate the error.

II. Uninstall BAM manually

1) Delete service programs

Execute the following two commands in the DOS mode:

D:\iMSC\Services\BAMService -UnregServer

D:\iMSC\Services\smirror –UnregServer

In the above two commands, "D:\iMSC\" should be the BAM software setup directory.

If BAMService is still in operation at this time, it should be terminated first.

Then select [My Computer/Control Panel/Service] to open the [Service] dialog box. At this time, the two services BAMService and Smirror cannot be found.

2) Delete registration information

Run the regedit.exe program to open the registry editor. Find the key "HKEY_LOCAL_MACHINE\ SOFTWARE\HuaWei" and delete the subkey "VMSC60".

3) Delete database

Run SQL Server Enterprise Manager and select the databases belonging to MSC, including: Bam, Alarm, Stats, Test and VDP, then delete them one by one.

4) Process program directories

Record the program directory (D:\iMSC\), the database log file directory (E:\iMSC\), and the database backup file directory (F:\iMSC\) in the current BAM server. Open [My Computer] and delete the former two directories. During the deleting process, select "YES" in all dialog boxes. Save the database backup file directory in another name.

5) Restart the computer

III. Restore original BAM

1) Install BAM of original version

Run the BAM setup program of the original version to setup the BAM. During setup, make sure the program directory, database log file directory and the database backup file directory are the same respectively with those used in the previous setup.

2) Restore original database

Make sure that no program is connected with the SQL Server database on BAM. Run "SQL Server Enterprise Manager", find the database server corresponding to the BAM server. Right click on the node [Databases] and select [All Tasks/Resotre Database... ] in the popup shortcut menu to restore the database.


A-13

If the database is successfully restored, a dialog box will pop up indicating the success. If the operation fails, a dialog box will also pop up indicating the failure. The cause for this failure is usually that a certain program is connected with the database to be restored.

3) Restore databases "Alarm", "Bam", "Stats", "Test" and "VDP" in sequence. If all the above operations succeed, it indicates the data in the BAM server has been restored to the original version.

4) Restore original host programs, data and patches: Copy the directory D:\iMSC\Hostdata\ backed up during the preparation to overwrite the current directory.

5) Format new data file and load the host programs, data and patches: Execute the command FMT, then load the host programs and data. After the host starts normal operation, load patches to the host if available.

A.3 Host Upgrade Instruction

This section describes the host upgrade procedures and the cautions, as well as the system fallback procedures when exception occurs.

A.3.1 Preparations

The voice files of one or two SPT boards have been updated. BAM has been upgraded and connected to the system. The billing center has collected bills one hour prior to the upgrade operation. The power to all racks has been shut down. The DIP switches at the back of the frame whose frame No. will be modified have

been set to the new positions.

Caution:

In the SRM frame there are four DIP switches. They should be modified according to the individual frame No.


A-14

A.3.2 Upgrade Process

I. Host upgrade flow chart

Start

Adjust softw are parameters of activ e/standby AMP, CDP and BCP boards on maintenance

console

Pow er on CPM and CCMframes for loading

Pow er on CNET framefor loading

Pow er on LIM frame of GMHI for loading

Pow er on SRM frame for loading

Pow er on LIM frames of GE16 and GECP boards for loading

Pow er on SPM modulefor loading

Update voice files of SPT boards

Observe statuses of all boards from maintenance console and reset

abnormal ones for reloading until normal

Check whether voicefile updatingis completed

Upgrading completed

1

2

3

4

5 6

7

8

10

12

9

11

Dialing checkafter upgrade

Start

Adjust softw are parameters of activ e/standby AMP, CDP and BCP boards on maintenance

console

Pow er on CPM and CCMframes for loading

Pow er on CNET framefor loading

Pow er on LIM frame of GMHI for loading

Pow er on SRM frame for loading

Pow er on LIM frames of GE16 and GECP boards for loading

Pow er on SPM modulefor loading

Update voice files of SPT boards

Observe statuses of all boards from maintenance console and reset

abnormal ones for reloading until normal

Check whether voicefile updatingis completed

Upgrading completed

1

2

3

4

5 6

7

8

10

12

9

11

Dialing checkafter upgrade

Figure A-7 Host upgrade process


A-15

II. Host upgrade procedures

After board loading, please carefully check whether the board software is correct. The board software list is available in the attached Release Notes.

1) Load the boards in sequence. The specific procedures are avaialbe in Chapter 3 2) Conduct corresponding dialing checks after the upgrade. 3) If no abnormalities are found in the dialing checks, update the voice files of the

GSPT boards that haven’d been loaded (which may last about 80 minutes).

A.3.3 Fallback Process

If severe problems are found during the host upgrade process or during the check process, the system will have to fall back. The fallback process is as follows.

I. Preparation

The emergency workstation has taken the place of the BAM access system, and is in normal operation.

The voice files in this workstation have been restored to the original version. All cabinets of the host have been powered off.


A-16

II. Fallback flow chart

Start fallback

Adjust board parameter from maintenance cons ole

Power on CP M and CCM frames fo r loading

Power on CNET framefor loading

Power on LIM frameof GMHI fo r loading

Power on SRM f ramefor loading

Power on LIM frames ofGE16 and GE CP boards

for loading

Power on SPM modulefor loading

Fallback voice files of SPT board

Observer statuses of all boardsfrom UI of maintenance c onsole,reset abnormal ones fo r reloading

until normal

Check whether voice file updating is comple ted

Host fallback completed

1

2

3

4

5 6

7 8

910

11

Start fallback

Adjust board parameter from maintenance cons ole

Power on CP M and CCM frames fo r loading

Power on CNET framefor loading

Power on LIM frameof GMHI fo r loading

Power on SRM f ramefor loading

Power on LIM frames ofGE16 and GE CP boards

for loading

Power on SPM modulefor loading

Fallback voice files of SPT board

Observer statuses of all boardsfrom UI of maintenance c onsole,reset abnormal ones fo r reloading

until normal

Check whether voice file updating is comple ted

Host fallback completed

1

2

3

4

5 6

7 8

910

11

Figure A-8 Fallback flow chart

III. Fallback procedures

1) Modify the board software loading switch

Execute command MOD LSS to change all the board loading soft switches to "Program Unavailable, Data Unavailable, Program Writable and Data Writable".

2) Reload the host programs of the original version


A-17

Load the original host programs to the following frames in sequence: CPM, CCM, CNET, LIM (where GMHI board is located), SRM, LIM (where GE16 and GECP boards are located) and SPM.

3) Load original voice files 4) Conduct post-fallback dialing check

After the fallback of SPM frame, wait until the voice file fallback of one GSPT board succeeds, then conduct the post-fallback dialing check. If the result is normal, the fallback process is completed.

Installation Manual - System Commissioning M900/M1800 MSC/SSP/IP Appendix B Patch Operations

B-1

Appendix B Patch Operations

The M900/M1800 MSC/SSP/IP terminal system supports online patch operations via the maintenance console so as to fix and perfect the corresponding host programs without affecting the normal operation of the system service. This system also supports patch operations to the terminal system in the overwriting mode (including the BAM server and the Client).

Patch operations (without any specific methods and procedures) in terminal system are designed according to actual situations and they are seldom conducted on the terminal system. So their corresponding descriptions will not be covered in the manual. For details, please refer to the description related.

B.1 Patch Operations on Host System

B.1.1 Functions of Host Patches

The maintenance personnel can implement patch operations on the maintenance console of the M900/M1800 MSC/SSP/IP terminal system to fix or perfect the corresponding host programs without affecting the normal operation of the system service. In this way frequent upgrade of the host programs can be avoided.

Caution:

Online software patching is a critical operation, which may directly affect the running of the host programs. Thus, you should be careful when using the software patches.

B.1.2 Host Patch Features

The host patches are online patches which support the automatic overwriting mode. The new patches completely contain the old patches. The function of some patches can be controlled through software parameters.

The boards that can be patched online are: GSPC, NCC, AMP, CDP and GVDP. Each board has its own patch. The patch files can be presented in formats "cc08pat.xxx" and "cc08sym.xxx" ("xxx" stands for SPC, VDP or AMP, etc.)


B-2

Prior to patching operation, make sure to refer to the related patch notes attached with the patches. The notes contain the detailed information of all patches, including operation procedures, troubleshooting methods and cautions, etc. On the maintenance console, the user can execute commands corresponding to such operations as Load, Activate, Fallback, Run, Delete and Query, etc with reference to the operation procedures in the notes to add or delete software patches online.

Caution:

1. The design of basic version plus patch is adopted for the patch. That is, each patch corresponds to a specific basic version. 2. Patches of different host versions cannot be mixed.

B.1.3 Host Patch Status

On the foreground, there are four patch statuses: Idle, Deactivated, Active and Run.

1) Idle: The initial status, indicating this patch not exist in the memory. 2) Deactivated: Indicating that the patch has been loaded but not activated, and the

patch code has not been executed. 3) Active: Indicating the patch has been activated and the patch code is running. This

is a trial status. The user can execute the fallback command to fall back to the Deactivated status. The patches will be loaded automatically once the host is restarted after reset but cannot be restored to the Active status.

4) Run: Indicating that patches in the Active status have been written into the Flash and are running. Fallback can not be performed in this status. What can be done at this stage is to delete the patch. Furthermore, if the host resets, the patch will be loaded automatically and resume the Run status after the restart.

Figure B-1 shows the patch status conversion flow.

Figure B-1 Patch status conversion


B-3

Note:

1. Active status is a temporary status, when the patches are in trial running. If the system proves normal after a certain period of time, its status should be changed to the Run status. Since the Active status is a temporary status, patches in this status will not be restored after the restart. 2. Run status is the running status of the patch. Upon system restart only patches in the Run status are restored.

B.1.4 Host Patch Operation Commands

The patch operations include loading, activating, confirming, deleting of patches, querying patch status, and querying patch files, etc.

Load (LOD PATCH): Used to load patch files, namely load the realization code of the patches to the patch area of each board. The boards that supports online patch loading are GSPC, GCPC, NCC, AMP and CDP. Each board has its own patch.

Activate (ACT PATCH): Used to activate patches. If "N" is input in the field [Patch ID], all patches in the range from 0 to N will be activated.

The patch in the Idle status indicates that it has not been loaded yet and the host will return an error prompt. When activating a group of patches, if one patch cannot be activated, its ID will be returned. However, the patches numbered before this one have already been activated. The patch in the Active or Run status indicates that it has been activated. In this case, if to activate a group of patches, this patch will be skipped.

Deactivated (DEA PATCH): Used to deactivate patches. This operation is also called fallback. After a patch has been activated, if any error in its function is found, this command can be executed to deactivate this patch. If "N" is entered in the field [Patch ID], all patches in the Activate status after No.N will be deactivated.

Confirm (CFM PATCH): Used to write patches in the Active status into the Flash Memory. After this operation, the status of the patch will change from Active to Run. Patches in the Run status can be restored automatically when the system is powered off and restarted, while the patches in other statuses will be discarded.

Remove (RMV PATCH): Used to delete the patch of the specified module. After this patch is deleted, its status will change to Idle. If "N" is entered in the field [Patch ID], all patches after the patch No.N (including itself) will be deleted from the Flash Memory.

If the patch is in the Run status, it cannot be deactivated. If error in its function is found, the only method to rectify it is to delete this patch. Since this operation may seriously affect the system function, it should be confirmed by the system administrator first.


B-4

List (LST PATCH): Used to query the static information of the patch files (in the BAM database), including the number of patches, compatible patch versions and patch list.

Display (DSP PATCH): Used to query the status of a certain type of patches in the host of the specified module. When any non-query operation is performed to the patch, please check whether the status of the patch is consistent with the expected result with this operation.

B.1.5 Host Patch Operation Procedures

I. Obtain correct patch files

The online patch of the board is based on the software version, and there is strict corresponding relationship between them, thus it is required that they should be used together. Because patch files of different versions cannot be replace each other, correct patch files should be selected. To obtain the information of the applicable version of the patch, please read carefully the notes released with the patch.

Multiple software modifications may exist in a patch file. To adapt to the same version, the newly-released patch files are all new patches added on the basis of the original patch, if it is not otherwise specified. That is, the subsequent patch files not only solve new problems, but also old problems.

The storage directory of the patch file is the same as that of the corresponding host programs. The default directory on BAM is D:\iMSC\HOSTDATA\. If original patch file exists in this directory, back it up to another directory, then delete it from this directory, and copy the new patch file to this directory. After copying, execute the command LST PATCH to check the result, and then check the applicable version and other relevant information of the patch again.

Main board patch files are as follows:

SPM patch file: cc08pat.spc SPM symbol file: cc08sym.spc CDP patch file: cc08pat.cdp AMP patch file: cc08pat.amp NCC patch file: cc08pat.ncc VDP patch file: cc08pat.vdp


B-5

Caution:

1. The description file of the patch should be copied at the same time for the purpose of check when any error occurs. 2. It is recommended that the original patch files be saved as another name for the sake of restoration.

II. Load patches

Make sure that the backup switches of the modules have been turned on before loading the patch. Because the patches of the active/standby board must be consistent with each other, backup should be able to be performed over the board during setup and operation. Then execute command DSP PATCH to check whether any patch exists in the board. Both active and standby boards should be queried to check whether they are in consistent status. If not, load patches after the two boards resume the consistent status. After any non-query operation on the patch, please execute this command to check the status of the patch.

Because the newly-added patch contains the original patch, the command LOD PATCH can be executed to load patches no matter whether any patch exists in the board. During patch loading the board type and module No. should be specified. Without module No., the patches will be loaded to all boards of this type.

Validity of the patch needs to be verified during the loading. When the host version is inapplicable, please make sure whether the applicable versions of the patch files and that of the running host programs are consistent. If not, please change the patch files. It is possible that some of the patch not formally released exists in the board. At this time, please delete all the original files and reload the patch again. Once the loading is completed, check with the command DSP PATCH whether all the patches in the patch files have been loaded, and whether the status of active/standby boards is consistent. At this time, the newly-added patches should be in the Deactivated status.

When the loading command is executed, two cases may occur: 1) If the original patches with the same number are in the Idle status or in the Deactivated status in the system, they will be overwritten; 2) If the patches in the system are in the Active status or Run status, the newly-loaded patches will be discarded.

After the patch loading, the consistency of patches of the active/standby board should be checked. If the patches are inconsistent, please perform level-four restart over the standby board and load patches to it again, so that the active board and the standby board can enter the consistent status.


B-6

Note:

1. When loading is performed to all the modules simultaneously, loading failure may occur to certain modules. In this case, patches can be loaded to the modules individually on which the batch loading has failed. 2. After loading, the patches are in the Deactivated status and will not affect the system operation at all. 3. The command LST PATCH is used to check whether patch files and file information exist in BAM. The command DSP PATCH is used to check the patch information in the patch area of the board.

III. Activate patches

After being loaded, the patches should be activated to run and take effect. After confirming that the status of active/standby board is consistent, execute the command ACT PATCH to activate the patches. Upon the activation operation, the corresponding [Board Type], [Module No.] and [Patch ID] should be specified. The default value indicates that all patches of all modules will be selected. After the operation, the patch will be in the Active status and embedded into the original software, where it runs and takes effect. In this case, it is necessary to check whether the system is in normal operation. If exception is found, deactivate the patches with the command DEA PATCH, and then the patches will change to the Deactivated status. Or you may delete the patches with the command RMV PATCH. If switchover or reset operation is performed over the system, the patch in the Active status will fall back to the Deactivated status automatically.

Caution:

1. To ensure that the patch can run normally, please start subsequent patch operation after the system has been running steadily for 15 minutes. During this period, please observe the system status and the patch running status. 2. The actual patch operation may not be in the strict compliance with the above procedures. For example, in some case of patch loading, some patch of the former version must be deleted. In some other cases, the board should be reset after patch activation. Therefore the instruction for patch usage must be used as reference. 3. During patch activation, the maximum patch ID will take effect. 4. During patch fallback or deletion, the minimum patch ID will take effect. For example: If 6 Active patches exist in an SPM module, and "2" is selected as the [Patch ID] in the input command parameter, the patches with IDs ranging from 2 to 6 will be deleted while the patch whose ID is 1 remains. Thus, "All Patches" should be selected unless special requirement is given.


B-7

IV. Confirm patch

Once the patches are activated, observe whether the board status is normal. For this operation, please refer to the CPU load, board status, alarms, and so on. The purpose is to check whether the loaded patches will cause system exception. The observation should last about 15 minutes. After confirming the active/standby boards are in consistent status and the system operation is normal, execute the command CFM PATCH to confirm the running of the patches (the corresponding parameters should be the same as those for the command ACT PATCH.), so that the patches will enter the Run status.

Now, all operations on patches are completed.

Caution:

1. The functions of the patches in the Run status and the ones in the Active status are realized in the same way. But in the case of board reset or switchover, the patches in the Run status will restore to the Run status and remain running, while the patches in the Active status will change to the Deactivated status and will not run any more. 2. After confirmation, the only way to stop the running of the patches in the Run status is to delete the patches with the command RMV PATCH. 3. Once the version of host programs is changed, the original patch will not take effect any more.

V. Special cases

In the following cases, severe problems may occur:

1) The patch is deleted when the active/standby boards are in inconsistent statuses. 2) During patch loading in the case of module reset or switchover, the patch file in the

directory D:\iMSC\HOSTDATA\ has been deleted or become unavailable. At this time, the board will continuously try to restore the status of the patch, which may affect the normal operation of the system.

In the above case, try to obtain the patch version matching the host version and save it in the loading directory. At the same time, contact the Huawei local branch to handle the problem.


B-8

B.2 Cautions for Patch Operations

Please refer to the instructions for patch modification and the patch description during patch setup, and pay attention to the following items:

1) After the patch operation for each board, check against the patch notes whether the patch is complete and whether its status is normal.

2) Fallback is not allowed to the patches of BAM. Therefore the databases and the directory iMSC must be backed up prior to the patch operation. If the patch setup fails, first overwrite the original directory iMSC with the backup directory iMSC, then restore the database with the backup data.

3) The patches of GSPC standby board remain consistent with the host patches via the backup function. If the backup switch of the standby board is turned off, the patches of the standby board should be loaded through the host after data loading and should keep synchronized with the host, so that the standby board and the Host are in the same status. The standby board will send a request to the host for restoring the patch status, but the host can not achieve the synchronization of the active/standby patches through the backup function. The patches of the standby board will keep trying to restore the status, and the message "Restoring…" will be displayed. In this case, you can only execute the command STR SFTD to restore the GSPC board to the unpatched status. For example, STR SFTD: MN=1, PID="73", CTRL="1", PM0="1", PM1="1". Therefore, for all types of GSPC boards, the patches must be uninstalled before the data or programs are reloaded, and reinstall the patches after data or program loading is completed. If the programs of other AM boards are not changed, the patches may not be uninstalled. The patches must also be uninstalled before new programs are loaded.

Generally, the patches of the M900/M1800 MSC/SSP/IP system are mutually independent from each other. But some of the patches involve the entire system, such as the clock patch. Since the modification of the clock mode may affect BAM, AMP and SPM, the relevant patches should take effect simultaneously; otherwise the system time will be messed.

Installation Manual - System Commissioning M900/M1800 MSC/SSP/IP Appendix C Online Expansion

C-1

Appendix C Online Expansion

System expansion refers to the expansion of system capacity on the original basis, while online expansion refers to the capacity expansion on the original basis, without affecting the normal operation of the MSC.

The capacity expansion of M900/M1800 MSC/SSP/IP system involves that of AM/CM, SPM and SRM. This chapter only describes the expansion of LIM, SPM and SRM modules.

Caution:

The online expansion mode described in this chapter is a general operational method or principle. The actual on-site expansion should be based on the operation guide provided!

C.1 Expansion Modes and Configuration Instructions

C.1.1 LIM Module Expansion Principle

I. Select board

1) GE16

Usually, GE16 and GECP boards are configured simultaneously during expansion. The GE16 board only provides trunk ports. It cannot provide EC (echo cancellation) function. According to the cable type for GE16 boards, one GE16 board should be fixedly configured with one DRCA or DRCB board (DRCA is the 75✡ E1 interface connector board of the GE16 board, while DRCB is the 120✡ E1 interface connector board of the GE16 board).

2) GECP

Uasually, GE16 and GECP are configured simultaneously during expansion. GECP can provide the EC function but does not provide outgoing trunk ports. One GECP board can provide 256 EC channels for the outgoing E1 trunks of GE16 and GSTU boards.

3) GECS


C-2

GECS can provide both trunks and EC function. GECS can partially substitute the combination of GE16 and GECP. During expansion, the user can select GE16+ GECP or GECS or select the combination of the two as per the actual requirement. Since only 50% trunks require the EC function, if only GECS is adopted, the EC resources will be wasted. Therefore, each GE16 board should be configured with one DECA or DRCB board fixedly according to the types of cables connected with the GE16 board

4) GSTU

GSTU provides standard 155M STM-1 SDH interface or electrical interface. Different cables or optical cables should be selected according to actual interface type. Besides, TMC is the rear outlet board of GSTU. Each active/standby board is fixedly configured with one TMC.

II. Add LIM frame and LIM cabinet

1) When the slots in the LIM frame meet the expansion requirements

If sufficient slots are available in the original LIM frame for the configuration of GE16/GSTU/GECP/ GECS, and the capacity meets the expansion requirements, the main control rack of AM may not be changed. It will suffice to configure the corresponding GE16/GSTU/GECP/GECS boards in the original LIM frame. Optical fibers or cables should be added for different boards.

2) When LIM frames are to be added

If insufficient slots are available in the original LIM frame for the configuration of GE16/GSTU/GECP/ GECS, or the capacity cannot meet the expansion requirements, one LIM frame should be added. At this time if two pairs of unused optical interface still remains available on the pair of GSNU boards, two pairs of optical fibers can be led out directly from these interfaces to a new LIM frame. Then the corresponding GE16/GSTU/GECP/GECS can be configured in this new frame so that optical fibers or cables can be added. If no optical interface is available on GSNU, one pair of GSNUs should be configured. From this pair of GSNUs, two pairs of optical fibers can be led out to a new LIM frame. In this new frame, corresponding GE16/GSTU/GECP/EC16 boards can be configured, and optical fibers or cables can be added.

3) Add LIM cabinets

If the added LIM frame must be configured to a new interface rack, it may be necessary to add one pair of GSNUs, one pair of GFSNs (unnecessary if sufficient HDLC links are available to meet expansion requirements), one new interface rack and one set of cables integrated with interface rack. Two pairs of optical fibers can be led out from this pair of GSNUs to a new LIM frame. In this new frame, corresponding GE16/GSTU/GECP/EC16 boards can be configured and optical fibers or cables can be added.


C-3

C.1.2 SPM Expansion Principle

I. Select board

1) GSPC

Since trunk boards are added, it should be considered whether to add SPM modules. If the existing SPM module is capable of processing all the added trunk services, it is unnecessary to add SPM modules; otherwise corresponding active/standby GSPC boards, HW cables and network cables should be configured.

2) GCPC board

One GCPC board can support 4 SS7 links or PRA links. If it is necessary to add some links as required for expansion, corresponding GCPC boards and HW cables should be added. After GCPCs are added, it should be considered whether the GMHIs can support the GSPC boards. If the existing GMHIs are not capable enough, some GMHIs should be added to the LIM frame of the original GMHI.

II. Add SPM module

When adding SPM modules while the existing SPM frame can still support corresponding SPC and CPC boards, SPM frames may not be added. If no remaining space is available for SPM frames in the SPM cabinet, it is necessary to add SPM racks and a set of SPM cabinet cables (incluidng network cables, HWs, etc.).

C.1.3 SRM Expansion Principle

The full configuration of the system includes 2 SRM frames. After expansion, it is necessary to add GSPT/GSRC boards to meet the tone play and Dual Tone Receiving requirements. If only one SRM frame is available prior to the expansion while the current SRM frames are not sufficient, an extra SRM frame should be added. After adding GSPT/GSRC, please check the capability of the existing GMHIs. Add GMHIs if necessary to the LIM frame of the original GMHI).

C.2 LIM Module Expansion Process

C.2.1 Add GE16 and GECS Board

1) Hardware condition: Boards have been placed and trunks have been connected. 2) Execute the command ADD BRD to add boards which have been placed. 3) Execute the command ADD SPME1 to add the E1 resources of the new board to

the SPM module. If this operation is successful, please execute the command DSP E1CH to check whether all the E1 ports are normal.

4) Start board loading


C-4

5) After loading, execute the command DSP BVER to check the board version and execute the command DSP BRD to check the board status.

6) Add trunk data and signaling data as required. 7) Check the status of the newly added trunk circuits. Their status should be Idle. 8) Conduct specified trunk circuit dialing check to ensure the newly added circuits are

available. For detailed operation procedures, please refer to 6 Specified Trunk Test.

C.2.2 Add LIM Frame

Add a LIM frame for outgoing trunks.

1) Hardware conditions: Frames and boards have been placed. All internal cables including power cables, emergency serial port cables, optical fibers, CCM-HWs and clock cables have been connected. The Frame No. settings are correct. After the hardware are ready, power on and load data in the online mode.

2) Execute the command ADD IFAM to add LIM frames, and then execute the command RMV BRD to delete unavailable boards, and execute the command ADD BRD to add physically existing boards.

3) Execute the command ADD CCMHW to configure HWs in the CCM planes. 4) Execute the command ADD SPME1 to add the new E1 resources to the SPM

module. 5) Start board loading. 6) After loading, execute the command DSP BVER to check board version. Execute

the command DSP BRD to check board status. 7) Execute the command DSP HDLC to check whether CCMHW links are normal. 8) Execute the command DSP E1CH to check the E1 port status. 9) Add trunk data and signaling data as required. 10) Check the status of the newly added trunk circuits. Their status should be Idle. 11) Conduct specified trunk circuit dialing check to ensure the newly added circuits are


C.3 SPM Module Expansion Process

C.3.1 Add GCPC Board

1) Hardware conditions: GCPC boards have been placed and the HWs from GMHI to GCPC are also connected.

2) Execute the command ADD BRD to add boards which have been placed. 3) Execute the command ADD CPCCFG to configure GCPC board resources. 4) Start board loading.


C-5

5) After loading, execute the command DSP BVER to check board version. Execute the command DSP BRD to check board status.

6) Add trunk data and signaling data as required. 7) Check whether the newly added links are normal.

C.3.2 Add GVDP Board

1) Hardware conditions: The GVDP boards have been placed and the HWs from GMHI to GVDP have been connected.

2) Execute the command ADD BRD to add boards which have been placed. 3) Execute the command ADD CCMHW to configure HWs in the CCM planes. 4) Start board loading. 5) After loading, execute the command DSP BVER to check board version. Execute

the command DSP BRD to check board status. 6) Execute the command DSP HDLC to check whether CCMHW links are normal.

C.3.3 Add SPM Frame

Add an SPM frame. This new frame can accommodate such boards as GSPC, GVDP, GCPC and BCC, etc.

1) Hardware conditions: The boards have been placed, and the internal cables have been connected including power cable, emergency serial port cable, optical fibers, CCM-HW, MHI-HW and clock cables, etc. The network cables of SPC have been connected and the Frame No. is correct. Then power on the frame and load data in the online mode.

2) Execute the command ADD SPMFRM to add SPM frame, then the command RMV BRD to delete unavailable boards and the command ADD BRD to add physically existing board.

3) Execute the command ADD SPM to add SPM module. 4) Execute the command ADD CCMHW to configure HWs in the CCM planes. 5) Execute the command ADD SPME1 to add the new E1 resources to the SPM

module. 6) Execute the command ADD CPCCFG to configure GCPC board resources. 7) Start board loading. 8) After loading, execute the command DSP BVER to check board version. Execute

the command DSP BRD to check board status. 9) Execute the command DSP HDLC to check whether CCMHW links are normal. 10) Execute the command DSP E1CH to check the E1 port status. 11) Add trunk data and signaling data as required. 12) Check whether the signaling links and trunk circuits are correct. 13) Conduct specified trunk circuit dialing check to ensure the newly added circuits are



C-6

C.4 SRM Module Expansion Process

C.4.1 Add GSRC Board

1) Hardware conditions: The GSRC boards have been placed and the HWs from GMHI to GSRC have been connected

2) Execute the command ADD BRD to add boards which have been placed. 3) Execute the command ADD SRCCFG to configure DSP units and HW resources

for GSRC. 4) Start board loading. 5) After loading, execute the command DSP BVER to check board version. Execute

the command DSP BRD to check board status. 6) Execute the command DSP RESCHN to check the channel status of GSRC

boards. The normal status should be Idle.

C.4.2 Add GSPT Board

1) The GSPT boards have been placed and the HWs from GMHI to GSPT have been connected.

2) Execute the command ADD BRD to add boards which have been placed. 3) Execute the command ADD SPDCFG to confgure the HW resources and the

asynchronous signal tone attributes of GSPT. 4) Start board loading. 5) After loading, execute the command DSP BVER to check board version. Execute

the command DSP BRD to check board status. 6) To update the GSPT voice files, please refer to steps 11~16 in section 3.3.5. 7) Conduct specified timeslot signal tone dialing check. For detailed operation

procedures, please refer to 6 Specified Trunk Test.

Installation Manual - System Commissioning M900/M1800 MSC/SSP/IP Appendix D Abbreviations and Acronyms

D-1

Appendix D Abbreviations and Acronyms

A

AM Administration Module

AMP Main Processing Board

AOC Advice of Charge

AoCC Advice of Charge (Charging)

AoCI Advice of Charge (Information)

B

BAIC Barring of All Incoming Calls

BAM Back Administration Module

BAOC Barring of All Outgoing Calls

BCC Bus Communication Control Board

BIC-Roam Barring of Incoming Calls When Roaming Outside Home PLMN Country

BIOS Basic Input/Output System

BOIC Barring of Outgoing International Calls

BOIC-exHC Barring of Outgoing International Calls except those directed to the Home PLMN Country

C

CDP Central Database Processing Board

CFB Call Forwarding Busy

CFNRc Call Forwarding on mobile subscriber Not Reachable

CFNRy Call Forwarding on No Reply

CFU Call Forwarding Unconditional

CIC Circuit Identification Code

CKM ClocK Module

CLIP Calling Line Identification Presentation

CLIR Calling Line Identification Restriction

CM Call Management

CNET Central NETwork transfer and switch

COLP Connected Line Identification Presentation

COLR Connected Line Identification Restriction

CPM Central Processing Module


D-2

CPU Central Processing Unit

CRC Cyclic Redundancy Check

CUG Closed User Group

CW Call Waiting

D

DIP Dual-In-line Package

DRAM Dynamic Random Access Memory

E

EC Echo Cancellation

F

FTP File Transfer Protocol

G

GBAC Bus Administration Configuration Board

GBDP

GCDI Circuit Data Interface Board

GCPC Central Processing Board

GE16 16-port Interface Board

GECP Echo Cancellation Pool Board

GECS 16-port Echo Canceller Trunk Board

GETS 16*E1/T1 Interface Board

GFSN Frame Switching Network Board

GHN7 HIGH-SPEED NO.7 LINK PROCESS

GMHI Muti-HW Interface Board

GMSC Gateway Mobile Switching Center

GNET

GQSI High-Speed Signal Interface Board

GSNU Skirt Network Unit

GSPC Service Processing Board

GSPT Special Voice Board

GSRC Shared Resource Card

GSTU SDH Interface Unit

GVDP Visitor Location Register Data Processor

H

HDLC High-level Data Link Control


D-3

HW Highway

I

IAI Initial Address Message with Information

iGWB iGateway Bill

IMSI International Mobile Station Identity

IN Intelligent Network

IP Intelligent Peripherals; Internet Protocol

ISUP Integrated Services Digital Network User Part/ISDN User Part

IWF InterWorking Function

L

LAN Local Area Network

LIM Line Interface Module

M

MAP Mobile Application Part

MML Man Machine Language

MO Mobile Origination

MPTY Multiparty Service

MS Mobile Station

MSC Mobile Switching Center

MSISDN Mobile Station International ISDN Number

MT Mobile Termination

N

NCC Network Communication Control Board

O

ODB Operator Determined Barring

OMC Operation & Maintenance Center

P

PCB Printed Circuit Board

PDF Power Distribution Frame

PPS Pre-Paid Service

PRA Primary Rate Access

PSTN Public Switched Telephone Network

S

SDH Synchronous Digital Hierarchy


D-4

SLS Signaling Link Selection Code

SPM Service Processing Module

SQL Structured Query Language

SRC Shared Resource Board

SRM Shared Resources Module

SS7 CCITT Signaling System No.7

SSP Service Switching Point

STM-1 SDH Transport Module -1

T

TCP Transfer Control Protocol

TMC STU Conversion Card

TUP Telephone User Part

U

USSD Unstructured Supplementary Service Data

V

VLR Visitor Location Register

VMSC Visited Mobile Switching Center , Visited MSC

W

WS Workstation

Documents

Installation Manual-System Commissioning