[asterisk-bugs] [JIRA] (ASTERISK-26733) asterisk queue segfault

[Rusty Newton (JIRA)]

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

Rusty Newton commented on ASTERISK-26733:
-----------------------------------------

Alex, please read through: https://www.digium.com/products/asterisk/certified-asterisk

bq. SLA customers are provided with Support contacts as a part of their agreement for the purposes of reporting issues to Digium. Issues reported by SLA customers and resolved by Digium will trigger point releases of Certified Asterisk. Issues reported by users who are not SLA customers will not trigger point releases of Certified Asterisk.

Yes, eventually, it will be fixed in a certified Asterisk release, but not in a point release unless you are a Digium customer and reporting it to Digium under SLA.

Please read through the whole page and FAQ to better understand the purpose of Certified Asterisk. You can direct any further questions to Digium sales. https://www.digium.com/content/contact-digium-sales

Closing out this issue as a duplicate for ASTERISK-25888.

> asterisk queue segfault
> -----------------------
>
>                 Key: ASTERISK-26733
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26733
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue
>    Affects Versions: 13.8.0
>         Environment: Centos 7 
> 3.10.0-514.2.2.el7.x86_64 #1 SMP
> Asterisk certified/13.8-cert4
>            Reporter: Alex
>            Severity: Critical
>         Attachments: backtrace.txt
>
>
> Hi! I use Asterisk 13.8-cert4. From time to time in log I get
> asterisk[1704]: segfault at 154 ip 00007fab89f3a497 sp 00007fab4b948850 error 4 in app_queue.so[7fab89f26000+35000]
> PS. ringinuse is set to 'no'.
> PPS. Is this problem similar to ASTERISK-25888? Will it be fixed for certified version? 



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