Call Us Today! 877.742.2583

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


Please NOTE that Debian 9 “Stretch” is now officially supported by FreeSWITCH™ .


Debian 8 "Jessie" was the reference platform for FreeSWITCH™ as of version 1.6. We recommend Debian 9 "Stretch" as it's most suitable for the FreeSWITCH™1.8 release.

 Click here to expand Table of Contents
echo "deb jessie-backports main" >> /etc/apt/sources.list


2016.02.14 — Please note this important change that went into Master today. As of today, we are no longer using system versions of libyuv and libvpx due to major conflicts with system versions of these libraries.  These are now built static into the freeswitch core.  Also note, mod_vpx no longer exists, it is automatically loaded as part of the core and you will no longer have nor have to load it manually.  I'll have more details coming, but let me know if you have any questions. 

Please note for anyone doing cross compiling, this probably means a bit more work for you, I'll be working on fixing that this week.

- Mike Jerris

Commit Log

See all FreeSWITCH commits here:

Easy Way

Installing From Debian Packages

Latest Release Branch:

Release package

FreeSWITCH™ is now installed and can be accessed with

FreeSwitch CLI

Master Branch ("git"):

WARNING not suitable for production

Master Test Package


Building Debian Packages From Master Branch

WARNING not suitable for production

The master branch depends on different libraries which are not available as packages in Debian distribution, but are available from FreeSWITCH repository. Thus, you will need internet access to the FreeSWITCH DEB repository.

Build your own .deb Master package


Compiling from source code

Building From Source

Compiling Release Branch (production)

Release source build


Compiling Latest Master (for testing)

WARNING not suitable for production

Master source build

Before Starting FreeSWITCH

If you built FreeSWITCH™ from source code you should set file permissions and ownership before starting FreeSWITCH. Follow the post-installation instructions.



Quick Start FreeSWITCH Demo With Verto Communicator

WARNING not suitable for production

Script FreeSWITCH demo install


  1. What's the different between freeswitch-meta-all and freeswitch-all package ?

    1. nothing really, -meta-all points is effectively an alias for -all
      -all installs pretty much everything

  2. echo "deb jessie main" > /etc/apt/sources.list.d/freeswitch.list

    Above line is breaking my "apt-get update"  functionality with below errors, as its using SHA1 algo, instead of SHA256.

    Error -1: 

    W: GPG error: xenial InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 018DDB2EF14D5181
    W: The repository ' xenial InRelease' is not signed.
    N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
    N: See apt-secure(8) manpage for repository creation and user configuration details.


    Then i added the key into gpg with below command

    apt-key adv --keyserver --recv-keys D76EDC7725E010CF


    Error-2: After adding the key got below error

    W: Signature by key 20B06EE621AB150D40F6079FD76EDC7725E010CF uses weak digest algorithm (SHA1)


    apt-get install -y freeswitch-meta-all nginx-extras freeswitch-mod-verto freeswitch-mod-rtc

    The following packages have unmet dependencies:
    freeswitch-meta-all : Depends: freeswitch-meta-codecs (= 1.6.15~32~bec4538-1~jessie+1) but it is not going to be installed
    Depends: freeswitch-mod-av (= 1.6.15~32~bec4538-1~jessie+1) but it is not going to be installed
    Depends: freeswitch-mod-soundtouch (= 1.6.15~32~bec4538-1~jessie+1) but it is not going to be installed
    Depends: freeswitch-mod-spandsp (= 1.6.15~32~bec4538-1~jessie+1) but it is not going to be installed
    Depends: freeswitch-mod-perl (= 1.6.15~32~bec4538-1~jessie+1) but it is not going to be installed
    E: Unable to correct problems, you have held broken packages.

  3. So I installed verto with no errors, and it's running on my secure site. Can anyone please tell me how to get a secure web socket (wss) connection? Netstat shows my server is listening on wss port 8082 but connection is rfefused both firefox & chrome, and I did restart fs many times, nginx too.

    The port is open in my firewall so i am stuck on what to try next.

    Going to research on using SIP TLS and not use wss to see if I can connect

    1. Looks like you are trying to connect Verto Communicator to mod_sofia's WSS.... you need to setup mod_verto....


  4. I think these parts in the Master and Release source build sections are over the top!

    You really shouldn't tell people to change their global config...

    I'd put it like that



  5. Hi Folks,

    i have install free switch successfully and i'm trying to implement HA as well, but i want to know how to stop free-switch being automatically start.

  6. hi,

    after install, the default wss.pem gives error, so to test verto communicator with a custom certificate (i think this info is around here) if testing in local without a public domain to use lets encrypt:

    mkdir /root/ssl

    cd /root/ssl

    openssl req -newkey rsa:2048 -nodes -keyout key.pem -x509 -days 365 -out certificate.pem

    #TIP: put in common name the ip address, so when testing you only have the warning for invalid

    cat key.pem certificate.pem > /usr/local/freeswitch/certs/wss.pem


    #enable or replace in nginx ssl options for /etc/nginx/sites-enabled/default

    ssl_certificate /root/ssl/certificate.pem;

    ssl_certificate_key /root/ssl/key.pem;


    #vc into www,

    cp -a /usr/src/freeswitch/html5/verto/verto_communicator/dist/* /var/www/html/


    hope it helps others (smile)

  7. I wanted to do video conferencing using the free switch. I am a new user can anyone guide me to do that