HELP ME!! Lines going dead after in service for a couple of days

[telephonesteve]

About 3 months ago I insalled a MICS 6.0 with 2 global caller ID cards. The customer has 6 incoming lines and 2 door/gate boxes.

After 2-3 weeks of service lines 31-34 went out. (display read: not in service) Resetting(unplugging) the system fixed it. At this time I thought it was a fluke, wishfull thinking on my part.

A few days/weeks later same thing, this time I swapped cards it happens again, and again. I finally swap the whole system 0x32, software and new CLID cards.

3 weeks later lines 31-34 are out of service again with all new equipment. I did not replace telephones (I would hope a bad telephone can not take down a trunk card)
Resetting clears the problem.

The event code that I get is: 52-02-2
After unplugging it I get: Startup, Evt:299, Evt:462 which I think in normal on a power up.

I have also ramdomly had: Evt:995, Evt:247 but I do not know what these or Evt:462 are, does anyone know what these are?

I checked the loop current milliamps and the lines on that card are:
33ma, 33ma, 31ma, 41ma

I don't know if these are to high but does anyone know the tolerences for loop current for this switch?

I am looking for any ideas on what else to check or do

Help

Steve Yearley

 

[luv2ski]

did you check dip switch settings?

 

[telephonesteve]

All the switches on the global CLID card are in the off (0)position.

 

[luv2ski]

what does the paperwork that came with them say

 

[telephonesteve]

The Global ATC and CLI Cartridge Installation Notice
says that the default dip switch settings are for North America and it also gives a table of all dip switch settings. The cards installed are set up correctly according the the installation notice table. There is a screen print of the dip switch table on the CLID card itself.

 

[luv2ski]

event 247 says"an invalid channel related event was recieved"
action= record event message and contact your local support group
event 462 says "system shrinkage. corrupted data set to default"
action=customer data must be programmed
if these are the codes i would try a call to itas or do a startup and reprogram from scratch...i would call itas if its going to take longer than an hour or 2 to reprogram

 

[Stacyjo4]

I have the same situation, but with a T-1 card. Random channels show inactive - I have to deprovision and then reprovision the lines to get them up.

Did you get yours figured out?

Thanks
Stacy

 

[telephonesteve]

Have not figured it out yet.

Stacy, what version of software are you have trouble with/
I am going to install some loop current regulators next week. I don't know if this will really help but it won't hurt

 

[Stacyjo4]

My MICS version is - 30BwE02 NAT

Let me know what happens on your end!
Thx
Stacy

 

[Arr]

Telephone Steve,
Some random thoughts..
Your loop current is perhaps, maybe, could be.. a little high.. but it is easily within telco range. Did you measure the voltage? By your stated loop current values it should be within spec too. What does the maint function state when the lines report out of service?
What software and release of cards are you using? Is the site rural? Have you got really good grounding and lightning protection on the COs? Where I am we get a huge amount of sheet lightning which you don't see.. but its there ... and it goes to ground just the same way. Also check your AC ground terminal (third prong). Make sure it actually goes to ground.
Do you have a fast rad on this to report alarms as they are occurring?
The fact that the line groups appear to be randomly going out of service leans my thinking towards the COs acting as a system ground. But check and verify the grounding on site.

Good Luck
PhM

 

[yahoogy]

Mite seem dumb-but check your line supervision settings and change them to see what affect it has.But sounds more like a software problem from nortel related to the new system design for the e-1.