[asterisk-bugs] [JIRA] (ASTERISK-28377) Core dump hanging up unanswered channel

[Joshua C. Colp (JIRA)]

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

Joshua C. Colp commented on ASTERISK-28377:
-------------------------------------------

Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description did not include enough information. Please read over the Asterisk Issue Guidelines [1] which discusses the information necessary for your issue to be resolved and the format that information needs to be in. We would be grateful if you would then provide a more complete description of the problem. At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected and the location of documentation that led you to that expectation.
3. The behavior you actually encountered.

To demonstrate the issue in detail, please include Asterisk log files generated per the instructions on the wiki [2]. If applicable, please ensure that protocol-level trace debugging is enabled, e.g., 'sip set debug on' if the issue involves chan_sip, and configuration information such as dialplan and channel configuration.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

[2] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information

We ideally need an ARI application which reproduces this issue - and not just a short description of what you're doing. Arguments and such can play a big part. We also need the console log showing what is going on.

A backtrace from the core dump would also be useful.

> Core dump hanging up unanswered channel
> ---------------------------------------
>
>                 Key: ASTERISK-28377
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28377
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Sorcery
>    Affects Versions: 16.2.1, 16.3.0
>         Environment: x86_64 x86_64 x86_64 GNU/Linux (Centos 7.6.1810) running in a docker container on same OS
>            Reporter: David Dhuyvetter
>         Attachments: bridge.py, core.517.tar.gz, extensions.conf
>
>
> Using ARI
> 1) accept inbound channel
> 2) create outbound channel
> 3) bridge inbound channel to outbound
> 4) dial outbound and let dial timeout expire
> 5) hangup outbound channel and destroy bridge
> 5) hangup inbound channel
> This results in either messages like:
> [2019-04-09 14:58:14.291878] WARNING[401][C-00000001]: bridge.c:1851 bridge_impart_internal: Channel SIP/199.68.168.27-00000000 has a PBX thread and cannot be imparted into bridge 65da81c3-613f-4ad4-a094-98f6e4e6e2c9
> FRACK!, Failed assertion user_data is NULL (0) at line 942 in dial_bridge_after_cb of stasis/control.c
> [2019-04-09 14:58:14.307946] ERROR[401][C-00000001]: stasis/control.c:942 dial_bridge_after_cb: FRACK!, Failed assertion user_data is NULL (0)
> [2019-04-09 14:58:14.308661] ERROR[401][C-00000001]:   Got 11 backtrace records
> # 0: /usr/sbin/asterisk(__ao2_lock+0x1ed) [0x45d59d]
> # 1: /usr/lib64/asterisk/modules/res_stasis.so(+0x151f0) [0x7f8e86f0d1f0]
> # 2: /usr/sbin/asterisk() [0x477251]
> # 3: /usr/sbin/asterisk(ast_datastore_free+0x1c) [0x4ca98c]
> # 4: /usr/sbin/asterisk() [0x499e39]
> # 5: /usr/sbin/asterisk(__ao2_ref+0x25c) [0x45de5c]
> # 6: /usr/sbin/asterisk() [0x52046e]
> # 7: /usr/sbin/asterisk() [0x5210db]
> # 8: /usr/sbin/asterisk() [0x59a149]
> # 9: /lib64/libpthread.so.0(+0x7dd5) [0x7f8eaf191dd5]
> #10: /lib64/libc.so.6(clone+0x6d) [0x7f8eae533ead]
> or Segmentation Fault, or both



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