We work on an open source softswitch called FreeSWITCH http://www.freeswitch.org/
Blocked ports and content filtering can mess up Voice over IP traffic running on your broadband line which can be used as a free alternative to the "Digital Phone" services many providers offer. Some entire countries already do this type of thing like China for instance. There are ways around it using secure packets so the payload cannot be sniffed and other workarounds but it would be a huge pain if we had to do that inside the US.

We have an Open Source project called FreeSWITCH http://www.freeswitch.org/ that allows you to do this sort of thing with any computer running Windows MAC or most UNIX. It can be paired with traditional phones with a small analog adapter or a hardware telephony card from Sangoma http://www.sangoma.com./ But you could just get a software phone for free as well and play around with it.
 

When you create closed source code you have a much higher chance of flaws because your code can not tested nearly as much as open source can. As the leader of an open source project, FreeSWITCH http://www.freeswitch.org/ , I am fortunate to have a very large crowd of beta testers who help ensure our releases are as stable as they can be. If you are selling the application and never letting anyone see the source you run a very high risk of missing something in Q/A and releasing buggy software. When people pay for it the will get angry so I am not surprised such a suggestion is being made but I find it unpractical to enforce since if it "works right" is hard to judge in some cases besides maybe medical equipment or other situation where human lives are at stake. Blue screens of death are hardly an excuse to sue anyone.

Our project (FreeSWITCH) uses the MPL for the main application and BSD for satellite libraries that we create that can be used by other projects etc.

Once you decide to have open source code, it's more logical to stick with the fact that at least the core code is FREE and come up with ways to develop a product on top of it if you want to have something to sell. Otherwise it sounds like an "open source tax" and businesses do not like uncertainty. If they choose to use a code base they need to know it will always be available.

Yep, like i said, it's a shame, The idea is that we would use it in our project which is a telephony server that runs much better on 64bit, that's really the only show stopper from our being able to try it instead of the spidermonkey library we use now.

The whole point of open source is for projects to work together and combine their efforts to make better software. As I said I am the author of an open source software. It has over 300,000 lines of code of it's own then a large list of dependency libs that added up account for about 2.5 million lines of code see: http://fisheye.freeswitch.org/browse/FreeSWITCH A library developer makes a library for other people to use. Adding 64 bit support to someone else's library is an exercise best left to the lead developer since it's his decision to support it or not.

I was looking at using v8 in our open source soft-switch/pbx/telephony application server FreeSWITCH http://www.freeswitch.org/

We currently are using spidermonkey from Mozilla and it has it's ups and downs in the scalability department since it was not designed for thousands of concurrent sessions in a single process. The documentation for v8 was impressive but sadly, 64 bit is not supported. It would be nice to get 64 bit supported so we could experiment further with it because it looks really well written.