Trouble Shooting
www.huawei.com
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Objectives

Upon completion of this course, you will be able to:

Understand the normal flow and methods to deal with trouble

Master how to orientate Hardware system’s and User system’s
trouble

Master the universal trouble shooting methods
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page1
Contents
1. Normal Flow & Method
2. User System & Hardware System’s Trouble
3. The Common Trouble Shooting Orientation Method
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page2
Basic Requirement For Operator

Familiar with system and network

Master the instrument and meter equipment

Familiar with operation

Professional technique and skill
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page3
Normal Flow

Collecting message


Judging trouble


Make sure the range and category
Finding out the trouble point


Obtain the original information as soon as possible
Find out the reason of the trouble
Eliminating the trouble

Eliminate the trouble and repair system according to the suitable
processing
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page4
Normal method

Analyzing original information

Alarm messages

Indicating light status

Dialing test

Instrument and meter equipment

Traffic statistics
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page5
Normal method

Dynamic & Signaling tracing

Test / Loop

Contrast / Interchange

Switchover / Reset

Contact with Huawei Support Technology
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page6
Normal method

Analyzing original information

Example 1:

U (User): My phone has some problem, please help me to check it.

E (Engineer): When did you face this problem? Calling out or calling in.

U: Oh, calling in. I could hear ring-back tone when I used mobile to call my phone set.
But the phone didn’t ringing. What’s the problem?

E: Ok, Did you try to pick up the phone when you make a call? Could you hear
anything?

U: Yes, I tried it before. I just heard “Du…Du…”, and couldn’t talk with each other.

E: You may have “Call forwarding unconditional” service. Could you dial #57# to
cancel it ?

Solve the problem
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page7
Normal method

Alarm messages

Example 2:We can observe the alarm messages by Alarm Box
and Alarm Station.
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page8
Normal method

Indicating light status

Example 3:DTF card alarm indicating lights

If “LOS1” turn on, it means the first E1 Loss of Signal. It
RUN
CAS
may be disconnect or one-way audio.
LLB1
RLB1

If “SLP2” turn on, it means the second E1 slip frame. It may
RRA1
RMA1
SLP1
be low clock synchronization performance or high
transmission attenuation.
LOS1
RCL1
DSP
LLB2

RLB2
Suggestion:
RRA2
RMA2
SLP2

Operator should pay attention to accumulate indicator’s
LOS2
RCL2
status. It will help to improve the ability of fleetly solving
problem.
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page9
DTF
Normal method

Dialing test

Example 4: It is a new SS7 trunk group between Office A and opposite
office. The trunk circuits and links status are normal. But they can’t
use new trunk to make inter-office call.



Using a local office user to dial the opposite office number and tracing this
user, observing the result is “No route available”. And don’t send “IAM” to
opposite office.
Orientating: The route selection data has some problem and the system
can’t choose suitable circuit.
Hint:

Dialing test is used popular. It’s usually used with dynamic tracing.
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page10
Normal method

Instrument and meter equipment

Example 5: Most user’s CLIP service are abnormal in a certain frame.

To judge the influence for CLIP of PWX card. Using oscillograph to
analyzing output ringing current wave shape. It’s contain many “harmonic
voltage”. First judging burr interference “FSK” sending and make CLIP
abnormal.

Suggestion:

If condition permission, can choose instrument and meter equipment for
trouble analysis. The key point is the correct using for instrument.
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page11
Normal method

Traffic statistics

Example 6: The office A create TG Incoming Office statistics. It
contains “Lost Calls Of Int Congest Times” 10 times in 500 call
attempts an hour.

It has several reasons for “Lost Calls Of Int Congest Times ” . Creating the
Fail reason traffic in total office traffic task, The “No Ipath times” and “No
Available Circuit Times” amounts are the same.

Which module is congesting? To tracing SS7 link and observing the SEC
message, the operator finds the problem in X module.

Check the iDT trunk circuit between X module and Central module, they
find that some PCM system are self-looped.
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page12
Normal method

