Wow! The crew working on Freeswitch are certainly pushing forward. Michael Collins just post a notice of the availability of v1.0.3 which includes 127 fixes & changes. A couple of the more interesting include leveraging the Digium TC400B hardware for multi-channel G.729a and G.723.1 transcoding, also AMR-WB passthough.
Kristian K of Star2Star and Astlinux fame has also worked to make Freeswitch compile within the Astlinux development environment. So you can have a high-performance SIP proxy and Asterisk running on small format embedded hardware. OMG, I love that!
Since Freeswitch is now an installable module for pfsense you could also have it running on your router. That’s great, too!
According to the pfSense blog there’s been an effort to implement Freeswitch as an installable package to pfSense. This is very interesting. There’s a long list of comments to the blog post which collectively spell out some of the merits of this idea, as well as how it relates to running an IP-PBX inside the LAN.
Some indicate a preference for Asterisk over Freeswitch. Others ask for a lightweight configuration supporting just a SIP proxy to an inside PBX. It’s noted that Freeswitch is a much larger application than siproxd, which would handle that well enough.
I’ve been considering giving pfSense a try. This is just one more good reason to make the effort some time soon.
However, Manuel Kasper (m0n0wall project lead) had some interesting ideas on how to revise and perhaps simplify my approach. What he describes departs from the approach underlying the present implementation of the Magic Shaper in m0n0wall. Use of the Magic Shaper is the basis of the existing screencast.
Updated to provide a YouTube version in the post and ftp downloadable high quality version.
After several months of thinking about it I finally got around to recording a screencast tutorial about setting up the traffic shaping feature in m0n0wall to accommodate VOIP traffic. Phillip Cooper’s series of screencasts were the inspiration for this. In going though his work (thank you!) it occurred to me that documenting the settings that allow my VOIP systems might be useful to others.
I have a new (ish) Comcast cable modem service here in my office, which gave me a testbed to setup another router and go through the setup process from scratch.
The finished screencast is not online yet. I’ve passed it to the m0n0wall project leads for comment & revision before making it public. It should be available in the next few days.
I’m not a typical user. I’m an early adopter. I don’t mind putting in some effort to making something work up to its promised potential. I also like open source, but I just don’t see the value in running 3rd party software on a hobbled router platform. It’s just not good use of my time.
Jared Valentine has posted an interesting description of a system he developed for automatically manipulating QoS & bandwidth allocation to support the use of VOIP over his DSL service. He calls this “Application Aware Triggered QoS.”
He described his initial problem as being trouble with inbound bandwidth management. This is something that I’ve never experienced myself. My trouble was always related to limited outbound bandwidth.