INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Jobs

Avaya IP Office Server Edition - 10.0.0.5 build 3

Avaya IP Office Server Edition - 10.0.0.5 build 3

(OP)
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.

RE: Avaya IP Office Server Edition - 10.0.0.5 build 3

did you report this to Avaya

RE: Avaya IP Office Server Edition - 10.0.0.5 build 3

(OP)
No I did not report it to Avaya. The customer was down for several days while we are waiting for Avaya to "gather logs from the system." This has been my experience with Avaya and their support. They will "gather logs" and chew them for several days and make you wait. In the meantime, the customers are getting upset that they can't run their business. I have yet to have a successful support experience with them. Especially when it's a critical system down emergency.

RE: Avaya IP Office Server Edition - 10.0.0.5 build 3

The few times I reported a critical error I've had a tech connected within an hour collecting log.

In this case since your issues started after an update I would collect logs, downgrade to solve customers issues and send the logs to Avaya and wait for a CP.
Why would you wait days for Avaya in this case?
If it took more than 2 hours I would hit the escalate button which usually results in a manager calling you.

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

RE: Avaya IP Office Server Edition - 10.0.0.5 build 3

Another Question
What was your reason for upgrading from 10.0.4?

one odf the biggest rules in maintenance is "If it ain't broke don't fix it"

upgrade only when :-

1)
your customer is experiencing an issue that you cannot resolve (It will be the first thing avaya ask you to try anyway)
2
the new software has an additional feature that your customer needs (& is willing to pay for )


Do things on the cheap & it will cost you dear

RE: Avaya IP Office Server Edition - 10.0.0.5 build 3

Like a friend of mine always says
The enemy of good is perfect
Had that bite me a few times when I tried to perfect something and broken it instead.

Joe W.

FHandw, ACSS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter

RE: Avaya IP Office Server Edition - 10.0.0.5 build 3

(OP)
The original reason we upgraded is because the Server Edition would suddenly not work at all and the only thing that would resolve it is rebooting. Again, Avaya support "gathered logs" and chewed on them for several days while the customer gets more and more upset with the situation.

As we have experienced in the past with the IP office nodes in the past, Avaya doesn't seem too concerned with security and has 0 measures in place to prevent attacks.

RE: Avaya IP Office Server Edition - 10.0.0.5 build 3

What are you saying?
You have IP Offices with public IPs or that are accessable from the internet?

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

RE: Avaya IP Office Server Edition - 10.0.0.5 build 3

(OP)
What I am saying is that there is definitely a bug in the most recent 10.0 version for outbound SIP traffic. My intent is to make the community aware of the situation to avoid upgrading to that version.

RE: Avaya IP Office Server Edition - 10.0.0.5 build 3

So what do bugs have to do with security?

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

RE: Avaya IP Office Server Edition - 10.0.0.5 build 3

My Server Edition has been running for 90 days, no issues.

RE: Avaya IP Office Server Edition - 10.0.0.5 build 3

(OP)

Quote (rdoubrava)

My Server Edition has been running for 90 days, no issues.

Are you running 10.0.0.5 Build 3 using SIP trunks?

RE: Avaya IP Office Server Edition - 10.0.0.5 build 3

Seeing that 10.0.5 came out on September 11th (9 days ago) I would think that rdoubrava runs an older version.

I have some server editions with SIP trunks on 10.0.3 that were installed months ago without issues so it may be some other external reason why you have these issues

Joe W.

FHandw, ACSS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter

RE: Avaya IP Office Server Edition - 10.0.0.5 build 3

I'm still interested in what he means with this comment =)

Quote (GeekBell)

As we have experienced in the past with the IP office nodes in the past, Avaya doesn't seem too concerned with security and has 0 measures in place to prevent attacks.

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

RE: Avaya IP Office Server Edition - 10.0.0.5 build 3

