sundance-communications.com/forum Forums Other TDM Phone Systems Allworx Telephones & Systems 6x 7.5.4.10 crashes every 6 hours

To the others seeing 7.5 crashes, have you seen it on new installs (fresh install of 7.5, then programmed), or on any 7.5 system?

The reason I ask is that we upgraded our in-house system to 7.5.2.3 and settings here and there were lost. For example, the imap port, 143, was no longer open on the WAN. The system (a 48X!) would crash after five minutes [it was functioning as a router for only five people (although this was possibly due to the DoS attack against system that were hacked and then subsequently patched but I didn't have time to capture packets)]. To fix it I put in a different router and disabled ping (stealth dmz).

As a general rule, never install the newest allworx software until it's been out for about six months or has seen about 3 or 4 revisions. This software is on the portal as "not having seen a diverse range of deployments", which is their way of saying its beta.

Update:
My customer's installer downgraded their loaner box to 7.4, and still had the same issues of crashing every 6 hours, so it is not a sftw issue. So I had him unplug the WAN port for a weekend, and the system stayed up the whole time. Soon as it was connected again, back to 6 hour crashes.
So this is definitely not a hardware or sftw issue. Customer did pay the installer to install a firewall at install but the one they wanted to put in was back ordered. Hopefully they will get that in soon. If his system is being attacked then that should solve it. If it doesn't, than this must be a Broadvox issue. So a new SIP provider might be the next step if they can't fix it.
Not there yet, but at least we're narrowing it down.
Thanks all for the input, I'll post resolution once we get there.

Had a new tech go out there Monday, and couldn't really find much, however he did see a verizon router connected to the network that was for his cable TV in the waiting room. They disconnected it just to rule out a conflict, and surprise surprise system has been up ever since. Turns out it is a couple years old and had a known issue for "every 6 hours" trying to ping and if it didn't get through it would throw a monkey wrench in the network. Which would explain the every 6 hour crash, something so simple but took so long for it to be noticed. Hope this helps someone out there one day, and again I appreciate everyone's input in the matter.