Welcome To FreeSWITCH
The World's First Cross-Platform Scalable FREE Multi-Protocol Soft Switch
FreeSWITCH is a scalable open source cross-platform telephony platform designed to route and interconnect popular communication protocols using audio, video, text or any other form of media. It was created in 2006 to fill the void left by proprietary commercial solutions. FreeSWITCH also provides a stable telephony platform on which many telephony applications can be developed using a wide range of free tools.
FreeSWITCH was originally designed and implemented by Anthony Minessale with the help of Brian West and Michael Jerris. All 3 are former developers of the popular Asterisk open source PBX. The project was initiated to focus on several design goals including modularity, cross-platform support, scalability and stability. Today, many more developers and users contribute to the project on a daily basis.
We support various communication technologies such as Skype, SIP, H.323 and GoogleTalk making it easy to interface with other open source PBX systems such as sipXecs, Call Weaver, Bayonne, YATE or Asterisk.
FreeSWITCH supports many advanced SIP features such as presence/BLF/SLA as well as TCP TLS and sRTP. It also can be used as a transparent proxy with and without media in the path to act as a SBC (session border controller) and proxy T.38 and other end to end protocols.
FreeSWITCH supports both wide and narrow band codecs making it an ideal solution to bridge legacy devices to the future. The voice channels and the conference bridge module all can operate at 8, 12, 16, 24, 32 or 48 kilohertz and can bridge channels of different rates. The G.729 codec is also available under a commercial license.
FreeSWITCH builds natively and runs standalone on several operating systems including Windows, Max OS X, Linux, BSD and Solaris on both 32 and 64 bit platforms.
FreeSWITCH supports FAX, both over audio and T.38, and can gateway between the two.
Our developers are heavily involved in open source and have donated code and other resources to other telephony projects including openSER, sipXecs, The Asterisk Open Source PBX and Call Weaver.
a Spec Sheet is available on our Wiki.
Our buddy Dan York has written a piece about Microsoft's assimilation acquisition of Skype. For better or for worse it is a done deal. I don't know about you but I must confess that I'm keeping my eye on this one. It could be great or it could be a train wreck. In either case I've got the popcorn ready...
We wanted to keep everyone informed of the schedule for upcoming FreeSWITCH training. Darren Schreiber, co-author of the FreeSWITCH book and CEO of the 2600hz project, is the lead instructor. There are beginner and advanced classes as well as a 5-day complete training. Visit VoIP.com for all the details. Also, don't forget that Darren and Company can also offer customized training suited to your specific business and technical needs. Contact them at email@example.com to obtain more information.
Thanks to Darren and all the great folks at 2600hz for helping to expand the reach of the FreeSWITCH community all over the world!
Those of you running Linux/Unix systems no doubt make use of the time zone database. Now it seems a foolish group of astrologers/software developers has actually sued the long-time maintainer of this database, among others. They claim that they have a copyright on the timezone data. All the selacious details are available in this Techdirt post. Keep your eyes open on this one, it should be interesting.
An interesting item just came across my desk. A post over at Boston Review talk's about Susan Landau's new book: Surveillance or Security?: The Risks Imposed by New Wiretapping Technologies. It is quite an interesting read. If you are at all interested in Internet security and privacy, especially with VoIP communications, I highly recommend reading this article.
We would like to let everyone know that the 2600hz team has more official FreeSWITCH training sessions here in the United States:
- Nov 7-9, 2011 in NYC
- Jan 18-20, 2011 in Austin, TX
Pricing, accommodations and other information is available on the VoIPKB website.
Last week Anthony Minessale added the new mod_sms into the FreeSWITCH tree. This module allows you to route SMS messages in a FreeSWITCH server. How does it work?
Mod_sms binds on the global event system and listens for MESSAGE events. When it catches a MESSAGE event it routes it to the new chatplan. The chatplan is to chat messages as the dialplan is to phone calls. The chatplan "routes" the message to the appropriate endpoint. If there is no match then the message is handled the way any other chat message would be, that is, it is simply a message directly from one client to another.
Special thanks to Seven Du who has started a nice wiki page for mod_sms. Please try out this new module and give us your feedback. We would love to hear ideas on how you are using this in a production environment and what problems you are solving with it.
Here is a nice blog post from SunTel Technologies. I thought you all might enjoy a nice read.
There is a Network World article with the following headline:
Linux Foundation chief: 'You are an idiot' if you don't give back to open source
The lede on the story is this:
Taking without contributing back to the upstream project defeats the benefit of open source and sooner or later, all open source users realize this, contends Jim Zemlin
After reading the whole article I think you'll agree that the title is pretty much just sensationalistic clickbait. However, Jim Zemlin does make an interesting argument about why it's important to give back to the open source projects that you use: It's in your business interest to do so. I think that makes a lot of sense. The usual mantra we hear (and often repeat ourselves) is, "Don't be a leech! Give back to the project that you downloaded for FREE." That mantra is probably still true. However, in a world where Open Source is big business it may not matter any more.
Consider the "money" quote from Jim Zemlin in the aforementioned article. Instead of giving back because it's "the right thing" to do there are business reasons to give back:
"It doesn't matter. I don't care if anyone contributes back... [It's] not the right thing to do because of some moral issue or because we say you should do it. It's because you are an idiot if you don't. You're an idiot because the whole reason you're using open source is to collectively share in development and collectively maintain the software. Let me tell you, maintaining your own version of Linux ain't cheap, and it ain't easy."
I like Jim's reasoning here. Normally the people who don't "give back" are considered "idiots" or "leeches" or a host of other colorful epithets. However, none of that really matters any more. Those who don't give back aren't idiots in the epithetical sense. Rather, they are idiots because they are running the risk of shooting themselves in the foot from a business perspective. If you use Open Source software in your business then a healthy Open Source project and community is good for business.The more heavily you rely on Open Source, the more you need healthy projects and communities. Giving something back to the community is an investment in your own business.
That brings up an interesting question: what, exactly, does it mean to "give back"?
What It Means To "Give Back"
The article cites Canonical (the Ubuntu folks) as an example of an entity that "doesn't give back." The basis for this claim is that Canonical isn't in the top 10 list of employers who contribute to the Linux kernel. According to the article, they're not even in the top 30 of employers who contribute to the Linux kernel. To some, this is damning evidence of "idiocy" on the part of Canonical: if you aren't making contributions to the kernel then you aren't "giving back." The list cites "number of changesets per employer" for the most recent quarter. It is foolish to use this metric as a proxy for how much a company "gives back." By this metric, Microsoft is a better Linux community member than Canonical! (Not to mention others who came in behind Microsoft this quarter: TI, Broadcom, Oracle, AMD, Nokia, Fujitsu, Google,...)
Since I live in the US I'll use an American football metaphor. Using "number of changesets per employer" as a metric for "how much they give back" is like using "number of yards gained" as a metric for how much a player "contributes" to his team's success. By this token, the members of the offensive line don't contribute, nor do the members of the defense, and all the special teams players aside from the kick returner. The fullback must be a slacker because he only carried the ball 3 times for a total 6 yards. What if he punched it in on 4th and goal from the 1 yard line? You get the idea. Yards gained is a valuable metric for certain players, but it isn't the only metric and certainly isn't the most important one. (Points scored, anyone?) By the same token, the number of changesets per employer is an important metric for seeing who's doing what in contributing to the Linux kernel. However, it is not a viable proxy for measuring how much someone "gives back" to a project.
Thankfully we hear from Jim Zemlin again. Regarding Canonical he states: "Just to be clear, Canonical staff, engineers, management are not idiots. They get open source well and as they grow, I think it will be in their business interests to give back."
I agree. Besides, there is a difference between "Linux" the kernel and "GNU/Linux" the complete operating system environment. The Linux kernel is like the Hemi engine running the automobile. The automobile doesn't do much without the engine, and the engine needs something to move. They work together. Giving back to the Linux ecosystem is every bit as important as contributing to the Linux kernel. Does anyone think that Canonical hasn't helped the Linux ecosystem? Of course, they have!
So, how can you give back to your favorite open source project? If you know how to write code then submitting patches is almost universally accepted as a way to give back. "Patches welcome" is not just a catch phrase. However, most of us are not skilled coders. We can give back in other ways. For example, the need for testing and documentation is ubiquitous. If you know how to check out a piece of software and run it through its paces then please do so. Find out how your favorite project's bug tracking system works. FreeSWITCH uses Jira. Most developers will tell you that a well-researched, detailed bug report is a godsend. Many developers spend an inordinate amount of time trying to decipher and reproduce bugs that are reported. A useful skill to develop to help them out is to be a "bug marshal" - someone who reads bug reports and verifies them by trying to reproduce the symptoms.
You can also help out by getting involved in the community. Most communities have a mailing list and a community knowledge store called a wiki. FreeSWITCH uses MediaWiki. Some projects have a community forum. Get connected with your community. Read the mailing list posts and answer the easy questions that you know. Join the IRC channel if your community has one. This is a great way to connect with others who share your interest in an open source project. The experts will help you when you are a noob and after you learn a bit you'll be in a position to help the next newbie. (Remember how it felt the first time you asked a question in IRC or on the mailing list?) Developing a thriving community is a great way to keep an Open Source project healthy.
If you really want to help out then consider donating money or buying a developer something from his or her wishlist. Send them a gift card from Starbucks or Amazon.com. Find a way to give them a personal "thank you" - they appreciate what you do and they will definitely be more inclined to help you the next time you have a question.
The moral of the story: don't be an "idiot"! Giving back to your Open Source project helps everyone, yourself included.