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

[awais nazir]

Thanks Avi, this link really helped, I am using export instead of set for variables.

Is there anyway we can put A and B legs logs separate?


From: awais-nazeer at hotmail.com
To: freeswitch-users at lists.freeswitch.org
Subject: Re: [Freeswitch-users] freeswitch to write cdr after every bridge attempt (failed or successful
Date: Sun, 17 Jun 2012 22:29:20 +0500





Actually , some user defined variables like huting attempt ,customer and
 vendor names I define in dialplan. The solution to make join with uuid 
is bit complicated and seem to require bit efforts like pushing in to 
mysql and then make join. Even then the variables only appears according
 to successful or last bridge attempt. 

On Sun, Jun 17, 2012 at 10:15 PM, Avi Marcus <avi at avimarcus.net> wrote:
Oh that's what you meant.If it's in leg A, why do you expect it to be in Leg B CDR?
That said, there's an option to let you do that: http://wiki.freeswitch.org/wiki/Variable_copy_xml_cdr but I've never tried it.

-Avi


On Sun, Jun 17, 2012 at 7:27 PM, awais nazir <awais-nazeer at hotmail.com> wrote:







I will attempt get reply again, the channel variable being set in dialplan are seen in A leg cdr but not in B leg cdr, can somebody help ?




From: awais-nazeer at hotmail.com
To: freeswitch-users at lists.freeswitch.org


Subject: Re: [Freeswitch-users] freeswitch to write cdr after every bridge attempt (failed or successful
Date: Sat, 16 Jun 2012 23:07:14 +0500





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

 		 	   		   		 	   		  

_________________________________________________________________________

Professional FreeSWITCH Consulting Services:

consulting at freeswitch.org

http://www.freeswitchsolutions.com









Official FreeSWITCH Sites

http://www.freeswitch.org

http://wiki.freeswitch.org

http://www.cluecon.com

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