[asterisk-biz] Bounty: Transfer Channel/Context to properly Inherit Channel Variables

[Steve Poirier]

Sorry for the flood, To Add Details to what we want to be achieved:

See Comment from kpfleming on the following issue report by another user a
few years ago: https://issues.asterisk.org/view.php?id=4188

The issue reported by the user at this time was modified to "Feature
Request".

I believe that it would be logical for the transfer channel to inherit
channel variables previously set with _ or __

This would also make the use of a transfer context much more flexible.

Quote:
"This behavior is as-designed; when you hit the transfer feature sequence, a
new channel is created, which does not have any special channel variables
associated with it. Variables set in either of the channels that are part of
the original conversation are not involved in the new channel.

It would be possible to make channel variables inherit from the transferer's
channel using the _NAME syntax already available in other parts of Asterisk,
but that is not currently in place."

End Quote
__
Steve Poirier

On Wed, Apr 7, 2010 at 12:44 PM, Steve Poirier <mousepad99 at gmail.com> wrote:

> $200 Bounty to be able to retrieve channel variables on transfers
>
> Example Scenario:
>
> Initial Call:
> [context]
> Set(TRANSFER_CONTEXT=transfer_context)
> Set(_myvar=foo)
>
> Person hit transfer key, dials a number
>
> [transfer_context]
> exten => _.,1,Noop(${myvar})  ; this will currently return blanks, we want
> this to return foo
>
> Current behavior is that channel variables are not readable in the tranfer
> channel
>
> Need that on 1.4.21.1, 1.4.22 and 1.4.30
>
> $100 Bonus if accepted by digium on 1.6
>
> I'm not sure about the amount of work required at this time to make this
> work, so forgive me if the bounty amount sounds ridiculous, all serious
> offers welcome.
>
> mousepad99 (at) gmail (dot) com
>
> Regards,
> __
> Steve Poirier
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-biz/attachments/20100407/61c8bcbb/attachment.htm