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 mod_vpx.so 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.

Installing From Debian Packages

Latest Release Branch:

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.

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 installedE: Unable to correct problems, you have held broken packages.

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.

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: