1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. If you had a PIAF Forum account in the vBulletin days, log in with your old credentials. Otherwise, sign up again and we'll get you back in business as soon as we can.
  3. A serious FreePBX vulnerability has been reported. Update your Framework Module immediately. Click here for details.

Asterisk 1.8.7.1 Now Available

Discussion in 'Today's Tech News & Events' started by darmock, Jun 1, 2011.

Thread Status:
Not open for further replies.
  1. darmock PIAF Developer

    As of December 09, 2011 @ 1630 EDT *UPDATED*

    CURRENT ISO VERSION

    1.7.5.7.1 Both 32 and 64 bit versions are available. It is recommended you only do new installs with this ISO and destroy any earlier ones.


    CURRENT PAYLOAD VERSIONS NEW INSTALLS

    The list below is the default version of Asterisk that PBX in a Flash distributes. In other words when you do a NEW install from OUR ISO (Which is the only supported way) and choose one of the menu choices these are the versions you will get installed by DEFAULT

    PBX in a Flash Gold


    Asterisk 1.4.21.2
    Asterisk Addons 1.4.13
    Libpri 1.4.11.5
    Zaptel 1.4.12.1


    PBX in a Flash Silver

    Asterisk 1.4.43
    Asterisk Addons 1.4.13
    Libpri 1.4.12
    Dahdi 2.5.0.2+2.5.0.2


    PBX in a Flash Bronze


    Asterisk 1.6.2.21
    Asterisk Addons 1.6.2.3
    Libpri 1.4.12
    Dahdi 2.5.0.2+2.5.0.2


    PBX in a Flash Purple

    Asterisk 1.8.7.2
    Libpri 1.4.12
    Dahdi 2.5.0.2+2.5.0.2


    PBX in a Flash Red *THIS IS CLASSIFIED AS BETA BY THE PBX IN A FLASH DEV TEAM!*
    Asterisk 10.0.0-rc2
    Libpri 1.4.12
    Dahdi 2.5.0.2+2.5.0.2

    You can also install SOME previous and a newer version of PIAF-Purple using this syntax from the command prompt: piafdl -p beta_1871. Below are the only versions supported using the -p flag for new installs. If you don't know what this means, read this Nerd Vittles article first!

    1832
    1833
    184
    beta_1841
    beta_1842
    beta_1843
    beta_1844
    beta_1850
    beta_1860
    beta_1870
    beta_1871 *NEW Default install is 1872*

    UPDATE-SOURCE - EXISTING INSTALLS

    You can update existing version of Asterisk in the same family by using the EXPERIMENTAL update-source program. You cannot upgrade between families! Thus you CANNOT upgrade between Asterisk 1.4 to 1.6 or 1.8, etc.

    The file located in /etc/pbx/digiumsource.conf controls versioning and can be changed to upgrade or downgrade.

    In order to use this program you must specify the version you want to use WITHOUT the beta_ preface! Thus in order to install Asterisk 1.8.7.1 you would change

    PASTERISK="asterisk-1.8.7.2" and NOT PASTERISK="beta_1872"

    NOTE this program is EXPERIMENTAL!

    Finally, FOR THE TRUE PIONEERS: If you'd like to experiment with the latest SVN release of Asterisk, this thread will show you how.


    What does 1.7.5.7.1 MEAN?

    The version number refers to the INSTALLED ISO VERSION ONLY! It has nothing to do with the actual versions of the programs we have created.

    thus for the current ISO

    1.7.5.7.1 =

    1.7 = The Pbx in a Flash Version. The next version is 2.0

    5.7 = The version of Centos. Then next version of centos is 6.0

    .1 = This is the release version of the ISO only. Sometimes the ISO's are updated when new rpm's or kernels are available.


    PBX in a Flash Development Team
  2. eCase New Member

    Hey Darmock/ Ward:

    1) Do we edit the /etc/pbx/digiumsource.conf file prior to running update-source, or before?
    2) Are we supposed to run amportal stop or stop any other services on the server before editing this file?
    3) I installed PIAF PURPLE using the -p flag to install webmin and Asterisk 1842 - but when I checked the /etc/pbx/digiumsource.conf file, the lines not commented out with a # show:

    LIBPRI="libpri-1.4.11.5"
    SOUNDS="asterisk-core-sounds-en-gsm-1.4.21"
    SNDEXTRA="asterisk-extra-sounds-en-gsm-1.4.11"
    DAHDI=dahdi-linux-complete-2.4.1.2+2.4.1
    FPBX="freepbx-2.8.0"

    ZAPTEL="zaptel-1.4.12.1"
    GASTERISK="asterisk-1.4.21.2"
    GADDONS="asterisk-addons-1.4.13"

    SASTERISK="asterisk-1.4.42"
    SADDONS="asterisk-addons-1.4.13"

    BASTERISK="asterisk-1.6.2.19"
    BADDONS="asterisk-addons-1.6.2.3"

    PASTERISK="asterisk-1.8.4.1"
    PADDONS="asterisk-addons-1.6.2.3"

    4) I have FREEPBX 2.9+ installed, along with Asterisk 1842 - but this file indicates otherwise. Is this something that should keep me up at night?

    [OT] I've had a terribly hard time trying to integrate an Asterisk sounds package with better quality than GSM - I'm trying to use alaw or ulaw (I forget which). Is this a task that is better done at a fresh install, or can it be integrated into a current system?

    Thanks guys!
  3. darmock PIAF Developer

    Depends what you are trying to do!

    digiumsource.conf is used by update-source only.

    the current version of this file indicates the stable releases to use with PIAF.

    You edit it to move to a different version of purple using update-source.

    this has no effect on a new install

    You dont have to use amportal stop to edit this file as it is only accessed when update-source is being run

    Using the -p flag means you are specifying a new install version digiumsource.conf has no effect as it is not used by the install-pbx program

    This file is not updated when you update freepbx as it is not used by freepbx <quit worrying>. If and when fpbx 2.9 is supported as the base install then this entry will change. This is used to indicate what the original installed version of freepbx was used.

    The default is gsm for audio. You can change this by hand compiling asterisk and selecting the relevant packages

    cd /usr/src/asterisk
    ./configure
    make menuconfig

    <you will see a screen come up and if you scroll down you can do whatever you want. Be warned that making incorrect choices here can cause asterisk to not compile correctly>

    make

    make install


    good luck


    Tom
  4. wardmundy Nerd Uno

    Asterisk 1.8.5 is now available in new PIAF installs. See first post in this thread for how it works and how to upgrade. :wink5:

    [IMG]

    [IMG]
  5. wardmundy Nerd Uno

  6. OTA Guru

    Odd... I just installed PiaF about an hour or so ago and received 1.8.4.1. Using a fresh ISO off SourceForge. Oh well. I'll reinstall and see what happens. I'd hate to run update-source on a brand new system.

    Update: At 6pm ET, I'm watching PiaF install... it just DL'd 1.8.4.1.
  7. darmock PIAF Developer

    from nerdvittles.com

    Changes in PBX in a Flash Distribution. In light of the events outlined in our recent Nerd Vittles article and the issues with Asterisk 1.8.4, the PIAF Dev Team has made some changes in our distribution methodology. As many of you know, PBX in a Flash is the only distribution that compiles Asterisk from source code during the install. This has provided us enormous flexibility to distribute new releases with the latest Asterisk code. Unfortunately, Asterisk 1.8 is still a work in progress to put it charitably. We also feel some responsibility to insulate our users from show-stopping Asterisk releases. Going forward, the plan is to reserve the PIAF-Purple default install for the most stable version of Asterisk 1.8. As of June 1, Asterisk 1.8.4.1 is the new PIAF-Purple default install. Other versions of Asterisk 1.8 (newer and older) will be available through a new configuration utility which now is incorporated into the PIAF 1.7.5.6.2 ISO. Here's how it works. Begin the install of a new PIAF system in the usual way by booting from your USB flash drive and pressing Enter to load the most current version of CentOS 5.6. When the CentOS install finishes, your system will reboot. Accept the license agreement, and choose the PIAF-Purple option to load the latest stable version of Asterisk 1.8. Or exit to the Linux CLI if you want a different version. Log into CentOS as root. Then issue a command like this: piafdl -p beta_1841 (loads Asterisk 1.8.4.1), piafdl -p 184 (loads Asterisk 1.8.4), piafdl -p 1833 (loads Asterisk 1.8.3.3), or piafdl -p 1832 (loads Asterisk 1.8.3.2). If there should ever be an outage on one of the PBX in a Flash mirrors, you can optionally choose a different mirror for the payload download by adding piafdl -c for the .com site, piafdl -d for the .org site, or piafdl -e for the .net site. Then add the payload switch, e.g. piafdl -c -p beta_1841.
    [IMG]


    So there is a new BETA build of asterisk. If you want to participate with these experimental builds then follow the information in the above text. The current Official Build for asterisk is 1.8.4.1. If you want to use 1850 then on a fresh install piafdl -p beta_1850 will do the trick


    Tom
  8. tbrummell Guru

    That kind of conflicts what Ward posted above...
  9. OTA Guru

    At least I'm not the only one who saw/thought that. I see they've changed the first post to show 1.8.4.1 as the correct version.
  10. tbrummell Guru

    Hmmm, I see that now too. It did say 1.8.5 would be used on new installs, which I thought was kind of strange since it was just released. Anyway, I've upgraded to 1.8.5 and it seems to be working fine so far.
  11. wardmundy Nerd Uno

    Ooopsy. Got too excited. :crazy:
  12. darmock PIAF Developer

    Stuff happens. Too little coffee or sleep wires get crossed sometimes....The whole dev team tries to review each others post to ensure accuracy. Don't worry be happy.

    We were lucky to notice it at all as the dev team is deep into Centos 6 at the moment. So thanks for letting us know.

    Tom :nukeb:
  13. Fala New Member

    I load Asterisk 1.8.5 with the results shown above, with the exception that instead of "VIRTUALIZED", mine shows "HARDWARE". The problem I'm having is I cannot get any of my Extensions to Register with my PBX Server. I'm using both an SPA-3102 and SPA-2102 ATA.

    After running IncrediblePBX and using extensions 701 and 704, with the same password for each extension, the extension registration failed. I'm using the default values for the extensions, with the password as the only change! Could someone point me in the right direction as to what might be causing this. I had no problems with a previous install using the same hardware and ATA. Thx.
  14. darmock PIAF Developer

    The virtualized or hardware moniker depends if you are running PIAF on a real machine or inside a virtualization environment.

    As for the incredible Ward is MIA for a bit so hopefully someone else will speak up. That being said You really need to start a new thread in the help forum with your problem and not hijack this one please. In the new thread read this post and include the relevant information as requested http://www.pbxinaflash.com/forum/showthread.php?t=10022

    Your best bet is to post in the help forum.


    Tom
  15. womble1 Guru

    it looks flaky to me just upgraded and although the status application say's it's OK intact if you look on freepbx system status Asterisk is down.
    No calls either.. so the terminal status application is reporting the wrong status…
    Which is odd… !
    Wondering if I should down grade….
  16. wardmundy Nerd Uno

    Works fine for us. Open a Help thread and post info about your setup.
  17. lgaetz Pundit

    This sounds a lot like what I dealt with on an install 2 days ago.
  18. sukasem Guru

    I'm no expert here but I think I have this problem when I install 1.8.4 a month ago and also ASTERISK server show FAILED on FreePBX but STATUS show ONLINE. IIRC, 70X extension has permit/deny address in extension config and also check iptable (try changing the line with port 5060 from WHITELIST to ACCEPT). If it solve the problem then you have ptoblem with the whitelist like me and have to create one and change it back from ACCEPT to WHITELIST.

    BTW. Uncle Ward, Could you add some instruction about Whitelist/iptable in your article on NerdVittles.

    Cheers,
  19. wardmundy Nerd Uno

  20. darmock PIAF Developer

    A number of updates have been pushed out today.

    1. Added support for Centos 5.7 to all programs. There were some interesting gotchas with 5.7 which took a couple of days to iron out.

    2. Updated purple default version of Asterisk to 1.8.6.0

    3. Added support for beta_1870 to various programs

    4. Update-fixes now contain the latest gv patches. If they are required they are added if not you are notified.

    5. PBX in a Flash 1.7.5.7.1 - Beta ISO's have been created and extensively tested. Both 32 and 64 bits have been uploaded to our private server. Ward will make the official announcement as to where and when they are available. Please dont bug Ward or the Dev team as we are slaying dragons at the moment and excessive emails may delay the release of the ISO's This is to simply notify you that we have been working on it and have finished it. The first ISO are 17571 and they are NOT marked beta as we hope that these will be the final release ISO's.

    6. In order to better support AASTRA phones most of the required php modules are now installed automatically on new installs.

    7. Added support for PBX in a Flash 1.7.5.7 to all programs.

    8. Updated various notification screens on all programs.

    Everything is available now EXCEPT the ISO's. If you use an older 1755 or 1756 ISO you will till get Centos 1757 installed and install PBX in a Flash 1.7.5.7 HOWEVER you will NOT be running the true Centos 5.7 Kernel. If you require the features of the latest kernel during you new install please wait until the new ISO's are officially released.

    If there are bugs to report please start a new thread.


    Tom
Thread Status:
Not open for further replies.

Share This Page