Alarm: 7743

Troubleshooting Guide
Table of contents:

Title 1

Table of Contents 2

1 Alarm Text…………………………………………………………. 3

2 Meaning………………………………………………………......... 3

3 Supplementary Information Fields………………………………. 3

4 General Explanation……………………………………………... 4

5 Some Real Time Causes for this Alarm…………………………….. 4

6 Points to remember while checking 7743…………………………. 4

7 How to find root cause for this Alarm………………………………. 5

8 Affecting KPI's…………………………………………………………... 5
 1. Alarm Text
MEAN HOLDING TIME BELOW DEFINED THRESHOLD

2. Meaning

Mean holding time on a channel is below the operator-defined minimum during the
measurement period. The alarm is used to supervise the functioning of traffic channels
and to detect the possible faulty channels.

3. Supplementary Information Fields

1 Indicates if the mean holding time is below the defined threshold in

Timeslot 0
00: above threshold (no alarm)
01: below threshold (alarm)

2 Indicates if the mean holding time is below the defined threshold in

Timeslot 1
00: above threshold (no alarm)
01: below threshold (alarm)

3 Indicates if the mean holding time is below the defined threshold in

Timeslot 2
00: above threshold (no alarm)
01: below threshold (alarm)

4 Indicates if the mean holding time is below the defined threshold in

Timeslot 3
00: above threshold (no alarm)
01: below threshold (alarm)

5 Indicates if the mean holding time is below the defined threshold in

Timeslot 4
00: above threshold (no alarm)
01: below threshold (alarm)

6 Indicates if the mean holding time is below the defined threshold in

Timeslot 5
00: above threshold (no alarm)
01: below threshold (alarm)

7 Indicates if the mean holding time is below the defined threshold in

Timeslot 6

© Nokia Siemens Networks NSN Internal Document

 00: above threshold (no alarm)
01: below threshold (alarm)

8 Indicates if the mean holding time is below the defined threshold in

Timeslot 7
00: above threshold (no alarm)
01: below threshold (alarm)

9 Identifies the Timeslot where the mean holding time is shortest

10 Identifies the sub channel in the Timeslot with the shortest mean holding
time
00: TCH/H sub channel 0 01:
TCH/H sub channel 1
02: TCH/F sub channel

11 Shortest mean holding time in seconds during the measurement period

(TCH)

4. General Explanation

This alarm explains that calls are not holding on a particular Timeslot for the minimum
holding time as defined by the operator specific parameter. This does not mean that call is
always getting dropped. It means call stays on a particular Timeslot for less than minimum
predefined holding time.

5. Some Real Time causes for this alarm

If calls are not holding on any timeslot means they are trying for handover. So reason may
be any handover reason in this case. With normal traffic pattern below are the possible
causes for this alarm.

• Hardware problem at either TRX level or sector level. In this case most of the
Timeslots on specific TRX will cause this alarm. You may get 7745 alarm
which means it is affecting TCH drop.
• Too many handover attempts or ping-pong effect can cause this alarm in high
number of 7743.
• Threshold affecting this alarm are not set properly. Following are the
thresholds with their default values which can be checked from ZEEO
command are affecting this alarm trigger.

o MINHTT = minimum mean holding time for a TCH (10 s)

o PRDMHT = length of TCH supervision measurement (240 min)
o CS = channel seizure threshold value (10)
6. Points to remember while checking 7743

Normally this alarm comes and gets cancelled automatically. ZEOH i.e History logs for 24
Hours will be more effective than current alarm logs for analysis. Always map TCH Drop &
HOSR of the cell against alarm count. It is not necessary that this alarm will affect Drop.
But yes it surely indicates that calls are not holding on a particular channel for a long time
and which is a point to be taken care even for Handover KPI.

7. How to find the root cause for this alarm

Subfields for this alarm are helpful things to find out the root cause for this alarm. Let us
understand one sample alarm log.

BSC92VIR BCF-0017 BTS-0049 QUAL 2009-06-15 21:42:46.13

** ALARM TRX -010 NZLPZOLAPUR3

(50367) 7743 MEAN HOLDING TIME BELOW DEFINED THRESHOLD

00 00 00 01 01 01 01 01 04 00 0d

The above example shows that calls are not holding on for the specified minimum time on
TRX no. 10 of BCF no. 17 of BSC92VIR. The affected Timeslots are TS 3 to
7.

First identify at which level the alarm is present, if it is at Timeslot level only. Simply
locking-unlocking of that Timeslot may resolve the problem. If the alarm persists on most
of the Timeslots of the specified TRX, check the TRX cabling or replace the TRX. If it
persists at sector level than it may be Hardware problem or too many handover attempts.
In most of the cases you will get alarm 7604, 7606 or 7745 on the site which means TCH
drop is currently affected. Incase of 7604 or 7606 it confirms hardware problem.

If the alarm is at very high number in network then first check the parameter thresholds
as described in point 5. If they found to be ok then take action at cell level.

8. Affecting KPIs

• TCH Drop at cell level can be highly affected by this KPI.

• HOSR may get affected due to high number of Handover attempts.