That’s important advice.
Along those lines, may I suggest the creation of a Wiki page that lists all of the contexts created and used by FreePBX, and their intended use? I imagine that you already have such a document internally for developers.
↧
Can you allow barge in on a line without parking a call
↧
FreePBX design discussion
The above observation is 100% correct. FreePBX is much more affordable, much more powerful, and much more customizable.
And given that, you have to wonder, why would anyone buy 3CX rather than using FreePBX? The answer, as I’ve been saying all along, is that 3CX has much better documentation and is much easier to use.
As ITConsultant said, he learned much of what he knows about FreePBX from videos posted by a third party (CrossTalk). When I started, those videos did not exist. I learned much of what I know from WiseOldOwl and MichiganTelephone, and from spending more than 1,000 hours playing with FreePBX and then examining how changes in the GUI impacted the Asterisk’s *.conf files. Ideally, everyone should learn what they need to know from the source (currently Sangoma), and not from third parties or from having to experiment (which I believe to be fun but which most people do not).
It should not be necessary to consult with third parties to learn how to use FreePBX, nor should it be necessary to attend expensive training seminars. Both of these things impose a barrier to entry that makes 3CX look better to new adopters.
This discussion started with Jared asked what we thought future of FreePBX should be.
The immediate future of FreePBX should be about (1) building a comprehensive set of documentation, (2) updating the documentation as soon as new features are added, and (3) ensuring that when new features are added, the GUI is changed in a way that doesn’t break the documentation.
Long term, FreePBX should look at ways to simplify the GUI, rather than complicate it. The focus should be on making configuration quick, rather than making it look fancy. Fancy sure looks nice, but it will stop working when the browser extensions that are needed to support it are deprecated.
At the end of the day, the people who work for me and who live in my house only care that the phones work. They never see the GUI and don’t care how fancy it is. I use the GUI, but I don’t care about fancy. I want configuration to be quick and easy. I used to be able to set-up a new FreePBX install, complete with emergency routes, intracompany routes, parking lots, conference rooms, queues, rings groups, time conditions, time groups, superfecta (which sends CID to Kodi on all my TVs) and a ton of custom code in about 4 hours. Now it takes nine. For the very same configuration.
↧
↧
FreePBX design discussion
since it’s an open source project crosstalk Solutions videos is a contribution to freepbx and sangoma saw how good crosstalk’s videos were so they actually hired him to make the videos for sangoma University which anyone can access by signing up for free, and personally I like more when a third-party makes the documentation and gives you the cold hard truth like for example not jumping on every new update or switching everything right away to PJSIP and that resulted my systems being much more stable the developer would never tell me about these things and a lot of other practical advice and how to implement 3rd party stuff
↧
Crackling audio on system recordings
I have FreePBX installed on a raspberry pi which I use for my home. I use 3 x Grandstream 2 Line 1 SIP phones as well as 2 x Mitel 5300 phones with SIP Version 06.03.03.06 which was implemented by TFTP. After setting up the Mitel 5330 phones I realised that there was an issue with the sound recordings on the Mitel 5330 where the sound recordings for voices distort/crackle. This is not the case on some of the sounds but majority of the sounds start to crackle. With my Grandstream phones, the sound recordings do not crackle. When calling in and out using the phones including extensions within the house, the audio is clear. The crackle only appears to be with the system recordings voice.
↧
FreePBX design discussion
Again, you and I are on the very same page, but I have some thoughts of what you’re written:
First, Crosstalk wouldn’t have needed to make those videos if the FreePBX dev team had made documentation more of a priority. The reason that Crosstalk made those videos, and that WiseOldOwl and MichiganTelephone wrote up their own documentation before Crosstalk make those videos, is because the dev team has focused their efforts almost exclusively on development.
Documentation has been a second (or third or fourth) priority for the dev team. I know that I sound like I’m being critical, but I’m not. I’m simply stating a fact.
Second, Crosstalk’s videos are great now. But, what happens when the FreePBX dev team decides to totally revamp the GUI? All of their hard work could become obsolete overnight. It has happened in the past, more than once.
Third, I agree 100% with your observation about pjsip as well, but that observation has much broader implications. In the open source universe, the more mature (i.e., older) version is almost always the safer choice. If you are offered the option to install Asterisk 13 or Asterisk 16 with your FreePBX installation, you should generally choose 13. If FreePBX 14 was just released last week, you should install FreePBX 13. If you love playing with software, like I do, you should play with 14, but 13 should be running your office until 14 becomes more mature.
Information about versions should be one of the first pieces of information that appears in any open source documentation. It should probably appear right before, or right after, the system requirements.
With FreePBX, to find out the difference between 14, 13, 12, etc., you generally have to hunt down the roadmap and release blog posts and then compare them to one another just to get a sense of what has changed. In contrast, for example, Polycom has released detailed (hundreds of pages) of documentation everytime that they make a .x firmware change. There’s a Polycom Firmware 5.8 manual, and another manual for 5.9.
I’m not sure that FreePBX needs to go that far, but a move in that direction would be a good way to compete with 3CX!
↧
↧
System Recordings not working
↧
Config.php hacked - need to replace
I received the odd email this morning from my Sangoma FreePBX appliance:
SECURITY NOTICE:
You have 1 tampered files:
Module: “FreePBX Framework”, File: “/var/www/html/admin/config.php altered”
There are 4 modules vulnerable to security threats:
backup (Cur v. 14.0.10.7) should be upgraded to v. 14.0.10.10 to fix
security issues: SEC-2020-003
superfecta (Cur v. 14.0.23) should be upgraded to v. 14.0.25 to fix security
issues: SEC-2020-002
cel (Cur v. 14.0.2.14) should be upgraded to v. 14.0.2.15 to fix security
issues: SEC-2020-001
framework (Cur v. 14.0.13.12) should be upgraded to v. 14.0.13.23 to fix
security issues: SEC-2019-000
I logged in remotely, and the config.php file was most certainly hacked - it had lines to delete a lot of files in the system, and lines to allow any user named “mohammed” to login to the admin page. I immediately deleted the file, and am now trying to figure out how to restore it from an RPM package using yum or rpm.
Any guidance on how to restore the now deleted config.php file is appreciated. Or what should be in it.
Note that I cannot find references to the above security updates on the FreePBX community either, so am now questioning the legitimacy of the email.
Thanks.
↧
Config.php hacked - need to replace
Reinstalling or upgrading framework will probably restore the config.php.
https://wiki.freepbx.org/display/FOP/List+of+Securities+Vulnerabilities
You almost certainly are allowing untrusted access to the admin GUI, you wan’t to disallow that.
↧
System Recordings not working
Restore it then.
↧
↧
System Recordings not working
I have done and it seems to still not work
↧
System Recordings not working
I have done and I still get the following error that I added to the original post
↧
Config.php hacked - need to replace
Thanks - can I reinstall framework using yum?
Thanks for the list of vulnerabilities - looks like those were in the list. By untrusted access, I guess you mean I need to restrict the IP access to the admin GUI login page to trusted IP’s? Is there an easy way to go about that or do I just dig into the firewall rules on the appliance?
Thanks.
↧
Mitel crackling audio on system recordings
Audio Codec g729 works with Mitel with no crackling however calls are automatically hung up when answered on the Mitel phone and does not allow music on hold to be heard on the Mitel phone in a queue.
↧
↧
Config.php hacked - need to replace
No. Framework is a pbx module, use the Module Admin page.
https://wiki.freepbx.org/display/FPG/Firewall+Getting+Started+Guide
↧
System Recordings not working
Did you mess with the permissions as well?
Make sure there’s proper file permissions set.
↧
Mysterious PJSIP channel
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
↧
Config.php hacked - need to replace
Lorne,
Unfortunately, I cannot get into the Module Admin page - the entire admin page is offline, as it appears config.php is the main file used. I guess I can download FreePBX to one of my Linux boxes, and unpack it and try to find the admin/config.php file I need, then copy it over to the Sangoma appliance.
Once I get it up, I’ll start looking at the firewall rules. It is enabled, but I have some users who needed remote access to the admin page, to change forwarding rules and ring groups remotely. I’ll just have to shut that off to anyone who is not VPN’ed into the office.
↧
↧
Config.php hacked - need to replace
Try
fwconsole ma downloadinstall framework --force↧
Config.php hacked - need to replace
Thanks, I actually grabbed the latest FreePBX 14 tarball, unpacked it here on my laptop and copied up to the PBX at the office. I’m into the admin panel now, and am installing updated modules, then locking down the firewall to the LAN and my home IP only, since I am the only person that truly needs remote access on port 443. The user control panel is on its own port, and I will leave that open for now.
↧
System Recordings not working
I have tried using chmod 777 custom. Is this correct?
↧