[asterisk-bugs] [JIRA] (ASTERISK-26764) chan_pjsip: Crash looking up PJSIP call-id on hungup channel.

[Daniel Journo (JIRA)]

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

Daniel Journo commented on ASTERISK-26764:
------------------------------------------

Frequency for me is about 10 times today on 4 separate servers.
13.14.0-rc1 was installed 3 weeks ago, and suddenly today, it's broken.
I did make a few dialplan changes but I've tested the dialplan and it appears to work fine.
The CLI doesn't show anything obvious, nor points to any specific line in the dialplan.


> chan_pjsip: Crash looking up PJSIP call-id on hungup channel.
> -------------------------------------------------------------
>
>                 Key: ASTERISK-26764
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26764
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip
>    Affects Versions: 13.13.1
>         Environment: kubuntu 10.04 32-bit
>            Reporter: Richard Mudgett
>         Attachments: asterisk_26764_testsuite_logs.zip, backtrace.txt, full backtrace.txt
>
>
> Got a crash during testsuite test:
> channels/pjsip/transfers/blind_transfer/caller_refer_only
> res_hep_rtcp was processing a stasis bus message and trying to lookup the PJSIP channel's call-id in assign_uuid().  This is a third-party thread trying to get the call-id of a channel that may get hung up while trying to get the information.  The dialplan function CHANNEL(pjsip,call-id) calls pjsip_acf_channel_read() which indirectly calls read_pjsip() in another thread.  read_pjsip() then calls channel_read_pjsip() which can crash if the channel is hungup by the time execution gets to channel_read_pjsip().



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