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

Frederic Steinfels (JIRA) noreply at issues.asterisk.org
Tue Mar 20 18:45:13 CDT 2018


     [ https://issues.asterisk.org/jira/browse/ASTERISK-27749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Frederic Steinfels updated ASTERISK-27749:
------------------------------------------

    Attachment: dailtwice.txt
                dialonce.txt

> 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)



More information about the asterisk-bugs mailing list