[asterisk-users] DIALSTATUS vs HANGUPCAUSE
dovid at telecurve.com
Tue Mar 13 21:30:49 CDT 2018
I would think that is a bug since the only time DIALSTATUS = BUSY is where
you got a 486 or 600 (as per
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
> 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
> 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.
> New to Asterisk? Start here:
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the asterisk-users