Ip office restart issue

[Guilherme1000]

hello,

I'm having a strange issue... almost everyday my ip office restarts. I have changed the hardware, control unit, PRI, nobreak and etc. but it's still happening. I got some prints from monitor, my digital line gives me a alarm 7 or 8 before every restart.

I supose it's a provider issue.

Has anyone seen this issue before?

 

[tlpeter]

Post a trace of the reboot and a couple of minutes before that (one trace, no sip or H.323)


BAZINGA!

I'm not insane, my mother had me tested!

 

[Westi]

had several different reasons for restarts, from a faulty release that did restarts out of whatever stupid reason to a faulty config that needed to be reprogrammed. Never had a faulty line force a restart though but that doesn't mean it is not the line
What release and hardware do you have, if you have an older release search the TB's for later releases if there was a fix for reboot issues.

Joe W.

FHandw, ACSS

http://convergednetworks.ca

 

[amriddle01]

I have seen ISDN30/PRI lines cause reboots and there have been several posts on here to the same end

 

[Westi]

I get old Andy I don't remember these posts :-(

Joe W.

FHandw, ACSS

http://convergednetworks.ca

 

[amriddle01]

I believe it's when the errors count up to a set point the system just gives up the ghost, it's been a weird provider issue or clock source issue (multiple set to network) every time if I'm not mistaken

 

[derhubi1985]

Hello,

I have the same problem since I have updated to R8.1. The problem is that the Provider has got a solve a problem on the line during I have updated the system. So I don't know where issue come from. Is it a IPO Problem or a Provider problem.

We have made a trace by the Provider and the resolution is, that line is clean.

At this time we opened a case by Avaya. But since thuesday we have no answer.

 

[amriddle01]

What does a monitor trace show leading up to the restart? In my book no matter what goes on with a line it shouldn't cause a system restart anyway, unless it's like a massive power surge or something

 

[hairlessupportmonkey]

versions of phone manager too old for the IPO release (or too new) can also cause this.

ACSS - SME
General Geek