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

[Leo Burd]

- Sounds good. Thanks!

.L.


Ryan Bullock wrote:
> Hello Leo,
>
> Their would be nothing stopping you from simply waiting for the the
> OrignateComplete event in your application, before issuing any further
> commands, to provide a synchronous/blocking behavior.
>
> Regards,
>
> Ryan Bullock
>
> On Thu, May 6, 2010 at 2:42 PM, Leo Burd <leob at media.mit.edu> wrote:
>   
>> Hello there,
>>
>> For my kind of application, it would be great to keep the Async option
>> and let users run synchronous requests to Originate.  Is that something
>> that has already been ruled out of the plans?
>>
>> Best,
>>
>> Leo
>>
>>
>>
>> *
>>     
>>> *
>>> -------------------------------------*
>>> [asterisk-dev] Proposed changes to Originate Action [Issue: 0017221]
>>> *Ryan Bullock* rrb3942 at gmail.com
>>> <mailto:asterisk-dev%40lists.digium.com?Subject=%5Basterisk-dev%5D%20Proposed%20changes%20to%20Originate%20Action%20%5BIssue%3A%0A%090017221%5D&In-Reply-To=-6860553992492326028%40unknownmsgid>
>>> /Tue Apr 27 13:25:15 CDT 2010/
>>> ------------------------------------------------------------------------
>>> 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 <http://lists.digium.com/mailman/listinfo/asterisk-dev>> wrote:
>>>       
>>>> / Great, thanks!
>>>>         
>>> />/
>>> />/ On Apr 27, 2010, at 11:17 AM, Ryan Bullock <rrb3942 at gmail.com <http://lists.digium.com/mailman/listinfo/asterisk-dev>> wrote:
>>> />/
>>> />>/ So when you use 'Channel: Local/1234 at context <http://lists.digium.com/mailman/listinfo/asterisk-dev>'?
>>> />>/
>>> />>/ 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
>>> />/
>>> /
>>>       
>> *
>>
>> --
>> _____________________________________________________________________
>> -- 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
>>
>>     
>
>