*snipped
ast_set_variables(chan, vars);
insert pbx_builtin_var here -->
ast_pbx_run(chan);
since DIALSTATUS and HANGUPCAUSE are both protected, you will probably
have to create another such as FAILEDCODE.
i hope th
Richard Lyman wrote:
Rich Doughty wrote:
Richard Lyman wrote:
Rich Doughty wrote:
i am creating call files, and catching successfully the ones that don't
connect in a 'failed' extension. can anyone tell me how to find out the
reason for the failure (ie busy, no answer).
${DIALSTATUS} doesn't
Rich Doughty wrote:
Richard Lyman wrote:
Rich Doughty wrote:
i am creating call files, and catching successfully the ones that don't
connect in a 'failed' extension. can anyone tell me how to find out the
reason for the failure (ie busy, no answer).
${DIALSTATUS} doesn't appear to get set (pre
Richard Lyman wrote:
Rich Doughty wrote:
i am creating call files, and catching successfully the ones that don't
connect in a 'failed' extension. can anyone tell me how to find out the
reason for the failure (ie busy, no answer).
${DIALSTATUS} doesn't appear to get set (presumably because Dial(
Rich Doughty wrote:
i am creating call files, and catching successfully the ones that don't
connect in a 'failed' extension. can anyone tell me how to find out the
reason for the failure (ie busy, no answer).
${DIALSTATUS} doesn't appear to get set (presumably because Dial() isn't
used) and chan
i am creating call files, and catching successfully the ones that don't
connect in a 'failed' extension. can anyone tell me how to find out the
reason for the failure (ie busy, no answer).
${DIALSTATUS} doesn't appear to get set (presumably because Dial() isn't
used) and channel_status doesn't se
