|
|
Roadmap
-
System & Core Modules
New MenuSystem?? to take advantage of module categoriesModuleDependancies / requirements Greg Rocks.GuiStyles?? (e.g. A@H, Dev, Home, SOHO, etc.)
o does this refer to CSS layout/colors or the type of interface (basic/advanced/expert) shown?
Trunk / Routing Improvements (TimeConditionsChange, ProvisioningModule, ???)Investigate PossibleUseOfAjax? Ajax is nice, but I don't think we can do it yet
o I may use AJAX to do reload, it will actually make the interface simpler (since reload is in footer - so it's after all processing - having HTML elements BEFORE footer (the reload code) requires using javascript to show/hide them).
Modules
CallScreeningAndBlacklistingSpeedDials- QueuesModule?? re-write (move away from 'extensions' table + numerious bugs now logged (#1119 ..? ))
VoicemailModule -- functionality to be split out from core
-
Many of the targets for 2.3 are incremental steps to 3.0
Online Update SystemCore Modules to Online SystemFreePBX Framework to Online SystemAutomatic Update Checking and reporting
Asterisk 1.4 SupportAdd notification frameworkAllow warnings such as default password to be registered in one placeAllow critical failures (e.g. retrieve_conf failing) and similar to be logged and prominently displayedAllow available updates to be prominently displayed
Add crontab style frameork/managerUsed by the online update checker- modules like backup should move to using this framework
config.php, header.php, header_auth.php, footer.php cleanupconsolidation and improvement of amportal.conf parsermove to all components using one parser with common defaults, etc.FreePBX, retrieve_conf, module_adminremove parsing from agi-scripts by supplying conf settings into dialplan for phpagi access
Improved installation processadd auto install of packaged modules
Remove all known hardcoded pathsStyling and Logo Faceliftimprove the use of CSS in the process
New Admin Index PageDashboard style system status / overviewconsolidated location for notifications
- Sqlite3 support
FOP ChangesLatest version 0.27Configurable in amportal.conf to run/not runamportal options to start/stop/restart FOP only
Core/Framework Changes & Additions to Support Feature workNew ringgroup/followme strategiesARI Control of Followme & VmX Locater
Core/FollowMe Destinations Merge and ChangeMerge core extensions and followme destinations so they work just like dialing an extension in the systemMake 3 new categories for destinations:ExtensionsVoicemail (with both unavail and busy for each extension)Terminate Call (for destinations like zapateller, hangup, busy, ...)
Day/Night Mode ModuleMisc Feature Work
-
FreePBX 2.3
Extension RegistrySee ExtensionDestinationRegistriesImplement call-back mechanism and API to determine if any module is using an extensionCreate API to produce all extensions being used in the systemUpdate all existing modules to make checks before creating duplicate extensions
Destination RegistrySee ExtensionDestinationRegistriesImplement call-back mechanism and API to determine if any module is using oneself before allowing deletionsUpdate all existing modules to make checks before deleting an instance used elsewhere as a destination
Custom Apps ModuleModule that allows custom destinations and custom extensions to be registered in the registriesPurpose is to expose custom dialplan that FreePBX would not otherwise seeHelps get full view of system's integrity to avoid conflicts with custom code
LanguagesCreate Language Module to allow language changes as calls flow through a module chainAs part of extension module, add Language attribute to extensions/users
Paging & IntercomImprove paging / intercom to work properly with users & devicesExtend paging module to work with broader set of phones by addressing some of the hardcoded stringsPut hook into paging/intercom to allow for custom handling of devices not handled in moduleAdd default page group, and ability to designate extension/device to group at creation/edit
Module AdminImprove 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 channelsTrap zap channel as today, assign the given did, send to ext-did where a did should be availableThis will allow all inbound routing to be handled the same wayMigrate 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 properlyGenerate hints in extensions_additional.conf based on astdb stateUpdate hints dynamically during login/outCome up with a solution to address CLI initiated reloads which can result in stale dataCan look at #exec in extensions.conf? Has some issuesCan require reload to be initiated through FreePBX or equivalent CLI command to address hintsSolution 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 usageUpdate Queues and Core (sip, zap, iax) to remove generate_configurations scriptsused 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 settingrequires core changes in dialparties.agi
Move vmblast contributed module in supported modulerequires significant work to bring it up to par, what was there never worked, was very poorly writtenenhance with announcement and optional passwordadd 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
-
FreePBX 2.5
The following is a summary of new features that are part of the 2.5 release. There are many Feature Requests that are not on the list below but have been included, you can filter by Feature Request on the right and review what has been included.
- Introduce the optional use of func_devstate to many features. This is an Asterisk 1.6 feature with a very stable 1.4 back-port available. This allows manually setting BLF status allowing very flexible use of programmable buttons. Features to be targeted for this include:
- DND
- Enable/Disable Follow-Me
- Possibly Call Forward
- Day/Night Modes Buttons
- Conference Rooms
- Merge directdids into inbound routes
- Allow basic directdid info to be set in extension/user as today
- Use inbound routes to set all advanced information
- add view filtering on incoming to display only directdids, all but directdids, unassigned or everything
- Inbound routes ability to have a CID only route take precedence over a DID only route if a call comes in with that DID. (Today the DID only will always take precedence)
- Ability to define a different set of default feature codes from those hard-coded in each module, to facilitate localization related needs
- Follow-Me - add a feature code to enable/disable
- Ring Groups - add Skip Busy Agents and feature to Ignore Agent CF settings
- Caller Screening - caller recorded call announcement/confirmation per user
- New Queue Priority Module, allowing call flows to set higher priority for calls prior to entering a queue
- New DUNDi check module, detect and block extension conflicts across a branch office cluster, do lookups on defined routes in branch office cluster
- Auto-transcode support to MoH uploads form MP3 to wav linear formats in MoH module
- Add ticket/changeset links to Module Admin Changelog display
- Merge naftali5's original timegroups module and timeconditons changes (#774, #1695) into timeconditions
- Adds the ability to create time groups with multiple times per group
- Time conditions are then linked to a time group
- Time group will be usable by other modules, see TimeConditionsChange
- Daynight / Timeconditons Modules Integration
- Allow a daynight feature code to be directly associated with one or more timeconditons (not timegroups) so that the condtions can be overridden with that featurecode without the need to setup call flows. (And providing more capability such as a single daynight feature code that could override multiple timecondtions at once.
- Restrict Agent Callback numbers that can be entered for dynamic queue agents
- To address #2876 - putting bogus feature codes into a queue callback
- To provide the more generalize ability of restricting what numbers can be entered for callbacks, for example if you would like only extensions 3000-3999 or if you want to keep from putting external numbers, or a specific set of extensions to be allowed.
- Add feature codes to individual system recordings for easy editing (#2899)
- Allow Modules to be hidden in Module Admin GUI
- Add VmX configuration to FreePBX GUI (previously only in ARI
- Misc GUI touch up and navigation aids
- tabindex for for more logical tabbing
- various add/edit/delete icons
- improved links between related entities (e.g. users/devices)
- Recordings usage change to ID throughout modules
- Change DISA to allow multiple calls to be made once connected, and modify to use authenticate to create a more usable DISA
- Get remaining changes in to provide full sqlite3 support
- IVRs allow alternative messages to be played after timeout/invalid extension scenarios
- Queues
- have the caller's wait time prepended to the CID option
- queue weights configurable
- autofill per queue configurable
- persistentmemebers set so dynamic agents are not lost on a restart
- option not to try any additional members if the first one fails
- Significant performance enhancements to page load times by improved caching of XML module data and other streamlined changes to improve quietmode access often used by ajax calls
- MoH add ability to set Streaming Music Categories in addition to downloaded file directories
- Fix remaining localization issues with gettext so that the current i18n implementation works properly everywhere (featurecodes was one sore spot, Module's also need to be able to provide their own translations for things like the left navigation bar).
- Compatibility Mode for DAHDI support, to allow current Zaptel configurations in FreePBX to run auto-magically when DAHDI is used once an appropirate dahdi.conf file has been configured. The ability is non-destructive, reverting back to Zaptel continues to work.
- Introduce the optional use of func_devstate to many features. This is an Asterisk 1.6 feature with a very stable 1.4 back-port available. This allows manually setting BLF status allowing very flexible use of programmable buttons. Features to be targeted for this include:
-
FreePBX 2.6 - Some Highlights
- Added Extended Repository to allow more contributed modules not part of main project, some extended modules include:
- Bulk Extension Add/Delete/Edit
- Bulk DID Add/Delete/Edit
- Voicemail Admin
- Set CID
- Route Permissions
- Custom Contexts
- Moved the following modules to the extended repository:
- Customer DB
- Inventroy DB
- Gabcast
- Added new modules:
- Asterisk SIP Settings
- Asterisk IAX Settings
- Outbound Route Messages
- Phone Restart
- Weak Password Checks (back ported to 2.5 also)
- Several Enhancements to Queue Module
- Enhancements to Print Extensions
- Performance Enhancements to Paging (helps large page groups)
- Added Virtual Extension support
- Added Pinless Dialing exception to Extension/User GUI
- More improvemenmts to Directed Call Pickup for Asterisk 1.4+ systems
- New version of mindTerm (used in Java SSH module); has new licensing options (and restrictions). See http://www.appgate.com/index/products/mindterm for more info.
- Added fields for Publisher and License in module.xml
- Added ability to put dependencies on PHP versions and PHP components in module.xml
- Changed database mode passwords form clear text to encrypted passwords
- Changed internal schema of trunks to add proper sql tables
- Eliminated dialparties.agi accessing AMI when EXTENSION_STATE() is avail
- Updated FOP to run with Asterisk 1.6
- Added Extended Repository to allow more contributed modules not part of main project, some extended modules include:
-
The 2.7 release will concentrate on adding functionality to take advantage of the FAX for Asterisk as well as improve the usability of FAX in general in the GUI.
We will role in a handful of other features opportunistically but will make the cut off when the new FAX module and required migration code is finished and stable for a very quick beta/rc cycle. All other tickets will be pushed to the next release or bugs will be addressed as minor module updates.
A list of features targeted for this release are:
- FAX module as described
- Different CID Options for Follow-Me Module
- Different CID Options for Ring Group Module
- Some enhanced functionality in Queues and improved dynamic agent abilities
- Setting Penalties for Dynamic Agents
- Restricting a queue to only specific dynamic agents
- Advanced mode to specify static devices vs. extensions
- Some improvements to Backup
- per backup set FTP and SCP options for remote storage of backup sets
- per session additional directories to backup (and restore if needed)
- Language option for incoming routes
- Increased handling of HANGUPCAUSE codes
- Outbound Route Specific CIDs
- Force Trunk CIDs and remove CNAM option on trunks
- CF Unconditional add support for DEVSTATE
- per device hints created with BLF support
- toggle option created designed to work with BLF
- BEEPONLY support added to minimize messages played
- Advanced Outbound Route Selection
- allows routes to be chosen based on dialed number and CID/extension number or pattern
- Add MoH Class choice for Conferences
- Allow MoH directory to be specified in amportal.conf
- Add ability for Module Admin to reinstall the same version or and older version (with many caveats)
- Move all of recordingcheck AGI script into dialplan
- Add optional and experimental macro-dial-one that can be used to replace macro-dial for single extension only dialing (no ringgroups, followme, etc.). Requires special setup, see: #4068.
-
FreePBX 2. 8
The 2.8 Feature Set is under evaluation and as tickets are reviewed from the current Cut Line they will be moved into this milestone. Not all tickets listed under the milestone are guaranteed to make it into this release.
Supported Asterisk Version
Our current statistics are showing less than 5% of the installed base of 2.5 - 2.7 systems are using Asterisk 1.2 and the bulk are using 1.4. As a result, this release will not officially support Asterisk 1.2. We will not take out support but we will consider the features set of 1.4+ when making decisions for changes and additions.
- Asterisk 1.2 not officially supported
- Asterisk 1.4 Supported and the mainstream release (based on installed base statistics)
- Asterisk 1.6+ Supported
Features
Features currently under evaluation, not confirmed and this list far from final.
- replace macro-dial + dialparties.agi with macro-dial-one
- current hurdle is lack of official EXTENSION_STATE() function (func_extstate.c) in Asterisk 1.4
- Modernize the internal plumbing of outbound routing and adding some enhancements in the process
- prepend digits ability
- associate route with a Time Group
- more flexible re-ordering of routes
- more intuitive GUI for entering dial patterns
- Trunk internal and cosmetic enhancements
- same more intuitive GUI as Outbound Routes
- deprecate fixlocalprefix AGI in place of dialplan
- Native DAHDI support (vs. current Compatibility Mode)
- Real Company Directory Module
- Many more features - see Closed Feature Request tickets associated with this Milestone
-
FreePBX 2. 9
The 2.9 Feature Set is under evaluation and as tickets are reviewed from the current Cut Line they will be moved into this milestone. Not all tickets listed under the milestone are guaranteed to make it into this release.
Supported Asterisk Version
Our current statistics are showing less than 5% of the installed base of 2.5 - 2.8 systems are using Asterisk 1.2. As a result, this release will not officially support Asterisk 1.2. We will not take out support but we will consider the features set of 1.4+ when making decisions for changes and additions.
- Asterisk 1.2 not supported
- Asterisk 1.4 Supported and the mainstream release (based on installed base statistics)
- Asterisk 1.6.2 Supported (see notes on 1.6.0 and 1.6.1)
- Asterisk 1.8 Supported
We also support 1.6.0 and 1.6.1, however, FreePBX may make certain assumptions about the existence of functionality in presenting various configuration options and sometimes in the generation of dialplan. When doing such, the support may assume 1.6.2 if running off of the "1.6" branch and if there are issues reported, we may choose to address them by requesting an upgrade to the 1.6.2 branch if running within 1.6.0 or 1.6.1 and the reported issues are in fact available with 1.6.2. As a general rule, the two main targets for Asterisk support in FreePBX are 1.4 and 1.8, as 1.6.X has been generally considered a bit of a 'disaster' by the general Asterisk community and as such, very hard to support and track given the number of variations between the three.
Architectural Enhancements
This version has introduce several significant architectural changes intended to modernize the Framework infrastructure and work drive the produce to a more supportable infrastructure and also one more easy to program to and accessible to both standard FreePBX modules as well as outside applications that need access to FreePBX. Examples of outside applications can simply be CLI based versions of functionality such as the already existing module_admin tool that allows full CLI access to the Module Admin functionality in the GUI (and a few more things beyond that one). These major enhancements include:
- Re-architected to bootstrap the full FreePBX environment with the inclusion of a single freepbx.conf file which is technically a 7 line PHP file that includes your database credentials and a path to the bootstrap.php application.
- Re-architected the amportal.conf settings. These settings have been traditionally used to fine tune many behaviors of FreePBX with a text based configuration file. All the configuration settings have been moved to a freepbx_conf class within FreePBX (meaning they live in the SQL database). This has resulted in an Advanced Settings page in core where these can be examined and changed, and also gives the program the opportunity to automatically make some changes when it detects the need for this.
- Linked the CSS and Images used in the FreePBX GUI branding and styling into the new Advanced Settings parameters such that almost all aspects of styling, logos and branding links can be redesigned. Only the fine print licensing and Copyright at the very bottom of the page must still remain.
- Consolidated some disjoint and rarely used FreePBX logging facilities into a single freepbx_log() function that we will start to use more extensively going forward. We also tied in existing messaging and the notification system into this logging facility so that quite a bit of logging information is already available immediately including:
- installation info (all the messages that get spit out also get logged)
- upgrade information (all the messaging you get during an upgrade get logged
- Notification subsystem in the Dashboard (all the information that gets updated there gets logged)
- Module Admin Repositories have been restructured away from the current Standard and Extended repository. Part of the design change means that you should no longer get phantom new modules available when switching between the repos. It also means that once you have loaded a module, you will be notified of any updates available for it even if you are not checking the repository it came from anymore. The new repositories include
- Standard - What we see as the most commonly used set of modules
- Extended - Other supported modules that are less commonly used.
- Unsupported - Modules available online but not supported by the FreePBX team, though often supported by the author
- Commercial - A future category reserved for third party modules that may be available for purchase. (There are such modules today, but no facility to distribute them)
- Support has been added for multiple language sound files in the FreePBX module structure. We will look forward to getting sound files for other languages contributed and added to the various modules that supply some of their own sounds.
These represent the major changes that have been implemented. There are quite a few other changes including some directory structure changes, facilities in Modules to better control and provide assets (CSS, js, image files) while avoiding name space clashes with other modules, and other areas. We have tried very hard to maintain compatibility with outside applications and third party modules that we do not have control over and in general, everything should continue to run without change.
Features & Functionality
There has been quite a bit of feature work done in this Milestone and the work is still un finished. The following highlights many of the changes that have been done or are planned to be done in this milestone. As always, some features may ultimately be cut and moved to the next milestone. As always, this is not a complete list as there are too many changes to track every one without a detailed analysis of the checkin log.
- Endpoint Management Functionality - due to its very nature, this is and will continue to be an ongoing project as phones and demand for supported phones continue to grow. Andrew Nagy is heading this up and for the most part, has done almost all the work to make this module a reality. We will be looking for feedback as this tool gets m ore widely exposed to help improve on it's capabilities and and support for different phones and other endpoints.
- Add DAHDi Configuration Module
- Extension Features:
- Extension Destinations for BUSY, NOANSWER and CHANUNAVAIL along with CID prepends for each case
- Ability to have any phone configured to auto answer (intercom style) for all internal calls while ringing like normal for external calls. An advanced setting also exists to override each phone's setting and put the entire PBX in this mode. (This depends on properly phone support for auto-answer and proper configuration such that it would otherwise work with the Paging and Intercom module.
- Separate Call Forward Timer. The current PBX behavior will ring the CF, CFU and CFB destinations for the same amount of time as configured to ring the line before going to voicemail (assuming there is voicemail associated with the extension). It is now possible to set this value independently or set it such that it will ring the Forwarding number forever as many other PBXs do. (If not changed, it will continue to use the standard ring timer value).
- Outbound call concurrency limits settable per extension. This allows you to control the number of simultaneous outbound calls any give extension can make. (This can be used as a throttling fail safe on extensions that are accessible from outside the PBX, in the event that credentials are stolen and the extension is hijacked for fraudulent calling, this would limit how many concurrent calls they could do. Of course strong passwords and other measures should be the primary defense).
- Optional Diversion headers (using the new Advanced Settings controls). This allows for Call Diversion information to be automatically generated for all forwarded calls as a result of Call Forwarding, Follow-Me, Ringgroups, Queues, Misc Destinations or any other mechanism that can take a call that originated from the outside and resulted in a new call being placed out a trunk.
- Search Extension Number ability added into the Print Extensions Module allowing large systems the ability to search for specific numbers, partial numbers or patterns. Also added are links to the configuration of every number listed on the Print Extensions page for quick access.
- Automatic Destinations generated for all Feature Codes that have a usable destination. In the past it was necessary to make a specific Misc Destination just to use a Feature Code (such as Voicemail Access) as a destination. Now these are automatically generated under the Destination category of Feature Codes.
- Support for app_confbridge in Meetme, for systems that don't have timing devices such as Dahdi cards or dahdidummy drivers. (With reduced conferencing functionality due to the limitations of app_confbridge).
- Call Confirmation ability added to Queues, such that external off PBX numbers can be forced to confirm the Queue call prior to the queue passing on the customer to the answered line. (This will also force confirmation on for any Follow-me that is pursued). The queue can also override the call confirmation message with one specified by the queue, even if ending up in someone's follow-me that has their own message configured.
- Feature Code associated with every Time Condition, that can be used to override the current time condition state and then reset itself once the current time period is over. (Or if put in sticky mode, it will stay until manually reset). These feature codes are also BLF enabled and will always reflect the current state in the BLF (off if in normal time mode, on if in false time mode).
- Third 'force' mode added to paging groups. Currently a busy phone can be skipped or the call can be forced sent to all phones. The latter behavior results in some phones automatically putting the current caller on hold and auto answering the new call. The third mode will use ChanSpy which allows Asterisk to simply insert the paging stream into one of the channels of the current call, such that the PBX extensions will hear the paging in their ear, but the party they are talking to will not hear it.
- Chan gtalk and jabber added to the Asterisk Info module
- Merging of the contributed module vmadmin functionality into the Voicemail Module to provide significantly increase Voicemail GUI configuration ability and move away from the manual editing of the vm_general.inc and vm_email.inc files.
- Added required support in core to facilitate the mISDN unsupported module which will be available online for downloading.
- Some feature not yet started but we are still hoping to get in:
- Camp-On Feature using the Asterisk 1.8 CallCompletionRequest Application
- "Reverse CID" using the Asterisk 1.8 CONNECTEDLINE() function (let's you push CNAM information back to the caller such as the internal display name of who is answering the phone), for those phones that support this
- Features that look like they will probably slip to the next milestone:
- Enhancements to Call Parking now available in 1.8 (and maybe some in 1.6.2), possibly including multiple parking lots
- Support for Google Voice Trunks with Asterisk 1.8
- Some level of integration with the Asterisk 1.8 Calendar function (adjusting call flow based on the current state of an external calendar
-
FreePBX 2. 10
The 2.10 feature set and other changes and planning are under evaluation at this point. This information represents a working document by the development team in conjunction with feedback from the user community as to the plans and changes for 2.10. Tickets and suggestions will get evaluated as the milestone shapes up (and 2.9 gets locked down) so nothing listed here should be taken as a guarantee to be in this milestone. The current due date is a 'stake in the ground' right now. As the plans get more solid and once the final release of 2.9 is confirmed, this due date is very likely to be modified.
Supported Asterisk Version
The supported versions for this milestone are:
- Asterisk 1.2 not supported (and you may see functionality start to break)
- Asterisk 1.4 Semi-Supported (not officially unsupported, but if a good reason come up support will be immediately dropped)
- Asterisk 1.6.x Supported
- Asterisk 1.8 Supported and targeted as mainstream (based on current usage trends)
- Asterisk 1.10 Supported
In addition to this support matrix, the following functions may be expected to be present in earlier releases, none of which are standard in Asterisk 1.4 but all of which have very straight forward back ports available and are fully contained in a single func_xyz.c file which can also be loaded by simply obtaining the func_xyz.so module and installing it in your Asterisk modules directory.
- DEVSTATE() or DEVICE_STATE() : func_devstate.c/func_devstate.so
- EXTENSION_STATE() : func_extstate.c/func_extstae.so
- SHARED(): func_shared.c/func_shared.so
PHP Support
- PHP4 will no longer be supported in Core and Framework and functionality will be added that will break with PHP4
- Notes About PHP4
- PHP4 went End Of Life 12/31/2007
- PHP4 stopped receiving Critical and Security fixes 8/8/2008
- PHP5 was first introduced 7/13/04 and is the mainstream PHP release almost everywhere
Architectural Enhancements
Each milestone includes some architectural enhancements or other changes such as cleanup of some hard to use APIs. As FreePBX is coming on 7 years old, it is important to whittle away at some of its core to keep things from rotting away, or to add new capabilities that make it easier and more powerful to develop for. It is always of extremely high priority when making these changes to do everything reasonably possible to maintain compatibility with third party modules and other outside programs that enhance the FreePBX eco-system. It is also critical to assure that past versions can be migrated automatically when upgrade modules are installed, as well as at the command line using the install_amp installation method.
- Find a good alternative or addition to FOP (FOP2?)
- Kick off the design of a brand new User Panel (to replace ARI) - would probably span multiple Milestone's and be housed in its own.
- Further architectural changes to the main FreePBX view to accommodate more significant configurable GUI layouts.
- Enhance (and fix) internal Call Recording settings to give more fine grain control on what calls to record and what not. (Probably in conjunction with the above User Portal since viewing the recordings is paramount) #5202
- Evaluate the replacement of the current Call Reports code with some existing alternatives that are available and show promise.
- Replace PEAR DB with PDO, probably add a class that looks similar to the current PEAR class and handles the 95% usage case within the FreePBX code base to provide a transition that minimizes the overall porting effort.
- Seriously evaluate the applerasin Asterisk branch that allows AstDB to be mapped to an Asterisk realtime configuration thus allowing it to be tied to a SQL database. This could include modifications to allow FreePBX to interface to AstDB directly through the configured database vs. the backwards approach Asterisk currently required of accessing AstDB variables through manager calls.
==mbrevda==
- amportal chown takes a long time #5174
- PearDB's is error methd is NOT static #5179
- Abstract gui elements #5165 (maybe)
- Abstract call recordings to its own module #5202 (maybe)
- Move module build scripts to php, add support hooks #5208
Features & Functionality
These represents specific features and capabilities that we hope to introduce during this milestone
- Enhancements to Call Parking now available in 1.8 (and maybe some in 1.6.2), possibly including multiple parking lots (some of this has been done in 2.9)
- Support for Google Voice Trunks with Asterisk 1.8+
- Some level of integration with the Asterisk 1.8 Calendar function (adjusting call flow based on the current state of an external calendar)
mbrebvda
-
* Asterisk 11 Support
* Destination popOvers
* Module Admin Security Auditing capability
* Outbound Route and Trunk enhancements
* Extension Routing Module
* Hotel Wakeup Call Module
* Chan Motif Module (google voice enabler)
* CallerID Superfecta Module
-
FreePBX Cut Line
This Milestone is simply a bin to catch all feature requests and other tickets that have not yet been assigned into a Milestone above. There may be very valid tickets in here that should be moved into a more active Milestone and if you find such, you are encouraged to comment in the ticket with your suggestions concerning that.
Supported Asterisk Version
Architectural Enhancements
Features & Functionality