Dynamic & Signaling tracing

Example 7: Office A connect to Tandem X. There are some CGC
message between them. It has the influence for call completion rate.

The link and circuits status are normal. Data setting is correct.

The result of link tracing as below:
Tandem
Local

IAI
IAI
IAI….
CLF
IAI… (total:22 IAI) CGC
CLF……
RLG
CGC
RLG……
There are 22 IAI messages which contents are the same. The reason is
Local office A and Tandem setting the same prefix and make cyclic
between each other.
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page13
Normal method

Test / Loop

Example 8: Local office A connects to office B. It appears many E1
slip alarms that has serious influence between them. The Network
structure of office B as bellow:

We can choose point ①、②、③、④ for loop testing. According to
compare with the result, we can orientate the fault which is belong to
switch system of transmission system.

This method is used widely for transmission fault.
OFFICE
A
C&C08
Transmission
DDF
1
Transmission
2
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
OFFICE
B
DDF
3
4
Page14
Normal method

Contrast / Interchange

Example 9: When make the test for rise digits in office X, some incoming call
are rejected by system. The system send SST and the data setting is correct.
The network structure as below:



According to dialing test: C can connect to B, but can’t connect to A. A & B call
forwarding unconditional to D.
Compare with SS7 signaling, the “Redirected call indicator ” in IAI is 1 when C call A,
since C call B is 0.
Change soft parameter. The system no need judge “Redirected call indicator ”, and
solve this problem.
CC08
OFFICE X
USER A
USER B
TUP
Tandem
USER C
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
USER D
Page15
Questions

How many kinds of method we have learned for trouble
shooting?

Which kind of method did you use before?
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page16
Contents
1. Normal Flow & Method
2. User System & Hardware System’s Trouble
3. The Common Trouble Shooting Orientation Method
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page17
Category of Hardware System Trouble

Central Module
CNET
LANSWITCH
BAM
TCP/IP
TCP/IP
393M
C B N
N D C
U R C
…
S S S
N N N
U U U
…
393M
393M
CCM
CPM
A C B
M D C
P P P
…
HDLC
The Fault of Card
And internal connection
The fault of TCP/IP
connection
The fault of CCMHW
connection
F B F
S A S
N C N
SPM
S B C
P C P
C C C
HDLC
HDLC
HDLC
…
E
Q O T S
S B 1 T
I C 6 U
…
40.96M
SM
LIM
E
Q O T S
S B 1 T
I C 6 U
…
E1
OPPOSITE
OFFICE
HDLC
LIM-MHI
HDLC
…
MHIHW-2M
…
MHIHW-8M
SRM
S S
P R
D C
LIM
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Q M M
S H H
I I I
The fault of MHIHW
connection
…
The fault of OFL
connection
Page18
Category of Hardware System Trouble

Central Module

The fault of Card

The fault of Internal connection

The fault of TCP/IP connection

The fault of CCMHW connection

The fault of MHIHW connection

The fault of OFL connection

The fault of Clock Line connection

The fault of DIP switch

The different version of hardware and software
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page19
Category of Hardware System Trouble

Switching Module

The fault of card

The fault of internal connection (NOD, HW)

The fault of OFL connection between Central Module

The fault of switches setting
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page20
Typical trouble case

Example 1:

Phenomenon Description: The 4# LIM can’t load in 128M.

Cause Analysis:

First to check the DIP switch (00000100), since the Frame ID must
keep the same as DIP switch.

Handling Process:

The 4# LIM DIP switch setting is incorrect when the operator check
it in the office. The 4# LIM begin to load after change DIP switch.
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page21
Typical trouble case

Example 2:

Phenomenon Description: The SPM version can’t report after loading.

Cause Analysis:

The data and program are loaded in SPC by TCP/IP. The SPC
communicate with other cards though CCMHW. If CCMHW setting is
incorrect, the SPC can’t communicate with other card and can’t report the
version.

