[asterisk-dev] Originated Calls and Progress Detection

[Richard Lyman]

see inside

Whit Thiele wrote:
> Richard,
>
> Thanks for the suggestion. The OriginateResponse event is generated
> automatically. 
>
>   
branch 1.4
pbx.c
in ast_pbs_outgoing_exten

			if (ast_exists_extension(chan, context, "failed", 1, NULL)) {

so, no, it is not automatically generated.

you must have a failed,1,Something to trigger the event we want.


> I've also used the failed extension and tried to look at both DIALSTATUS and
> HANGUPCAUSE variables, but they don't appear to get set properly either.
> There was a similar thread on this strategy back in February, 2007 which had
> a couple other dialplan suggestions (like looking at DIALSTATUS using the
> 'h' extension) None of these suggestions yielded any solutions.
>
>   
iirc i was a part of that thread also, in which i stated all this.  are 
you sure you aren't expect the 'asterisk causes'? (which you will not get)

> On my test system, HANGUPCAUSE is always set to 16 and the OriginateResponse
> reason is 0 for both a real No Answer and a Disconnected Number. Even the
> CDR records show NO ANSWER for both calls. 
>   
the hangupcause is not going to be of much help to you.  the reason 0 
means 'Unknown Error OR Disconnect'.
so it gave you the answer you wanted. (i do not go by the cdr's as those 
were always off (last i looked was ages ago).

> This is why I'm trying to look into changing the code itself (hence the
> posting on this list) for a solution. 
>
>   
i wish you luck. (i actually didn't even notice this was the dev list)

> So the question seems to be where the best place is to attach a dsp process
> to determine what's going on during the call launch.. unless there is
> something else to try that I've missed.
>
>
>   
ast_request_and_dial
failed check
cdr
all occur in ast_pbx_outgoing_exten, you might want to start there.