[Freeswitch-users] xml_cdr call flow

[Luis F Urrea]

On our test calls we haven't been able to correlate times from the A leg
with times from the B leg.

I would expect something as A-leg(duration)=
B-leg1(duration)+B-leg2(duration)

Also the <times> tag within <callflow> tag does not seem to be in epoch
microseconds. so it does not seem that's where i should be looking for that
info.

Here's an example of the <times> tag for a test call on the A-Leg:


   1. <times>
   2.       <created_time>1233942283835696</created_time>
   3.       <profile_created_time>1233942283835696</profile_created_time>
   4.       <progress_time>1233942283999716</progress_time>
   5.       <progress_media_time>1233942283999716</progress_media_time>
   6.       <answered_time>1233942287291931</answered_time>
   7.       <hangup_time>0</hangup_time>
   8.       <transfer_time>1233942303240916</transfer_time>
   9.     </times>


any hint is appreciated


On Thu, Feb 12, 2009 at 3:46 PM, Luis F Urrea <lfurrea at gmail.com> wrote:

> Hi all,
>
> We are writing a xml_cdr parser to load CDRs in SQLite. We are interested
> in logging times for both A leg and B leg so that transfers are reported as
> individual calls with accurate timing. eg Inboud call to AA lasted 14
> seconds then call to operator 20s and then call to actual extension 5min
>
> As of now we are using the <callflow> tag with the "number" attribute to
> find out who did the A leg talk to, then we open the B leg files and get the
> times from each jump from the <times> tag within the <callflow> tag on the B
> leg file.
>
> Is this right or maybe someone could suggest a better way to do it.
>
> TIA
>
> Luis
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20090212/2077fea2/attachment-0002.html