Random IP Office Reboot 1

[jawillo]

Hello,

I am having this very strange problem with IP Office where it'll just randomly kick off all the users in one of my buildings...

We have two buildings.
Both have an IP Office 500 unit.
This only happens at one building.
We have a hot desking sort of setup (user extensions logon on top of the phone ID with the **Extn method)

Any ideas on how to stop this? It happens about once a day, and will actually kick users off of live phone calls (which is terribly disruptive)

Thanks for any help!

 

[jawillo]

jml,
"the initial information monitor posts is how long the system has been up for? Does the time on there coincide with when your system has it's issue?"

the information given by Monitor does indeed coincide with the last random reboot. (and thus the information regarding alarms that I see in the System Status).

Since we put this new system in, our main building has had this reboot happen only once or twice... while our 2nd building has it happen almost daily.
still troubleshooting...
thanks

 

[jawillo]

TheProvider,
I also checked my hunt group status, and I don't have any set to do a recursive overflow as you described. thanks for the input though.

Avaya is supposed to be working on a patch for this... but, they're proving difficult in providing a completion date for us.

 

[573dawn]

I have no hunt groups overflowing to themselves either.

 

[PlatinumGuy]

Dont rule out the obvious/coincedental here.

I have had experience in the last couple of weeks where by new 406's (not 500's granted) were rebooting on a daily basis.

Everything tried, check cfg, reprg by hand, take off network, take ip dect off blah blah blah.

HARDWARE FAULT WAS THE ISSUE.

Swap the control unit out, happy days.

I know it isnt cost effective to some smaller resellers but swapping hardware should always be in your mind, whe something is having major issues it isnt always a software bug.

If your trunks are saying out of service then you may wish to also check the clock quality setting on the pri trunks. I had a site whereby they were getting this issue and the system was set to clock off a QSIG PRI that was connected to a RAS server, there was obviously no real clock on this circuit and it was playing havoc with the system.

Also is this system on a cleansing UPS? You need to rule out possible power issues too.

Also go here and check v4 for known reboot issues already found and see if any of these already known issues apply to you.

http://marketingtools.avaya.com/knowledgebase/caveats/

ACA - IP Office Implement
ACS - IP Office Implement
ACE - IP Office Implement