What’s the plan for making sure critical (security) changes get patched into this version?

From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Chad Vogel
Sent: Friday, October 28, 2011 7:44 PM
To: FreeSWITCH Users Help
Subject: Re: [Freeswitch-users] Feedback

I had a couple of my developers work full time of converting FS for the last several weeks however on the VoiceXML / SCXML took a few months to develop and was part of another project we developed but it was in C++/CLR – this is really why we converted the FS core. Now being in the CLR it’s really natural to take advantage of the existing namespaces for: regex, xml, configuration and SQLClient, this allows us to shrink the code that needs to be upgraded, a cleaner interface for module development, advantages of garbage collection and being managed code means having a vaster library of development options. Also we didn’t bother converting many modules with our build; we only have mod_sofia, mod_loopback, mod_spandsp and mod_dialplan_xml. We will be developing our proprietary modules and client - licensing them to enterprises.

On Oct 28, 2011, at 5:02 PM, Henry Huang wrote:

Only started a few weeks and you have so many things hacked(in good terms) does make me a little skeptical. And I have the same question as Michael, why make it work with windows? Isn't the sole purpose is just have a nice .Net interface? Don't see other advantages making it run production on windows.

Henry

On Sat, Oct 29, 2011 at 2:55 AM, Chad Vogel <cvogel@lyonl.com> wrote:

Hello,

I wanted to reach out and get some feedback from everyone because my company started a project using FS as base several weeks ago, our goal was to optimize and integrate FS more directly into Windows environments. Here is my question, we would like to share our changes and where should we host our project? Because we understand our build breaks compatibility with the UNIX environments and fails to meet the objectives cross platform compatibility, however it could contribute greatly and be beneficial to other windows users.

Here are some of the changes we have made:

We converted FS core to C++ and having it compiling to .NET 4.0 CLI
FS now runs inside its own namespace
We replace FS_CLI with a PowerShell shell app
Supports SQL Server support via the Native SQL Server Client API
Support for windows clustering (up to 32 node active/active cluster)
Ties more directly into the Win32 API and has less reliance on open source Libs
Replaces OpenSSL sockets with Windows encrypted sockets
Added windows performance monitoring
No longer need to use mod_managed for managed modules
Memory management relies on .Net garbage collection
Added support for Microsoft Speech
VoiceXML 3.0 and SCXML support
No longer supports JS, LUA, PHP development - Modules can be only developed in .NET, C or C++( we feel support for other languages can be added back in but falls outside the scope of our objectives at this time, support for SCXML should make limit the need for other scripting languages)
Fixed RTP clock timing issues in virtualized environments
New configuration file format using .Net App Configuration files (kind of looks like an IIS config file)

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org