BTW: A far simpler set up is simply dispatching to FS boxes. Then for maintenance, you pause calls (fsctl pause) or tell FS to shut down when calls are finished (fsctl asap, as per mod_commands#shutdown<http://wiki.freeswitch.org/wiki/Mod_commands#shutdown> ). Are you looking into track-calls for FS crashes, or for maintenance to move calls around..? This satisfies the second just fine.. -Avi p.s. mod_ha_cluster in development should handle this beautifully... some info on mod_ha_cluster<http://wiki.freeswitch.org/wiki/FS_weekly_2012_01_04#Suggestions_For_Future_Meetings_.26_Future_To_Dos> On Thu, Jan 19, 2012 at 5:47 PM, Carlo Dimaggio <jaasmailing@gmail.com>wrote:
Hi all,
I would like to know if the track-calls feature could be used in a multi-primary - multi-backup scenario. What I think is an environment with Kamailio dispatcher to N freeswitch boxes with a (multi or) single freeswitch backup. In case of failure, one primary should be replaced with a backup (spare) box that will take its IP and active calls.
If all active freeswitch track call state in the same table/database, how the backup box will know what calls should be recovered? Anyone could explain the call recovery algorithm?
Best Regards,
_________________________________________________________________________ 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