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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Abnormal System Reboot?

Status
Not open for further replies.

IPOMonkey

Programmer
Jun 18, 2003
163
GB
I have an IP403 V2.1(15) with DT handsets.

I set a reboot when free and on my return checked monitor to see that the system had been up and running for 10 minutes but the client said it had not rebooted.The system then rebooted of its own accord and cut off all calls in progress it done this a good few times.

Then whenever i done a merge config the system seemed to cut of all calls in progress.

There is no corruption in the database and only a Listen In feature was added.

Is this a software issue?

 
First go to 2.1(27) seems to be the only stable version in 2.1.
Then look if you still have the same problems.

Greets Peter
 
I have similar problem to this. The problems occurs once we upgraded to 27. we have reverted back to 24. There were problems with the config which we have ironed out.

When performing merges the system rebooting are most common in the afternoon. I can do loads in the morning no problem without any problem. Do one in the afternoon and it reboots about 90% of the time. We have isolated the switch from the network but this problem still persists.

From viewing the logs there is no definite message which cause the system to reboot. The system reboots when monitor logs the message:
PRN: ff0528e0 00000000 00000000 00000000 00000000 00000000 00000000 00000000

We also have a problem that first thing the system seems to reboot and also after everyone has left for the evening. The only computers on during the evening crash are the network and monitor machin all others are shut down.

Any suggestions
 
We had a very similar problem. We ran the configs through the wizard without finding any issues, so we cut and pasted the fields one at a time checking the stability of the system after each one. We found that it was an incomming call route that was just bad. We re-programmed the route the exact way it was in before and it fixed the problem. The fact that the problem is only durring specific times is odd, but I would try to re-write if the upgrade/downgrade doesn't work.
 
I had the same problem on a busy system that rebooted every time you tried a merge. After deleting and reprogramming all incoming call routes the system became stable again.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top