[asterisk-bugs] [JIRA] (ASTERISK-27666) Checking the HANGUPCAUSE variable, crash asterisk

[Leandro Dardini (JIRA)]

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

Leandro Dardini updated ASTERISK-27666:
---------------------------------------

    Attachment: core.srv02-2018-02-11T07-50-18+0100-brief.txt
                core.srv02-2018-02-11T07-50-18+0100-full.txt
                core.srv02-2018-02-11T07-50-18+0100-locks.txt
                core.srv02-2018-02-11T07-50-18+0100-thread1.txt
                crashlog.pcap

> Checking the HANGUPCAUSE variable, crash asterisk
> -------------------------------------------------
>
>                 Key: ASTERISK-27666
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27666
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/CallCompletionSupplementaryServices
>    Affects Versions: 13.19.0
>         Environment: CentOS 6.9 64bit
>            Reporter: Leandro Dardini
>            Severity: Minor
>         Attachments: core.srv02-2018-02-11T07-50-18+0100-brief.txt, core.srv02-2018-02-11T07-50-18+0100-full.txt, core.srv02-2018-02-11T07-50-18+0100-locks.txt, core.srv02-2018-02-11T07-50-18+0100-thread1.txt, crashlog.pcap
>
>
> I usually log the HANGUPCAUSE when the Dial command doesn't succeed. I discovered, with one particular provider, it crashes asterisk. Here the simple asterisk dialplan:
>         9999 => {
>              Dial(SIP/999383371137 at crashprovider);
>              NoOp(This is CallEnd - DIALSTATUS is ${DIALSTATUS} - HANGUPCAUSE is ${HANGUPCAUSE});
>              }
> In attach, you'll find the crash report and the pcap for the traffic with the server. The call was made from extension 103 (103-DEVEL)



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