Trunk line - lockout status

[letacla21/2]

Hi all,
Any one tell me how could i identify the issues,why the trunk line gets into a lockout state, below are the alarms:
16/11/10 13:22:45 000001M|000/14/0/002|=4:0279=Shift into line lockout status
16/11/10 13:12:18 000001M|000/08/0/011|=4:0279=Shift into line lockout status
16/11/10 10:52:15 000001M|000/16/0/014|=4:0279=Shift into line lockout status
16/11/10 10:52:11 000001M|000/01/0/017|=4:0279=Shift into line lockout status
16/11/10 09:33:19 000001M|000/14/0/002|=4:0279=Shift into line lockout status
16/11/10 09:21:37 000001M|000/08/0/009|=4:0279=Shift into line lockout status
16/11/10 01:19:02 000001M|000/01/0/005|=4:0279=Shift into line lockout status
15/11/10 23:23:30 000001M|000/08/0/003|=4:0279=Shift into line lockout status
15/11/10 22:02:52 000001M|000/01/0/009|=4:0279=Shift into line lockout status
15/11/10 19:07:18 000001M|000/01/0/004|=4:0279=Shift into line lockout status
15/11/10 18:36:40 000001M|000/08/0/003|=4:0279=Shift into line lockout status
15/11/10 18:10:13 000001M|000/01/0/022|=4:0279=Shift into line lockout status
15/11/10 17:17:40 000001M|000/01/0/004|=4:0279=Shift into line lockout status
15/11/10 11:58:36 000001M|000/01/0/007|=4:0279=Shift into line lockout status
15/11/10 10:03:09 000001M|000/08/0/009|=4:0279=Shift into line lockout status
15/11/10 06:48:34 000001M|000/10/0/018|=4:0279=Shift into line lockout status
15/11/10 06:18:47 000001M|000/01/0/000|=4:0279=Shift into line lockout status
15/11/10 00:17:21 000001M|000/14/0/017|=4:0279=Shift into line lockout status
14/11/10 19:19:51 000001M|000/01/0/018|=4:0279=Shift into line lockout status
14/11/10 18:35:40 000001M|000/03/0/006|=4:0279=Shift into line lockout status
14/11/10 17:58:26 000001M|000/03/0/006|=4:0279=Shift into line lockout status
But the trunk cards is in Slot 2,11 & 1 trunk grp is configured and the system info :
CPU type : cpu7
Linux version : 62.3

Delivery software version : h1.301 ;
Patch version : 28 ;
Dynamic patch version : b ;

MAO software version : H1.301.28 ;
Software Version Name : R9.0 ;
config :
+-------------------------------------------------------------------+
| Cr | cpl| cpl type | hw type | cpl state | coupler ID |
|----|----|------------|-----------|--------------|-----------------|
| 0 | 0 | UA32|---------- | IN SERVICE | 3BA53050ABBC01 |
| 0 | 1 | Z24_2|---------- | IN SERVICE | 3BA53065NACF03 |
| 0 | 2 | NDDI|---------- | IN SERVICE | 3BA53095AWBB02 |
| 0 | 3 | Z24_2|---------- | IN SERVICE | 3BA53065NACF03 |
| 0 | 5 | eZ32|---------- | IN SERVICE | 3BA23265ABCB04 |
| 0 | 6 | CPU7_STEP2|---------- | IN SERVICE | BAD PCMS CODE |
| 0 | 7 | IO2N|---------- | IN SERVICE | 3BA23190ABKD02 |
| 0 | 8 | Z24_2|---------- | IN SERVICE | 3BA53065NACF03 |
| 0 | 10 | Z24_2|---------- | IN SERVICE | 3BA53065NACF03 |
| 0 | 11 | NDDI|---------- | IN SERVICE | 3BA53095ADBB04 |
| 0 | 12 | Z24|---------- | IN SERVICE | 3BA53065AFBA02 |
| 0 | 13 | MMSFD|---------- |ONLY MAO FILE | BAD PCMS CODE |
| 0 | 14 | Z24_2|---------- | IN SERVICE | 3BA53065NACF03 |
| 0 | 15 | Z24|---------- | REG NOT INIT | BAD PCMS CODE |
| 0 | 16 | Z24|---------- | IN SERVICE | 3BA53065AFBA02 |
| 0 | 17 | GPA2|---------- | IN SERVICE | 3BA23241AAJC05 |
| 0 | 20 | CPU7_STEP2|---------- | IN SERVICE | BAD PCMS CODE |
| 0 | 21 | IO2N|---------- | IN SERVICE | BAD PCMS CODE |
| 0 | 23 | Z24|---------- | IN SERVICE | 3BA53065AFBA02 |
| 0 | 24 | NPRAE|---------- | IN SERVICE | 3BA23254ABJE02 |
| 0 | 25 | Z24_2|---------- | REG NOT INIT | BAD PCMS CODE |
| 0 | 26 | UA16|---------- | REG NOT INIT | BAD PCMS CODE |
| 0 | 27 | Z12|---------- | IN SERVICE | 3BA53071AFBA02 |
+-------------------------------------------------------------------+

thanks

[vad]

Why you say about trunk line? 0-3-6 - Z24_2 board (internal analog set).
May be person dial prefix - set feature/ lock?

[letacla21/2]

I have given the alarms that generated from the system, only the trunk lines gets lock. no alarm related to a trunk cards.


thanks

[enio.eltz]

Hi letacla

The problem is with analog sets, see the incinfo:

Incident number (q to quit):0279

INCIDENT NUMBER: 279
Network indicator: Alcatel 4400
OBJECT CLASS: Dhs3Terminal
EVENT TYPE: ProcessingErrorAlarm (10)
PROBABLE CAUSE: Unknown (0)
SEVERITY: Warning

"Shift into line lockout status"
"Analog station shift into line lockout status"
"Analog station in line lockout status. When the set returns to"
"the normal status, no other additional messages are edited."
"No system reaction"
"No operator action required";

All the boards in your alarms are Z boards. It seems like the phone offhook too much time.

Vad, do you agree with this explanation?

Regards.

[vad]

All alarms from Z equipment (0-1, 0-3, 0-8...) - Z24 boards.

F.e.
14/11/10 17:58:26 000001M|000/03/0/006|=4:0279=Shift into line lockout status (equipment 0-3-6)

from config we can see
| 0 | 3 | Z24_2|---------- | IN SERVICE | 3BA53065NACF03 |


Noting about TRUNKS.

[letacla21/2]

So how could i get Trunk lines alarms...or is that because of too much off-hook from the relevant equipments the trunk gets lockout.
appreciate if any tell me how could i trace the line lockout issues...

thanks

[vad]

You say "trunks, trunks" - show (or explain) something about trunks.
Line in OS state, not disconnected transit calls, something else.

We see incidens with Z equipment. Nothing about TG or NDDI boards.

[enio.eltz]

Hi

What are the problems you are having at the trunks?
You have shown us incidents with the Z boards. These are for analog phones.
As Vad said before, nothing about TG or trunk boards.

[enio.eltz]

Or better

Explain here the problem you are having...

[letacla21/2]

my problem is trunks getting lock, (at this time all the trunks shows busy, and cannot size any trunk), so i need to trace why trunks getting hang.