Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

5330 Fatal Error

Status
Not open for further replies.

james1982

Technical User
Nov 14, 2003
441
GB
Hi

I have a 3300 MXE with 700ish 5330s connected.
A problem has arisen over the last week where intermitently random phones restart. The phone screen flashes and a message appears on screen "Fatal Error" and then the handset counts down from 60 seconds and then restarts itself.
About 8 weeks ago we upgraded to rel 8 ur 4, unsure if its anything to do with this.

Im in the process of gathering dates / times of the fault to attempt to try scroll through the logs but in the meantime was wondering if you guys had experienced this at any time?

Cheers
 
Did all the phones upgrade ?
Why upgrade to UR4 if there is a UR5 and 9.0 already ?


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
yes all phonse upgraded, rel9 wasnt out took it up to rel 4 as we have numerous sites running all stable, whereas we have a few sites on rel 5 with issues. plus this customer has other sites within there network running rel 4.

any ideas as to the cause of the error?
 
Never seen it to be true but i am not that long busy with a Mitel :)


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
I've seen this at UR4 with phones that had never been connected. They were fine if I connected them to a system running UR3 and then they were fine for UR4.

I also had an issue at 8.0 where the VLAN was statically assigned but the priority wasn't. The Priority wasn't assigned in DHCP either.

Both scenarios resulted in fatal errors.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top