Thirdlane.com logo

Preferred version of 1.6.x?

Posted by fuse3 on Wed, 03/09/2011
Forums
Thirdlane platform General Questions

I have a box running 1.6.2.13 that is having a problem that eeman detailed in a prior post:

“beware of another bug I've seen occur on 2 MTE installations sofar. Randomly a reload command will result in a locked state where asterisk does not finish the reload and no further calls will process. The only solution is to force a restart of asterisk. If you notice your calls stop working and phones wont register remember this solution”

I am looking to resolve it and im looking to a “newer” version of 1.6.2.??

Anyone running a version later than .13 that they have had success with?

Thank you

Submitted by eeman on Thu, 03/10/2011 Permalink

later versions are unstable as hell. except .14 and .16 but that bug persists. You need to revert to .11 until that bug gets resoloved. Now that its proven it does not occur on .11 but does in .13, it should be only a matter of time. I know someone paid for digium support and opened an internal ticket on it.

Submitted by fuse3 on Wed, 03/16/2011 Permalink

looks like a downgrade to 1.6.2.11 is on my todo list for the night
almost afraid to look at the list of fixes from that build forward :(

Submitted by moshe on Wed, 03/30/2011 Permalink

Erik
Any update with digium fix for the reload issue

fus3
Any major bugs on 1.6.2.11 to be aware of

This reload issue is killing me

Any comments will be greatly appreciated

Submitted by eeman on Wed, 03/30/2011 Permalink

I asked the customer the other day if digium fixed it but I think they've gotten complacent. I also wonder if 1.8 is immune from the problem. I saw an issue with 1.6.2.11 somewhere on this forum but its not nearly as frequent as the reload hanging issue. It seems to really get bad on systems that have over 1000 handsets. Just about 1 in 3 reloads will lock the system up.

obviously there are serious bugs that were fixed later on including 6 chan_local fixes that caused crashes, dtmf issues, etc. Theres also a few security fixes that went in that were being exploited for denial of service. In latest branch code there is finally a fix for RFC2833 on SONUS switches.