IP Office Reboots on its own..

[nekau]

Our IP 406 V2 rebooted today for no apparent reason. The error message in Monitor was:

ALARM: 14/05/2007 16:20:17 IP 406 DS 3.2(55) <TLB Data Error> CRIT RAISED addr=000004c3 d=13 pc=ff6a2cb8 00000001 ff8043e8 ff7fc56c ff7fc6cc ff7c33f4

IT also happened almost exactly a month ago.

Does anyone know how to decipker these very cryptic messages?

 

[jamie77]

Check config for errors.

See if a particular user rings a particular number once a month!!!

Long shot!!!

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

http://www.alliedcom.co.uk

Fooball is not a matter of life and death-It is far more important!!!!

 

[mforrence]

I have a customer had rebooted several times since upgrading to 3.2.55. Avaya provided a private build - hasn't rebooted since (if you have wood nearby, please knock upon it).
Mike

 

[gknight1]

I knocked for you mforrence!

 

[nekau]

Any way I can get that private build.

I have a case open with my vendor, and have been waiting 2 weeks for fixes to several issues:

IPO Rebooting
ICLID incoming truncated to 4 digits
Static and calls dropping

The system is an absolute nightmare.

I would not recommend anyone going down the IPO road unless Avaya gets it together soon.

 

[tlpeter]

nekau the ipo ofice is a good system
every system that is bad programmed is not good.


ACA - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[nekau]

The programing on our IPO is according to the Avaya documentation.

Comments made here should not be taken personally.

The fact is there are so many outstanding issues in the 3.2.x software release that are causing many businesses major headaches, that the cost of maintaining these systems is climbing. This is a business issue.

All you have to do is look through the forums, and that is obvious.

I don't doubt that certain loads of software have work better than others, in my previous job, I has 6 412 units running older versions of code that were solid. The later code is not good.

 

[janni78]

You can't measure the stability of the IPO based on this forum. I have a bunch of systems running on 3.2 software fine. I'm not gonna sit here and write daily how good the work.
Forums is the place to take up problems, and therefore if you base your oppinion on that you'll think the software is buggy.
Fact is that most of the time something goes wrong it's beacause of programming issues, even though it's programmed by the book.
But this discussion ain't old, it comes up every time that remark is said so enough about that

 

[PlatinumGuy]

Im going to interject here, i dont want to labour the point so ill be brief.

Any software has bugs, FACT.

Its just if you find them or not.

 

[nekau]

Well put. Enough said.

 

[gknight1]

where are you, maybe you should look for a different vendor?

 

[nekau]

I'm in Canada, but I am dealing with a company in NY.

We recently made a large purchase from them, based on my recommendation that the IPO was a very good product based on my previous experiences.(Pre 3.2)

Moving to a different vendor is probally not possible now.

It is quite frustrating though, because I know others are getting interim releases of code that are fixing issues that can't wait for the quarterly maintenence releases.

 

[tlpeter]

sometimes a single upgrade that is done wrong can mess up a complete good working system
whe can discuss this for years but it won't help
all brands have there own problems
every pbx in these days run on software and they will all have there problem
the bugs that are found are all found because no manufacture has the time to test there software for a long period
they could do it for a longer while but don't


ACA - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[bigjerms]

They need to stop beta testing at the customer level.

I've seen many private builds in a short peroid of time.

It can't be the person programing the IP Office that is doing the bad programming if Avaya has to release a private build to resolve the issue. Its Avayas programming that is at fault in this instance.

 

[aarenot]

I have worked on 100 plus IPO's, not a huge number, but more than a few. Of the systems I have programmed I have had no major issues, but I have learned how to avoid a few.

The systems others have programmed, I have helped with on here, or elsewhere looking through the configs has always shown some programming errors. The size, as well as the quantity of errors can either cause issues. Even Avaya does not always catch all the programming errors, as I know from having sent CFG's to them early on in working with the IPO when I had systems I needed help troubleshooting.

Also, the book is very vague, does not spell out how to do everything, and therefore in many situations I can think of 10 different ways to accomplish something. For instance, time profiles in the IPO, or schedules in the VMPRO, which should you use? Now of the ten ways I mentioned, 7 suck in performance, the remaining three combined have less issues than the previously mentioned 7. The third has an issue once a week, the second has an issue once a month, the first has not had an issue reported. None of these I mention have anything programmed in a way that the book says you can not do things, but some ways are still better than others.

Of the ones which I seem to not be able to fix the issue, 4 needed a PB, the rest needed either a new piece of hardware, or downgrading the IPO, and then re-upgrading it fixed it. Other issues were sub-standard VMPRO servers, or application servers being used, etc. All 4 which needed a PB were very taxed systems running advanced applications, not your simple systems, ones with CCC, IMS, etc, and a unique probably not run into situation in the trials.