Changeset 5399
- Timestamp:
- 12/10/07 16:47:11 (5 years ago)
- Files:
-
- freepbx/trunk/CHANGES (modified) (5 diffs)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
freepbx/trunk/CHANGES
r5305 r5399 1 1 2.4.0 2 3 WARNING: changes were made to some of the core_did_XXXX() API calls that could effect 4 any custom applications that were depending on these. 5 6 WARNING: changes were made to context ordering wrt to ext-did-catchall and 7 from-did-direct. Previously, if you had not ext-did-catchall you might be in a 8 situation where you were reveiving direct DID calls to your extensions even though 9 not configured since there was no catchall route. If you then made a catchall route 10 you would suddenly stop receiving those calls and would have to add the dids in a 11 route or as a direct did. With this change, it is now deterministic but the behavior 12 of an existing system could change (they could suddenly start receiving DIDs). This 13 can be easily corrected though by intercepting those DIDs with an inbound route (with 14 pattern matching if need be). 2 15 3 16 - Implementation of a distributed Extension and Destination Registry through callbacks … … 10 23 and any inegrity issues are supplied to the notification panel. All supported modules 11 24 should be instrumented to use these once updated. 25 26 - Addition of Custom Applications Module. Provides a place to register custom extension 27 numbers as well as custom destinations that are to be used in FreePBX. Replaces the 28 old Custom Destinations choice that was available in each module. 29 30 - Moved vmblast form contributed modules to supported module after significant changes 31 and fixes as it never worked form the original contributor. Add additional features 32 to it and added a default vmblast group option to be used with extensions/user add 33 and edit. 34 35 - Custom destinations will no longer show up under the destination selections unless there 36 is already one configured or an unknown destination is detected (which are one and the 37 same). To use a custom destination in FreePBX, it will have to be registered with this 38 module to appear as a choice to other modules. (Similar to adding a destination to the 39 Misc Dests module). 40 12 41 - Module admin changed so that 'problem' modules that have dependency issues will not 13 42 block other modules from being downloaded and/or installed. A warning is still generated 14 43 but the action is allowed to proceed with any modules that have all their dependencies 15 44 met. 16 - Custom destinations will no longer show up under the destination selections unless there 17 is already one configured or an unknown destination is detected (which are one and the 18 same). Misc Applications module will continue to support custom destinations. Users must create 19 a Misc Application for any required custom destinations, and then use Misc Dest to access 20 that destination so that it will appear as an option to other modules. This is more 21 cumbersome but ultimately less error prone and more supportable for the user. 45 22 46 - Removed Channel Routing from 'Inbound Routes.' Added 'Zap Channel DIDs' to core modules 23 47 to assign DIDs to Zap Channels which can then use 'Inbound Routes' to route them with … … 26 50 converted and entries inserted into the 'Zap Channel DIDs' tables. 27 51 28 WARNING: changes were made to some of the core_did_XXXX() API calls that could effect29 a ny custom applications that were depending on these.52 - Ringgroups, Queues and Follow-Me have been enhanced with a Quick Pick utilitlity that 53 allows extensions to be added into the the ring list. 30 54 31 55 - Several changes and enhancements have been made to improve the usability of Users/Devices … … 37 61 - There are still issues if reloading from the CLI. A script and some instructions will 38 62 be supplied on ways to address this until a more permanent solution can be determined. 63 39 64 - Pulled some agi scripts and macro calls out of dialout-trunk / dialout-enum into the outbound 40 65 route code so they would only be called once when the call sequence has to try multiple 41 66 trunks. 67 42 68 - Added reload option to CLI module_admin to peform same task as the reload bar. 69 43 70 - Added support in macro-user-callerid to support per-user/extension language changes. 71 44 72 - Significant changes within Paging & Intercom Module for 2.4 version of Module. Highlights: 45 73 - Intercom works properly when User is logged into multiple devices and will intercom them all 46 74 - Explicit Allow and Deny options to control who can/can't intercom you 47 75 - AstDB flag that can be set for a specific extension to block it from intercoming anyone 76 - designate a group as default for add/edit at extension/device creation/edit time 48 77 - Significant improvments in Auto-Answer ability for more phone support: 49 78 - Defaults pulled from database which can be changed by an advanced user … … 53 82 - Abilility to trigger custom macros for phones based on useragent info or on a per-device 54 83 basis with information stored in AstDB for that device, for advanced users. 84 85 - Queues Module has been updated to remove its dependency from the old legacy extensions table 86 and the current queues table is replaced with queues_config and queues_details table. 87 88 - Queues and the SIP, IAX2 and ZAP conf file generation has been replaced with proper queues_conf 89 and core_conf classes 90 55 91 - Misc other bug fixes and some feature requests that can be obtained through the SVN log. 56 92
