My IP Office Valentine 1

[Spanning]

I vote the ip office the best of its kind, put a side the contant rollout of the new software and bug fixes its got to be my true valentine.

Why because its easy to install and programe and i make loads of money from it, ask the Mrs ?

 

[intrigrant]

?

 

[NuggiFirst]

Sadly, i totally disagree!

Avaya is too focused on introducing new features, but forgets to make the existing ones work!

Some examples:

1. You can queue a call against a user on DND!

2. A queued call never returns to you! Nice when it's parked against a use on DND...

3. You have Voicemail activated on your extension. You are queueing a call against a busy user. After queueing the call you receive another call. The user you have queued against becomes available while youre busy. This sends the queued call to your voicebox! Nice work Avaya And why is this not a bug?!? New feature request ehh..

4. Same scenario as above, except that you don't have VM activated on your extension. In this case the queued call will just be disconnected. According to Avaya this is also not a bug...

Need more examples?!? There's plenty!

 

[andy4uk]

I AGREE??????
Avaya sort IT!!!!!!!!

 

[IPAlot]

Yep, That queueing is a real pain, end up putting groups into OOS or nite service etc to get what you want working and sometims having to recreate call flows for the OOS and nite with new groups .

Soopa Doopa Intergalactic IP Office installation mechanic and configuration corruptor from way back.

 

[Spanning]

Nuggifirst,

The queing problem is being addressed known feature, give me more examples plz.

 

[jtpurcell]

I'm sure there 100's to choose from!

 

[Spanning]

jtpurcell, thats no good , if you have one just say out it loud man ,if highlighted may be it can be fixed.
I challenge you for 100 examples.

 

[Quadnet]

The idea is, for a easy to use/configure.. this system comes out near the top for value and ease of maintenance giving great out of the box functionality.. for small business.. can't say about the larger ones..have no experience with them!

 

[NuggiFirst]

More examples?!?

To be fair to Avaya, i will only post things that have been adressed as "New feature request"

Small Community Networking: When two og more systems are connected in SCN, the following is a classic: A user on site A has forwarding unconditional set to his mobile. A site B user calls the site A extension. The site B system takes the forwarding number, and uses it on it's own CO-lines. Now imagine that the systems are places in different countries... Our customers cannot accept that this isn't sorted right away

DS-phones: When you call a user on DND, the phone will say "busy" in the display. Nice when you are transferring a call! Imagine the caller says he want's to wait on the user: Then you just queue the call, because the phone says the extension is busy.... nice

On a 64xx-phone, you need to program 3 buttons to operate a headset! Even when the phone has a headset-jack

Think i'll stop here! Someone else must have some good examples...

 

[big70]

Every telephone system has his strong points and week points,thats no problem.
The only thing is to now what system to use for what custumor.
The custumor must come first and not the money!!
I see many problems at custumors were they didn,t listen at the custumor and his needs.


Greets Peter

 

[intrigrant]

NuggiFirst, i have two suggestions for you:
1. Go to your customers who have problems with some configuration and both make a financial claim to Avaya, your problems will vanish as snow for the sun....
2. If you are so unhappy with the system why even bother to sell/implement it? Try Cisco, Mitel, Alcatel or whatever system you can sell but do not complain on this forum wich is meant to help each other as engineers/users.

Cheers.

 

[IPmonkey]

Intrigrant your statement below
1. Go to your customers who have problems with some configuration and both make a financial claim to Avaya, your problems will vanish as snow for the sun....
I would be interested to know how many times have you been to avaya for financial compensation and what did you get back? LOL

Quadnet:- this system comes out near the top for value and ease of maintenance. The IP Office system and ease of maintenance don't go together, maybe if you sell a single site basic 403 system with no PM, VM, Soft console then you might have no problems, even the Pot phones have problems with CLI and recall.
Bring back the Index a much better Telephone System

 

[NuggiFirst]

