[asterisk-bugs] [JIRA] (ASTERISK-26652) Asterisk hung channels

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-26652:
------------------------------------------

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 hung channels
> ----------------------
>
>                 Key: ASTERISK-26652
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26652
>             Project: Asterisk
>          Issue Type: Information Request
>      Security Level: None
>    Affects Versions: 11.21.2
>         Environment: Centos 6.6. Final running Linux Kernel 2.6.32
>            Reporter: Andrew van Niekerk
>
> We run several hosted PBX at a data center with remote extensions. Most are running fine but there are several of them that get stuck/ghost channels. The only way to fix it is to restart Asterisk otherwise Asterisk crashes eventually once you reach a few thousands calls. Here is an example of when it starts:
> 54 active calls
> 41.221.0.33      4c6765c32fd  28:08:35 0000000000  0000000000 ( 0.00%) 0.0000 0000000000  0000000000 ( 0.00%) 0.0000
> 41.221.0.33      628c3c2b69d  03:49:53 0000000000  0000000000 ( 0.00%) 0.0000 0000000000  0000000000 ( 0.00%) 0.0000
> 77 active SIP channels
> I have tried:
> 1) Increasing max DB connections
> 2) Increasing max open files
> 3) Adjusting jitter buffers
> 4) Added SSD drives to system
> 5) Repaired MySQL DB
> 6) Rebooting



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