How do I install FreePBX v3?

There are detailed installations instructions available on our installation page.

How can I upgrade from v2 to v3?

FreePBX v3 is a developer release and not ready for production installations. As it matures, we will review the upgrade options.

I would like to write a module, how can I get started?

The development community around FreePBX is very active on the Freenode IRC channel #freepbx-dev and is usually the best way to get in contact with us directly. There is also a V3 Forum Thread and other options listed on our getting help page for developers.

I would like to see something new/changed in the core. How do I request that?

The core developers are constantly looking for feedback and are pretty quick at implementing any suggestions or solutions to problems in the core design. Please drop by the IRC channel for best results. We hope you'll be pleasantly surprised!

Why is FreeSWITCH supported before Asterisk?

FreePBX is designed to be engine agnostic. Doing the initial development against an engine other than Asterisk provided a new reference frame in assuring that the approach is really engine independent. Work on an Asterisk generator has already begun, and we would love to see developers familiar with Yate and other engines come forth to help drive those alternatives.

Won't the engine agnostic design limit FreePBX v3 to the most common denominator?

No. Being engine agnostic does not mean that all modules and features must run with all engines. We fully anticipate that modules will be written that address capabilities only available or very specific to a specific engine. For example, it would be very easy for a Queue Module be written that takes advantage of the very feature rich Queue Application in Asterisk, that would not be available today when running with other engines.

What license is used?

FreePBXv3 is based on the OSI Approved MPL v1.1 license. MPL is the well-known license for the thousands of open-source project including the popular Firefox project. It is a well supported license and is compatible with both Asterisk and FreeSWITCH's own licenses. It does not have any attribution requirements, unlike our initial CPAL license selection.

Isn' t there a conflict since FreePBX v2 is GPLv2 which is not compatible with MPL?

FreePBXv3 has been re-written from ground up. All the code is new so there is no conflict.

Why did FreePBX v3 change to a new license?

Most see the Mozilla Public License as a developer friendly, "weak" copyleft license that allow for proprietary code to be combined with MPL code in one program, or "larger work." Given the large base of VARs and resellers who build commercial solutions around FreePBX, it was seen as a better match for this project and the ecosystem that surrounds it.

If I write a module, does it need to be MPL?

No. FreePBX modules can be licensed however the original developer of such modules see fit. This is one of the advantages of the MPL license. This includes other Open Source licenses as well as any other license so long as that license doesn't itself have a conflict when being included within a larger work.

Can I make my own skin and how does the MPL license effect this?

FreePBX v3 is designed to be easily skinned. This has been a long requested feature on version 2 and has been built into v3 form the start. This means you can create a skin unique to your own business. We also hope it results in some great designs contributed back to the project. The MPL presents no obstacles. The attribution clause requires a small and minor display at the beginning of a session or in the form of a splash screen. It does not need to be displayed afterward and leaves all of the screen real estate in the GUI to design as you see fit.

Related Content