[asterisk-users] DIALSTATUS vs HANGUPCAUSE

Tony Mountifield tony at softins.co.uk
Wed Mar 14 04:44:19 CDT 2018

In article <CAPu3kNV8w+bYQT0W+QbnTSby0V5gfjLqZXq15c4i5enr_-tJtg at mail.gmail.com>,
Patrick Wakano <pwakano at gmail.com> wrote:
> Thanks Dovid!
> Indeed looks a bug but regardless of this, this problem made me think that
> the HANGUPCAUSE could be used for this purpose with benefits.
> I couldn't find an explanation about when DIALSTATUS would actually be
> better.
> The HANGUPCAUSE was reworked in version 11 (
> https://wiki.asterisk.org/wiki/display/AST/Hangup+Cause) but I didn't find
> someone actually stating it is a better alternative or replacement to the
> DIALSTATUS or something similar.

I think you should always check DIALSTATUS, as that will be set regardless of
the way in which a dial fails. I believe HANGUPCAUSE is set to the Q.931 code
received from PRI or SIP when a call is rejected or terminated. However, there
could be other mechanisms for failure (such as failure to create a channel
within Asterisk, or an attempt to send to an unreachable peer), that may set

So HANGUPCAUSE should be considered as extra detail, rather than a replacement
or alternative to DIALSTATUS.

Tony Mountifield
Work: tony at softins.co.uk - http://www.softins.co.uk
Play: tony at mountifield.org - http://tony.mountifield.org

More information about the asterisk-users mailing list