We run our hosted system on 10.0.0.3 which is SIP only and have had zero issues. Maybe there is a problem with SIP on 10.0.0.5, if so downgrade to .3 and all will be good :)

| ACSS SME |

RE: Avaya IP Office Server Edition - 10.0.0.5 build 3

(OP)

Quote (Pepp77)

We run our hosted system on 10.0.0.3 which is SIP only and have had zero issues. Maybe there is a problem with SIP on 10.0.0.5, if so downgrade to .3 and all will be good :)

They SIP functionality seemed to work good until we upgraded to .5. Have you been able to downgrade a Server Edition without reinstalling and restore? I couldn't find a reasonable method of downgrading.

Quote (janni78)

I'm still interested in what he means with this comment =)
I don't want to get into a discussion about Avaya's security. Too easy to hack unless you completely finger pick the routes.

RE: Avaya IP Office Server Edition - 10.0.0.5 build 3

Downgrading is documented in the Knowledgebase

http://marketingtools.avaya.com/knowledgebase/businesspartner/ipoffice/mergedProjects/SE_Deployment/_frame2.html?Downgrade_Policy.html?zoom_highlight=downgrade

Any PBX is easy to hack, that's why you have security appliances handling communication between them and the rest.
I've never finger picked a route and apparently managed to not get hacked, although I have cleaned up a lot of installations from other dists.

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

RE: Avaya IP Office Server Edition - 10.0.0.5 build 3

(OP)
janni78

You obviously did not read the link you sent, nor are you following the thread. But, appear to just want to demonstrate your security expertise. The knowledgebase states:

6.You can perform a Minor Linux server downgrade by performing a complete reinstallation and re-ignition.

As my question states above:
"Have you been able to downgrade a Server Edition without reinstalling and restore? I couldn't find a reasonable method of downgrading."

complete reinstallation to me is NOT a reasonable method of downgrading.

RE: Avaya IP Office Server Edition - 10.0.0.5 build 3

I followed the thread, you first informed about issues you had after upgrading to 10.0.5.

Then you stated that you didn't report this as Avaya Support since you haven't had any success in the past, which means that the bug will stay unless someone else reports it.
Then suddenly you brought up their lack of interest of security which kinda made me curious.

Might not be reasonable to reinstall, but since you state your customer was down for days I would rather have reinstalled and restored from backup.

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

RE: Avaya IP Office Server Edition - 10.0.0.5 build 3

Quote (Geekbell)

I don't want to get into a discussion about Avaya's security. Too easy to hack unless you completely finger pick the routes.

It is NOT easy to hack if you have installed it correctly, which is which Janni asked "You have IP Offices with public IPs or that are accessible from the internet?"

an IPO should always be behind a firewall & not directly accessible from the internet.
to secure sip if your ISP required ports forwarded to the IPO (Most don't) then the forwarding should be restricted to only known IP Addresses or use a SBC.

if you have IP Office systems fully visible on the internet then you are both incompetent & grossly negligent & should cease installing IPO's until you know better.



Do things on the cheap & it will cost you dear

RE: Avaya IP Office Server Edition - 10.0.0.5 build 3

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/10102...

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

RE: Avaya IP Office Server Edition - 10.0.0.5 build 3

(OP)
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.

RE: Avaya IP Office Server Edition - 10.0.0.5 build 3

To be fair the first mention of security was by you :)

| ACSS SME |

RE: Avaya IP Office Server Edition - 10.0.0.5 build 3

2
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.

RE: Avaya IP Office Server Edition - 10.0.0.5 build 3

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

RE: Avaya IP Office Server Edition - 10.0.0.5 build 3

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.

RE: Avaya IP Office Server Edition - 10.0.0.5 build 3

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.

RE: Avaya IP Office Server Edition - 10.0.0.5 build 3

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

RE: Avaya IP Office Server Edition - 10.0.0.5 build 3

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

RE: Avaya IP Office Server Edition - 10.0.0.5 build 3

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.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Resources

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close