Skip to main content

Safety of Upgrading to Asterisk 1.8

Posted by eskimogroup on Sat, 11/06/2010

I am currently running Third Lane MTE with Asterisk 1.4. I was wondering how safe it would be for me to manually upgrade to Asterisk 1.8. Please inform me of any possible pitfalls that could result.

Thanks.


Submitted by klalletti on Sun, 11/07/2010 Permalink

I tried it, but wouldn't recommend it.

I've been experimenting with my first ThirdLane roll-out, and that was my initial test target.

ThirdLane + Fedora 14 + Asterisk 1.8 running on an ESX4 Host.

Reason for Fedora14 above CentOs is the kernel that's above 2.6.25 which allows for Asterisk 1.6.x / 1.8 to use res_timerfd which is a -much- more precise clock source than the previous ones.

As for the 1.8 experience; strangely the voicemails didn't work, and I was getting a lot of asterisk-manager connection warning messages. I would say that the usability is 90% there.

I backtracked to Asterisk 1.6.2.13 and its working perfectly!

Hope it helps!
Cheers

Submitted by eeman on Mon, 11/15/2010 Permalink

I just tried it on MTE 6.1.1.6 .. strangely the problem I had was my sip proxies running siproxd were crashing on transfer.

calls worked fine until one phone did an attended transfer to another phone and suddenly siproxd would segmentation fault. Downgrading to 1.6.2.14 resolved the issue. I hadnt noticed a voicemail problem mentioned before, but almost all my clients use sip proxies so this is a deal-killer until we can figure out if this is a bug or a feature. My initial thought is that the new callerid feature they included in 1.8 is causing the crash (I know they were working on a way to update callerid on connected calls so that attended transfers would show the callerid)