Page tree
Skip to end of metadata
Go to start of metadata

About


This page describes FreeSWITCH™ numbering conventions, basic download instructions, and directions to useful installation pages. 

 Click to expand Table of Contents

Conventions

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

Current Production

The current production version/release of FreeSWITCH™ recommended for production systems is 1.6, created 8 September, 2015 followed by maintenance levels. The current release of sounds and prompts is 1.0.51 as of 9 October, 2014 .

If you're using FreeSWITCH™ version 1.4 which is tagged End Of Life, you should upgrade to 1.6 NOW. If you find bugs or issues with 1.6, please file a JIRA ticket.

The latest maintenance level of the current production version of FreeSWITCH™ can be downloaded 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 stable production 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.

A Note About Bugs and Issues

The developer team only considers bug reports if the bug was first tested using the latest Master branch because it's very possible the problem was fixed.

Master Development

The master development release contains the latest fixes and features going into the next release. The current branch contains fixes going into the next maintenance level for the release. If there are problems with the stable production version, the developers will request that you install the master version or current branch for diagnosis.

Download the master version using the first "git clone" command below. Download the current branch using the -b argument followed by 'v' concatenated with the release number, see the second command below. The git command creates the freeswitch directory and downloads the FreeSWITCH™ 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.

Full details available at freeswitch.com

If you're new to FreeSWITCH™ consider purchasing the Mastering FreeSWITCH™ book and be sure to read this introductory article: http://www.linuxpromagazine.com/Issues/2009/106/TALK-SOFT.

 

Installation Methods

Easy Way

The easiest way to get FreeSWITCH™ is to install the package for your operating system. Pre-built binaries are available for installation on some Linux and Unix distributions as well as Windows.

Debian 8 Package (FreeSWITCH 1.6)

Debian 8 Jessie (preferred) The development team uses and builds against Debian 8 "Jessie". They recommend Debian because of its stable, yet updated, kernel and wide support. 

Centos 7 Package (FreeSWITCH  1.6)

CentOS 7 and RHEL 7

Windows

Freeswitch Installer .msi

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

Special notes for building from source on OpenBSD.

Smartos

Recently updated installation guide for SmartOS


Updating Binaries

Config Changes

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.

Debian 7 Package (FreeSWITCH 1.4)

Debian Wheezy Package

CentOS 6 Package

rpm -Uvh http://files.freeswitch.org/freeswitch-release-1-0.noarch.rpm
yum install freeswitch-config-vanilla
yum install sox freeswitch-sounds*

Enjoy FreeSWITCH!

Deprecated Compiling From Source Code

These deprecated instructions are FreeSWITCH you may compile from source code. FreeSWITCH™ is available for source compilation on Unix and Linux distributions as well as Windows.

Debian 7 Source

Makefile that builds FreeSWITCH™ including libraries and build dependencies.

CentOS 6 Source

Makefile that builds FreeSWITCH™ including libraries and build dependencies.

Unix Variants

Mac OS X

Instructions for non-supported OS X systems can be found at Mac OS X Archive.

Windows

Compile with Visual Studio.

13 Comments

  1. yum install freeswitch

    Enjoy FreeSWITCH!

    --

    From what repo? base, epel -  not found

  2. Any current instructions for Raspberry PI?

    1. 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.

    2. Ask and ye shall receive!

      Raspberry Pi

      1. As far as I can tell, 1.6 means the end of hosting FS on R-Pi.  In fact, there are no packages for arm in the repo.  Guess I'll have to buy a NUC.  

        1. A core motto of FreeSWITCH is: "Don't glue the Lego pieces together"

          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 (smile)

          1. John,

            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.  

            libpng16-dev
            libvpx2-dev | libvpx-dev (>= 1.4.0)
            libyuv-dev
            libbroadvoice-dev
            libcodec2-dev
            libflite-dev
            libg7221-dev
            libilbc-dev
            libsilk-dev
            libsngtc-dev
            libmongoc-dev

            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.

  3. the windows binary listed above never seem to be updated since January 2015

    1. 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.

      1. how about add a wiki on compile with VS so others know if the sdk and other tools required to build FS 1.6

      2. 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?

        1. Since Windows is not the core target environment, the core development team welcomes a Pull Request to include the necessary modules. (smile)