@Intrigant

To your points:
1. My customers get their problems solved! They don't need to make any financial claims to Avaya. But the amount of time used to compensate for these issues...

2. You've got that one right.. I'll just tell the bosses that i'm only interrested in installing Cisco! Beeing an Avaya-only dealer, that would surely do wonders to my personal economy

No, i'm not interrested in moving to another platform. I actually like the concept of the IPO, and I have a hell of a lot of experience on it. I'm just noting that Avaya have moved the focus away from stability, towards new features. I'm not the only one bashing v2.1 in here!
I have only mentioned things that have been logged as feature requests. I have no problem with feature request, but they shouldn't be used on things that are serious bugs! I have not mentioned any registered bugs in this thread, why should I?? That's problems being taken care of. I haven't mentioned any real feature requests either.

Only things mentioned here are things that causes serious problems to the customers, for me, my colleagues, and other companies. Problems which Avaya refuses to see as bugs.

Intrigant, you say this forum is meant to help others! Of course it is. I do help others by pointing these things out, so that people can be aware of them. We could really help each other, if the rest of you logged the bugs that you find serious enough. Besides that, normally I do my best to help other installers in this forum, in a positive way.

 

[intrigrant]

I know you really help NuggiFirst and that is very appreciated.
My reaction is not meant to offence you but more a advise what to do, but unfortunally my english isn't that good that i can say it nicely it seems.
My excuses on that.

And yes, i'm working with INDeX from the start and i am a big fan of this platform, it will take years before the IP Office can reach that level of stability if it will even get that good.
2.1 is a weak version, 2.0 is good and i pray and hold my breath for 3.0, although Avaya did took the time to test it at a lot of sites.

 

[NuggiFirst]

Actually I think we agree on the most of it

Our INDeX-guys constantly reminds me of the good old days, where a system was set up, and you only saw the christmas greeting from the customer...

Avaya is said to work had on the 3.0, to make it as bug-clean as possible. We are also really hoping here :-/

 

[andy4uk]

I agree every system has it's good points and bad points, I started on the INDeX many years ago and always thinking of those good old days!!!!
The IP Office I'm coming around and enjoying working on, The only thing i would change would be on live day with many changes, I then have to tell the customer I'm going to reboot the system? That goes down really well.

Bring on Version 3.0 ??????

P.S i'm still working on the INDeX platform, and still having problems which avaya fix with a new patch!!

There will never be a day when a system comes out and never has a problem, It makes OUR job more interesting.

 

[IPGuru]

Hey I dont wat a system that is 100% perfect, if we ever get one my job in maintanence will cease to exist!

The INDeX is a fine switch but does has had some interesting "features" that required patches to get working ( Many of whic re-apeared in the next new version & needed patching all over again!)

 

[Raffles666]

OK - a lot of people do slate the Avaya software - and rightly so. I remember the good old NA days when too much time was spent on getting VoIP to work than actually getting the correct phones to ring in the correct order!

Avaya seem to have 'acquired' some of these problems - but still have done very little to cure them (perfect example is the users being disabled from groups due to a phone manager bug - which is still in version 2.1.8!).

I used to plead on the old NA-Resellers forum (and the beta testers one prior to that) for telephony issues to be fixed - but all that ever happened was that yet more features were introduced - along with "it's supposed to work like that" problems (eg. you can't send DTMF tones to an incoming call using a 2010 because of the 'dial-ahead' feature).

Yes - the IPO is a great piece of kit when it's working - and when you know it's little quirks. This is true of any phone system though (and I've worked on a few - inluding INDeX).

Here's looking forward to version 3 - and the new 'features' it will bring

cheers



Old school Alchemy engineer - trying to keep up with the times

 

[intrigrant]

You can send DTMF tones for collect calls on 20xx series telephone, just press the "Program" key once during conversation and you can send DTMF tones.
Not every thing is a bug, just ask Avaya.