Hi I have made a number of fixes and additions to mod_mono/mod_mono_managed so that: - It builds on Linux (non-managed and managed parts) - It works when FreeSWITCH is embedded in a Mono program. I'd like to submit these changes to the project - how would I do that? Raise a Jira item? The versioning of the SWIG-generated files (mod_mono/freeswitch_wrap.cxx and mod_mono_managed/swig/*.cs) is problematic - since mod_mono managed attempts to wrap the entire core FreeSWITCH library, when the library functions change, then the mod_mono SWIG should be run again. Otherwise, mod_mono may try to call functions that have changed their interface (though perhaps that is rare). So it would be ideal if the SWIG stage were just part of the FreeSWITCH build. Is it safe to assume that SWIG is available when building FreeSWITCH? Perhaps it is is used in other modules? Cheers David 360CRM Limited, registered address, Caledonia House, 89 Seaward Street, Glasgow, G41 1HJ, Registered in Scotland, company number SC261952. This email and its attachments may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of 360CRM Ltd. This email does not form any part of a contract. If you are not the intended recipient of this email and its attachments, you must take no action based upon them, nor must you copy or show them to anyone. Please contact the sender if you believe you have received this email in error.
start with a jira and visit us on irc and maybe we can get you either a branch or commit to trunk on mod_mono On Thu, Sep 4, 2008 at 8:23 AM, David Brazier <David.Brazier@360crm.co.uk>wrote:
Hi
I have made a number of fixes and additions to mod_mono/mod_mono_managed so that: - It builds on Linux (non-managed and managed parts) - It works when FreeSWITCH is embedded in a Mono program.
I'd like to submit these changes to the project - how would I do that? Raise a Jira item?
The versioning of the SWIG-generated files (mod_mono/freeswitch_wrap.cxx and mod_mono_managed/swig/*.cs) is problematic - since mod_mono managed attempts to wrap the entire core FreeSWITCH library, when the library functions change, then the mod_mono SWIG should be run again. Otherwise, mod_mono may try to call functions that have changed their interface (though perhaps that is rare). So it would be ideal if the SWIG stage were just part of the FreeSWITCH build. Is it safe to assume that SWIG is available when building FreeSWITCH? Perhaps it is is used in other modules?
Cheers
David
360CRM Limited, registered address, Caledonia House, 89 Seaward Street, Glasgow, G41 1HJ, Registered in Scotland, company number SC261952. This email and its attachments may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of 360CRM Ltd. This email does not form any part of a contract. If you are not the intended recipient of this email and its attachments, you must take no action based upon them, nor must you copy or show them to anyone. Please contact the sender if you believe you have received this email in error.
_______________________________________________ Freeswitch-dev mailing list Freeswitch-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ AIM: anthm MSN:anthony_minessale@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> iax:guest@conference.freeswitch.org/888 googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:213-799-1400
Hi David, Thanks, this sounds great. Today we did a few minor updates to the VS projects and the win32 swig batch file. You can email me, get me on IRC sometimes (michaelgg), or IM me on my site (www.atrevido.net). I'd be happy to work on getting these committed. -Michael ________________________________________ From: freeswitch-dev-bounces@lists.freeswitch.org [freeswitch-dev-bounces@lists.freeswitch.org] On Behalf Of David Brazier [David.Brazier@360crm.co.uk] Sent: Thursday, September 04, 2008 7:23 AM To: freeswitch-dev@lists.freeswitch.org Subject: [Freeswitch-dev] mod_mono Build Hi I have made a number of fixes and additions to mod_mono/mod_mono_managed so that: - It builds on Linux (non-managed and managed parts) - It works when FreeSWITCH is embedded in a Mono program. I'd like to submit these changes to the project - how would I do that? Raise a Jira item? The versioning of the SWIG-generated files (mod_mono/freeswitch_wrap.cxx and mod_mono_managed/swig/*.cs) is problematic - since mod_mono managed attempts to wrap the entire core FreeSWITCH library, when the library functions change, then the mod_mono SWIG should be run again. Otherwise, mod_mono may try to call functions that have changed their interface (though perhaps that is rare). So it would be ideal if the SWIG stage were just part of the FreeSWITCH build. Is it safe to assume that SWIG is available when building FreeSWITCH? Perhaps it is is used in other modules? Cheers David 360CRM Limited, registered address, Caledonia House, 89 Seaward Street, Glasgow, G41 1HJ, Registered in Scotland, company number SC261952. This email and its attachments may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of 360CRM Ltd. This email does not form any part of a contract. If you are not the intended recipient of this email and its attachments, you must take no action based upon them, nor must you copy or show them to anyone. Please contact the sender if you believe you have received this email in error. _______________________________________________ Freeswitch-dev mailing list Freeswitch-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
Michael & All That's good - those updates do tidy up the SWIG bit. After updating I had a couple of Windows problems: 1. When linking mod_mono, all the FS core lib symbols were undefined - I had to add FreeSwitchCoreLib as a reference. 2. Because I had just installed Mono 2.0 and still had Mono 1.9.1, the FindFirstFile in setMonoDirs() was finding Mono-1.9.1 first and then all the assemblies were wrong. So I just changed line 111 to find %PROGRAMFILES%\Mono - which you're now saying must be where the Mono you want is installed: switch_snprintf(findPath, MAX_PATH, "%s\\Mono", progFilesPath); But actually all the FindFirstFile stuff isn't needed at all now, is it? I've revisited my changes and put patches on http://jira.freeswitch.org/browse/MODLANG-83. Regards David 360CRM Limited, registered address, Caledonia House, 89 Seaward Street, Glasgow, G41 1HJ, Registered in Scotland, company number SC261952. This email and its attachments may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of 360CRM Ltd. This email does not form any part of a contract. If you are not the intended recipient of this email and its attachments, you must take no action based upon them, nor must you copy or show them to anyone. Please contact the sender if you believe you have received this email in error.
Hi David, Good point about FindFirstFile not working. While we'll require Mono to be symlinked for building, I'm not sure it should be a requirement for deployment. What do you think? It'll probably be better, now that we only support 2.0+, to have a more intelligent Mono directory probe. -Michael -----Original Message----- From: David Brazier [mailto:David.Brazier@360crm.co.uk] Sent: Monday, September 15, 2008 9:08 AM To: freeswitch-dev@lists.freeswitch.org Cc: Michael Giagnocavo Subject: RE: mod_mono Build Michael & All That's good - those updates do tidy up the SWIG bit. After updating I had a couple of Windows problems: 1. When linking mod_mono, all the FS core lib symbols were undefined - I had to add FreeSwitchCoreLib as a reference. 2. Because I had just installed Mono 2.0 and still had Mono 1.9.1, the FindFirstFile in setMonoDirs() was finding Mono-1.9.1 first and then all the assemblies were wrong. So I just changed line 111 to find %PROGRAMFILES%\Mono - which you're now saying must be where the Mono you want is installed: switch_snprintf(findPath, MAX_PATH, "%s\\Mono", progFilesPath); But actually all the FindFirstFile stuff isn't needed at all now, is it? I've revisited my changes and put patches on http://jira.freeswitch.org/browse/MODLANG-83. Regards David 360CRM Limited, registered address, Caledonia House, 89 Seaward Street, Glasgow, G41 1HJ, Registered in Scotland, company number SC261952. This email and its attachments may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of 360CRM Ltd. This email does not form any part of a contract. If you are not the intended recipient of this email and its attachments, you must take no action based upon them, nor must you copy or show them to anyone. Please contact the sender if you believe you have received this email in error.
Michael Could look in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Mono\2.0? Please thanks Mario for his help - in the end, I tried compiling Mono 2.0 on another similar box and it worked, so there must be something messed up on the development box I was using. David -----Original Message----- From: Michael Giagnocavo [mailto:mgg@giagnocavo.net] Sent: 15 September 2008 20:11 To: David Brazier; freeswitch-dev@lists.freeswitch.org Subject: RE: mod_mono Build Hi David, Good point about FindFirstFile not working. While we'll require Mono to be symlinked for building, I'm not sure it should be a requirement for deployment. What do you think? It'll probably be better, now that we only support 2.0+, to have a more intelligent Mono directory probe. -Michael -----Original Message----- From: David Brazier [mailto:David.Brazier@360crm.co.uk] Sent: Monday, September 15, 2008 9:08 AM To: freeswitch-dev@lists.freeswitch.org Cc: Michael Giagnocavo Subject: RE: mod_mono Build Michael & All That's good - those updates do tidy up the SWIG bit. After updating I had a couple of Windows problems: 1. When linking mod_mono, all the FS core lib symbols were undefined - I had to add FreeSwitchCoreLib as a reference. 2. Because I had just installed Mono 2.0 and still had Mono 1.9.1, the FindFirstFile in setMonoDirs() was finding Mono-1.9.1 first and then all the assemblies were wrong. So I just changed line 111 to find %PROGRAMFILES%\Mono - which you're now saying must be where the Mono you want is installed: switch_snprintf(findPath, MAX_PATH, "%s\\Mono", progFilesPath); But actually all the FindFirstFile stuff isn't needed at all now, is it? I've revisited my changes and put patches on http://jira.freeswitch.org/browse/MODLANG-83. Regards David 360CRM Limited, registered address, Caledonia House, 89 Seaward Street, Glasgow, G41 1HJ, Registered in Scotland, company number SC261952. This email and its attachments may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of 360CRM Ltd. This email does not form any part of a contract. If you are not the intended recipient of this email and its attachments, you must take no action based upon them, nor must you copy or show them to anyone. Please contact the sender if you believe you have received this email in error.
This is looking great. I tried building on Linux but runswig.sh the Makefiles I had put in the patch had got their format messed up. So the runswig.sh needs dos2unix run over it & chmod +x. And I've re-worked the Makefiles (below) so hopefully they fit in with the standard build a bit better. ***mod_managed/Makefile*** #MOD_CFLAGS=`pkg-config --cflags --libs mono` MOD_CFLAGS=-D_REENTRANT -pthread -I/opt/mono-1.9/lib/pkgconfig/../../include/mono-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -lmono #LDFLAGS=`pkg-config --libs mono` BASE=../../../.. VERBOSE=1 include $(BASE)/build/modmake.rules LOCAL_OBJS=freeswitch_managed.o freeswitch_wrap.o local_depend: $(LOCAL_OBJS) freeswitch_managed.o: freeswitch_managed.h freeswitch_managed.cpp freeswitch_wrap.o: freeswitch_wrap.cpp freeswitch_wrap.cpp: freeswitch_wrap.cxx cp freeswitch_wrap.cxx freeswitch_wrap.cpp local_depend: cd managed && make local_install: $(MODINSTDIR)/libmod_managed.so cd managed && make MODINSTDIR=$(MODINSTDIR) install $(MODINSTDIR)/libmod_managed.so: ln -s $(MODINSTDIR)/mod_managed.so $(MODINSTDIR)/libmod_managed.so local_uninstall: rm -fr $(MODINSTDIR)/libmod_managed.so cd managed && make MODINSTDIR=$(MODINSTDIR) uninstall local_clean: cd managed && make clean ***mod_managed/managed/Makefile*** all: mod_managed_lib.dll clean: rm -fr mod_managed_lib.dll mod_managed_lib.dll: Loader.cs ManagedSession.cs ApiFunction.cs AppFunction.cs Extensions.cs Log.cs Demo.cs swig.cs gmcs -target:library -out:mod_managed_lib.dll -d:DEBUG Loader.cs ManagedSession.cs ApiFunction.cs AppFunction.cs Extensions.cs Log.cs Demo.cs swig.cs install: mod_managed_lib.dll install mod_managed_lib.dll $(MODINSTDIR) uninstall: rm -f $(MODINSTDIR)/mod_managed_lib.dll 360CRM Limited, registered address, Caledonia House, 89 Seaward Street, Glasgow, G41 1HJ, Registered in Scotland, company number SC261952. This email and its attachments may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of 360CRM Ltd. This email does not form any part of a contract. If you are not the intended recipient of this email and its attachments, you must take no action based upon them, nor must you copy or show them to anyone. Please contact the sender if you believe you have received this email in error.
David, that module is not "quite" ready for prime time just yet, we are still sorting a few differences between native .net clr and mono but when thats complete, we will get rid of mod_mono. Thanks for the build stuff, I'll get that merged in today. Mike On Sep 26, 2008, at 10:40 AM, David Brazier wrote:
This is looking great. I tried building on Linux but runswig.sh the Makefiles I had put in the patch had got their format messed up. So the runswig.sh needs dos2unix run over it & chmod +x. And I've re- worked the Makefiles (below) so hopefully they fit in with the standard build a bit better.
***mod_managed/Makefile*** #MOD_CFLAGS=`pkg-config --cflags --libs mono` MOD_CFLAGS=-D_REENTRANT -pthread -I/opt/mono-1.9/lib/pkgconfig/../../ include/mono-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -lmono #LDFLAGS=`pkg-config --libs mono` BASE=../../../.. VERBOSE=1 include $(BASE)/build/modmake.rules LOCAL_OBJS=freeswitch_managed.o freeswitch_wrap.o local_depend: $(LOCAL_OBJS)
freeswitch_managed.o: freeswitch_managed.h freeswitch_managed.cpp
freeswitch_wrap.o: freeswitch_wrap.cpp
freeswitch_wrap.cpp: freeswitch_wrap.cxx cp freeswitch_wrap.cxx freeswitch_wrap.cpp
local_depend: cd managed && make
local_install: $(MODINSTDIR)/libmod_managed.so cd managed && make MODINSTDIR=$(MODINSTDIR) install
$(MODINSTDIR)/libmod_managed.so: ln -s $(MODINSTDIR)/mod_managed.so $(MODINSTDIR)/ libmod_managed.so
local_uninstall: rm -fr $(MODINSTDIR)/libmod_managed.so cd managed && make MODINSTDIR=$(MODINSTDIR) uninstall
local_clean: cd managed && make clean
***mod_managed/managed/Makefile*** all: mod_managed_lib.dll
clean: rm -fr mod_managed_lib.dll
mod_managed_lib.dll: Loader.cs ManagedSession.cs ApiFunction.cs AppFunction.cs Extensions.cs Log.cs Demo.cs swig.cs gmcs -target:library -out:mod_managed_lib.dll -d:DEBUG Loader.cs ManagedSession.cs ApiFunction.cs AppFunction.cs Extensions.cs Log.cs Demo.cs swig.cs
install: mod_managed_lib.dll install mod_managed_lib.dll $(MODINSTDIR)
uninstall: rm -f $(MODINSTDIR)/mod_managed_lib.dll
360CRM Limited, registered address, Caledonia House, 89 Seaward Street, Glasgow, G41 1HJ, Registered in Scotland, company number SC261952. This email and its attachments may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of 360CRM Ltd. This email does not form any part of a contract. If you are not the intended recipient of this email and its attachments, you must take no action based upon them, nor must you copy or show them to anyone. Please contact the sender if you believe you have received this email in error.
_______________________________________________ Freeswitch-dev mailing list Freeswitch-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
Looking at that again, I was still thwarted by dodgy line breaks - that first line should be all of this: MOD_CFLAGS=-D_REENTRANT -pthread -I/opt/mono-1.9/lib/pkgconfig/../../ include/mono-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -lmono NB this requires Mono 1.9.1 - will try to get a 2.0 version together. To get mod_managed to load you need to tell mono where to look for mod_managed_lib.dll: export LD_LIBRARY_PATH=/usr/local/freeswitch/mod:$LD_LIBRARY_PATH (http://www.mono-project.com/PInvoke#Linux_Shared_Library_Search_Path might suggest better ways) Finally you need to make sure you have "mod/managed" directory even if you don't have anything to put in it (perhaps should be in the Makefile?): mkdir /usr/local/freeswitch/mod/managed David 360CRM Limited, registered address, Caledonia House, 89 Seaward Street, Glasgow, G41 1HJ, Registered in Scotland, company number SC261952. This email and its attachments may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of 360CRM Ltd. This email does not form any part of a contract. If you are not the intended recipient of this email and its attachments, you must take no action based upon them, nor must you copy or show them to anyone. Please contact the sender if you believe you have received this email in error.
We have been doing some major updates to mod_managed over the past few days, I did my best to merge your changes in. A few notes: runswig.sh is gone. It is now integrated into the makefile itself. all your other changes I merged in the best I could, but don't have a mono linux build env yet, so have not tested. the newest builds of mod_managed REQUIRE version 2.0. It will segfault on 1.9. we should be using pkg-config to specify the cflags and ldflags... it can be done with something like this in the makefile: LOCAL_INSERT_CFLAGS= pkg-config mono --cflags LOCAL_INSERT_LDFLAGS= pkg-config mono --libs Can you please give it a try and let me know what else I am missing on this build. Mike On Sep 26, 2008, at 5:59 PM, David Brazier wrote:
Looking at that again, I was still thwarted by dodgy line breaks - that first line should be all of this:
MOD_CFLAGS=-D_REENTRANT -pthread -I/opt/mono-1.9/lib/ pkgconfig/../../ include/mono-1.0 -I/usr/include/glib-2.0 -I/usr/lib/ glib-2.0/include -lmono
NB this requires Mono 1.9.1 - will try to get a 2.0 version together.
To get mod_managed to load you need to tell mono where to look for mod_managed_lib.dll:
export LD_LIBRARY_PATH=/usr/local/freeswitch/mod:$LD_LIBRARY_PATH
(http://www.mono-project.com/ PInvoke#Linux_Shared_Library_Search_Path might suggest better ways)
Finally you need to make sure you have "mod/managed" directory even if you don't have anything to put in it (perhaps should be in the Makefile?):
mkdir /usr/local/freeswitch/mod/managed
David
360CRM Limited, registered address, Caledonia House, 89 Seaward Street, Glasgow, G41 1HJ, Registered in Scotland, company number SC261952. This email and its attachments may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of 360CRM Ltd. This email does not form any part of a contract. If you are not the intended recipient of this email and its attachments, you must take no action based upon them, nor must you copy or show them to anyone. Please contact the sender if you believe you have received this email in error.
_______________________________________________ Freeswitch-dev mailing list Freeswitch-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
I'm very excited to see this work! :) I'm really interested to see the speed comparisons between mono and MS CLR. Thanks to everyone for a great project. --Dave http://dave.thehorners.com/ On Fri, Sep 26, 2008 at 11:46 AM, Michael Jerris <mike@jerris.com> wrote:
David, that module is not "quite" ready for prime time just yet, we are still sorting a few differences between native .net clr and mono but when thats complete, we will get rid of mod_mono. Thanks for the build stuff, I'll get that merged in today.
Mike
On Sep 26, 2008, at 10:40 AM, David Brazier wrote:
This is looking great. I tried building on Linux but runswig.sh the Makefiles I had put in the patch had got their format messed up. So the runswig.sh needs dos2unix run over it & chmod +x. And I've re- worked the Makefiles (below) so hopefully they fit in with the standard build a bit better.
***mod_managed/Makefile*** #MOD_CFLAGS=`pkg-config --cflags --libs mono` MOD_CFLAGS=-D_REENTRANT -pthread -I/opt/mono-1.9/lib/pkgconfig/../../ include/mono-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -lmono #LDFLAGS=`pkg-config --libs mono` BASE=../../../.. VERBOSE=1 include $(BASE)/build/modmake.rules LOCAL_OBJS=freeswitch_managed.o freeswitch_wrap.o local_depend: $(LOCAL_OBJS)
freeswitch_managed.o: freeswitch_managed.h freeswitch_managed.cpp
freeswitch_wrap.o: freeswitch_wrap.cpp
freeswitch_wrap.cpp: freeswitch_wrap.cxx cp freeswitch_wrap.cxx freeswitch_wrap.cpp
local_depend: cd managed && make
local_install: $(MODINSTDIR)/libmod_managed.so cd managed && make MODINSTDIR=$(MODINSTDIR) install
$(MODINSTDIR)/libmod_managed.so: ln -s $(MODINSTDIR)/mod_managed.so $(MODINSTDIR)/ libmod_managed.so
local_uninstall: rm -fr $(MODINSTDIR)/libmod_managed.so cd managed && make MODINSTDIR=$(MODINSTDIR) uninstall
local_clean: cd managed && make clean
***mod_managed/managed/Makefile*** all: mod_managed_lib.dll
clean: rm -fr mod_managed_lib.dll
mod_managed_lib.dll: Loader.cs ManagedSession.cs ApiFunction.cs AppFunction.cs Extensions.cs Log.cs Demo.cs swig.cs gmcs -target:library -out:mod_managed_lib.dll -d:DEBUG Loader.cs ManagedSession.cs ApiFunction.cs AppFunction.cs Extensions.cs Log.cs Demo.cs swig.cs
install: mod_managed_lib.dll install mod_managed_lib.dll $(MODINSTDIR)
uninstall: rm -f $(MODINSTDIR)/mod_managed_lib.dll
360CRM Limited, registered address, Caledonia House, 89 Seaward Street, Glasgow, G41 1HJ, Registered in Scotland, company number SC261952. This email and its attachments may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of 360CRM Ltd. This email does not form any part of a contract. If you are not the intended recipient of this email and its attachments, you must take no action based upon them, nor must you copy or show them to anyone. Please contact the sender if you believe you have received this email in error.
_______________________________________________ Freeswitch-dev mailing list Freeswitch-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
_______________________________________________ Freeswitch-dev mailing list Freeswitch-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
participants (5)
-
Anthony Minessale
-
David A. Horner
-
David Brazier
-
Michael Giagnocavo
-
Michael Jerris