[asterisk-dev] CDR Problem Proposals
Atis Lezdins
atis at iq-labs.net
Fri Nov 21 11:34:18 CST 2008
> Steve,
>
> Although it's not a CDR problem we had, it is / was a similar thing. I
> needed to track a call from the moment it came in, to the moment it
> ended, regardless of parking / transfers etc etc.
>
> I managed to achieve this by allocating a GUID to the call, and saving
> that GUID as an inherited variable. Thus, all other channels that came
> into contact with the original channel inherited the call GUID.
>
> Couldn't you do something similar internally ? When a call first comes
> in, create a CDR object, and allocate a GUID to it. Set an inherited
> internal channel variable to the value of the CDR GUID and pass that
> around. This should bypass all the issues with transfers / masquerades
> etc. Perhaps have a parent CDR GUID as well, so a channel has it's own,
> and the one of the channel it connected to.
>
> I know, I know, it's an extremely simplistic scenario and it most likely
> will not work but perhaps it is enough to give food for thought.
>
> Julian.
>
<snip>
Julian,
We are doing exactly the same, and i suggested this a long time ago,
so Murf catched this idea.
It has been named "linkedid" and should be somewhere in trunk and now
probably in 1.6.1.
Regards,
Atis
--
Atis Lezdins,
VoIP Project Manager / Developer,
IQ Labs Inc,
atis at iq-labs.net
Skype: atis.lezdins
Cell Phone: +371 28806004
Cell Phone: +1 800 7300689
Work phone: +1 800 7502835
More information about the asterisk-dev
mailing list