Meridian Phones Going Off

[jalvayu1]

Meridian 61C VERSION 2921 Release 3. After a recent upgrade everyday, at random, some of the phonesets(M3903) get hung. The display goes blank, no voice, but the phone remains alive. It's status is shown as IDLE. The menus can be accessed using the phoneset buttons. Even a call can be dialed and received, but there is no speech and no display. The problem gets resolved without any intervention after an indefinite time (usually hours). Can any one help?

 

[Nortellian]

who did the upgrade? Make sure they loaded all the patches.
you probably want to fdls xxxx in load 32. This will flash download your 3900 sets. Do this when phones are not being used becasue it takes phone out of service for a while.

 

[DocVic]

You didn't detail what type of upgrade. Software, hardware and what release??? Were all patches and PEP's installed? Was the system ground re-checked? Need more details, since this problem started after the upgrade.

Doc-V

 

[janchundia]

you need download the firware in each digital phone.
I prefer to made in non-bussines hours the procedure.

LD 32
.FDLU TN
OR
.FDLS XXXX where xxxx =3902,3903,3904,3905, all and now

Regards.


Javier

 

[johnpoole]

another known problem is phones that do not match the as built type.. they don't go down, but phones that call them do.. here's a list of patches you may need

IN-SERVICE PATCHES : 47
PAT# PRS/CR PATCH REF # NAME DATE FILENAME
00 MP05829 ISS1:1of1 Core 30/10/04 p12511_1.cpt
01 Q00464575 ISS1:1OF1 BRIL/BRIT 30/10/04 p16540_1.cpt
02 Q671307 ISS5:1OF1 QSIG 30/10/04 p17448_5.cpt
03 Q00689616 ISS1:1OF1 ACD/NACD 30/10/04 p17512_1.cpt
04 Q00665199 ISS2:1OF1 CDR 30/10/04 p17559_2.cpt
05 Q00702474 ISS1:1OF1 CORE 30/10/04 p17571_1.cpt
06 Q00709405 ISS1:1OF1 Symposium 30/10/04 p17643_1.cpt
07 Q00712182 ISS1:1OF1 Group Hunt/PLDN 30/10/04 p17790_1.cpt
08 Q00349307 ISS1:1OF1 CORE 30/10/04 p17820_1.cpt
09 Q00724590 ISS1:1OF1 TAURUS 30/10/04 p17823_1.cpt
10 Q00757690 ISS1:1OF1 Meridian Mail 30/10/04 p17825_1.cpt
11 Q00748087 ISS1:1OF1 Core 30/10/04 p17845_1.cpt
12 Q00753247 ISS1:1OF1 CORE 30/10/04 p17853_1.cpt
13 Q00743283_ ISS1 1OF1 CORE 30/10/04 p17889_1.cpt
14 Q00743414 iss1:1of1 CORE 30/10/04 p17890_1.cpt
15 Q00749407 ISS1:1OF1 CORE 30/10/04 p17891_1.cpt
16 Q00755208 ISS1:1OF1 Core 30/10/04 p17893_1.cpt
17 Q00761422 ISS1:1OF1 core 30/10/04 p17895_1.cpt
18 Q00660652- ISS1:1OF1 Taurus Sets 30/10/04 p17897_1.cpt
19 Q00761893 ISS1:1OF1 Core 30/10/04 p17899_1.cpt
20 Q00754053 ISS1:1OF1 Core 30/10/04 p17922_1.cpt
21 Q00771896 ISS2:1OF1 CORE 30/10/04 p17946_2.cpt
22 Q00775297 ISS1:1OF1 Core 30/10/04 p17960_1.cpt
23 Q00743121 ISS1:1OF1 CORE 30/10/04 p18024_1.cpt
24 Q00573831 ISS2:1OF1 CallPilot 30/10/04 p18025_2.cpt
25 Q00755955- ISS1:1OF1 Core 30/10/04 p18028_1.cpt
26 Q00779816 ISS1:1OF1 ACD/NACD 30/10/04 p18040_1.cpt
27 Q00735881 iss1:1of1 CORE 30/10/04 p18043_1.cpt
28 Q00769104 ISS1:1of1 CORE 30/10/04 p18051_1.cpt
29 Q00782006 ISS1:1OF1 ACD/NACD 30/10/04 p18066_1.cpt
30 Q00790668 ISS1:1OF1 QSIG 30/10/04 p18081_1.cpt
31 Q00767458 ISS1:1OF1 CORE 30/10/04 p18090_1.cpt
32 Q00792920- ISS2:1OF1 ACD/NACD 30/10/04 p18123_2.cpt
33 Q00798017 ISS1:1OF1 GF 30/10/04 p18163_1.cpt
34 Q00773689 ISS1:1OF1 Core 30/10/04 p18229_1.cpt
35 Q00828559 iss1:1of1 CORE 30/10/04 p18242_1.cpt
36 Q00783145 ISS1:1OF1 p18250_1 30/10/04 p18250_1.cpt
37 Q828904 ISS1:1OF1 QSIG 30/10/04 p18305_1.cpt
38 Q00744653 iss1:1OF1 Core 30/10/04 p18380_1.cpt
39 Q00792601 ISS1:1OF1 Symposium 30/10/04 p18387_1.cpt
40 Q00811297 ISS1:1OF1 CORE 30/10/04 p18393_1.cpt
41 Q00861684 ISS1:1OF1 QSIG 30/10/04 p18433_1.cpt
42 Q00859329 ISS1:1OF1 Symposium 30/10/04 p18444_1.cpt
43 Q00850201 ISS1:1OF1 CORE 30/10/04 p18446_1.cpt
44 RAJARSHI H ISS2:1OF1 ACD/NACD 30/10/04 p18677_2.cpt
45 Q00834606 ISS1:1OF1 p18739_1 30/10/04 p18739_1.cpt
46 Q00800638 ISS1:1OF1 p18875_1 30/10/04 p18875_1.cpt




john poole
bellsouth business
columbia,sc

 

[msunjai]

True, Known problem now, and can be fixed with patches mentioned above by John.

6-8 months after migrating, I also faced this problem on my 61c nearly 1&1/2 year back that too in contact center. Nobody was sure that time what exactly has gone wrong all of sudden. And there was no time sequence, card or particular loop which was facing this problem, but random occurence. so no wild guess even...

we did thorough check on power side, phones cabels, enabled trace on TNs, downloaded firmare on all 39xx phones, changed CP/IODUC, CNI, CC on IPE, and DLC too but nothing worked out.

Later on full system re-install(we need that b'cos full h/w & config chg has created a lot of bugs) and proper patches solved this problem.

check the latest patch available...in NNT library, I believe that will solve your problem. No need to worry about M1 h/w or power at the first instant itself.

 

[janaya]

what did your tech tell you...

"patches...patches...we don't need no stinking patches"

Seen all this and it's either a firmware upgrade, usually to Phase II will clear, or a patch install, but patches were usually needed prior to succession.

 

[janchundia]

I had the same problem in a new installation.
After firware upgrade for all phones the system is working in normal mode