By default, the modules for logging only log the A leg of the call. You can turn on b-leg logging in whichever module you are using for call logs. Do note you'll have to reconstruct the call then, based on which is the A-leg and which is B leg, and using bridge_uuid, signal_bond or last_bridge_to of the B leg (whichever is set) to see which A leg it came from. (Also note on enterprise originates: they are reported as leg A in xml_cdr and need to be tied using the variable: ent_originate_aleg_uuid) This kind of "advanced" CDR handling should probably be wikified... -Avi On Fri, Jun 15, 2012 at 4:17 PM, awais nazir <awais-nazeer@hotmail.com> wrote:

Hi

I am trying to use following context to get failover gateways working

    <action application="set" data="hangup_after_bridge=true"/>     <action application="bridge" data="sofia/local_profile/1111@example1.company.com" />     <action application="bridge" data="sofia/local_profile/1111@example2.company.com" />

if call on first gateway fails , call connection is attempted on second gateway but FS is writing only one CDR.How can it write CDR on every bridge attempt.

BR --waisee

_________________________________________________________________________ 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

Join Us At ClueCon - Aug 7-9, 2012

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