One of the most often-heard questions from the Adhearsion community has long been: "Do you guys support FreeSWITCH?". I joined the Adhearsion Project with a great desire for it to support FreeSWITCH, and since then we've been working towards making that happen. At the last <a href="http://adhearsion.com/conference">AdhearsionConf</a> we announced the future that was to become Adhearsion 2. A large part of that vision was the ability to write your voice application once, and then to enjoy the portability across any supported telephony engine. With the release of Adhearsion 2.0 back in April, we made a huge leap in that direction, adding first-class support for <a href="http://voxeolabs.com/prism">Voxeo PRISM</a>. Today, we are very happy to finally announce initial support for FreeSWITCH in Adhearsion.<br>
<br>I would also like to take a moment to share the philosophy behind the version numbers used by the Adhearsion team. We are big believers in <a href="http://semver.org/">SemVer</a>. To put it briefly: we accept the API promise and hold it sacred. Application developers should always feel confident upgrading versions of Adhearsion within a major number (eg. 2.0 to 2.1; even 2.0 to 2.9). We promise to make sure that Adhearsion remains perfectly backward compatible as long as the major version number remains the same. Anything else is a bug and we promise to fix it.<br>
<br>So today marks the release of Adhearsion 2.1.0. Take a moment and see some of the other exciting improvements we have made in addition to FreeSWITCH support by reading the <a href="https://github.com/adhearsion/adhearsion/blob/v2.1.0/CHANGELOG.md">Changelog</a>. As always, we appreciate bug reports on <a href="https://github.com/adhearsion/adhearsion/issues">Github Issues</a> and will be happy to answer questions or provide assistance on the <a href="http://groups.google.com/group/adhearsion">Adhearsion community mailing list</a>.<br>
<br>Regards,<br>Ben Langfeld