IP412 restarting

[simiewimie]

Hi,

Has anyone else experenced a problem with their IP412 restarting sporadically?
I have had it happen recently, but today it has done it 4 times in about 15 minutes!
Any ideas would be greatfully received. Our system maintainer has sent the logs out to AVAYA, but would love to hear from anyone who has/had this problem and to hear if it got sorted.

Thanks

Here is the tale end of one of the last logs:


CallingNum=3850 () Internal=0 Time=41 AState=Dialled
1056679mS PRN: AdjustCount 1,1 -> cur=10 out=5 v=9 d=1
1056679mS CMLineTx: v=1
CMSetup
Line: type=Q931Line 1 Call: lid=0 id=1516 in=0
Called[01173042700] Type=Default (100) SndComp
BC: CMTC=Speech CMTM=Circuit CMTR=64 CMST=Default CMU1=ALaw
Display [Sadie Cooper]
Cause=16, Normal call clearing
Locale: eng
1056803mS CMLineRx: v=1
CMProceeding
Line: type=Q931Line 1 Call: lid=0 id=1516 in=0
BChan: slot=2 chan=8
1056803mS CMMap: a=19.30 b=2.8 M1
1056805mS CD: CALL: 0.1515.0 BState=Idle Cut=3 Music=0.0 Aend="Sadie Cooper(3850)" (19.30) Bend="Line 1" [Line 1] (2.8) CalledNum=01173042700 ()

CallingNum=3850 () Internal=0 Time=169 AState=Dialled
1056806mS CD: CALL: 0.1515.0 BState=Dialled Cut=3 Music=0.0 Aend="Sadie Cooper(3850)" (19.30) Bend="Line 1" [Line 1] (2.8) CalledNum=01173042700 ()

CallingNum=3850 () Internal=0 Time=170 AState=Dialled
1056807mS CMExtnTx: v=3850, p1=29
CMProceeding
Line: type=DigitalExtn 5 Call: lid=0 id=29 in=0
Called[01173042700] Type=Default (100)
BChan: slot=19 chan=30
Display [01173042700]
Timed: 24/11/06 11:47
1056842mS CMExtnRx: v=3850, p1=29
CMShortCode
Line: type=NoLine 0 Call: lid=0 id=-1 in=0
ShortCode GetCallInfo (108) = []
1056842mS CMExtnTx: v=3850, p1=29
CMShortCode
Line: type=DigitalExtn 5 Call: lid=0 id=29 in=0
ShortCode GetCallInfo (108) = []
BChan: slot=19 chan=30
UUI type=User2User [C.........] [0x43 0x00 0x00 0x00 0x00 0x00 0x00 0x05 0xeb 0x00 ]
Timed: 24/11/06 11:47
1056855mS CMExtnRx: v=3850, p1=29
CMShortCode
Line: type=DigitalExtn 5 Call: lid=0 id=29 in=0
ShortCode GetUser (88) = [] Calling[901173042700] Type=Default (100)
UUI type=User2User [..] [0x00 0x01 ]
1056856mS CMExtnTx: v=3850, p1=29
CMShortCode
Line: type=DigitalExtn 5 Call: lid=0 id=29 in=0
ShortCode GetUser (88) = []
BChan: slot=19 chan=30
UUI type=User2User [..] [0x00 0x01 ]
Timed: 24/11/06 11:47
1056907mS CMExtnRx: v=3850, p1=29
CMShortCode
Line: type=DigitalExtn 5 Call: lid=0 id=29 in=0
ShortCode GetGroup (89) = [] Calling[901173042700] Type=Default (100)
1056908mS CMExtnTx: v=3850, p1=29
CMShortCode
Line: type=DigitalExtn 5 Call: lid=0 id=29 in=0
ShortCode GetGroup (89) = []
BChan: slot=19 chan=30
Timed: 24/11/06 11:47
1056956mS CMExtnRx: v=3850, p1=29
CMShortCode
Line: type=DigitalExtn 5 Call: lid=0 id=29 in=0
ShortCode GetUser (88) = [] Calling[01173042700] Type=Default (100)
1056956mS CMExtnTx: v=3850, p1=29
CMShortCode
Line: type=DigitalExtn 5 Call: lid=0 id=29 in=0
ShortCode GetUser (88) = []
BChan: slot=19 chan=30
Timed: 24/11/06 11:47
1057002mS CMExtnRx: v=3850, p1=29
CMShortCode
Line: type=DigitalExtn 5 Call: lid=0 id=29 in=0
ShortCode GetGroup (89) = [] Calling[01173042700] Type=Default (100)
1057002mS CMExtnTx: v=3850, p1=29
CMShortCode
Line: type=DigitalExtn 5 Call: lid=0 id=29 in=0
ShortCode GetGroup (89) = []
BChan: slot=19 chan=30
Timed: 24/11/06 11:47

********** contact lost with 192.168.1.3 at 11:48:15 24/11/2006 - reselect = 1 **********
******************************************************************

 

[Markee71]

the only time i saw that was a badly fitted pri/bri daughterboard - removal and refitting solved it for me

hth

 

[janni78]

Is that a default monitor trace?

Just expected to see more if it's rebooting.

 

[simiewimie]

Yes it is from the Monitor trace. I have not included the log after it has rebooted.

 

[janni78]

I meant have you changed anything under "Trace Options" or did you press "Default All" before taking the trace.

 

[simiewimie]

Aha! It is defaulted.

 

[aarenot]

if you have any exts which do not have active phones plugged into them yet are patched through to a jack, unplug their patch cord. if you have cat 5 jacks for voice and data, i have seen users plug their pc network patch cord into the phone jack, and bam down comes the module which it was plugged into.

stray voltage on the external ground, a bad phone, overheating power supply, bad power lead, are also some of the lucky things i have discovered.

 

[jml2665]

had this with a bad P/S on the control unit. Never saw a reason because it would just shut off leaving nothing in the log but the "contact lost"
as aarenot said also, check those items as well, I have never had it happen but this forum has had several reports of bad wiring causing the system to restart

 

[aarenot]

in this situation the modules had been deemed to need replacement until i arrived on site with the new module and unplugged the patch cords one by one to see the module come back up as i unplugged the patch cord which was plugged into the nic card on a pc. might try checking all your patch cords to see they are connected to valid phones on the other end at the jack.

 

[simiewimie]

Thank you all for your help. I shall get all the ports checked on Monday.