[Freeswitch-users] Skypopen - Skype Client on a different machine than Freeswitch with Skypopen module

[Seven Du]

On Tuesday, January 31, 2012 at 2:20 AM, A E [Gmail] wrote:

> Ok cool. Thank you so much.
> 
> I found this as some very slimmed down modules.conf.xml figuring FS running on an embedded platform might give me the best case from which to build on. It's here: https://dev.openwrt.org/browser/packages/net/freeswitch/files/etc.minimal/autoload_configs/modules.conf.xml?order=date 
> 
> Apart from adding mod_skypopen to this, does this look good? What else needs to be added to it?  
> 
Add anything you need, see http://wiki.freeswitch.org/wiki/FreeSwitch_Modules for detail

you still can remove some modules if you don't use them, e.g. mod_cdr_csv etc.
 
> 
> Thanks so much for your help :)
> 
> 
> On Mon, Jan 30, 2012 at 9:00 AM, Seven Du <dujinfang at gmail.com (mailto:dujinfang at gmail.com)> wrote:
> > Yes, exactly, you could remove any unnecessary modules if you don't use them.
> > 
> > to be clear, you could send calls from FS1 to FS2 and FS3 give you have proper dialplan set to route calls to the desired destination. 
> > that means you could just treat FS2 and FS3 as a third party sip gateway but they can routing calls to anywhere you want. 
> > 
> > FS1 (mod_sofia) ----------------------  (mod_sofia)FS2(mod_skypopen) -------------------skype 
> >                            \
> >                             \------------------  (mod_sofia)FS3(mod_dingaling) ---------------------gtalk
> > 
> > That testimonial is completely following the wiki's sharing rule, but you can use the idea completely freely. 
> > 
> > On Monday, January 30, 2012 at 12:46 PM, A E [Gmail] wrote:
> > 
> > 
> > 
> > > On Sun, Jan 29, 2012 at 2:14 AM, Seven Du <dujinfang at gmail.com (mailto:dujinfang at gmail.com)> wrote:
> > > > skype clients should run with FS on the same box. 
> > > > 
> > > > You could run both FS and skype clients on another box just as a gateway if you want scale. We had run multi- FS instances on one box for scale/stable purpose, but you can get the idea from http://wiki.freeswitch.org/wiki/FreeSWITCH_Testimonial_on_Idapted.com 
> > > > 
> > > > -- 
> > > > About: http://about.me/dujinfang
> > > > Blog: http://www.dujinfang.com
> > > > Proj:  http://www.freeswitch.org.cn
> > > > 
> > > > Sent with Sparrow (http://www.sparrowmailapp.com)
> > > > 
> > > Thanks Seven. I had a good read of that testimonial and it's basically saying what you just said here in a line. The question now is are the design docs for that setup proprietary or kinda sorta can be GPL'ed or "shared" in some form? :)
> > > 
> > > If not, then just to clarify, the FS-Skype servers load their own mod_skypopen and is just a gateway to send calls to once it's determined by the FS in the center acting like a soft-switch/call-control platform? Is it completely possible to run/build an FS instance with just mod_skyopen or mod_dingaling (and anything else that's fundamentally needed by FS) loaded? I mean I could Google this but it might help if you could tell me what your modules.conf.xml looks like for Skype only instance? 
> > > 
> > > Thanks so much in advance, and apologies if I'm being unreasonable in requesting for the info :) 
> _________________________________________________________________________
> Professional FreeSWITCH Consulting Services:
> consulting at freeswitch.org (mailto:consulting at freeswitch.org)
> http://www.freeswitchsolutions.com
> 
> 
> 
> 
> Official FreeSWITCH Sites
> http://www.freeswitch.org
> http://wiki.freeswitch.org
> http://www.cluecon.com
> 
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org (mailto:FreeSWITCH-users at lists.freeswitch.org)
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
> 
> 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20120131/1768ef6e/attachment-0001.html