Asterisk 1.4 and Asterisk 1.6.2: End-Of-Life Approaching

By Kevin P. Fleming

Well, it’s almost here. Asterisk 1.4 was released in December of 2006, and was later deemed the first ‘Long Term Support’ release of Asterisk, when that policy was put in place. Nearly a year ago, when it was 4.5 years old, Asterisk 1.4 entered the ‘Security Fix Only’ support mode, which means that we began actively encouraging people to base new installations on Asterisk 1.8 (the next Long Term Support release). At the same time, the End-Of-Life (EOL) date for Asterisk 1.4 (and Asterisk 1.6.2) was announced.

Now, as we approach April of 2012, those EOL dates are just around the corner. As of April 21, 2012, there will be no more releases made of Asterisk 1.4 or Asterisk 1.6.2, even if security vulnerabilities are identified. If you are using systems based on either of these release branches of Asterisk, you should consider moving to a supported release as soon as you can practically do so.We hope that this change won’t cause you any undue anxiety or inconvenience. However, should you be concerned, note that this change will occur only one day after 4/20, so feel free to relieve your anxiety in advance, if you wish!

For more information about the Asterisk release branch release dates and lifetimes, see the Asterisk Versions page on the Asterisk Wiki.


Related Posts

There Are 7 Comments


    please help me

    after installing asterisk server…every package installed properly but i showed on my browser………….. please suggest me

    Not Found

    The requested URL was not found on this server.
    Asterisk Server
    on terminal status is good,,,,,,,,

    [email protected]:~/asterisk- sudo make checkconfig
    — Checking Asterisk configuration to see if it will support the GUI —
    * Checking for http.conf: OK
    * Checking for manager.conf: OK
    * Checking if HTTP is enabled: OK
    * Checking if HTTP static support is enabled: OK
    * Checking if manager is enabled: OK
    * Checking if manager over HTTP is enabled: OK
    — Everything looks good —
    * GUI should be available at http://ubuntu:8088/asterisk/static/config/index.html

    * Note: If you have bindaddr= in /etc/asterisk/http.conf
    you will only be able to visit it from the local machine.

    Example: http://localhost:8088/asterisk/static/config/index.html

    * The login and password should be an entry from /etc/asterisk/manager.conf
    which has ‘config’ permission in read and write. For example:

    secret = mysecret3153
    read = system,call,log,verbose,command,agent,config
    write = system,call,log,verbose,command,agent,config

    — Good luck! —

  • says:

    Asterisk PBX: La guía en español paso a paso.


    Diseñe e implemente soluciones de Voz sobre IP completa o integre su sistema PBX tradicional con Asterisk. Incluso si sus conocimientos de telecomunicación son básicos esta guía es fácil, le muestra paso a paso como instalar, configurar y administrar sus sistemas telefónicos basados en software libre Asterisk.

    ver mas información

  • Ray says:

    Hello Guys,

    We have Asterisk and Elastik as the GUI configured on our PABX and we use Polycom phones. We need to implement a feature that can pause and resume call recording.

    For a example, when an agent is in a call with a customer and he has to take the customer’s credit card details like the CVV number, the agent must have the ability to pause the call recording and resume the recording after the customer has given the credit card details. This can be done through DTMF signal. We are looking for a solution to implement this feature on Asterisk. Although I have seen that this is possible via the documentation presented on the Internet with regards to Asterisk, I have been unable to get this to work. It either crashes my configuration files or the changes don’t make any effect. We are looking to see if we can find someone with more extensive experience working with Asterisk that can solve this problem for us.

    Please help.


  • Jehanzaib says:

    Hi Ray,
    Ask the agent to Park the call and here you can stop the recording using stop monitor in the diaplan or using AMI. This could also be easily done if you just make a simple web interface to stop the monitoring on an agent’s channel.

  • Manoj says:

    Hi Team We need Asterisk Support for incoming call issue.

    I have a Asterisk Server with Centos OS . I have mapped Asterisk with SIP Trunk when customer dialed on my Pilot number i.e SIP-Trunk number its get connected with my asterisk server that’s means incoming calls patched successfully. But some time or some fraction of time some callers can’t connect with my server (unable to make call on my PRI) if they called it from mobile witin 1 second calls disconnect and if they called from Landline or pstn it’s say Dialed number doesn’t exist .Please check the number’ after some time means 30 to 40 second its working fine .
    Please suggest me what should I do

  • maiya says:

    Dear All,

    Kindly any one could let me know about how to get started with asterisk, as I am very new to this, and i’m planning to do “1 to many” call center project. Immediate answer it would appreciate. Thanks in advance.

  • john says:

    having this problem for the few days , please help me out ???

    [[email protected] ~]# cd /usr/src/dahdi-linux-complete*
    [[email protected] dahdi-linux-complete-2.10.2+2.10.2]# make all
    make -C linux all
    make[1]: Entering directory `/usr/src/dahdi-linux-complete-2.10.2+2.10.2/linux’
    make -C drivers/dahdi/firmware firmware-loaders
    make[2]: Entering directory `/usr/src/dahdi-linux-complete-2.10.2+2.10.2/linux/drivers/dahdi/firmware’
    make[2]: Leaving directory `/usr/src/dahdi-linux-complete-2.10.2+2.10.2/linux/drivers/dahdi/firmware’
    You do not appear to have the sources for the 2.6.32-042stab106.4 kernel installed.
    make[1]: *** [modules] Error 1
    make[1]: Leaving directory `/usr/src/dahdi-linux-complete-2.10.2+2.10.2/linux’
    make: *** [all] Error 2

Add to the Discussion

Your email address will not be published. Required fields are marked *