[asterisk-dev] Proposed changes to Originate Action [Issue: 0017221]

[Ryan Bullock]

It does not help with this case, as the channel returned is from the
same functions as the old one.

If you watch the manager events after doing an originate with a local
channel you will see the local channel get renamed to the appropriate
tech/data channel. It makes sense that the functions creating the call
cannot determine the end device and technology for a local channel, as
a the dialplan could end in any number of ways, depending on runtime
variables.

On Tue, Apr 27, 2010 at 11:57 AM, Timothy Rodriguez
<timothy.rodriguez at gmail.com> wrote:
> Great, thanks!
>
> On Apr 27, 2010, at 11:17 AM, Ryan Bullock <rrb3942 at gmail.com> wrote:
>
>> So when you use 'Channel: Local/1234 at context'?
>>
>> I don't know if this will fix the problems introduced by masquerading.
>> If I get some time I will try to load up that scenario and test it.
>>
>> --
>> _____________________________________________________________________
>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>>
>> asterisk-dev mailing list
>> To UNSUBSCRIBE or update options visit:
>>   http://lists.digium.com/mailman/listinfo/asterisk-dev
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-dev
>