My main use case for FreePBX is that I've had instances where somebody had a Cisco call center and the licensing fees were too high, and I migrated their call flows from Cisco to FreePBX. Mostly it's smaller systems, but I've been in one place in El Segundo, where the in-house phone system was FreePBX and it had over 100 stations. It's quite a good system, as it's a Windows wrapper around an Asterisk-based system.

A quick specific example of how I used FreePBX in one of those migrations is the one client I had with the Cisco call center; they had their call flows laid out in Visio and I was able to replicate them on a FreePBX system. They did sales of musical instruments for schools from upstate New York. But they were so enamored with the solution that they had two call centers, so they bought two FreePBX systems, and there's a hot standby that you can do where if one goes down for any reason, everything switches over to the standby system.

I developed a demo for a university on the West Coast as my main use case, and we were going to do 900 phones, something along that line. They decided to go with something else, but I was able to stand up a demo on a DigitalOcean droplet, a system in the cloud, and restore one of my old demo systems and modify it. I was able to stand it up within a week and be able to show them the call functions and the call flows and give them softphones and really flesh out the demo. I've had demo systems on DigitalOcean for many years and it's been quite beneficial.

The best features FreePBX offers are that the software is free, but usually for someone to install it, there's a cost.

FreePBX positively impacts my organization because I'm a one-man organization. I get some work doing FreePBX installs and migrations and maintenance. For my clients, they call me up and ask for an address move change or some new call flow and I can have it done in very short order.

The speed at which I can make changes with FreePBX depends on the change, but I know the system well enough that I can make normal call flow and announcement changes and IVR changes in very short order, sometimes in less than an hour, with testing. Depending on what they want, it can take some time. When I've done large systems, some of the migrations took three or four weeks, and some have taken a couple of months depending on what they're asking for.

FreePBX can be improved as they come out with a new version every year or so. Their current version is FreePBX 17. The user community and the FAQ are great; you can search for just about anything you want to do on FreePBX and they're getting new AI engines and new text to speech engines from third party vendors all the time. So it's a very rich community.

Sometimes the security is a bit odd with FreePBX, but security is a bit odd overall, so I don't know if that's a valid concern. I appreciate it; it's a good environment. Sangoma is the owner of the system. If I ever get stuck on something, and it doesn't happen very often, I can call and get help from Sangoma, and sometimes they want me to pay for it. It's fine if that's what it takes, but there's great support.

I have been using FreePBX for 10 to 15 years, over 20 installations, and maintenance and migrations.

FreePBX is stable in my experience; I've run into clients who run the server for years without anybody touching them. In fact, their call recordings sometimes would choke the hard drive out of free space.

The scalability of FreePBX is all about memory and CPU. FreePBX has an appliance, and I use that as a baseline for scalability. The big one is 400 users and 350 simultaneous calls. That uses an Intel i7 and 8 gigabytes of RAM. You can do that pretty easily in a cloud environment. For my demo system, I had 4 gigabytes of RAM and a two-core processor and 80 gigs of hard drive, and it worked great, flawlessly.

The customer support for FreePBX is very good. I can search for just about anything. I can call VoIP-Supply, who's the retail supplier of Asterisk and FreePBX and some other systems as well from Grandstream. But if I really get in a pickle over something, I can purchase support hours and get an answer.

I previously used different solutions including Cisco, Avaya, and NICE CXone, and I have some experience with AWS. This is such a rich environment where the base software is free, and that's quite attractive to people.

My experience with pricing, setup costs, and licensing for FreePBX indicates that most of the general features are available for free. But if you want to do a hot backup or an AB style backup system, there's a fee for that, and some of the call center reporting options can be very expensive, but nothing compared to what Avaya or Cisco would ask for that sort of thing.

I have seen a return on investment with FreePBX; for example, the musical instruments group saved over $30,000 a year by moving from Cisco to FreePBX for their licensing.

Before choosing FreePBX, I evaluated other options, including Avaya, Cisco, and NICE CXone. They're very expensive in comparison, and that tends to be the differentiator.

