[asterisk-dev] ${DIALSTATUS} = NULL - is that OK?
Peter Beckman
beckman at angryox.com
Mon Jun 9 11:41:08 CDT 2008
On Mon, 9 Jun 2008, Russell Bryant wrote:
> Andrew Kohlsmith (lists) wrote:
>> On June 9, 2008 06:34:29 am Chris Maciejewski wrote:
>>> Is behaviour described above normal? The reason I am asking is because
>>> my dialplan logic depends on ${DIALSTATUS} variable and currently I
>>> use "GotoIf($[${ISNULL(${DIALSTATUS})} = 1]?label1:label2)" which
>>> works fine for now, but may break if Dial will return some status in
>>> the future.
>>
>> Personally I would like to see Dial set the variable to INPROGRESS as soon as
>> it runs. I use DIALSTATUS=NULL to see if I dialed at all. :-)
>
> That would be a reasonable enhancement to make.
>
> In response to the original question. I think that if there is any code
> path which allows Dial() to exist without setting a DIALSTATUS, then
> that is a bug.
Somewhat related is ANSWEREDTIME when passed to a Macro. ANSWEREDTIME is
0 or NULL when a macro is used, even if the call _IS_ answered and
DIALSTATUS is ANSWERED. Annoying.
---------------------------------------------------------------------------
Peter Beckman Internet Guy
beckman at angryox.com http://www.angryox.com/
---------------------------------------------------------------------------
More information about the asterisk-dev
mailing list