Milestone 2.4

FreePBX 2.3

• Extension Registry
  • See ExtensionDestinationRegistries
  • Implement call-back mechanism and API to determine if any module is using an extension
  • Create API to produce all extensions being used in the system
  • Update all existing modules to make checks before creating duplicate extensions
• Destination Registry
  • See ExtensionDestinationRegistries
  • Implement call-back mechanism and API to determine if any module is using oneself before allowing deletions
  • Update all existing modules to make checks before deleting an instance used elsewhere as a destination
• Custom Apps Module
  • Module that allows custom destinations and custom extensions to be registered in the registries
  • Purpose is to expose custom dialplan that FreePBX would not otherwise see
  • Helps get full view of system's integrity to avoid conflicts with custom code
• Languages
  • Create Language Module to allow language changes as calls flow through a module chain
  • As part of extension module, add Language attribute to extensions/users
• Paging & Intercom
  • Improve paging / intercom to work properly with users & devices
  • Extend paging module to work with broader set of phones by addressing some of the hardcoded strings
  • Put hook into paging/intercom to allow for custom handling of devices not handled in module
  • Add default page group, and ability to designate extension/device to group at creation/edit
• Module Admin
  • Improve situation where dependencies keep other modules from being downloaded/installed
    • Ideally allow download of modules if the dependent modules are also included in list of downloads/installs
    • At least download/install the ones that are not problematic and skip the dependent ones
    • Any fix here should be considered for backport to 2.3 if simple enough
• Change Zap Channel routing to provide DIDs for channels
  • Trap zap channel as today, assign the given did, send to ext-did where a did should be available
  • This will allow all inbound routing to be handled the same way
  • Migrate by creating DIDs in the form of zapchan_nn for existing channel routes and then converting the channel routing record to that DID
• Fix Adhoc Devices to handle hints properly
  • Generate hints in extensions_additional.conf based on astdb state
  • Update hints dynamically during login/out
  • Come up with a solution to address CLI initiated reloads which can result in stale data
    • Can look at #exec in extensions.conf? Has some issues
    • Can require reload to be initiated through FreePBX or equivalent CLI command to address hints
    • Solution is to have amportal.conf DYNAMICHINTS variable which then has #exec inserted into ext-local
• Update Queue Module to get rid of legacy extensions table usage
• Update Queues and Core (sip, zap, iax) to remove generate_configurations scripts
  • used to be old PERL scripts (retrieve_conf_from_mysql scripts)
  • replace with core_conf class and queues_conf class
• Add option to Queues to have occupied phones be ignored regardless of CW setting
  • requires core changes in dialparties.agi
• Move vmblast contributed module in supported module
  • requires significant work to bring it up to par, what was there never worked, was very poorly written
  • enhance with announcement and optional password
  • add default vmblast group with ability to include extension/user at add/edit time
• Add Limited Support for a DUNDi trunk~
  • add a DUNDi trunk type. No support to generate the dundi.conf file but once configured, provide support to integrate branches into the dialplan