Not sure what section of the forum this should go in but I’ll throw it here for now.
@lgaetz @mbrooks @mattf and anyone else that needs to see this. The FreePBX project needs to be tracking and communicating to its user base about the deprecation and removal of Asterisk modules so they can be aware of what they need to do. While Asterisk v16 saw a number of modules go from automatically being built/installed to you having to enable them during build. Now this isn’t a big deal for most Distro users, you guys are enabling them. I mean you have to, FreePBX is still using a some of them.
However, Asterisk v19 saw many of the modules that have been deprecated for almost a decade be removed. This is a trend that will continue in Asterisk v21, a very important release as this is when pretty much all the deprecated stuff FreePBX is still relying on for a lot of its workload to be completely removed.
As I pointed out in another thread, FreePBX is no longer something that Asterisk users are using to help manage Asterisk. It is now something that non-technical people are using as a solution for their businesses. These users certainly have no idea about Asterisk and they shouldn’t because they are using FreePBX/PBXact as their solution. They aren’t paying attention to the multiple FOSS projects that are being used under the hood of FreePBX/PBXact, they expect FreePBX/PBXact to keep them informed of changes that are happening.
Development in the Asterisk project and how the project handles things (such as deprecation) has changed over the past few years. Deprecated modules are not going to be hanging out in Asterisk for a decade after being deprecated anymore. They will be marked as deprecated and within the next Standard be removed from auto compiling/loading process (like app_macro now) followed by full removal in the next LTS.
This project (and PBXact) needs to make a very, very, very strong effort in educating and informing its user base about these changes that are happening. Because as of Oct 2023 which will see the release of Asterisk v21 the following will be completely removed and no longer usable (highlighting the ones I think are most used in this project by users)
Monitor will be removed. This means anything that uses Monitor for call recordings will no longer function. This includes FOP2, which so far hasn’t updated to MixMonitor. This will also impact other modules/applications such as app_queue that have settings/options for Monitor. Those modules/applications will be impacted by this as well.
Not sure how much this is used but it is an option for Cisco phones but this will no longer function making Cisco phones using it no longer work.
This is a big one as FreePBX has a lot of Macro() calls. Also due to the amount of ancient documentation and long term users never moving to GoSub() (replacement) the use of Macro() is still very high in documentation out in the wild and those following that documentation. This also means any other applications such as app_macro, app_dial, etc that have options to execute/call a Macro() will be impacted as those options will no longer be viable and could break usage.
Probably the most important one. This projects education and push to get people off of chan_sip is dismal, at best. There is still too many “it didn’t work on chan_pjsip but with chan_sip it does so I guess that’s what I’ll use” or those recommending “Well that just works with chan_sip, use that.” happening within this community. There needs to be an active effort to stop that going forward.
At this point there are very little use cases in which Chan_PJSIP cannot replace Chan_SIP but again, that is a very small piece of the pie. The average FreePBX/PBXact user can safely move to Chan_PJSIP without much worry. I’m going to venture to say that 99% of the time someone says “It doesn’t work in Chan_PJSIP but does in Chan_SIP” will be due to a configuration issue and not understanding differences. Which is why this project needs to make a stronger effort (or any really at this point) to educate its base.
Because right now with FreePBX’s new version release schedule being roughly 2 years between major versions and FreePBX 16 being released in Oct 2021 that means by Oct 2023 FreePBX 17 will be out and if that version doesn’t address any of this there is going to be a serious nightmare of problems.