Hello list, Hope all doing well! 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.... 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 (https://wiki.asterisk.org/wiki/display/AST/Hangup+Cause+Mappings). Anyway I am thinking about actually not checking the DIALSTATUS anymore and just rely on the HANGUPCAUSE, which seems more powerful. 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? Or does someone knows exactly where is more suitable to use one over the other? Thanks, Kind regards, Patrick Wakano -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20180314/1b0c3a0b/attachment.html>
I would think that is a bug since the only time DIALSTATUS = BUSY is where you got a 486 or 600 (as per https://wiki.asterisk.org/wiki/display/AST/Hangup+Cause+Mappings). On Tue, Mar 13, 2018 at 10:11 PM, Patrick Wakano <pwakano at gmail.com> wrote:> Hello list, > Hope all doing well! > > 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.... > 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 (https://wiki.asterisk.org/wiki/display/AST/Hangup+Cause+ > Mappings). Anyway I am thinking about actually not checking the > DIALSTATUS anymore and just rely on the HANGUPCAUSE, which seems more > powerful. > 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? > Or does someone knows exactly where is more suitable to use one over the > other? > > Thanks, > Kind regards, > Patrick Wakano > > -- > _____________________________________________________________________ > -- 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 >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20180313/98d57c9a/attachment.html>
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. Cheers, Patrick Wakano On 14 March 2018 at 13:30, Dovid Bender <dovid at telecurve.com> wrote:> I would think that is a bug since the only time DIALSTATUS = BUSY is where > you got a 486 or 600 (as per https://wiki.asterisk.org/ > wiki/display/AST/Hangup+Cause+Mappings). > > On Tue, Mar 13, 2018 at 10:11 PM, Patrick Wakano <pwakano at gmail.com> > wrote: > >> Hello list, >> Hope all doing well! >> >> 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.... >> 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 (https://wiki.asterisk.org/wik >> i/display/AST/Hangup+Cause+Mappings). Anyway I am thinking about >> actually not checking the DIALSTATUS anymore and just rely on the >> HANGUPCAUSE, which seems more powerful. >> 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? >> Or does someone knows exactly where is more suitable to use one over the >> other? >> >> Thanks, >> Kind regards, >> Patrick Wakano >> >> -- >> _____________________________________________________________________ >> -- 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 >> > > > -- > _____________________________________________________________________ > -- 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 >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20180314/8eb63c2e/attachment.html>