[asterisk-bugs] [JIRA] (ASTERISK-25386) Asterisk Chan_sip.c Deadlock. All SIP traffic stops

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-25386:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> Asterisk Chan_sip.c Deadlock. All SIP traffic stops
> ---------------------------------------------------
>
>                 Key: ASTERISK-25386
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25386
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 1.8.15.0, 1.8.32.3
>         Environment: Centos 6.4 Kernel 2.6.32-358.el6.i686. Core i7-3770k Jetway Q77, 8 GB RAM
> Static flatfiles created by Execs. 
>            Reporter: Christopher
>
> All SIP traffic stops randomly. core show channels will never return, core show Locks shows Deadlock in the channel driver. our core show locks looks similar to 21228 and also to 25213. However we are NOT using realtime. this issue occured on average about every 50,000 call completions on 1.8.15-cert5. we installed 1.8.32.3  with DONT_OPTIMIZE, DEBUG_THREADS, BETTER_BACKTRACES, and we are lucky to get 3000 calls being lockups. each time our BT and locks look similar. existing calls continue to progress through applications such as voicemail, queues, etc until they reach a point where chan_sip is required.. (ie a call will continue in the queue until its time to ring an agent.. then that call will hang in dead air). no SIP registrations are accepted. all NOTIFY traffic stops as well. the AMI continues to function. CLI command sip show channels returns, however core show channels hangs. will attach pertinent backtraces



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