[asterisk-bugs] [JIRA] (ASTERISK-24600) Stuck IAX channels, Asterisk stops responding to most traffic, potential deadlock

[Rusty Newton (JIRA)]

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

Rusty Newton commented on ASTERISK-24600:
-----------------------------------------

Additionally, see if you can get an [Asterisk log with "DEBUG" logger type turned up to 5|https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information] and an IAX trace running. We would want to see the last few minutes up until Asterisk stops responding. Then after that moment, if you can get the output of "core show channels" and "iax2 show channels".

> Stuck IAX channels, Asterisk stops responding to most traffic, potential deadlock
> ---------------------------------------------------------------------------------
>
>                 Key: ASTERISK-24600
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24600
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_iax2
>    Affects Versions: 13.0.1
>         Environment: Ubuntu 14.04.1 LTS (trusty) x86_64
>            Reporter: Jeff Collell
>         Attachments: asterisk-bug.PNG, backtrace-threads.txt, core-show-locks.txt, iax.conf, threads-of-interest.txt
>
>
> Setup:
> 20 endpoints, register locally over SIP (no NAT)
> 1 IAX trunk to another remote Asterisk box (unauthenticated, IP restricted on firewalls)
> Server randomly gets 2 IAX channels "stuck" (most likely after the call has ended since we haven't had complaints of dropped calls), stops responding to IAX, SIP registrations, etc. High CPU usage on 2 threads (see attached).
> Issue seems to be happening randomly with calls over trunk (SIP to IAX and IAX to SIP). I can reproduce it by simply creating lots of channels over the trunk (it's not rare, but more channels just means I get the issue to happen sooner, not a load issue). Happens every few dozen calls made by the client (about daily since this is a small office).
> Our next steps will be to configure a SIP trunk between sites to isolate if the issue is IAX specific.



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