# Upgrading Asterisk

**URL:** <https://community.asterisk.org/t/upgrading-asterisk/8450>\
**Category:** Asterisk Support\
**Created:** [August 9, 2006, 6:45pm UTC](https://community.asterisk.org/t/upgrading-asterisk/8450 "2006-08-09T18:45:39Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![alta\_skier](https://avatars.discourse-cdn.com/v4/letter/a/9dc877/32.png) [@alta\_skier](https://community.asterisk.org/u/alta_skier)\
**Post date:** [August 9, 2006, 6:45pm UTC](https://community.asterisk.org/t/upgrading-asterisk/8450/1 "2006-08-09T18:45:39Z")

</div>

I have been tasked w/ upgrading our Asterisk server from version  
CVS-v1-0-06 to asterisk-1.2.10,

Can this be done while asterisk is running or do i need to shut it down first.

---

<div class="post-metadata">

**Author:** ![bubbapcguy](https://avatars.discourse-cdn.com/v4/letter/b/eada6e/32.png) [@bubbapcguy](https://community.asterisk.org/u/bubbapcguy)\
**Post date:** [August 10, 2006, 12:29am UTC](https://community.asterisk.org/t/upgrading-asterisk/8450/2 "2006-08-10T00:29:16Z")

</div>

stop it , should only take a few mins…  
You make need to update zaptel as well (really you need to update along the same trunk and all the addons / sounds / libpri at the same time…

---

<div class="post-metadata">

**Author:** ![IronHelix](https://avatars.discourse-cdn.com/v4/letter/i/da6949/32.png) [@IronHelix](https://community.asterisk.org/u/IronHelix)\
**Post date:** [August 10, 2006, 2:10am UTC](https://community.asterisk.org/t/upgrading-asterisk/8450/3 "2006-08-10T02:10:39Z")

</div>

download the new files (asterisk+zaptel, with libpri if you have any PRI’s), untar them

zaptel folder- make clean ; make  
asterisk folder- make clean ; make

(assuming redhat/centos/fedora and you use config scripts)  
service asterisk stop  
service zaptel stop  
zaptel folder- make install  
asterisk folder- make install  
service zaptel start  
service asterisk start

if you dont have the config scripts you can make them with make config.

---

<div class="post-metadata">

**Author:** ![magua100](https://avatars.discourse-cdn.com/v4/letter/m/ba8739/32.png) [@magua100](https://community.asterisk.org/u/magua100)\
**Post date:** [August 10, 2006, 6:18pm UTC](https://community.asterisk.org/t/upgrading-asterisk/8450/4 "2006-08-10T18:18:57Z")

</div>

> > if you dont have the config scripts you can make them with make config.  
> > Where is this done? in the untared Asterisk dir?

---

<div class="post-metadata">

**Author:** ![IronHelix](https://avatars.discourse-cdn.com/v4/letter/i/da6949/32.png) [@IronHelix](https://community.asterisk.org/u/IronHelix)\
**Post date:** [August 11, 2006, 1:32am UTC](https://community.asterisk.org/t/upgrading-asterisk/8450/5 "2006-08-11T01:32:25Z")

</div>

in the untarred Asterisk and zaptel dirs. Keep in mind that you may already have something else starting \* when the machine boots- adding a config script will make that redundant.

---

<div class="post-metadata">

**Author:** ![Helix26404](https://avatars.discourse-cdn.com/v4/letter/h/3d9bf3/32.png) [@Helix26404](https://community.asterisk.org/u/Helix26404)\
**Post date:** [August 11, 2006, 4:11am UTC](https://community.asterisk.org/t/upgrading-asterisk/8450/6 "2006-08-11T04:11:54Z")

</div>

This should work:

wget [ftp.digium.com/pub/asterisk/rele … .10.tar.gz](http://ftp.digium.com/pub/asterisk/releases/asterisk-1.2.10.tar.gz)  
tar -xzvf ./asterisk-1.2.10.tar.gz  
mv ./asterisk-1.2.10 ./asterisk

wget [ftp.digium.com/pub/zaptel/releas … 2.7.tar.gz](http://ftp.digium.com/pub/zaptel/releases/zaptel-1.2.7.tar.gz)  
tar -xzvf ./zaptel-1.2.7.tar.gz  
mv ./zaptel-1.2.7 ./zaptel

wget [ftp.digium.com/pub/libpri/releas … 2.3.tar.gz](http://ftp.digium.com/pub/libpri/releases/libpri-1.2.3.tar.gz)  
tar -xzvf ./libpri-1.2.3.tar.gz  
mv ./libpri-1.2.3 ./libpri

wget [ftp.digium.com/pub/asterisk/rele … 2.3.tar.gz](http://ftp.digium.com/pub/asterisk/releases/asterisk-addons-1.2.3.tar.gz)  
tar -xzvf ./asterisk-addons-1.2.3.tar.gz  
mv ./asterisk-addons-1.2.3 ./asterisk-addons

wget [ftp.digium.com/pub/asterisk/rele … 2.1.tar.gz](http://ftp.digium.com/pub/asterisk/releases/asterisk-sounds-1.2.1.tar.gz)  
tar -xzvf ./asterisk-sounds-1.2.1.tar.gz  
mv ./asterisk-sounds-1.2.1.tar.gz ./asterisk-addons

Then after all of that is done, compile/install:

cd /usr/src/zaptel  
make clean  
make install

cd …/libpri  
make clean  
make install

cd …/asterisk  
make clean  
make install

cd …/asterisk-addons  
make clean  
make install

cd …/asterisk-sounds  
make install

Good luck. This is what I used to update and it worked just fine.

---

<div class="post-metadata">

**Author:** ![facha](https://avatars.discourse-cdn.com/v4/letter/f/71c47a/32.png) [@facha](https://community.asterisk.org/u/facha)\
**Post date:** [August 11, 2006, 10:55am UTC](https://community.asterisk.org/t/upgrading-asterisk/8450/7 "2006-08-11T10:55:35Z")

</div>

Sorry for offtopic. Is there a need to recompile zaptel and libpri every time my kernel is updated?

---

<div class="post-metadata">

**Author:** ![baconbuttie](https://sea1.discourse-cdn.com/asterisk/user_avatar/community.asterisk.org/baconbuttie/32/916_2.png) [@baconbuttie](https://community.asterisk.org/u/baconbuttie)\
**Post date:** [August 11, 2006, 1:44pm UTC](https://community.asterisk.org/t/upgrading-asterisk/8450/8 "2006-08-11T13:44:54Z")

</div>

well, the zaptel modules are stored in the lib/modules/ directory specific to the kernel in use … so yes … change the kernel, you need to recompile zaptel.

it’s never a bad idea to recompile software that uses the kernel headers or sources anyway.

---

<div class="post-metadata">

**Author:** ![whoiswes](https://avatars.discourse-cdn.com/v4/letter/w/dec6dc/32.png) [@whoiswes](https://community.asterisk.org/u/whoiswes)\
**Post date:** [August 11, 2006, 1:57pm UTC](https://community.asterisk.org/t/upgrading-asterisk/8450/9 "2006-08-11T13:57:19Z")

</div>

one thing everyone forgets (and has burnt me more htan once) is to make sure to clean out /usr/lib/asterisk/modules

it’s not required, probably, but it definitely cannot hurt, especially if you’re going from the 1.0 branch to the 1.2 branch…

---

<div class="post-metadata">

**Author:** ![ianplain](https://sea1.discourse-cdn.com/asterisk/user_avatar/community.asterisk.org/ianplain/32/1776_2.png) [@ianplain](https://community.asterisk.org/u/ianplain)\
**Post date:** [August 11, 2006, 6:34pm UTC](https://community.asterisk.org/t/upgrading-asterisk/8450/10 "2006-08-11T18:34:32Z")

</div>

Hi

[quote]it’s not required, probably, but it definitely cannot hurt, especially if you’re going from the 1.0 branch to the 1.2 branch…  
[/quote]

Personaly I think its a must and its a shame its not a better documented must do.

Ian

---

<div class="post-metadata">

**Author:** ![whoiswes](https://avatars.discourse-cdn.com/v4/letter/w/dec6dc/32.png) [@whoiswes](https://community.asterisk.org/u/whoiswes)\
**Post date:** [August 11, 2006, 6:36pm UTC](https://community.asterisk.org/t/upgrading-asterisk/8450/11 "2006-08-11T18:36:31Z")

</div>

hell, couldn’t that be added to the makefile? that way there would be NO question of whether you had deprecated modules loading or not…