The user interface of FreePBX is web-based. You just hit the URL as an admin and log in with your username and password. It's very flexible. The logging is tremendous. In Linux, you can get out to the command line and do certain diagnostics for things that are not working or how to get around the problem. It's such a rich environment that there are add-on products for just about anything you would want to do. I've worked on very large Avaya and Cisco and NICE CXone systems and some of those things are much more difficult and exponentially more expensive.

I advise others looking into using FreePBX that if you're not familiar with it, I would recommend having someone to walk you through the process, and I can give whatever level of support that you would want. I'm not the only one; there are some very good groups out there who would do the install or even host the server in the cloud for you.

There are softphones, some of which are free, some of which charge. With softphones, if somebody's PC is very busy, it can't give it enough CPU cycles to sometimes answer the phone. There have been instances where the president's secretary had a large Excel spreadsheet and she was doing something that required a lot of CPU cycles and she was backing up the receptionist. So softphones can have their own set of oddities. Hard phones are beautiful; I've got some Polycoms that are very durable and very reliable. I rate my overall experience with FreePBX as a 9 out of 10.

My main use case for FreePBX is for the PBX functionality. A quick specific example of how I use FreePBX for PBX functionality is that we have a toll-free number. When a call comes into that, we route the call to the time condition and then from the time condition to the IVR for sales support. Then, each sale and support will have the ring group or a find me/follow me. So, it will have that call connected with the concerned person. That is pretty much the core of what I do with FreePBX.

Since it is a free solution, all the features FreePBX offers are valuable. I would like to bring up the support of FXO and FXS hardware via DAHDI. The FXO and FXS hardware support has helped my organization because these are the gateways, SIP gateways for the analog phones. We had that gateway implemented for us as well as for one of our clients for the conversion of the analog ports.

The features are easy to use, and the FXO and FXS support is excellent. We can also have good community support for that. FreePBX has positively impacted my organization as the call routing can be handled very quickly via the interface. There is no need to have a CLI job or execute commands via SSH into the server. The interface made it very easy to configure everything.

Regarding the numbers, any route can be changed within a couple of minutes or a maximum of 10 minutes, whatever logic we want to have for the call routing when it is not a complex configuration.

Since it is an open-source product, FreePBX can be improved. There are a few commercial models available in the market, which are paid solutions. The presence, infrastructure, and UX/UI can be more friendly than what currently exists.

Security would be the main feature that I wish was better because the FreePBX box can get hacked quickly. Security needs to be implemented at a higher level. I have not seen any other improvements needed for FreePBX besides what I mentioned earlier about security and UI.

I have been using FreePBX for almost two-plus years.

FreePBX is stable.

It is not too scalable, to be honest. If you are running for one instance or one customer, then it is good. It does have a scalability issue with multi-tenancy.

The customer support for FreePBX was overall good. The community-based support was good, and there is some paid support as well from Sangoma. From the community support, I would rate it an eight out of 10.

Before FreePBX, we tried with 3CX, but it was a paid solution. All the features we needed were fulfilled with FreePBX, so we chose to use that.

My company does not have a business relationship with this vendor other than being a customer.

I have definitely seen a return on investment. Money was saved, as opposed to taking a subscription-based model for each of the extensions. FreePBX provides an unlimited solution. Time-saving is definitely there since anyone with technical knowledge can configure it.

My experience with pricing, setup cost, and licensing is that we only need to pay for the server through DigitalOcean billing. Since it is open source, you can have the ISO and install it on your own.

Before choosing FreePBX, we did not evaluate other options. We were looking for an Asterisk solution, so we went with FreePBX.

My advice to others looking into using FreePBX would be that it is overall good. If you are looking for a single-tenant solution that can fit in-house, cloud, and in-house servers, it will be an overall good experience. If you are going with analog cards or analog devices, then it is a good solution. I would rate this product an 8 out of 10.

I use FreePBX in many different ways depending on the need. Sometimes I use it as a contact center solution with a third-party plugin such as FOP. I do integrations with the operator panel so that operators can assign calls and manage queues. I also use FreePBX as a Session Border Controller (SBC) because some customers still run FXO or PRI lines. To convert those to SIP, I prefer to use FreePBX since I compile my own version and can compile additional drivers such as DAHDI to make PRI or FXO lines work.

