[asterisk-bugs] [JIRA] (ASTERISK-22805) Dial using JSSIP results in crash
Matt Jordan (JIRA)
noreply at issues.asterisk.org
Fri Nov 1 10:50:03 CDT 2013
[ https://issues.asterisk.org/jira/browse/ASTERISK-22805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=211439#comment-211439 ]
Matt Jordan commented on ASTERISK-22805:
----------------------------------------
Your backtrace appears to come from an un-optimized version of Asterisk:
{noformat}
#1 0x00007f12f34daa14 in dtls_srtp_check_pending (instance=0x7f132402b7d8, rtp=<value optimized out>) at res_rtp_asterisk.c:1244
pending = <value optimized out>
{noformat}
Are you sure you compiled Asterisk with DONT_OPTIMIZE?
That aside - based on the backtrace, it looks like we're crashing when calling BIO_ctrl_pending:
{noformat}
size_t pending = BIO_ctrl_pending(rtp->write_bio);
{noformat}
If you have the core file, it'd be very interesting to see what the value of {{rtp->write_bio}} is.
Can you attach your {{sip.conf}} to this issue as well? Did you configure {{sip.conf}} to support DTLS-SRTP?
> Dial using JSSIP results in crash
> ---------------------------------
>
> Key: ASTERISK-22805
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-22805
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Channels/chan_sip/General
> Affects Versions: 11.5.1, 11.6.0, 11.7.0
> Environment: Linux 2.6.32-358.18.1.el6.x86_64, OpenSSL 1.0.1e-fips 11 Feb 2013, srtp 1.4.4
> Reporter: Dmitry Burilov
> Assignee: Dmitry Burilov
> Severity: Critical
> Attachments: backtrace.txt
>
>
> Dial from Chrome 30.0.1599.101m via jssip application crash asterisk11.
> -----------gdb output ----------------
> Core was generated by `/usr/sbin/asterisk -f -vvvg -c'.
> Program terminated with signal 11, Segmentation fault.
> #0 0x00007f1353750875 in BIO_ctrl (b=0x7f132403bd80, cmd=10, larg=0, parg=0x0) at bio_lib.c:367
> 367 ((ret=cb(b,BIO_CB_CTRL,parg,cmd,larg,1L)) <= 0))
> (gdb) q
> ----------------------------
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list