Handling Process:

The SPC and BCC CCMHW should be 16,17,18, but the data setting are
17,18,16. The SPM version can report after changing data setting.
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page22
Common reason and handling
procedure in User System Trouble

Typical case analysis and discussing

The common trouble phenomenon in User System

The common reason for User system trouble
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page23
Typical trouble case analysis

Example 1: no feedback

Phenomenon Description: The user can’t hear dial tone after
hook off. And the “work indicator” on telephone turn off.
Indicator
Turn off
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page24
Typical trouble case analysis


Cause Analysis:

The external user line is short circuit or break.

The port which provided by ASL card is fault.

The external user line or analogue circuit is broken.

swinging cross.

The user’s phone set is broken
What’s
the
reason?
Suggestion and summary: The most trouble occur in external
user line or ASL card fault. It is necessary to test external user
line and ASL card regularly for preventing trouble.
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page25
Typical trouble case analysis

Example 2: CLIP service is abnormal

Phenomenon Description:

The phone set which apply the CLIP service can’t display the caller
number as called。

The caller number display is fault. For example : the number
uncompleted, loss number or number error.
Why caller number
disappeared?
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page26
Typical trouble case analysis

Case analysis:

“can’t display the caller number” analysis:
– Check the FSK signal starting or not
– Check ASL card port is fault or not
– Check user’s phone set is fault or not
– Check user’s supplementary contains CLIP or not
– Check BNET(SM) or SRC(SPM) is fault or not
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page27
Typical trouble case analysis

Case analysis:

“the caller number error” analysis:
– Check external user line
– Check ASL card port is fault or not
– Check BNET(SM) or SRC(SPM) is fault or not
– Check clock signal is normal or not
– Contact with “Huawei Technology Support”
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page28
Typical trouble case discussing

Example for discussing 1: Ringing abnormal

Phenomenon Description :

No ringing. When make a call, caller can hear ring back tone, but called
don’t ringing. They can make conversation if called hook off.

Self-ringing. The phone will ringing itself even there isn’t incoming call.
When the called pick up, find is no incoming call here. The ringing mode
could be normal, long and so on.

Can’t cut off the ringing. Caller hear ring back tone, called ringing then
called off-hook. The called keep ringing and they can’t make conversation.

What’s the possible reason?
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page29
No Ringing Analysis
No.
1
2
Reason
Remark
PWX is fault. No ringing
There are no ringing current in User Frame.
current.
It’s usually whole frame user no ringing.
The supplementary service The called set “CFU” and doesn't cancel in
is used unsuitable.
time. It brings on all of the call transfer to
other user.
3
The circuit for ringing is
The corresponding user can’t ringing.
fault.
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page30
Self-ringing Analysis
No.
1
Reason
Remark
The user ling in ASL is fault. Ring
The user will be self-ringing or
relay start-up unconventionally or
ringing for long time.
can’t release after startup.
2
3
The power supply is unstable. It
It makes ASL ring relay start-up error
contains harmonic wave.
and the user self-ringing.
The software running procedure
It makes ASL ring relay start-up
is abnormal.
abnormal and the user self-ringing.
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page31
Can’t cut off the ringing Analysis

Reason: The loop resistance is larger than switching system
monitor range.

Criterion:

The loop resistance in free status ≤1800Ω; The loop resistance in off-hook
status≤300Ω. If switching system can’t detect the off-hook, the called party
will be considered free and the system will send ringing current continually.

Summary:

This kind of trouble occurs in village almost. It can solved by change
external user line or augment external user line’s core area. And can
use the better remote feeding ASL card to solve this problem also.
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page32
Typical trouble case discussing

Example for discussing 2: The half of frame or whole frame
users are fault


Phenomenon Description :

The phone set is no feedback, and can’t call in

No dial tone

