Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

9.0.3?

Status
Not open for further replies.

telecotek1

Vendor
Nov 13, 2007
390
US
Stable? What's everyone's take on this software. Is everyone using this code at this point? Trying to squash a random reboot issue.
 
reboots arent random. something causes it.

what does your monitor trace show?

ACSS - SME
General Geek

 
I couldn't agree with you more...

Here's what I have

alarm in sysmon says ISI Exception CRIT RAISED....

In the actual Sysmon trace...

09:03:48 915704862mS PRN: .FATAL ISI Exception address=00000000 d=5 pc=00000000 f155f068 f155f0f4 f0857f70 f0858ad8 f0858d6c IP 500 V2 9.0.2.0 build 860

This system has several 9608's with Bridged appearances. I had read that
some people were having reboot issues with bridged appearances on IP Phones
 
if you have iliminated all other causes & think you have a bug in 9.0.2 you really have 3 options

1) report to Avaya via IPOSS ;-)
2) Downgradde to V9.0.1
3) Upgrae to 9.0.3 this is the first thing avaya will ask you to do anyway

from the above I woudl sugest upgrading & see what happens


A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear
 
I've had the same issue with bridged appearances casuing restarts in 9.0.3 so upgrading probably will not fix your issue. It is currently with Avaya in the IPOSS gimme logs, traces and configs queue, and after a week goes by they will request more logs, traces and configs.
 
@biv343 Do your traces look like mine? wonder if that what my issue is.
 
Not quite the same as what I was seeing. I was showing segmentation violations at address 00000000 as the termination cause.
 
I hear IPOSS is doomed....

Careful what you wish for - something about the devil you know versus the one you don't.

I really think Avaya needs to dump anyone associated with the IPOSS debacle, though.
 
Off topic, but I fortunately have not had to submit anyone to IPOSS coverage. Yet. What is the debacle?

NTS Direct
 
OK City personnel are rude and arrogant (people from outside the USA may not have to experience this).

How can Avaya expect to succeed with a culture like this? I thought it could be me (I can be abrasive) but when my customers call me to reinforce these perceptions then I know it's not me - and Avaya is wrong, clearly wrong, and needs to change.

Times they are a changin' - get with it Avaya.
 
I had the same problem with bridged appearances also on 9.0.3. If a phone had a bridged appearance on it and put a called on hold it caused the system to reboot. Avaya was able to provide me a patch for it that resolved the problem. I also heard about this happening with line appearances as well.
 
I'm having a reboot issue with two R9.0.3 systems as well. I haven't been able to isolate the cause yet however. It happens about once a week on a system with 60 users and the system with 210 users reboots every 2-3 days. It seems to be somewhat common with R9.
 
It seems to be common in 9.0.3
We run the 9.0.2 version and it does not reboot as long as i don't screw around with it :)


BAZINGA!

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

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top