Asterisk 1.8 on Debian Squeeze

As we work a lot with Asterisk PBX systems at work, I decided to download and compile the latest version 1.8 on my Squeeze installation (which hopefully will become the new “stable” soon)

1. Create a temporary directory:
mkdir /home/rich/tmp

2. Change to tmp
cd /home/rich/tmp

3. Get the Asterisk 1.8 tarball from here:
wget http://downloads.asterisk.org/pub/telephony/asterisk/asterisk-1.8-current.tar.gz

4. Unpack it:
tar xvf asterisk-1.8-current.tar.gz

5. Get some dependencies that are need for Asterisk and Documentation:
sudo apt-get install libxml2-dev libncurses5-dev doxygen libgtk2.0-dev

6. Compile Asterisk 1.8
./configure
make
sudo make install

7. Install the documentation:
make progdocs

All went schwimmingly!

Time to have a play. 🙂

Advertisements

5 thoughts on “Asterisk 1.8 on Debian Squeeze

  1. For dependencies, please try contrib/scripts/install_prereq
    I suspect that its 'test' mode will be useful.

    Other notes:

    * Asterisk default to installing directly to /usr . Not to /usr/local. Thus it may conflicts with the packaged copy.

    * Core sounds and MoH sounds are packaged. They are installed under /usr/share/asterisk/{sounds,moh} . aptitude search asterisk . This happens not to conlfict with the unpackaged copy.

    * For those more familiar with 1.4: yes, libxml2-dev is required. If you want to avoid it, you'll have to do without the inline help.

    * Doxygen is generally only needed for the API documentation. If you don't intend to write your own Asterisk C code, you probably don't need it (and shouldn't bother with the 'progdocs' target).

    * Libncurses6 will do just fine.

    * If you happen to have Openh323 installed, don't want it, and don't want to waste time on it: ./configure –without-pwlib

    * Just about any other module should be buildable using Debian Squeeze packages. I can't remember now which don't.

  2. Thanks for the feedback Tzafrir.

    Currently at work we are using Asterisk 1.6 in production environments for clients after upgrading from 1.4 as Zaptel didn't work with PRI hardware. Unfortunately although Dahdi is compatible with the hardware, it uses far more processor power than Zaptel did. I saw that with alternative bridging and timing (non Dahdi), 1.8 would probably solve both problems when stable and production ready.

    I only installed 1.8 as a test. In general we don't use anything (or consider it stable) until it has been accepted into the Debian repositories.

    Hopefully we'll see 1.8 in the Squeeze repos once Squeeze goes stable. Being able to work without having to depend on Dahdi will be better for us.

  3. Might also want to remind people to install the build-essentials and dpkg-dev packages. I setup 1.8 last night on Squeeze with unixODBC for RTA. Going to rebuild again from scratch to remove all the crap I don't need.

    Thanks for the info.

  4. That's true. I just thought that anybody who is going to attempt to install Asterisk on Debian would already have build-essential, kernel-headers and dpkg deps already installed. It's not really a newbie type of application.
    Thanks for the comment 🙂

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s