Check the contents of the direction tag. It will be either inbound (aleg) or outbound (bleg). Steve on iPhone On 3 Jun 2010, at 14:09, Michael Toop <michaelt@voxcore.voxtelecom.co.za> wrote:
Hi Adam,
We also have this problem (no way to tell the a-leg from the b-leg in xml_cdr POST data).
What I do, which is a bit of a work around, is to look for the typical SIP media IP of the b-leg of the call to differentiate the a from b legs.
It would however be great to have a tag in the POST to make life easier, similar to the feature where xml_cdr file is prefixed with a 'a_'.
Cheers,
Michael
On Tue, Mar 2, 2010 at 9:27 PM, Adam Ford <lists@redbonez.net> wrote: Is there any way to tell whether it is the a-leg or b-leg when receiving the POST data from mod_xml_cdr?
I wrote a parser in Python which parses the a_*.cdr.xml log files, and only grabs the info in the associated b-leg log files if it needs additional information(for example - in the case of a call that ends with mod_fifo). I want to adapt this to using the POST features of mod_xml_cdr so that it can be real time.
Any suggestions are greatly appreciated,
-Adam
_______________________________________________ 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
_______________________________________________ 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