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.

FreePBX 2.9 Gotchas/Answers

Discussion in 'Add-On Install Instructions' started by wardmundy, Apr 19, 2011.

  1. wardmundy Nerd Uno

    This thread covers the changes you'll need to make in PBX in a Flash and Incredible PBX to restore "normal" operation to your system. Please read the entire thread before you attempt to upgrade your server to FreePBX 2.9.

    Please don't post problems here unless you already know the answer and can post that as well. Start a new thread in the Help Forum for problems. When there is a fix, we'll add it below.

  2. wardmundy Nerd Uno

    Eliminating Warning Message for Default Manager Password

    After upgrading to FreePBX 2.9, log into your server as root and edit:

    nano -w /var/www/html/admin/modules/framework/bin/retrieve_conf

    Comment out lines 648, 649, 650, 651, and 653:

    if ($amp_conf['AMPMGRPASS'] == $freepbx_conf->get_conf_default_setting('AMPMGRPASS')) {
    //  if (!$nt->exists('core', 'AMPMGRPASS')) {
    //        $nt->add_warning('core', 'AMPMGRPASS', _("Default Asterisk  Manager Password Used"), _("You are using the default Asterisk Manager  p$
    //  }
    //} else {
            $nt->delete('core', 'AMPMGRPASS');
    Refresh your browser on the FreePBX System Status page after making all the changes to this file to make sure you commented out the correct lines!!
  3. wardmundy Nerd Uno

    Restoring CallerID Superfecta 2.2.4 to Normal Operation

    After upgrading to FreePBX 2.9 on an Incredible PBX or any other PIAF server with CID Superfecta 2.2.4 installed, log into your server as root and issue the following commands:

    Better yet, upgrade to CID Superfecta 2.2.5 which resolves the problem.
  4. wardmundy Nerd Uno

    Permissions Issue

    Upgrading to FreePBX 2.9RC1 gives this notice in FreePBX System Status, under FreePBX Notices:

    Checking ls -l amportal.conf gives:

    root@pbx:/etc $ ls -l amportal.conf
    -rw-r--r-- 1 root root 10332 Apr 20 13:18 amportal.conf

    See also this FreePBX thread: http://www.freepbx.org/forum/freepbx/installation/amportal-conf-not-writeable

    : Log into your server as root and issue the following command:

    amportal chown
  5. wardmundy Nerd Uno

    Restoring Google Voice FreePBX Module to Operation

    WARNING: The original post here was an incorrect patch. See next page for the correct fix.

    Or, a prepatched version that works correctly in FreePBX 2.8 and 2.9 can be downloaded from here.

    See this thread for the source of the incorrect patch. Sorry.

    Google Voice DOES work in FreePBX 2.9.

    Disregard comments below and see next page in this thread for correct patch explanation.

    Open functions.inc.php in googlevoice module. Edit the beginning of the file from:

    to this:

    global $amp_conf;
    // Do we run FreePBX 2.8?
    if(file_exists($amp_conf['AMPWEBROOT']."/admin/extensions.class.php")) {
      // Yes, then include these files
      } else {
            //We are on a FreePBX 2.9 system
    Mikael Carlsson
    FreePBX Development Team
  6. lgaetz Pundit

    Patching Hotel Style Wakeup Calls Module

    Problem discovered by tm1000 and reported in this post.

    Locate this file:
    and delete the final two characters "?>" (without quotes) at the end of the file.

    A proper fix may be a while coming.

  7. jmars New Member

    Any benefit in upgrading to Freepbx 2.9 vs 2.8?
  8. rossiv Guru

    Not that I have seen at all. As you can see in this thread, there are several "Gotchas" with PIAF and 2.9. I would stick at 2.8 now until the kinks are worked out.
  9. tm1000 Schmoozecom INC/FreePBX

    The 'kinks' you speak of are related to third party developers that may or may-not fix their issues. They are not related to freepbx and are technically the result of bad coding.

    Therefore unless the third party developer comes back to fix said modules these issues will keep happening because FreePBX is unassociated with all of the modules above

    I think the feature set for FreePBX 2.9 was pretty outstanding personally


  10. rossiv Guru

    Right - I wasn't trying to say that FreePBX 2.9 itself is bad and bug-ridden or offend anyone- I was saying that when used with PIAF and its pre-installed modules (written by either the PIAF Dev Team or other 3rd Party Contributors), there are some issues that have yet to be resolved without manual user intervention (i.e. editing files). So until those bugs get squashed, I would reccomend staying at 2.8.
  11. tm1000 Schmoozecom INC/FreePBX

    Ok. After consulting with the FreePBX Development team (Mainly only mbrevda) we discovered that this was the incorrect way to patch this module

    The correct way is to replace lines (20-34) with this:

    global $amp_conf;
    // Do we run FreePBX 2.8?
    if(file_exists($amp_conf['AMPWEBROOT']."/admin/extensions.class.php")) {
      // Yes, then include these files
      } else {
            //We are on a FreePBX 2.9 system
    function googlevoice_hookGet_config($engine) {
    	global $ext;	
    	if (!method_exists($ext, 'ext_senddtmf')) {		
    		class ext_senddtmf extends extension {
    			var $digits;
    			function ext_senddtmf($digits) {
    				$this->digits = $digits;
    			function output() {
    				return 'SendDTMF('.$this->digits.')';
    class googlevoice_conf {
    I've attached the CORRECT functions.inc.php for google voice in this thread.


    Attached Files:

  12. Gotenks New Member

    FreePBX 2.9 with CID Superfecta

    Also see here for another solution: http://pbxinaflash.com/forum/showpost.php?p=69315&postcount=77
  13. wardmundy Nerd Uno

    Symlink Error

    If you experience a symlink error after the upgrade, see this thread for the fix.
  14. wardmundy Nerd Uno

    The new patch (at the top of this page) for the FreePBX Google Voice module now has been incorporated into new installs of PIAF-Purple and PIAF-Red. Without this patch, the previously provided patch blew CallerID Superfecta out of the water on FreePBX 2.9 installs and upgrades.
  15. wardmundy Nerd Uno

  16. You are very quick to point fingers, are you Wardmundy. It turned out to be googlevoice 0.9 that was to blame.
  17. wardmundy Nerd Uno

    I'm going to repeat this one more time, mickecarlsson...

    When we find things that aren't working or when other folks report things that are not working, we document it for all of our users and also ask the person finding the problem to report it to the appropriate party. IT'S NOT A MATTER OF POINTING FINGERS! IT'S THE APPROPRIATE WAY TO GET ISSUES IDENTIFIED AND RESOLVED.

    As for FreePBX 2.9, we personally like it; however, there have been numerous reports of problems (see the previous 17 posts). We have tried to document the issues and work through them as they arise with the able assistance of people like you. However, for first-time users, this can be an incredibly frustrating experience if there's nowhere to turn for documented information on how to address or avoid the gotcha's.

    Let's work through the issues respectfully and professionally... and lighten up on the personal stuff. Thanks.

    As for the Recordings issue, loading the current fix to the Google Voice Module resolves the issue. Was it your earlier patch to the GV module that actually caused the problem, or am I missing something?? The SVN link to 0.1.1 is here. Can't find a tarball link.
  18. One post about a problem, and you blame FreePBX 2.9 when it actually was a third party module that was faulty. Equal as to the other 17 posts, all related to modules outside of FreePBX Developers control.

    I did read this thread and I have a few comments:

    You teach users to edit out code (IMHO a very BAD approach) in FreePBX instead of fixing your distro. This is not a FreePBX problem. I have even mailed you a solution to this, why don't you fix that? We do it in our distro.
    Every framework we push out break this "fix".

    The post about the problem with Superfecta, not a FreePBX problem.

    Your third post: (sorry, I edited out this reply, you would not have liked it at all)

    I suggest that you rename the thread to Multiple problems with Third Party Modules in PIAF with FreePBX 2.9, that would be a more appropriate title.

    If you want to document and actually helping users and developers, document this:

    Third Party Developers, please use the following tag in module.xml for your modules that don't support FreePBX 2.9:
    If all developers for Third Party Modules followed this, none of the above post had been necessary.

    You can read all about module.xml here: http://www.freepbx.org/trac/wiki/module.xml

    After they have updated the module, they can change the tag to:
    They can even add two depends:
    The above example would only allow the module to be installed on FreePBX 2.6, 2.7 and 2.8

    Take care,
  19. wardmundy Nerd Uno

    You Break It, You Fix It. I Break It, I Fix It...

    We could probably have this discussion until the cows come home, but since you brought it up, let's address it. I've been around and around with the Asterisk developers on this same subject.

    My position is and always has been the same. If a new version of code (in this case FreePBX) breaks existing modules regardless of who wrote them, the primary responsibility for documenting the changes (SO THAT THE THIRD-PARTY APPS CAN BE FIXED) lies with the person(s) that broke the existing code. It's unreasonable to expect any outside party to wade through hundreds of thousands of lines of code looking for what's been "improved." Sorry.

    And blocking old apps from being installed is not a fix! This is particularly true in the case of major modules such as Google Voice, CallerID Superfecta, and EndPoint Manager which are used by hundreds of thousands of end-users. They are the reason FreePBX has been able to make a business case for continuing development!

    There have been very few new versions of FreePBX that broke existing code of third-party developers. I've been through dozens of upgrades. FreePBX 2.9 is an exception thankfully.

    The module.xml link you provided doesn't provide the first clue as to what has been changed in 2.9, how those changes affected existing third-party modules, and what steps could be taken to get these modules working with 2.9. Somebody knows!

    Finally, if it hadn't been for tm1000 and Moshe Brevda, the transition to FreePBX 2.9 would have been a disaster for most end users. I hope the FreePBX Development Team will reconsider what appears to be a new approach to software development.

Share This Page