Avaya IP Office 11.1 Feature Pack 2 Service Pack 3 14

[Johnhyde]

Having lots of issues with 11.1.2.3, yes having issues with the One-X Portal, Web Manager, Web Control, Voicemail Pro, ACR, memory leak on IP500V2...many more issues... I have around 25 SR open with Avaya!

Really Avaya needs to bring back beta testing at least they can hopefully stop some of these bugs before releasing.

With the amount of time I've spent collecting logs, and replicating the issues I may as well be working for Avaya fault finding all the issues they could not be bothered to test.

 

[IamaSherpa]

I totally agree with you @Johnhyde and you have to be certified and pay IPOSS to do that... that's crazy!

 

[BFG9K]

All this is solidifying our decision to move away from Avaya. I came in very late to the party (2018) but even then I could see how Avaya gave zero shits about IP Office and it's ecosystem. When COVID hit there wasn't any push to get IP Office integrated with anything like MS Teams or Slack, and even now getting MS Teams connected to IP Office requires an SBC and manually setting up SIGMA scripts. It took me 3 hours to configure MS Teams with IP Office, while it was a checkbox on 8x8.

Avaya have done their best to move people away from them and it's all coming to a head now. Businesses don't want to pay stupid prices just for Power User Licenses, note to mention the cost of Server Edition licenses. They weasel all the money they can out of you, and when the shit hits the fan the Avaya engineers know LESS about the product than I do!? We literally lost a (huge) client this year because of ongoing issues with ACCS and IPOSE. Avaya support had no idea how to fix it and eventually the client stopped talking to us, and then advised they were going with another vendor as Avaya has been such a headache and they want something that just works without babying it all the time.

Avaya screwed the pooch and now they can't recover. I'm a little sad over it but no more than see Nortel die.

Hopefully the future is a bit brighter, I am so sick of seeing good ideas being destroyed by greed and incompetence.



Cheers,
BFG9K
Avaya IPO/ACCS Technician
Melbourne, Australia

 

[hostedguru]

lol not been on hear for a while cant be-leave people are still installing ip office like the previous poster said the future is hosted been installing hosted now for 10-15 years and never looked back

 

[CMUK]

@hostedguru Hosted not for everyone, a lot of my customers like to own their hardware and not have a subscription service. Cost of ownership for an IPO is much better on a lease for my customers and the Avaya/RingCentral offering is not something we will be partaking in.



Calum M
ACSS

 

[AvayaRed]

We were discussing if IPO is going to EOS when the Ring Central partnership happened in 2019 and we were complaining then how buggy it was then.

I guess they just do not want to continue development/support IP Office and want everyone to go to Ring Central. IP Office is not EOS but with this amount of bugs, it is clear they do not do any quality testing to make sure it works before making it GA....

 

[BFG9K]

I am expecting the IP Office line to be sunset over the next two years. It's obvious Avaya want it to go away in favor of subscriptions to ACO/RingCentral, and the GA releases have been really declining in quality over the last few years and I always talk to the same support engineers, so it's obvious that they only have a handful of people working on it.

Just a few I remember for the past few releases:
[ul]
[li]Attempting to re-create an SD Card using Manager would fail halfway and leave you with an unusable card due to a file that was 0KB in size[/li]
[li]Upgrading Server Edition via normal ISO method would erase your configuration entirely, licenses and all. Had to build a brand new machine on the new version and migrate the config[/li]
[li]Memory leak in One-X Portal service that would slowly eat up all your RAM, issue persisted over 5 releases[/li]
[li]Web Management writing enormous cache files over time and entirely filling up the disk[/li]
[li]VMPro mailboxes filling up even though they are set to forward to email only (This was never and will never be fixed)[/li]
[li]Faulty J100 firmware causing a site-wide outage on a Monday morning[/li]
[/ul]

And let's not even talk about ACCS, I would rather shoot myself than ever have to set up a new customer's flows on ACCS ever again. After having used a current-year Contact Center Admin interface, it's like watching a Blu-Ray 4K movie on a 70" OLED panel after being stuck with a VHS and CRT TV combo from 2002.

Cheers,
BFG9K
Avaya IPO/ACCS Technician
Melbourne, Australia

 

[Johnhyde]

I don't think IP Office will go EOS, they just made IP Office subscription available to everyone (even in Ringcentral areas) previously in UK IP Subscription was not available unless an SBR is raised or Avaya involvement, now is available to all.

Some interesting new features in 11.2, especially the SBC-less deployment and teams integration/O365

Although I expect none of them to work properly and break previous working features!

 

[IamaSherpa]

Thank you @Johnhyde eventhough (TBH) we are talking about R11.2 since then, no scheduling (for what I know) and we are still waiting R11.0 SP8, may be they will wait to release R11.2 up to Jan/23 when the R11.1 SP4 should be released?

 

[derfloh]

Do you have details about 11.2?

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[Johnhyde]

I believe 11.2, 11.4 SP4. 11.0 SP8 will be released end of Jan 23 (but don't hold your breath on that!)

I have some details on 11.2, these were sent to me by our Avaya account manager.

 

[derfloh]

Can you share those details?

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[liquidshokk]

Is anyone else seeing DTMF issues in 11.1? We upgrade to 11.1 a couple of months back as advised by Avaya to fix a completely different issue and straight away DTMF wasn't recognised by any external auto attendants. Logged an SR and was advised to switch to Inband DTMF which "fixed" it for 80% of auto attendants but some still completely ignore any options chosen. Gamma say it is because we aren't sending payload 101, which makes sense as we aren't using RFC2833. So it seems we either have to get Gamma to only send DTMF as inband or wait until Avaya sort their lives out??

Surely we can't be the only business to have suffered this since upgrading?

 

[jamie77]

They’re a DTMF issue in one of the earlier 11.1 builds. Might have been 11.1.1 GA, can’t recall.

Patch was released and permanent fixed in next SP.

If you use the latest 11.1.2 you won’t have this issue (but you may have others!!)

Jamie Green

[bold]A[/bold]vaya [bold]R[/bold]egistered [bold]S[/bold]pecialist [bold]E[/bold]ngineer

 

[IPOtek101]

Using Manager, switch it to Inband, save and make live.
Pull a new config new minutes later and switch back to RFC2833 = bug.
Webmanager does not fix the issue.

Monitor with SIP Verbose logging can help see what's going on
Below are response from IPO regarding what it sees
HandleSDPContext: found_rfc2833 with payload 101
HandleSDPContext: No RFC2833 in the message, use inband DTMF

 

[PeluIPO]

Hi guys,

I have the same issue with DTMF that liquidshokk described earlier on IPO 11.1.2.3.

Does anybody solve this DTMF issue on SIP trunks?

Also I see that today was published 11.1.2.4 but there is no release notes for that. Does anybody already installed it.

 

[Travis Harper]

I just installed 11.1.2.4

So far so good... I can't wait to read the release notes.