Avaya IP Office Server Edition - 10.0.0.5 build 3 4

[GeekBell]

I'm starting this thread to warn people of upgrading the IP Office SE to 10.0.0.5.

We had a horrible time troubleshooting SIP issues after the upgrade from 10.0.0.4. We thought it was a sip issue and were getting the following error:

481 Dialog/Transaction Does Not Exist

The SIP failures were occuring extremely random. We had checked into EVERYTHING and still could not get it to work. I finally connected another SIP provider to see if I would have the same issue. On a different SIP provider we would get the same results. One phone call would work, then the next 4-5 phone calls would produce a similar error depending on the provider. In my case, the second provider would give us a 404 error when dialing outbound.

Inbound phone calls would work without any issues.

SKIP THIS VERSION and upgrade to the 10.1 version which is a free upgrade instead of the previous versions where the .1 upgrade is a licensed version.

Let me know if you have any questions about this. I'll be glad to provide any additional symptoms / advice.

 

[budbyrd]

If you're into reading the docs, there is a 124 page manual outlining platform security guidelines for R10.

https://downloads.avaya.com/css/P8/documents/101028353

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[GeekBell]

I'm really just trying to let the community know about the bug with SIPs in the 10.0.0.5 Server edition. NOT to get into a security discussion. I don't understand why all of you insist on having a security discussion. If that's what I wanted to discuss, I would open a thread on security so that all of you experts can let us know how to properly secure an IP Office. I hope that this thread will help someone that is struggling with the same issues on 10.0.0.5 and upgrade to 10.1 immediately instead of re-installing the server to downgrade to a previous version as suggested.

I'm almost sorry I opened this thread to make people aware of an actual issue. I didn't know it was going to turn into a security discussion.

 

[Pepp77]

To be fair the first mention of security was by you

| ACSS SME |

 

[intrigrant]

AND i think the way the SIP tunk is programmed may be the root of the problem.
Things evolve continously and so are the SIP trunk features so maybe a config on 10.0 may work fine while the same config on 10.1 may be troublesome.
Talk to Avaya first before stating it is a bug.

 

[IPGuru]

GeekBell

People are discussing security because you made a statement that suggest you may have a fundamental error in the way you have configured your system exposing it to potential hacking

We are trying to help YOU, but if you are not interested that is fine & I sincerely hope that we have misinterpreted your statement & you are not at risk.



Do things on the cheap & it will cost you dear

 

[holdmusic34]

Thanks for letting us know to watch out for it. It sounds like PAI is not being sent on some calls. This issue was originally addressed in 8.1.5

I hate jokes about German sausages.

They're the wurst.

 

[derfloh]

There is also an issue with missing PAI for twinned calls on 10.1. Hope to get a CP soon.

BTW stepping back a Server Edition Linux System in your case is just going into the update section within WebControl and select the option to 'change version' of the IP Office package. So the whole server can stay on SP5 but you can step back the IPO service to SP4.

 

[IPGuru]

interesting twinned calls on my V10.1 SE (demo) seem to work fine - passing on CLI without any issues


Do things on the cheap & it will cost you dear

 

[janni78]

PAI is a bit iffy, it act differently depending on what kinda URI it goes through.

If you have both Diversion Header and PAI it populates different compared to just using one of them.

"Trying is the first step to failure..." - Homer

 

[wrenchmonkey]

Intigrant. Showed some love with the pink because I totally agree with your statement. Everything continues to evolve and it's not always a bug if it doesn't work the way it use to. I'm the first to admit that sometimes Avaya drops the ball on documenting the nuances we find, but that doesn't necessarily make it a bug. If we as a community don't interact with Avaya then nothing gets resolved and we start using work arounds that aren't necessary and may cause future issues.

Yes, this was off topic. No I wouldn't leave a customer down for several hours, much less several days. Yes, I'm done.