Noise is great in conversation
What’s the possible reason?
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page33
The possible reason-1
No. Reason
1
The mother board
Remark
If fuse F1,F2 are burned, it will no feedback in whole frame.
fuse is burned
2
The mother board
Can’t call in and the noise is heavy in conversation.
is fault
3
DRV card is fault
The DRV can used for receive DTMF, transfer user line
signal and drive HW signal. It usually used for a pair. If one
is broken and another card can’t start-up help function, the
half or whole frame’s users will can’t hear dial tone, can’t
call in or can’t work normal.
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page34
The possible reason-2
No. Reason
4
NOD card is fault
Remark
NOD likes communication bridge between MPU and other
cards. If NOD is broken, the whole frame user can’t hear dial
tone and can’t call in. If half of NOD is broken, the call loss
will be higher in user frame.
5
HW connection
There are 2 HWs in each user frame. If one of them is
broken, since help function can’t start-up, It occurs no dial
tone, heavy noise and one-way audio in half of frame. It will
affect whole frame if serious.
6
NOD connection
If NOD line disconnect, it will bring on calling loss,
increasing no dial tone times and so on.
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page35
The summary of user system
phenomenon-1
Range
Single user
Category
Phenomenon
No feedback
No dial tone
Ringing abnormal
No ringing, self-ringing, can’t cut off ringing
Call in abnormal
Can’t call in, can’t conversation, just ring one time
Call out abnormal
No dial tone, can’t cut off dial tone, hear busy tone when
pick up the phone
Connect abnormal
Intra-module, Inter-module, Inter-office connect abnormal
Conversation
Noise is loud, the voice is small or loud, cross-talking
abnormal
Different
range user
CLIP abnormal
No display, display error, display incomplete
Half frame of whole
No feedback, can’t call in, no dial tone, heavy noise,
frame
CLIP service abnormal and so on.
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page36
The summary of user system
phenomenon-2
Range Category
Different
Whole office congestion
range
Phenomenon
All of the trunks disconnect, the system can’t process
any incoming and outgoing call. Or all of the modules
can’t call each other.
user
Inter-module congestion
The user in SM, RSM, SPM can’t make conversation
between other modules.
Intra-module congestion
The user in SM, RSM, SPM can’t make conversation in
the same module.
Intra-module connection
one-way audio, can’t make conversation, disconnect
abnormal
when make conversation.
Inter-module or inter-
Connection cost long time, one-way audio, can’t make
office connection
conversation, disconnect when make conversation.
abnormal
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page37
The summary of user system trouble
reason-1
Category Reason
External
disconnect/shor
user line
t circuit
Remark
No feedback, no ringing, can’t call in, no dial tone
Grounding
Loud noise, dial wrong number, ringing abnormal
Swinging cross
No feedback, no ringing, self-ringing, no dial tone, can’t cut off dial
tone, display caller number error, the voice is small
Hardware
ASL card fault
No feedback, ringing abnormal, noise in conversation, the voice is
small, display caller number abnormal
DRV card fault
No dial tone, can’t cut off dial tone, hear busy tone when pick up the
phone, usually affect a half of frame
PWX card fault
No ringing, loud noise, display caller number abnormal, usually affect
a half of frame
NOD card fault
No dial tone, can’t call in, usually affect a half of frame or whole frame
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page38
The summary of user system trouble
reason-2
Category Reason
Hardware
Remark
SIG card fault
No dial tone, usually affect one module
BNET card fault
Intra-module connection abnormal, If clock phase abnormal, it
will appear noise in conversation, disconnect when surf in
network, display caller number abnormal
HW line fault
No dial tone, no ring back tone, one-way audio
NOD line fault
No dial tone, can’t call in, usually affect a half of frame
Clock line fault
noise in conversation, disconnect when surf in network or in
conversation, usually affect a half or whole frame
Other
reasons
Didn’t define user data
No dial tone, can’t call in
Phone set fault
No feedback, dial wrong number, ringing abnormal, noise in
conversation, the voice is small, one-way audio
CIC no matching
Outgoing call one-way audio,
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page39
Summary

What did we learn in this chapter?