When I use FreePBX as an SBC or for integrating with operator panels, I recently had a customer with a Grandstream device connected to what is called a SIP MLS, which is a private SIP line obtained from a local provider. The Grandstream device was unable to support that PRI interface, so I compiled Asterisk and the DAHDI drivers, configured the PRI interface, and delivered it to the customer.

FreePBX is an IP PBX that I sometimes use as an SBC to move traffic from one box to another, making one FreePBX instance act as an SBC for PRI to SIP conversions or FXO to SIP conversions. I have also used FreePBX for outbound dialers and outbound dialing, though that was a custom project involving custom dial plans and call files developed specifically for a customer.

I believe the best thing FreePBX offers is the ease of use to get it running and the features it provides. From my perspective, the greatest feature is the community support forum. Since FreePBX is a free product, the responsibility to fix issues falls on the user, making the community forum invaluable. Additionally, FreePBX is built on Asterisk, so anyone who understands Asterisk can accomplish anything with FreePBX.

Customization is the primary feature I appreciate about FreePBX. As long as you understand how to work with dial plans and Asterisk, and you have some programming knowledge and understand how APIs work, you can make many things happen. You could even build your own cloud PBX with FreePBX by integrating WebRTC and building your own SIP client with your custom design to create your own version.

FreePBX has made a positive impact on my organization, and we have completed many projects with it. It is a great application and one of the best open-source projects available. As an engineer, I appreciate working with FreePBX because I love Asterisk. It improves ease of configuration since we are all familiar with it, and for many situations, FreePBX is simply the better solution.

I believe FreePBX could be improved regarding the user interface. Sometimes the user interface has bugs, and when you apply configuration changes, they do not always apply properly. I have needed to access the command line interface and run commands to complete tasks. A more modern, responsive, and faster user interface would be beneficial.

I have been familiar with FreePBX for at least ten years.

I love FreePBX and Asterisk. The pricing for FreePBX is reasonable, and the licensing is fair. I use the free tier because I support the product, so I do not use the paid version of FreePBX. The free version is excellent. Regarding cloud providers, I use Linode, which sometimes has occasional issues, but they always resolve them and are easy to use. I would like to use other cloud providers, but I am more familiar with Linode. I rate this review a ten out of ten.

My main use case for FreePBX is to design IVR, manage queues, extensions, and Find Me/Follow Me features. I also configure inbound routes and especially design custom destinations and recordings. I set up backup schedules as well.

When I have a new application, I create a new IVR, such as pressing four to route the call to my application. The IVR asks the caller questions and routes them to the queue. I also created extensions to answer the calls.

FreePBX offers the best features for a small call center for a small company with 20 or 30 agents.

FreePBX has positively impacted my organization because it allows quick setup for a small call center and is easy to use. I can create announcements, design an IVR, and use SIP phones for agents. The cost is reasonable.

I think FreePBX can be improved by offering users the ability to design a call flow more easily through a drag and drop interface. Currently, the user has to create a queue, an extension, an IVR, and an announcement in different menus. Combining them on one page would be beneficial.

I am familiar with using FreePBX and I think the current state is acceptable regarding the needed improvements.

I have used FreePBX for about eight years.

FreePBX is stable in most cases.

FreePBX's scalability is good.

FreePBX customer support is great. I had some questions and received support.

I previously used Asterisk, the core Asterisk, as a different solution. I can customize Asterisk for my purpose because it is an open-source solution.

I rate the initial setup as 8 out of 10 because it is a lightweight framework that is easy to set up and use. That is the main reason I chose this rating.

I learned about the features through online research on Google and the internet.

I use a free version of FreePBX, but my customer uses a commercial version. I do not know exactly how much they have to pay for the license.

Before choosing FreePBX, I evaluated it because my customer uses FreePBX and I need to support them. FreePBX has built-in features and security.

Since I started using FreePBX, I think it could serve as a customer service tool. The company can build a quick team and use FreePBX for customer service to gather customer feedback and improve their products.

I will invite some of my friends to use FreePBX if they want to build a small call center with quick setup and do not need complicated features. I rate this product 8 out of 10 overall.