M3905 damaged totally and give ERR080

[nokia6600]

Dear All,

I have a problem in call center handsets M3905 (firmware 8.3)
the problem is :
each about 2 or 3 days and suddenly the M3905 is damaged and went to out of service, i.e No power on the phones , no display on the screen at all ( the phone totally damaged).

System type is - Communication Server 1000E/CP PM
RELEASE 6
LOADWARE VERSION: PSWV 100+

within this 2 weeks we got 15 phones damaged .
today 3 phones are damaged at TNs :
12 0 6 3
16 0 7 2

the logs (ahst file) at the time of the problem show the ERR080
on the damaged TNs.

Note that before 1 months our vendor has installed the latest patches on the CS1000E (LOADWARE VERSION: PSWV 100+)
the problem happend 1 week later.
we did all the necessary checking (cabling , power earthing ... but no problem on it)
Please help me solving this case !!!!!!!!!!!!


Log file
************************************
TIM000 13:00 17/1/2012 CPU 0
%
% QOS018 QoS unacceptable jitter: [57.6] % in zone [1]
%
% SEC054 A device has connected to, or disconnected from, a pseudo tty without a
uthentica
% ting
%
% TTY #13 LOGGED IN ADMIN2 13:07 17/1/2012
%
% TTY #13 LD 020 ADMIN2 13:07:29 17/1/2012
%
% QOS018 QoS unacceptable jitter: [60.0] % in zone [1]
%
% ERR080 16 0 7 2 112
%
% ERR080 16 0 7 2 117
%
% ERR080 16 0 7 2 91
%
% ERR057 12 0 6 3 0000DDBF
%
% QOS018 QoS unacceptable jitter: [69.1] % in zone [1]
%
% TIM000 13:15 17/1/2012 CPU 0
%
% ERR080 12 0 10 9 95
%
% ERR080 12 0 10 9 224
%
% ERR080 12 0 10 9 40
%
% ERR118 12 0 10 9
%
% ERR118 12 0 10 9
%
% ERR118 12 0 10 9
%
% QOS018 QoS unacceptable jitter: [75.3] % in zone [1]
%
% VAS008 ADMIN VSID 9 CUST -- TIME & DATE 13:20:16 17/01/2012
%
% AUD370 VSID 9 CUST --
%
% QOS018 QoS unacceptable jitter: [92.7] % in zone [1]
%
% TTY #13 LOGGED OUT ADMIN2 13:27 17/1/2012
% SESSION DURATION: 00:21
%
% QOS018 QoS unacceptable jitter: [66.6] % in zone [1]
%
% VAS008 ADMIN VSID 9 CUST -- TIME & DATE 13:29:16 17/01/2012
%
% AUD370 VSID 9 CUST --
%
% TIM000 13:30 17/1/2012 CPU 0
%
% QOS018 QoS unacceptable jitter: [64.1] % in zone [1]
%
% QOS018 QoS unacceptable jitter: [52.9] % in zone [1]
%
% QOS018 QoS unacceptable jitter: [50.2] % in zone [1]
%
% QOS018 QoS unacceptable jitter: [52.7] % in zone [1]
%
% TIM000 13:50 17/1/2012 CPU 0

 

[nessman]

ERR0080 tn key
Key input from software-unequipped add-on module.
Action: Check SL-1 telephone data. Ensure that add-on module is defined and that key number is less than last key.

ERR0057
Excess invalid input messages from digital sets. Every input message is counted. When the total count reaches a limit, this error message will be printed and the count is reset to zero. The TN printed is only the TN that generated the last invalid message. Other TNs may have generated earlier messages. If no faults are found on the reported unit then investigate other cards.

ERR0118
Invalid Keymap Download Request for nonexistent add-on module.


Print out the programming for the affected phonesets and copy/paste here and let's take it from there. Also confirm if there are or are not any AOM's physically attached to these 3905's.


In the meantime, I'd get on the horn with your vendor and have them take a look - especially if you're under maintenance or warranty.

 

[nokia6600]

Hi nessman,
thanks for the reply .

there is no AOM's attached to the phonset.
please note that phonsets's firmware is not up-to-date and doesn't match patch level.
here is the printout for the affeted TNs:

NACT
REQ: prt
TYPE: tnb
TN 16 0 7 2
DATE
PAGE
DES

