| Summary: | ASTERISK-27538: chan_sip: Stuck channels | ||||
| Reporter: | amirali (amirali) | Labels: | |||
| Date Opened: | 2017-12-30 13:27:26.000-0600 | Date Closed: | 2020-01-14 11:14:16.000-0600 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | Channels/chan_sip/General | ||
| Versions: | 13.13.1 14.7.5 | Frequency of Occurrence | |||
| Related Issues: |
| ||||
| Environment: | Description: Debian GNU/Linux 8.7 (jessie) 64 bit | Attachments: | |||
| Description: | Hello
We are facing this issue for sometimes now some of the channels does not hangup in asterisk and it seems happening randomly . I looked at channel states and each are stuck in different state (Ring,BYE,etc) It seems channels are locked somehow and asterisk can not release them. PCC-PP*CLI> core show channels verbose Channel Context Extension Prio State Application Data CallerID Duration Accountcode PeerAccount BridgeID SIP/451-0000188e from-internal 451 1 Ringing AppDial (Outgoing Line) 451 293:47:0 SIP/101-0000188d macro-dial s 11 Ring Dial SIP/451,"",Tt|M(record-mi 101 293:47:0 SIP/231-000031aa from-internal 555 4 Up ChanSpy (Empty) 231 103:14:5 SIP/409-00002a29 polling-19 s 5 Up Read ITEM_NUMBER,custom/Admini 409 132:45:3 SIP/408-00002a2e from-internal 99 1 Up AppQueue (Outgoing Line) 408 132:45:3 Also the dreadful log : [2017-12-30 22:26:20] WARNING[2101]: chan_sip.c:4329 __sip_autodestruct: Autodestruct on dialog '993168359@172.17.106.155' with owner SIP/231-000031aa in place (Method: BYE). Rescheduling destruction for 10000 ms Which repeats many times and asterisk can not kill the channels . Any idea what is happening and how to troubleshoot further ? | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2017-12-30 13:27:27.634-0600 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]. By: Joshua C. Colp (jcolp) 2017-12-30 13:31:06.717-0600 We suspect that you have a deadlock occurring within Asterisk. Please follow the instructions on the wiki [1] for obtaining debug relevant to a deadlock. Once you have that information, attach it to the issue. Be sure the instructions are followed exactly as the debug may otherwise not be useful. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace#GettingaBacktrace-GettingInformationForADeadlock By: amirali (amirali) 2017-12-30 13:56:15.542-0600 I guessed so joshua , I compiled asterisk with debug options as soon as new stuck channels appear i will provide you the logs. By: Asterisk Team (asteriskteam) 2018-01-16 12:00:00.957-0600 Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1]. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines | ||||