About the only real addition in 2.7 is support for Digium's closed-source
Fax for Asterisk commercial product. This gives you a good idea where the FreePBX project may be headed unfortunately.
Now now Ward, are we trying to stir up trouble again
...
It would seem that you have not spent any time reviewing 2.7 given this "somewhat naive" statement. With 142 tickets closed in 2.7 and the addition of features to Follow-Me, Ring Groups, Queues, Backups, Inbound Routes, Outbound Routes, Trunks, Conferences, Module Admin, and many dozens of other minor and not so minor bug fixes and feature requests, I would hardly call your assessment grounded in reality. Here's the Milestone data for the record:
freepbx.org/v2/milestone/2.7
Let's be very clear about what the additions wrt to fax-ing were all about. If we only wanted to support FFA, it would have been a trivial change and in fact it was already supported as FFA has their own compatibility mode for rxfax() in 1.4. The goal in the FAX module was to make what was previously a very un-intuitive GUI when it came to routing FAX DIDs and fax configuration in general, and make it much easier to understand. (I'll venture to ask anyone - and no cheating looking at your neighbors test - how to "properly" route a DID directly to a fax email without the use of detection on 2.6 and prior. Most people get that wrong.)
If you have followed a lot of the significant work going on with the Fax-ing module it was in fact very much about getting faxing working properly with "spandsp" (app_fax/app_rxfax). The fact that it also supports FFA is relatively trivial though for some it is a pretty important support as it does appear to provide a notch over spandsp from many reports.
So let's try to speak in terms of facts when providing such information.
Philippe
p.s. for some of you who have had problems with custom-context, there is a change that will go out with the next core module update that should eliminate the issue that has been reported:
freepbx.org/trac/changeset/9096
and I recently updated custom-context with another fix that had been reported as a result of the threads kenn10 has listed. I've also been in contact with naftal5 (the author) wrt to the module to see what could be done in helping to keep it updated. But with the above, I believe it will be back where it was (and then some) from 2.6.
Now on the down side wrt to custom-context, come 2.8 it will be completely broken unless naftali5 or someone else is able to step up and get it in sync with some significant changes in the entire outbound routing "internal plumbing." Ward is already aware of this change as I've given him a personal heads up with LOTS of time to adjust for any issues it may cause. I hope to get an alpha tarball out in the next week to start early testing to give at least a couple months time for the various third party module developers to see what is going on and if it effects them, have a chance to address the changes. (and as always, no need to wait, it's all their, in realtime, in SVN for all eyes to see) It's a rare but necessary change in FreePBX that has been on the drawing board for a long time (and in fact one of a few reasons why we chose not to bring custom-contexts into the core supported modules.)
This is why our production machine is still running 2.5!
Phone System 
