[Freeswitch-users] xml_cdr Call Flow for attended transfer

[Luis F Urrea]

any hints?

what would be the best way to report CDRs for attended transfers??

We are using C with libxml to create a binary that can be called from a
script to rotate xml_cdrs and insert them on SQLite and would gladly submit
the code to your revision, advice and maybe even potential use.

I appreciate your advice.

On Mon, Feb 16, 2009 at 5:52 PM, Luis F Urrea <lfurrea at gmail.com> wrote:

>  Hi all,
>
>
> I am trying to understand xml_cdr for an attended (consultative) transfer,
> I was thinking that the A-leg that initially
> originated the call would remain untouched but I see that it's global tags
> get replaced.
>
> I have a test call that goes as follows:
>
> 201 originates a call and talks to 203                 -----> A-leg(1) and
> B-leg(1)
>
> 203 puts 201 on hold and calls 202 (attended)     ------> A-leg(2) and
> B-leg(2)
>
> 203 transfers the call
>
> 201 and 202 are talking                                     ------>
> A-leg(1) w/ B-leg(2) ???
>
> Here are the relevant captures:
>
> A-leg(1)
> http://pastebin.freeswitch.org/7253
>
> B-leg(1)
>  http://pastebin.freeswitch.org/7254
>
> A-leg(2)
> http://pastebin.freeswitch.org/7252
>
> B-leg(2)
> http://pastebin.freeswitch.org/7255
>
> I was expecting A-leg(1) to have <variables> corresponding to 201 which is
> the original A-leg but it seems that on the transfer, it reverts and 202
> appears as the A-leg and 201 as the B-leg.
>
> Can someone shed some light on how that transfer gets logged in terms of
> A-leg and B-leg?
>
> TIA
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20090217/940eb515/attachment-0002.html