We have described hardware system and user system trouble
shooting in detail.

We have learned the trouble phenomenon, cause analysis and
handling process in hardware system and user system.
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page40
Contents
1. Normal Flow & Method
2. User System & Hardware System’s Trouble
3. The Common Trouble Shooting Orientation Method
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page41
The Common Trouble Shooting Method

The category of common trouble

Trunk/Link system common trouble

Charging/Bill management common trouble
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page42
Trunk/Link system

Trunk/Link system data setting
ADD CALLSRC
Pay attention:
OPC
DPC
CIC
SLC
TKC selection mode…
SET OFI (ADD OFI)
ADD N7DSP
ADD OFC
ADD N7LKS
ADD N7RT
ADD CPCCFG
ADD SRT
ADD SPME1
ADD RT
ADD N7TG
ADD RTANA
ADD SPMN7TKC
ADD SPMN7LNK
ADD CNACLD
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page43
Typical trouble case discussing

Case 1: No.7 link status abnormal

Trouble phenomenon:

Disconnect. Viz. the link can’t locate.

The link is unsteady. Namely the link always Initial alignment and
can’t transfer MSU.


The link interdiction, viz. remote processor outage.

The link is congestion. Namely the link works overload.
What’s possible reason?
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page44
Typical trouble case discussing

The possible reason:

Transmission fault

STP fault

ET16/STU/DTF card is fault

Remote processor outage

Data setting incorrect (DPC/SLC/Link selection code)
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page45
Typical trouble case discussing

Case 2: SS7 Trunk circuit status abnormal
Circuit status
Remark
Fault
If trunk circuits are not blocked when DPC unreachable or
PCM system fault, the trunk circuit status is fault.
Available blocked
That indicates blocked opposite circuits already. It can make
outgoing call but can’t accept incoming call in these status.
Unavailable blocked
That indicates blocked local circuits already. It can accept
incoming call but can’t make outgoing call in these status.
Unknown
When office sends RSC/GRS message for this circuit and
doesn’t receive RLC, it will change to this status.
Uninstall

That indicates didn’t configure trunk data yet.
What’s possible reason?
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page46
Typical trouble case discussing

The possible reason-1:
No.
1
Reason
Remark
Transmission
Circuit status “fault”
disconnect/error code
2
ET16, STU, DTF card
fault
3
Data configuration
If didn’t configure trunk data, the circuit status is
incorrect or didn’t do it
“uninstall”. If didn’t configure DPC or make
mistake, the status is “fault”.
4
CPU overload and start-
“Available block”
up congestion control
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page47
Typical trouble case discussing

The possible reason-2:
No. Reason
Remark
5
BLOCK
6
CIC no matching
“Unknown”
7
Link fault
If DPC unreachable, the circuit status is “fault”. If
link congests or has high error rate, the circuit
status is “unknown”.
8
Local side hardware fault
“Unavailable block”
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page48
Typical trouble case discussing

Case 3: The SS7 signal cooperation abnormal

Trouble phenomenon:

The SS7 signal cooperation abnormal usually means inter-office
connection abnormal. Like can’t make conversation.

The caller number send abnormal. The incoming office can’t obtain
caller number or can’t obtain the real caller number.

What’s possible reason?
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page49
Typical trouble case discussing

The possible reason-1:

CIC no matching

The corresponding data for caller number is incorrect

Like “can request caller number”, “request caller number”,
“connect without or with invalid caller number”, “default number”,
“CLI provision mode”.

The call barring data is incorrect

The barring group number, the caller discrimination number and
so on.
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page50
Typical trouble case discussing

The possible reason-2:

The supplementary signaling setting unsuitable

Like “send caller number”, “translate caller number”, “send
original called” setting unsuitable, then can’t carry out some
supplementary, such as CLIP, CLIR, call forward and so on.

The soft parameter setting unsuitable
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page51
Real case analysis

Example 1: When user in Fix Network Office A call mobile
user, the caller number can’t carry area code.

