About

Conventions

The FreeSWITCH™ numbering format is "version.release.maintenance". The release numbering convention is even numbers for current public releases and odd numbers for development branches.

Selecting a Version

The primary FreeSWITCH™ releases are: Current public release, recommended for production systems. Current branch, contains in-test fixes since the current public release, intended as the next maintenance release. Master development,containing the latest fixes and features, intended as the next major release.

A Note About Bugs and Issues

If you find bugs or issues with the current public release, they must be tested using the latest Master because it's possible the problem was fixed. Also, the developers require all bugs to be tested using the latest Master before considering any bug reports.

If you're using
FreeSWITCH™ version 1.6 which is tagged End Of Life, you should upgrade to 1.8 NOW.

Download Current Public Release

The current public version/release of FreeSWITCH™ recommended for production systems is 1.8, created 31 July, 2018 followed by maintenance levels. The current release of sounds and prompts is 1.0.51 as of 9 October, 2014.

The latest maintenance level of the current public version of FreeSWITCH™ can be downloaded from freeswitch-files via a browser. If you're using linux it's much easier to copy/paste the long command line below. This single line performs: 1- Determines the latest public release available. 2- Downloads the compressed source file. 3- Decompresses the file into a folder in the current directory. 4- Renames the folder to freeswitch. If you don't want the folder renamed remove the last && to the end of the line.

Download Current Branch

The current branch contains fixes going into the next maintenance level for the release. Download the current branch using the -b argument followed by 'v' concatenated with the release number. The git command creates the freeswitch directory and downloads the FreeSWITCH™ source files, replace # with the release number.

Download Master Development

Themaster development releasecontains the latest fixes and features going into the next release. Download the latest master release using the "git clone" command below which creates the freeswitch directory and downloads the FreeSWITCH™ master development source files.

FreeSWITCH Adavantage

FreeSWITCH Advantage Support

The FreeSWITCH Advantage provides commercial-grade support services based on a trouble-free installation package to get you up and running quickly and profitably.

Centos 7 Package (FreeSWITCH 1.6)

Windows

The binary MSI installer is built each weekend from Git head, includes default modules and 8KHz sounds, and is available for both x86 (32-bit) and x64 (64-bit).

Compiling Master Source Code

If you require the very latest features or patches or wish to hack FreeSWITCH you may compile from source code. FreeSWITCH™ is available for source compilation on Unix and Linux distributions as well as Windows.

Debian 8 Jessie Source

FreeSWITCH™ 1.6 depends on a number of libraries included with Debian 8, which is now the distribution of choice for FS core development team. Follow the instructions on the Debian 8 Jessie page; refer to Debian Post-Install Tasks for finishing touches.

macOS

The comprehensive macOS guide contains instructions for setting up FreeSwitch™ on a Mac with features such as autostart, emailing voicemails and log management.

OpenBSD

Smartos

Updating Binaries

In version 1.4 the names of a number of configuration settings were changed, so you can not simply use old config files on your new
FreeSWITCH™ binaries.

Settings of the form sip_*_media have become rtp_*_media because they properly control RTP media streams, SIP has nothing to do with them.

For example, sip_secure_media is now called rtp_secure_media.

Deprecated Instructions

Deprecated Packages

FreeSWITCH™ is developed on Debian 8 "Jessie" which is the much preferred platform. These instructions for older operating systems are maintained as a courtesy, but are unlikely to work without a great deal of effort.

13 Comments

There were some individuals porting FreeSWITCH over to RPi. I don't know how the recent FS 1.6 changes affect that effort, however. Many of the changes in FS 1.6 involved switching to system libraries in Debian 8 along with greatly improved video conferencing support. Since an RPi is not up to the task of video processing I'm guessing you could omit much of that if you want to stay current with FS 1.6 or use the 1.4 branch.

FS is a modular system so you are not required to build every last piece, especially the extensive video components that come with 1.6 version. If you trim down what you build to the bare essentials there's no reason it should not run on RPi.

These wiki comments don't see much exposure, so you're much better off asking on the Freeswitch-users mailing list. I know there is interest out there, but it is up to those who have the interest and expertise in RPi to take the ball and run with it. I'm pretty sure the core team doesn't have the wherewithal to port FS to RPi or other architectures as they have their hands full just getting things right with Debian

I dug into the deps-most package found in the 1.6 installation instructions and attempted to manually install each of them. Out of 47 dependencies, I found 11 of them were not available in the raspbian repos. These are the packages that were not available.

Can you offer any advice on how to determine which modules depend on these? I've searched a few in confluence and have found one reference to libyuv in mod_fsv, but I'm thiking there's got to be a better way to check if these are things I must have.

The core team is working to update the Windows build system. God bless them since there are MANY changes that must be incorporated into the Windows libraries. The FreeSWITCH-users mailing list has the latest on that while it's underway.

Seeing how http-cache is now getting installed together with freeswitch-config-vanilla it would be awesome to see http-cache included in default Windows install package as well, do you have any comment on that?