[asterisk-dev] Controlling the flow of connected line info after attended transfer of stasis-controlled channels
Stephen Davies
stephen.l.davies at gmail.com
Tue Oct 30 15:25:59 CDT 2018
On Tue, 30 Oct 2018 at 22:20, Stephen Davies <stephen.l.davies at gmail.com>
wrote:
> Could you comment on why the Dial with ,,I doesn't block the connected
> line update propagating from the called side of the dial back to the
> calling side. That is what it should do and that's how the code seems to
> work. My impression is that the processing of the REFER seems to
> propagated the connected line update all the way back through to the
> original channel despite this flag.
>
>
Ah - my apologies, I see its actually documented:
The option blocks all redirecting updates since they should only happen
>> before a call is answered. The option only blocks the connected line update
>> from the initial answer. Connected line updates resulting from call
>> transfers happen after the application has completed. Better control of
>> connected line and redirecting information is obtained using the
>> interception macros.
>
>
So its intended to work the way it works.
So its then important to understand how to use the interception macros or
some equivalent in the context of ARI.
Thanks,
Steve
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20181030/3de5dff9/attachment.html>
More information about the asterisk-dev
mailing list