The Adhearsion framework firmly takes the 3PCC approach via inbound event socket, and does a similar thing on Asterisk. We believe that to be the best way to isolate business logic from the switch. Regards, Ben Langfeld On 7 September 2012 15:43, Brett Clark - Grasshopper <bclark@grasshopper.com
wrote:
There seems to be at least 4 general ways for customizing FS:****
- Use the event socket and build an app to interface with it****
- Use mod lua, or similar, to develop in a particular language****
- Develop your own ‘module’ to interface directly with the core****
- Use the XML interface to implement IVR, PBX, and voicemail type functionality and all the rest.****
** **
How prevalent is each approach in the community? It seems like everyone is doing a little of both, but maybe someone has a better handle of what the actual ratios are? ****
** **
Which is best suited for an arbitrarily large and complex application? I realize this isn’t a simple question—what I want is to understand the most evolved and featureful way to interface with FS? I don’t want to adopt an approach which isn’t being actively maintained or is missing features. As new stuff is added to FS, which approach will allow me to adopt those new features most easily?****
** **
Thanks! Brett****
** **
** **
** **
** **
** **
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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