asterisk users - Aug 2018 - Queue breaks Dynamic_Features on Attended Transfer

Hi,

I think I've identified an issue and just want to check before completing a
bug report.

Prior to a call entering a Queue, I set __DYNAMIC_FEATURES=NewRecordApp. AgentA
answers and is able to use that feature code.
If AgentA performs an attended transfer of a call from a queue to AgentB, the
feature code no longer works.

Cases that do work are as follows...
Calls using both Queue() and Dial() applications, prior to transfer, feature
code works.
Calls using the Dial() application, both Blind and Attended transfers still
allow the feature code to work.
Calls using the Queue() application where AgentA performs a Blind transfer to
AgentB still allow the feature to work.

It only doesn't work when using Queue() and an Attended transfer is
performed.

Is this a bug or is there something that needs to be set to allow the
DYNAMIC_FEATURES to be inherited after an attended transfer from a queue?

Many thanks,
Dan

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20180808/fd3fd6a4/attachment.html>

> Prior to a call entering a Queue, I set __DYNAMIC_FEATURES=NewRecordApp.
> AgentA answers and is able to use that feature code.
> If AgentA performs an attended transfer of a call from a queue to AgentB,
the
> feature code no longer works.
>
> It only doesn't work when using Queue() and an Attended transfer is
> performed.
>
> Is this a bug or is there something that needs to be set to allow the
> DYNAMIC_FEATURES to be inherited after an attended transfer from a queue?
Doing some more tests, this reads like a bug to me.
Using a hanguphandler with DumpChan in the dialplan context that executes the
Queue, I can see that DYNAMIC_FEATURES is set.
After the attended transfer when the call is ended, the hanguphandler still
shows that DYNAMIC_FEATURES is set. It's just not accessible.

Any thoughts?
Thanks
Dan
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20180808/9c0549f6/attachment.html>

On Wed, Aug 8, 2018 at 1:53 PM, Daniel Journo <dan at
keshercommunications.com>
wrote:
> > Prior to a call entering a Queue, I set
__DYNAMIC_FEATURES=NewRecordApp.
> > AgentA answers and is able to use that feature code.
> > If AgentA performs an attended transfer of a call from a queue to
> AgentB, the
> > feature code no longer works.
> >
> > It only doesn’t work when using Queue() and an Attended transfer is
> > performed.
> >
> > Is this a bug or is there something that needs to be set to allow the
> > DYNAMIC_FEATURES to be inherited after an attended transfer from a
queue?
>
> Doing some more tests, this reads like a bug to me.
> Using a hanguphandler with DumpChan in the dialplan context that executes
> the Queue, I can see that DYNAMIC_FEATURES is set.
> After the attended transfer when the call is ended, the hanguphandler
> still shows that DYNAMIC_FEATURES is set. It's just not accessible.
>
> Any thoughts?
>
It likely depens on how you are doing the attended transfer.  Via DTMF?
Via SIP or channel technology protocol?
Does the Agent B channel have the DYNAMIC_FEATURES channel variable set on
it?

Richard
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20180808/ff84dc91/attachment.html>