DES AGNT
TN 016 0 07 02 VIRTUAL
TYPE 3905
CDEN 8D
CTYP XDLC
CUST 0
ERL 0
FDN
TGAR 1
LDN NO
NCOS 0
SGRP 0
RNPG 0
SCI 0
SSU
LNRS 16
XLST
SCPW
SFLT NO
CAC_MFC 0
CLS TLD FBD WTA LPR MTD FND HTD TDD CRPD STSD
MWD LMPN RMMD SMWD AAD IMD XHD IRA NIA OLA VCE DRG1
POD DSX VMD SLKD CCSD SWD LNA CNDA
CFTD SFD MRD DDV CNID CDCA MSID DAPA BFED RCBD
ICDD CDMD MCTD CLBD AUTU
GPUD DPUD DNDA CFXD ARHA CNTD CLTD ASCD
CPFA CPTA ABDD CFHD FICD NAID BUZZ AGRD MOAD
UDI RCC HBTD AHA IPND DDGA NAMA MIND PRSD NRWD NRCD NROD
DRDD EXR0
USRD ULAD RTDD RBDD RBHD PGND OCBD FLXD FTTC DNDY DNO3 MCBN
FDSD NOVD CDMR PRED MCDD T87D PKCH
CPND_LANG ENG
HUNT
LPK 0
PLEV 02
PUID
DANI NO
SPID NONE
AST 01 00
IAPG 1
AACS YES
ACQ AS: TN,AST-DN,AST-POSID
ASID 19
SFNB 1 2 3 4 5 6 9 10 11 12 13 15 16 17 18 19 22 24 25 26 3
3 34 35 36 37 38
SFRB 1 2 15
USFB 1 2 3 4 5 6 7 9 10 11 12 13 14 15
CALB 0 1 3 4 5 6 8 9 10 11 12
FCTB 1
ITNA NO
DGRP
PRI 01
MLWU_LANG 0
MLNG ENG
DNDR 0
KEY 00 ACD 2700 0 262
AGN
01 SCR 232 0 MARP
02 NRD
03 MSB
04 DWC 2700
05 ACNT
06 EMR
07
08
09
10
11 ASP
12
13
14
15
16
17
18 AO6
19
20 RGA
21 PRK
22 RNP
23
24 PRS
25 CHG
26 CPN
27 CLT
28 RLT
29
30
31
DATE 10 OCT 2011


NACT
************************
REQ:
QOS018 QoS unacceptable jitter: [100.7] % in zone [1]
prt
TYPE: tnb
TN 1*
TN 12 0 6 3
DATE
PAGE
DES

DES AGNT
TN 012 0 06 03 VIRTUAL
TYPE 3905
CDEN 8D
CTYP XDLC
CUST 0
ERL 0
FDN
TGAR 1
LDN NO
NCOS 1
SGRP 0
RNPG 0
SCI 0
SSU
LNRS 16
XLST
SCPW
SFLT NO
CAC_MFC 0
CLS TLD FBD WTA LPR MTD FND HTD TDD CRPD STSD
MWD LMPN RMMD SMWD AAD IMD XHD IRA NIA OLA VCE DRG1
POD DSX VMD SLKD CCSD SWD LNA CNDA
CFTD SFD MRD DDV CNID CDCA MSID DAPA BFED RCBD
ICDD CDMD MCTD CLBD AUTU
GPUD DPUD DNDA CFXD ARHA CNTD CLTD ASCD
CPFA CPTA ABDD CFHD FICD NAID BUZZ AGRD MOAD
UDI RCC HBTD AHA IPND DDGA NAMA MIND PRSD NRWD NRCD NROD
DRDD EXR0
USRD ULAD RTDD RBDD RBHD PGND OCBD FLXD FTTC DNDY DNO3 MCBN
FDSD NOVD CDMR PRED MCDD T87D PKCH
CPND_LANG ENG
HUNT
LPK 0
PLEV 02
PUID
DANI NO
SPID NONE
AST 01 00
IAPG 1
AACS YES
ACQ AS: TN,AST-DN,AST-POSID
ASID 19
SFNB 1 2 3 4 5 6 9 10 11 12 13 15 16 17 18 19 22 24 25 26 3
3 34 35 36 37 38
SFRB 1 2 15 32
USFB 1 2 3 4 5 6 7 9 10 11 12 13 14 15
CALB 0 1 3 4 5 6 8 9 10 11 12
FCTB
ITNA NO
DGRP
PRI 01
MLWU_LANG 0
MLNG ENG
DNDR 0
KEY 00 ACD 2700 0 2993
AGN
01 SCR 1105 0 MARP
02 NRD
03 MSB
04 DWC 2700
05 ACNT
06 EMR
07
08 ASP
09
10
11
12
13
14
15
16
17
18 AO6
19
20 RGA
21 PRK
22 RNP
23
24 PRS
25 CHG
26 CPN
27 CLT
28 RLT
29
30
31
DATE 11 OCT 2010


NACT

 

[nessman]

To upgrade the firmware go in to LD 32 and refer to Nortel's documentation for the specifics. Just keep in mind that you will brick the phone if you interrupt the firmware upgrades... do schedule these for when you know the phones will be idle for a period of time (takes about 5 minutes per phone).

 

[treys10]

Ld 97 (fdl) you can set it to run at a specific time. Then turn it on in ld 32.

 

[curtismo]

Sorry, but this still sounds like a wiring issue, either a short or other voltage on the wiring. Have you tried pulling the jumpers at the MDF and place one of these phones directly on the switch tails, prior to entering your plant wiring?

Also, have you tried swapping out the line card that has an affected 3905 on it?

 

[Meridianman64]

go step by step, at the MDF make a test jack from an insert and punch down directly at the frame. If the phone works there, go to the associated IDF and do the same..if it works all the way to the jack, replace/rewire the jack and then test again.