My mistake, they do seem to be microsecs.


But still I cannot correlate times from the A-leg with the B-legs.

I have included below the xml_cdr files generated for the test call. 

The test call was made using three registered extensions. Basically, Ext 201 calls ext 203 and they talk, then 203 blindly transfers to 202, 202 does not answer and call rolls to voicemail.

A-leg:
http://pastebin.freeswitch.org/7206

B-leg:
http://pastebin.freeswitch.org/7204

B-leg:
http://pastebin.freeswitch.org/7205


Thanks for your help

On Thu, Feb 12, 2009 at 6:08 PM, Michael Collins <msc@freeswitch.org> wrote:
On Thu, Feb 12, 2009 at 3:31 PM, Luis F Urrea <lfurrea@gmail.com> wrote:
> Heres pastebin of the A-leg
>
> http://pastebin.com/m6731913d
>
>
> On Thu, Feb 12, 2009 at 5:00 PM, Michael Collins <msc@freeswitch.org> wrote:
>>
>> Pastebin the whole file so that we can see it in context...
>> -MC
>>
>> On Thu, Feb 12, 2009 at 2:50 PM, Luis F Urrea <lfurrea@gmail.com> wrote:
>> > 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)
I don't know that this is necessarily true. Can you pastebin your
dialplan entry (or whatever generated this call) so we can take a
look? Also, please use our pastebin so that it's easier for us to find
stuff:
http://pastebin.freeswitch.org

>> >
>> > 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:
>> >
>> > <times>
>> >       <created_time>1233942283835696</created_time>
>> >       <profile_created_time>1233942283835696</profile_created_time>
>> >       <progress_time>1233942283999716</progress_time>
>> >       <progress_media_time>1233942283999716</progress_media_time>
>> >       <answered_time>1233942287291931</answered_time>
>> >       <hangup_time>0</hangup_time>
>> >       <transfer_time>1233942303240916</transfer_time>
>> >     </times>
>> >
>> > any hint is appreciated
>> >
Perhaps I'm missing something but they sure look like epoch microseconds to me.
-MC