The trouble phenomenon:

The network structure is as below. When user who is in Fix
Network call mobile user, the caller number need carry area
code in gateway office. All of users are carry area code normal,
except in office A.
A,C
Office A
Mobile Office
A,C
USER A
Office B
B,C
USER C
0755B,C
Gateway Office
USER B
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page52
Real case analysis

Handling Process:

Using signaling tracing in gateway office, compare with A->C IAI and B-
>C IAI message. The “Nature of address indicator” is “00”(Local
number) in B->C IAI message. And the “Nature of address indicator” is
“10”(National significant number) in A->C IAI message.

Let office A change parameter “Nature of address indicator” to “00”, the
caller number turn to normal.

Cause analysis:

The parameter “Nature of address indicator” in signal which is sent by
office A is incorrect. Although the caller number doesn’t carry area
code, the “Nature of address indicator” is “10”(National significant
number). The gateway office considers the toll call and no need append
area code.
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page53
Charging/Bill management system

Charging/Bill management system
ADD/MOD ST
Caller
ADD CHGIDX
ADD/MOD CNACLD
Called
ADD CHGANA
MOD CHGMODE
Charging
analysis
Charging
operation
STR BILIF
MPU/SPC
DETAIL
BAM
METER
RST BILPOL
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page54
Real case analysis

Example 1:

Phenomenon:

When use ISP mode to carry out “simultaneous ringing”, the user B
registers “simultaneous ringing” to user C. If the user A who comes
from opposite office call user B through incoming TG, system charge
incoming TG. B and C ring at same time. If B picks up the phone,
system generate one incoming TG ticket for A-B. If C picks up the
phone to make conversation, there isn’t incoming TG ticket in system. It
must generate incoming TG ticket for A-B, ether B picks up or C picks
C&C08
up.
Office A
A,B
A,C
A,B
Office C
USER C
USER B
USER A
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page55
Real case analysis

Example 1:

Cause analysis:

It must generate incoming TG ticket for A-B, ether B picks up
or C picks up in ISP mode for “simultaneous ringing”.

Pay attention: If C pick up the phone, according to incoming TG
charging source code and the charging selection code in prefix
for virtual PBX indicating number, system analyze charging
case. It may be that the charging data for prefix of virtual PBX
indicating number is incorrect.
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page56
Real case analysis

Example 1:

Handling Process:

When check charging data, the data setting is no charging for
corresponding incoming TG charging source code and charging
selection code of virtual PBX prefix. After change the charging
case to detail ticket, the charging is normal. When A dial B, the
B and C ring at same time. The system generates incoming TG
ticket successful for A-B, ether B picks up or C picks up.
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page57
Real case analysis

Example 2:

Phenomenon:

The BAM couldn't fetch bill tickets from the exchange since
some day. There were no new *.bil generated since that
moment, and the total amount of bill tickets in the SPM (there
was only one SPM module in this office, no SM) was more than
20,000.
MPU/SPC
STR BILIF
DETAIL
METER
BAM
Creating
file in
D:/bill/bill
is fault
RST BILPOL
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page58
Real case analysis

Example 2:

Cause Analysis:

After checking the billprint.txt, operator found the reason as
follows. >2005-11-29 10:45:53 Failed to open or create ticket
file (filename d:\bill\bill\2005112814.BIL) So the problem was on
the BAM. The following needs to be checked.

1. Disk space on the BAM

2. Disk quality

3. If the attribute of folder bill has been set as read only mode
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page59
Real case analysis

Example 2:

Handling Process:

After contacting the on-site engineer, he said that the customer
did something yesterday afternoon. Finally he found that the
folder Bill was set as read-only mode. The problem was solved
after changing folder Bill to writable mode.
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page60
Summary

In these course, we have learned:

Normal flow and method for trouble shooting

The hardware and user system trouble phenomenon, cause
analysis and handling process.

Some common trouble shooting orientation method
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page61
Thank you
www.huawei.com