<div dir="ltr">I would think that is a bug since the only time DIALSTATUS = BUSY is where you got a 486 or 600 (as per <a href="https://wiki.asterisk.org/wiki/display/AST/Hangup+Cause+Mappings">https://wiki.asterisk.org/wiki/display/AST/Hangup+Cause+Mappings</a>). </div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar 13, 2018 at 10:11 PM, Patrick Wakano <span dir="ltr"><<a href="mailto:pwakano@gmail.com" target="_blank">pwakano@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>Hello list,<br></div>Hope all doing well!<br><br></div>I've been checking some cases when a Dial fails and dialplan execution continues to handle this. I am finding it a little confusing how we should handle the DIALSTATUS and the HANGUPCAUSE in this situation....<br>More specifically, I am facing a case in version 13.6.0 where I am getting a DIALSTATUS=BUSY and HANGUPCAUSE=19 after receiving a 480 SIP error. Seems wrong to me, since 480 should be converted to
HANGUPCAUSE=19
and DIALSTATUS = NOANSWER
(<a href="https://wiki.asterisk.org/wiki/display/AST/Hangup+Cause+Mappings" target="_blank">https://wiki.asterisk.org/<wbr>wiki/display/AST/Hangup+Cause+<wbr>Mappings</a>). Anyway I am thinking about actually not checking the DIALSTATUS anymore and just rely on the HANGUPCAUSE, which seems more powerful.<br>
</div><div>Looks like for a pure SIP environment the
HANGUPCAUSE
would have a more accurate information about the error. So question is
can I always use this info and completely ignore what the DIALSTATUS is?<br></div><div>Or does someone knows exactly where is more suitable to use one over the other?<br></div><br>Thanks,<br>Kind regards,<br></div><div>Patrick Wakano<br></div></div>
<br>--<br>
______________________________<wbr>______________________________<wbr>_________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" rel="noreferrer" target="_blank">http://www.api-digital.com</a> --<br>
<br>
Check out the new Asterisk community forum at: <a href="https://community.asterisk.org/" rel="noreferrer" target="_blank">https://community.asterisk.<wbr>org/</a><br>
<br>
New to Asterisk? Start here:<br>
<a href="https://wiki.asterisk.org/wiki/display/AST/Getting+Started" rel="noreferrer" target="_blank">https://wiki.asterisk.org/<wbr>wiki/display/AST/Getting+<wbr>Started</a><br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" rel="noreferrer" target="_blank">http://lists.digium.com/<wbr>mailman/listinfo/asterisk-<wbr>users</a><br></blockquote></div><br></div>