In article <capu3knv8w+byqt0w+qbntsby0v5gfjlqzxq15c4i5enr_-t...@mail.gmail.com>, Patrick Wakano <[email protected]> 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 DIALSTATUS without setting HANGUPCAUSE. So HANGUPCAUSE should be considered as extra detail, rather than a replacement or alternative to DIALSTATUS. Cheers Tony -- Tony Mountifield Work: [email protected] - http://www.softins.co.uk Play: [email protected] - http://tony.mountifield.org -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- Check out the new Asterisk community forum at: https://community.asterisk.org/ New to Asterisk? Start here: https://wiki.asterisk.org/wiki/display/AST/Getting+Started asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
