IP 500 Units

[mattKnight]

Anyone had problems with the IP 500 units - specifically the PSU dying.

We've installed 4 or so and at least 2 have died after only 2 months.

Just wondering...

Take Care

Matt
If at first you don't succeed, skydiving is not for you.

 

[tlpeter]

i have one running now for 2 months or so
first 6 weeks at the office and now at the customer
no problem at all for now
maybe bad luck or it went hot ?
it could be possible that theinternal power supply makes it hotter inside that with a 406 or 412 ?
i don't thing they changed the PSU


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!

 

[ProviderReborn]

Had a couple which kept rebooting like a power loss. Showed the same in monitor. That was a dodgy PSU and was swapped out.

 

[jamie77]

Ours in the office has been fine since March.

Got one on site, been running for about 4 weeks with no issues (apart from SIP!!!!!!!!)

I hope your wrong about the 500's. Our sales is only quoting or 500's now. We wonder about the life span of the 406 and SOE (and 412?!?!?!) so we are only going to be installing 500's.

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!!!!

 

[mattKnight]

I hope your wrong about the 500's

Me too! From the quick straw poll no-one else seem to be having the same problems. So either we are doing something wrong or we've just had a couple of "friday Afternoon" IP500s

As for the the life span of the otehr kit - You raise an interesting point. At its base configuration, the 500 is cost comparable with the SOE. Licensed for Professional use, it is certainly as good as the 406 (I don't know about price) The only advantage that the 412 has is 12 expansion ports...

I suspect that the life of the other units is limited, but probably 18/24 months...
We'll see!

Take Care

Matt
If at first you don't succeed, skydiving is not for you.

 

[kwing112000]

we have alot of 500's out there and have not had any issues with them yet. They have been out for a while and i have not had any power supplies go bad.

 

[mattKnight]

Thanks very much all

We must have just got 2 bad'uns...

Take Care

Matt
If at first you don't succeed, skydiving is not for you.

 

[justinrphillips]

Our first 500 is having major issues. Calls are droppingl, and phones are rebooting every day.

 

[tlpeter]

That has nothing to do with a PSU (or the complete system must die)
It can be bad programming
it can be bad network

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!

 

[justinrphillips]

Tier 3 along with a network assesment has ruled out networking and our programming has been given a clean bill of health. I am reaching now.

 

[tlpeter]

that good to know

what does SSA say ???
is your ip500 grounded ?


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!

 

[aarenot]

Hey Justin,
You might want to check out a few things which I have found from other techs implementations which were having weird issues. Unless you are starting from scratch yourself which makes it your implementation, you cannot know if the system was properly upgraded in it's firmware, so you must downgrade, then re-upgrade the system from the original factory installed firmware to the release you intend to use. I would not recomend any shortcuts, it takes an extra 3/4 hour to upgrade through every major release, but then I have never had to DTE a system either so I think it is worth the time. Also, none of my implementations have ever had any serious issues either, and I think that may have something to do with it. Proper upgrading of firmware is something you can only be sure is done, if you do it yourself from my experience.

Other items:

1 Grounding
2 Power issues, brown power, or short interuptions.
3 Channel banks (Adit 600 being the worst) can cause many issues with drops, and with not recognizing ringing. I can probably fix this with a Telco vendor meet consult.
4 Only use the factory provided patch cords between IPO expansion modules, and proccessor.
5 Make sure all the modules are on the same release of firmware, as well as the VMPRO on the same level as well.
6 Do not run AV, or firewall during install of Avaya software, firmware upgrades, transfer of application files, or testing of the system.
7 Do not rely on distributor tech support personel to be able to give your CFG's a clean bill of health. They are tech support, not field engineers, and thus have less experience than most field engineers. They listen to your issues, and look at the list of possibilities for those issues, not at experiences in most cases. Most of the time in calls to them I have solved the issue during the support call, or while waiting in Q without their help, or after they have given up by trial and error. They simply offer advice which is 95% of the time things I have already tried. The biggest thing they have done for me is to offer me a patch for the firmware, or to refer me to Avaya T3.
This is true of at least two of the distributors I have dealt with for IPO support.

Avaya tech support is better than this, but T4 is where they really seem to have some consistant personal experience in the field level application of the IPO. A good field tech, and T4 really work together on the issue as peers, this is true of some T3 tech support as well.

Before any distributor, or Avaya support people take offense, this is just my experience, and not indicitive of all distributor or Avaya tech support personel. I have found some to have much knowledge, and experience. I am speaking of levels where it seems to be a given that the support will be at that level, not a hit and miss depending on who you get on the phone thing.