Open Source Training Seminar FreePBX Paid Support

The purpose of this page is to provide some focus on addressing and dealing with some of the 2.3 tickets, where we can discuss and prioritize where it may not be appropriate to add comments to the tickets.

High Priority

  • #2020 - (symlinked agis can fail) This is the symlink issue with includes. Need to understand what is going on and how to deal with this, is it a php config. It has come up at least two times but does not seem to be related to OS specifics. Three now in this latest post. This has become the top priority, for some reason, on the victim system, the agi scripts are running with their env pwd path set to /tmp which makes them fail. It is not clear why. We will have at least a temporary work around for this by the weekend.

    PROPOSED SOLUTION FOR NOW - we have looked at multiple ways to get the proper path to the ag-bin and it involves some unpleasant options of multiple attempts to find php variables that will have the path followed by attempts of hard coded paths. The alternative is to not symlink these, but to hard copy them so we are back to where we were (that is what install_amp does). This is a known working state. Until we can determine a conclusive way of dealing with this, I think we should go this route.
  • #1982 - (depends version checking used by module admin is broken) I ran into this on 2.2.2 when I made some module updates depend on 2.2.2 and even when they had 2.2.2 it failed. Furthermore, they got broken and could not fix once a new module was made available without hand deleting the module. So all this needs to be fixed.

    Related, we need to fix the depends on code to automatically include dependent modules in the upgrade since it will get really tedious and un-usuable when we start using more depends on code.

Direction to Take Needs Decision

  • #1841 - (Can't add + to Direct DID for extension) This happens with providers like bandwidth.com. They send DIDs and CIDs in this format. The issue is if you accept + in the DID (and CID) then you end up with a potential mess, since most people don't yet use the + notation. However, should we restrict them and not allow it? That is the first decision that needs to be made. The next, or related, should we provide a standard "from-trunk-remove-plus" type concept which will remove the + from for DIDs and CID. Not sure what to do on this one.
  • #1961 - (findmefollow problem with extensions 0-leaded) Currently uses int as extension number, should probably use varchar. Same goes for ringgroups (and probably some others?). Should we change this in this release or not? Even if we changed it, do we allow extensions starting with 0, or does this have other undesirable consequences)?
    • Comments by WAudette - IMHO I think we should allow leading zeros as valid extensions as I know that some users have purcahased blocks of DIDs that they tie to their internal extension numbering schema so they match to make things easy on their users. Say someone purchased a block of 200 numbers starting with 503-123-0012 to 503-123-0212 and they want four digit dialing. They would be out of luck w/o leading zeros being allowed.
  • #1487 - (Cannot edit / delete Queue when queue number is 0) Any reason to not allow queue (or extension number) of 0?
    • Comments by WAudette - IMHO Extension zero should be allowed. Queue zero should not. I see no reason to block the use of extension zero as many users already expect that number to take them to the operator.
    • #1659 Has some patches that address this so we will review and probably use these to enable it.
  • #1612 - (Modules should store recording ID - not recording file list) Is this one of those re-architecting things that we should be moving to the next release?

Suggest we Ignore/Delay

  • #1679 - (install_amp creates version.txt on the webroot) Suggest we ignore, push to trunk. It is an easy fix but doesn't hurt anything and not worth the effort to search for now.
    • I have moved this to SVN-HEAD, will address later.
  • #1703 - (Voicemail menu is not hidden when not enabled) This one always bugged me to, but it is en grained in the guielements code. I suggest we address it when that gui code is moved to quickforms.
    • Comments by WAudette - IMHO This seems to me to be a cosmetic issue only. I'd like to see it addressed when the code is moved to quickforms.
Donate



Support
Download
Develop
Forums
News
Documentation
Paid Support
About

Paid Ads