Avaya wisdom 2

[teletechman]

I opened a ticket for an SBC that I am having issues with connecting Android phones to and Avaya said that the release of the SBC is not compatible with the version of the IPO. see the list I have made to see if this makes sense or if it is Avaya's wisdom?
IP Office 11.1.2 SBC 8.1.3
IP Office 11.1.1 SBC 8.1.1 or 8.1.2
IP Office 11.1 SBC 8.0.1 or 8.1.3 or 10.1 or 10.1.1
IP Office 11.0.4 SBC 7.1, 7.1.1, 7.1.2, 7.1.2, 8.1, 8.1.2, 8.1.3
IP Office 11.0 SBC 7.1, 7.1, 7.2, 7.2.1, 7.2.2, 8.0, 8.0.1, 8.1, 8.1.1, 8.1.2, 8.1.3, 10.1, 10.1.1
I was told be TS that I needed to downgrade my SBC because I have a IPO R 11.1.1 and an SBC R10.1.
Avaya is pissing me off with stuff like this all the time.
Mike

 

[sizbut]

Their list is utter rubbish, ask them where they got it, ie. an actual link to a published document. R11.1.1 is a later version of R11.1, it would support later versions of SBC, not fewer and older versions! Ditto for IP Office R11.1.2.

Stuck in a never ending cycle of file copying.

 

[teletechman]

I got this from the Avaya compatibility website, this is what is causing me the most grief when dealing with TS. The fact that they have little to no idea what their products will do or what they can be used with.
Mike

 

[derfloh]

Let's work on your issue. I sent see the incompatibility. Nevertheless, the latest 8.1 of SBC and the largest 11.x of IPO fixes eine issues.

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

 

[jamie77]

SBC is public facing device. Surely it should be on the latest version possible?

Not how how the SBC version can cause any issues with the IPO.

Typical Avaya support over the last 2-3 years. Avoid fixing anything. Delay until you get bored. Produce crap realses when they can be bothered.

Example. I've a ticket open currently becuase the call direction is wrong on SMDR when answering a call on MS Teams. Nice simple on. Chcuk it to dev and get me a CP, and put it in the next SP. Nope. 6 weeks or messing about getting irrelavent traces. Confirmed as a bug and told it will be in the next SP. IN SEPTEMBER!! Nope, go get me a CP. That was last week!

And I'm still waiting for a proper fix for the Teams direct routing (loggin in December). sip-all.microsoft will be retired next month and it will all fall over when that happens.

Jamie Green

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

 

[daken]

Great Thanks Jamie77

Just when we have deployed it, its going to stop working
[URL unfurl="true"]https://support.avaya.com/ext/index?page=content&id=SOLN369323[/url]