[asterisk-bugs] [JIRA] (ASTERISK-27749) DIALSTATUS inconsistent

[Joshua Colp (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-27749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=242895#comment-242895 ] 

Joshua Colp commented on ASTERISK-27749:
----------------------------------------

Forcing "answered elsewhere" on alters the hangup cause so it's not actually busy when it gets to that point, which thus in turn changes the dial status. That's why it is doing what it is doing. From looking at the code it's always been like that so changing it could have repercussions for other people with the behavior change.

> DIALSTATUS inconsistent
> -----------------------
>
>                 Key: ASTERISK-27749
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27749
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_dial
>    Affects Versions: 15.2.2
>            Reporter: Frederic Steinfels
>            Assignee: Unassigned
>            Severity: Minor
>              Labels: pjsip
>         Attachments: dailtwice.txt, dialonce.txt
>
>
> Please consider these three scenarios:
> Scenario 1:
> Dial(PJSIP/blabla)
> Scenario 2:
> Dial(Local/abc at default)
> [default]
> abc,s,1 => Dial(PJSIP/blabla)
> Scenario 3:
> Dial(Local/abc at default)
> [default]
> abc,s,1 => Dial(Local/xyz at default)
> xyz,s,1 => Dial(PJSIP/blabla)
> blabla is a mobile phone where I am pressing the red button when the call comes in (decline). In Scenario 1+2, the DIALSTATUS variable is BUSY which is correct. In Scenario 3, the DIALSTATUS is CHANUNAVAIL. To be clear, I was always monitoring the CHANUNAVAIL variable on the Dial(PJSIP/blabla) command. I was even trying to get further information or differences using b(), B() and hangup handlers on the dial command in order to find further differences - with no avail.



--
This message was sent by Atlassian JIRA
(v6.2#6252)