Re: [Asterisk-java-users] Originating calls for automatic messaging

[Carlos G M. <tr...@ac...>]

Stefan Reuter @ 29/09/2006 11:58 -0300 dixit:
> Carlos G Mendioroz wrote:
>> Yes, and it sort of works, but I don't get access to the failure
>> conditions. (i.e. Busy becomes channel unavailable) :(
>>
>> Hmm, I thought it was going to be an easy one ...
> 
> no. detecting the cause for a failure is one of the most complicated
> things with the originate stuff and the current implementation in
> Asterisk-Java is probably far from excellent in this regard.
> You can do me a favor and provide me with a detailed description of the
> situations (i.e. what you did in your code and whether the caller/callee
> is busy an), a dump of the events received through the Manager API (see
> http://asterisk-java.org/page/aj?entry=debugging_manager_api) and the
> logs. Then I can further investigate and possibly enhance the detection.
> 
> =Stefan

Ok, no problem, I'll try to do that, but first let me get clear which
way "should" I be doing this:

The originate command gets a channel and a destination, which could be a
context/extension or an application.
My idea was that the reporting would be about the action involved in
doing this connection and not in the creation of the involved channel.

But in fact, I'm interested in the "real" call leg and the "loopback"
was just that, a virtual channel to make the framework work.

So I'm going to do:
	originateToExtension("Local/dest@dialout","dialing","0",1,timeout);
redirect("service", "srv_no", 1);

Or use the asynch model and get the different completion states. Right ?

-- 
Carlos G Mendioroz  <tr...@ac...>