Topic: Upgrading Asterisk Verison [Comments: 4]
abongard
Thu, 05/13/2010 - 11:33 | Upgrading Asterisk Verison
We are currently running Centos 5.3 with Asterisk 1.6.0.6 and MTE PBX Manager 6.0.1.81.
Is there any suggestions why we should not upgrade to Asterisk 1.6.2.x
Thank you





Thu, 05/13/2010 - 18:53 | test the release candidate..
test the release candidate.. other versions had something wrong with them. 1.6.7 would randomly declare my sip trunk to my main switch as UNAVAILABLE and wouldnt pass the damn sip traffic until I stopped asterisk, waited 10 seconds and restarted it. Then it worked again for about 7 hours till it repeated the problem. I haven't had that problem with 1.6.2.8-rc1. Anything prior to 1.6.2.7 had some dtmf passthru bugs which might affect your customers and there was an issue where UDP ports werent getting free'd up which was stopping all calls dead in their tracks every 1000 calls.
Erik Smith
CTO
BluegrassNet Voice
dCAP
Thirdlane Support by BluegrassNet Voice
eeman at bluegrassnetvoice dot com
Tue, 05/18/2010 - 13:56 | Upgrading Asterisk
Do you have the "easy" set of instructions to do this upgrade?
Anything else we should know before upgrading from 1.6.0.6 to 1.6.2.8-rc1
Regards,
Andrew
Wed, 05/26/2010 - 18:12 | Is there a simply way to
Is there a simply way to upgrade from asterisk 1.6.0.6 to 1.6.2.8rc1 besides loading centos 5.4 onto a new machine.
Thank you
Wed, 05/26/2010 - 19:27 | building a new box isnt
building a new box isnt neccessary... but the mere fact you're asking indicates you dont understand the fundamentals to compiling and installing code. This means that its a long way away from 'simple'. The ISO did not even include the required -devel rpm's needed to compile asterisk. Whats worse is that if you dont get them all (say the 3 packages required to buid the res_snmp.so module) then you wont have compiled that module yet there was a pre-existing old-version module that is going to try to load and likely cause crashes (legacy wrong version of res_snmp.so for example).
so in short order you have to obtain from yum every devel package needed for each and every already-build module in /usr/lib/asterisk/modules/.
once this is done the standard installation instructions to installing asterisk from source apply (dont do make samples or you will lose your configs)
Erik Smith
CTO
BluegrassNet Voice
dCAP
Thirdlane Support by BluegrassNet Voice
eeman at bluegrassnetvoice dot com