I’m not positive you’ll find it in the variables.  Just grep for the right uuid in one to confirm where you can find it.  You should see similar info in the json cdr, but probably not in any of the flat formats.


On Aug 18, 2016, at 12:26 PM, Victor Chukalovskiy <victor.chukalovskiy@gmail.com> wrote:

Thanks Michale, which chan var do you refer by "it"? I imagine if it's present in XML CDRs, it would be feasible via any other CDR output method...


    
On 16-08-18 12:16 PM, Michael Jerris
      wrote:

    

    
look in the xml cdr, it's in there for sure.

      

      On Thursday, August 18, 2016, Victor Chukalovskiy <victor.chukalovskiy@gmail.com>
      wrote:

      
Good day,

        

        My ultimate goal is for any given a-leg CDR to find the very
        last b-leg CDR.

        

        var "last_bridge_to" allows to find last b-leg for any given
        a-leg as

        long as call was actually "bridged". However, if given a-leg had
        b-leg

        originated, but no actual media or ring-back happened, variable

        "last_bridge_to" remains empty. So I can't use that.

        

        So is there a single variable on a-leg CDR that contains UUID of
        the

        last "originated" leg?

        

        I know there are arrays e.g. "originated_legs" or
        "originate_causes", so

        worst case scenario I can iterate and pick the last UUID in
        either one

        of these arrays. But this means external code or fancy trigger
        functions

        upon CDR SQL insert. Trying to avoid that.

        

        Many thanks!

        

        -Victor