So once it has been initialized, leave it in memory and re-use the same instance. If you really insist on completely unloading it, launch freeswitch as an external process and communicate with it using event socket.
Mathieu Rene Avant-Garde Solutions Inc Office: + 1 (514) 664-1044 x100 Cell: +1 (514) 664-1044 x200 mr...@avgs.ca On 2010-06-30, at 1:44 PM, Paulo Vicentini wrote: > Hi, > I require that because by embedding libfreeswitch in my app there is time > when my code using libfreeswitch is "out of context" so that I need to call > switch_core_destroy but when I "in context" again I suppose to call > switch_core_init_and_modload so that It would be usefull to have the core > plugable as well. > Thanks > > On Wed, Jun 30, 2010 at 2:07 PM, Mathieu Rene <mrene_li...@avgs.ca> wrote: > A lot of stuff is statically initialized, the core isn't designed to be > loaded/unloaded like that. Why exactly do you require calling > switch_core_init_and_modload() after the initial startup? > > Mathieu Rene > Avant-Garde Solutions Inc > Office: + 1 (514) 664-1044 x100 > Cell: +1 (514) 664-1044 x200 > mr...@avgs.ca > > > > > On 2010-06-30, at 12:44 PM, Paulo Vicentini wrote: > > > Hi, > > I am embedding libfreeswitch to my application's process space and I need > > to "init" and "destroy" freeswitch while running my process. > > I face problems after calling switch_core_destroy and when my business > > logic demands I call switch_core_init_and_modload to work with > > libfreeswitch (again) > > It seems that struct switch_runtime runtime is not cleared aproprietaly > > when destroying the core. > > I made some tests clearing runtime struct but still getting segfaults on > > apr_queue_trypush (trying to find out the issue) > > Can you please help me out with this issue? > > Thanks > > _______________________________________________ > > 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 > > _______________________________________________ > 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
