IPOffice 500V2 7.029 rebooting 6

[makinconversation]

Hello, I am looking for anyone who has seen an issue of a reboot due to ABNORMAL TERMINATION. I turned sysmon on, so I have something to go on, and it looks as though it captured my problem. Now, I can't find any info on this. I am about to open a ticket with Avaya, but wanted to check here first. The last reading states "PRN: Pipe Send too big 583"... then it rebooted. It has done this 3 times in several weeks...middle of day, tv station. Any info would be great. Thanks

 

[LJDirk]

thanks for info, but the ipo run with 8.0.16 and the error is "pipe send too big 582

 

[tlpeter]

8.0.16 has the same bugfixes as 7.0.27
So when this bug is fixed in 7.0 then it will also be fixed in 8.0
I think that the difference in the number will not make a big difference.
You can raise a case with Avaya if you are a business partner.


BAZINGA!

I'm not insane, my mother had me tested!

 

[LJDirk]

thanks, sorry - understand you wrong.

the case with Avaya is runing and will escalate to tier4 today. Will see...

 

[tlpeter]

Ok, then you will be fine


BAZINGA!

I'm not insane, my mother had me tested!

 

[makinconversation]

I upgraded min to 8.016 and the VMPRO as well. Now it reboots more than it ever did. I am getting a system staus of Abnormal Termination Addr=00000000 PC=f032b060. Avaya says the address=00000000 is from the local provider, possible problem with the PRI. We are checking into that now... Anyone having this issue on one with analog trunks?

 

[LJDirk]

do you have 9508 connected? What say the ipo trace before ipo reboot?

 

[makinconversation]

It displayed Watchdog timeout dcpldisplay task stack, then several codes that look like f032b060...

 

[LJDirk]

also "pipe send too big"?
If yes, then it´s a bug in the 8.0.16. like in 7.0.12

I opened a ticket to avaya and received yesterday a privat build from there to fix that - hopefully ;-)
thats in the readme: "... Fixed crash when large terminal display update messages were sent to 95xx type phones. Updates are now split into smaller chunks.

 

[makinconversation]

Yes yes yes, pipe send too big right before the error, then a reboot. I have a tier 3 opened with Avaya, so I hope to get that fixed today...or we are opening conversation up to do a speedy install on a Mitel product

 

[tlpeter]

Ha ha ha Mitel. Don't make me laugh!!!!
Mitel cannot even get close to what the IPO can.
I know it is very annoying that you have those reboots but this is only happening because of certain conditions.
I did not see an IPO reboot with this error yet so it is not a very common issue.



BAZINGA!

I'm not insane, my mother had me tested!

 

[amriddle01]

The Mitel 5000 isn't a million miles away Peter, and has some distinct advantages over IPO for the same price range, depends what you want/need really. No one can deny that R7 and R8 is not exactly the best work we have seen from Avaya ...from a bug standpoint

http://www.ipoffice.tel

 

[tlpeter]

About the bug part you are absolutely right.
Mitel will not get in my dictionary


BAZINGA!

I'm not insane, my mother had me tested!

 

[amriddle01]

I know but you are an ex 3300 man I think, the 5000 is a bit better and more like we are used too

http://www.ipoffice.tel

 

[amriddle01]

Basically ever since Avaya outsourced the development it has been worse than previous GA's and even Maint Releases (perhaps with the exception of 4.0)

http://www.ipoffice.tel

 

[tlpeter]

You are absolutely right.
Outsourcing is never a good idea.
The first thing that goes down is quality.
And my company still does Mitel 3300's

BAZINGA!

I'm not insane, my mother had me tested!

 

[amriddle01]

You will notice in Avaya's price to feature comparisons they do they will compare the IP Office to the 3300 not the 5000 which is actually the system aimed at the same market, they do that so the IP Office looks cheaper, in a comparison to the 5000 it isn't and so they never even mention it

http://www.ipoffice.tel

 

[makinconversation]

Don't mistake me for a Mitel fan, I love the IPO. The change to Mitel would be purely to get the bad taste out of the customers mouth...lol

 

[makinconversation]

If you are having this issue with 9500 series phones, pull off all your bridged appearances and get a t3 with Avaya. This solved my problem until they can build a patch for me. It was rebooting every 10 minutes, now we are an hour out so far with no reboots.

 

[nurban]

I just got the same issue -

<ISI Excep> addr=00000000 d=0 pc=a97e0000

Except the system is only running on POTS so I think this would eliminate the thoughts about PRI being the cause...

Build 7.0(232702)

Only Apps being used are VMPro and ContactStore

 

[makinconversation]

Our issue was a single user had a bunch of bridged appearances. She had a bm-12 on the side of a 9508. They requested her 3 appearances, plus the 3 bridged appearances of 3 other users. 9 bridged appearances on her bm-12. The problem stopped as soon as we removed them, then Avaya built us a patch. It has been reboot free since the installation of the patch. We had to open a T3 and they had T4 build the patch. Hope that helps your case.