Random phone system "crashes"

[cholzhauer]

I have three 5000's and over the past few months, they've all crashed at least once.  The main 5000 has only crashed once, but even once is too much.  The two remote systems seem to have more problems and the crashing seems to be random.

Let me clarify "crash".  In this sense, crash means the phone system won't route calls.  The endpoints look normal and I'm able to connect to the 5000 via the Mitel software, but no one is able to make IC or outbound calls.

I'm running 6.0.11.95

Thanks for any help you can provide.

[akuhn]

I logged into my 5000 and attempted to determine our current version:

System Release [6.0.85]: Mitel 5000 Release mtl-5000-6_0-release-51_SP_1_PR_5

If what I have is newer than what you have, please consider an upgrade to the firmware.  When we moved to our new location, we were getting tons of fast busy signals.  This update fixed the problem.  It didn't present itself until we got a new PRI.  Simple change brought this issue to the top.  Luckily, our area Mitel Tech had seen this before and came out and did the upgrade.  15 minutes and it was fixed.

Hope this helps.

Adam in DC

[Tech Electronics]

Cholzhauer,

Alright, so you are at the latest version of software 6.0 SP2 PR1 on the system you sent the logs in for. When exactly did this thing lock up. I see that you logged in on the 27th and did a reset; is that when it locked up as well?

Thanks,

TE

[cholzhauer]

Unfortunately I don't know when it actually crashed.  I reset it the morning of the 27th and again this morning, but it could have crashed any time in between there.

[akuhn]

While you guys are probably more well versed on Mitel than I am, are we sure that the version in question is the newest one? 

System Release 6.0.85 is a higher number than 6.0.11.95

However, it's possible I'm looking at the wrong number.  Just want to make sure there isn't an update available for you to take advantage of.

[Tech Electronics]

akuhn,

I appreciate you trying to help, and keep it up, but your version is actually 6.0.10.85 [6.0. SP1 PR5]. The version we are looking at is 6.0.11.95 [6.0 SP2 PR1]. So basically your version is two behind the version we are working on here. Although I would not upgrade yours to the latest version just yet since the latest version has been having some problems.

As a side not it is never a good idea to update to the latest release due to these types of issues, but I guess at some point someone has to do it or we would never find these problems.

Thanks,

TE

[Tech Electronics]

Cholzhauer,

Just looking at your log files nothing jumps out as to it having a major problem; that I have found. This will have to be sent to Mitel Tech Support for analysis.

Sorry,

TE

[cholzhauer]

We've opened a case with them; thanks for your help

[marcolive]

Do you have SIP port opened to the outside world?

We have dozens of 5000 systems and many of them are networked. Never seen this kind of issues. Something is wrong somewhere... In most environments, 5000 PBXs are solid and reliable systems.

Meanwhile, we see multiple instances of SIP hacking on 5060 port. Some people somewhere try different usernames/passwords via Internet. This impacts the CPU up to make the system unstable.

If you opened the 5060 port, try to close it for few days just to see!

[cholzhauer]

Thanks for the response.  SIP isn't enabled on this system, but it is on our "main" system.  However, it's locked down to specific outside addresses (our SIP provider)

[619Tech]

I have a similar issue. But now my PRI's actually go offline about a half hour after an A1007 - IPRA Critical - MSP Alert IPRA lost communication. Curious if you have any of those?

[cholzhauer]

I've never seen that error...when ours stops working, the phones look normal until you go to make a call; I have yet to see an error be shown on one of the admin phones.

[619Tech]

We were not seeing anything on the admin phones either. A1007 started showing up in Adcon Alarms. Mitel just found the issue in the latest freeze: SSH hack attempts from China & France on the PS-1. Having customer lock down port 22.

[cholzhauer]

We don't have ssh open on the outside

I've heard the system will crash if the logs become full, is that true?

[NTEDave]

The system just deletes the oldest logs when that logs particular memory allocation becomes full.