[Freeswitch-users] freeswitch to write cdr after every bridge attempt (failed or successful

awais nazir awais-nazeer at hotmail.com
Sat Jun 16 22:07:14 MSD 2012


Hello 

Thanks enabling leg B is certainly giving expected results but it's now showing up few variables including some user defined variables defined in the dialplan being executed. This problem did not exist in default enabled leg A.



On Fri, Jun 15, 2012 at 6:51 PM, Avi Marcus <avi at avimarcus.net> wrote:
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 at 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 at example1.company.com" />

>     <action application="bridge"

> data="sofia/local_profile/1111 at 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

 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20120616/abc12348/attachment.html 


Join us at ClueCon 2011 Aug 9-11, 2011
More information about the FreeSWITCH-users mailing list