Adhearsion and FreeSWITCH: It’s About Time

One of the most often-heard questions from the community has long been: “Do you guys support FreeSWITCH?”  From the time I first took over as head of the Adhearsion Project and went on stage publicly to talk about the future of Adhearsion, we have wanted to make that happen.  At the last AdhearsionConf 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 FreeSWITCHany 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 Voxeo PRISM.  Today, I am very happy to finally announce initial support for FreeSWITCH in Adhearsion.

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

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 Changelog.  As always, we appreciate bug reports on Github Issues and will be happy to answer questions or provide assistance on the Adhearsion community mailing list.

Subscribe to our mailing list

* indicates required
I want to read about...
Email Format

What do you think?